Database Info

flashed wrong bootloader

Idk what to do I flashed the wrong bootloader on my S7 (snapdragon) through flashfire and now I get a black screen with a blue LED with a green LED slowly blinking behind it. How to recover? Right now I'm just letting it die. Can't hard reset either.

rifek4 said:
Do a download mode is working for you?
Click to expand...
Click to collapse
Nope. Sadly. I get no response from the phone whatsoever. I heard a USB jig can fix this but i need to make sure before i buy..

savagevegeta said:
Nope. Sadly. I get no response from the phone whatsoever. I heard a USB jig can fix this but i need to make sure before i buy..
Click to expand...
Click to collapse
USB jig doesn't work on the S7, got one here
Probably gonna have to take it somewhere for repair unless there is a program similar to SP Flash Tool (Smart Phone Flash Tool) which can flash a seemingly dead device, for the S7

*Detection* said:
USB jig doesn't work on the S7, got one here
Probably gonna have to take it somewhere for repair unless there is a program similar to SP Flash Tool (Smart Phone Flash Tool) which can flash a seemingly dead device, for the S7
Click to expand...
Click to collapse
Even a completely dead one? I don't want to have to buy a replacement motherboard, but it looks like i HAVE to. I was counting on the usb jig working, but i guess not. Not even my PC can recognize it. When i plug it it, nothing happens. Do you know of anyway i can revive it?

savagevegeta said:
Even a completely dead one? I don't want to have to buy a replacement motherboard, but it looks like i HAVE to. I was counting on the usb jig working, but i guess not. Not even my PC can recognize it. When i plug it it, nothing happens. Do you know of anyway i can revive it?
Click to expand...
Click to collapse
It's not dead, you just can't boot it because of whatever you did to it, hardware is still OK more than likely
That flash tool I was talking about just needs the device to have power, not sure exactly how it works but it can flash without being in any download mode for the devices it was designed for
If I knew of a way for you to revive it I would have suggested it in my first reply
Possibly a Linux machine and some shell commands could push a new BL to it, but that's above my knowledge
Basically you managed to kill it with software, so in theory it should be repairable without replacing hardware, but you're gonna need the right tools, and likely only a repair shop would have them
EDIT - And I just realised it's the Snapdragon S7, so the bootloader is locked, making it even more difficult

*Detection* said:
It's not dead, you just can't boot it because of whatever you did to it, hardware is still OK more than likely
That flash tool I was talking about just needs the device to have power, not sure exactly how it works but it can flash without being in any download mode for the devices it was designed for
If I knew of a way for you to revive it I would have suggested it in my first reply
Possibly a Linux machine and some shell commands could push a new BL to it, but that's above my knowledge
Basically you managed to kill it with software, so in theory it should be repairable without replacing hardware, but you're gonna need the right tools, and likely only a repair shop would have them
EDIT - And I just realised it's the Snapdragon S7, so the bootloader is locked, making it even more difficult
Click to expand...
Click to collapse
I am open to suggestions on what tools i may use. Im trying the flash tool as soon as i get home.
I tried to downgrade using flashfire after rooting the device but it failed and thats why it's dead.
At first it was just a blue light with a green one blinking behind it, but i let it die over night in hopes of being able to recover it in the morning. Now, there isnt even the light.
The battery isnt dead according to my multimeter.
While the bootloader is locked, it HAD engineerboot so maybe that allows something. :/
I would have taken it to a repair shop but the closest one knows nothing about software issues and only suggest hardware repairs, hence me wanting to replace the motherboard.
I'm going to search how to fix it with linux since i have a linux machine, i just have no experience with it at all. At least pushing the bootloader will help an awful lot. If you have any knowledge on any of these, even the slightest, do share. Ill do some research meanwhile and if i find a fix, I'll post it. This phone was so good and i miss it dearly, which is why i need all the help and research i can get.
Apparently no one has ever bricked the snapdragon version of this phone, given the lack of any google results similar to this situation on this phone. ;-;

*Detection* said:
It's not dead, you just can't boot it because of whatever you did to it, hardware is still OK more than likely
That flash tool I was talking about just needs the device to have power, not sure exactly how it works but it can flash without being in any download mode for the devices it was designed for
If I knew of a way for you to revive it I would have suggested it in my first reply
Possibly a Linux machine and some shell commands could push a new BL to it, but that's above my knowledge
Basically you managed to kill it with software, so in theory it should be repairable without replacing hardware, but you're gonna need the right tools, and likely only a repair shop would have them
EDIT - And I just realised it's the Snapdragon S7, so the bootloader is locked, making it even more difficult
Click to expand...
Click to collapse
Its in QUSB_BULK now. At least the computer SEES it

savagevegeta said:
Its in QUSB_BULK now. At least the computer SEES it
Click to expand...
Click to collapse
Yea seems to be as suspected, here is a different device with same QUSB ID, and the fix is as I suggested using adb and different flash tools to push the correct files to the device
https://xiaomi.eu/community/threads/sudden-death-or-hardbrick.36285/#post-334687
http://www.androidbrick.com/xiaomi-mi5-how-to-flash-global-multilanguage-rom-unbrick-guide/
This is not for the S7 though, so don't copy it or use their tools, but it will give you a general idea of what the process would be if you had the correct files and flash tools available
---------- Post added at 22:51 ---------- Previous post was at 22:25 ----------
Not sure how to enable the bootloader update function, if it will enable once you load firmware into the sections on the right, but try ODIN 3.12.10
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
---------- Post added at 22:53 ---------- Previous post was at 22:51 ----------
https://forum.xda-developers.com/showthread.php?t=2711451

*Detection* said:
Yea seems to be as suspected, here is a different device with same QUSB ID, and the fix is as I suggested using adb and different flash tools to push the correct files to the device
https://xiaomi.eu/community/threads/sudden-death-or-hardbrick.36285/#post-334687
http://www.androidbrick.com/xiaomi-mi5-how-to-flash-global-multilanguage-rom-unbrick-guide/
This is not for the S7 though, so don't copy it or use their tools, but it will give you a general idea of what the process would be if you had the correct files and flash tools available
Click to expand...
Click to collapse
Thanks for researching this. It did give me an idea, but it sucks that there is no tools for samsung devices stuck in QHSUSB_BULK mode. I found a guide that allows me to flash a PIT file and the bootloader file onto an SD card, and then insert it into the bricked S7, but that process requires a second S7 to flash the files onto. I tried flashing the boot.img and recovery.img onto the SD and hoping for the best, but still no luck. I'm looking for other methods. I saw on youtube that some guy used a program to flash an unbrick.img onto an SD, and that got it to go into download mode, but the tool he used was S5 specific and the video was a guide for the S5

