Fastboot issues when rooting Moto G Pure - General Questions and Answers

Device is a Moto G Pure (codename Ellis), I've found little to no support for this device on the Internet, and a friendly redditor informed me due to the nature of the processor's manufacturers (MediaTek), there never will be much support for this model of device. I have managed to unlock the bootloader, and I'm all ready to go with drivers and fastboot and ADB, and I also have a twrp recovery image. My issue is I'm unsure if this is the correct TWRP img as I downloaded one for a similar Moto model (Moto G Stylus 2020, TWRP 3.5.0-0) and fastboot keeps throwing errors when I try to flash or boot this image. First error was 'command is not support' as I was using flashboot boot boot.img, did some research and instead tried flashboot flash boot boot.img which wasn't liked either, threw the error 'image size exceeds file limit'. I changed active partition from a to b and tried both commands, both of which presented the same issue. I even tried compressing the file down to 35mb and it still threw a fit. The TWRP file is only 48mb, what do I do? Further researching the issue is not bringing me much luck

there is no TWRP for Moto G Pure (yet) don't do stupid things

aIecxs said:
there is no TWRP for Moto G Pure (yet) don't do stupid things
Click to expand...
Click to collapse
So what should I do to start the rooting process? Do I use a different root program or… wait for support?? I was going to flash LOS as my custom rom too, I guess they don’t support moto g pure either then considering I downloaded a generic moto rom

