Related
Ulefone power 2 Development and Support-
Basic Device Details-
Display- 5.5 inch
OS- android 7.0 Nougat
Chipset - MT6757T
RAM- 4GB
Disclaimer-
Code:
i am not Responsible for any damage to Your Device..
official Firmware-
https://drive.google.com/drive/folders/0B8NC4kBpjQhYV1lWOEtYWThRRms
twrp Recovery-
https://drive.google.com/open?id=0B1aXJDZjE8bvM0h0aTVEOEdBS1U
SP Flash tools and Driver-
https://drive.google.com/folderview?id=0B6O3B5Tc7Wr9ZzgxQmcyNmNoX00
Magisk-
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
No verity opt-Encrypt-
https://www.androidfilehost.com/?fid=673368273298927206
extras-
Greenify for Battery-
http://m.hiapphere.com/apk-com.oasisfeng.greenify
Build.prop tweaks-
[Must Backup official before try-
https://forum.xda-developers.com/attachment.php?attachmentid=4248841&stc=1&d=1503381757
Guide-
Flash Firmware-
1. Install Vcom Driver Run SP flash tools, Load Scatter File , Check Everything and then click Download, as soon as connect your Switched off Phone.
Flash twrp-
Code:
fastboot oem unlock
fastboot flash recovery recovery.img
or use inbuild script
if you have Scatter then you can Flash with SP flash tools.
Root-
flash Magisk via twrp or you can also use Supersu 2.78XX.
Mod-
Will be added Soon....:good:
version- 3.00XX
Credit- XN Logos
Donation- https://Paypal.me/droiddeveloper
Please Don't create mirror Without the Link of This Page.
I tried it but it didn't work. twrp is installed but my phone doesn't boot into the system anymore. When I reboot it goes back to Twrp and then the touchscreen doesn't work anymore. I have to connect an USB-mouse. But it still doesn't boot.
When I try to flash or wipe sth it says "unable to mount"
I had to flash the original software again with SP Flash Tools
No flash No verity encrypt to Disable boot verification
XN Logos said:
No flash No verity encrypt to Disable boot verification
Click to expand...
Click to collapse
sorry but what does that mean?
So i used your TWRP Recovery, normally it should work and it does but why is my data shown as 0.
Thank you too. Please help
where is the scatter file?
gasperoni said:
where is the scatter file?
Click to expand...
Click to collapse
no Scatter included use Fastboot, or You can take scatter from ROM.
Ok but where is the recovery image file to flash via SP Flash Tools? I only see an exe-file saying "flash recovery" and a 12.6MB file called "rk" but it's shown me as a mp4-file
it worked!!! Thank yoU!! @gasperoni, just start "Flash Recovery.exe" and do what is written in the window. It's really easy.
i have include a Script which have ability to unlock bootloader and then flash twrp, if you flash with SP flash tool your Device not bootup because bootloader is Loacked. so Simply use Given Instruction Not SP flash.
any custom ROM
non yet
hm..i install twrp with your "flash recovery.exe", my phone reboots, i have to press "volume up" to unlock my bootloader. then trwp starts.
until here everything works fine. But when i am installing Superuser and restart my phone, it writes sth like "orange mode, your phone is untrusted" and just boots into twrp, touchscreen isnt working. So i have to flash it again, but i didnt achieve twrp of course :S
Unlucky25 said:
hm..i install twrp with your "flash recovery.exe", my phone reboots, i have to press "volume up" to unlock my bootloader. then trwp starts.
until here everything works fine. But when i am installing Superuser and restart my phone, it writes sth like "orange mode, your phone is untrusted" and just boots into twrp, touchscreen isnt working. So i have to flash it again, but i didnt achieve twrp of course :S
Click to expand...
Click to collapse
Same issue for me.
I tried twice to install the recovery with the .exe file. Both times I bricked the phone. Why?
kylebutler said:
Same issue for me.
I tried twice to install the recovery with the .exe file. Both times I bricked the phone. Why?
Click to expand...
Click to collapse
Same result here. But how did you get the factory rom to flash on the phone? I first got some checksum error and had to find a checksum generator and now the silly multiport flash software says:
" Warning maybe error as follows: 1 com port number repetitive or invalid 2 brom and preloader have the same comport number! Please modify them in INI file or scan again."
I think i did everything correctly (installed the drivers and stuff as it says on the ulefone download page) but i haven't flashed any mediatek devices in a long time and i would be very thankful if someone can tell me what i'm doing wrong. I don't mind it getting bricked as i know that is always a risk with mediatek, but i do need to be able to flash the stock rom.
ml11ML said:
Same result here. But how did you get the factory rom to flash on the phone? I first got some checksum error and had to find a checksum generator and now the silly multiport flash softwhttps://forum.xda-developers.com/usercp.phpare says:
" Warning maybe error as follows: 1 com port number repetitive or invalid 2 brom and preloader have the same comport number! Please modify them in INI file or scan again."
I think i did everything correctly (installed the drivers and stuff as it says on the ulefone download page) but i haven't flashed any mediatek devices in a long time and i would be very thankful if someone can tell me what i'm doing wrong. I don't mind it getting bricked as i know that is always a risk with mediatek, but i do need to be able to flash the stock rom.
Click to expand...
Click to collapse
I had also issues using the flash tool provided on the Ulefone website, the same as you say (with the checksum). None of checksum-generating software worked for me, so I was searching long for an alternative and found this flash tool: https://spflashtool.com/. Using this tool, flashing worked for me perfectly even without having to bother with checksums.
Good luck!
pavelmracek said:
I had also issues using the flash tool provided on the Ulefone website, the same as you say (with the checksum). None of checksum-generating software worked for me, so I was searching long for an alternative and found this flash tool: https://spflashtool.com/. Using this tool, flashing worked for me perfectly even without having to bother with checksums.
Good luck!
Click to expand...
Click to collapse
Thank you very much for this! That tool works flawlessly unlike the ulefone garbage.
On another note... anyone know if there is source code for the power 2 to be found somewhere or did the dev just port another recovery somehow? I tried a while back just porting twrp by swapping files but i couldn't get the image to repack with the kitchen tool so i gave up.
ml11ML said:
Same result here. But how did you get the factory rom to flash on the phone? I first got some checksum error and had to find a checksum generator and now the silly multiport flash software says:
" Warning maybe error as follows: 1 com port number repetitive or invalid 2 brom and preloader have the same comport number! Please modify them in INI file or scan again."
I think i did everything correctly (installed the drivers and stuff as it says on the ulefone download page) but i haven't flashed any mediatek devices in a long time and i would be very thankful if someone can tell me what i'm doing wrong. I don't mind it getting bricked as i know that is always a risk with mediatek, but i do need to be able to flash the stock rom.
Click to expand...
Click to collapse
hey, how did you set your IMEIs after bricking? I usually used Engineer Mode to set them, but thats not working since i am missing "CDS Information"
Unlucky25 said:
hey, how did you set your IMEIs after bricking? I usually used Engineer Mode to set them, but thats not working since i am missing "CDS Information"
Click to expand...
Click to collapse
Uh, i never even bothered to think about imei as it just worked without doing anything.
ml11ML said:
Uh, i never even bothered to think about imei as it just worked without doing anything.
Click to expand...
Click to collapse
ok nevermind, i found a solution..yeyy
so if anybody stumples across here, who has no IMEI set, CDS information in MTK mode and no rooted phone... u can set your IMEI in MTK engineering mode under "GPRS"!
hi Guys
I'm in the forum for a very long time as an assistant helper now it has got me hard I have an Axon 10 Pro with curly boot loader and trying to flash a TWRP I have somehow the device or SotA and SlotB have shrunk. The Axon Bootet permanently in 0.5 second cycle and also a FULL Restot or FULL Flash with EDL Tool has not changed anything. Likewise, a new flash about fastboot with the command (fastboot flash boot_a boot.img) the same for boot_b then try with fastboot command (fastboot boot twrp.img) Recovery to start without success fastboot erase boot_a and boot_b has also flashing new but it does not start. Always bootloop:crying::crying::crying::crying:
the Axon 10 pro is back because he had no backup of all we had from my Axon 10 pro made a backup with the edl tool (Backup all) and have then copied his efs backup purely and then this with then on the Axon 10 flashed the Axon 10 pro is now back
Where did you get the twrp from?
From udev
On his donload page
https://forum.xda-developers.com/showpost.php?p=80156866&postcount=3
I had a bootloop issue as well and even though I reflashed using the EDL tool, it doesn't erase and the errors remained, but when I entered EDL mode and reflashed using the Xiaomi Flash Tool, storage was completely erased and the device was flashed cleanly and booted correctly.
I've encountered a similar issue with my Axon (2020U version). I can boot into EDL but nothing else (no fastboot, recovery, etc.). I previously had TWRP up and running successfully, not sure what happened.
Is there a full EDL zip or similar that I can flash to return everything to stock? I tried restoring with the EDL tool but with no success
jbeaulieu said:
I've encountered a similar issue with my Axon (2020U version). I can boot into EDL but nothing else (no fastboot, recovery, etc.). I previously had TWRP up and running successfully, not sure what happened.
Is there a full EDL zip or similar that I can flash to return everything to stock? I tried restoring with the EDL tool but with no success
Click to expand...
Click to collapse
The reason the EDL tool may not work is that is doesn't have the capability to erase. The boot loop that occurs is usually due a corrupt bootfile. Use the MiFlash fastboot recovery tool. Make sure to select the clean all button at the bottom. Place your phone in EDL mode. Hit refresh to make sure your phone is detected. Select the EDL file and then hit flash.
jim262 said:
The reason the EDL tool may not work is that is doesn't have the capability to erase. The boot loop that occurs is usually due a corrupt bootfile. Use the MiFlash fastboot recovery tool. Make sure to select the clean all button at the bottom. Place your phone in EDL mode. Hit refresh to make sure your phone is detected. Select the EDL file and then hit flash.
Click to expand...
Click to collapse
Apologies for my ignorance - what exactly am I flashing? I see the "clean all" radio button, but I'm not sure what EDL package to flash after selecting that option - is there a 2020U package floating around that I'm not seeing?
jbeaulieu said:
Apologies for my ignorance - what exactly am I flashing? I see the "clean all" radio button, but I'm not sure what EDL package to flash after selecting that option - is there a 2020U package floating around that I'm not seeing?
Click to expand...
Click to collapse
The EDL package, use the same EDL package that you used with the EDL tool. Just select the "clean all" radio button. Select the path to the EDL , hit refresh once phone, in EDL mode, is detected, hit flash.
jim262 said:
The EDL package, use the same EDL package that you used with the EDL tool. Just select the "clean all" radio button. Select the path to the EDL , hit refresh once phone, in EDL mode, is detected, hit flash.
Click to expand...
Click to collapse
Okay, I'm trying to use MiFlash to restore the backup I took through the original EDL tool. The MiFLash tool is only timing out with a "cannot receive hello packet" - was this something you encountered as well?
jbeaulieu said:
Okay, I'm trying to use MiFlash to restore the backup I took through the original EDL tool. The MiFLash tool is only timing out with a "cannot receive hello packet" - was this something you encountered as well?
Click to expand...
Click to collapse
I did attempt to flash the wrong EDL file (They are region and device specific) and received that error. I have the Chinese version and once I downloaded the correct EDL file, I had no issues I have even maintained an unlocked boot loader, flashed Magisk and taken OTAs.
jim262 said:
I did attempt to flash the wrong EDL file (They are region and device specific) and received that error. I have the Chinese version and once I downloaded the correct EDL file, I had no issues I have even maintained an unlocked boot loader, flashed Magisk and taken OTAs.
Click to expand...
Click to collapse
Ah, okay. I have the US version - A2020U. Unless I'm mistaken, it looks like there isn't a full EDL zip file available for my version yet, so I might be stuck
There were EDL files up, but apparently they were taken down for some reason.
in the russians there are the 1.6 of the g model as edl (which one can use in a brick) but I do not know if this is synonymous with the u model as you would have to ask @Unjustified Dev or something
@MOD
I hope that the links are allowed here else delete please
1.6 g model edl
http://4pda.ru/forum/index.php?showtopic=965431&st=0#entry88768840
And the lonk too the forum
http://4pda.ru/forum/index.php?showtopic=965431
Chris axon 7 said:
in the russians there are the 1.6 of the g model as edl (which one can use in a brick) but I do not know if this is synonymous with the u model as you would have to ask @Unjustified Dev or something
@MOD
I hope that the links are allowed here else delete please
1.6 g model edl
http://4pda.ru/forum/index.php?showtopic=965431&st=0#entry88768840
And the lonk too the forum
http://4pda.ru/forum/index.php?showtopic=965431
Click to expand...
Click to collapse
Thanks for sharing these. @Unjustified Dev do you happen to know if the 1.6 2020G EDL would be able to be flashed to a 2020U model to recover from a brick? Or if not, is there a place to obtain the proper files, either here on the forums or via PM?
jim262 said:
I did attempt to flash the wrong EDL file (They are region and device specific) and received that error. I have the Chinese version and once I downloaded the correct EDL file, I had no issues I have even maintained an unlocked boot loader, flashed Magisk and taken OTAs.
Click to expand...
Click to collapse
Please share us the EDL file for the Chinese version.
has anyone found the US EDL file yet?
Futility's Forgotten Soldier said:
has anyone found the US EDL file yet?
Click to expand...
Click to collapse
Still waiting. I'm stuck on the EU version.
I have been looking for some sort of root for the ulefone armor 9, and I can't seem to find anything apart from sketchy websites. Can anyone help?
I found the scatterfile, but i still need to find the authentication file, and a download agent? I don't recall ever having to do any of this to root a phone before. Where do I get these files for a ulefone armor 9?
Look inside here:
Systemless Rooting with MagiskSU - Download APK
MagiskSU is an all-in-one Android rooting solution that is developed by topjohnwu. With Magisk Manager, users can easily root Android smartphones in a fastest and effective way. You can download MagiskSU, Magisk Root, Magisk Manager latest versions here.
magisksu.com
jwoegerbauer said:
Look inside here:
Systemless Rooting with MagiskSU - Download APK
MagiskSU is an all-in-one Android rooting solution that is developed by topjohnwu. With Magisk Manager, users can easily root Android smartphones in a fastest and effective way. You can download MagiskSU, Magisk Root, Magisk Manager latest versions here.
magisksu.com
Click to expand...
Click to collapse
there isn't a twrp for this phone.
M8E1 said:
there isn't a twrp for this phone.
Click to expand...
Click to collapse
TWRP isn't needed at all. Look inside here:
[Guide][Root] Magisk without TWRP on Android P
Via Magisk Manager: This method does not need root, and also does not require a custom recovery. However, you MUST have a stock boot image dump beforehand, and you also have to be able to flash the patched boot image, either through fastboot mode...
forum.xda-developers.com
jwoegerbauer said:
TWRP isn't needed at all. Look inside here:
[Guide][Root] Magisk without TWRP on Android P
Via Magisk Manager: This method does not need root, and also does not require a custom recovery. However, you MUST have a stock boot image dump beforehand, and you also have to be able to flash the patched boot image, either through fastboot mode...
forum.xda-developers.com
Click to expand...
Click to collapse
I did this, and I got a "red state" boot loop
M8E1 said:
I did this, and I got a "red state" boot loop
Click to expand...
Click to collapse
Am I missing something? The phone is apparently locked in fastboot mode, and will not accept downloads.
M8E1 said:
I did this, and I got a "red state" boot loop
Click to expand...
Click to collapse
Then report this issue in the related XDA-thread.
jwoegerbauer said:
Then report this issue in the related XDA-thread.
Click to expand...
Click to collapse
What thread would that be? This is for support and questions, isn't it?
M8E1 said:
What thread would that be? This is for support and questions, isn't it?
Click to expand...
Click to collapse
Of course this one:
[Guide][Root] Magisk without TWRP on Android P
Via Magisk Manager: This method does not need root, and also does not require a custom recovery. However, you MUST have a stock boot image dump beforehand, and you also have to be able to flash the patched boot image, either through fastboot mode...
forum.xda-developers.com
Is there anyone who can help? Fastboot does not respond to commands, and patching the boot.img and vbmeta.img via sp flash tool only puts my phone in a "red state". I have tried so many methods for rooting this phone, i'm starting to become convinced that it doesn't exist.
M8E1 said:
Is there anyone who can help? Fastboot does not respond to commands, and patching the boot.img and vbmeta.img via sp flash tool only puts my phone in a "red state". I have tried so many methods for rooting this phone, i'm starting to become convinced that it doesn't exist.
Click to expand...
Click to collapse
i rooted this phone on the first day i got,, i now trying to get proper working twrp so,, search on the google this,, ulefone armor 9 root hovatek and follow the guide there, thats how i did it.
kanadali said:
i rooted this phone on the first day i got,, i now trying to get proper working twrp so,, search on the google this,, ulefone armor 9 root hovatek and follow the guide there, thats how i did it.
Click to expand...
Click to collapse
Hello,
I tried to root my Armor 9E using Magisk but I ended with a bootloop. after a moment of stress (I'm a noob) I was able to put the original boot.img thanks to Fastboot,
I found your thread on Hovatek, how do you patch vbmeta.img ? in my case it's a Armor 9E
About TWRP, do you have any update ? will it be compatible with 9E also ?
Thanks
EDIT : I had to flash the vbmeta.img , I took it from hovatek here https://forum.hovatek.com/thread-36629.html
Totem95d said:
Hello,
I tried to root my Armor 9E using Magisk but I ended with a bootloop. after a moment of stress (I'm a noob) I was able to put the original boot.img thanks to Fastboot,
I found your thread on Hovatek, how do you patch vbmeta.img ? in my case it's a Armor 9E
About TWRP, do you have any update ? will it be compatible with 9E also ?
Thanks
EDIT : I had to flash the vbmeta.img , I took it from hovatek here https://forum.hovatek.com/thread-36629.html
Click to expand...
Click to collapse
Ok guys, don't stress out. I've been dealing with Ulefone for awhile now. I have about 20 of their phones and I have the Armor 9. I just rooted the Armor x7. To start with, Ulefone has the stock system files for download right there on their website for every model they sell.
You are going to need the SP flash tool. I think they even include it in their mega download page.
3086 Armor 9 - Google Drive
drive.google.com
Now these are Mediatek so they do things differently. You turn the phone off and start the flash on SP Flash tool and plug it in. You use the All-in-one authorization for it that's included. Find the special empty vbmeta file on hovatek and use it in place of the other one. Remove the checksum.ini file.
But before all this when you got the boot off of there put it on your sdcard and install Majisk manager. Tell it to install magisk and to patch your boot. Pick the boot file. Then adb pull that file onto your computer and name it boot.img
put all of them back together in place of the old ones with all the stuff you downloaded from the ulefone link and run the checksum generator that it comes with which will produce a checksum.ini file. And if you have that empty vbmeta also you can use SP flash to flash it to your phone and it'll take it. You'll be left with a yellow or orange state then relock your bootloader and you'll be back to normal with magisk installed and root. So...you know, Friggin Mediatek
The reason for your bootloop was because you didn't put the empty vbmeta file in the mix.
MurdochPizgatti said:
Ok guys, don't stress out. I've been dealing with Ulefone for awhile now. I have about 20 of their phones and I have the Armor 9. I just rooted the Armor x7. To start with, Ulefone has the stock system files for download right there on their website for every model they sell.
You are going to need the SP flash tool. I think they even include it in their mega download page.
3086 Armor 9 - Google Drive
drive.google.com
Now these are Mediatek so they do things differently. You turn the phone off and start the flash on SP Flash tool and plug it in. You use the All-in-one authorization for it that's included. Find the special empty vbmeta file on hovatek and use it in place of the other one. Remove the checksum.ini file.
But before all this when you got the boot off of there put it on your sdcard and install Majisk manager. Tell it to install magisk and to patch your boot. Pick the boot file. Then adb pull that file onto your computer and name it boot.img
put all of them back together in place of the old ones with all the stuff you downloaded from the ulefone link and run the checksum generator that it comes with which will produce a checksum.ini file. And if you have that empty vbmeta also you can use SP flash to flash it to your phone and it'll take it. You'll be left with a yellow or orange state then relock your bootloader and you'll be back to normal with magisk installed and root. So...you know, Friggin Mediatek
The reason for your bootloop was because you didn't put the empty vbmeta file in the mix.
Click to expand...
Click to collapse
Trying this method works fine for me until I try to relock the bootloader. Once I do that, I end up with a red state again.
Any advice? I am relocking the bootloader via fastboot flashing lock - is that correct?
MurdochPizgatti said:
Ok guys, don't stress out. I've been dealing with Ulefone for awhile now. I have about 20 of their phones and I have the Armor 9. I just rooted the Armor x7. To start with, Ulefone has the stock system files for download right there on their website for every model they sell.
You are going to need the SP flash tool. I think they even include it in their mega download page.
3086 Armor 9 - Google Drive
drive.google.com
Now these are Mediatek so they do things differently. You turn the phone off and start the flash on SP Flash tool and plug it in. You use the All-in-one authorization for it that's included. Find the special empty vbmeta file on hovatek and use it in place of the other one. Remove the checksum.ini file.
But before all this when you got the boot off of there put it on your sdcard and install Majisk manager. Tell it to install magisk and to patch your boot. Pick the boot file. Then adb pull that file onto your computer and name it boot.img
put all of them back together in place of the old ones with all the stuff you downloaded from the ulefone link and run the checksum generator that it comes with which will produce a checksum.ini file. And if you have that empty vbmeta also you can use SP flash to flash it to your phone and it'll take it. You'll be left with a yellow or orange state then relock your bootloader and you'll be back to normal with magisk installed and root. So...you know, Friggin Mediatek
The reason for your bootloop was because you didn't put the empty vbmeta file in the mix.
Click to expand...
Click to collapse
Hi!
I'm having the same issue as MulBe039.
Device: UleFone Armor 9E (Android 10)
My steps so far:
0.0 Get boot.img, scatter file, checksum generator (from ulefone), magisk.apk (from github), vbmeta.img, drivers, SP Tool (from Hovatek)
0.1 Install magisk on my phone and patch boot.img.
0.2 Enable developer options on my phone
0.3 Enable OEM unlocking and USB debugging on my phone.
0.4 Install drivers on my PC
0.5 Copy scatterfile, boot.img, vbmeta.img into checksum generator's folder and get checksum.ini.
1.0 Connect phone
> adb devices
> adb reboot bootloader
> fastboot devices
> fastboot oem unlock
> fastboot reboot
Phone boots in orange state.
2.0 Re-enable dev opts, (phone shows as already unlocked), USB debugging and turn off the phone.
2.1 Start SP Flashtool
2.2 Select scatter file
2.3 Check only vbmeta.img
2.4 Start download
2.5 Connect phone
2.6 Download completes successfully.
2.7
> fastboot devices
> fastboot reboot
Orange state.
2.8 Factory reset from phone
3. Repeat 2., except at 2.3 check only the patched boot.img
Still orange state.
Magisk app is installed.
4.0 Turn the phone on, enable dev opts and USB debugging, connect to PC
> adb devices
> adb reboot bootloader
> fastboot devices
> fastboot oem lock
> fastboot reboot
Red state - boot loop.
5.0 Hold power button until it turns off abruptly
5.1 Hold volume up until load some sort of boot selector menu.
5.2 Select fastboot mode with vol up button.
5.3 Vol down to boot selected mode
5.4
> fastboot devices
> fastboot oem unlock
> fastboot reboot
Orange state - everything else is working.
What am I missing / doing wrong? How do I re-lock the bootloader?
Thanks in advance!
I have been able to root my Ulefone armor 9 using the method described here https://github.com/bkerler/mtkclient
1 - download boot partition from your device using mtkclient
2 - patch it with magisk manager
3 - flash it again with mtkclient
4 - flash an empty vbmeta (not really sure if this is necessary)
5 - boot your device
I'm not really sure if it is needed to have the bootloader unlocked, but I had it
0xf331dead said:
I have been able to root my Ulefone armor 9 using the method described here https://github.com/bkerler/mtkclient
1 - download boot partition from your device using mtkclient
2 - patch it with magisk manager
3 - flash it again with mtkclient
4 - flash an empty vbmeta (not really sure if this is necessary)
5 - boot your device
I'm not really sure if it is needed to have the bootloader unlocked, but I had it
Click to expand...
Click to collapse
And remember that you cannot lock your bootloader after modifying stuff because signatures will not match and so on
I had to press volume up + volume down while connecting the usb to get mtkclient working
Original Stock PRELOADER_MERLIN.BIN for MERLIN
Works with:
- Xiaomi Redmi 10X 4G
- Xiaomi Redmi Note 9
Firmware Versions:
- (Engineering) AL2522-Merlin-V039-Q-0513
- (Engineering) AL2522-Merlin-V044-Q-0920
- V12.5.1.0.RJOMIXM (FLASHING EDL only.)
- V12.0.1.0.RJOMIXM (FLASHING EDL only.)
- V12.0.8.0.QJOMIXM (FLASHING EDL only.)
- V12.0.7.0.QJOMIXM (FLASHING EDL only.)
- V12.0.6.0.QJOMIXM (FLASHING EDL only.)
- V12.0.5.0.QJOMIXM (FLASHING EDL only.)
- V12.0.4.0.QJOMIXM
- (China) V12.0.4.0.QJOCNXM
- V12.0.3.0.QJOMIXM
- V11.0.5.0.QJOMIXM
- V11.0.4.0.QJOMIXM
- V11.0.2.0.QJOMIXM
How to flash it?
Code:
fastboot flash preloader preloader_merlin.bin
MD5 hashes:
AL2522-Merlin-V039-Q-0513: bc7ebc0c2ca06b0d99856d595949e215
AL2522-Merlin-V044-Q-0920: d2c78e614adf75b98b2b6de74dfb4675
V12.5.1.0.RJOMIXM: 5db0756e0c2c0af508e5a823f204a6f1
V12.0.1.0.RJOMIXM: 1871c0dc6d8de2060175f8c90b133012
V12.0.8.0.QJOMIXM: d9a5ed36161265b61176178bebed8281
V12.0.7.0.QJOMIXM: 2124bb907077b745b8ada8d7108802f9
V12.0.6.0.QJOMIXM: 8c5d38f293d1609da6f79aa7d43b5c0b
V12.0.5.0.QJOMIXM: 27349a358cfd49f73ed3d31d423ca7fd
V12.0.4.0.QJOMIXM: 61ec78ae4a096c0b9f46cf814e5988c3
(China) V12.0.4.0.QJOCNXM: d06b365a15bc622327772586d3c54b18
V12.0.3.0.QJOMIXM: 9a14afee8301b12848ff8ec56c5aebbf
V11.0.5.0.QJOMIXM: 6fb0758e03bf1e43794f5a5273b627b8
V11.0.4.0.QJOMIXM: ea0e773af461a339b76907f94eff73c9
V11.0.2.0.QJOMIXM: d7d5c5b53817b4cc62accfe0eb0cabe3
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/
My device is on China version 12.0.8, will I get bricked if I flash preload 12.0.4 Global?
p233 said:
My device is on China version 12.0.8, will I get bricked if I flash preload 12.0.4 Global?
Click to expand...
Click to collapse
No.
It will works perfectly.
I've attached preloader of V12.0.4.0.QJOCNXM (China) too.
Enjoy
How do i flash is in EDL mode, what should i use because i am at miui 12.5 and i dont know how to make this into edl mode and flash it there
briangwapo81 said:
How do i flash is in EDL mode, what should i use because i am at miui 12.5 and i dont know how to make this into edl mode and flash it there
Click to expand...
Click to collapse
You can't. If you are at MIUI V12.0.5.0 or higher, ou need to flash in fastboot.
For EDL you need an authorized account for use EDL.
You need to go the service centre for professional assistance.
Read it: https://www.xda-developers.com/xiaomi-edl-unbrick-authorized-mi-accounts/
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/
VD171 said:
You can't. If you are at MIUI V12.0.5.0 or higher, ou need to flash in fastboot.
For EDL you need an authorized account for use EDL.
You need to go the service centre for professional assistance.
Read it: https://www.xda-developers.com/xiaomi-edl-unbrick-authorized-mi-accounts/
Click to expand...
Click to collapse
I made the way of VD171 and succeeded. Furthermore I can switch back to MIUI 11.0.5 Global. However, when I was in version 11.0.5, I installed TWRP, but Root didn't work.
p233 said:
I made the way of VD171 and succeeded. Furthermore I can switch back to MIUI 11.0.5 Global. However, when I was in version 11.0.5, I installed TWRP, but Root didn't work.
Click to expand...
Click to collapse
Here, you can see what is working for MERLIN: https://forum.xda-developers.com/t/...omi-redmi-10x-4g-xiaomi-redmi-note-9.4209269/
As you can see, MAGISK is working perfectly on V11.0.5.0.
Did you flash magisk using TWRP or did you flash magisk patched boot.img ?
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/
VD171 said:
Here, you can see what is working for MERLIN: https://forum.xda-developers.com/t/...omi-redmi-10x-4g-xiaomi-redmi-note-9.4209269/
As you can see, MAGISK is working perfectly on V11.0.5.0.
Did you flash magisk using TWRP or did you flash magisk patched boot.img ?
Click to expand...
Click to collapse
I flash magisk using TWRP.
p233 said:
I flash magisk using TWRP.
Click to expand...
Click to collapse
Try patching boot.img using magisk manager.
And then, flashing the magisk patched boot.img to boot partition.
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/
Good afternoon! I flashed my RN 9 with the version merlin_global_images_V12.0.1.0.RJOMIXM. Then I flashed LK from lk-V12.0.4.0.QJOMIXM. The result is this: the phone is loaded only in EDL mode. Now only carry it to the service center?
Gardlok said:
Good afternoon! I flashed my RN 9 with the version merlin_global_images_V12.0.1.0.RJOMIXM. Then I flashed LK from lk-V12.0.4.0.QJOMIXM. The result is this: the phone is loaded only in EDL mode. Now only carry it to the service center?
Click to expand...
Click to collapse
Just bypass the EDL authentication and flash the LK-V12.0.1.0.RJOMIXM.
I suggest you to flash the preloader-V12.0.4.0.QJOMIXM and then, you can flash in download mode and avoid the EDL authentication.
VD171 said:
Just bypass the EDL authentication and flash the LK-V12.0.1.0.RJOMIXM.
I suggest you to flash the preloader-V12.0.4.0.QJOMIXM and then, you can flash in download mode and avoid the EDL authentication.
Click to expand...
Click to collapse
After loading the DA, after 60 seconds (timeout), it returns an error: Error: "EXCEPTION STATUS_EXT_RAM_EXCEPTION". I am 100% sure that I did not click "format all". I have successfully bypassed authentication. I saw your post, it said that preloader_merlin-V12.0.1.0.RJOMIXM cannot load DA...
Gardlok said:
After loading the DA, after 60 seconds (timeout), it returns an error: Error: "EXCEPTION STATUS_EXT_RAM_EXCEPTION". I am 100% sure that I did not click "format all". I have successfully bypassed authentication. I saw your post, it said that preloader_merlin-V12.0.1.0.RJOMIXM cannot load DA...
Click to expand...
Click to collapse
You need to flash using the firmware upgrade mode, it will erase userdata and relock bootloader.
And then, you can restore your backup.
VD171 said:
You need to flash using the firmware upgrade mode, it will erase userdata and relock bootloader.
And then, you can restore your backup.
Click to expand...
Click to collapse
The switched-off phone is not detected by the computer in any way, only EDL mode is possible, I tried to flash in the "Firmware upgrade" mode, the error is the same...
Gardlok said:
The switched-off phone is not detected by the computer in any way, only EDL mode is possible, I tried to flash in the "Firmware upgrade" mode, the error is the same...
Click to expand...
Click to collapse
May you attach the screenshot, please?
VD171 said:
May you attach the screenshot, please?
Click to expand...
Click to collapse
Ok. In the settings, I put UART, 921600.
Gardlok said:
Ok. In the settings, I put UART, 921600.
Click to expand...
Click to collapse
The good news: your device is okay, just need some attention.
The bad news: you really need to do more tests.
Did you try another older MIUI version?
VD171 said:
The good news: your device is okay, just need some attention.
The bad news: you really need to do more tests.
Did you try another older MIUI version?
Click to expand...
Click to collapse
Yes, I tried it. I have tried many different versions of the firmware, both for Russia and for the whole world. I also tried the engineering firmware. I also tried to install various drivers, SPFT. I was booting using Live WinPE. Conclusion: there is always an error that is described above. I think the phone's memory has switched to read-only mode. My phone is under warranty, I will take it to the service... I was upset... eh...
Gardlok said:
Yes, I tried it. I have tried many different versions of the firmware, both for Russia and for the whole world. I also tried the engineering firmware. I also tried to install various drivers, SPFT. I was booting using Live WinPE. Conclusion: there is always an error that is described above. I think the phone's memory has switched to read-only mode. My phone is under warranty, I will take it to the service... I was upset... eh...
Click to expand...
Click to collapse
You just applied some change to the device, causing some brick.
SP Flash Tool is your best friend, certainly it can solve your problems.
Please help me, my phone comes with miui 12.5.X, I have unlocked the bootloader with "MediatekBootloaderUnlock" and I can use "MTK-bypas" to flash it using SP - TOOL, apparently the flashing is always successful, however the system won't boot , it only shows the android logo and I can't access the recovery menu, only fastboot. I tried with MIU 13, MIU 12.5.3 with the same results.
In the end I tried with MIU 12.0.1 (merlin_global_images_V12.0.1.0.RJOMIXM_20210520.0000.00_11.0_global):
1- Use EDL bypass and SPFLASH, it was successful, because fastboot now shows a different logo, but the system does not start and I cannot access the recovery menu either.
2- Use Mediatek Bootloader Unlock
3- Start fastboot and use: "fastboot flash preloader preloader_merlin--V12.0.1.0.RJOMIXM.bin" with apparent success.
4- I go back to SP-Flash and try to flash again MIU 12.0.1 (in theory it should no longer need EDL bypass), uncheck "preloader", I press download and connect my phone and it starts to turn itself on, if I press a key then I receive the authentication error.
If someone could give me a better guide on what to do, I would greatly appreciate it. I have tried formatting using SP-Flash and tried to flash by changing the preloader from "merlin_global_images_V12.0.1.0.RJOMIXM_20210520.0000.00_11.0_global" to "preloader_merlin--V12.0.1.0.RJOMIXM.bin", using "DA_VD171--3.3001 .2020-07-02020-07-14.bin" and "MT6768_Android_scatter--V12.0.1.0.RJOMIXM.txt" but I get the error, the screenshot is from this attempt.
Please help me
What is a brick?If there is no usual way to recover your mobile, then it is called brick in my opinion. That means if you can't able to go to recovery and fastboot mode or the device is just blank with no sign of life.
When brick happens?It will happen because of locking bootloader with custom images or just because of Mediatek/Realme strange behaviour.
What we have to do if brick happens?Simply we have to flash stock firmware with Smart Phone Flash Tool(aka SPFlash Tool). With only SPFlash Tool we can't do anything, since we don't have permission for it. But with the advent of MTK-bypass, we can have full control over our device. If we don't have this MTK-bypass, then we have search for costly alternative's.
You can't flash only if your eMMC is damaged, which is the worst case because oppo phones are prone to eMMC failure.
Click to expand...
Click to collapse
Where to get firmware to flash?Download decrypted .ofp firmware from https://drive.google.com/file/d/1SOmRxix9_UtjOLLanXPYxf4YK1NrA_RW/view
Thanks to @bx2_nero for it.
What is the procedure for using MTK-bypass and SPFlashTool?MTK-bypass is a Python script and it needs different USB ways for working. So with these two in place, we can get our work done.
Linux UsersFor Linux we have to use FireISO or patched kernels for working of MTK-bypass.
Use the Linux guide by @bx2_nero at https://forum.xda-developers.com/t/...our-realme-6-6i-india-6s-linux-method.4251077
Windows UsersFor Windows we have to use libusb32 filter for MTK-bypass working.
Use the guide by @daeSundae at https://forum.xda-developers.com/t/...india-6s-using-spflash-tool-for-free.4222027/
MTK-bypass Official instructionsSee Github ReadMe at https://github.com/MTK-bypass/bypass_utility and XDA support thread at https://forum.xda-developers.com/t/mod-dev-mediatek-mtk-auth-bypass-sla-daa-utility.4232377/
Creditsxyzz / xyz`: GitHub | XDA
chaosmaster / k4y0z: GitHub | XDA
Dinolek: GitHub | XDA
References- https://forum.hovatek.com/thread-37957.html
- https://www.xda-developers.com/bypass-mediatek-sp-flash-tool-authentication-requirement/
- https://forum.xda-developers.com/t/repair-dead-hard-bricked-realme-3-3i-tutorial.4224255/
- https://forum.xda-developers.com/t/...d-flash-in-edl-with-no-auth-for-free.4229683/
- https://forum.xda-developers.com/t/...ash-tool-authentication.4236881/post-84627359
MTKClient
After MTK-bypass got success, @viperbjk who is a reverse engineer came up with a FOSS replacement of SP Flash Tool.
MTKClient combines MTK-bypass and SP Flash Tool together and with many improvements and new features.
Ability to flash partitions without Scatter file
Ability to Readback partitions without specifying address and length
Ability to Format partitions without specifying address and length
Run multiple commands without reconnecting the device
Flash protected partitions(opporeserve2, special_preload, my_custom and cdt_engineering) with locked bootloader
Unlock bootloader without need of in-depth test/Deep testing app from Realme
GitHub - bkerler/mtkclient: MTK reverse engineering and flash tool
MTK reverse engineering and flash tool. Contribute to bkerler/mtkclient development by creating an account on GitHub.
www.github.com
Reserved
I need help, my C12 is stuck on fastboot mode. This happened after flashing a GSI using TWRP and flashing the image in the Super (System and Vendor) partition.
I tried rebooting to recovery mode by executing fastboot reboot recovery but it says that bootloader is not known.
I also tried to flash a GSI (taught it might fix the problem) using fastboot flash system system.img but it says that no partition named system exists.
Please suggest what I should do.
Bro, can you make a video about this? my realme c12 got hardbricked after I flashed ozip file from stock recovery while bootloader is unlocked. it got hardbricked when I reboot it after flashing ozip
DFM23 said:
Bro, can you make a video about this? my realme c12 got hardbricked after I flashed ozip file from stock recovery while bootloader is unlocked. it got hardbricked when I reboot it after flashing ozip
Click to expand...
Click to collapse
What is the present state of the device? Can you able to boot to fastboot mode?
HemanthJabalpuri said:
What is the present state of the device? Can you able to boot to fastboot mode?
Click to expand...
Click to collapse
it has no sign of life, cant go to recovery or fastboot. when I connect it to pc it goes connect and disconnected.
How can I reboot to recovery mode when in fastboot mode? The command fastboot reboot recovery is not working for me.
youcancallmekhen said:
How can I reboot to recovery mode when in fastboot mode? The command fastboot reboot recovery is not working for me.
Click to expand...
Click to collapse
Use latest platform tools
youcancallmekhen said:
How can I reboot to recovery mode when in fastboot mode? The command fastboot reboot recovery is not working for me.
Click to expand...
Click to collapse
HemanthJabalpuri said:
Use latest platform tools
Click to expand...
Click to collapse
Sir I've finally able to reboot to recovery. I've tried flashing the OZIP file for my model but after some time it says Installation failed. When I was still using custom recovery, I wasn't able to mount System and Vendor. My bootloader is also unlocked sir.
Should I lock my bootloader sir?
youcancallmekhen said:
Should I lock my bootloader sir?
Click to expand...
Click to collapse
Don't lock bootloader.
Download this https://drive.google.com/file/d/1jLdDz7M0G_KPDn4jXjTeuFnO1C-MFaBs/view (It is from A.87 UI 1.0 Stock ROM)
Extract above 7z file and flash ONLY super partition from it and TWRP from https://androidfilehost.com/?fid=7161016148664807816 with below commands
Code:
fastboot -w
fastboot flash super super.img
fastboot flash recovery TWRP.img
fastboot reboot recovery
Now enable 'Skip Treble Compatibility error' in TWRP settings and flash stock ROM .ozip in TWRP.
Thanks
HemanthJabalpuri said:
Don't lock bootloader.
Download this https://sourceforge.net/projects/realmec11/files/Fastboot-ROM/[email protected]/download
Extract above 7z file and flash ONLY super partition from it with below commands
Code:
fastboot -w
fastboot flash super super.img
fastboot flash recovery stock-recovery.img
fastboot reboot recovery
Now flash stock ROM .ozip in stock recovery.
Thanks
Click to expand...
Click to collapse
Oh my, thank you so much sir. You have no idea how much you are helping me sir! My parents will be so happy, and we won't waste money… Thank you so much sir…
I'll update you sir after doing these, thank you sir! ♥
HemanthJabalpuri said:
Don't lock bootloader.
Download this https://sourceforge.net/projects/realmec11/files/Fastboot-ROM/[email protected]/download
Extract above 7z file and flash ONLY super partition from it with below commands
Code:
fastboot -w
fastboot flash super super.img
fastboot flash recovery stock-recovery.img
fastboot reboot recovery
Now flash stock ROM .ozip in stock recovery.
Thanks
Click to expand...
Click to collapse
I don't have much data left today sir, so I will download this later. Thank you very much again sir, you're my hero!
DFM23 said:
it has no sign of life, cant go to recovery or fastboot. when I connect it to pc it goes connect and disconnected.
Click to expand...
Click to collapse
Follow the guide and you can get your mobile back to life.
Thanks
HemanthJabalpuri said:
Follow the guide and you can get your mobile back to life.
Thanks
Click to expand...
Click to collapse
thank you bro, Ill follow your guide then. btw does the RMX2185 firmware you provided works with realme c12? I look it up and saw that it was for realme c11
DFM23 said:
thank you bro, Ill follow your guide then. btw does the RMX2185 firmware you provided works with realme c12? I look it up and saw that it was for realme c11
Click to expand...
Click to collapse
Yes, both use same firmware.
I tried the guide but when I click download on sp flash tool it would stay in red bar for 1 min or more then message will appear saying STATUS_EXT_RAM_EXCEPTION. I have read a same comment here in xda about realme c12 I dont know if its only on realme c12.
Thanks for your works sir, you are super awesome!
I rooted My Device (Realme X2 Pro) by Magisk. And Since My Device Bootloader was unlocked I Unrooted/Uninstalled MAgisk.
While Locking Bootloader My Device is Stuck where It displays { The Current Image (boot/recovery) have been destroyed dand cannot boot. Please flash the correct Image or Contact Customer Service to fix it }
While Trying to ENter the Fast Boot Mode {By pressing Volume + - and Power Button} Its Unresponsive
It shows Realme Logo And chrging Display for a Instant
Do you Know any way around to fix my Problem?
Bhuprab said:
I rooted My Device (Realme X2 Pro) by Magisk. And Since My Device Bootloader was unlocked I Unrooted/Uninstalled MAgisk.
While Locking Bootloader My Device is Stuck where It displays { The Current Image (boot/recovery) have been destroyed dand cannot boot. Please flash the correct Image or Contact Customer Service to fix it }
While Trying to ENter the Fast Boot Mode {By pressing Volume + - and Power Button} Its Unresponsive
It shows Realme Logo And chrging Display for a Instant
Do you Know any way around to fix my Problem?
Click to expand...
Click to collapse
Since your device is Qualcomm, I don't know. In any device, we have to flash stock rom (or atleast the partitions that are modified) to get device in working state.
You may get better help at https://forum.xda-developers.com/f/realme-x2-pro-questions-answers.9439/
Thanks