Database Info

[Q] Flashed Recovery for Another Device

I was in the process of upgrading TWRP on my phone when I wasn't paying attention and accidentally flashed the wrong zip (This one to be exact).
Now the phone shows no signs of life. Doesn't respond to any button combination presses, or when connecting it to a computer. Doing some searching, I came across this thread. Is that applicable for my situation, or should I just get a JTAG service on it? Thanks, and let me know if I'm not providing enough details. I appreciate the help.

CommieSalami said:
I was in the process of upgrading TWRP on my phone when I wasn't paying attention and accidentally flashed the wrong zip (This one to be exact).
Now the phone shows no signs of life. Doesn't respond to any button combination presses, or when connecting it to a computer. Doing some searching, I came across this thread. Is that applicable for my situation, or should I just get a JTAG service on it? Thanks, and let me know if I'm not providing enough details. I appreciate the help.
Click to expand...
Click to collapse
Yes try that, if partitions do not enumerate properly, only choice is jtagg.

exad said:
Yes try that, if partitions do not enumerate properly, only choice is jtagg.
Click to expand...
Click to collapse
How about leaving the phone consuming the battery, then plugging it to AC, charging it a little, letting it booting normally then using adb reboot bootloader to make the phone enter the bootloader mode and flashing the right recovery with fastboot flash .... The whole point is to make the phone reach the bootloader state, isn't it?
Later edit: I thought you have flashed only the wrong recovery. The above method might help only in that case. When the partition table and the bootloader partition are overwritten, only a jtag may help. And expect your phone not to look the same!
Another edit: Isn't the OTA script supposed to check the phone platform before starting to write the files? Then, when flashing an OTA zip, the recovery decompresses its contents and if it doesn't have enough space, it ends the process with an error. What am I missing here?

AlxMAX said:
How about leaving the phone consuming the battery, then plugging it to AC, charging it a little, letting it booting normally then using adb reboot bootloader to make the phone enter the bootloader mode and flashing the right recovery with fastboot flash .... The whole point is to make the phone reach the bootloader state, isn't it?
Later edit: I thought you have flashed only the wrong recovery. The above method might help only in that case. When the partition table and the bootloader partition are overwritten, only a jtag may help. And expect your phone not to look the same!
Another edit: Isn't the OTA script supposed to check the phone platform before starting to write the files? Then, when flashing an OTA zip, the recovery decompresses its contents and if it doesn't have enough space, it ends the process with an error. What am I missing here?
Click to expand...
Click to collapse
It isn't an OTA script. When flashing something through fastboot there isn't really any check. Numerous people have made this mistake:
fastboot flash boot recovery.img
They're attempting to flash a recovery but they've accidentally flashed a recovery to the boot partition which will obviously mean the device can't boot. This is just an example I'm using to highlight the fact that you are your own safety barrier when flashing via fastboot, if you get it wrong, there's a high chance of bricking.
This particular user has flashed a recovery to the recovery partition but because the recovery is for another device it has corrupted the recovery partition and probably the other partitions too.
Sent from my Evita

I got a Jtagg on my phone and it was saved.

Not ever remotely relevant.
Sent from my Evita

Installed TWRP to Boot, want to boot myself in the a**.

Own the OPP6; Rooted, on OxygenOS 5.18.
Went to install the newest TWRP (was going to install XXX no limits), when asked where to install it to, accidentally, without thinking, hit install to Boot.
Problems.
I can get into fastboot, the PC sees the phone in fastboot.
Have tried to flash a recovery image and similar, got an error saying: FAILED (remote: (recovery_b) No such partition).
Just want to get the phone booting again, wipe the whole thing start over, from fastboot.
Any help appreciated.

https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892

Thank you, the tool worked like a charm.
BTW: I did search and find other "methods" but none of them worked

noncomjd said:
Own the OPP6; Rooted, on OxygenOS 5.18.
Went to install the newest TWRP (was going to install XXX no limits), when asked where to install it to, accidentally, without thinking, hit install to Boot.
Problems.
I can get into fastboot, the PC sees the phone in fastboot.
Have tried to flash a recovery image and similar, got an error saying: FAILED (remote: (recovery_b) No such partition).
Just want to get the phone booting again, wipe the whole thing start over, from fastboot.
Any help appreciated.
Click to expand...
Click to collapse
What you should have done was fastboot boot twrp.img. which would start twrp, then you could have used the installer in to install twrp on phone. After that you would have to installed stock or custom kernel.

MrSteelX said:
What you should have done was fastboot boot twrp.img. which would start twrp, then you could have used the installer in to install twrp on phone. After that you would have to installed stock or custom kernel.
Click to expand...
Click to collapse
That is exactly what I wanted to do.
I could get into TWRP, but I couldn't see the phone on the PC and couldn't move files (ROM) to the phone (although fastboot was working and I could see the device using adb) but I couldn't figure out how to have TWRP look for or find the ROM on the PC.