MisterMilo said:
So what should I do to start the rooting process? Do I use a different root program or… wait for support?? I was going to flash LOS as my custom rom too, I guess they don’t support moto g pure either then considering I downloaded a generic moto rom
Click to expand...
Click to collapse
The stock rim is available at lollinet. I actually have a copy of it and have a magisk patched boot img. I think where your reaching the error is ( and I'm very new so feel free to correct me) the fastboot command. I think it's an a b partition. So it would be fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
MisterMilo said:
So what should I do to start the rooting process? Do I use a different root program or… wait for support?? I was going to flash LOS as my custom rom too, I guess they don’t support moto g pure either then considering I downloaded a generic moto rom
Click to expand...
Click to collapse

I rooted mine through magisk by just boot image didn't disable dm verity or vb meta I do have root but you can't flash twrp from any other moto g because the moto g pure has a mediatek Helios g25 chip (I think,definitely mediatek tho)and all the others have quallcom snapdragon chips that's why you can't flash twrp in fastboot mode it's crazy no one's compiled twrp yet for this device seeing how easy it is to root. If you need help rooting yours lmk.

bayjones742 said:
I rooted mine through magisk by just boot image didn't disable dm verity or vb meta I do have root but you can't flash twrp from any other moto g because the moto g pure has a mediatek Helios g25 chip (I think,definitely mediatek tho)and all the others have quallcom snapdragon chips that's why you can't flash twrp in fastboot mode it's crazy no one's compiled twrp yet for this device seeing how easy it is to root. If you need help rooting yours lmk.
Click to expand...
Click to collapse
I Wanna Root Mine, Can You Teach Me How???

ROBOOTO said:
I Wanna Root Mine, Can You Teach Me How???
Click to expand...
Click to collapse
Easy all you gotta do is download your rom/firmware you can easily do this through the Lenovo rescue tool once you download your rom/firmware just extract into a folder somewhere you can easily access oh that rescue tool will download the firmware into crogramData\RSA\Download\RomFiles I think even though it says it's in downloads folder at first I couldn't find it for like an hour but anyways once you find the rom just extract it into a folder somewhere you can easily access & take the boot.img and send it or a copy of it into your phone's internal storage after you do that just download magisk 25.2 you know the latest one from johnwu's GitHub page and install that on your phone and you know how the rest goes just go to install magisk select img to patch choose the boot.img you transferred onto your phone let magisk do it's thing once it's done you have to transfer it back into the rom files you extracted remember to rename it back to boot.img because magisk names it something else but once you put it back in it's folder with the rest of the roms files I can't remember if I zipped em back up or not but anyways take that whole file back to the folder where the rescue tool downloaded it CrogramData\RSA\Download\RomFile and just go and adb reboot your phone into bootloader mode and let the rescue tool flash your moto g pure but with the patched boot image and hahahahaha you done oh but you have to have an unlocked bootloader otherwise you can't flash ... boi! Oh btw you'll have root but I can't uninstall system apps can't mount mount system to rw and as far as I know there's no TWRP but use fox's magisk module manager and flash bootloop protector it save my butt couple times already don't flash Sony Bravia engine will cause bootloop idk if I could compile TWRP I would almost 10 years I been doing this ... and still haven't learned to do that...lol
{Mod edit: Inappropriate language iaw. rule no. 2 removed. Oswald Boelcke}

Hi I'm feeling your pain from not having rw with your root. Have you checked out lebigmac's make sysRW script? I had to do it to get RW on my Moto G Stylus 5G cuz Android 11. Looks like I'll have to do it again for this model. Any luck on getting TWRP?

Related

[MOTO G6+] Root guide from start (pro users)

Hi,
This guide is based on my experience with a Moto G6+ RETEU XT1926-3.
And it supersedes the explanations on this thread: https://forum.xda-developers.com/moto-g6/help/root-g6-t3786379
In any case is only for experienced users! If you like to create a more user friendly guide, then contribute to it!
GUIDE:
Boot for first time (don't use your gmail user, just skip all!). Enable "developer options". Set "OEM Unlocking". Set "USB debugging".
Get your Bootloader Unlock Key from Motorola: https://forum.xda-developers.com/moto-g6/how-to/guide-unlock-bootloader-t3791238
Connect to PC with USB and Accept the connection. In the PC Shell:
"adb reboot bootloader"; "fastboot oem unlock UNIQUE_KEY" (2 times); "fastboot reboot bootloader". Afer end check that all is OK!
Insert SD-Card, and check it works!
In the PC Shell:
"adb reboot bootloader"; "fastboot boot twrp-3.2.1-0-evert.img".
When the TWRP boots --> READ-ONLY mode! Inside "Mount" select "Micro SD card" and push button "Disable MTP". Open ADB shell.
WARNING: This TWRP is an unofficial version for Moto X4! Don't flash it!
Inside the ANDROID (ADB) shell:
"dd if=/dev/block/platform/soc/c0c4000.sdhci/by-name/boot of=/external_sd/boot.img"
"dd if=/dev/block/platform/soc/c0c4000.sdhci/by-name/logo of=/external_sd/logo.bin"
Power off, extract the SD-Card and secure copy your backup!
Power on in fastboot mode. Then flash patched logo.bin (for disable unlock warning), and flash boot patched kernel:
"fastboot flash logo logo.bin"
"fastboot boot patched_boot-MotoG6+-OPW27.113-45.img"
Reboot and make the initial setup with your regular user. Check that all is OK!
Before any reboot install MagiskManager:
https://github.com/topjohnwu/MagiskManager/releases
Upgrade to lasted Magisk Beta:
- Inside the Magisk Manager "Settings", change "Update Channel" to "Beta".
- Then in the Main Magisk select "install" and "Install" the last version (v16.7) with "Direct Install".
- Reboot.
That's all! Your phone is rooted with MagiskSU, and you can install Magisk Modules! :good:
If you boot with the patched boot kernel and install Magisk with the direct mode then you will have a backup of the stock boot.img inside Magisk. Useful for OTA updates and to uninstall it. In this case points 4-7 is not required (but recomended). The backup is stored in "/data/stock_boot_XXXXXXXXX.img.gz".
PENDING: Disable dm-verity (/data encryption) for TWRP backups!
GREETINGS:
@jekyll86 for Magisk patched kernel image https://forum.xda-developers.com/moto-g6/development/guide-magisk-patched-boot-image-opw27-t3794977
@luiz_neto for patched logo https://forum.xda-developers.com/moto-g6/development/bootlogo-remove-message-unlocked-t3789155
@luiz_neto for unofficial TWRP for Moto X4 https://forum.xda-developers.com/showpost.php?p=76501832&postcount=3
@lohanbarth for Unlock Bootloader guide https://forum.xda-developers.com/moto-g6/how-to/guide-unlock-bootloader-t3791238
root for the normal g6, still nothing? I would also like to know how the tea is decrypted, Thank you
Enviado desde mi moto g(6) mediante Tapatalk
stifmaster81 said:
root for the normal g6, still nothing? I would also like to know how the tea is decrypted, Thank you
Click to expand...
Click to collapse
No at time! I don't have any G6, only G6+ that it's a very different device.
Here an idea for any that have sufficient skills and one Moto G6:
- Search for a similar device with a custom recovery (TWRP).
- Try to boot this TWRP image (fastboot boot twrp.img).
- If it works, extract the kernel to boot.img using the shell of the TWRP.
- Use some Magisk Manager tool for repack/patch the extracted boot.img.
- Try to boot this kernel (fastboot boot patch_boot.img).
- If it works, then install the Magisk Manager and patch the flash kernel.
After that, you have rooted your device! Then extract then the patched kernel and share with others. The rest of the guide will be the same with this custom kernel.
manos78 said:
No at time! I don't have any G6, only G6+ that it's a very different device.
Here an idea for any that have sufficient skills and one Moto G6:
- Search for a similar device with a custom recovery (TWRP).
- Try to boot this TWRP image (fastboot boot twrp.img).
- If it works, extract the kernel to boot.img using the shell of the TWRP.
- Use some Magisk Manager tool for repack/patch the extracted boot.img.
- Try to boot this kernel (fastboot boot patch_boot.img).
- If it works, then install the Magisk Manager and patch the flash kernel.
After that, you have rooted your device! Then extract then the patched kernel and share with others. The rest of the guide will be the same with this custom kernel.
Click to expand...
Click to collapse
Very complicated for me, I'll wait to see if someone gets something out
Enviado desde mi moto g(6) mediante Tapatalk
---------- Post added at 02:40 PM ---------- Previous post was at 02:35 PM ----------
To decrypt the mobile, can something be done? By command line Nexus type or something?
Enviado desde mi moto g(6) mediante Tapatalk
What is this for? i rooted my g6+ just booting this twrp and normally flash magisk zip in recovery and that was it.
CreasingMass Dev said:
What is this for? i rooted my g6+ just booting this twrp and normally flash magisk zip in recovery and that was it.
Click to expand...
Click to collapse
Well, I do in this way because:
1) This TWRP isn't for Moto G6+, instead is for Moto X4. So, if it's something wrong in the partition mapping (fstab) then you can end with a bricked device. I'm satisfied if you can do it... but you be in risk.
2) If you review my guide, you will see how to obtain a BACKUP of the "boot.img". With your method, you'll lose it. And then, how you will apply the next OTA when it comes?
In any case, it's good to discover and test more rooting methods.
Perhaps for users with the Moto G6 or Moto G6 play, this other method can help them.
Regards.
manos78 said:
Well, I do in this way because:
1) This TWRP isn't for Moto G6+, instead is for Moto X4. So, if it's something wrong in the partition mapping (fstab) then you can end with a bricked device. I'm satisfied if you can do it... but you be in risk.
2) If you review my guide, you will see how to obtain a BACKUP of the "boot.img". With your method, you'll lose it. And then, how you will apply the next OTA when it comes?
In any case, it's good to discover and test more rooting methods.
Perhaps for users with the Moto G6 or Moto G6 play, this other method can help them.
Regards.
Click to expand...
Click to collapse
ye i don't care about OTAs, rooted my device just 30mins after getting it wishing there was some treble stuff but nah, anyway i don't care about losing that, i still use my g5 plus instead of this one because of the roms, can't use moto stock Sh!t it's just useless and full of bs
CreasingMass Dev said:
i still use my g5 plus instead of this one because of the roms, can't use moto stock Sh!t it's just useless and full of bs
Click to expand...
Click to collapse
Wooh! I really hate my Moto G5+ ... 3GB or RAM is a joke from Motorola. The 4GB of RAM of the Moto G6+ is a glory! And I prefer Oreo than Nougat, in Stock with a lot of Magisk modules.
FYI,
If you rooted your Moto G6+ with this guide, and now you like to apply the June's OTA over the April firmware... then, you need to wait!
The OTA refuses to install, even if you uninstall Magisk, or boot with the stock kernel, or reflash the stock kernel.
Have same issue....
I have a Moto G6.
When submitting the string on Motorola's site, I get this;
Your device does not qualify for bootloader unlocking
Any ideas how to get around this roadblock?
worried_G6 said:
I have a Moto G6.
When submitting the string on Motorola's site, I get this;
Your device does not qualify for bootloader unlocking
Any ideas how to get around this roadblock?
Click to expand...
Click to collapse
There is no way around it. if your device is branded from Verizon or probably AT&t the bootloader is not unlockable.