savagevegeta said:
Thanks for researching this. It did give me an idea, but it sucks that there is no tools for samsung devices stuck in QHSUSB_BULK mode. I found a guide that allows me to flash a PIT file and the bootloader file onto an SD card, and then insert it into the bricked S7, but that process requires a second S7 to flash the files onto. I tried flashing the boot.img and recovery.img onto the SD and hoping for the best, but still no luck. I'm looking for other methods. I saw on youtube that some guy used a program to flash an unbrick.img onto an SD, and that got it to go into download mode, but the tool he used was S5 specific and the video was a guide for the S5
Click to expand...
Click to collapse
Yea I know about the one for the S5, that was my phone before the S7, maybe PM that dev (He's from XDA) on the S5 forums and see if he could help you out?

Vortex SYNQ Dev Thread (TWRP Image & Bootloader Unlock!!!)

During our quest to gain root on the ANS UL40, @Matthew702 and I went a bit off topic and started messing with his Vortex Synq he picked up. 'Thew was able to find a method to unlock the bootloader, which I will post here shortly, and we shortly thereafter found out that the device is "vulnerable" to using SPFT--as in the VCOM port stays open and allows us to read/write partition images directly from the emmc.
UPDATE: We now have enough people to really get the ball rolling for some development for this phone, so as we accomplish more things we'll post them here

Anything you try from here, you do so at your own risk. This may void your warranty, break your device, etc.
HOW TO UNLOCK THE BOOTLOADER
Go to Settings>About Phone>Build Number and tap this a lot really fast to enable developer mode
Go to the new developer mode option in the Settings menu, check the switch that says Allow OEM Unlock
Plug your phone into your computer, enable ADB Debugging, open up a terminal on your computer, and initiate an "adb reboot fastboot" to put the device into fastboot mode
In your computer terminal again, type in "fastboot oem unlock". If it fails, run it again. If it fails again, reboot to fastboot one more time and try a couple more times. Eventually it should work after a couple tries, it did for us
Confirm the device unlock on the phone (pressing volume up at the prompt I believe), and wait for the phone to reboot. Note that it's not stuck in a bootloop at this point, it's just factory resetting after the unlock, so give it time to work
HOW WE WANT TO ROOT IT (NOT DONE YET): METHOD 1
Pull a recovery image from the phone with SPFT using a proper mtk6739 scatter file which I can't exactly find
Port TWRP to the phone from another device's mtk6739 TWRP image with carliv image kitchen tool, and flash it back to the phone with SPFT
Flash Magisk in TWRP, reboot, profit
HOW WE WANT TO ROOT IT (NOT DONE YET): METHOD 2
Pull a boot image with SPFT
Use the Magisk APK to inject magisk into the boot image
Flash the boot image back with SPFT (or maybe fastboot), reboot, profit
HOW TO FLASH TWRP TO THE PHONE (STILL EXPERIMENTAL)
Download the TWRP image from here
Reboot to the bootloader
Assuming you unlocked the bootloader from before, just do "fastboot flash recovery [imagename]" to get it on there
If fastboot complains about it not being able to flash, try running the command one more time
CUSTOM ROMS FOR THIS PHONE
This phone came with 8.1 Oreo, so that means it has to be Treble enabled. I'm no expert with Treble stuff but I believe GSIs made for arm a-only partitions SHOULD work on here. We haven't tested this for ourselves yet though
Like mentioned before, feel free to drop by and leave a message if you're willing to help us out on our endeavors. I also want to try and get 'Thew a working recovery on his phone again if possible, since for some reason when we try to flash back the image we pulled (with our "best guess" mt6739 scatter file) it didn't work

i might have one.. i will check as soon as i get to the shop

jasonmerc said:
During our quest to gain root on the ANS UL40, @Matthew702 and I went a bit off topic and started messing with his Vortex Synq he picked up. 'Thew was able to find a method to unlock the bootloader, which I will post here shortly, and we shortly thereafter found out that the device is "vulnerable" to using SPFT--as in the VCOM port stays open and allows us to read/write partition images directly from the emmc.
Unfortunately during our testing, he seems to have messed up his recovery image and is unable to restore a stock one on there. If there's any other owners out there willing to help us out (and maybe willing to risk their device for some test builds of TWRP too) I beseech thee to make yourself known.
Click to expand...
Click to collapse
i have one .. if you need

desbloqueokings said:
i have one .. if you need
Click to expand...
Click to collapse
Check your PMs on here, just sent you something

So the other 6739 scatter files we found didn't exactly work for this phone, so we pulled our own with a tool we found on Hovatek. This isn't a "port" from another phone, this directly came from the Synq itself.
Give major thanks to @desbloqueokings for pulling this for us!

The group we had seems a bit inactive now, so I'll post my new creations up here for all you guys here to test and tell us all if it works or not. One is a patched boot image that contains Magisk, all you'd need to do for that is flash the boot image and install a Magisk APK and you should be good to go for root. The other is a dirty port of TWRP Recovery I did from another MT6739 phone. It was hard finding an image to port from, so I want to give a huge thanks to @lopestom who sent me a 6739 image he had that I could port from
PLEASE BE AWARE THAT THESE ARE TEST IMAGES. I DONT HAVE THIS PHONE MYSELF AND CANT TEST IT MYSELF, SO IM NOT SURE IF THESE WILL WORK OR NOT. PLEASE MAKE A BACKUP OF YOUR CURRENT BOOT & RECOVERY IMAGES WITH SPFT USING THE SCATTER FILE ABOVE BEFORE TRYING ANY OF THIS. WHAT YOU DO TO YOUR OWN PHONE IS YOUR OWN RESPONSIBILITY. WHILE I WILL TRY TO HELP YOU IF SOMETHING BREAKS, IM NOT RESPONSIBLE FOR WHAT YOU CHOOSE TO DO
With that being said, here's the Mega folder containing the boot and recovery images. You can either flash these through SPFT like most people do with mediatek phones, or through fastboot, whatever you can get working. I'd also recommend you unlock your bootloader using the method posted above before doing any of this
Let me know if this stuff works or not, if you choose to flash it

Our victory was bittersweet, but a victory nonetheless
We got a working recovery image from @lopestom that seems to work fine on the surface, but when we need to flash the zip that disables dm-verity (disables force encryption) it supposedly breaks the /system partition on the stock ROM. My recommendation would be to take a backup of your /system directory in recovery before trying to flash anything. But since this is a Treble-enabled device, that means GSI ROMs could also work when flashed.
Here's a link to the recovery image we were using. We flashed it in fastboot with an unlocked bootloader but I imagine it would work just fine in SPFT too. I was told by the person that made the image that it's apparently not a good idea to flash the disable-force-encryption zip on a dirty port of a TWRP image like this (and to also never wipe /data). While you should be able to use this TWRP to flash something like Magisk, don't do those other two things for now.
Here's some screenshots from @Matthew702 to show the phone booting to TWRP (we made the mistake of trying to wipe /data and trying to flash the disable-encryption zip, please do not do this):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Thank you!

You guys are amazing.
I had a SYNQ just laying around taking up space. Now it is not totally useless. Anyway i wanted to say thanks and post some proof of concept.
Sorry for the horrible quality...
So i used the recovery image named “recoverytest3.img” if im not mistaken. Once that was complete (And i figured i messed everything up because i had a dead android guy every other time....) To my surprise TWRP popped up in russian. At that point i installed magisk manager and downloaded the most recent package then rebooted to recovery and flashed the pack.
NOTES - I did use Command line WIN 10 via the platform tools package your provided for the whole process.... If you don’t know russian or whatever lang TWRP happens to be in just good. Anyway im sure im missing some data i should add but i am dog tired and having trouble reading the phone.
night all and i hope it all goes well for everyone else.
xAlimorAx

xAlimorAx said:
I had a SYNQ just laying around taking up space. Now it is not totally useless. Anyway i wanted to say thanks and post some proof of concept.
Sorry for the horrible quality...
So i used the recovery image named “recoverytest3.img” if im not mistaken. Once that was complete (And i figured i messed everything up because i had a dead android guy every other time....) To my surprise TWRP popped up in russian. At that point i installed magisk manager and downloaded the most recent package then rebooted to recovery and flashed the pack.
NOTES - I did use Command line WIN 10 via the platform tools package your provided for the whole process.... If you don’t know russian or whatever lang TWRP happens to be in just good. Anyway im sure im missing some data i should add but i am dog tired and having trouble reading the phone.
night all and i hope it all goes well for everyone else.
xAlimorAx
Click to expand...
Click to collapse
Yeah it showed up in Russian for our tester too. Not sure why it does that, but otherwise it should still work fine

Need your assistance
Season greetings to you my friend, I ended up formatting my vortex synq using Sp flash tool, after attempting to root, now I have black screen only vcom for sp flash tool works but I need preloaded files and others to unbrick, it was gonna be a Xmas gift for my aunt, but I messed it up, wont turn on just vcom when connected to PC, I have the files stckboot and recovery but sp tool needs pre-loader error, plz help me

Please back up vortex synq
Good I ask for a help to see if someone will have or could make a back up for this vortex synq cell phone since some of us have problems in the firmware when modifying it and we do not have a previous backup if someone can collaborate, it would be infinitely appreciated.

I know this post is old but if somebody can backup the firmware from this it would be awesome, because i am trying to restore my vortex snyq (its hard bricked) but i can't find the preloader for this phone anywhere, when i tried to flash the preloader with sp flash tool it gives me this: STATUS_DA_HASH_MISMATCH, the preloader has to match this phone, if anyone has a backup of the firmware feel free to post it here or dm me, but yeah just wanted to post here.

also need firmware having the same issue ages now
any help much appreciated
safe 2021-2022

use this to unlock bootloader and backup fw https://github.com/bkerler/mtkclient

Making this post to do a dump of the Vortex Synq stuff I had on Mega. XDA allows us to upload large files to here now, and my Mega account is getting pretty full, so I want to transfer everything I have that's Vortex Synq related from there to here. That means any download links pointing to my Mega will be broken, but all of that stuff previously linked by me can be found in this zip.
disclaimer
Feel free to use any of my stuff in any way you see fit. The only thing I ask is that if you do improve on something, share it with everyone else and don't just keep it for yourself. Keep it going for the good of the community/public.
Also, know that it's been a long time since I've messed with this phone, so I don't remember what mods/images/etc in my Mega repo are functional or not. Anything contained within this zip, FLASH AT YOUR OWN RISK.
/disclaimer

[CLOSED] Delete Thread.

Due to the disrespect of certain members I will no longer share the tutorials.

Wait does this mean you finally got my script to work?

lebigmac said:
Wait does this mean you finally got my script to work?
How about a little feedback in my project thread? Is that too much to ask for?
Did the latest fix work for you or not? Hello?
Click to expand...
Click to collapse
I said you were working on it. LOL. If it worked I'd be writing a Guide for that!

Make sure boot.img matched with the phone build number, or the phone may get bootloop.
Moto One Ace is one of the easiest phone to root

mingkee said:
Make sure boot.img matched with the phone build number, or the phone may get bootloop.
Moto One Ace is one of the easiest phone to root
Click to expand...
Click to collapse
Exactly. Definitely made a note of that in the guide since that is why the frozen touchscreen issue happens.

Articul8Madness said:
.This tutorial is for people like me than ran into problems rooting the Moto One 5G Ace XT2113 (MetroPCS Qualcomm Variant) running on stock Android 10. I got this phone literally last week brand new in the box. This is a hand holding guide for the Noobs that really are intimidated by rooting their device.
Follow the following at your own risk! I am not responsible for any mishaps with your devices.
I want to thank @mingkee and @sd_shadow for pointing me in the right direction. And for the rest of the contributors that I took bits and pieces from that helped me figure out rooting this; I did achieve root out the starting gate but initially lost touchscreen functionality. The issue was that you have to use the boot.img of your firmware to patch into Magisk; if you do this with your phone out the box you really don't know which firmware was used and that is where the bungle happens. This will clear up all those potential freakout moments.
Thanks to Android 10 being System As Root with all these new super partitions running amuck, you cannot get Write access in the actual system files. So even when you achieve root, you can't do much. @lebigmac is working on that as we speak. Drop by his thread on R/W access and beta test his script so he can get more knowledge about how our phone works.
Introduction/Preparation
First, go and prepare by READING EVERYTHING. Very important. This is the Qualcomm variant and NOT the Mediatek variant. Flashing does make a difference between the two. Last thing you want to do is brick the device because you flashed the wrong firmware to the wrong processor, or you flashed other software for the other similiar Moto One 5G and it bricked.
Second, unlock the bootloader. All T-Mobile and their subsidiary variants can be unlocked by Motorola as well as International and Motorola factory variants; go to their bootloader official unlock site and follow their instructions, it's easy peasy. If you do it in firefox it may not go to the third step page and hang on the page where you put the long code in (follow instructions on page to get the unlock code you'll see what I'm talking about). It is HIGHLY ADVISABLE to do this in Waterfox or Chrome (I used Waterfox). And yes, you may have to request the code 3x to get it to send to your email depending on their server traffic. When you get it, follow Motorola's instructions for unlocking the bootloader in fastboot. It will show you that the bootloader is unlocked.
Verizon and ATT Variants CANNOT BE BOOTLOADER UNLOADER UNLOCKED.
***NOTES SO YOU DON'T FREAK OUT***
1. I did NOT see the motorola post screen telling me it was unlocked. I had to find this in fastboot's menu.
2. The only way to restore the phone if something goes wrong is by flashing it via fastboot. The way to get to fastboot is turn the phone off and press Volume Down and Power. The Motorola tool will NOT work. That's normal.
3. You will see a cute message that you've unlocked the bootloader and that the phone software integrity is compromised when you boot the phone up every single time after the bootloader unlock. It will also say press the power button to pause. This is normal. Give it a minute, you havent broke it.
4. OEM Unlocking should already be activated and greyed out in the Developer Options once the bootloader is unlocked; you can't access it anymore.
Files
You will need an SD card for root. You will also need other apks to successfully help you pull off root ready to install. Pull ALL the necessary files you will need.
1. Get Minimal ADB and Fastboot (it's easier).
2. Download the Motorola Drivers from their site if yo don't already have them (if you run into problems you will have to uninstall and reinstall them through their utility which is found on PC here: C:\Program Files\Common Files\Motorola Shared\Mobile Drivers
3. Cpu-Z.apk (Very important, its hard to know your hardware without this).
4. Magisk v22.0.apk (They no longer have a separate Magisk Manager)
5. Root Explorer.apk (This software helps navigation better but you can use any Explorer of your choice).
6. Root Checker.apk
7. Stock Firmware XT2113-3_KIEV_RETEU_10_QZK30.Q4-40-62_subsidy-DEFAULT_regulatory-XT2113-3-EU-SAR_CFC.xml (This is important if you mess up the boot image trying to root). You can get the firmware of your choice at Motorola Official Firmware For Kiev.
8. Patience (and a good movie keeping you going).
As of now this device as no TWRP, so you have to do this the old fashioned way to root. And just so you know, I used Windows 7 for all of this.
Pre-Rooting
1. Make sure the phone is fully charged.
2. Make sure your sim card is REMOVED from the phone. Everytime you wipe the phone or do anything messing with the boot image the phone resets itself to factory settings, and tries to push an update. Just take the silver key thing and pop it out. You will have to push it back in and out in a second, but start with it out.
3. Make sure your wifi is OFF.
4. Make sure your SD is in and mountable and all files you need are on the card.
5. Make sure you Save boot.img to your SD Card from your firmware files. This is very important for root.
6. Make sure your developer options are activated.
7. Make sure your USB debugging is enabled AND you've given permissions for your computer to have administrative access with it enabled (more on this below).
8. Make sure to check CPU-Z for your hardware specs so you download the right files for the phone and avoid potential problems.
9. Make sure you manually set USB to Transfer files (no other option will work and by default its set to Charge this Device).
10. Make sure you have the STOCK CABLE that comes with the phone. Like most Motorolas this model is funky about using other cables.
11. Make sure you back up all your calls, texts, pics, etc. Flashing the firmware is the ultimate factory reset and you will lose all your files on the phone. SMS Restore is a good software to backup Calls and Text logs and it supports keeping MMS.
12. Make sure you have the internet. It is necessary for some steps.
Rooting
1. Make sure all the firmware files are extracted into your Minimal ADB and Fastboot folder (or whatever ADB folder you're using for this).
2. Open FlashFile.xml in Notepad. This is located among the firmware files you put in the Minimal ADB and Fastboot folder.
3. Cut, copy, and paste everything from the FlashFile that is shown and then paste it in an online Flash file Converter. I used Online Flash File Converter here.
4. Convert the text by pressing the bar below where you pasted the text. It may be in Spanish or Portuguese but is should say something like Cerar Commandos.
5. Copy the text by hitting the two pieces of paper icon in the corner after it's converted. Or just cut copy and paste manually.
6. Turn the phone completely OFF.
7. Plug your phone via USB cable into the computer.
8. Press Volume Down and Power to boot into fastboot mode. Do not use "adb reboot bootloader" as that command may or may not work and hang at "waiting for device" (it was iffy for me and it knocked off USB permissions BADLY).
9. Open up Minimal ADB and Fastboot (Make sure you don't have it set to open this as an administrator, it messes with permissions) Make sure your firmware files are in the Minimal ADB directory or it won't work.
10. Paste the contents of the flashfile converter into Minimal ADB and Fastboot. This should start the process of the flashing.
11. When the entire flash is complete, boot the phone and disconnect phone from the computer. Ignore the bootloader unlock error.
12. Wait. Sometimes this takes up to 3-5 minutes on a new flash. You should see the boot animation of Motorola.
13. Push your Sim Card back into the phone.
14. Start setting up your device on the screen. Sim Card must be in or it will give you a message your phone is Network Locked.
15. Once you make it to the Wifi Setup screen take the Sim back OUT the phone. Do not connect to Wifi.
16. Once you are done with setup, go to Settings>About phone.
17. Go all the way down to Build Number and press it until you unlock Developer Options.
18. Go to Settings>System>Advanced>Developer Options. Advanced is a pull down tab that will reveal Developer Options.
19. Disable Automatic System Updates. I know this is hard for some people, but a forced OTA update may cause problems and prohibit root.
20. Enable USB Debugging. Disable Verify bytecode of debuggable apps. Disable Verify apps over USB if it is highlighted. Exit.
21. Put your SD/Sim card back into the phone.
22. Go to the Files folder and install Magisk first, then Root Explorer and Root Checker.
23. Open Magisk. You will see Magisk and App. Hit Install by Magisk (a fingerprint looking icon is to its left).
24. Allow Magisk to access photos, media, and files if it asks.
25. Select option "Select and Patch A File."
26. It will take you to a screen where you can select your explorer to navigate to your SD card where you saved the boot.img. Go there and select it.
27. Magisk will save it as magisk_patched.img. Once you get it patched, find where it saved, make sure it's on your SD card and then turn off the phone.
28. Plug your phone via USB cable into the computer.
29. Press Volume Down and Power to boot into fastboot mode.
30. Open up a fresh Minimal ADB and Fastboot (Make sure you don't have it set to open this as an administrator, it messes with permissions) Make sure you transfer the magisk_patched.img that Magisk patched off your SD card into this folder.
31. Rename your original boot.img to "boot.img original" or whatever distinct name you want to give it in your Minimal ADB and Fastboot folder.
32. Rename your magisk_patched.img to boot.img.
33. In Minimal ADB and Fastboot type "fastboot flash boot boot.img" and hit enter.
34. If all goes well it should flash to the partition before it says done and in how many seconds.
35. When it is done, reboot phone by selecting START (keep pressing volume rockers until you see it, then press the power button).
36. Wait for the bootloader cannot be trusted screen to pass (may take a minute) and wait for the Hello Moto opening.
37. Open Root Checker and confirm root. You can uninstall it after confirmation if you like.
38. Open Root Explorer. A prompt asking you to grant permission should pop up.
Congrats. You should be rooted now.
***NOTES SO YOU DON'T FREAK OUT***
1. Do NOT flash someone else's patched boot image. It WILL NOT WORK. Do the work, find your firmware, and patch the boot image yourself. You're asking for bootloop hell if you do as your boot.img that Magisk patches needs to match that particular firmware you used.
2. While it hasn't happened to me, You may have followed everything perfect and it still bootlooped. Save yourself the frustration and just flash it over. See the next section on the proper way to flash so you don't lose your baseband, IMEI, or any other important stuff.
3. While you won't lose anything just flashing boot.img, you will lose everything having to flash ALL the firmware over. Keep backups of all your important stuff.
****Notes on Flashing The Stock Firmware if you have to****
In the event you bootloop and have to start from scratch, follow my guide on restoring the firmware on the phone. And don't worry - it won't relock the bootloader. You can find my guide here: The Complete Noob Guide to Flashing via Fastboot MetroPCS Moto One 5G Ace XT2113 [Qualcomm Version]
Hope this helps my fellow TMobile and subdiary acolytes and othoers. I have flashed and reflashed my phone with different variant roms trying to force Write status and beta testing scripts for @lebigmac on our device so it's pretty straightforward now.
I will try and answer questions if I can or point you in the right direction.
Click to expand...
Click to collapse
Question I keep seeing you have to use adb to fix if messed up, sorry not a question yet but that's wrong. When I did it I think I mixed up my moto g stylus boot.img and got a boot loop. I flashed stock boot.img and it came up with a screen saying Android os was corrupted try to reboot if didn't work factory reset is needed. Rebooted popped up again hit factory reset and the phone did it for me. Not sure if you knew that, question tho lol sorry, can I patch boot img with magisk and flash to a phone that's not fresh from a factory reset

bobbyp1086 said:
Question I keep seeing you have to use adb to fix if messed up, sorry not a question yet but that's wrong. When I did it I think I mixed up my moto g stylus boot.img and got a boot loop. I flashed stock boot.img and it came up with a screen saying Android os was corrupted try to reboot if didn't work factory reset is needed. Rebooted popped up again hit factory reset and the phone did it for me. Not sure if you knew that, question tho lol sorry, can I patch boot img with magisk and flash to a phone that's not fresh from a factory reset
Click to expand...
Click to collapse
Well, when I rooted the 1st time I got a frozen touchscreen as I didn't have the correct Firmware (as the phone's firmware out of the box auto updated and the firmware that was available did not match its peripherals). So my phone lost ALL TOUCH ability. The way I explain in this guide is what worked for me, as the LHSA tool doesn't help at that stage. And honestly, I think adb is better and more familiar to most Moto folks that have had several devices and got root on them.
If you mixed up your Moto G Stylus boot.img, all you have to do is try and reflash your firmware boot.img and flash it (or if you have root your patched boot.img). I've flashed this phone almost 70 times in 9 days and I normally do not reflash my boot.img as its already patched to the firmware and I'm just starting from scratch. However, I wouldn't advise that on recovery.img that went wrong, just saying. The phone will force a factory reset.
I don't recommend a factory reset for flashing if you're trying to get root. It's best to compile all the files in ADB to make sure they're taking together, and not going after the fact. There is no shutting off DM-Verity at this time, especially without TWRP and a patch for it, and this model is a bit funky about added flashing with this new Dynamic Partition crap.

Articul8Madness said:
Well, when I rooted the 1st time I got a frozen touchscreen as I didn't have the correct Firmware (as the phone's firmware out of the box auto updated and the firmware that was available did not match its peripherals). So my phone lost ALL TOUCH ability. The way I explain in this guide is what worked for me, as the LHSA tool doesn't help at that stage. And honestly, I think adb is better and more familiar to most Moto folks that have had several devices and got root on them.
If you mixed up your Moto G Stylus boot.img, all you have to do is try and reflash your firmware boot.img and flash it (or if you have root your patched boot.img). I've flashed this phone almost 70 times in 9 days and I normally do not reflash my boot.img as its already patched to the firmware and I'm just starting from scratch. However, I wouldn't advise that on recovery.img that went wrong, just saying. The phone will force a factory reset.
I don't recommend a factory reset for flashing if you're trying to get root. It's best to compile all the files in ADB to make sure they're taking together, and not going after the fact. There is no shutting off DM-Verity at this time, especially without TWRP and a patch for it, and this model is a bit funky about added flashing with this new Dynamic Partition crap.
Click to expand...
Click to collapse
That's what mine did, I flashed stock boot, is corrupted my phone says and forced reset, I'm newish to moto, Samsung for many years, had to ditch them tho lol.
I appreciate the help and hope I didn't come across as arguing, more like clarifying. I too prefer adb over anything, only get the rom from tool. Again thanks for info.

bobbyp1086 said:
That's what mine did, I flashed stock boot, is corrupted my phone says and forced reset, I'm newish to moto, Samsung for many years, had to ditch them tho lol.
I appreciate the help and hope I didn't come across as arguing, more like clarifying. I too prefer adb over anything, only get the rom from tool. Again thanks for info.
Click to expand...
Click to collapse
If your bootloader is unlocked the only way you should have gotten the corruption is if you flashed an incompatible firmware. Mine came with MetroPCS but I've flashed RETUS and RETEU well. I'd stray from any VZW or ATT software just because you can't trust their firmware won't lock down the bootloader.
Or maybe the software just didn't download well. Try re-downloading it . I've had a bad download mess up a flash before.

I think it's cause 1 magisk wasn't installed and 2i used a different phone to patch

bobbyp1086 said:
I think it's cause 1 magisk wasn't installed and 2i used a different phone to patch
Click to expand...
Click to collapse
You have to install Magisk and patch on the phone in question since it's looking for that firmware and that phone's peripherals. You can't use another phone - that's a no no. This ain't Gingerbread, lol.

Articul8Madness said:
You have to install Magisk and patch on the phone in question since it's looking for that firmware and that phone's peripherals. You can't use another phone - that's a no no. This ain't Gingerbread, lol.
Click to expand...
Click to collapse
I'm fairly new to magisk, just recently in past year or so stopped using supersu. Not by choice lol but upgraded my note 4 lmao. So as far as the script for read and write, never flashed and after I got magisk, no modules only su permissions, fx did mount /
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and fix file permissions, it's in settings

bobbyp1086 said:
I'm fairly new to magisk, just recently in past year or so stopped using supersu. Not by choice lol but upgraded my note 4 lmao. So as far as the script for read and write, never flashed and after I got magisk, no modules only su permissions, fx did mount /View attachment 5279427View attachment 5279429View attachment 5279431View attachment 5279433 and fix file permissions, it's in settings
Click to expand...
Click to collapse
Having Root on this device is not going to magically fix the fact that Android 10 on ALL DEVICES is READ ONLY. You will have to go to @lebigmac or @munjeni and try their R/W mount scripts to get true root access. Munjeni's V2 worked for me. He's on V7 now. LeBigMac has been hard at work trying to get us up and running with his script, but we have Super partitions AND A/B. So it's taking some time.

Articul8Madness said:
Having Root on this device is not going to magically fix the fact that Android 10 on ALL DEVICES is READ ONLY. You will have to go to @lebigmac or @munjeni and try their R/W mount scripts to get true root access. Munjeni's V2 worked for me. He's on V7 now. LeBigMac has been hard at work trying to get us up and running with his script, but we have Super partitions AND A/B. So it's taking some time.
Click to expand...
Click to collapse
I am not familiar with either but take it that's it's not an easy task. Should I run v2 or v7 then? Moto one g ace metro.
I was fooled by the trickery, I thought something seemed off with the root on modern phone's.

I just bought a new Moto One 5G ace and was wondering where I can find the stock T-Mobile Firmware variants to prevent bricking?

I successfully rooted it with Magisk patched and ready to go. Unfortunately for the time being the phone won't bypass safety net even with MagiskHide. It just won't work but I'm really happy this phone can be unlocked

bobbyp1086 said:
I am not familiar with either but take it that's it's not an easy task. Should I run v2 or v7 then? Moto one g ace metro.
I was fooled by the trickery, I thought something seemed off with the root on modern phone's.
Click to expand...
Click to collapse
Android 10 is very challenging. It is easy to root but it is a trickable root with a false sense of root since Google locked all Android 10 and newer as Read Only on the System with this super partition crap trying to be Apple.

Skel40 said:
I just bought a new Moto One 5G ace and was wondering where I can find the stock T-Mobile Firmware variants to prevent bricking?
Click to expand...
Click to collapse
Check my guide. I posted link to where the repository is.

Skel40 said:
I successfully rooted it with Magisk patched and ready to go. Unfortunately for the time being the phone won't bypass safety net even with MagiskHide. It just won't work but I'm really happy this phone can be unlocked
Click to expand...
Click to collapse
You will not pass safety net because you've rooted it and Android 10 will block it. It isn't necessary, especially if you delete all Google stuff and their tracking Covid crap.

Articul8Madness said:
Having Root on this device is not going to magically fix the fact that Android 10 on ALL DEVICES is READ ONLY. You will have to go to @lebigmac or @munjeni and try their R/W mount scripts to get true root access. Munjeni's V2 worked for me. He's on V7 now. LeBigMac has been hard at work trying to get us up and running with his script, but we have Super partitions AND A/B. So it's taking some time.
Click to expand...
Click to collapse
Hi @Articul8Madness. Thanks for mentioning me
There's a Motorola user who recently got my script to work using the troubleshooting repair script that I posted here
It turns out the lpmake arguments that are auto-generated by the original script were flawless and were not the root cause of the unidentified lpmake error that some Motorola users were experiencing at the end of the original script. According to @Xiaoleng the error was most likely caused by some kind of new Motorola security feature that prevents the terminal command from executing if the arguments are too long. Go figure.
And he was even able to fastboot flash the super_fixed.bin in one piece without having to first split it up into chunks. That's a huge surprise to me. I always thought Motorola users can only fastboot flash super sparsechunks?!
Please feel free to give it a try and report back your results. Thanks. Good luck!

[Solved!] [SM-G955F] RMM state still locked after 7 days (RMM State Prenormal)

I've been trying to install TWRP on my phone for about 3 weeks straight now and i keep running into this exact same issue.
Basically, every time I try to flash anything other than a stock ROM the flash fails and i get "Only official released binaries are allowed to be flashed(RECOVERY)" on my phone's Download screen. (Here's an pic of Odin when the flash fails)
I've tried flashing the latest carrier-unlocked stock ROM to it, and using the phone for 2 week without rebooting (was constantly connected to the internet, uptime was around 300 hours before i attempted to flash TWRP again). I've also tried some solutions I've found on the XDA forums (like flashing the nougat bootloader to my phone, and changing back the time by a month) but nothing appears to work.
I also got the phone used if that's any useful info.
The "OEM Unlock" option was also enabled for some reason after enabling Developer Options. And i also made the mistake of resetting the phone via the recovery menu since i didn't know the previous owner's Samsung account password to remove it from the phone (I'm guessing that's the thing that initially triggered it?)
The phone is also from Spain (but i flashed a stock ROM from my country so it should be fine?) and i have a SIM inserted into it if it's relevant.
I also very much don't care if KNOX trips or not. I don't plan on using any Samsung-made apps ever again since I wanna install a FOSS (free and open-source) ROM to my phone and I don't plan to *ever* sell this phone either.
HUGE thank yous to anyone who finds a solution

FlooferLand said:
I've been trying to install TWRP on my phone for about 3 weeks straight now and i keep running into this exact same issue.
Basically, every time I try to flash anything other than a stock ROM the flash fails and i get "Only official released binaries are allowed to be flashed(RECOVERY)" on my phone's Download screen. (Here's an pic of Odin when the flash fails)
I've tried flashing the latest carrier-unlocked stock ROM to it, and using the phone for 2 week without rebooting (was constantly connected to the internet, uptime was around 300 hours before i attempted to flash TWRP again). I've also tried some solutions I've found on the XDA forums (like flashing the nougat bootloader to my phone, and changing back the time by a month) but nothing appears to work.
I also got the phone used if that's any useful info.
The "OEM Unlock" option was also enabled for some reason after enabling Developer Options. And i also made the mistake of resetting the phone via the recovery menu since i didn't know the previous owner's Samsung account password to remove it from the phone (I'm guessing that's the thing that initially triggered it?)
The phone is also from Spain (but i flashed a stock ROM from my country so it should be fine?) and i have a SIM inserted into it if it's relevant.
I also very much don't care if KNOX trips or not. I don't plan on using any Samsung-made apps ever again since I wanna install a FOSS (free and open-source) ROM to my phone and I don't plan to *ever* sell this phone either.
HUGE thank yous to anyone who finds a solution
Click to expand...
Click to collapse
Can you send a screenshot of the bootloader screen?

Kenora_I said:
Can you send a screenshot of the bootloader screen?
Click to expand...
Click to collapse
I'm guessing you mean the Download screen..?
Here's the Download screen if so:
https://imgur.com/pxu0hsS

FlooferLand said:
I've been trying to install TWRP on my phone for about 3 weeks straight now and i keep running into this exact same issue.
Basically, every time I try to flash anything other than a stock ROM the flash fails and i get "Only official released binaries are allowed to be flashed(RECOVERY)" on my phone's Download screen. (Here's an pic of Odin when the flash fails)
I've tried flashing the latest carrier-unlocked stock ROM to it, and using the phone for 2 week without rebooting (was constantly connected to the internet, uptime was around 300 hours before i attempted to flash TWRP again). I've also tried some solutions I've found on the XDA forums (like flashing the nougat bootloader to my phone, and changing back the time by a month) but nothing appears to work.
I also got the phone used if that's any useful info.
The "OEM Unlock" option was also enabled for some reason after enabling Developer Options. And i also made the mistake of resetting the phone via the recovery menu since i didn't know the previous owner's Samsung account password to remove it from the phone (I'm guessing that's the thing that initially triggered it?)
The phone is also from Spain (but i flashed a stock ROM from my country so it should be fine?) and i have a SIM inserted into it if it's relevant.
I also very much don't care if KNOX trips or not. I don't plan on using any Samsung-made apps ever again since I wanna install a FOSS (free and open-source) ROM to my phone and I don't plan to *ever* sell this phone either.
HUGE thank yous to anyone who finds a solution
Click to expand...
Click to collapse
You did run fastboot OEM unlock?
or
fastboot flashing unlock