There's no recovery partition on A/B phones remember.

RusherDude said:
There's no recovery partition on A/B phones remember.
Click to expand...
Click to collapse
Thanks for that. and that explains a few things and explains why when I installed TWRP, I didn't see the recovery option. Doesn't pardon my hitting install to Boot.
Just thought of another Q, if there is no recovery partition, where is the OEM recovery stored? (I figured the lack of a recovery partition is why TWRP gets overwritten if installed without a custom ROM)
I did a quick read on that, it seems really interesting and may be of some use as soon as I learn more.
I've got so much to learn about this. I keep meaning to take time to begin, but stuff comes up and boom more changes.
I've got to do more reading to take advantage of that.
@MrSteelX mentioned that I could have used TWRP to install a ROM from the PC.
Is this what is referred to as "sideloading". I've been looking for some info on this and haven't really come across much that is any good.
Are there any available guides that anyone can point to so I can learn about using TWRP that way?

noncomjd said:
Thanks for that. and that explains a few things and explains why when I installed TWRP, I didn't see the recovery option. Doesn't pardon my hitting install to Boot.
Just thought of another Q, if there is no recovery partition, where is the OEM recovery stored? (I figured the lack of a recovery partition is why TWRP gets overwritten if installed without a custom ROM)
I did a quick read on that, it seems really interesting and may be of some use as soon as I learn more.
I've got so much to learn about this. I keep meaning to take time to begin, but stuff comes up and boom more changes.
I've got to do more reading to take advantage of that.
@MrSteelX mentioned that I could have used TWRP to install a ROM from the PC.
Is this what is referred to as "sideloading". I've been looking for some info on this and haven't really come across much that is any good.
Are there any available guides that anyone can point to so I can learn about using TWRP that way?
Click to expand...
Click to collapse
In twrp, you go to advance/sideload. Twrp then waits for adb sideload to push file to phone then auto flashes file.
In your case, you would sideload rom to flash and have been go to go.

noncomjd said:
Own the OPP6; Rooted, on OxygenOS 5.18.
Went to install the newest TWRP (was going to install XXX no limits), when asked where to install it to, accidentally, without thinking, hit install to Boot.
Problems.
I can get into fastboot, the PC sees the phone in fastboot.
Have tried to flash a recovery image and similar, got an error saying: FAILED (remote: (recovery_b) No such partition).
Just want to get the phone booting again, wipe the whole thing start over, from fastboot.
Any help appreciated.
Click to expand...
Click to collapse
If you have working fastboot mode and getting detected via fastboot then
fastboot flashable stock rom via fastboot mode.
U don't have to do anything just downloaded zip file unzip it any folder u want. Connect u r phone to. Computer in fastboot mode
Then go to that folder and just click flash all bat waut for 10to 15 min and then phone boots in working oos.
(all data will be get wipes after this)
Link
https://www.google.co.in/amp/s/foru...m-stock-fastboot-roms-oneplus-6-t3796665/amp/

MrSteelX said:
In twrp, you go to advance/sideload. Twrp then waits for adb sideload to push file to phone then auto flashes file.
In your case, you would sideload rom to flash and have been go to go.
Click to expand...
Click to collapse
Thanks.
I will give this a try. After I learn a little more about the A/B partitions & recovery on this phone, I want to try one on the custom ROMs.

pankspoo said:
If you have working fastboot mode and getting detected via fastboot then
fastboot flashable stock rom via fastboot mode.
U don't have to do anything just downloaded zip file unzip it any folder u want. Connect u r phone to. Computer in fastboot mode
Then go to that folder and just click flash all bat waut for 10to 15 min and then phone boots in working oos.
(all data will be get wipes after this)
Link
https://www.google.co.in/amp/s/foru...m-stock-fastboot-roms-oneplus-6-t3796665/amp/
Click to expand...
Click to collapse
Thanks for the link/guide. I had been trying an iteration of this (and the guide) but after reading your link, it too explains some things. I was trying to restore a Stock ROM from fastboot according to your link:
Things are changing with the advent of project treble. OnePlus will no longer release ROMs flashable via recovery (either stock or twrp) because is no more needed. The updates will be done on the slot not used for example if you are using slot a the update will be installed on slot b and the slot b will be set as default. If you brick and you are in bootloop how you can restore the rom? You can't with Stock ROM you have, because the zip can be only installed via Update Engine, so what can you do? Flash a stock rom via fastboot. I have extracted all images from the stock zip and i have made a new zip with the Fastboot ROM with a flash-all.bat included. This will work only if your bootloader is unlcoked. This will erase all your data and will wipe
I download and was trying to use the stock ROMs, I didn't see any bats, and now I know why.
Lots more reading to do. I love doing playing with this stuff, but trying to learn & keep up with things burns time, which most days I don't have.
This is the longest I've ever been on a stock OS (6 weeks? got the phone right after its release) although it's rooted (can never leave things completely alone).

