Related
Wanted to share this to get the ball rolling on this device
https: //www .asus .com /us/Phone/ZenFone-Max-Plus-M1/HelpDesk_Download/
just unlock,but no custom for this device
ill try porting twrp
mfbutan said:
just unlock,but no custom for this device
Click to expand...
Click to collapse
Magisk sytemless root. Unlock bootloader and it works flawless
someone said they got magisk to work,but doesn't it need a custom recovery?
Have you been able to get it to work?i just gave it a shot and it failed, multiple times.
what were you trying?
P2thaizarts said:
Have you been able to get it to work?i just gave it a shot and it failed, multiple times.
Click to expand...
Click to collapse
what were you trying?if you can please locate the boot.img location for our phone and I can try rooting and telling you how I did it.
Dandaivin said:
Magisk sytemless root. Unlock bootloader and it works flawless
someone said they got magisk to work,but doesn't it need a custom recovery?
Click to expand...
Click to collapse
I will try..Thanks
mfbutan said:
I will try..Thanks
Click to expand...
Click to collapse
How'd it go,I was unable to unlock bootloader,haven't tried root as I've heard flashing root with adb will make the phone not boot if bootloader is still locked.
Already try but no luck,i cant unlock..unknown error..
So sad..
same thing happening to me
mfbutan said:
Already try but no luck,i cant unlock..unknown error..
So sad..
Click to expand...
Click to collapse
same thing happenening to me and calling asus doesn't help because they say that the majority of peeopl aren't having this issue.
now it's the no pin error,however i think it worked.
mfbutan said:
Already try but no luck,i cant unlock..unknown error..
So sad..
Click to expand...
Click to collapse
I think Asus fixed their ****,so basically I was able to flash the patched_boot.img now.At first it gave me the network error but every time I always tried again,eventually it gave me the no pin error even thought I had a pin.I tried several times with that too and sometimes it would reboot but not wipe anything,until I took away my pin and it immediately gave the no pin error and I tried again and it rebooted without wiping anything.I contacted asus support over the phone and on zentalk and they told me it was already unlocked.I tried flashing the patched boot image and it went through.I booted into the phone with no problems indicating boot loader was unlocked I think.then surprisingly I checked root with root checker and it came back saying I did have root. I guess they updated the unlock boot loader tool to make it not wipe anything.
Dandaivin said:
I think Asus fixed their ****,so basically I was able to flash the patched_boot.img now.At first it gave me the network error but every time I always tried again,eventually it gave me the no pin error even thought I had a pin.I tried several times with that too and sometimes it would reboot but not wipe anything,until I took away my pin and it immediately gave the no pin error and I tried again and it rebooted without wiping anything.I contacted asus support over the phone and on zentalk and they told me it was already unlocked.I tried flashing the patched boot image and it went through.I booted into the phone with no problems indicating boot loader was unlocked I think.then surprisingly I checked root with root checker and it came back saying I did have root. I guess they updated the unlock boot loader tool to make it not wipe anything.
Click to expand...
Click to collapse
Please post your patched_boot.img if you successfully root our Max Plus sir.. thanks...
can't upload files on xda
Jongkits2011 said:
Please post your patched_boot.img if you successfully root our Max Plus sir.. thanks...
Click to expand...
Click to collapse
It's easy enough to do dowload the firmware from their website,install the magisk manager apk.extract the firmware zip and locate boot.img file.copy it either onto a sdcard or select file transfer on your phone and transfer to your phone.AFter doing so go back in to the magisk manager apk you installed select install->patch boot image file->locate the boot.img file you copied let it patch.After it patches make note where it saves,copy that "patched-boot.img" back to your computer(into the adb folder)and inside adb folder hold shift key+right click then open a comman prompt window.type adb devices.Make sure usb debugging is enable in developer options after pressing build number 7 times.make sure your device is found after hitting enter on adb devices.type adb reboot bootloader.after your phone reboot into fastboot mode(ther'll be a llittle word on the bottom left of your phone screen)main screen will be powered by android rest is black.now type fastboot devices to make sure your device is seen.and then type fasboot flash boot "patched-boot.img".Then you'll be rooted.Make sure you unlock bootloader with their tool first.
any news on how it went for you?
Until now i have no luck to unlock my max plus.. I already ask asus personel but until now its under investigation... Im still waiting.
Successfully root my device zenfone max plus thru magisk manager.
Repair imei!
Hello, does anyone know how to recover the imei of this device? was formatted by sp flash tool and now the imei disappeared does not recognize the chips of the operator and does not access the front camera and the option of front camera, opens the wide angle ... Does anyone have any solution for this?
mbsmatthew said:
Hello, does anyone know how to recover the imei of this device? was formatted by sp flash tool and now the imei disappeared does not recognize the chips of the operator and does not access the front camera and the option of front camera, opens the wide angle ... Does anyone have any solution for this?
Click to expand...
Click to collapse
Someone who managed to route the zenfone max plus m1, could I provide the files in the MDDB folder, so I can retrieve the device's image?
Bootloop
Dandaivin said:
It's easy enough to do dowload the firmware from their website,install the magisk manager apk.extract the firmware zip and locate boot.img file.copy it either onto a sdcard or select file transfer on your phone and transfer to your phone.AFter doing so go back in to the magisk manager apk you installed select install->patch boot image file->locate the boot.img file you copied let it patch.After it patches make note where it saves,copy that "patched-boot.img" back to your computer(into the adb folder)and inside adb folder hold shift key+right click then open a comman prompt window.type adb devices.Make sure usb debugging is enable in developer options after pressing build number 7 times.make sure your device is found after hitting enter on adb devices.type adb reboot bootloader.after your phone reboot into fastboot mode(ther'll be a llittle word on the bottom left of your phone screen)main screen will be powered by android rest is black.now type fastboot devices to make sure your device is seen.and then type fasboot flash boot "patched-boot.img".Then you'll be rooted.Make sure you unlock bootloader with their tool first.
Click to expand...
Click to collapse
I tried this, and now my phone has a bootloop...
I have no backup of the original boot.img.
Flashing the whole FW with SP Flashtool doesn´t work (Brom error), I tried all combinations with Vol. Up & Down...
Does anyone has an idea how to get my phone working again?
It came with FW Version WW-V14.02.1711.22 and a chinese Recovery, I wasn´t able to install updates from the beginning.
ADB is also not working, the device is shown as MTP, I have no connection via ADB.
The only thing which is working is fastboot.
Is there a solution to get it working again with fastboot? Can just flash an other boot.img?
Help
can you explain how you did it please, I have the same
Jongkits2011 said:
Successfully root my device zenfone max plus thru magisk manager.
Click to expand...
Click to collapse
Jongkits2011 said:
Please post your patched_boot.img if you successfully root our Max Plus sir.. thanks...
Click to expand...
Click to collapse
Can you please send me thE patched_booot.img you already used.?
Disclaimers:
> I am NOT encouraging anyone to do this. I'm not responsible for anything that happens to your device once you've rooted it already. I did this out of curiosity and I'm just sharing my experience.
> Also yeah, Rmx2040. Not Rmx2040EU.
> It's doable, but it is NOT stable. It boots but you can't use the phone normally. You know, like how you'd normally use a phone.
> I SOFTBRICKED MY PHONE.
Bugs:
UI Restarts every time you go landscape and go back to portrait
Can't open camera
UI Restarts every time you scroll on playstore or anywhere with lots of images
Phone lags, actually no, it restarts all the damn time
NOTES:
@Kraitos was looking for boot.img files so i decided to do a little digging too. I saw in a post somewhere that you need vbmeta.img and a patched (via magisk) boot.img from the device itself.
The "vbmeta.img" I used here was from a Realme 5. I figured all they 'kinda' looked the same plus I don't know if the file is also patched. I tried patching it in magisk but it didn't work, so I just grabbed a (patched?) vbmeta.img (from Realme 5 somewhere in the internet) and used that for our device which is, Rmx2040 (6i)
I grabbed the boot.img from the official ozip file in realme's site (From version A.27, I couldn't find any boot.img for A.31 because they haven't updated the link in the site yet). I opened it up, looked for it, grabbed it and patched it using magisk. Thankfully, it worked.
I used both the vbmeta.img (again, idk if it's patched) and the patched boot.img to root my device. I doubted it too, I thought it'll give me a bootloop or something, but it didn't.
If you want to do it, here are the steps:
Unlock your bootloader. Go here:
https://forum.xda-developers.com/realme-6i/how-to/unlocking-bootloader-realme-6i-rmx-2040-t4174255
Credits to @Kraitos for this awesome guide on how to unlock Rmx2040's bootloader.
If you're done unlocking your bootloader, download these files:
boot.img:
https://drive.google.com/file/d/1D7S9JGwDusyL6hJ6pWrFRBLo_9DdQLGR/view?usp=sharing
vbmeta.img:
https://drive.google.com/file/d/1Do2SfGI_Tp2jERcO77Vh1vEfjiQ6Xxe9/view?usp=sharing
Portable adb fastboot (if you don't have it yet):
https://drive.google.com/file/d/1m78UIsabMQlCvNIIv2e4xI19pN9b1otw/view?usp=sharing
Put all in one folder, it doesn't have to have a name.
Extract the zip file (minimal_adb_fastboot_1.4.3_portable.zip)
*Your folders should have the ff:
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
boot.img
cmd-here.exe
Disclaimer.txt
fastboot.exe
vbmeta.img
Enable USB debugging in your phone.
Connect your phone to your pc.
Double click "cmd-here.exe"
Type the following in CMD:
adb reboot bootloader
If it displays a text in the middle, type "fastboot devices" on cmd. You SHOULD your phone's code there. If it doesn't display anything, replug the type C cable on your phone and type it again, do this until it shows.
Copy this and paste it in CMD:
fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification
Then press enter.
once it's done, copy this next:
fastboot flash boot boot.img
Then press enter.
Reboot your device by typing this in CMD:
fastboot reboot
If you've made it this far, you should install the latest Magisk Manager after you've unlocked the bootloader though. Or do it last, whatever you prefer works.
Viola, now you have an unstable phone.
I'm gonna try locking my bootloader later to flash the A.27 ozip later, I hope going back to "stock and unrooted" fixes the bugs I've experienced :|
I don't really know anything besides trying stuff out, I just wanted to see if it'll work properly with root. If anyone here noticed that I've done something wrong, please do tell me. I wanna try all the methods we can think of just so we can root this device.
Have a wonderful day y'all
Edit:
Everything went bad. I locked the bootloader because I needed access to stock recovery. It gave me a "red state"
I don't know how to fix this problem :|
Awesome guide and thanks for mention you know some people do that if you pay them to unlock bootloader and rooting device so this thread will be a savior to alot of people , I'll do testing in a couple of days asap i get a laptop relocking bootloader is mostly the same when you unlocked bootloader so it should be easy to flash stock again
Alright, so, quick update:
I tried to lock the bootloader while it had root (in my case, magisk). When I did, the phone went to "red state" (For those who don't know, it's basically bootloop wherein the phone never goes to recovery no matter what you do. Not even in stock).
Now, my phone is broken. It bootloops. I don't know what to do with this problem except going to a service center and have this fixed. Does anyone know how much it costs for reflashing stock rom to realme devices?
Sidenote: I tried the volume + down/up method to get into fastboot mode or stock recovery, but it never works. And honestly speaking, I don't think it will. To get into fastboot mode the bootloader needs to be unlocked, so that's crossed out AND I can't get into stock recovery because the phone restarts every 5 seconds because of that pesky "red state" thingy at the start.
Joesh.lucas said:
Alright, so, quick update:
I tried to lock the bootloader while it had root (in my case, magisk). When I did, the phone went to "red state" (For those who don't know, it's basically bootloop wherein the phone never goes to recovery no matter what you do. Not even in stock).
Now, my phone is broken. It bootloops. I don't know what to do with this problem except going to a service center and have this fixed. Does anyone know how much it costs for reflashing stock rom to realme devices?
Sidenote: I tried the volume + down/up method to get into fastboot mode or stock recovery, but it never works. And honestly speaking, I don't think it will. To get into fastboot mode the bootloader needs to be unlocked, so that's crossed out AND I can't get into stock recovery because the phone restarts every 5 seconds because of that pesky "red state" thingy at the start.
Click to expand...
Click to collapse
The problems you faced after rooting the phone is because you flashed an older version of boot.img thats why it wasn't working with latest rom and caused instability in system... And the second problem that you faced that red state thing..!! it was your fault you shouldn't relocked the bootloader with a patched boot img.. and if you wanted to boot the stock recovery you should have used the command " fastboot reboot recovery " this command in fastboot mode reboots the phone to recovery mode... Well i want to know what happend did your phone survived??
mehdi.shah said:
The problems you faced after rooting the phone is because you flashed an older version of boot.img thats why it wasn't working with latest rom and caused instability in system... And the second problem that you faced that red state thing..!! it was your fault you shouldn't relocked the bootloader with a patched boot img.. and if you wanted to boot the stock recovery you should have used the command " fastboot reboot recovery " this command in fastboot mode reboots the phone to recovery mode... Well i want to know what happend did your phone survived??
Click to expand...
Click to collapse
Thanks for the information, I now understand that I should use the same boot.img. It was worth the experiment tho, I just hoped I did it better so I wouldn't have to go through this process again.
My phone is here with me. It's still stuck on red state and I haven't went to a service center to have it fixed yet. I went to Hovatek to look for some ways to fix this problem. I tried using miracle box and the SP flashtool method but the latter had problems with the scatter file and the former didn't get past this:
Waiting for USB Port...
Set OPPO PreLoader USB VCOM (Android) (COM4)
>>Please Hold "ON" to connect with the phone...
I also looked a little bit more into it and I found out that I can use the OFP file and the flasher application here: https://firmwarex.net/realme-6i-rmx2040-official-firmware/
But unfortunately, I can't use the application because it's asking for an OPPO ID or something. Either I bring this phone to a service center or I'll just let it be this way until I decide to sell it somewhere. I hope I'll be able to fix this on my own tho, at least, someday.
Edit:
You can read more of my experience here:
Rmx2040 (realme 6i) scatter file
Hi guys, I'm trying to get the scatter file in this and so far I found this on the ozip file: preloader 0x0 pgpt 0x0 recovery_a 0x8000 misc 0x2008000 para 0x2088000 opporeserve1 0x2108000 opporeserve2
forum.hovatek.com
I'm subma rine13.
Joesh.lucas said:
Thanks for the information, I now understand that I should use the same boot.img. It was worth the experiment tho, I just hoped I did it better so I wouldn't have to go through this process again.
My phone is here with me. It's still stuck on red state and I haven't went to a service center to have it fixed yet. I went to Hovatek to look for some ways to fix this problem. I tried using miracle box and the SP flashtool method but the latter had problems with the scatter file and the former didn't get past this:
Waiting for USB Port...
Set OPPO PreLoader USB VCOM (Android) (COM4)
>>Please Hold "ON" to connect with the phone...
I also looked a little bit more into it and I found out that I can use the OFP file and the flasher application here: https://firmwarex.net/realme-6i-rmx2040-official-firmware/
But unfortunately, I can't use the application because it's asking for an OPPO ID or something. Either I bring this phone to a service center or I'll just let it be this way until I decide to sell it somewhere. I hope I'll be able to fix this on my own tho, at least, someday.
Edit:
You can read more of my experience here:
Rmx2040 (realme 6i) scatter file
Hi guys, I'm trying to get the scatter file in this and so far I found this on the ozip file: preloader 0x0 pgpt 0x0 recovery_a 0x8000 misc 0x2008000 para 0x2088000 opporeserve1 0x2108000 opporeserve2
forum.hovatek.com
I'm subma rine13.
Click to expand...
Click to collapse
Hey buddy i just rooted my realme 6i (RMX 2040) on build number A.37... everything went smooth and working flawlessly.... No system instabilities at all... Btw sorry to hear that your phone is still in brick state.. actually thing is oppo does not allow the users to flash stock rom on locked bl devices that why flasher tool asks for oppo authorized account in order to flash the device... And about SP flash tool.. it will not work either we have to wait for the patched rom that can be flashed on locked devices with sp flash tool
mehdi.shah said:
Hey buddy i just rooted my realme 6i (RMX 2040) on build number A.37... everything went smooth and working flawlessly.... No system instabilities at all... Btw sorry to hear that your phone is still in brick state.. actually thing is oppo does not allow the users to flash stock rom on locked bl devices that why flasher tool asks for oppo authorized account in order to flash the device... And about SP flash tool.. it will not work either we have to wait for the patched rom that can be flashed on locked devices with sp flash tool
Click to expand...
Click to collapse
Woah, is it true you've rooted it? How did you manage to pull it off? Is it similar to what I did except with different files?
Oh and yeah, I think I'll need to bring this to an authorized service center to have it fixed. In your currency, how much do you think it costs to flash the stock rom back to the phone? This has been a question that's been bothering me for months. I do hope it isn't pricey, because if it is then maybe I'll never have it fixed.
Joesh.lucas said:
Woah, is it true you've rooted it? How did you manage to pull it off? Is it similar to what I did except with different files?
Oh and yeah, I think I'll need to bring this to an authorized service center to have it fixed. In your currency, how much do you think it costs to flash the stock rom back to the phone? This has been a question that's been bothering me for months. I do hope it isn't pricey, because if it is then maybe I'll never have it fixed.
Click to expand...
Click to collapse
Yeah the procedure was the same as yours... I unlocked the bootloader i was on A27 build... And i downloaded the latest ozip file from the official site and i opened it up in file manager it asked if i want to update the software i clicked yes.. and it rebooted to stock recovery and started updating the device.. after successful update i opend up the ozip file by renaming it to .zip and extracted the boot.img and vbmeta.img. i patched the boot.img with latest magisk manager and tha than flashed those files in fastboot mode... With same commands that u used... And everything went well and its all good and rooted no problem at all..
And yeah the service center thing.. if its the software issue than the charge around 1.5 to 2k rupees in my country...which is around 9.34 to12.4 US dollars..
mehdi.shah said:
Yeah the procedure was the same as yours... I unlocked the bootloader i was on A27 build... And i downloaded the latest ozip file from the official site and i opened it up in file manager it asked if i want to update the software i clicked yes.. and it rebooted to stock recovery and started updating the device.. after successful update i opend up the ozip file by renaming it to .zip and extracted the boot.img and vbmeta.img. i patched the boot.img with latest magisk manager and tha than flashed those files in fastboot mode... With same commands that u used... And everything went well and its all good and rooted no problem at all..
And yeah the service center thing.. if its the software issue than the charge around 1.5 to 2k rupees in my country...which is around 9.34 to12.4 US dollars..
Click to expand...
Click to collapse
Does root work as it should?
Russian community guys reported that root exists in the system but not works at all. Rooting procedure looks the same.
sqzd0 said:
Does root work as it should?
Russian community guys reported that root exists in the system but not works at all. Rooting procedure looks the same.
Click to expand...
Click to collapse
Yeah it is working like it should work... I tried many things... Different magisk modules.. even changed boot animation with root file manager every thing works like charm..
mehdi.shah said:
Yeah it is working like it should work... I tried many things... Different magisk modules.. even changed boot animation with root file manager every thing works like charm..
Click to expand...
Click to collapse
I don't mean to be rude but, can you make a thread for that? Some rmx 2040 owners want to root their device and I think i just gave them a recipe for disaster.
Oh and by the way, thanks for answering my question. I have another one, will it be okay to update your device whilst rooted? If so then how do you stop the auto update?
(Sorry for the questions man hahahaha I wanted the same outcome but I failed miserably :| )
mehdi.shah said:
Yeah it is working like it should work... I tried many things... Different magisk modules.. even changed boot animation with root file manager every thing works like charm..
Click to expand...
Click to collapse
Bro give me boot.img a37
mehdi.shah said:
Yeah it is working like it should work... I tried many things... Different magisk modules.. even changed boot animation with root file manager every thing works like charm..
Click to expand...
Click to collapse
Give me boot.img of a37 version
mehdi.shah said:
Hey buddy i just rooted my realme 6i (RMX 2040) on build number A.37... everything went smooth and working flawlessly.... No system instabilities at all... Btw sorry to hear that your phone is still in brick state.. actually thing is oppo does not allow the users to flash stock rom on locked bl devices that why flasher tool asks for oppo authorized account in order to flash the device... And about SP flash tool.. it will not work either we have to wait for the patched rom that can be flashed on locked devices with sp flash tool
Click to expand...
Click to collapse
If you rooted dump the stock recovery and boot.img through terminal emulator I will try to port twrp
Boot.img and Vbmeta file can now be accessed by clicking the text above
Do is still need to relock my bootloader inorder to downgrade to A.27 update ? Thanks
mehdi.shah said:
Yeah it is working like it should work... I tried many things... Different magisk modules.. even changed boot animation with root file manager every thing works like charm..
Click to expand...
Click to collapse
Bro i tried the rooting process and i didnt check the boot and i rooted my phone the wifi,blueooth, camera, etc doesnt work anymore. If POSSIBLE can i revert it back to normal?
Can anyone provide me a twrp recovery file for realme 6i rmx2040 A.47 plsss
Hello,
There is any way for unlocking bootloader and rooting the device Motorola Moto E6s XT2053-2 (Fiji) ?
I can allow oem unlock on develop settings. But fastboot says oem unlock doesn't exist and I can't flash anything.
:-(
Thank you very much
try to downgrade for the fist version of fiji firmware and put this command via fastboot
fastboot flashing unlock_critical
it worked with E6+
raphable said:
try to downgrade for the fist version of fiji firmware and put this command via fastboot
fastboot flashing unlock_critical
it worked with E6+
Click to expand...
Click to collapse
how did you downgrade with unlocked bootloader?
VD171 said:
how did you downgrade with unlocked bootloader?
Click to expand...
Click to collapse
install flash tool, and download the oldest rom for fiji from lolinet mirrors, then, extract the rom and power off your device, open flash tool and select the scatter file from the stock, press the download button. In the device, press volume down and connect to the computer, then, if flashed successfully, go to fastboot and run the command
raphable said:
install flash tool, and download the oldest rom for fiji from lolinet mirrors, then, extract the rom and power off your device, open flash tool and select the scatter file from the stock, press the download button. In the device, press volume down and connect to the computer, then, if flashed successfully, go to fastboot and run the command
Click to expand...
Click to collapse
which DA file did you use? also my oldest rom is 288.13, pretty much factory stock for my phone region but fastboot commands are still disabled
VD171 said:
Hello,
There is any way for unlocking bootloader and rooting the device Motorola Moto E6s XT2053-2 (Fiji) ?
I can allow oem unlock on develop settings. But fastboot says oem unlock doesn't exist and I can't flash anything.
:-(
Thank you very much
Click to expand...
Click to collapse
Here is instruction for e6 plus, i think for e6s it might work. I want try this later.
Stock firmwares can take here
Mortyk said:
Here is instruction for e6 plus, i think for e6s it might work. I want try this later.
Stock firmwares can take here
Click to expand...
Click to collapse
Thanks, I will try this !
VD171 said:
Thanks, I will try this !
Click to expand...
Click to collapse
Link to fitmware little incorrect.
I pasted link for 2053-2, but in my phone show 2053-1.
Here is for 2053-1.
Waiting for your report on the successful operation.
VD171 said:
Thanks, I will try this !
Click to expand...
Click to collapse
So you try unlock the phone or no?
well i tried rooting it by flashing an empty vbmeta and a patched boot.img and soft bricked my device because there's no way to unlock the bootloader with the current fw
gonna need to reflash my preloader but the DA isn't letting me flash anything to that partition
luridphantom said:
well i tried rooting it by flashing an empty vbmeta and a patched boot.img and soft bricked my device because there's no way to unlock the bootloader with the current fw
gonna need to reflash my preloader but the DA isn't letting me flash anything to that partition
Click to expand...
Click to collapse
If you try to flash any modified/patched partition to an unlocked device, certainly you will brick it.
VD171 said:
If you try to flash any modified/patched partition to an unlocked device, certainly you will brick it.
Click to expand...
Click to collapse
it's been a while and i've unbricked my device and now am trying to unlock the bootloader
anybody know how to enter brom mode on these fijis? if thats possible, this tool can unlock bootloaders by patching the seccfg partition: https://github.com/bkerler/mtkclient
luridphantom said:
it's been a while and i've unbricked my device and now am trying to unlock the bootloader
anybody know how to enter brom mode on these fijis? if thats possible, this tool can unlock bootloaders by patching the seccfg partition: https://github.com/bkerler/mtkclient
Click to expand...
Click to collapse
You can't.
I tested it, but it gave an error: Preloader - [LIB]: Status: Handshake failed, retrying...
br.rafael.venancio said:
I tested it, but it gave an error: Preloader - [LIB]: Status: Handshake failed, retrying...
Click to expand...
Click to collapse
yea i can enter meta mode so far but nothing else. even the usual volume down and usb plug in that works in spft doesn't work for mtkclient. must be some authentication required to enter brom for flashing
luridphantom said:
yea i can enter meta mode so far but nothing else. even the usual volume down and usb plug in that works in spft doesn't work for mtkclient. must be some authentication required to enter brom for flashing
Click to expand...
Click to collapse
You can't.
Hi! I am Ukraine bad english. I am unlock (not pay dongle, just pc) this smart moto e6s 4/64 (and this very simple for 2/32) Now, i am try in hex edit lk for remove 5 sec and message, flash lk from e6plus no try. info for edit lk for remove 5 sec and message? help. and help how root. (also i am unlock meizu m3 max, not pay dongle, just pc, flash preloader, reset pin frp work)
severagent007 said:
Hi! I am Ukraine bad english. I am unlock (not pay dongle, just pc) this smart moto e6s 4/64 (and this very simple for 2/32) Now, i am try in hex edit lk for remove 5 sec and message, flash lk from e6plus no try. info for edit lk for remove 5 sec and message? help. and help how root. (also i am unlock meizu m3 max, not pay dongle, just pc, flash preloader, reset pin frp work)
Click to expand...
Click to collapse
you used a pay dongle or what free tool to unlock? mtkclient doesnt work for me but i know the dongles can unlock the e6s
to root, go to lolinet and find your firmware version there, unzip and extract boot.img and patch with magisk. flash with fastboot
luridphantom said:
you used a pay dongle or what free tool to unlock? mtkclient doesnt work for me but i know the dongles can unlock the e6s
to root, go to lolinet and find your firmware version there, unzip and extract boot.img and patch with magisk. flash with fastboot
Click to expand...
Click to collapse
its very simple) from fastboot anl 29.137 firmware. Thanks i am try patch boot. fastboot still not flash any part but spft now flash editing lk vbmeta/ vbmeta i flash empty and lk with remove mess orange state. But i am dont flash twrp - i am dont know adress partition - in scatter not find him. Now i am search why its did
severagent007 said:
its very simple) from fastboot anl 29.137 firmware. Thanks i am try patch boot. fastboot still not flash any part but spft now flash editing lk vbmeta/ vbmeta i flash empty and lk with remove mess orange state. But i am dont flash twrp - i am dont know adress partition - in scatter not find him. Now i am search why its did
Click to expand...
Click to collapse
ok i will try when i get home. maybe i cant downgrade to that version and they removed it like with the e6
posted the lolinet link in the other thread. the scatter file is in there
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
Hi guys,
so after I got my xiaomi with a global ROM and wanted to update and that is when I accidentally relocked the bootloader. The version of ROM was invalid apparently and wouldn't let me boot and now I'm stuck in fastboot mode.
My problem is as follows:
-can't enter recovery, stuck at fastboot no matter how many times I try and reboot
-adb not working since I didn't enable it
-bootloader locked (miflash says so and it can't unlock it since I didn't check 'oem unlock enable' and I cannot boot ROM so I can't enable it)
-fastboot flashing says 'not allowed in lock state'
-edl mode not available
I've seen tutorials where people opened their phones to force the phone into edl mode via the testing points but is that the only way`?
Any suggestions on how I could unbrick it?
Much appreciated
yes, it is the only way.
koniv90 said:
Hi guys,
Any suggestions on how I could unbrick it?
Much appreciated
Click to expand...
Click to collapse
you can use this tool to flash the phone on fastboot mode
Xiaomi King Tool - Home.
xiaomikingtool.com
its cost you only 5 credit
Can you flash files by fastboot? if so, flash the global rom images one by one, then reboot
I know this is a late reply, but I was in a similar situation with my phone and here is how I dealt with it: You need to access EDL mode, it doesn't require disassembling the device like the other user here suggested. Here is a thread you can find several variations of fixes here: https://forum.xda-developers.com/t/xiaomi-12-pro-completely-bricked-dead.4422997/
If anyone needs help with a locked bootloader bootlooped phone and doesn't know what to do I can help for a fee.
eclipsek20 said:
I know this is a late reply, but I was in a similar situation with my phone and here is how I dealt with it: You need to access EDL mode, it doesn't require disassembling the device like the other user here suggested. Here is a thread you can find several variations of fixes here: https://forum.xda-developers.com/t/xiaomi-12-pro-completely-bricked-dead.4422997/
If anyone needs help with a locked bootloader bootlooped phone and doesn't know what to do I can help for a fee.
Click to expand...
Click to collapse
I need help please my phone redmi k50 gaming is no recovery and . bootloader is locked
eclipsek20 said:
I know this is a late reply, but I was in a similar situation with my phone and here is how I dealt with it: You need to access EDL mode, it doesn't require disassembling the device like the other user here suggested. Here is a thread you can find several variations of fixes here: https://forum.xda-developers.com/t/xiaomi-12-pro-completely-bricked-dead.4422997/
If anyone needs help with a locked bootloader bootlooped phone and doesn't know what to do I can help for a fee.
Click to expand...
Click to collapse
Please I have pocophone f1 which says system has been destroyed I have downloaded the firmware xiaomi_poco_f1_V12.0.2.0.QEJRUXM_20200907.0000.00_Gobal_10_XFT (by xiaomistockrom.com) and Qualcom Driver V1.0 and MiFlash tool 20210226 and ADB drive R13 and MiFlash unlock tool en-3.5.1128.45 and platform tool r33.0.3-windows after installing all this drives the phone doesn't want to flash when I use MIFLASH TOOL to flash it say ERROR FLASH IS NOT ALLOWED IN LOCK STATE MODE. when I use windows powershell it says the same thing it looks like the bootloader is lock and I don't know the xiaomi e-mail, number and password on the phone pls help me
This what I'm facing
Dims_Camper said:
yes, it is the only way.
Click to expand...
Click to collapse
So even with a locked bootloader and disabled developer options, I can still flash stock rom in edl mode, regardless?
kskksks said:
So even with a locked bootloader and disabled developer options, I can still flash stock rom in edl mode, regardless?
Click to expand...
Click to collapse
Nope, only very old devices.
NOSS8 said:
Nope, only very old devices.
Click to expand...
Click to collapse
So that's why I get the error "operation not allowed for write" in QFIL... What do i do then? Is there a way to unlock bootloader in edl mode? I can't access recovery mode because of the bootloop... Only EDL mode
kskksks said:
So that's why I get the error "operation not allowed for write" in QFIL... What do i do then? Is there a way to unlock bootloader in edl mode? I can't access recovery mode because of the bootloop... Only EDL mode
Click to expand...
Click to collapse
Have you tried to flash stock rom?
I mean, if you have Chinese rom before, just flash with latest Chinese rom.
Ghanaba said:
Please I have pocophone f1 which says system has been destroyed I have downloaded the firmware xiaomi_poco_f1_V12.0.2.0.QEJRUXM_20200907.0000.00_Gobal_10_XFT (by xiaomistockrom.com) and Qualcom Driver V1.0 and MiFlash tool 20210226 and ADB drive R13 and MiFlash unlock tool en-3.5.1128.45 and platform tool r33.0.3-windows after installing all this drives the phone doesn't want to flash when I use MIFLASH TOOL to flash it say ERROR FLASH IS NOT ALLOWED IN LOCK STATE MODE. when I use windows powershell it says the same thing it looks like the bootloader is lock and I don't know the xiaomi e-mail, number and password on the phone pls help me
Click to expand...
Click to collapse
Try to flash the .img files of the fastboot rom, unzip the rom and find all the .img files and flash them with CMD from fastboot, one by one
jholfran3 said:
Try to flash the .img files of the fastboot rom, unzip the rom and find all the .img files and flash them with CMD from fastboot, one by one
Click to expand...
Click to collapse
Hello, My Poco X3 System destroyed itself while I was using it, it showed a glitch screen and turned off. Now I went to flash my mobile through Miflash but it showed the bootloader is locked and now I can't unlock it as the system itself is destroyed and can't do anything. So i wanted to know if i can flash my mobile with cmd as you said above flashing img files one by one or let me know if there is any method to flash my mobile or unlock the bootloader? Please me help bro
flashing is possible with modified firehose programmer (no auth factory loader) or with authorized xiaomi account. both solutions are paid service and cannot advertised here.
please -as always- read the thread you posted in. I can see useful information shared already. wait for other replies.
letsgofly said:
Hello, My Poco X3 System destroyed itself while I was using it, it showed a glitch screen and turned off. Now I went to flash my mobile through Miflash but it showed the bootloader is locked and now I can't unlock it as the system itself is destroyed and can't do anything. So i wanted to know if i can flash my mobile with cmd as you said above flashing img files one by one or let me know if there is any method to flash my mobile or unlock the bootloader? Please me help bro
Click to expand...
Click to collapse
Hi, try to flash the .img files from the fastboot stock rom whit cdm in fastboot, one by one, some files will give error but skip that, then reboot the phone as normal, it should work.
example:
fastboot flash boot boot.img
fastboot flash cust cust.img
etc.
jholfran3 said:
Hi, try to flash the .img files from the fastboot stock rom, one by one, some files will give error but skip that, then reboot the phone as normal, it should work.
Click to expand...
Click to collapse
If it were that simple, it would have been known for a long time.
You have already posted about this (post#14).
NOSS8 said:
If it were that simple, it would have been known for a long time.
You have already posted about this (post#14).
Click to expand...
Click to collapse
I had a Mi 9T and by mistake I installed a recovery that didn't correspond to it, the phone got bricked, and the only way to save it was like this, I searched and read everywhere but I couldn't find a solution, flashing the .img files was my idea, I didn't know if it would work but it did.
:V
jholfran3 said:
I had a Mi 9T and by mistake I installed a recovery that didn't correspond to it, the phone got bricked, and the only way to save it was like this, I searched and read everywhere but I couldn't find a solution, flashing the .img files was my idea, I didn't know if it would work but it did.
:V
Click to expand...
Click to collapse
To install a recovery, the bootloader must be unlocked.