[GUIDE] [ELI5] [Root] [TWRP] [Moto E5] Root and TWRP for Moto E5 Play Explained

Explain It like I'm 5 - TWRP and Root for Moto E5 Play (and other E5 variants)
Step-by-Step explanation of the Root procedure found in @CodyF86 TWRP and Root thread for the Moto E5 Play
Because there are some entry-level users out there, I wanted to break down the steps for those of us who might not have as much experience in working with phones.
12/02/18 - THREAD UPDATE!
PLEASE READ BEFORE CONTINUING
Procedure should be safe for all E5 devices.
DO NOT FLASH ANY NO-VERITY KERNELS LISTED IN XDA
Expand for details...
This guide was originally written for James specific devices.
HOWEVER.. many have asked if this will work on their specific devices, and after answering questions and doing some brief research, I am convinced that this procedure SHOULD BE safe for ALL Moto E5 devices.
BEWARE.. The TWRP port provided for this procedure is not fully ported for the E5. I have confirmed flashing zip or image files, and making/restoring backups of boot, system and data are successful with James. These basic features of TWRP will work on all E5 phones, BUT this TWRP build will cause your phone to be identified as a PERRY device when checked by ROMs or flashable zips that do assert checks on the device name or id.
Prerequisites
ADB and Fastboot installed on PC
Motorola USB Drivers installed for your device
TWRP and fstab files from E5 Play Root / Recovery thread.
Latest Magisk
DISCLAIMER
Unlocking your bootloader is not for the faint of heart. Unlocking your device and installing your own software might cause the device to stop working, disable important features and functionality, and even make the device unsafe to the point of causing you harm. Neither Motorola, nor your wireless carrier or retailer from whom you purchased the device, will be responsible for such damage, so please do not unlock or load any software unless you know what you are doing.
You have only yourself to blame. Unless you have a Developer Edition device, once you get the unlock code, your device is no longer covered by the Motorola warranty; in other words, please don't blame us if things go wrong, even if they appear unrelated to unlocking the bootloader.
The law still applies. You still need to operate your device in compliance with all applicable laws, rules and regulations prescribed by the FCC, and any other governmental agency for that matter. Your wireless carrier may prohibit unlocked devices from operating on their network.
Steps from Stock Device
1 - Unlock Bootloader
Procedure
Enable Developer Options on your Device (Settings -> About Device -> Software -> Tap Build No. until Dev. Options are enabled.
Enable USB Debugging under Developer Options.
Enable OEM Unlock under Dev Options
Follow the Motorola Bootloader Unlock Prodecure on Motorola's Customer Support Portal
2 - Flash TWRP
DISCLAIMER
This process will overwrite your recovery partition. It is wise to make a complete nandroid backup of your device prior to performing any of the steps below.
Procedure
Download Magisk zip package, TWRP 3.2.1 E5 Play and fstab.qcom files from the E5 Play Root Recovery thread.
Put these 3 files in your adb/fastboot directory on your pc
With your phone on and booted to android, connect to your PC using your USB cable.
Open Command Prompt and cd to your ADB/Fastboot directory
run "adb devices" to make sure your device is connected to adb (you will need to approve the initial connection on your device)
manually copy twrp_james.img to your phone's external sd card or
Code:
adb push twrp_james.img /sdcard/
run "adb reboot bootloader" to reboot to fastboot mode
boot directly to TWRP with
Code:
fastboot boot twrp_james.img
make a full backup and store the backup on your phone's external sd card or transfer to your PC.
in TWRP, Reboot->Reboot Bootloader
When back in fastboot mode, flash TWRP to your recovery partition.
Code:
fastboot flash recovery twrp_james.img
fastboot reboot recovery
your phone should reboot to TWRP now on your recovery partition.
3 - Disable Force-Encryption and Root device with Magisk
Procedure
while in TWRP, run the following in your ADB terminal
Code:
adb shell mount -o,rw /dev/block/bootdevice/by-name/vendor /vendor
adb push fstab.qcom /vendor/etc/fstab.qcom
from TWRP menu: Wipe-> Format Data
copy magisk zip to newly formatted data partition
Code:
adb push Magisk-v17.2.zip /sdcard/
From TWRP, Install Magisk zip
You now are rooted and have TWRP on your Recovery partition. After rebooting to Android, make sure you install the latest Magisk Manager first thing.
Great tutorial. Worked like a charm on my James.
Thanks for posting this. Ive been rooting and messing with phones for years but never really got comfortable with adb and fastboot commands and the other post makes no mention of unlocking the bootloader even though it was obvious i needed to. I considered doing it this way same way i unlocked my e4 Qualcomm but wasn't 100% sure that was what was needed until i read this. Very easy to follow guide that ensures i didn't miss anything.
AesopRock127 said:
Thanks for posting this. Ive been rooting and messing with phones for years but never really got comfortable with adb and fastboot commands and the other post makes no mention of unlocking the bootloader even though it was obvious i needed to. I considered doing it this way same way i unlocked my e4 Qualcomm but wasn't 100% sure that was what was needed until i read this. Very easy to follow guide that ensures i didn't miss anything.
Click to expand...
Click to collapse
My pleasure. Thank you very much. I'm happy to help.
Working like a charm on my Moto E5 PLAY XT1920-16
HI,
After a few attempts i've managed to root my Moto E5 PLAY XT1920-16. I did not flashed twrp_james.img (boot error) just boot directly to TWRP (fastboot boot twrp_james.img) and followed the instructions from step 3. Flashed boot logo from here to "hide" N/A, Bad Key message.
Thanks for this, as it's easy to understand and follow - especially the ADB in TWRP for FSTAB which I previously messed up and got into all sorts of horrible boot loops / errors and had to run away and hide for 36 hours as my wife threatened to chop off something if she heard me scream "B*******" one more time.
No drama this time, it just worked :laugh:
Will this work on a regular E5?
diaconu.silviu said:
HI,
After a few attempts i've managed to root my Moto E5 PLAY XT1920-16. I did not flashed twrp_james.img (boot error) just boot directly to TWRP (fastboot boot twrp_james.img) and followed the instructions from step 3. Flashed boot logo from here to "hide" N/A, Bad Key message.
Click to expand...
Click to collapse
Thanks for this! I've been trying to figure out how to hide the N/A forever on this phone
bubba1601 said:
Thanks for this, as it's easy to understand and follow - especially the ADB in TWRP for FSTAB which I previously messed up and got into all sorts of horrible boot loops / errors and had to run away and hide for 36 hours as my wife threatened to chop off something if she heard me scream "B*******" one more time.
No drama this time, it just worked :laugh:
Click to expand...
Click to collapse
Awesome lol. Thanks for your comment
Slavois said:
Will this work on a regular E5?
Click to expand...
Click to collapse
TWRP version excluded, yes, it should. First make sure you get a TWRP image that is compatible with E5 model you are working with. I wouldn't use the twrp_james.img file linked in this thread if you dont have a james device. I dont know if the regular E5 is james, nora or rhannah. You should have information related to this on your fastboot screen.
If I recall correctly, the fstab.qcom file linked in this thread, which is needed to disable encryption, should work on your phone. There was another member who used it on their E5 Plus without issue.
weakNPCdotCom said:
TWRP version excluded, yes, it should. First make sure you get a TWRP image that is compatible with E5 model you are working with. I wouldn't use the twrp_james.img file linked in this thread if you dont have a james device. I dont know if the regular E5 is james, nora or rhannah. You should have information related to this on your fastboot screen.
If I recall correctly, the fstab.qcom file linked in this thread, which is needed to disable encryption, should work on your phone. There was another member who used it on their E5 Plus without issue.
Click to expand...
Click to collapse
Also a warning about twrp.....
I'm using the XT1920-15 E5 play (PETTYL) and the alleged twrp version for that device (not available here on XDA) doesn't work on that device.
The James version works on PETTYL.
There's two or three E5 play and plus twrp versions floating around here, just a heads up for users to be cautious.....
bubba1601 said:
There's two or three E5 play and plus twrp versions floating around here, just a heads up for users to be cautious.....
Click to expand...
Click to collapse
I would love a TWRP build for this phone that supports backups for all the major partitions and not just basic system/data/cache
Would also be nice if it could wipe lock screen security.
If I knew how to port twrp I would build some
Error msg.
When I run this command I get the following message below. I used both command prompt and powershell. Powershell gives me that error message while command prompt just goes through, but it doesnt give me any confirmation. What must I do?
PS C:\Users\Lit\Desktop\Moto E5 play root> adb shell mount -o,rw /dev/block/bootdevice/by-name/vendor /vendor
Error msg:
At line:1 char:19
+ adb shell mount -o,rw /dev/block/bootdevice/by-name/vendor /vendor
+ ~
Missing argument in parameter list.
+ CategoryInfo : ParserError: ) [], ParentContainsErrorRecordException
+ FullyQualifiedErrorId : MissingArgument
Im using moto e5 play for TMobile xt1921-3 and was wondering if someone can point me in the right direction for twrp installation? And the proper img file? The one I flashed, twrp_james.img, stuck for like a day but now its gone?? Wat am i doin wrong?
Swagnutz34 said:
Im using moto e5 play for TMobile xt1921-3 and was wondering if someone can point me in the right direction for twrp installation? And the proper img file? The one I flashed, twrp_james.img, stuck for like a day but now its gone?? Wat am i doin wrong?
Click to expand...
Click to collapse
If you follow these directions in the op exactly you will be fine and twrp will stick after you boot. The twrp linked here in the op is the one. I used it and I have same exact device as you, same model and all. From my experience tinkering with it you gotta decrypt for twrp to stay. Otherwise if you wanna stay encryted you just use fastboot and fastboot boot twrp.img from your computer every time you use recovery. Hope that helps.
Sent from my XT1921-3
SM210 said:
If you follow these directions in the op exactly you will be fine and twrp will stick after you boot. The twrp linked here in the op is the one. I used it and I have same exact device as you, same model and all. From my experience tinkering with it you gotta decrypt for twrp to stay. Otherwise if you wanna stay encryted you just use fastboot and fastboot boot twrp.img from your computer every time you use recovery. Hope that helps.
Click to expand...
Click to collapse
I got twrp to stick but cant back up data? N magisk flashed no problem....here are some screenshots. Im tryin to flash lineage rom n im gettin no where lol. Sorry im a noob!
Swagnutz34 said:
I got twrp to stick but cant back up data? N magisk flashed no problem....here are some screenshots. Im tryin to flash lineage rom n im gettin no where lol. Sorry im a noob!
Click to expand...
Click to collapse
As 1st post states: see my screenshot attached from the original post... Follow that exactly
then flash magisk 17.2 zip in twrp recovery and reboot and you then can see your data partition in recovery and twrp will hold perminately.
Hope that helps. Always read up alot , I always try to. As specially these days. TONS of new things to learn. Hope that helps. Cheers.
Sent from my james using XDA Labs
for some reason i can flash the hannah twrp 3.2.3 for my moto e5 plus and i can boot intp twp recovery. i made a back up and now its just stuck on the start up loop. and when i get to the adb part of this tutorial i cant push none of the files using the sideload option in twrp so i can decrypt twrp.
Failed at 'fastboot reboot recovery' with the following:
rebooting into recovery FAILED (remote: 'Unknown command')
Continued from step 3 after bring it back to TWRP as [email protected] suggested. However, did not get root. Any suggestions what to try next? The device is XT1921-2.
Thanks!
Hi! I have the xt1920-18 version and TWRP doesn't recognize touch. In case anyone else has this problem, I used the mouse with OTG and it works perfect.Hi! I have the xt1920-18 version and TWRP doesn't recognize touch. In case anyone else has this problem, I used the mouse with OTG and it works perfectly.