noncomjd said:
Thanks for the link/guide. I had been trying an iteration of this (and the guide) but after reading your link, it too explains some things. I was trying to restore a Stock ROM from fastboot according to your link:
Things are changing with the advent of project treble. OnePlus will no longer release ROMs flashable via recovery (either stock or twrp) because is no more needed. The updates will be done on the slot not used for example if you are using slot a the update will be installed on slot b and the slot b will be set as default. If you brick and you are in bootloop how you can restore the rom? You can't with Stock ROM you have, because the zip can be only installed via Update Engine, so what can you do? Flash a stock rom via fastboot. I have extracted all images from the stock zip and i have made a new zip with the Fastboot ROM with a flash-all.bat included. This will work only if your bootloader is unlcoked. This will erase all your data and will wipe
I download and was trying to use the stock ROMs, I didn't see any bats, and now I know why.
Lots more reading to do. I love doing playing with this stuff, but trying to learn & keep up with things burns time, which most days I don't have.
This is the longest I've ever been on a stock OS (6 weeks? got the phone right after its release) although it's rooted (can never leave things completely alone).
Click to expand...
Click to collapse
I have to unzip the downloaded fastboot ROM at any folder on computer and open that folder u will see named [flash all bat]
Now connect phone in fastboot mode to computer and just click [flash all bat] file