Kenora_I said:
You did run fastboot OEM unlock?
or
fastboot flashing unlock
Click to expand...
Click to collapse
I don't think my phone even has fastboot
I tried booting it into recovery and selecting to apply an update with ADB, I've also tried it at the "Waiting for update" screen.
Fastboot just gets stuck saying < waiting for any device >
The OEM unlock checkbox is already checked in Developer Options.
I don't think the S8+ needs another way to enable OEM unlock other than the checkbox in Developer Options.
EDIT: Here's the output of adb logcat --regex rmm after booting into Android if that's helpful(?) (I have no idea how to use Logcat):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

you did install fastboot drivers? Sometimes if you connect with a usb 3.0 port it dosent work properly

Kenora_I said:
you did install fastboot drivers? Sometimes if you connect with a usb 3.0 port it dosent work properly
Click to expand...
Click to collapse
I've seen a lot of people say the S8+ doesn't have fastboot, there's also no "Reboot to fastboot" option in the recovery menu

Apparently Samsung's RMM server (https://rmm.samsung.com/) appears to be dead (SSL certificate expired and the entire server seems to not work)
So i'm wondering if there's a way to actually spoof the data the server sends, basically blocking Samsung's server and making my own DNS that resolves to my own server sending it's own data.
My problem then is, how would i even know what data my server is supposed to send? And would that even be possible?
I'm very much out of ideas XD
I also found this post (and i have a continuation file for my own phone so in theory it should work?) but it requires the use of iRoot and some proprietary sketchy Windows program. And iRoot and all of these one-click root apps have been known for injecting malware system-level into devices.

