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
Related
Guys i have a really really big problem with mate 9 (MHA-L29). I broke both twrp and system same time (please don't ask why.)
Now, my phone don't open, just fastboot&rescue mode, useless huawei recovery (which can't format data neither install stock rom). Besides, i can't install stock rom because i tried once, and i downloaded wrong system file, and i can't format the phone now. Because of that, stock rom that i download sd card not working too. Because there is a dload file in phone.
worst of all, i can't install twrp again, because my fastboot screen tell me that: "Phone Unloced" (with red) "FRP Lock" (with green). When i try to install twrp, adb says "Failed, remote command not allowed"
Now, if can install the twrp, all my problems will be solve. There is 1 custom rom (RomAur) and 1 system backup.
How can i install twrp with this situation?
Please someone help me i spend 2 days and still nothing! How can i open this phone? Stock rom, with/without root, custom rom whatever, just tell me how can i open this phone
up
You get that command when trying to flash the wrong recovery partition, was your room nougat or Oreo based?? If nougat it's fastboot flash recovery recovery.img and Oreo fastboot flash recovery_ramdisk recovery.img I think you are trying to flash the wrong partition
shae23 said:
You get that command when trying to flash the wrong recovery partition, was your room nougat or Oreo based?? If nougat it's fastboot flash recovery recovery.img and Oreo fastboot flash recovery_ramdisk recovery.img I think you are trying to flash the wrong partition
Click to expand...
Click to collapse
No, my twrp is not wrong, i installed before, and i used long time, till broken. I installed wrong twrp recovery over correct recovery (i was trying to chance recovery because project treble). Thats why my twrp broken. Now i try to correct one, but adb says "not allowed". My custom rom nougat based.
cannurkars said:
No, my twrp is not wrong, i installed before, and i used long time, till broken. I installed wrong twrp recovery over correct recovery (i was trying to chance recovery because project treble). Thats why my twrp broken. Now i try to correct one, but adb says "not allowed". My custom rom nougat based.
Click to expand...
Click to collapse
With FRP lock you'll have to use DC-Phoenix.
But it costs €19 (For 3 days usage).
Simply put you can bypass FRP with it by force closing DC-Phoenix when it has activated the backdoor, after this you can flash anything from fastboot (until you reboot).
So you could use it to flash back TWRP.
Or you can use it to install stock firmware
ante0 said:
With FRP lock you'll have to use DC-Phoenix.
But it costs €19 (For 3 days usage).
Simply put you can bypass FRP with it by force closing DC-Phoenix when it has activated the backdoor, after this you can flash anything from fastboot (until you reboot).
So you could use it to flash back TWRP.
Or you can use it to install stock firmware
Click to expand...
Click to collapse
I will try it. Thank you very much.
cannurkars said:
Guys i have a really really big problem with mate 9 (MHA-L29). I broke both twrp and system same time (please don't ask why.)
Now, my phone don't open, just fastboot&rescue mode, useless huawei recovery (which can't format data neither install stock rom). Besides, i can't install stock rom because i tried once, and i downloaded wrong system file, and i can't format the phone now. Because of that, stock rom that i download sd card not working too. Because there is a dload file in phone.
worst of all, i can't install twrp again, because my fastboot screen tell me that: "Phone Unloced" (with red) "FRP Lock" (with green). When i try to install twrp, adb says "Failed, remote command not allowed"
Now, if can install the twrp, all my problems will be solve. There is 1 custom rom (RomAur) and 1 system backup.
How can i install twrp with this situation?
Click to expand...
Click to collapse
During startup the menu there is a option to go in Huawei e-recovery, when you are at the start up menu hold volume up for about 5 second.
ConnerZhao929 said:
During startup the menu there is a option to go in Huawei e-recovery, when you are at the start up menu hold volume up for about 5 second.
Click to expand...
Click to collapse
No it wasn't work for me. But thank for your attention. I'm glad to find a good person to help me and my problem solved about 1-2 hour ago.
Special Request
Hey ante . Is it possible to help me ? I rooted my phone 2 days back and messed it up while downloading a framework app which ended me up in a bootloop. I have been reading and following your posts of you helping others. I don't really get the steps what I should follow.
My phone is unlocked. FRP shows Unlock.
Rooted on oreo and I tried e-recovery and fastboot steps you mentioned in other threads using kernel and ramdisk etc. ( After this I have lost access to TWRP and I am simply getting EMUI Screen with options for Factory Data Reset and Wipe Cache Partition. I don't know where it is going to lead me next :-/.
Also downloaded Huawei Extractor and tried to extracted specific files but the firmware file I have doesn't have CUST.img file.
Also the site link you mentioned for download firmware is in some other language and I am unable to search for my firmware.
I also tried the placing update file in the dload on my sd card but fails at 5%. The file was correct and I am sure I did'n download the wrong firmware.
Currently it shows this on the fastboot screen.
Andorid reboot reason
: AP_S_ABNORMAL 32
NA
Just don't know what I should be doing ? PLEASE HELP BRO?
ante0 said:
With FRP lock you'll have to use DC-Phoenix.
But it costs €19 (For 3 days usage).
Simply put you can bypass FRP with it by force closing DC-Phoenix when it has activated the backdoor, after this you can flash anything from fastboot (until you reboot).
So you could use it to flash back TWRP.
Or you can use it to install stock firmware
Click to expand...
Click to collapse
AniMaL92 said:
Hey ante . Is it possible to help me ? I rooted my phone 2 days back and messed it up while downloading a framework app which ended me up in a bootloop. I have been reading and following your posts of you helping others. I don't really get the steps what I should follow.
My phone is unlocked. FRP shows Unlock.
Rooted on oreo and I tried e-recovery and fastboot steps you mentioned in other threads using kernel and ramdisk etc. ( After this I have lost access to TWRP and I am simply getting EMUI Screen with options for Factory Data Reset and Wipe Cache Partition. I don't know where it is going to lead me next :-/.
Also downloaded Huawei Extractor and tried to extracted specific files but the firmware file I have doesn't have CUST.img file.
Also the site link you mentioned for download firmware is in some other language and I am unable to search for my firmware.
I also tried the placing update file in the dload on my sd card but fails at 5%. The file was correct and I am sure I did'n download the wrong firmware.
Currently it shows this on the fastboot screen.
Andorid reboot reason
: AP_S_ABNORMAL 32
NA
Just don't know what I should be doing ? PLEASE HELP BRO?
Click to expand...
Click to collapse
What's your firmware now?
You can get that info in Fastboot using
Code:
fastboot oem get-product-model
fastboot oem get-build-number
Since your recovery and fastboot still functions you probably will only need to use HWOTA to get back to stock.
It can be found here: https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-oreo-update-package-t3699522
But post your cust/build before proceeding.
Also cust.img is found in UPDATE.APP in the hw data zip.
Problem Solved - Somewhat
Hey ante. Thanks for the promt reply. I got it solved by using CHIMERA tool.
Would like to suggest others also stuck with same issue to use CHIMERA.
Note - It is a paid tool and 100% legit and it can help with all problems related to FRP, Bootloader Lock / Unlock & also flashes back to factory firmware.
However what I am facing now I have flashed another version of firmware which isn't my region and some features of my phone like fingerprint scanner and other things are not working but phone is back to live. So Im glad and looking forward to searching for clean Oreo Firmware for my region to flash using CHIMERA Again.
Also, the sick and stupid part of it. I went to the service center and a person non-technical told me straight that you lost your device and it's of no use now. We cannot fix such issues 99% but I'll still ask my team and let you know after 3 days.
Thank God I didn give them and wasted my time and money.
As soon as I returned, I followed up to things and got it done myself. :good:
Anybody can possibly suggest a official firmware Oreo EMUI for Middle East Region!? If not which one can be flashed instead and where to download from?
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.?
Hi,
My phone is actually dying and I don't know how to recover it this time.
I had a perfectly working setup with latest weekly update of Xiaomi eu MIUI , TWRP and magisk, and know even fastboot is not responding.
I usually don't like when people say that, but I think a malware did it, as my apps started not responding in a few minutes, and the reboot finished the job.
Now it won't boot anymore, when it's plug the notification led is red, and fastboot is detected but commands are stuck.
Also, TWRP is neither accessible from "power + vol up" since last miui eu update, nor from fastboot since the "accident"
If someone have any advice on how to unlock fastboot, flash back the rom or any other way to recover my phone, please help
Also, if you want to know the rest of the story, it's here...
I was using my phone as usual, trying to setup a bridge openvpn connection. (like everyone :laugh: )
The issue is that the only app claiming to do that isn't free, and I want to be sure I can make it work before spending any money.
So I tried to patch it and different apks (I know it's bad...), and while transferring an apk from my laptop to my phone, I noticed the transfer was kinda slow for a few seconds (nothing worrying, but unusual)
Then some of my apps didn't want to launch and, back to the app drawer, most of my apps had their package names, with no icons...
It was at this moment Jackson I knew I screwed up...
I then tried rebooting, and the phone stayed a few minutes on the MIUI screen, then shut off.
After a reboot, I noticed the red led, the absence of boot animation, and the bootloop.
Obviously, if I had a fastboot access, it would be easy to boot on TWRP and then flash back my rom properly but I can't...
EDIT: to make this clearer (I know the post above is a little bit messy), I have the following issues:
- No access to TWRP (for flashing)
- Fastboot is accessible but broken enough so flash/boot to twrp is not possible
- I just though of EDL mode, but "fastboot oem edl" doesn't seems to work
- I prefer to avoid opening my phone (to access to the EDL test points)
EDIT2: You can't flash anything in EDL mode without specific autorisations from xiaomi, so this mode becomes way more useless than on my previous Mi A1. I managed to miraculously flash some things by using miflash in fastboot mode. Maybe working on a windows os instead of gnu/linux helped somehow...
Thelm76 said:
Hi,
My phone is actually dying and I don't know how to recover it this time.
I had a perfectly working setup with latest weekly update of Xiaomi eu MIUI , TWRP and magisk, and know even fastboot is not responding.
I usually don't like when people say that, but I think a malware did it, as my apps started not responding in a few minutes, and the reboot finished the job.
Now it won't boot anymore, when it's plug the notification led is red, and fastboot is detected but commands are stuck.
Also, TWRP is neither accessible from "power + vol up" since last miui eu update, nor from fastboot since the "accident"
If someone have any advice on how to unlock fastboot, flash back the rom or any other way to recover my phone, please help
Also, if you want to know the rest of the story, it's here...
I was using my phone as usual, trying to setup a bridge openvpn connection. (like everyone :laugh: )
The issue is that the only app claiming to do that isn't free, and I want to be sure I can make it work before spending any money.
So I tried to patch it and different apks (I know it's bad...), and while transferring an apk from my laptop to my phone, I noticed the transfer was kinda slow for a few seconds (nothing worrying, but unusual)
Then some of my apps didn't want to launch and, back to the app drawer, most of my apps had their package names, with no icons...
It was at this moment Jackson I knew I screwed up...
I then tried rebooting, and the phone stayed a few minutes on the MIUI screen, then shut off.
After a reboot, I noticed the red led, the absence of boot animation, and the bootloop.
Obviously, if I had a fastboot access, it would be easy to boot on TWRP and then flash back my rom properly but I can't...
Click to expand...
Click to collapse
Hi
I had a similar situation
I comfigured an app and during configuration the phone start framing
I rebooted and stucked at miui screen
I tried to reboot in recovery ,nothing
I downloaded latest miui for europe 12.0.3 and mi flash
For me fastboot worked to flash latest firmware from xiaomi
And now is working and my bootloader is locked
Thelm76 said:
Hi,
My phone is actually dying and I don't know how to recover it this time.
[/hide]
Click to expand...
Click to collapse
Xiaomi.eu has TWRP issue...
Go to https://www.androidfilehost.com/?w=files&flid=50678 and find your recovery (lmi) and flash it with fastboot and boot to recovery.
fastboot flash recovery twrp.img
fastboot boot twrp.img
Now download the new ROM 20.10.16, push it to the internet storage and install it dirty... Wipe Cache and reboot....
My problem is almost same, i unlock the bootloader to flash xiaomi.eu rom from global rom, unlocking and flashing custom recovery was done smoothly, when i tried to flash xiaomi.eu rom version 12.0.8 it booted back to recovery, and i format the data partition and booted to system, and same result. I tried global its same result.
Then i tried miflash tool, " antirollback error ".
Now i don't know what to do. Hope my precious poco f2 pro is not bricked, coz i can still manage to boot in custom recovery, and can use miflash tool but error.
Can someone out there help me please. Thanks in advance.
Eldybug said:
My problem is almost same, i unlock the bootloader to flash xiaomi.eu rom from global rom, unlocking and flashing custom recovery was done smoothly, when i tried to flash xiaomi.eu rom version 12.0.8 it booted back to recovery, and i format the data partition and booted to system, and same result. I tried global its same result.
Then i tried miflash tool, " antirollback error ".
Now i don't know what to do. Hope my precious poco f2 pro is not bricked, coz i can still manage to boot in custom recovery, and can use miflash tool but error.
Can someone out there help me please. Thanks in advance.
Click to expand...
Click to collapse
Since you have access to a properly working fastboot and recovery, I believe there is always a way to recover your phone.
I'll be glad to help you but for now, I'm more focused on my issue.
Only thing, while using miflash, be careful to never lock your bootloader since you would have to open your phone to access EDL mode in case of bootloop
(but you can lock it afterwards if you want)
Enricosteph said:
Xiaomi.eu has TWRP issue...
Go to https://www.androidfilehost.com/?w=files&flid=50678 and find your recovery (lmi) and flash it with fastboot and boot to recovery.
fastboot flash recovery twrp.img
fastboot boot twrp.img
Now download the new ROM 20.10.16, push it to the internet storage and install it dirty... Wipe Cache and reboot....
Click to expand...
Click to collapse
Well, the main issue here is that fastboot seems to be broken too...
i found this for you on the LOS rom for poco f2 pro (am not the autor) this is for the "Anti-rollback error" (i hope that can help you):
romabah said:
Gentlemen with EU versions of Poco F2 pro, could you help me out?
Right now i am running 12.0.2.0 QJKEUXM.
To flash Lineage i first need to flash MIUI V12.0.3.0.QJKMIXM via MiFlash. I tried to do that but got an Anti-rollback error.
Checking via fastboot i saw that my phones anti rollback value is 1, but MIUI V12.0.3.0.QJKMIXM firmware has an anti rollback of 0.
Some folks say to delete first 5-6 lines in text editor from .bat file, but at the same time people tell everywhere to NOT flash firmware with lower value that your current anti rollback.
Any advice? How did other EU folks fix this?
Edit: I fixed it! I will NOT and cannot claim that this will fix all rollback error's, but it fixed mine.
0) This is applicable to fastboot version of MIUI V12.0.3.0.QJKMIXM (aka tgz file that you need to extract twice)
1) Move the extracted firmware directory imi_global_images_V12.0.3.......ets.ets. ( map with flash_all.bat, images ) to C: directory and rename to something short, like xiaomiFirm.
This will solve a lot of weird error's as MiFlash doesnt like long directories
2) Within the moved map open flash_all.bat with text editor and delete everything starting and including "::check anti_version" to and including "echo %..."
This removes the anti rollback check somehow. The reason for only editing flash_all.bat is because this is the .bat file that is run when you choose clean all option in MiFlash, i assume you dont want to clean all and lock now do you?
3) After finishing flashing mine gave error Not catch checkpoint flash is not done, but booted normally. Gave me a heart attack.
Sanity check: When running cmd "fastboot getvar anti" it returned "anti: 1"
Meaning i just flashed a ROM with anti of 0 on a phone with a anti value of 1. At least i believe so.
In any case, thank all for giving feedback for other ways of fixing this.
Click to expand...
Click to collapse
I'll try to make a type C deep flash cable to flash fastboot, and edit this message to explain if this works
Thelm76 said:
Well, the main issue here is that fastboot seems to be broken too...
Click to expand...
Click to collapse
Try to hold down only Vol Down and connect it to your computer
Enricosteph said:
Try to hold down only Vol Down and connect it to your computer
Click to expand...
Click to collapse
I don't know if this was my cable or fastboot oem edl, but windows recognised the phone as qualcomm qdloader 9008. I'll now try to update fastboot, install twrp and check the extent of the damages.
Fangstergangsta said:
i found this for you on the LOS rom for poco f2 pro (am not the autor) this is for the "Anti-rollback error" (i hope that can help you):
Click to expand...
Click to collapse
Indeed, OP, try to flash everything from the start thep by step.
You must stop therapeutic relentlessness!!!
Just plug out the charger and let him die softly...
Put him back in his sweet box after his last breathe
Bury him in your garden with a decent burial : he deserve it!!!!
It's HIS TIME, dude....
Regards
Mastakony said:
You must stop therapeutic relentlessness!!!
Just plug out the charger and let him die softly...
Put him back in his sweet box after his last breathe
Bury him in your garden with a decent burial : he deserve it!!!!
It's HIS TIME, dude....
Regards
Click to expand...
Click to collapse
Haha it's not therapeutic relentlessness when you're sure it will live again in a few days (and fully working!)
It just need a good memory wipe and android replacement
As I managed to get to emergency mode, I can now easily replace its software
EDIT: I didn't know that for these xiaomi devices, you need very specific autorisations to flash something with EDL... Fortunately, after messing around with miflash, I managed to unlock myself out of this infinite loop
As I managed to get to emergency mode, I can now easily replace its software
Click to expand...
Click to collapse
How are you going to flash the software?
Well,
By using edl mode and miflash, I got some errors as I was not authorised to do this operation, so I rebooted to fastboot, reused miflash, and I don't know which kind of magic did that but after some files flashed and an error, I was able to boot on TWRP. With this done, I tried to keep my data but didn't worked, and as I have everything constantly backup, I dicided to do a flashall.
now, I think I have a good MIUI base to flash MIUI EU back
Thelm76 said:
Well,
By using edl mode and miflash, I got some errors as I was not authorised to do this operation, so I rebooted to fastboot, reused miflash, and I don't know which kind of magic did that but after some files flashed and an error, I was able to boot on TWRP. With this done, I tried to keep my data but didn't worked, and as I have everything constantly backup, I dicided to do a flashall.
now, I think I have a good MIUI base to flash MIUI EU back
Click to expand...
Click to collapse
I have the same situation plus no fastboot or recovery at all.. Please tell me how did you resolve it?
ghannaiem said:
I have the same situation plus no fastboot or recovery at all.. Please tell me how did you resolve it?
Click to expand...
Click to collapse
Is the phone detected by the pc in usb?
And when you press power+ sound + or - What is happening?
NOSS8 said:
Is the phone detected by the pc in usb?
And when you press power+ sound + or - What is happening?
Click to expand...
Click to collapse
Yes , detected by usb but as qcom 9008,
And when holding down power button with + or - vol it restarts again to 9008 .
So it is not detected by any means, but only detected in edl mode
ghannaiem said:
Yes , detected by usb but as qcom 9008,
And when holding down power button with + or - vol it restarts again to 9008 .
So it is not detected by any means, but only detected in edl mode
Click to expand...
Click to collapse
how did it happen?
My imei got lost so I tried to flash eng rom through MI flash to fix it. It flashes all except certain file called (aop. Mbn) so I tried to flash it by cmd commands via fastboot and then the phone bricked.. No booting to fastboot anymore , no recovery. even with disconnecting battery and reconnecting again... Phone only recognized in Edl mode and when flashing through MI flash it asks for edl authorization... Account login successful but then flash fail cuz account is not authorized. So I think The only solution will be authorized account or patched prog_ufs file
[READ FIRST] {BLU G90 PRO} I am new to all this, I started learning about rooting a week ago. If you can help, please explain in detail. TL/DR at bottom
[CAUSE] I'm not sure but I attempted root by useing migisk and lateset firmware boot.img provided by xda.
[PROBLEM] My phone constantly bootloops. I cannot access recovery mode as it just reboots. adb won't work as the phone does not connect to the computer. I can go to fastboot mode though.
[ATTEMPTS] I have let the battery die which did nothing, I tried to let the phone charge but it does not go up that much, but fastboot mode at least lets it chare a little. I have tried to reflash the stock boot.img but adb doesn't work. (see video).
[RESOURCES] I have all files assosiated with this. I now have stock firmware as well. Willing to wipe phone completely. I am bootloaded.
TL/DR: ****ed up root with wrong boot.img in magisk. Bootlooped and low battery..
[VIDEO]
I_like_root_pls said:
[READ FIRST] {BLU G90 PRO} I am new to all this, I started learning about rooting a week ago. If you can help, please explain in detail. TL/DR at bottom
[CAUSE] I'm not sure but I attempted root by useing migisk and lateset firmware boot.img provided by xda.
[PROBLEM] My phone constantly bootloops. I cannot access recovery mode as it just reboots. adb won't work as the phone does not connect to the computer. I can go to fastboot mode though.
[ATTEMPTS] I have let the battery die which did nothing, I tried to let the phone charge but it does not go up that much, but fastboot mode at least lets it chare a little. I have tried to reflash the stock boot.img but adb doesn't work. (see video).
[RESOURCES] I have all files assosiated with this. I now have stock firmware as well. Willing to wipe phone completely. I am bootloaded.
TL/DR: ****ed up root with wrong boot.img in magisk. Bootlooped and low battery..
Click to expand...
Click to collapse
How to root/alternate for twrp? BLU G90 PRO
I have spent 2 days trying to figure out how to root my g90 pro. I can't find twerp for it and every possible guide I find destroys my sanity when I find out it won't work. I have magisk as a zip file on my phone right now, is there an alternate...
forum.xda-developers.com
[CAUSE] You not know how using fastboot mode:
Code:
fastboot devices
If okay so you can using:
Code:
fastboot flash boot boot.img
But the boot.img file is in the folder platform?
[PROBLEM] You need better file patched. Maybe your pacthed_boot.img is wrong! So you can flash TWRP but need modified vbmeta file. I can help with that file!
[ATTEMPTS] two ways: 1- charge battery for using with fastboot. 2- Using SPFT for flash stock ROM or stock boot.img only.
[RESOURCES] You know use SPFT for flashing stock ROM?!
Created 2 posts with same device?? daaammm
Look this guy!: https://forum.xda-developers.com/t/...310ww-mt6765-android-10.4163497/post-84082633
LMFAO I FORGOT THE ./
but your post also made alot of things click for me. I was feeling down cause I though I ****ed up my first phone before a week even passed. Thanks for the help! Feeling alot better now!
also I got the recovery mode to pop up and I'm downloading verified stock firmware rn. Will update
Everything is fixed! I used spft and installed the stock rom! Everything is backing up now from my cloud account.
Now I want to root even more and I got a bit more experience. I saw your post mentioned a program bprd. Should I use that instead of the twrp build I found for this?
Also thanks!
I_like_root_pls said:
program bprd
Click to expand...
Click to collapse
Where did I write that?
Now understand: You have 2 ways for flash only recovery.img(TWRP or PBRP).
Using SPFT;
Using adb-fastboot.
Obviously if you want ROOT without Custom Recovery you should use magisk to create patched_boot.img and flash with 2 same ways.
Long story short I messed up and now I don't have recovery. Only fastboot. Was bricked too before the no recovery thing.
How do I try to sort this? I don't have a pc either.
Using my old OnePlus 8T I was able to unlock, root and install a custom kernel.
Any ideas?
shadowofdeth said:
Long story short I messed up and now I don't have recovery. Only fastboot. Was bricked too before the no recovery thing.
How do I try to sort this? I don't have a pc either.
the good news is your phone can very likely be fixed. however in my experience you will need a computer. Folks here would love to help but knowing what device you are having an issue with would probably help with response to your situation. from fastboot you can boot a recovery image for your device and go from there. from fastboot you can also likely flash stock firmware to your device and start over fresh. It's also common to have to perform a factory reset after flashing the device to get it to properly boot.
Click to expand...
Click to collapse
OnePlus 9.
I tried searching but there are so many dead ends for finding the stock recovery. Even with that I'd still be bricked.
Where would one find the stock recovery, kernel and fastboot ready update.zip?
You do realize the boot.img is both recovery and kernel. Just extract it from payload.bin
MrSteelX said:
You do realize the boot.img is both recovery and kernel. Just extract it from payload.bin
Click to expand...
Click to collapse
If only I thought of that. It's not like I've been trying all day without success extracting what I need from the payload.bin. Definitely no dead ends there. Thanks for the massive help.
shadowofdeth said:
If only I thought of that. It's not like I've been trying all day without success extracting what I need from the payload.bin. Definitely no dead ends there. Thanks for the massive help.
Click to expand...
Click to collapse
borrow a laptop from someone , use the msm tool
taintsx said:
borrow a laptop from someone , use the msm tool
Click to expand...
Click to collapse
Im so close I can smell it now. Managed to get Python installed (had to deep dive into the comments on articles and tutorials) and have everything extracted in the last hour.
Now, for flashing these images I have to use Termux and it's working for the most part. My issue is now that I can flash one batch of images but not the other as per the xda guide linked now:
Restore OnePlus 9 to Stock via Fastboot Commands
This guide assumes you have the SDK Platform Tools installed and working, along with USB drivers for your device (if needed), and have your full update zip which you've already extracted the payload.bin from, and then dumped the images using...
forum.xda-developers.com
I keep getting errors about the partition being locked or something.
So close man. So close.
Locked partitions can only be flashed in fastbootd (fastboot reboot fastboot to get there).
First of all... Hold the both volume and power button for around 2 minutes. It'll take you to the bootloader mode. Then from the bootloader mode turn off your device then boot into edl then flash with msm.
Lesson learned