noncomjd said:
Thanks for that. and that explains a few things and explains why when I installed TWRP, I didn't see the recovery option. Doesn't pardon my hitting install to Boot.
Just thought of another Q, if there is no recovery partition, where is the OEM recovery stored? (I figured the lack of a recovery partition is why TWRP gets overwritten if installed without a custom ROM)
I did a quick read on that, it seems really interesting and may be of some use as soon as I learn more.
I've got so much to learn about this. I keep meaning to take time to begin, but stuff comes up and boom more changes.
I've got to do more reading to take advantage of that.
@MrSteelX mentioned that I could have used TWRP to install a ROM from the PC.
Is this what is referred to as "sideloading". I've been looking for some info on this and haven't really come across much that is any good.
Are there any available guides that anyone can point to so I can learn about using TWRP that way?
Click to expand...
Click to collapse
"recovery" (what's left of it... wipe and mostly nothing else) is inside the boot partition. TWRP on those devices is installed into the boot partition (NOT overwriting the boot partition, but into the "ramdisk", a part of the kernel where OEM recovery resides and where TWRP, Magisk, Xposed and all the mods do their stuff on the kernel. On a phone with A/B partitions, you have to fastboot BOOT twrp, and then you have to flash the installer zip, you should never ever flash the image to any partition since there isn't any.

RusherDude said:
"recovery" (what's left of it... wipe and mostly nothing else) is inside the boot partition. TWRP on those devices is installed into the boot partition (NOT overwriting the boot partition, but into the "ramdisk", a part of the kernel where OEM recovery resides and where TWRP, Magisk, Xposed and all the mods do their stuff on the kernel. On a phone with A/B partitions, you have to fastboot BOOT twrp, and then you have to flash the installer zip, you should never ever flash the image to any partition since there isn't any.
Click to expand...
Click to collapse
Thanks for the information.
and this is what I did, originally I thought I had accidentally selected the wrong partition, but it seems since there is no recovery partition, I did it wrong from the start.
Q: I'm guessing this is why when you do load TWRP (the correct way, which I did once, following a guide) without a custom ROM (still using Oxygen OS) that the OEM recovery overwrites TWRP or the OEM recovery is called up at the next reboot into recovery?
Q: I understand, at least in theory the benefit of the A/B partitions, what is the benefit of eliminating the recovery partition other than giving more control of the phone to the OEM and OS? Is this setup limited to the stock kernel or mandated to be copied by any potential replacement kernels (this information is new to me, I haven't yet read up on kernels).

Mi mix 3 Global ROM bootloop

I'll start by apologizing if this has been solved elsewhere I have searched but found no answers.
I have the global variant and was rooted with twrp. I wanted the ota update so I unrooted and updated. Today I had some time so I flashed twrp wiped and entered bootloop. I attempted a full factory reset through twrp but still bootlooped. I have fastboot rom and have attempted to use miflash to fix it but get the "cannot found lock.bat" error though when first starting miflash I get the "can't find flash script" error. The drivers are properly installed yet the error persists. I cannot get adb to sideload which is, I'm guessing because of the wipe removing debugging mode? Is there any way to get the ROM image to the phone(I tried adb push command but says no device. Yet flashing recovery works so I know it's connected and recognized) so I can flash it via TWRP or the stock recovery img to flash and work from there? I'm kind of at a loss here. Am I now the proud owner of a very neat paper weight? I seriously hope not as I'm not exactly made of money and I've only owned the phone for a couple months.
Any and all help is greatly appreciated.

Update
I have managed to get adb push to start sending global v10.2.2.0 to the root folder. I'm hoping this will allow me to flash from twrp.
Mota420 said:
I'll start by apologizing if this has been solved elsewhere I have searched but found no answers.
I have the global variant and was rooted with twrp. I wanted the ota update so I unrooted and updated. Today I had some time so I flashed twrp wiped and entered bootloop. I attempted a full factory reset through twrp but still bootlooped. I have fastboot rom and have attempted to use miflash to fix it but get the "cannot found lock.bat" error though when first starting miflash I get the "can't find flash script" error. The drivers are properly installed yet the error persists. I cannot get adb to sideload which is, I'm guessing because of the wipe removing debugging mode? Is there any way to get the ROM image to the phone(I tried adb push command but says no device. Yet flashing recovery works so I know it's connected and recognized) so I can flash it via TWRP or the stock recovery img to flash and work from there? I'm kind of at a loss here. Am I now the proud owner of a very neat paper weight? I seriously hope not as I'm not exactly made of money and I've only owned the phone for a couple months.
Any and all help is greatly appreciated.
Click to expand...
Click to collapse

Update 2 phone working but still confused.
Pushing the ROM via ADB did indeed allow me to flash from twrp and restore the phone. My question now is why did it happen? Is the new OTA MIUI 10.3... update incompatible with twrp or did something anomalous happen with the flash? I flashed exactly the same method I used with the 10.2.2 ROM a few weeks ago....

OTA's should only be used when completely stock! Even though you uninstalled root, there were still system modifications that more than likely caused your issues. The fastboot version of the firmware is different than the TWRP image. You can not flash a TWRP image via fastboot, hence the missing scripts and bat files. If you had actually downloaded the fastboot image, you would have had a flash_all.bat file that would have returned your device completely to stock with a single run of that file.

Thanks for the reply and information. I actually expected my issues to begin upon installing the ota update and was quite surprised that it updated without error. What confuses me is how flashing twrp after the update caused the issues. I went through the normal process when flashing twrp and still ended up bootlooped. I made the mistake of thinking boot.img was the old stock recovery i renamed when i first rooted and flashing that as recovery. Obviously this was not the recovery file but fastboot. It was then that panic mode kicked in and things went from bad to worse. I formatted planning to flash the stock rom via adb which didn't work. Given that I never touched the fastboot image on the phone I'm confused on how the bat files and scripts weren't found.
I'll admit I'm not extremely well versed in this area.
Is it possible that the ota update contained different bat files and scripts than the previous rom had? Which would cause miflash to not recognize them when attempting to flash an older rom? I'm sorry if my questions are ignorant lol. I'm a process guy and a troubleshooter by nature which means even though I've resolved the issue, I need to figure out what caused it.
Would flashing fastboot to the phone as the recovery image have screwed up the bat and scripts? Having two instances of boot.img on the partition messed it up maybe? Was it the formatting even though I was still able to boot into fastboot after? Or was it something that happened during the unrooting and updating that messed it up and it didn't manifest until I flashed twrp? Like I said the update worked fine and the phone was fully functional until I tried to reroot.
Thanks again for taking the time to help. It's definitely appreciated.

Mota420 said:
Thanks for the reply and information. I actually expected my issues to begin upon installing the ota update and was quite surprised that it updated without error. What confuses me is how flashing twrp after the update caused the issues. I went through the normal process when flashing twrp and still ended up bootlooped. I made the mistake of thinking boot.img was the old stock recovery i renamed when i first rooted and flashing that as recovery. Obviously this was not the recovery file but fastboot. It was then that panic mode kicked in and things went from bad to worse. I formatted planning to flash the stock rom via adb which didn't work. Given that I never touched the fastboot image on the phone I'm confused on how the bat files and scripts weren't found.
I'll admit I'm not extremely well versed in this area.
Is it possible that the ota update contained different bat files and scripts than the previous rom had? Which would cause miflash to not recognize them when attempting to flash an older rom? I'm sorry if my questions are ignorant lol. I'm a process guy and a troubleshooter by nature which means even though I've resolved the issue, I need to figure out what caused it.
Would flashing fastboot to the phone as the recovery image have screwed up the bat and scripts? Having two instances of boot.img on the partition messed it up maybe? Was it the formatting even though I was still able to boot into fastboot after? Or was it something that happened during the unrooting and updating that messed it up and it didn't manifest until I flashed twrp? Like I said the update worked fine and the phone was fully functional until I tried to reroot.
Thanks again for taking the time to help. It's definitely appreciated.
Click to expand...
Click to collapse
OTA's are not a complete image. It is a partial update that only replaces what it has to replace. If MiFlash dis not recognize the image, it was either the wrong image or a corrupt image.
Sometimes updates to the system and recovery partitions fix exploits that things like root and TWRP take advantage of.
Fastboot isn't something you flash to the phone. It is a command line used to flash a dull factory image to the device properly. You do not need MiFlash to flash a fastboot factory image. All you do is extract the full image to your ADB folder unless it is system wide, boot your device into the bootloader, connect ir to your PC, and run the flash_all.bat command contained in the folder you extracted. A command prompt window will open, everything will complete after about a few minutes the window will close, and your phone will reboot.

So the "fastboot" rom is a rom designed to be flashed using fastboot? The miflash error was given because the rom I was trying to flash was corrupted. That makes sense as I'd never known of a fastboot rom before. But it has been a few years since I rooted and romd my phone. I always did the typical flash from the rom image from twrp. I'm still not sure how I got myself in a boot loop unless when I wiped after flashing twrp I accidentally selected another option that erased more than I wanted.. Which makes perfect sense. I knew it had to be an ID10T error lol.
Thanks for the explanation.

Broken Persist.img Problems

I have the T-Mobile OnePlus 8. SIM/BL unlocked, converted to international firmware. FP worked the whole time during the conversion. Had issues with the modem, but that's a given an was sorted out.
I heavily rely on Google Pay because I'm lazy and rarely carry my wallet with me. I ended up installing EdXposed to see what has changed since the last time I used it years ago. There was a XStadia module that came in handy so that I could use Stadia on my data connection instead of WiFi. After using it for some time, I decided that having Xposed wasn't worth breaking SafetyNet over, so I uninstalled. Well for some reason, it didn't uninstall probably or something happened along the way that SN was still broken. So I figured the only way to fix is to factory data reset. Bad idea. These devices nowadays aren't like what they used to be. Ended up with multiple CrashDump screens. Ran into a crap ton of issues so I ended up used my the MSM tool to go back to the stock T-Mobile firmware, using the 10.5.7 fastboot ROM to go back to international, etc.
When I went back to international again, I noticed that my fingerprint sensor wasn't working so I followed the guide found here: https://forum.xda-developers.com/oneplus-8/how-to/guide-fix-persist-img-loss-finger-print-t4126455 The only thing I wasn't able to do was downgrade to an earlier OOS like 10.5.4 mentioned in the guides OP due to the phone not letting me. I tried the MSM 10.5.4 tool, and the 10.5.4 fastboot ROM. Both didn't work and gave me errors (I'm guessing because it's a branded device and certain critical partitions can't be overwritten). So I ended up pulling my broken persist from the T-Mobile stock rooted firmware, fastboot flashed 10.5.7, and went from there.
After some time, I finally had a working FP. Thanks again @antnyhills. When it was working, I thought that every time I used the FP, it gave me more errors than it actually unlocked the phone. So, I thought I'd be a little curious and see if doing the FP tests again would fix it. IT DID NOT. I ended up breaking it so bad, that now I get an error saying "fingerprint hardware not present". When I go to setup a new fingerprint, it says "enrollment was not completed. Fingerprint sensor error, please try again". If I go back to dismiss the error, the FP is still present, and when I press on it, the circle lights up, it just doesn't vibrate or register anything.
So, I followed the guide again. Again, nothing. Now I'm sitting here and nothing works. Camera doesn't work (black screen when opening), flashlight doesn't work, and I'm sure there's a few other things, just didn't mention. What do I do now? Get a hold of OnePlus and see if they'll replace my device? Is there a way to erase the Persist.img from the device and reflash it again somehow?
TL;DR: FP sensor broken, camera broken, after following broken persist.img guide.