FIXED IT!!
The time trick actually worked.
All i had to do was turn back the time by like a year, reboot, enter recovery mode, delete cache, re-enable OEM unlock, spam the update phone button, and boot into download mode!

Nice work! tbh I'd never think of that lol,
FlooferLand said:
FIXED IT!!
The time trick actually worked.
All i had to do was turn back the time by like a year, reboot, enter recovery mode, delete cache, re-enable OEM unlock, spam the update phone button, and boot into download mode!
Click to expand...
Click to collapse

FlooferLand said:
FIXED IT!!
The time trick actually worked.
All i had to do was turn back the time by like a year, reboot, enter recovery mode, delete cache, re-enable OEM unlock, spam the update phone button, and boot into download mode!
Click to expand...
Click to collapse
The same problem, i tried everything, chImera, date, nothing works. Please help me @FlooferLand !

JuanMat97 said:
The same problem, i tried everything, chImera, date, nothing works. Please help me @FlooferLand !
Click to expand...
Click to collapse
The same goes. I have tried everything, and it seems that the post here suggests that we now entirely depend on Samsung to get the site certificate sorted out
Link pasted here for those who don't trust shortened links: https://forum.xda-developers.com/t/...d-expired-certificate-whats-next-lol.4403393/

JuanMat97 said:
The same problem, i tried everything, chImera, date, nothing works. Please help me @FlooferLand !
Click to expand...
Click to collapse
I very much have no clue how it worked for me XD
It's very much possible, you just have to continously try.
I've heard rumors that if you have a Snapdragon chip instead of an Exynos, the RMM is doomed to lock until Samsung resolves their issue. But idk anything about that so i can't really confirm it XD.
I would recommend upgrading to Android 9 and doing the thing i said tho, that worked for me.
Also make sure that your ROM is from the country your SIM card is from, very important.
My phone was originally from Spain, and having a ROM that was made in Spain seemed to caused the RMM to continuously trip out since my SIM wasn't from Spain, so it essentially detected my phone as stolen or smth. You can find official ROMs on something like SamFW.
If this still doesn't work, try waiting 7 days again, then doing the thing i said.

