FOR DUAL SIM IMEI REDMI 9
REDMI 9 IMEI NULL/ERROR
1. PREPARE rom_eng/CSC according to each device, take the file preload&cust&md1img to be replaced or moved to a global rom
(use: when reading dimauimeta it's easier & can directly write imei , remember only imei
2, if you want everything you have to install the STROMBAKER FOR LANCELOT kernel)
2. Direct flash global rom version preferably below 11.8.O (remember to replace 3 files numbered 1), after flashing, open Mauimeta and click connect, just unplug and plug it in directly without having to turn it off, write only IMEI 2 (safe for initial boot and backup process), then disconnect & turn on the cellphone normally.
3. After the main menu appears, just check the IMEI has appeared in *#06# or in the settings, if you can unlock the bootloader, you can go to the next stage.
4. unlockbootloader, install twrp preferably version 3.5.2, then in twrp backup only nvdata & nvram& boot, then install strombreaker kernel or special interest in lancelot.
5. directly open Mauimeta click connect, in twrp just restart the system and finally Mauimeta reads automatically, then enter both IMEI and restart again, and check IMEI *#06#
6. if you want to keep using the kernel, you don't have to continue this step, but if you want the original kernel, we continue.
back to twrp, just restore the backup results and restart, check the imei, both are still complete and change only the kernel (return to the original kernel)
7. I tried to upgrade to a rom, the only remaining IMEI 2, if you want 2 IMEI to read, do the above steps again.
ATTENTION: do not update the rom for sure the imei will be lost.
my advice:
MAUIMETA ~ requires preload reading which I suggest replacing earlier & cdc (well, we install this cdc manually, download the file, when Mauimeta asks for our cdc in the computer manager and we install it manually on the reading in question in the computer manager).
LIBUSB~ is useful for locking the mtk preload when first plugged into the computer.
BYPASSMTK~ is useful for locking preloads but with preload changed from rom_eng, so bypass software is not needed when flashing.
so the important thing from these 3 points is the cdc file
very few people want to explain this wide in my opinion.
thanks for CAMMARA.
{
"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"
}
Quote Reply
Report
[IMG alt="Raiz"]https://forum.xda-developers.com/data/avatars/s/8020/8020437.jpg?1606891852[/IMG]
RaizForum Moderator
Staff member
12 minutes ago
SEE YOU NOW said:
FOR DUAL SIM IMEI REDMI 9
REDMI 9 IMEI NULL/ERROR
1. PREPARE rom_eng/CSC according to each device, take the file preload&cust&md1img to be replaced or moved to a global rom
(use: when reading dimauimeta it's easier & can directly write imei , remember only imei
2, if you want everything you have to install the STROMBAKER FOR LANCELOT kernel)
2. Direct flash global rom version preferably below 11.8.O (remember to replace 3 files numbered 1), after flashing, open Mauimeta and click connect, just unplug and plug it in directly without having to turn it off, write only IMEI 2 (safe for initial boot and backup process), then disconnect & turn on the cellphone normally.
3. After the main menu appears, just check the IMEI has appeared in *#06# or in the settings, if you can unlock the bootloader, you can go to the next stage.
4. unlockbootloader, install twrp preferably version 3.5.2, then in twrp backup only nvdata & nvram& boot, then install strombreaker kernel or special interest in lancelot.
5. directly open Mauimeta click connect, in twrp just restart the system and finally Mauimeta reads automatically, then enter both IMEI and restart again, and check IMEI *#06#
6. if you want to keep using the kernel, you don't have to continue this step, but if you want the original kernel, we continue.
back to twrp, just restore the backup results and restart, check the imei, both are still complete and change only the kernel (return to the original kernel)
7. I tried to upgrade to a rom, the only remaining IMEI 2, if you want 2 IMEI to read, do the above steps again.
ATTENTION: do not update the rom for sure the imei will be lost.
my advice:
MAUIMETA ~ requires preload reading which I suggest replacing earlier & cdc (well, we install this cdc manually, download the file, when Mauimeta asks for our cdc in the computer manager and we install it manually on the reading in question in the computer manager).
LIBUSB~ is useful for locking the mtk preload when first plugged into the computer.
BYPASSMTK~ is useful for locking preloads but with preload changed from rom_eng, so bypass software is not needed when flashing.
so the important thing from these 3 points is the cdc file
very few people want to explain this wide in my opinion.
thanks for CAMMARA.
Click to expand...
Click to collapse
I tried it with Miui 12.5 with android 11 and it didn't worked. I mean, I already had the IMEI 2 written and working, but when I installed the stormbreaker kernel it was softbricked, and not detected by MauiMETA. So I didn't go any further. Is there any advice for this?
migueacastro said:
Saya mencobanya dengan MIUI 12.5 dengan Android 11 dan tidak berhasil. Maksud saya, IMEI 2 saya sudah ditulis dan berfungsi, tetapi ketika saya menginstal kernel stormbreaker itu menjadi softbrick, dan tidak terdeteksi oleh MauiMETA. Jadi saya tidak melangkah lebih jauh. Apakah ada saran untuk ini?
Click to expand...
Click to collapse
It's still giving me that problem, I mean, it softbricks after flashing that kernel
migueacastro said:
Itu masih memberi saya masalah itu, maksud saya, itu softbricks setelah menginstal kernel itu
Click to expand...
Click to collapse
kernel use if you done flash rom global and can open menu normal
after that you instal kernel
if you instal kernel after flash, you phone will error to register activation
i am indonesia, very hard to english language
What flash tool did you use
Did you flash in fastboot? Sorry im newbiee
kazuhiko23124 said:
Did you flash in fastboot? Sorry im newbiee
Click to expand...
Click to collapse
the essence of writing imei is only preload from rom_eng and md1img.img from rom_eng
the process
1. just flash preload and md1img
preload : to read boot without complicated bypass
md1img : for imei writing permission
after flash md1img we must format nvdata and nvram from flashtool so that no errors occur when entering Mauimeta (data format is in scatter)
2. For IMEI writing, use the Mauimeta application, IMEI writing is only for IMEI Sim2, if all are written, there will be an error.
3. If you want 2 IMEIs to be written, you have to complete the above process until the start menu opens, then go back to TWRP, install the Strombreaker kernel, then open Mauimeta again, just write down all IMEIs (kernel works fine on ROM 11.0.9 or above)
required files:
1.preload.bin from rom_eng
2.md1img.img from rom_eng
3.mauimeta good version 10
4.cdc driver for advanced reading of mauimeta
5. flashtool with DA and AUTH, can be used bypass
6.unlockbootloader for those who want to use the strombreker kernel via twrp,
7. the root process is easier in minimaladb
100% success guaranteed
hckbkl said:
the essence of writing imei is only preload from rom_eng and md1img.img from rom_eng
the process
1. just flash preload and md1img
preload : to read boot without complicated bypass
md1img : for imei writing permission
after flash md1img we must format nvdata and nvram from flashtool so that no errors occur when entering Mauimeta (data format is in scatter)
2. For IMEI writing, use the Mauimeta application, IMEI writing is only for IMEI Sim2, if all are written, there will be an error.
3. If you want 2 IMEIs to be written, you have to complete the above process until the start menu opens, then go back to TWRP, install the Strombreaker kernel, then open Mauimeta again, just write down all IMEIs (kernel works fine on ROM 11.0.9 or above)
required files:
1.preload.bin from rom_eng
2.md1img.img from rom_eng
3.mauimeta good version 10
4.cdc driver for advanced reading of mauimeta
5. flashtool with DA and AUTH, can be used bypass
6.unlockbootloader for those who want to use the strombreker kernel via twrp,
7. the root process is easier in minimaladb
100% success guaranteed
Click to expand...
Click to collapse
The preload and md1mg will be copied from rom eng? And then move it to global rom(11.0.9)? And then flash it?
kazuhiko23124 said:
The preload and md1mg will be copied from rom eng? And then move it to global rom(11.0.9)? And then flash it?
Click to expand...
Click to collapse
no,
flashing version 11.0.9.
after than flash just preload & md1img,
than you will bee write imei with mauimeta
remember only imei simcard 2 if you not instaling kernel
step
1.flasing v11.0.9
2.unlockboitloader & instal twrp
3.flash md1img & preload rom_eng
4.format nvdata & nvram, addres & partition in scatter rom folder image
5.open mauimeta write imei simcard2(if not use kernel),if 2 imei write after write imei you reboot to twrp and instaling kernel(best strombreaker)
enjoy
hckbkl said:
no,
flashing version 11.0.9.
after than flash just preload & md1img,
than you will bee write imei with mauimeta
remember only imei simcard 2 if you not instaling kernel
step
1.flasing v11.0.9
2.unlockboitloader & instal twrp
3.flash md1img & preload rom_eng
4.format nvdata & nvram, addres & partition in scatter rom folder image
5.open mauimeta write imei simcard2(if not use kernel),if 2 imei write after write imei you reboot to twrp and instaling kernel(best strombreaker)
enjoy
Click to expand...
Click to collapse
If I already have miui 11.0.9 , i will just flash it just like this?
z
hckbkl said:
no,
flashing version 11.0.9.
after than flash just preload & md1img,
than you will bee write imei with mauimeta
remember only imei simcard 2 if you not instaling kernel
step
1.flasing v11.0.9
2.unlockboitloader & instal twrp
3.flash md1img & preload rom_eng
4.format nvdata & nvram, addres & partition in scatter rom folder image
5.open mauimeta write imei simcard2(if not use kernel),if 2 imei write after write imei you reboot to twrp and instaling kernel(best strombreaker)
enjoy
Click to expand...
Click to collapse
or i will just replace the preloader and md1img from eng rom in miui 11 and then flash it in fastboot? if yes sir, which preloader i will choose preloader.img, preloader_emmc.img, pre loader_lancelot.bin or pre loader.ufs?
kazuhiko23124 said:
View attachment 5394409or i will just replace the preloader and md1img from eng rom in miui 11 and then flash it in fastboot? if yes sir, which preloader i will choose preloader.img, preloader_emmc.img, pre loader_lancelot.bin or pre loader.ufs?
Click to expand...
Click to collapse
after flash you format nvdata & nvram.
after that open mauimeta write imei simcard 2.reboot
hckbkl said:
after flash you format nvdata & nvram.
after that open mauimeta write imei simcard 2.reboot
Click to expand...
Click to collapse
I still dont get it sir, im sorry I am too newbie for this
hckbkl said:
after flash you format nvdata & nvram.
after that open mauimeta write imei simcard 2.reboot
Click to expand...
Click to collapse
how to format nvdata and nv ram sir
kazuhiko23124 said:
cara memformat nvdata dan nv ram pak
Click to expand...
Click to collapse
open scatter in your rom v11.0.9
in folder image ,open scatter.txt copy addres number & partition number to spflashtool(nvdata & nvram search)
format manual in spflastool like flash rom
after that open mauimeta to write imei simcard 2
kazuhiko23124 said:
how to format nvdata and nv ram sir
Click to expand...
Click to collapse
news trick
# for not unlock bootloader
1.preload.bin and md1img.img from rom_eng
2. flash format&download or flash download rom version 11.0.9 (insert or replace the preload file from rom_eng)
3. when finished, flash only md1img from rom_eng then format nvdata (the format code number is discatter)
4. after that open mauimeta(cdc drive is needed to read imei) write only imei simcard 2, reboot
5. Please enter micloud & register for the unlockbootloader process if needed.
# for already unlocked bootloader
6. root hp & go to twrp install strombreaker kernel, restart and enter mauimeta write both imei simcard 1 & 2
7. flash again using rom version 11.0.9 uncheck recovery, vbmeta (all vbmeta), userdata, super, boot, logo, md1img.
hckbkl said:
news trick
# for not unlock bootloader
1.preload.bin and md1img.img from rom_eng
2. flash format&download or flash download rom version 11.0.9 (insert or replace the preload file from rom_eng)
3. when finished, flash only md1img from rom_eng then format nvdata (the format code number is discatter)
4. after that open mauimeta(cdc drive is needed to read imei) write only imei simcard 2, reboot
5. Please enter micloud & register for the unlockbootloader process if needed.
# for already unlocked bootloader
6. root hp & go to twrp install strombreaker kernel, restart and enter mauimeta write both imei simcard 1 & 2
7. flash again using rom version 11.0.9 uncheck recovery, vbmeta (all vbmeta), userdata, super, boot, logo, md1img.
Click to expand...
Click to collapse
What is hp sir
You mean root my device? And then Im going to install twrp? If I successfully installed the twrp, Im going to reboot my device? And enter mauimeta? (In what state fastboot or just turn off the phone for entering mauimeta?)
Then if im successfully write both imei 1 and 2
Im going to flash the miui 11.0.9 and uncheck recovery, vbmeta, user data, super, boot, logo, md1mg?( in fastboot too?)
Related
Hi.
My 9300+ (chinese mtk6577) is dead... I have to updated wrong firmware and my phone will don't turn ON again, when I use the SP Flash Tool appears the message: "Firmware Upgrade could not be executed without PMT. Please "Download" ONLY first to create PMT on the target!
My internal partition is corrupted and i can't create PMT because my phone don't Turn On, but my USB is recognized by windows.
Please Help Me.
rstalker said:
Hi.
My 9300+ (chinese mtk6577) is dead... I have to updated wrong firmware and my phone will don't turn ON again, when I use the SP Flash Tool appears the message: "Firmware Upgrade could not be executed without PMT. Please "Download" ONLY first to create PMT on the target!
My internal partition is corrupted and i can't create PMT because my phone don't Turn On, but my USB is recognized by windows.
Please Help Me.
Click to expand...
Click to collapse
I know this is an old post, but this may help someone. (would have me a month ago)
Hopefully if your USB is seen in Windows you can convince SP Flash Tool to spew/download/write data to your phone while it's in Meta Mode.
I believe the PMT block is created by SP Flash Tool dynamically from scatter file. It's comparing the scatter file with what is sitting at the PMT address on the flash. If these two mismatch, you get the error you mentioned. If you want to force a new PMT that matches your scatter file's layout, you have to do a "Format" in SP Flash Tool. This will get you back to a PMT on flash that matches your scatter file, then SP Flash Tool will be happy and allow you to use Download (write to flash).
What is a PMT? A partition table that holds the addresses to all the other partitions.
syserr said:
I know this is an old post, but this may help someone. (would have me a month ago)
Hopefully if your USB is seen in Windows you can convince SP Flash Tool to spew/download/write data to your phone while it's in Meta Mode.
I believe the PMT block is created by SP Flash Tool dynamically from scatter file. It's comparing the scatter file with what is sitting at the PMT address on the flash. If these two mismatch, you get the error you mentioned. If you want to force a new PMT that matches your scatter file's layout, you have to do a "Format" in SP Flash Tool. This will get you back to a PMT on flash that matches your scatter file, then SP Flash Tool will be happy and allow you to use Download (write to flash).
What is a PMT? A partition table that holds the addresses to all the other partitions.
Click to expand...
Click to collapse
THANK YOU! :highfive::highfive::highfive::highfive::highfive::highfive:
LOVE YOU MAN
PMT Corrupted & Format-all done
I faced the same error.......my PMT got corrupted (possibly due to an earlier attempt to re-size (system / data) partition using Swiftbootloader)...... & un-fortunately, I clicked on Format in SP Flash Tool as well.
Now all is gone.... phone doesn't switch on.........
Please guide...... to bring the bricked handset (Spice Mi-350n) to life again. I have backups..... but that relate to different scatter file (PMT) perhaps........ do I need to search & learn webos & acmeinstaller kind of things now?
spandrd said:
I faced the same error.......my PMT got corrupted (possibly due to an earlier attempt to re-size (system / data) partition using Swiftbootloader)...... & un-fortunately, I clicked on Format in SP Flash Tool as well.
Now all is gone.... phone doesn't switch on.........
Please guide...... to bring the bricked handset (Spice Mi-350n) to life again. I have backups..... but that relate to different scatter file (PMT) perhaps........ do I need to search & learn webos & acmeinstaller kind of things now?
Click to expand...
Click to collapse
Hi spandrd,
did u manage to resolve this problem. I am also facing this problem after attempting to re-size the partition using meteos mtk6589 rom edit apk .... Although my phone is still working properly without any issue, i am unable to root or install CWM by any means (tried mtk mobileuncle tools, tried spflash tool) but not working. Can you guide me how to root and install cwm as i am unable to revert to my old backup w/o cwm.
spandrd said:
I faced the same error.......my PMT got corrupted (possibly due to an earlier attempt to re-size (system / data) partition using Swiftbootloader)...... & un-fortunately, I clicked on Format in SP Flash Tool as well.
Now all is gone.... phone doesn't switch on.........
Please guide...... to bring the bricked handset (Spice Mi-350n) to life again. I have backups..... but that relate to different scatter file (PMT) perhaps........ do I need to search & learn webos & acmeinstaller kind of things now?
Click to expand...
Click to collapse
HNaseer said:
Hi spandrd,
did u manage to resolve this problem. I am also facing this problem after attempting to re-size the partition using meteos mtk6589 rom edit apk .... Although my phone is still working properly without any issue, i am unable to root or install CWM by any means (tried mtk mobileuncle tools, tried spflash tool) but not working. Can you guide me how to root and install cwm as i am unable to revert to my old backup w/o cwm.
Click to expand...
Click to collapse
The best way to restore your phone was already answered in the previous post, that is to FORMAT your device and subsequently flash the official firmware.
syserr said:
I know this is an old post, but this may help someone. (would have me a month ago)
Hopefully if your USB is seen in Windows you can convince SP Flash Tool to spew/download/write data to your phone while it's in Meta Mode.
I believe the PMT block is created by SP Flash Tool dynamically from scatter file. It's comparing the scatter file with what is sitting at the PMT address on the flash. If these two mismatch, you get the error you mentioned. If you want to force a new PMT that matches your scatter file's layout, you have to do a "Format" in SP Flash Tool. This will get you back to a PMT on flash that matches your scatter file, then SP Flash Tool will be happy and allow you to use Download (write to flash).
What is a PMT? A partition table that holds the addresses to all the other partitions.
Click to expand...
Click to collapse
iZLeeP said:
The best way to restore your phone was already answered in the previous post, that is to FORMAT your device and subsequently flash the official firmware.
Click to expand...
Click to collapse
Hi iZLeeP
Thanks for the quick reply. I dont have any official rom. The only backup i have is using the CWM backup of the official rom before applying a custom LG rom. If it is possible, how can i utilize the CWM backup of the official rom to revert back please ? I can see boot.img and recovery.img files in cwm backup; can i utilize them somehow to revert back ? Please help. Thanks.
HNaseer said:
Hi iZLeeP
Thanks for the quick reply. I dont have any official rom. The only backup i have is using the CWM backup of the official rom before applying a custom LG rom. If it is possible, how can i utilize the CWM backup of the official rom to revert back please ? I can see boot.img and recovery.img files in cwm backup; can i utilize them somehow to revert back ? Please help. Thanks.
Click to expand...
Click to collapse
Let me remind people, the first order of business must be to have a full firmware backup from the phone manufacturer or thru MTK Droid Root & Tools. Reading that you tried to resize your system & data partition, your cwm backup should not be affected by it. Try restoring to default the partition sizes using the app/script you used to resize. It should have that function. Then flash custom recovery and root and see if it works.
phone booting to main-screen or not?
hi HNaseer....
As replied by @syserr & @iZLeeP .............you can try to "Format-All / Format-All except bootloader" type of thing PROVIDED THAT YOU HAVE COMPLETE BACKUP OF RELEVANT PARTITIONS (till Cache and / or till FAT partition length) using SP Flash Tool........ & MTK Droid Tool......... PLUS, YOU WILL NEED IMEI BACKUP (IMEI No.) in such case if you want to restore.
SP Flash Tool needs Scatter File......... (obtainable thru MTK Droid Tool) & can help in backup of various partitions even if phone not turning on. BUT IMEI backup would be good........ IF YOU ARE ABLE TO BOOT / reach main screen after boot animation.
Rest of the details can be first read / understood from my MT6589 chipset type handset link from @Atrvscet : http://forum.xda-developers.com/showthread.php?t=2514419
Or, better search exact thread on xda / elsewhere to get stock / custom rom & flashing etc.
Lastly, if you are able to boot in recovery, best thing should be to flash / force flash original cwm backup from recovery.
HNaseer said:
Hi spandrd,
did u manage to resolve this problem. I am also facing this problem after attempting to re-size the partition using meteos mtk6589 rom edit apk .... Although my phone is still working properly without any issue, i am unable to root or install CWM by any means (tried mtk mobileuncle tools, tried spflash tool) but not working. Can you guide me how to root and install cwm as i am unable to revert to my old backup w/o cwm.
Click to expand...
Click to collapse
spandrd said:
hi HNaseer....
As replied by @syserr & @iZLeeP .............you can try to "Format-All / Format-All except bootloader" type of thing PROVIDED THAT YOU HAVE COMPLETE BACKUP OF RELEVANT PARTITIONS (till Cache and / or till FAT partition length) using SP Flash Tool........ & MTK Droid Tool......... PLUS, YOU WILL NEED IMEI BACKUP (IMEI No.) in such case if you want to restore.
SP Flash Tool needs Scatter File......... (obtainable thru MTK Droid Tool) & can help in backup of various partitions even if phone not turning on. BUT IMEI backup would be good........ IF YOU ARE ABLE TO BOOT / reach main screen after boot animation.
Rest of the details can be first read / understood from my MT6589 chipset type handset link from @Atrvscet : http://forum.xda-developers.com/showthread.php?t=2514419
Or, better search exact thread on xda / elsewhere to get stock / custom rom & flashing etc.
Lastly, if you are able to boot in recovery, best thing should be to flash / force flash original cwm backup from recovery.
Click to expand...
Click to collapse
HNaseer.... I agree with everything spandrd just said. I'd like to stress though, getting a backup of your NVRAM partition is much better than having MTKDT copy your /data/nvram. So if you have a choice, backup the NVRAM partition with SPFT or if MTKDT has that option use it. (I've rarely used MTKDT as I found aspects confusing)
Incredible.
Thank you so much. HAd almost given up hope...
How to connect mtk6582device (spice dream uno) in meta mode
Plz help me out guys ??????
I have a similar issue with my Unite 2 phone. I tried the format option too but I am getting STORAGE_ERROR
[Storage Error] The load and the target are inconsistent!
A Hint message is also there :
The load to be downloaded is for EMMC.
The Target storage is .
Please select a correct load according to the storage.
Please help me in resolving this issue. My phone model is Micromac unite 2 A106 8GB model.
syserr said:
HNaseer.... I agree with everything spandrd just said. I'd like to stress though, getting a backup of your NVRAM partition is much better than having MTKDT copy your /data/nvram. So if you have a choice, backup the NVRAM partition with SPFT or if MTKDT has that option use it. (I've rarely used MTKDT as I found aspects confusing)
Click to expand...
Click to collapse
hello guys
how can i format my device Blu studio energy 2 with sp flash toolmy phone is dead after i do the format and i dont have firmware back up
thank you
---------- Post added at 01:24 AM ---------- Previous post was at 12:26 AM ----------
hello guys
how can i format my device Blu studio energy 2 with sp flash tool my phone is dead after i do the format and i dont have firmware back up
thank you
Omarod said:
hello guys
how can i format my device Blu studio energy 2 with sp flash toolmy phone is dead after i do the format and i dont have firmware back up
thank you
Not sure what you are expecting to do with a FORMAT. If you had a good backup of your NVRAM partition, then what you would need is a SCATTER file and ROM files, you could FORMAT then DOWNLOAD the ROM files and your NVRAM file to your device with SPFT. But since you don't have your NVRAM partition, you don't have an easy path. FYI, I don't know new devices... there could be more complication than MT6577/75.
Click to expand...
Click to collapse
syserr said:
Omarod said:
hello guys
how can i format my device Blu studio energy 2 with sp flash toolmy phone is dead after i do the format and i dont have firmware back up
thank you
Not sure what you are expecting to do with a FORMAT. If you had a good backup of your NVRAM partition, then what you would need is a SCATTER file and ROM files, you could FORMAT then DOWNLOAD the ROM files and your NVRAM file to your device with SPFT. But since you don't have your NVRAM partition, you don't have an easy path. FYI, I don't know new devices... there could be more complication than MT6577/75.
Click to expand...
Click to collapse
Thank you for reply
Where do i find the scatter file and the ROM for my blu studio energy 2 MT6735 chepset please
Thank you again
Click to expand...
Click to collapse
Omarod said:
syserr said:
Thank you for reply
Where do i find the scatter file and the ROM for my blu studio energy 2 MT6735 chepset please
Thank you again
Click to expand...
Click to collapse
Try google, or search xda, or needrom.com...
This may or may not help you. If I were you I would use SPFT right now to try to backup your NVRAM partition if it's not too late. Your FORMAT may have wiped the NVRAM partition already. If it has wiped it, your only good path is to find someone willing to give you their NVRAM partition. Then somehow insert your own IMEI and WIFI MAC in and pray.
Click to expand...
Click to collapse
Could you tell me step by step what can I do coz I'm new in sp flash tool and. Mtk droid root and flash tool
Thank you so much
First find proper ROM on www.needrom.com
Hello Guys
still waiting for help please
Blu Studio Energy 2 -Backup file- firmware Please
No IMEI, No Baseband, No Backup? - SOLUTION ~ Soft Bricked from No IMEI, No Baseband, No RIL, No WiFi MAC, BT MAC, comms etc.
DISCLAIMER:
*What you done to your phone is at your OWN RISK, you choose to do this modifications to your phone and don't blame me if anything goes wrong.
Preface:
Recently I have noticed many people who tried to flash Custom ROM's on P780 and causes the phone to lose IMEI, Baseband, RIL, WiFi MAC, BT MAC, SN, comms etc. and causes connectivity issues (including me), which renders our phone turned into a "AndroidPod" media device that cannot make calls, SMS etc. As an example, my phone which faced the exactly same problem.
{
"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"
}
See the IMEI and baseband are still there in factory mode!!!
What could cause this is problem to occur is probably during ROM flashing process, the installer probably wiped out the /data/nvram (folder/partition). The /data/nvram (folder/partition) is the heart of your phone of all communicating feature, if the (folder/partition) is corrupted, just like I said, no communication features.
*Actually the baseband is there, but because the /nvram (folder/partition) has corrupted, the Android OS were unable to recognize it thus showing Unknown.
So no backup = Phone dead? Nothing but a media player?
First step, ensure your phone:
On Stock ROM
Rooted
PC have ADB drivers installed (If you don't have it please ask Uncle Google :good
Well, that isn't true, recently I found out, the phone can actually be easily recovered (on most MediaTek devices) and gain at least those comm features back by simply delete the whole /nvram (folder/partiton). If your phone coldn't recognize SIM card, wait a while after deleted the folder, your phone should have signal after maximum 10 seconds of waiting.
*In most of the cases MobileUncleTools give AT command failed to send probably the /nvram folder is corrupted, simply delete the NVRAM folder and reboot will do.
For WiFi MAC address fix (WiFi NVRAM WARNING: ERR 0x10), because the solution already been posted, so please click here.
Bluetooth MAC address fix: Firstly, using any File Explorer with Root abilities navigate to /data/nvram/APCFG/APRDEB/BT_Addr and also a BT_Addr file under /data, then copy both files to your PC. Then open up the file by using Hex Editor (HHD Hex Editor). To fix a static MAC address, just simply type in your MAC address on the first row (0000) from column (00-05). That is what your MAC address should be (Edit both files with the same MAC address). After you have modified it, put it back in the exact location and remember to change permission.
Actually you can also get restore your IMEI, WiFi MAC, BT MAC, SN by restoring a backup created by MTKDroidTools with other exact same model as your phone.
Reserved.
Lenovo p780 dead
soralz said:
Reserved.
Click to expand...
Click to collapse
By using uncle tool, i flash recovery file and my phone lost sim card features, and work like tablet. later i did once again with another recovery file, now my phone did not start it just appear "lenovo" for 10 second and blank screen for 10 seconds. how i can restore my phone?
aavama said:
By using uncle tool, i flash recovery file and my phone lost sim card features, and work like tablet. later i did once again with another recovery file, now my phone did not start it just appear "lenovo" for 10 second and blank screen for 10 seconds. how i can restore my phone?
Click to expand...
Click to collapse
Just reflash your rom again. Look on my posts on Q&A posts.
Sent from my Lenovo P780 with LiFe v.07 and TWRP 2.6.3.0
aavama said:
By using uncle tool, i flash recovery file and my phone lost sim card features, and work like tablet. later i did once again with another recovery file, now my phone did not start it just appear "lenovo" for 10 second and blank screen for 10 seconds. how i can restore my phone?
Click to expand...
Click to collapse
If not working after you've reflash the ROM, try delete the /nvram folder. Make a backup of the folder first with MTKDroidTools before delete!!!. (Although it is corrupted)
aavama said:
By using uncle tool, i flash recovery file and my phone lost sim card features, and work like tablet. later i did once again with another recovery file, now my phone did not start it just appear "lenovo" for 10 second and blank screen for 10 seconds. how i can restore my phone?
Click to expand...
Click to collapse
actually mobile in bootloop mod. doest not start
and also how to flash in right way. I have s123 version
aavama said:
actually mobile in bootloop mod. doest not start
and also how to flash in right way. I have s123 version
Click to expand...
Click to collapse
Best way how to flash any ROM is using PC and SP flash tools.,
stympy said:
Just reflash your rom again. Look on my posts on Q&A posts.
Sent from my Lenovo P780 with LiFe v.07 and TWRP 2.6.3.0
Click to expand...
Click to collapse
lenovo P780 Life 07 said:
Best way how to flash any ROM is using PC and SP flash tools.,
Click to expand...
Click to collapse
can u post link to flash tool?
thanks
aavama said:
can u post link to flash tool?
thanks
Click to expand...
Click to collapse
http://forum.xda-developers.com/lenovo-p780/development/lenovo-p780-guide-t2658144
lenovo P780 Life 07 said:
http://forum.xda-developers.com/lenovo-p780/development/lenovo-p780-guide-t2658144
Click to expand...
Click to collapse
my phone did not on
its on boot loop mode so not able to use uncle tool. and in flash mode I did not find scatter file. where it is located?
thanks once agian
aavama said:
my phone did not on
its on boot loop mode so not able to use uncle tool. and in flash mode I did not find scatter file. where it is located?
thanks once agian
Click to expand...
Click to collapse
Scatter file is usually inside the unzipped ROM and has name : MT6589_Android_scatter_emmc.txt, read this link before once again.
U can try use small red button near memory card.
But I speaking here about flashing ROM from PC and SP flash tools not mobil uncle.
lenovo P780 Life 07 said:
Scatter file is usually inside the unzipped ROM and has name : MT6589_Android_scatter_emmc.txt, read this link before once again.
U can try use small red button near memory card.
But I speaking here about flashing ROM from PC and SP flash tools not mobil uncle.
Click to expand...
Click to collapse
thanks
I will check and reply
aavama said:
my phone did not on
its on boot loop mode so not able to use uncle tool. and in flash mode I did not find scatter file. where it is located?
thanks once agian
Click to expand...
Click to collapse
i down loaded ROM from following link
http://www.needrom.com/mobile/lenovo-p780-miui/
but not found MT6589_Android_scatter_emmc.txt in ROM
aavama said:
i down loaded ROM from following link
http://www.needrom.com/mobile/lenovo-p780-miui/
but not found MT6589_Android_scatter_emmc.txt in ROM
Click to expand...
Click to collapse
how to install TWRP?
aavama said:
i down loaded ROM from following link
http://www.needrom.com/mobile/lenovo-p780-miui/
but not found MT6589_Android_scatter_emmc.txt in ROM
Click to expand...
Click to collapse
Hi. Look close here what i am writing.
First step is to download from here: http://forum.xda-developers.com/lenovo-p780/development/rom-lenovo-p780-pre-rooted-official-t2553725
this: P780_ROW_S124_140403_rooted_twrp_gapps.7z
and from here flash tool: http://www.androidfilehost.com/?fid=23252070760972674
Second step is to unzip ROM and flash tool in separate folders.
Third step is to open flash tool.
After you open flash tool look in that picture i uploadet and see where you must introduce the scatter file is number 1. Press that button and browse in to the rom directory for the scatter file.
After that check DA/DLa with check button is number 2. DO NOT FORGET THIS STEP. IS CRUCIAL.
POWER OFF YOUR PHONE.
Press firmware upgrade button is near number 3, and after this insert the cable in to the phone. Flashing should start.
stympy said:
Hi. Look close here what i am writing.
First step is to download from here: http://forum.xda-developers.com/lenovo-p780/development/rom-lenovo-p780-pre-rooted-official-t2553725
this: P780_ROW_S124_140403_rooted_twrp_gapps.7z
and from here flash tool: http://www.androidfilehost.com/?fid=23252070760972674
Second step is to unzip ROM and flash tool in separate folders.
Third step is to open flash tool.
After you open flash tool look in that picture i uploadet and see where you must introduce the scatter file is number 1. Press that button and browse in to the rom directory for the scatter file.
After that check DA/DLa with check button is number 2. DO NOT FORGET THIS STEP. IS CRUCIAL.
POWER OFF YOUR PHONE.
Press firmware upgrade button is near number 3, and after this insert the cable in to the phone. Flashing should start.
Click to expand...
Click to collapse
thanks Dear
now mobile working with new ROM 126
but i want to know about twrp, how i can install it? i want to install custom ROM MUI, how i can do it?
thanks again for helping me
aavama said:
thanks Dear
now mobile working with new ROM 126
but i want to know about twrp, how i can install it? i want to install custom ROM MUI, how i can do it?
thanks again for helping me
Click to expand...
Click to collapse
Hi. You must doit by steps:
1. Install m44-toolbox.apk from archive i attched;
2. There you will find CWM Recovery;
3. Install it with this apk;
4. Reboot to recovery(Shoot down your phone, then power on with POWER AND VOL UP AND VOL DOWN pressed.) CWM is allmost like TWRP.
5. Download MIUI to SD Card not internal memory.
6. Flash-it from SDCARD.
stympy said:
Hi. You must doit by steps:
1. Install m44-toolbox.apk from archive i attched;
2. There you will find CWM Recovery;
3. Install it with this apk;
4. Reboot to recovery(Shoot down your phone, then power on with POWER AND VOL UP AND VOL DOWN pressed.) CWM is allmost like TWRP.
5. Download MIUI to SD Card not internal memory.
6. Flash-it from SDCARD.
Click to expand...
Click to collapse
Thanks for taking pain
I down loaded file
Un zip and put in sd card
Open M44 apk
Updatr recovery u provided
App asked to reboot in recovery. I did it and phone went in bootloop
So I have flashed s123 with pv
aavama said:
Thanks for taking pain
I down loaded file
Un zip and put in sd card
Open M44 apk
Updatr recovery u provided
App asked to reboot in recovery. I did it and phone went in bootloop
So I have flashed s123 with pv
Click to expand...
Click to collapse
Hmmm... you dont have the chinese version. My mistake. Go to Standuk post and get that 124 ROM. ROW Version. It have TWRP by default. After that flash MIUI.
stympy said:
Hmmm... you dont have the chinese version. My mistake. Go to Standuk post and get that 124 ROM. ROW Version. It have TWRP by default. After that flash MIUI.
Click to expand...
Click to collapse
Did
Down loaded $135 and installed
Then installed miui and works fine
Thanks lot
The following is a guide for repairing failed to mount efs and dm-verify fail (drk error)
We finally did it ~~~
Warning - We will not take any responsibility for your device. Follow the steps at your own risk. If your device is Knox 0, This guide would convert it into Knox 1 due to TWRP. For solutions that does not convert to knox 1 check out payed remote solutions. Everything on your device will be reset, including efs partition. You will need backup of efs.
Test on N950F binary 4 may work on other exynos models comment below if it worked for other samsung devices.
Problem Detail -
Bootloop with samsung stock firmware boot logo.
Recovery error E:Failed to mount /efs (Invalid argument) or dm-verity verification failed...
Device cannot boot into Factory binary or Stock Rom
Actions that could cause this problem -
Flashing a non-signed efs.img by odin
Corrupt flash of efs partition.
Note - Must have efs backup for device to work (very important)
Any error that cause bootloop would show in recovery required if
Files Required
Latest Odin (recommend 3.13)
Working Stock firmware and Combination file (same binary as bootloader)
PC
Winrar or 7zip etc
Solution for efs failed bootloop-
Extract Stock firmware AP file (rename .md5 to .tar)
Rename dqmdbg.img to efs.img (or smallest image must be smaller than 8000 KB). Extract Dqmdbg.img.lz4 so it’s just “Dqmdbg.img” and then rename it to efs.img and put that one in a tar. Other option is downloading a file that’s already made this way if your bootloader is binary 4, Saves you trouble of extracting / renaming: http://www.mediafire.com/file/589wucja9rk2v8f/efs.tar/file (if you download this file just move onto number 3)
Add file new efs.img into tar archive.
Flash tar as AP file in odin + download mode
Reboot download mode
Flash Combination with odin + nand erase option on Edit: suggest you to flash stock rom first and oem unlock, don't need to wait for 7 days if imei is 0000 skip combination step
Device Should boot into Factory binary
Use IME to restore imei using *#06# (or imei 0000 in stock rom) Edit: This step is not required if efs backup is restored successful
Your device should have dm-verify failed in recovery due to drk error
Continue drk bypass for dm verify error below to continue
Solution for dm-verify error (also known as drk bypass - but temporary read note)-
Extract Stock firmware AP file
Make a copy of boot.img and delete recovery.img
Note - if files is boot.img.lz4 format change name to recovery.img.lz4
Rename boot.img copy to recovery.img
Add all the files (including other files extracted) to tar.
Flash Modded AP file with BL, CP, CSC (nand erase not required)
The phone will boot into stock firmware
Note- cannot reboot, will stuck at dm-verify error again and need to flash modded AP again.
Wait 7 days to oem unlock phone or use 7 day bypass by changing dates (not always work, keep trying, don’t reboot, worked for Samsunguser932 Edit: Imei must be 0000)
Edit: oem unlock will fix drk - if not you must follow next step
Once oem unlock flash TWRP and restore efs backup Edit: if you haven't fixed imei fix now by *#06# with combination file
Flash stock firmware once again by odin (stock, not modded)
Done - phone is back to normal
If you cannot be bothered doing by yourself you can pay https://www.facebook.com/gsm.xraxxx/ to do this.
(after he used plexihub to fix phone, i believe he is using similar method. It doesn’t seem fair to post this guide as i’ll be damaging his income but it seemed also unfair to keep this as a secret. If you want to donate to me please donate to him and his team instead at https://spacial-file.com/ or paypal [email protected] Thx)
Special Thanks to -
Samsunguser932 - testing this guide you can see his post on https://forum.xda-developers.com/galaxy-note-8/help/note-8-phone-booting-efs-restore-t3830209
Ravi Kumar - for his help in giving me clues how to fix.
Resources: (where i got most my info)
https://forum.xda-developers.com/galaxy-note-8/help/unbrick-methods-t3703767
https://forum.xda-developers.com/galaxy-note-8/help/to-fix-efs-secondary-note-8-t3785600
https://forum.xda-developers.com/galaxy-note-8/help/note-8-phone-booting-efs-restore-t3830209
http://forum.gsmhosting.com/vbb/f453/samsung-s8-g955f-2426383/
Comment below for help.
Give me a thanks if you find this guide very/extremely helpful. :angel:
Share it with those in need.
edit: not all images were able to upload
update: to skip 7 day oem unlock imei must be 0000
The best method for bypassing oem unlock for 7 days.
Requirements - clean phone with stock firmware, samsung account logged in, imei 0000
Go to setting and check for manual update. This will fail/stuck and oem unlock would appear in development settings
Reserved
hello , i have samsung j737t with bad efs ,
Recovery error E:Failed to mount /efs (Invalid argument)
any help please ,i have cert in hand
maxpatri9 said:
hello , i have samsung j737t with bad efs ,
Recovery error E:Failed to mount /efs (Invalid argument)
any help please ,i have cert in hand
Click to expand...
Click to collapse
Try the above guide. This guide isn't just designed for the note 8.
from what file i need to create efs.img for s8+ g955F?
ditternation said:
from what file i need to create efs.img for s8+ g955F?
Click to expand...
Click to collapse
You do not need an efs.img to repair efs failed to mount. It is only required for the functionality of the phone (sim). This guide would work without an efs.img, it is recommended to install a custom rom after the guide. Even though this guide can allow you phone to work, but due to drk/dm-verify errors, it is currently impossible to restore the phone to the original state.
Note - you'll need to find someone that is kind enough to share a copy/backup of their efs.img g955F. Most people think it is illegal to share as the efs.img contain imei, but with cpid devices, the imei would be overridden by your current device. Most importantly you need to change the serial number in the SVC (or else you will have the same serial number as the person sharing.
plz my problem is oem lock on, frp on and drk error. i have combination file and stock can your guide work for me?
soundn said:
plz my problem is oem lock on, frp on and drk error. i have combination file and stock can your guide work for me?
Click to expand...
Click to collapse
This would only work if you're still on binary 3. Follow the steps for DM verity fix with 7.1.1 firmware. Flash stock 7.1.1 with replaced boot.img using Odin and fix frp using adb (guides online to enable adb). Wait for 7 day OEM unlock (no method to skip do not restart). Flash twrp and use twrp to flash custom ROM or DM verify fix.
Note - this method would fix function ability of the phone only if efs is not corrupted. (If you had paid someone to fix efs, this would not work). Finally the phone will become Knox 1 and normal update functions might not work. Practically makes the phone unable to resell as a working phone.
Hello. My efs partition was erased by a z3x box. Or an octopus, I do not know. I followed your instructions. The IME combination is empty. I install a modified firmware, it works but I can not enter the Samsung account (crashing), I can not check the system updates (infinite device registration). Should I wait 7 days before the OEM unlock? Will it work?
@Alarg read post 2 to skip 7 days. Infinite device registration should make OEM unlock show with samsung account logged in. OEM unlock must be first done before installing modified firmware (suggest kernel). You must have backup of efs, a backup from another phone will not work.
bluecub1st said:
@Alarg read post 2 to skip 7 days. Infinite device registration should make OEM unlock show with samsung account logged in.
Click to expand...
Click to collapse
I can't log in Samsung account (processing failure). Imei unknown, s/n 0000000000 This method does not work for me.
@Alarg Which firmware ver are you using?
Have you tried nand flash combination file and then flash firmware (before boot, hold download mode buttons so the phone won't boot to factory mode). I do not see a reason why Samsung account would not work, try another ver maybe the version you downloaded is corrupted.
bluecub1st said:
The following is a guide for repairing failed to mount efs and dm-verify fail (drk error)
We finally did it ~~~
Warning - We will not take any responsibility for your device. Follow the steps at your own risk. If your device is Knox 0, This guide would convert it into Knox 1 due to TWRP. For solutions that does not convert to knox 1 check out payed remote solutions. Everything on your device will be reset, including efs partition. You will need backup of efs.
Test on N950F binary 4 may work on other exynos models comment below if it worked for other samsung devices.
Problem Detail -
Bootloop with samsung stock firmware boot logo.
Recovery error E:Failed to mount /efs (Invalid argument) or dm-verity verification failed...
Device cannot boot into Factory binary or Stock Rom
Actions that could cause this problem -
Flashing a non-signed efs.img by odin
Corrupt flash of efs partition.
Note - Must have efs backup for device to work (very important)
Any error that cause bootloop would show in recovery required if
Files Required
Latest Odin (recommend 3.13)
Working Stock firmware and Combination file (same binary as bootloader)
PC
Winrar or 7zip etc
Solution for efs failed bootloop-
Extract Stock firmware AP file (rename .md5 to .tar)
Rename dqmdbg.img to efs.img (or smallest image must be smaller than 8000 KB). Extract Dqmdbg.img.lz4 so it’s just “Dqmdbg.img” and then rename it to efs.img and put that one in a tar. Other option is downloading a file that’s already made this way if your bootloader is binary 4, Saves you trouble of extracting / renaming: http://www.mediafire.com/file/589wucja9rk2v8f/efs.tar/file (if you download this file just move onto number 3)
Add file new efs.img into tar archive.
Flash tar as AP file in odin + download mode
Reboot download mode
Flash Combination with odin + nand erase option on Edit: suggest you to flash stock rom first and oem unlock, don't need to wait for 7 days if imei is 0000 skip combination step
Device Should boot into Factory binary
Use IME to restore imei using *#06# (or imei 0000 in stock rom) Edit: This step is not required if efs backup is restored successful
Your device should have dm-verify failed in recovery due to drk error
Continue drk bypass for dm verify error below to continue
Solution for dm-verify error (also known as drk bypass - but temporary read note)-
Extract Stock firmware AP file
Make a copy of boot.img and delete recovery.img
Note - if files is boot.img.lz4 format change name to recovery.img.lz4
Rename boot.img copy to recovery.img
Add all the files (including other files extracted) to tar.
Flash Modded AP file with BL, CP, CSC (nand erase not required)
The phone will boot into stock firmware
Note- cannot reboot, will stuck at dm-verify error again and need to flash modded AP again.
Wait 7 days to oem unlock phone or use 7 day bypass by changing dates (not always work, keep trying, don’t reboot, worked for Samsunguser932 Edit: Imei must be 0000)
Once oem unlock flash TWRP and restore efs backup Edit: if you haven't fixed imei fix now by *#06# with combination file
Flash stock firmware once again by odin (stock, not modded)
Done - phone is back to normal
If you cannot be bothered doing by yourself you can pay https://www.facebook.com/gsm.xraxxx/ to do this.
(after he used plexihub to fix phone, i believe he is using similar method. It doesn’t seem fair to post this guide as i’ll be damaging his income but it seemed also unfair to keep this as a secret. If you want to donate to me please donate to him and his team instead at https://spacial-file.com/ or paypal [email protected] Thx)
Special Thanks to -
Samsunguser932 - testing this guide you can see his post on https://forum.xda-developers.com/galaxy-note-8/help/note-8-phone-booting-efs-restore-t3830209
Ravi Kumar - for his help in giving me clues how to fix.
Resources: (where i got most my info)
https://forum.xda-developers.com/galaxy-note-8/help/unbrick-methods-t3703767
https://forum.xda-developers.com/galaxy-note-8/help/to-fix-efs-secondary-note-8-t3785600
https://forum.xda-developers.com/galaxy-note-8/help/note-8-phone-booting-efs-restore-t3830209
http://forum.gsmhosting.com/vbb/f453/samsung-s8-g955f-2426383/
Comment below for help.
Give me a thanks if you find this guide very/extremely helpful. :angel:
Share it with those in need.
edit: not all images were able to upload
update: to skip 7 day oem unlock imei must be 0000
Click to expand...
Click to collapse
thanx! for your guide but i have this problem after taking an official OTA!
DM-Verity ERRor!
any help will be greatly appreciated!
Can someone explain me what is this EFS ?? I'm flashing roms many many times and I hadn't such problems etc
klisza1993 said:
Can someone explain me what is this EFS ?? I'm flashing roms many many times and I hadn't such problems etc
Click to expand...
Click to collapse
Just Google "EFS android"
pixel989 said:
thanx! for your guide but i have this problem after taking an official OTA!
DM-Verity ERRor!
any help will be greatly appreciated!
Click to expand...
Click to collapse
Follow
Solution for dm-verify error (also known as drk bypass - but temporary read note)-
Extract Stock firmware AP file
Make a copy of boot.img and delete recovery.img
Note - if files is boot.img.lz4 format change name to recovery.img.lz4
Rename boot.img copy to recovery.img
Add all the files (including other files extracted) to tar.
Flash Modded AP file with BL, CP, CSC (nand erase not required)
The phone will boot into stock firmware
Note- cannot reboot, will stuck at dm-verify error again and need to flash modded AP again.
Wait 7 days to oem unlock phone or use 7 day bypass by changing dates (not always work, keep trying, don’t reboot, worked for Samsunguser932 Edit: Imei must be 0000)
Once oem unlock flash TWRP and restore efs backup Edit: if you haven't fixed imei fix now by *#06# with combination file
Flash stock firmware once again by odin (stock, not modded)
Done - phone is back to normal
Click to expand...
Click to collapse
Note -
dm verify cannot be completely fixed, it can only be bypassed (in the system by flashing no dm verify).
You will need to wait for 7 days for oem unlock (there is no method to skip oem unlock)
Warranty will be voided (KNOX 1) - don't think there is a method to avoid tripping knox.
Suggest installing a custom rom after oem unlock (many reports that no dm verify on latest oreo does not work without root)
klisza1993 said:
Can someone explain me what is this EFS ?? I'm flashing roms many many times and I hadn't such problems etc
Click to expand...
Click to collapse
EFS partition is not touched when flashing roms (they actually do but in a safe way), only retards like I would try to mod efs partition.
Hi guys, will it work in my case? https://ibb.co/mJRcHK
Device is SM-N950N FRP ON and OEM ON.
What kind of solution should I follow?
@Anvar2005 - This looks like a drk verify error. Which binary are you on? frp bypass only works with binary 3. You will not find anything for frp unlock on this forum. Same steps for drk verify but use nougat.
{
"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"
}
I would like to thank TeamWin for their amazing work!
I saw that the newer Samsung MediaTek phones were not getting any sort of love, so I bought one myself to kick start the development.
I have already made TWRP for M32 & A41 and thought why not add support for a sister device.
KEEP IN MIND THIS IS A BETA BUILD, expect bugs!
TWRP is the obvious choice as it is reliable and trustworthy with frequent updates and patches.
INSTALLATION:
Odin Method (Windows):
Step 0: Unlock Device Bootloader by toggling the OEM Unlock option in Developer Options. Device will reboot to Odin mode and will prompt you to long press volume up, device will then unlock bootloader and perform a complete factory reset so make sure to backup any data.
Step 1: Download the unofficial TWRP image from the link attached below.
Step 2: Put the device in Odin download mode by holding VolumeUp+VolumeDown and inserting USB cable after the device is completely shut down.
Step 3: Select the downloaded recovery.tar in AP slot and vbmeta_disabled_R.tar in USERDATA slot, connect the device to PC, go to options and untick "Auto-Reboot"
Step 4: Click START and the Device will get flashed, Odin will say SUCESS!.
Step 5. Exit Download mode by holding VolumeDown+PowerButton and then immediately boot
into Recovery mode by pressing VolumeUp+PowerButton.
Step 6: Congratulations, you have installed TWRP latest for your F22 4G, to access the system now, you need to perform some additional steps.
Step 7: Open up TWRP terminal and then type in "multidisabler" and then perform a full factory reset again by going into "Wipe" -> Format Data -> type "yes"
Step 8: Now stock ROM should work fine with TWRP!
Heimdall Method (Linux):
Step 1: Install heimdall tool on linux , google it.
Step 2: Put the device in Odin download mode by holding VolumeUp+VolumeDown and inserting USB cable after the device is completely shut down.
Step 3: Open up terminal in the downloaded TWRP directory, extract twrp image from recovery.tar
Step 4: Enter the command "heimdall flash --RECOVERY recovery.img --no-reboot" where twrp.img is name of the downloaded image
Step 5. Exit Download mode by holding VolumeDown+PowerButton and then immediately boot
into Recovery mode by pressing VolumeUp+PowerButton.
Step 6: Congratulations, you have installed TWRP latest for your F22 4G, to access the system now, you need to perform some additional steps.
Step 7: Open up TWRP terminal and then type in "multidisabler" and then perform a full factory reset again by going into "Wipe" -> Format Data -> type "yes"
Step 8: Now stock ROM should work fine with TWRP!
COMPATIBILITY:
TWRP Recovery is compatible with latest Android 11 firmware
tested on:
E225FXXU4AVB1 by @sunmughan thank you bro.l
First time you boot into TWRP, don't forget to backup your EFS, Secondary EFS and NVRAM! Go into Backup and select "EFS,", "Secondary EFS" and "NVRAM" and backup to preferably MicroSDcard and copy it to your PC in case you need it if IMEI corrupts.
DON'T IGNORE THIS STEP!
All kernel source and device tree below!
Device Tree: TWRP Device Tree
Kernel Tree: TWRP Kernel Tree
DOWNLOADS:
VBMETA DISABLED FOR R: MEGA LINK
TWRP TAR: MEGA LINK
I am getting:
E:Unable to unlock /dev/block/mmcblk0p42 for flashing: (null)
fermi6-626 said:
I am getting:
E:Unable to unlock /dev/block/mmcblk0p42 for flashing: (null)
Click to expand...
Click to collapse
you tried with ODIN or HEIMDAL?
MrVenom. said:
you tried with ODIN or HEIMDAL?
Click to expand...
Click to collapse
i tried with both odin and heimdall
First off, the twrp itself boots. But I couldn't find "System" or "Super" in erase section. I am not sure how useful it will be if I can't erase that before flashing another image.
fermi6-626 said:
I am getting:
E:Unable to unlock /dev/block/mmcblk0p42 for flashing: (null)
Click to expand...
Click to collapse
This error is not from TWRP itself. He just didn't unmount the partitions first. That's all. I didn't get the error when I dismounted first. Without dismounting, I see 16 unable to unlock errors.
Update: Another setback, TWRP can't flash super images. Only way would have been to use fastboot which is botched by uncle sam. Any other way to flash gsi images to this?
This error is not from TWRP itself. He just didn't unmount the partitions first. That's all. I didn't get the error when I dismounted first. Without dismounting, I see 16 unable to unlock errors.
Click to expand...
Click to collapse
Actually, The errors persists even after I unmount the partitions before flashing.
The errors are there whether I mount or unmount the partitions(at least for my device), but the correct procedure is unmounting before flashing.
But I couldn't find "System" or "Super" in erase section. I am not sure how useful it will be if I can't erase that before flashing another image.
Click to expand...
Click to collapse
Beats me.
[edit: /system partition is by default always unmounted before flashing a zip]
I should have heeded the warning. I didn't backup EFS, Secondary EFS and NVRAM.
Now , there is no IMEI and cant use the sim.
Is there any solution to this?
Thank you in advance.
dekisugihidetoshi said:
I should have heeded the warning. I didn't backup EFS, Secondary EFS and NVRAM.
Now , there is no IMEI and cant use the sim.
Is there any solution to this?
Thank you in advance.
Click to expand...
Click to collapse
I am fighting myself real hard not to reply with akhils avatar, but efs (for sure) and nvram (can't say for sure) is included in the stock, flash stock, probably gonna be alright.
fermi6-626 said:
Beats me.
Click to expand...
Click to collapse
There're these packages.... DynaPatch is less known and probably not so much polished and then there's the ChonDoe_Flasher, they can be used to flash gsi and then there was a linux thingy which is used to pack system.img into super.img with vendor.img and others so that twrp can flash it directly.
Akhil99 said:
I would like to thank TeamWin for their amazing work!
I saw that the newer Samsung MediaTek phones were not getting any sort of love, so I bought one myself to kick start the development.
I have already made TWRP for M32 & A41 and thought why not add support for a sister device.
KEEP IN MIND THIS IS A BETA BUILD, expect bugs!
TWRP is the obvious choice as it is reliable and trustworthy with frequent updates and patches.
INSTALLATION:
Odin Method (Windows):
Step 0: Unlock Device Bootloader by toggling the OEM Unlock option in Developer Options. Device will reboot to Odin mode and will prompt you to long press volume up, device will then unlock bootloader and perform a complete factory reset so make sure to backup any data.
Step 1: Download the unofficial TWRP image from the link attached below.
Step 2: Put the device in Odin download mode by holding VolumeUp+VolumeDown and inserting USB cable after the device is completely shut down.
Step 3: Select the downloaded recovery.tar in AP slot and vbmeta_disabled_R.tar in USERDATA slot, connect the device to PC, go to options and untick "Auto-Reboot"
Step 4: Click START and the Device will get flashed, Odin will say SUCESS!.
Step 5. Exit Download mode by holding VolumeDown+PowerButton and then immediately boot
into Recovery mode by pressing VolumeUp+PowerButton.
Step 6: Congratulations, you have installed TWRP latest for your F22 4G, to access the system now, you need to perform some additional steps.
Step 7: Open up TWRP terminal and then type in "multidisabler" and then perform a full factory reset again by going into "Wipe" -> Format Data -> type "yes"
Step 8: Now stock ROM should work fine with TWRP!
Heimdall Method (Linux):
Step 1: Install heimdall tool on linux , google it.
Step 2: Put the device in Odin download mode by holding VolumeUp+VolumeDown and inserting USB cable after the device is completely shut down.
Step 3: Open up terminal in the downloaded TWRP directory, extract twrp image from recovery.tar
Step 4: Enter the command "heimdall flash --RECOVERY recovery.img --no-reboot" where twrp.img is name of the downloaded image
Step 5. Exit Download mode by holding VolumeDown+PowerButton and then immediately boot
into Recovery mode by pressing VolumeUp+PowerButton.
Step 6: Congratulations, you have installed TWRP latest for your F22 4G, to access the system now, you need to perform some additional steps.
Step 7: Open up TWRP terminal and then type in "multidisabler" and then perform a full factory reset again by going into "Wipe" -> Format Data -> type "yes"
Step 8: Now stock ROM should work fine with TWRP!
COMPATIBILITY:
TWRP Recovery is compatible with latest Android 11 firmware
tested on:
E225FXXU4AVB1 by @sunmughan thank you bro.l
First time you boot into TWRP, don't forget to backup your EFS, Secondary EFS and NVRAM! Go into Backup and select "EFS,", "Secondary EFS" and "NVRAM" and backup to preferably MicroSDcard and copy it to your PC in case you need it if IMEI corrupts.
DON'T IGNORE THIS STEP!
All kernel source and device tree below!
Device Tree: TWRP Device Tree
Kernel Tree: TWRP Kernel Tree
DOWNLOADS:
VBMETA DISABLED FOR R: MEGA LINK
TWRP TAR: MEGA LINK
Click to expand...
Click to collapse
hello brother, this unofficial twrp tar cause me bootloop pls can you fix this. on my samsung f22 android 12 E225FXXU4BVF1
fermi6-626 said:
I am getting:
E:Unable to unlock /dev/block/mmcblk0p42 for flashing: (null)
Click to expand...
Click to collapse
Just ignore those errors.
Hello there! Is there any files that I could directly use to flash twrp? I already am root through magisk and didn't find the supported module/device of twrp which I downloaded from play store. Still no support for F22. So how do I install it? Without any desktop or pc. directly through my rooted phone? Thanks!
I haven't tried it yet, but in theory, shouldn't it work with android S & T if the appropriate vbmeta is flashed?
There is a new binary update, u5. Downgrading won't be possible and this device has only this twrp for it, to my knowledge.
dekisugihidetoshi said:
I should have heeded the warning. I didn't backup EFS, Secondary EFS and NVRAM.
Now , there is no IMEI and cant use the sim.
Is there any solution to this?
Thank you in advance.
Click to expand...
Click to collapse
Does this error got solved or not because i want to try custom rom in my samsung f22 please help me
I Flashed using SP Tool and i don't have backup of the partition.
i want the file so i can edit it and paste my imei.
NVDATA, NVRAM and nvcfg
mine boots to recovery and it says NVDATA corrupt.
PLZ HELP!
where to find it?
xn0live said:
where to find it?
Click to expand...
Click to collapse
It's a system partition.
Backup using SP Flash Tool V6 (from Mi Flash Pro Tool) by using Read Back and using mtkmeta utility for bypassing authentication file.
Install Microsoft visual C++ 2015 - 2022 Redistributable for SP Flash tool V6 to work.. RESTART PC AFTERWARDS
Install the libusb-win32.....driver and install the filter after setup by using your phone in BROM ( when power off, press and hold volume up and down together and connect USB to PC, Then you will see your phone detected on Filter installer wizard and select it and click install quickly as possible (within 3 seconds). other wise the phone is going to disconnect and boot back.
You also need to download the firmware and load the scatter file in to the SP Flash tool and Bypass authentication using MTKMETA Utility and go to read back to back up these Partitions in Img or bin format. USE Youtube for this purpose.
no sry to complicate
xn0live said:
no sry to complicate
Click to expand...
Click to collapse
It's ok
These are the partition of Poco M4 Pro 4G after losing IMEI and restoring it using DFT Pro. I formatted the phone afterwards and the IMEI was not permanent and it showed NVDATA corrupted and was not able to boot. These was the partition before getting the error. I did restore the partition and it showed the same error. Hope someone find it useful.... Use MI Flash Pro > SP flash tool V6 to restore.