antnyhills said:
Make sure you are using your original persist.img from your backup the first time you did this guide to transfer the two folders. If that fails. Flash your the same original back up persist.img and start the guide again.
Click to expand...
Click to collapse
Make sure you are using your original persist.img from your backup the first time you did this guide to transfer the two folders. If that fails. Flash your the same original back up persist.img and start the guide again.
If you get it working again, the FP sensor just as accurate as it was out of the box because you are using the factory calibrations.
When you set up your fingerprint it is not accurate at first but over time in learns you fingerprint even more and becomes more accurate and fast.

antnyhills said:
Make sure you are using your original persist.img from your backup the first time you did this guide to transfer the two folders. If that fails. Flash your the same original back up persist.img and start the guide again.
Click to expand...
Click to collapse
I did, multiple times to no avail. How do I go about flashing the persist.img? There are only a few options in TWRP. Two super, recovery, and boot.
I know, I remember reading somewhere that it learns every time. I should've just left it alone and let it do its thing, but of course I had to go and mess things up.
Is my flashlight and camera not working because of persist files?
When I got it working again using your guide, when I started tinkering around, even though my FP was working, when I rebooted, it said"fingerprint hardware not present". Now all of the apps that use FP don't even ask me if I want to use FP like it's not even there .

TheKnux said:
I did, multiple times to no avail. How do I go about flashing the persist.img?
Click to expand...
Click to collapse
Go to the bootloader.
Code:
fastboot reboot fastboot
This will take you to fastbootd. It will look like your recovery. You must have stock original recovery installed. TWRP will not work.
Code:
fastboot flash persist [INSERT YOUR PERSIST.IMG HERE]
Example:
Code:
fastboot flash persist C:\user\example\desktop\persist.img
Make sure you are flashing the persist.img from your original time you performed this guide. This will take you back to were you where before you ever performed the guide.
Then follow the guide one more time, follow it VERY CAREFULLY as there is a lot to go wrong.
Best of luck!
Edit: Also, I would assume your camera/flashlight broke because of your persist partition. Hence Why we are going to start from scratch with your original broken persist.img