FlooferLand said:
I very much have no clue how it worked for me XD
It's very much possible, you just have to continously try.
I've heard rumors that if you have a Snapdragon chip instead of an Exynos, the RMM is doomed to lock until Samsung resolves their issue. But idk anything about that so i can't really confirm it XD.
I would recommend upgrading to Android 9 and doing the thing i said tho, that worked for me.
Also make sure that your ROM is from the country your SIM card is from, very important.
My phone was originally from Spain, and having a ROM that was made in Spain seemed to caused the RMM to continuously trip out since my SIM wasn't from Spain, so it essentially detected my phone as stolen or smth. You can find official ROMs on something like SamFW.
If this still doesn't work, try waiting 7 days again, then doing the thing i said.
Click to expand...
Click to collapse
friend please, could you say, step by step and in an orderly manner what you did? for example when you said "The time trick actually worked.
All i had to do was turn back the time by like a year" 1-¿have you done that after a flash, a hard reset, or just rebooted without deleting anything?, and also when you said "reboot, enter recovery mode" 2-¿what you did was restart directly to recovery, or restart the system and then restart it again to recovery? and lastly in the part where you said "re-enable OEM unlock, spam the update phone button" 3-¿"re-enable", if you said "re" it means that before reactivating it you already had it activated, right? 4-¿"spam button" by that you mean pressing many times, but, did you have the automatic updates box enabled or not, and... how many times did you touch the update button? thanks in advance, I would appreciate if you answer the 4 questions