I tried rooting RMX2040

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

Infinix hot 10 play (X688B) stuck bootlooping to fastboot after orange state, help

i recently rooted my phone with magisk patched boot image and was working good after i restored my files, then it rebooted itself and now its stuck on orange state then going to fastboot mode, after that it loops back to orange state over and over again, please help
Reflash phone's Stock ROM to get rid off of all modifications you applied so far.
and what if i want to root the phone? flashing the stock rom gets rid of magisk, am i stuck without an option to root it? or should i install a custom recovery or cus os like calyxos?
new problem, i cant flash the stock rom using sp flash tool, gives me this weird error:
STATUS_BROM_CMD_STARTCMD_FAIL
any help?
I did this to my old phone if sp flash ain't working
"fasboot flash all slot a". if a/b partition
"fastboot flash all". if not a/b partition
and I feel like this method is faster than sp flash tool
edit:
lucky you could go to fastboot unlike mine can't go anywhere when I tried to flash my device it just reboot after 6 or 5 seconds ;-;
Does somebody have the stock rom for Infinix Hot 10 Play X688B?
There is the builder number X688B-H659ABCEFGHI-Q-GL-220109V524
Tzuyoda said:
Does somebody have the stock rom for Infinix Hot 10 Play X688B?
There is the builder number X688B-H659ABCEFGHI-Q-GL-220109V524
Click to expand...
Click to collapse
Download Infinix Stock ROM for all models (Latest Firmware)
Download the latest Infinix Stock ROM Firmware (Flash File) for all the available Infinix smartphones, feature phones, and tablets.
androidmtk.com
I could only find this one site that has all of the stock roms of XOS. Not exactly the model number. Just a 'c' and 'b' difference
Did you fix it? If not I can help you
I think the stock roms would work.
boomzkik said:
Did you fix it? If not I can help you
Click to expand...
Click to collapse
do you have the latest firmware files? i removed root and updated ota and i cant find any source of firmwares online, only the stock ones. can i use stock boot.img and patch it with magisk then install the patched stock boot.img with fastboot on an updated firmware?
mlgpro12345 said:
i recently rooted my phone with magisk patched boot image and was working good after i restored my files, then it rebooted itself and now its stuck on orange state then going to fastboot mode, after that it loops back to orange state over and over again, please help
Click to expand...
Click to collapse
Please I need your help on how you were able to root your infinix hot 10. I have the same phone and I was following YouTube tutorials they told me to use minimal adb and fastboot.. all the commands worked great but when I use command fastboot flash boot and paste my patched boot img it shows error... Unknown partition cannot determine image filename for boot img or so.