antnyhills said:
Go to the bootloader.
This will take you to fastbootd. It will look like your recovery. You must have stock original recovery installed. TWRP will not work.
Example:
Make sure you are flashing the persist.img from your original time you performed this guide. This will take you back to were you where before you ever performed the guide.
Then follow the guide one more time, follow it VERY CAREFULLY as there is a lot to go wrong.
Best of luck!
Edit: Also, I would assume your camera/flashlight broke because of your persist partition. Hence Why we are going to start from scratch with your original broken persist.img
Click to expand...
Click to collapse
I'm not a noob at rooting/ROMing. I'm just new at doing this kind of stuff. Messing with critical files in the root directory. I appreciate you chiming in and helping me with this. I'll do what you said and report back. Appreciate everything you've done, including you helping me with this.

TheKnux said:
I'm not a noob at rooting/ROMing. I'm just new at doing this kind of stuff. Messing with critical files in the root directory. I appreciate you chiming in and helping me with this. I'll do what you said and report back. Appreciate everything you've done, including you helping me with this.
Click to expand...
Click to collapse
No worries. Eager to hear your update.

antnyhills said:
No worries. Eager to hear your update.
Click to expand...
Click to collapse
target reported max download size of 805306368 bytes
sending 'persist' (32768 KB)...
OKAY [ 0.703s]
writing 'persist'...
FAILED (remote: Flashing is not allowed for Critical Partitions
)
finished. total time: 0.718s
That is my error I get when following your instructions.

TheKnux said:
target reported max download size of 805306368 bytes
sending 'persist' (32768 KB)...
OKAY [ 0.703s]
writing 'persist'...
FAILED (remote: Flashing is not allowed for Critical Partitions
)
finished. total time: 0.718s
That is my error I get when following your instructions.
Click to expand...
Click to collapse
Make sure you do
Code:
fastboot reboot fastboot
Like I mentioned it should look like the stock recovery. When you do that does it take you to your stock recovery?
If you have discord, I'll PM you a link, might be easier to communicate.

antnyhills said:
Make sure you do
Code:
fastboot reboot fastboot
Like I mentioned it should look like the stock recovery. When you do that does it take you to your stock recovery?
If you have discord, I'll PM you a link, might be easier to communicate.
Click to expand...
Click to collapse
So to my knowledge, stock recovery is the screen with the OnePlus logo, some chinese words, and English and Fastboot is the screen that says the SoC name, device state, etc.
I even tried "fastboot flash persist_critical persist.img" and it didn't work. Also, fastboot reboot fastboot doesn't do anything. Fastboot reboot bootloader sends me to fastboot. Using Windows 10/PowerShell.
I do have Discord but it runs like crap on my PC (old laptop) and since my phone is down currently, this is the only way to talk.

TheKnux said:
So to my knowledge, stock recovery is the screen with the OnePlus logo, some chinese words, and English and Fastboot is the screen that says the SoC name, device state, etc.
I even tried "fastboot flash persist_critical persist.img" and it didn't work.
I do have Discord but it runs like crap on my PC (old laptop) and since my phone is down currently, this is the only way to talk.
Click to expand...
Click to collapse
Boot phone
Put persist.img on the root of your 'sdcard'
Code:
adb shell
Code:
su
Code:
dd if=/sdcard/persist.img of=/dev/block/bootdevice/by-name/persist
reboot

antnyhills said:
Boot phone
Put persist.img on the root of your 'sdcard'
Code:
adb shell
Code:
su
Code:
dd if=/sdcard/persist.img of=/dev/block/bootdevice/by-name/persist
reboot
Click to expand...
Click to collapse
Okay, that seems to have worked. I did that while on T-Mobile firmware. I just fastboot flashed the 10.5.7 international firmware, updating to 10.5.9 via OTA now, when it reboots, I'm going to install TWRP and Magisk, and push the persist.img again using the command you gave me once more for good measure then fix FP using your guide. On the flip side, once I pushed the persist.img using your command, my flashlight and camera works again, just not FP, yet. I'll report back after following your guide. Thank you again.