which ROM were you using when you did theses steps to unlock? I've tried the 168hs+ method almost now and it didn't worked, then I found your post and tried doing this method changing the date and rebooting cleaning the partition but until now I couldn't achieve it, can you help me pleass

which ROM were you using when you did theses steps to unlock? I've tried the 168hs+ method almost now and it didn't worked, then I found your post and tried doing this method changing the date and rebooting cleaning the partition but until now I couldn't achieve it, can you help me pleass

General OP9 (LE2117.11.C18) T-MOBILE Stock Boot.img && Root [No Firmware Decrypt] EASYYYYY!!

Was able to get T-Mobile's OnePlus 9 stock boot image c18. Without having to decrypt firmware OTA. It's been months ever since Android 12 came out that I've been scouring for a stock boot image so I could root my OnePlus 9. All I ever found was 1 + 9 pro or use any regions boot image it will work but I couldn't do it I couldn't take the risk of possibly soft freaking or breaking my phone. So all this work all this work all this work and I finally figured it out and it was way way easier than it should have been for how much time and effort I had done to research this. I literally was able to pull my boot image then back up all my partitions and the matter of 10 minutes on top of hatching the boot image and rooting my phone and passing the safety net. I honestly didn't think it could be done because T-Mobile has their firmwares on lockdown tighter than Bill Gates wallet. If anyone would like to know how I did this or anybody would like to get a copy of the stock boot image for le2117 c18 send me a message and I'll send you the file or I will invite you on the easy process of going through and pulling your own image and your own partitions without the help of somebody else's or a different firmwares or decrypting OTA let's do this the
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
easy way all right?

