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
Hello all,
I'm so dessapointed, i brick my tablet when i want resize but i cant flash with the official firmware (official site " 51cube.com" and "cube-tablet" if you can help me ='(.
Perhaps the firmware is wrong or my manip is wrong, i don't know.
Thx for you help.
Ps : I'm french =)
nofansub said:
Hello all,
I'm so dessapointed, i brick my tablet when i want resize but i cant flash with the official firmware (official site " 51cube.com" and "cube-tablet" if you can help me ='(.
Perhaps the firmware is wrong or my manip is wrong, i don't know.
Thx for you help.
Ps : I'm french =)
Click to expand...
Click to collapse
Hello,
My tablets is good, i flash with the firmware on the site :
h**p://chinagadgetsreviews.com
the link for help.
h**p://chinagadgetsreviews.blogspot.ro/2015/12/download-latest-android-lollipop-51_0.html
Bye
How to?
nofansub said:
Hello,
My tablets is good, i flash with the firmware on the site :
h**p://chinagadgetsreviews.com
the link for help.
h**p://chinagadgetsreviews.blogspot.ro/2015/12/download-latest-android-lollipop-51_0.html
Bye
Click to expand...
Click to collapse
Please can you explain how to use that firmware?
I think it's a recovery firmware for going back to factory defaults when s**t happens.
But I read on some forums that I should backup my IMEI and NVRAM (with MTKDroidTools or something like that...i don't know if there's a specific tool for the Cube T8 Plus) BEFORE trying custom roms, otherwise there will be problems even on restoring stock firmware, right?
Can somebody please make a short-how-to for dummies focalized on this Cube T8 Plus (so poor and confused support on forums yet)?
- Backup before custom rom installation
- Custom rom installation
- Recover to stock firmware
Another question: why that page you linked says "Platform: Mediatek MT6753"
Isn't MT8783?
Thank you very much
my tablet is not bricked now but my serial number and my mac adress is wrong ='(
Use sp tool for save your firmware tablet ( i think).
I have the same problem, after the resizing of partition the tablet is soft bricked and I'm downloading the stock firmware form the above link.
Is there any way to backup the mac address and serial number from softbricked tablet?
...you should have a backup of nvram!
Morgan766 said:
I have the same problem, after the resizing of partition the tablet is soft bricked and I'm downloading the stock firmware form the above link.
Is there any way to backup the mac address and serial number from softbricked tablet?
Click to expand...
Click to collapse
I think it's too late.
I did a backup of nvram with SP Flash Tools BEFORE brick.
When i recovered the tablet after brick, my IMEI was invalid until i flashed my backup of nvram.
Anyone could suggest how and what to backup before trying Root and Resize?
Just backup nvram with sp flash tool
bolija said:
Anyone could suggest how and what to backup before trying Root and Resize?
Click to expand...
Click to collapse
The only unrecoverable partition (for mediatek devices like T8 Plus) is the nvram which contains info about IMEI.
Firmwares/ROMS that we can download from the web never comes with nvram because it's single product related. It's like mac address of wifi cards.
You can find even stock (original) firmwares online, they will bring your tablet back to factory default after a brick.
But if the brick corrupted the nvram, you will NEVER be able to recover it. That means no phone calls and no data connection.
Unless you did a backup of nvram before its corruption.
With SP flash tool you can "read back" from your T8 plus the nvram partition and save it as a file on your pc (file size must be 5MB). Of course you need drivers, SP flash tool and the scatter file. Since i wasn't able to retrieve the scatter file from my T8 plus, I used the scatter included in the stock firmware T8-PLUS_V1.0_20151004.
I am new forum user so I can't post links, but google is enough.
That stock firmware is hosted by baidu, so use browser translation and register an account to get permissions for download.
Remember: in the firmware archive you only need the scatter file! It will tell to SP flash tool where the nvram partition starts and where it ends.
If you will need to restore nvram (e.g. after the unbrick) ,you will have to download to your T8 plus that nvram file with SP flash tool, but before you have to edit the scatter file and set "is_download=true" in the nvram section. Otherwise you will not be able to select nvram in the partitions list from the download tab of SP flash tool.
So the backup will consist in two files:
- nvram file (5MB) (nvram, nvram.img, nvram.bin, extension doesn't matter)
- scatter file with edited "is_download=true" for nvram section
Thanks so much for your help. I think i will be able to backup NVRAM. But im kind of lost on scatter file editing and flash.
Im waiting for Tablet ti arrive
This is for real, folks. The first working custom recovery for Asus ZenPad 8.0 Z380M and a method to flash it under a locked bootloader. This took quite a bit of work to make, partly due to having to find a way to bypass the locked bootloader. And because of a kernel configuration issue that limited the size of the initial ramdisk, which took some serious effort to weed out. @lss1977 helped to port it to this device. And of course, credits to TeamWin for TWRP.
In addition to this thread, the current Z300M/Z301M TWRP thread and the the old Z300M recovery/rooting thread may be helpful. These models share the same hardware and software base, so most things that apply to one tablet also apply to the other.
DISCLAIMER
As usual, you do anything described in this post at your own risk. No one but you is responsible for any data loss, bricking or damage of your device.
REQUIREMENTS
Windows PC
SP Flash Tool version 5.1532 (only this version will bypass security checks)*
MediaTek VCOM drivers (available through Windows Update)
Z380M scatter file, attached
Recovery image, attached
Z380M preloader file (optional), available inside the stock firmware download
ZenPad Z380M tablet upgraded to Android N
* If you prefer to use a more recent SP Flash Tool, check out the special image file below.
This won't be a guide on how to use SP Flash Tool. There are plenty of good guides out there like this one on how to set up drivers, load scatter files, flash and make backups with SP Flash Tool. If you're not familiar with this software or how to flash MediaTek devices in general, please do your research before attempting this. I will just get straight to the specifics about the ZenPad 8.
FIRST TIME INSTALLATION
For a locked bootloader:
At this point you should have your tablet powered off, the drivers installed, all of your data backed up, and SP Flash Tool v5.1532's Download tab open and loaded with the tablet's scatter file. Open the download agent file DA_PL.bin, replacing the default MTK_AllInOne_DA.bin. (You can use the AllInOne DA if you want, but the procedure involves extra steps as described below.) Load the extracted TWRP recovery image (twrp-3.2.1-0-z380m.img) under the recovery partition line in the partition table. Click the Download button inside SPFT. Now just connect the USB cable to your tablet and your computer's USB port. It should start the download process automatically and disconnect when finished.
Alternative Method:
If you're using MTK_AllInOne_DA.bin, you have to hold the Volume Up key as you insert the cable, which puts the device into an emergency download mode. In addition, you will need to have the stock preloader*.bin file loaded inside SPFT for it to be able to communicate with your tablet. The preloader is available inside the official zip file download. Do not flash the preloader (untick the box) or any partitions other than recovery. You just need to have a valid bin file selected under the Preloader line.
For an unlocked bootloader:
If you have used the Asus unlock tool to unlock your device, you will still not be able to use fastboot flash to install a custom recovery. However, you can do a "hot boot" or a tethered boot of TWRP. This method doesn't require SP Flash Tool. Download the TWRP image, put your tablet in fastboot mode and connect to PC. Then run this command to boot TWRP dynamically:
fastboot boot twrp-3.2.1-0-z380m.img
Once inside TWRP, flash twrp-3.2.1-0-z380m.img to Recovery using Install -> Install Image. Then reboot to recovery. You may be able to use TWRP in the tethered boot mode, but that could result in glitches due to different parameters passed by the bootloader to the kernel. That's why flashing is recommended.
To update from your installed TWRP version to a new one, just transfer the image to your tablet, then boot to TWRP and install it by going to Install -> Install Image and flashing to Recovery.
START RECOVERY
With the tablet powered off, hold the Volume Up and Power keys together until you get to a menu where you can select "recovery". Use Vol. Up to scroll and Vol. Dn to select. If you have a locked bootloader, it will show a Yellow State message because the recovery is not signed by the OEM. Just press volume up to boot it. On the welcome screen of TWRP it will ask you about modifying the system partition, I suggest you go with Keep System Read-only. Doing otherwise will complicate your OTA updates.
WARNING: Never start the stock recovery from the bootloader menu on this device. It is programmed by the bootloader to instantly wipe your data without any warning. Also, be aware that Android installs the stock recovery at every normal boot cycle. So you either have to flash the TWRP every time you want to run it, or disable the automatic recovery installation in the stock firmware. Any kind of mod to the boot image will prevent the automatic recovery installation. If you're not sure which recovery you have installed, you can always do a 'adb reboot recovery' from Android without risk of data loss.
What works: Basically everything... access to major partitions, decrypted userdata partition, decrypted adoptable storage, external SD card, ADB, USB-OTG, touch interface, splash screen, installing stock Asus OTA/web FW updates
What doesn't work: (no known problems yet, but please report any)
Not guaranteed to work: factory reset
DOWNLOAD
(Updated February 3, 2018: updated kernel to firmware 5.3.18; up-to-date TWRP 3.2.1 sources)
SP Flash Tool v5.1532
Z380M Scatter file for all storage sizes (right click, Save link as...)
Recovery image
Signed image for Flash Tool only -- may be flashed with recent SP Flash Tool versions -- DO NOT INSTALL USING ANY OTHER METHOD -- tested with SPFT 5.1736.
Development and experimental files
Source code
P.S. The thanks button doesn't bite.
Nice one now lets get some custom roms done.
Has anyone installed this yet? I see the file has been downloaded a few times. Any feedback is welcome.
If you want the recovery to stick after reboot either rename or remove system/bin/install_recovery.sh.
lss1977 said:
If you want the recovery to stick after reboot either rename or remove system/bin/install_recovery.sh.
Click to expand...
Click to collapse
The way I did it was to edit the init.rc file inside the boot ramdisk and comment out the service block that calls install_recovery.sh. I used the MTK boot image unpack/repack tools. I don't know, it seems like changing anything on the system partition will break OTA updates because of dm-verity. Because that depends on verifying each block of the file system. I have never even mounted the system as R/W in recovery.
how to create scater file from text posted? I copied all text to MT8163_Android_scatter.txt file but when open with splash tools give error "scatter file is invalid"
please atach your working scatter file to other atachments
PxYra said:
how to create scater file from text posted? I copied all text to MT8163_Android_scatter.txt file but when open with splash tools give error "scatter file is invalid"
please atach your working scatter file to other atachments
Click to expand...
Click to collapse
OK, I added the scatter file as a download. It was a pain in the ass to copy & paste. (But it did work.)
Problem fixed downloaded new version of flashtool 5.16 and scatter working
Ok I installed TWRP on Z380M P00A, and wanna say to other
1. Use VCOM drivers only from splash tool official site
2. To install VCOM drivers first need enter chinese recovery tablet, then in windows device manager you see USB device, install manualy drivers (don forget in windows disable driver signature)
3. Use only SP-Flash-Tool-v5.1532.00, newer or older version not properly working with this phone
Ok, thanks for the update, PxYra. Just to let you know, there are signed versions of VCOM drivers floating around so you don't need to mess with signature enforcement. Here's one: https://www.androidfilehost.com/?fid=24591000424943663. They are also updated by Windows so you can just let Windows Update install them.
Thanks for your work.
Flashing procedure works only with "MTK_AllInOne_DA.bin" method for me. But this is OK!
(Updated May 6, 2017: added kernel from firmware 5.3.7, source code cleanup)
Click to expand...
Click to collapse
is it possible to get the older versions? I need Android 6.x, because of xposed-Framework for my Zenpad 8.0 Z380M.
Greets Freisei
Hey freisei...
I never posted a version for Android 6. There was just one based on the 5.3.6 kernel, practically the same as the current one. That's why I didn't keep it. I could try to build one for you if you want, but I can't test it of course. Does this recovery not boot at all on the old firmware?
It's strange that the DA_PL.bin method didn't work for you. What happened when you tried it? I suppose the old preloader doesn't allow it(?).
hello guys, you think lineage os official version for asus z380kl (p024) will work on our z380m ?
---------- Post added at 08:19 PM ---------- Previous post was at 08:05 PM ----------
Can anyone help me? after selecting recovery img, pressing download and inserting usb cable, nothing happens. Thanks in advance
lss1977 said:
If you want the recovery to stick after reboot either rename or remove system/bin/install_recovery.sh.
Click to expand...
Click to collapse
hello friend, can you please upload that file? I deleted it, but now I need it to revert to official recovery, as my zenpad is bricked! It would be of great help! thanks!
Pires_7 said:
hello friend, can you please upload that file? I deleted it, but now I need it to revert to official recovery, as my zenpad is bricked! It would be of great help! thanks!
Click to expand...
Click to collapse
Your ZenPad didn't brick because you deleted install_recovery.sh. It's because you modified the system partition. Making any mods to system is bad advice unless you know exactly what you're doing. Even mounting it in r/w mode can break it. That's because dm-verity has tripped and is blocking access to changed blocks of the file system. So you have 3 options: mod your boot image fstab file to disable dm-verity, restore the original system image block-for-block (either from backup or official firmware converted to an img file), or wipe userdata (lss reported that to work).
Pires_7 said:
hello guys, you think lineage os official version for asus z380kl (p024) will work on our z380m ?
Click to expand...
Click to collapse
Nope, no chance.
diplomatic said:
Your ZenPad didn't brick because you deleted install_recovery.sh. It's because you modified the system partition. Making any mods to system is bad advice unless you know exactly what you're doing. Even mounting it in r/w mode can break it. That's because dm-verity has tripped and is blocking access to changed blocks of the file system. So you have 3 options: mod your boot image fstab file to disable dm-verity, restore the original system image block-for-block (either from backup or official firmware converted to an img file), or wipe userdata (lss reported that to work).
Nope, no chance.
Click to expand...
Click to collapse
Ok. I made some real s*it, I think I deleted every partition except recovery. Can you provide me a twrp backup or some way around my problem?
What do you mean you deleted every partition except recovery? There's like 28 partitions. You would have to work hard to accomplish that.
My first suggestion is to extract a system.img from the Asus stock firmware zip using this. Then flash it with SP Flash Tool. You might also try to install a full firmware zip from TWRP. Although I have no idea if that will work or if it's even safe to try.
diplomatic said:
What do you mean you deleted every partition except recovery? There's like 28 partitions. You would have to work hard to accomplish that.
My first suggestion is to extract a system.img from the Asus stock firmware zip using this. Then flash it with SP Flash Tool. You might also try to install a full firmware zip from TWRP. Although I have no idea if that will work or if it's even safe to try.
Click to expand...
Click to collapse
i was able to extract system.new.dat from stock firmware zip, but it extracts to a system folder. How do I flash this through sp flash tool?
OK, the system folder you don't need. It should have produced a system.img file also. That's the file you need to flash. Just select it for the system partition row in the partition list and then Download. Hopefully that will be enough.
EDIT: I just looked at the script, and realized the system.img.img file gets deleted in the process. So what you need to do is start the extraction, then after it makes system.img.img, when it starts extracting individual files, hit Ctrl+C. Then you'll end up with the img file.
Thank you very much! it works! YOU are the BEST!
please tell me, in your scatter file, address partition_name: frp (0x80a5000) is correct? if i format this partition (frp), google account remove?
i downloaded the custom recovery for t20 (TWRP-3.2.3-TwrpBuilder-t20-2019-01-18_20-02) from gethub "i cant attach the link because of the forums rules"
then flashed it using fastboot , but then the tablet didn't boot into normal mode but i was getting the boot mode selection when i hold the (power + volume up) which gave me access to recovery mode and fastboot mode
the problem is that this custom recovery had issues with the touch screen and was basically not usable .
so i switched the phone into fastboot and i flashed the patched boot image that was working before but the tablet still didn't boot into normal mode , then i flashed the stock recovery image and now every thing gone .
the tablet has no options to boot into fastboot or recovery anymore.
basically the tablets boots and i get the teclast logo then the image of the broken android with a "no command" on screen and nothing else
i tried holding the volume up and plug in the usb-c cable but i got the same broken droid
holding volume up and power doesn't give the options for boot modes anymore
i would appreciate any help a this moment , thanks
hany20006 said:
i would appreciate any help a this moment , thanks
Click to expand...
Click to collapse
SP Flash tool should help you. Install stock firmware and everything should be restored, a device on MTK isn't so easy to kill. Just check the revision of your device (E1 or E2, on the back cover). I tried this TWRP and already spoke of that control it only with mouse (https://forum.xda-developers.com/showpost.php?p=78710093&postcount=5). I have my own version of the TWRP (3.2.2), there's also a problem with orientation of the screen. But PhilZ recovery works without problems, the management of keys.
ViAlexSt said:
SP Flash tool should help you. Install stock firmware and everything should be restored, a device on MTK isn't so easy to kill. Just check the revision of your device (E1 or E2, on the back cover). I tried this TWRP and already spoke of that control it only with mouse (https://forum.xda-developers.com/showpost.php?p=78710093&postcount=5). I have my own version of the TWRP (3.2.2), there's also a problem with orientation of the screen. But PhilZ recovery works without problems, the management of keys.
Click to expand...
Click to collapse
thanks for the reply my version is E2
i tried flashing the stock but i keep getting an error that the preloader file is not valid . can u upload yours so i can try with it
hany20006 said:
my version is E2
Click to expand...
Click to collapse
Here's firmware T20 (T2E2)-Android7.1.1_V1.02_8F48 specifically for revision E2: Chinese storage or my Y.Disk
If stock firmware doesn't help you, here's my read preload-partition, I have E2 (I hope you know how to restore it in SP Flash Tool using Write Memory option).
Partition address and size:
Code:
linear_start_addr: 0x0
physical_start_addr: 0x0
partition_size: 0x40000
ViAlexSt said:
Here's firmware T20 (T2E2)-Android7.1.1_V1.02_8F48 specifically for revision E2:
If stock firmware doesn't help you, here's my read preload-partition, I have E2 (I hope you know how to restore it in SP Flash Tool using Write Memory option).
Partition address and size:
Code:
linear_start_addr: 0x0
physical_start_addr: 0x0
partition_size: 0x40000
Click to expand...
Click to collapse
thank you very much for providing the y.disk link , i spent the whole yesterday searching for a way to download from baidu without luck.
i managed to flash the stock software (using format all +download) and it worked and now the tablet is up and running (unfortunately its chines ) i changed the language but there is bits here and there with chines still i cant complain.
there is no recovery image with this tablet , do u think i should flash the twrp recovery even if it has touch issues.
i cant thank u enough for your help
have a nice day
hany20006 said:
do u think i should flash the twrp recovery even if it has touch issues
Click to expand...
Click to collapse
See here: https://forum.xda-developers.com/showpost.php?p=78758523&postcount=7
ViAlexSt said:
See here: https://forum.xda-developers.com/showpost.php?p=78758523&postcount=7
Click to expand...
Click to collapse
yeah i just rooted the device and then flashed the recovery using the Mediatek (MTK) Auto TWRP recovery porter by Team Hovatek (TWRP 3.2.1-0)
the touch screen is till having issues , but i guess i have to use mouse as you said
Hey guys, have either of you had trouble using the flash tool to flash the patched boot image from Magisk? it will not flash no matter what I do. I just get a red bar .... THanks
Draiter said:
Hey guys, have either of you had trouble using the flash tool to flash the patched boot image from Magisk? it will not flash no matter what I do. I just get a red bar .... THanks
Click to expand...
Click to collapse
Those are the notes i made for my self regarding your issue:
at the end we may get an error when flashing the patched-boot.img using sp flash tool
so we need to use fastboot instead
first we need to install ADB and fastboot in the PC (follow link bellow):
https://www.howtogeek.com/239798/how-to-unlock-your-android-phones-bootloader-the-official-way/
then power off the device then (hold the volume up+ power ) to enter the BOOT mode (the usb must be disconnected)
then select the fastboot from the menu
then we can use the commands :
#fastboot flash boot c:/patched_boot.img --> make sure the image is in the C folder
if this failed we need to unlock the OEM
#fastboot oem unlock -- > then confirm from the tablet
then try again
#fastboot flash boot C:/patched_boot.img
and when its done we can issue the command for restarting tablet
#fastboot reboot
hany20006 said:
Those are the notes i made for my self regarding your issue:
at the end we may get an error when flashing the patched-boot.img using sp flash tool
so we need to use fastboot instead
first we need to install ADB and fastboot in the PC (follow link bellow):
https://www.howtogeek.com/239798/how-to-unlock-your-android-phones-bootloader-the-official-way/
then power off the device then (hold the volume up+ power ) to enter the BOOT mode (the usb must be disconnected)
then select the fastboot from the menu
then we can use the commands :
#fastboot flash boot c:/patched_boot.img --> make sure the image is in the C folder
if this failed we need to unlock the OEM
#fastboot oem unlock -- > then confirm from the tablet
then try again
#fastboot flash boot C:/patched_boot.img
and when its done we can issue the command for restarting tablet
#fastboot reboot
Click to expand...
Click to collapse
Hey thanks for the quick reply, I will give it a go
Sent from my SM-G935F using Tapatalk
Got the boot.img flashed and recovery flashed (Phil's), but cannot do a full backup in recovery, cannot Mount data.
Have you been able to do a full backup?
Sent from my SM-G935F using Tapatalk
Draiter said:
cannot Mount data
Click to expand...
Click to collapse
Standard phenomenon for Nougat/Oreo: to mount a partition /date, must first format it. With loss of user data!
Some TWRP editions don't require this, /data mounted.
Hello.
Thanks ViAlexSt for the help, but I´m still having problems with root
, I try with (MTK) Auto TWRP recovery porter and with MTK Auto Philz recovery porter, with success only with TWRP.
Wiith Philz only get into recovery, when go to the OS the screen freeze with Teclast Logo in red.
With TRWP have an error, not able to mound device.
Is no possible install zip or create a backup.
Any idea??
I have a T20 T2E1
Thanks
I format with SPFlashtool with format+flash option, but not work, no backup, no any wipe.
Still with message Unable to mount parition.
I will try with an older version OF TWRP.
Some screenshots.
Thanks
https://photos.app.goo.gl/qwmLqnhxVk8vRmWA8
https://photos.app.goo.gl/VP5vJCDC7HaDpgaB8
AWLanzarote said:
Still with message Unable to mount parition.
Click to expand...
Click to collapse
Did you manage to do it? It's necessary to format the partition from CWM/TWRP!
Do you need additional explanations?
ViAlexSt said:
Did you manage to do it? It's necessary to format the partition from CWM/TWRP!
Do you need additional explanations?
Click to expand...
Click to collapse
Thank you very much for yor reply.
Yes I try formating with twrp but the same problem, at the end I take the risk and use a downloanble image "TWRP-3.2.3-TwrpBuilder-t20-2019-01-18_20-02". The one generated with the porter doesn´t work for my Teclast T20 (T2E1).
With this one "TWRP-3.2.3-TwrpBuilder-t20-2019-01-18_20-02.img works at the first".
And after that I was able to install "Magisk-v18.0.zip" and "no-verity-opt-encrypt-6.0.zip".
And finally I get root access, but after a wile I see the propblem with the IMEI wich was Inavild, after try with many options like generate the file MP0B_001, use Uncletools, droid tools, and many other Apps.
Finally today... I found a solution in a Spanisf Forum Dual Sim, Thanks to user "pedrogem" the most easy way to set an IMEI.
https://play.google.com/store/apps/details?id=com.rungetel.ghostphone&showAllReviews=true
Many Thanks..
AWLanzarote said:
Thank you very much for yor reply.
Yes I try formating with twrp but the same problem, at the end I take the risk and use a downloanble image "TWRP-3.2.3-TwrpBuilder-t20-2019-01-18_20-02". The one generated with the porter doesn´t work for my Teclast T20 (T2E1).
With this one "TWRP-3.2.3-TwrpBuilder-t20-2019-01-18_20-02.img works at the first".
And after that I was able to install "Magisk-v18.0.zip" and "no-verity-opt-encrypt-6.0.zip".
And finally I get root access, but after a wile I see the propblem with the IMEI wich was Inavild, after try with many options like generate the file MP0B_001, use Uncletools, droid tools, and many other Apps.
Finally today... I found a solution in a Spanisf Forum Dual Sim, Thanks to user "pedrogem" the most easy way to set an IMEI.
https://play.google.com/store/apps/details?id=com.rungetel.ghostphone&showAllReviews=true
Many Thanks..
Click to expand...
Click to collapse
Are you able to make a T20 root step by step guide with all the necessary download's (patched boot.img included) ?
would be very appreciate.
regards
toxstoxs said:
Are you able to make a T20 root step by step guide with all the necessary download's (patched boot.img included) ?
would be very appreciate.
regards
Click to expand...
Click to collapse
Hi toxstoxs.
Is already done in this link with all the downloads https://romprovider.com/2019/01/teclast-t20-root-twrp/.
I follow these steps exept the use of adb. In stead, I used SP Flash Tool, the utility included in the the original ROM which you can download from the official Teclast website.
Be sure to make the backups mentioned in the procedure NVRAM and nandroid, in case you lose your IMEI you will need restore the NVRAM backup.
With SP flash tools, upload the recovry.img "the downloaded TWRP from the link above" and your boot.img "patched on your device with magisk manager from you original"
I use the boot image from the original rom downloaded from Teclast, which I flash previously.
Be sure to make the backups mentioned in the procedure NVRAM and nandroid, in case you lose your IMEI you will need restore the NVRAM backup.
Just take in mind... touch screeen is not working well in TWRP you should use a mouse, the touch screen is in portrait possition but wou will see the screen in landscape, I do it without a mouse but is not easy, if you can get a mouse will be bether.
Regards.
AWLanzarote said:
Hi toxstoxs.
Is already done in this link with all the downloads https://romprovider.com/2019/01/teclast-t20-root-twrp/.
I follow these steps exept the use of adb. In stead, I used SP Flash Tool, the utility included in the the original ROM which you can download from the official Teclast website.
Be sure to make the backups mentioned in the procedure NVRAM and nandroid, in case you lose your IMEI you will need restore the NVRAM backup.
With SP flash tools, upload the recovry.img "the downloaded TWRP from the link above" and your boot.img "patched on your device with magisk manager from you original"
I use the boot image from the original rom downloaded from Teclast, which I flash previously.
Be sure to make the backups mentioned in the procedure NVRAM and nandroid, in case you lose your IMEI you will need restore the NVRAM backup.
Just take in mind... touch screeen is not working well in TWRP you should use a mouse, the touch screen is in portrait possition but wou will see the screen in landscape, I do it without a mouse but is not easy, if you can get a mouse will be bether.
Regards.
Click to expand...
Click to collapse
I went troght that step by step guide but :
1) into Pre requirement steps, i made a NVRAM backup with SP Tool.
step 2 is not so interesting to me as the tablet is new so no personal data are saved.
point 3 : How suppose to make a nandroid backup if no TWRP is intalled???
then.. i suppose that it mean to INSTALL a TWRP and just after make a nandroid backup right?
but...
just after ulock the bootloader and reaching step by step the point 7 and 8 of the guide,
after the command "fastboot boot recovery.img" the device reboot and go in permanent loop.
No way to access the recovery.
is there something that i may check? just once i been able to enter the twrp and the main problem were the impossibilty to access and format the /data partition so, no factory reset were possible and obviously no bbot as well (permanent boot loop).
Im not use adb tools, im only use sp fash tool.
I do it like this.
1 flash the downloaded Rom from Teclast with SP flash tool, to get all fresh.
2 Enable usb debug and oem unlock
3 copy in your device the stock boot.img from the folder firmware from the zip downloaded from Teclast,
4 in your device install the app Majisk manager and use it to patch your original boot.img
5 copy into sd the files magisk.zip, No verity opt encrypt.zip,
6 with sp flash tool flash the patched boot.img and the downloaded TWRP-3.2.3-TwrpBuilder-2019-01-18_20-02"]twrp renamed to recovery.img ”this was the only one trwp which works on my T20”https://github.com/TwrpBuilderTests/android_device_teclast_t20/releases/tag/TWRP-3.2.3-TwrpBuilder-2019-01-18_20-02
7 reboot in recovery with TWRP and install magisk.zip and no verity opt encrypt.zip
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?)