Question How to unbrick One Plus Nord CE 2 Lite ?

I have bricked this device (One Plus Nord CE 2 Lite) by flashing the unofficial twrp image for this device. Device bootloops in TWRP.
Previously, I had succesfully unlocked the bootloader and rooted this device by flashing the patched magisk boot.img by following the method mentioned in this post (https://forum.xda-developers.com/t/rooting-oneplus-nord-2-ce-lite.4500297/)
How to restore the factory image and recover from this?
Any help is appreciated.
Thanks
...reboot to fastboot, flash the original boot and vbmeta and you're done ...maybe you have to change back the slot, but it's almost impossible to brick the device
...don't mess around with "Recovery" ...this device has already the newest partitioning system and there is no recovery partition
best regards
I messed up by flashing the wrong twrp image made. (Device was stuck on 1+ logo screen)
Thanks to your post i was able to rescue this device.
I used Oxygen Updater App, payload-dumper-gui and minimal adb fastboot.
Flashed boot and vbmeta with stock img files.
Restarting the device now will boot into fastboot mode.
Changing slots helped a lot.
(fastboot set-active=a/b)
After that, Device booted normally into OS.
... you're very welcome, Sir ...but really, don't mess around with "old school" recovery systems ...they are not needed anymore and furthermore they can't handle the "dynamic super partitioning" ...and again: nobody needs them after the year 2015 anymore
...best regards
NickR01 said:
I messed up by flashing the wrong twrp image made. (Device was stuck on 1+ logo screen)
Thanks to your post i was able to rescue this device.
I used Oxygen Updater App, payload-dumper-gui and minimal adb fastboot.
Flashed boot and vbmeta with stock img files.
Restarting the device now will boot into fastboot mode.
Changing slots helped a lot.
(fastboot set-active=a/b)
After that, Device booted normally into OS.
Click to expand...
Click to collapse
Hey can you help me pls, I am in the exact same situation as you but I can't get the stock img files, whenever I use payload-dumper it just gives me system.img and nothing else, could you maybe share your img files ?
Edit: I manged to get some files but still not the boot.img, I don't undestand why it just refuses to give them to me, I redownloaded everything at least 3 times...
Use Payload-Dumper-GUI instead of Payload-Dumper-Go
Hey @NickR01 if possible can you send me an boot.img and vbmeta
I don’t have windows pc so can’t use Payload-Dumper
It will also help future users to unbrick device.
NickR01 said:
Use Payload-Dumper-GUI instead of Payload-Dumper-Go
Click to expand...
Click to collapse
@vikas_anakin What's your device version?
cph2381 cph2409
NickR01 said:
@vikas_anakin What's your device version?
cph2381 cph2409
Click to expand...
Click to collapse
cph2381
@vikas_anakin I have files for eu variant, can't help you there bud. If flashed it can mess up your device.
If you are stuck with payload.bin extraction... try it with an android device.
Here's the tool for Android.
Payload-Dumper-Android
Here's the guide for it.
XDA Guide
Newb Guide
Follow the guide and download this app to extract the .bin file
Termux App: Termux Github
After the extraction, type fastboot (pc required) commands to flash and change current active slots from A to B if it's stuck in bootloop after flashing.
I hope this helps you recover your device.
NickR01 said:
@vikas_anakin I have files for eu variant, can't help you there bud. If flashed it can mess up your device.
If you are stuck with payload.bin extraction... try it with an android device.
Here's the tool for Android.
Payload-Dumper-Android
Here's the guide for it.
XDA Guide
Newb Guide
Follow the guide and download this app to extract the .bin file
Termux App: Termux Github
After the extraction, type fastboot (pc required) commands to flash and change current active slots from A to B if it's stuck in bootloop after flashing.
I hope this helps you recover your device.
Click to expand...
Click to collapse
Extracting the payload.bin is not an issue, The issue is I don't have stock firmware.
I used https://www.getdroidtips.com/oneplus-nord-ce-2-lite-5g-firmware-flash-file/ but my wifi and Bluetooth are not working after installing it.
Do you have any suggestions on how can i resolve these issues?
@vikas_anakin Download authentic firmware from this app. Files are pulled from OnePlus servers.
Google Playstore: Oxygen Updater
Oxygen Updater Settings -> Enable Advanced Mode
Select device region.
Latest update for holi is CPH2381_11_A.13 as of now.
I extracted the images from the payload.bin found in the Oxygen Updater file (that I had actually successfully used to update my device) and flashed 2 partitions:
fastboot flash vbmeta vbmeta.img
fastboot flash boot boot.img
I then rebooted and now it's stuck in a boot loop & I can't even access fastboot anymore. Can someone please help?
Thanks
EDIT:
I managed to access fastboot & flash the rest of the partitions to fix it.
Hi everyone, just to piggy back on this thread, I also have the same device, and I have unofficial twrp and boot loader unlocked, however I have no back up rom and just want to get the phone back to normal really. Ive been following guides all over the place, but could someone point me in the right direction ? can I just download a rom for the OP nord ce 2 lite 5g, put it on my phone and have twrp install it? could someone guide me please. many thanks!
lemonmuffs said:
Hi everyone, just to piggy back on this thread, I also have the same device, and I have unofficial twrp and boot loader unlocked, however I have no back up rom and just want to get the phone back to normal really. Ive been following guides all over the place, but could someone point me in the right direction ? can I just download a rom for the OP nord ce 2 lite 5g, put it on my phone and have twrp install it? could someone guide me please. many thanks!
Click to expand...
Click to collapse
Yes, that will work.
vikas_anakin said:
Yes, that will work.
Click to expand...
Click to collapse
Or else you can extract img files from the oneplus rom file.
and flash them using fastboot.
Okay thank you for the reply, would you be able to point me to a official img file ? Or maybe someone has one extracted I could use please? I have looked online, but the ones I have gotten don't seem to work. I have also looked on the oneplus website for an official img but I could not find one.
So after a little more research, I can use another android device with the app Oxygen updater, download the full img.... So I am currently doing that and then ill try use fastboot or twrp to flash. Just wanted to spread info incase anyone else is having issues getting latest official roms for this device.
Hey guys, i have bricked my Oneplus Nord ce 2 lite 5g (Cph2381)
I tried using the fastboot enhance tool to flash a payload.bin file i thought was the right one for the device ..the device went to blackscreen..ive tried switching it on but its not working..ive done alittle research and found out that i should use an msm tool to force flash the initial stock firmware so that it can boot up ...problem is i cant seem to find the right msm tool for Oneplus nord ce 2 lite 5g , which msm tool can i use ? help please
Jazzyjuis said:
Hey guys, i have bricked my Oneplus Nord ce 2 lite 5g (Cph2381)
I tried using the fastboot enhance tool to flash a payload.bin file i thought was the right one for the device ..the device went to blackscreen..ive tried switching it on but its not working..ive done alittle research and found out that i should use an msm tool to force flash the initial stock firmware so that it can boot up ...problem is i cant seem to find the right msm tool for Oneplus nord ce 2 lite 5g , which msm tool can i use ? help please
Click to expand...
Click to collapse
Hey man, I would suggest not going with msm tool or anything.
Just download the latest update file of your device using oneplus updater app, or you can ask for the file if some of your friends has the same device.
use this tool to extract payload files https://github.com/vm03/payload_dumper
Now you can follow the same procedure as here https://forum.xda-developers.com/t/...ock-oxygenos-firmware-on-oneplus-10r.4465077/

Categories

Resources