NishiMoon said:
Was able to get T-Mobile's OnePlus 9 stock boot image c18. Without having to decrypt firmware OTA. It's been months ever since Android 12 came out that I've been scouring for a stock boot image so I could root my OnePlus 9. All I ever found was 1 + 9 pro or use any regions boot image it will work but I couldn't do it I couldn't take the risk of possibly soft freaking or breaking my phone. So all this work all this work all this work and I finally figured it out and it was way way easier than it should have been for how much time and effort I had done to research this. I literally was able to pull my boot image then back up all my partitions and the matter of 10 minutes on top of hatching the boot image and rooting my phone and passing the safety net. I honestly didn't think it could be done because T-Mobile has their firmwares on lockdown tighter than Bill Gates wallet. If anyone would like to know how I did this or anybody would like to get a copy of the stock boot image for le2117 c18 send me a message and I'll send you the file or I will invite you on the easy process of going through and pulling your own image and your own partitions without the help of somebody else's or a different firmwares or decrypting OTA let's do this the View attachment 5675937 easy way all right?
Click to expand...
Click to collapse
No need to wait for months to get any image. You can use msm read back. F8 when it opens.( oneplus )password and read back the images you want to your C/drive.

Or you could enter edl no need for msm. I found out that using terminal while in edl is far superior.
I'm just happy I can give the LE2117 stock boot.img out since I have yet to see it anywhere on xda or the web yet. Let alone a boot.img for recent update c.18