TheKnux said:
So to my knowledge, stock recovery is the screen with the OnePlus logo, some chinese words, and English and Fastboot is the screen that says the SoC name, device state, etc.
I even tried "fastboot flash persist_critical persist.img" and it didn't work. Also, fastboot reboot fastboot doesn't do anything. Fastboot reboot bootloader sends me to fastboot. Using Windows 10/PowerShell.
I do have Discord but it runs like crap on my PC (old laptop) and since my phone is down currently, this is the only way to talk.
Click to expand...
Click to collapse
You need to have the latest version of adb and fastboot from Google on your PC for "fastboot reboot fastboot" to work and be able to access fastbootd.
https://developer.android.com/studio/releases/platform-tools
Fastbootd is something new and different from bootloader. It allows flashing to all partitions (required due to dynamic partitioning in Android 10). However, it looks very similar to stock recovery (it actually uses stock recovery which is why it won't work with TWRP flashed). "fastboot reboot bootloader" sends you to bootloader, which is no longer the same as fastboot.
However, the instructions posted by @antnyhills will also work perfectly fine for restoring persist. That's the method I use (personally I try to avoid fastboot flash at all on this phone)
Your problem is you completely corrupted your persist.img. That's why you have a backup . Or now you'd be without sensors, camera, flashlight, etc until someone posted theirs but then you would never be able to fix fingerprint.
Once you have fingerprint working again, take a new backup of persist. Then no need to fix it again in the future if it gets messed up. Simply restore it.

starcms said:
You need to have the latest version of adb and fastboot from Google on your PC for "fastboot reboot fastboot" to work and be able to access fastbootd.
https://developer.android.com/studio/releases/platform-tools
Fastbootd is something new and different from bootloader. It allows flashing to all partitions (required due to dynamic partitioning in Android 10). However, it looks very similar to stock recovery (it actually uses stock recovery which is why it won't work with TWRP flashed). "fastboot reboot bootloader" sends you to bootloader, which is no longer the same as fastboot.
However, the instructions posted by @antnyhills will also work perfectly fine for restoring persist. That's the method I use (personally I try to avoid fastboot flash at all on this phone)
Your problem is you completely corrupted your persist.img. That's why you have a backup . Or now you'd be without sensors, camera, flashlight, etc until someone posted theirs but then you would never be able to fix fingerprint.
Once you have fingerprint working again, take a new backup of persist. Then no need to fix it again in the future if it gets messed up. Simply restore it.
Click to expand...
Click to collapse
I tried Googling for the latest adb/fastboot drivers but I already spent half the day restoring my persist and fixing my FP. I thought there would be a flasher like the 1.4.2 drivers but it wants me to install the sdk and install it through there. Not my top priority right now, next time I'm on my pc though I will for sure. The method @antnyhills told me to do to push the persist worked great, followed his guide again, fixed FP, and backed up persist with FP and all sensors working. Stored it in two places so I don't accidentally delete them lol. The updated drivers you're mentioning, that'll allow me to flash critical partitions in case I mess something up again next time?
Huge thanks to @antnyhills for coming in here and helping me out, and to you for giving me your two cents as well. I was so tempted to be a Karen and get T-Mobile and OnePlus on the phone to RMA my device. ?

TheKnux said:
I tried Googling for the latest adb/fastboot drivers but I already spent half the day restoring my persist and fixing my FP. I thought there would be a flasher like the 1.4.2 drivers but it wants me to install the sdk and install it through there. Not my top priority right now, next time I'm on my pc though I will for sure. The method @antnyhills told me to do to push the persist worked great, followed his guide again, fixed FP, and backed up persist with FP and all sensors working. Stored it in two places so I don't accidentally delete them lol. The updated drivers you're mentioning, that'll allow me to flash critical partitions in case I mess something up again next time?
Huge thanks to @antnyhills for coming in here and helping me out, and to you for giving me your two cents as well. I was so tempted to be a Karen and get T-Mobile and OnePlus on the phone to RMA my device.
Click to expand...
Click to collapse
It's not updated drivers. It's an updated version of adb and fastboot that fully supports all the new commands needed (such as "fastboot reboot fastboot"). I had provided a link. Just download and unzip to your adb directory on your PC and select replace all files when copying.
https://developer.android.com/studio/releases/platform-tools

starcms said:
It's not updated drivers. It's an updated version of adb and fastboot that fully supports all the new commands needed (such as "fastboot reboot fastboot"). I had provided a link. Just download and unzip to your adb directory on your PC and select replace all files when copying.
https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
Where would the adb directory be if I used the "adb and fastboot installer for windows" (or whatever it's called) found here on XDA? I'm guessing it's years old. I think it said version 1.4.2 or something.
Also, are you or @antnyhills on Telegram at all?

what was the final of this, i have the oneplus8 tmobile, and i want to convert to globla, but this issue scared me

Phone boots into fastboot, system files corrupted

Hi! My old phone is booting into fastboot mode, when I try to boot normally I get a black screen, the "Power off" button appears when I hold the power button. The bootloader is not unlocked and the phone was never rooted. Wiping the user partition does not help. It is visible in fastboot mode and I can enter stock recovery, though trying to adb sideload a stock rom returns an error (footer is wrong; signature verification failed). Trying to fastboot boot twrp or recovery.img doesn't work either. I've ran out of ideas, what should I do to get this phone to work?

Try flashing the stock ROM with fastboot. I'm pretty sure ADB doesn't let you flash onto your phone because using your phone with ADB means that it's still powered on - which can cause some issues. You can also try and unlock your bootloader through fastboot, and then flash a recovery and custom ROM.

Both failed. I attached the errors I recieved.

crepper4454 said:
Both failed. I attached the errors I recieved.
Click to expand...
Click to collapse
Try "fastboot bootloader unlock", maybe. Also: Is there a flashall.bat in the stock ROM folder? If there is: Connect your device while in fastboot, and double-click it.

crepper4454 said:
Both failed. I attached the errors I recieved.
Click to expand...
Click to collapse
Try this maybe. I know you can't wipe through the stock ROM, so, try the command: "fastboot -w". That'll wipe everything off the device.
[INDEX][Osprey][Merlin] Moto G Factory Firmware Images
Disclaimer: I am not responsible for anything that happens as a result of flashing these files. Your destiny is your own. Moto G (3rd Gen) Factory Firmware Images - Provided by Firmware TEAM - Please report broken links. New Mirrors welcome...
forum.xda-developers.com

I can wipe through stock recovery. I did fastboot -w and it cleared the cache and userdata partitions, they were already clean afaik. Typing fastboot bootloader unlock returns unknown command. There are no .bat files in my firmware. I can try downloading one from the site you linked, but I don't know what to do with it if fastboot flash does not work.

crepper4454 said:
I can wipe through stock recovery. I did fastboot -w and it cleared the cache and userdata partitions, they were already clean afaik. Typing fastboot bootloader unlock returns unknown command. There are no .bat files in my firmware. I can try downloading one from the site you linked, but I don't know what to do with it if fastboot flash does not work.
Click to expand...
Click to collapse
Try this: https://forum.xda-developers.com/t/guide-osprey-fastboot-flashing-factory-firmware-images.3187750/

It says there that the "preflash validation failed" error occurs when the firmware being flashed is older than the one already installed. I will try downloading a newer version and flashing it. Will update here.

Update: I have dowloaded a newer rom and tried to flash it. This time got different errors (picture attached, this went for every sparsechunk). I think I know the reason but I do not know how to solve it. This might not be the exact stock rom of this phone so I cannot flash it with a locked bootloader. Could someone help me finding the correct rom or suggest a different solution?

Yooooo. I have the Moto e5 Cruise and so does my wife. We bought them in 2018 from Cricket and last night hers went to emmc failure, also known scientifically as 'no worky' mode.
The phone would only load in fastboot and had tried to use my Moto RSD tool to reflash but the phone would not detect in anything but fastboot mode.. Here's where it gets interesting....
There is a piece of software called the Lenovo (which now owns Moto) Rescue and Smart Assistant that can reflash your phone back to factory, no matter your sub-variant (cricket, metro, etc). Without having a fresh backup on hand, you're going to be beholden to the last cloud sync or manual backup you have because all data will be wiped in the below process.
BTW: Just run the assistant as it seems to be the easiest 'back-to-stock/working' tool I can find. Going to fastboot alone yielded weird errors since i didn't have the unlock code for the 'fastboot oem unlock [code goes here]' command.
**RESTORATION PROCESS**
This will apply to multiple Lenovo/Moto Mobility devices. Unknown at this time how many have been impacted by this seemingly pre-planned failure on Lenovo's part.
If your phone is stuck in fastboot mode where MTK download mode does not load, nor does adb, follow these simple steps:
(NOTE: BACKUP YOUR FILES IF POSSIBLE)
1. Click the link above to be directed to the Lenovo software download page and run the installer on your PC (Sorry Mac users :'().
2. The software, once installed, will require you to sign up for OR link a google, fb, g+, etc account to it for purposes of creating a Lenovo ID. Once signed in, click on 'Rescue Now'.
3. With your phone in fastboot mode, allow the software to download the firmware for your phone.
4. Once the firmware has finished downloading and validating, click on 'Rescue Now' once again. Your phone will begin the reflashing process.

That... actually worked. The program found the required ROM and flashing went without problems. Thank you very much @kmt5150 .

crepper4454 said:
That... actually worked. The program found the required ROM and flashing went without problems. Thank you very much @kmt5150 .
Click to expand...
Click to collapse
No problemo! Glad it worked!