NishiMoon said:
Or you could enter edl no need for msm. I found out that using terminal while in edl is far superior.
I'm just happy I can give the LE2117 stock boot.img out since I have yet to see it anywhere on xda or the web yet. Let alone a boot.img for recent update c.18
Click to expand...
Click to collapse
I have been looking for a way to do this for my LE2117 for so long could you. Type a quick walk through on your method with EDL and Terminal or I can just try with the MSM Tool Readback I just found that out as well.

NishiMoon said:
Was able to get T-Mobile's OnePlus 9 stock boot image c18. Without having to decrypt firmware OTA. It's been months ever since Android 12 came out that I've been scouring for a stock boot image so I could root my OnePlus 9. All I ever found was 1 + 9 pro or use any regions boot image it will work but I couldn't do it I couldn't take the risk of possibly soft freaking or breaking my phone. So all this work all this work all this work and I finally figured it out and it was way way easier than it should have been for how much time and effort I had done to research this. I literally was able to pull my boot image then back up all my partitions and the matter of 10 minutes on top of hatching the boot image and rooting my phone and passing the safety net. I honestly didn't think it could be done because T-Mobile has their firmwares on lockdown tighter than Bill Gates wallet. If anyone would like to know how I did this or anybody would like to get a copy of the stock boot image for le2117 c18 send me a message and I'll send you the file or I will invite you on the easy process of going through and pulling your own image and your own partitions without the help of somebody else's or a different firmwares or decrypting OTA let's do this the View attachment 5675937 easy way all right?
Click to expand...
Click to collapse
Any Link to this Stock Boot.img ?

Let me see if I can find it in my files

mattie_49 said:
No need to wait for months to get any image. You can use msm read back. F8 when it opens.( oneplus )password and read back the images you want to your C/drive.
Click to expand...
Click to collapse
Do I Need ROOT to do this on a T-Mobile OP9 ?
( seems too easy...)

barguybrady said:
Do I Need ROOT to do this on a T-Mobile OP9 ?
( seems too easy...)
Click to expand...
Click to collapse
No

NishiMoon said:
Or you could enter edl no need for msm. I found out that using terminal while in edl is far superior.
I'm just happy I can give the LE2117 stock boot.img out since I have yet to see it anywhere on xda or the web yet. Let alone a boot.img for recent update c.18
Click to expand...
Click to collapse
So...
Are you gonna offer any further supporting details, links, comments, or such about using EDL mode?
I cannot find any list of Commands, at least for a Linux Shell ?

barguybrady said:
So...
Are you gonna offer any further supporting details, links, comments, or such about using EDL mode?
I cannot find any list of Commands, at least for a Linux Shell ?
Click to expand...
Click to collapse
I don't know anything about Linux . I mentioned msm read back to pull images from what build your using. And how to use and password. One must partially find their own way eventually. We all have Google , I know there is info on what I shared.

mattie_49 said:
I don't know anything about Linux . I mentioned msm read back to pull images from what build your using. And how to use and password. One must partially find their own way eventually. We all have Google , I know there is info on what I shared.
Click to expand...
Click to collapse
Yes. I had one last time to access a Win 10 computer, late last night.
Using the MSM readback mode is Ridiculously EasY!
( maybe That's why some of these Forums have gotten quiet lately..? With Readback, getting ANY boot.img is almost easier than other methods...)
With root & magisk, I'm All Set !
May The Force Be With You All !

barguybrady said:
Yes. I had one last time to access a Win 10 computer, late last night.
Using the MSM readback mode is Ridiculously EasY!
( maybe That's why some of these Forums have gotten quiet lately..? With Readback, getting ANY boot.img is almost easier than other methods...)
With root & magisk, I'm All Set !
May The Force Be With You All !
Click to expand...
Click to collapse
If your into flashing builds may I suggest Pixel Extended here in the threads. Surely nice.

mattie_49 said:
If your into flashing builds may I suggest Pixel Extended here in the threads. Surely nice.
Click to expand...
Click to collapse
Hah !!
I was thinking about That One !
Bought the OP9 for the camera - and after 19 months on Lineage, with g-Cam & Open Cam, I was contemplating switching to Pixel Ext for it's advertised camera compatibility...
But, I doubt I'll keep this phone for much longer, mostly due to All the Issues that brought me here in the first place, carrier branded.... yadda, yadda, yadda....
SO, with Root, I think I'll keep using OOS, handle the Updates from t-MO as they come along, and Every Time I get Frustrated at this thing - use that as a reminder to Buy an International and Unlocked Phone from my Guys In Chicago....and run what-ever I wish, in any way I wish - WithOut Advertising or Bloat ! !

barguybrady said:
Hah !!
I was thinking about That One !
Bought the OP9 for the camera - and after 19 months on Lineage, with g-Cam & Open Cam, I was contemplating switching to Pixel Ext for it's advertised camera compatibility...
But, I doubt I'll keep this phone for much longer, mostly due to All the Issues that brought me here in the first place, carrier branded.... yadda, yadda, yadda....
SO, with Root, I think I'll keep using OOS, handle the Updates from t-MO as they come along, and Every Time I get Frustrated at this thing - use that as a reminder to Buy an International and Unlocked Phone from my Guys In Chicago....and run what-ever I wish, in any way I wish - WithOut Advertising or Bloat ! !
Click to expand...
Click to collapse
Fyi latest 5.7 PE has fully functional Oos cam. All video modes working perfect like stock. Slo-mo ,4k 8k. I'm real picky and always msm back to stock. I've def found a home.

mattie_49 said:
Fyi latest 5.7 PE has fully functional Oos cam. All video modes working perfect like stock. Slo-mo ,4k 8k. I'm real picky and always msm back to stock. I've def found a home.
Click to expand...
Click to collapse
That's quite AN Endorsement !