Database Info

I think I bricked my Xoom

I've looked through other posts about this and nothing seems to help. I went to actually UNroot my Xoom so I can install the latest update because I had no use for a root, but when I went to do fastboot flash system system.img with the stock .img file, it takes forever then gives me an error... I don't know how to get past this. I just want my Xoom back to normal, even if I can get it back to a rooted normal I can live with that.
(Also, the first first time I tried unrooting, I realized I used the wrong device files. I used the Verizon ones, when I only have WiFi.)
Somebody please help me, or I feel like I have an expensive paperweight.
Also, whenever I go to restart, I'm stuck at the boot logo screen and no matter which boot.img I flash, it won't go past it.

hocplyr98 said:
I've looked through other posts about this and nothing seems to help. I went to actually UNroot my Xoom so I can install the latest update because I had no use for a root, but when I went to do fastboot flash system system.img with the stock .img file, it takes forever then gives me an error... I don't know how to get past this. I just want my Xoom back to normal, even if I can get it back to a rooted normal I can live with that.
(Also, the first first time I tried unrooting, I realized I used the wrong device files. I used the Verizon ones, when I only have WiFi.)
Somebody please help me, or I feel like I have an expensive paperweight.
Also, whenever I go to restart, I'm stuck at the boot logo screen and no matter which boot.img I flash, it won't go past it.
Click to expand...
Click to collapse
Did you have ClockworkMod recovery installed? If so, do you know how to boot into CWM recovery? Disconnect from thr computer if connected, and press power and volume up to hard reboot and when you get to the dual core image, wait about three seconds, then press volume down and you should see android recovery in upper left corner, then press volume up and press power to select it.
I'm suggesting this in the hope that you did a nandroid backup before you decided to mess around and that you could somehow still access it.
If not, do you now have the correct system image files in your platforms or tools folder in order to flash from fastboot? Can you get to the "starting fastboot protocol?"
Look for your correct 3.2 wifi images here:
http://forum.xda-developers.com/showthread.php?t=1080963
Commands:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
Good luck!

okantomi said:
Can you get to the "starting fastboot protocol" screen?
Click to expand...
Click to collapse
yes if you somehow get into fast boot your problems can be solved.
I do not know whether by pressing vol up at boot time you can go to fastboot protocol screen.

okantomi said:
Did you have ClockworkMod recovery installed? If so, do you know how to boot into CWM recovery? Disconnect from thr computer if connected, and press power and volume up to hard reboot and when you get to the dual core image, wait about three seconds, then press volume down and you should see android recovery in upper left corner, then press volume up and press power to select it.
I'm suggesting this in the hope that you did a nandroid backup before you decided to mess around and that you could somehow still access it.
If not, do you now have the correct system image files in your platforms or tools folder in order to flash from fastboot? Can you get to the "starting fastboot protocol?"
Look for your correct 3.2 wifi images here:
http://forum.xda-developers.com/showthread.php?t=1080963
Commands:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
Good luck!
Click to expand...
Click to collapse
Not sure if I have CWM installed, but I can access fastboot and that's not really helping. I'll try again with the link you provided, but I'm able to flash everything BUT system.img. I'll try again and get back to you.
UPDATE: Yeah... It's doing the exact same thing. It's stuck at fastboot flash system system.img. It just says that it's sending it and it takes a long time before an error message pops up saying that there are too many links.
UPDATE UPDATE: Okay, now, even in fastboot, it doesn't let me flash boot.img. I don't know what to do anymore

hocplyr98 said:
Not sure if I have CWM installed, but I can access fastboot and that's not really helping. I'll try again with the link you provided, but I'm able to flash everything BUT system.img. I'll try again and get back to you.
UPDATE: Yeah... It's doing the exact same thing. It's stuck at fastboot flash system system.img. It just says that it's sending it and it takes a long time before an error message pops up saying that there are too many links.
UPDATE UPDATE: Okay, now, even in fastboot, it doesn't let me flash boot.img. I don't know what to do anymore
Click to expand...
Click to collapse
This is where you need to talk to the experts. Go to #xoom at freenode.net and get some assistance.

okantomi said:
This is where you need to talk to the experts. Go to #xoom at freenode.net and get some assistance.
Click to expand...
Click to collapse
Not very much help from the "experts" there. I was completely ignored, and nobody responded to me...

hocplyr98 said:
Not very much help from the "experts" there. I was completely ignored, and nobody responded to me...
Click to expand...
Click to collapse
It's impossible to brick a Xoom. You can make or buy a factory cable and flash stock images from Motorola and follow up with OTA upgrades or flash whatever custom stuff you desire. The below links should save your Xoom. Don't forget to hit the thanks button
http://forum.xda-developers.com/showthread.php?t=1077414
http://developer.motorola.com/products/software/?pubid=987654
http://forum.xda-developers.com/showthread.php?t=1108518

Although if you're going to give up and aren't comfortable to continue working with it I would be very interested in purchasing it, you can PM me if interested.

Saintfyre said:
Although if you're going to give up and aren't comfortable to continue working with it I would be very interested in purchasing it, you can PM me if interested.
Click to expand...
Click to collapse
Keep an eye out on ebay, I just got a xoom on there with launcher force closing repeatedly for $264
Sent from my ADR6400L using XDA App

davidsos said:
It's impossible to brick a Xoom. You can make or buy a factory cable and flash stock images from Motorola and follow up with OTA upgrades or flash whatever custom stuff you desire. The below links should save your Xoom. Don't forget to hit the thanks button
http://forum.xda-developers.com/showthread.php?t=1077414
http://developer.motorola.com/products/software/?pubid=987654
http://forum.xda-developers.com/showthread.php?t=1108518
Click to expand...
Click to collapse
Not impossible but not as likely as you would think with the 100 "I think I bricked My xoom threads floating around.
To the OP...if you do not even know whether clockwork modified recovery is installed on your device then I am not sure you have the knowledge necessary to be messing with your device...I guess most people need to learn the hard way...

Oneplus has no OS installed.

Hello all
I have a baaaaad situation going on!
I have been trying to delete me superuser in twrp, but something terrible happened....
1) When i boot my 1+ it just stays black.
2) When i boot into fastboot it just shows a linux penguin logo and noting else.
3) When i go to twrp i can do multiple things like adb sideload, and i can push a rom to my phone.
-> but everytime i do this and try to install it, it just fails and says i have no OS installed when i want to reboot.
I've contacted support from 1+ but nothing yet so far...
Anyone here who can help me? (i'm open for teamviewer and even want to pay the person who can fix my Oneplus)
Hoping one of you can help me!
Greetz
Michel
(I have a picture of the logo but i can't post i due to beiing a new member here )

You can't communicate with your phone through fastboot and ADB? Oh ****...

How did you manage to replace the bootloader with a Linux penguin? When you go into fast boot and type does fast boot devices does the pc recognize the phone?
Sent from my One A0001 using Tapatalk

The thing is, i was rooting my device and after i've done that my rootchecker told me the root was incomplete...
So smart as i was i started a complete unroot, to do it all over again...
In this process my device got stuck... so i booted in TWRP recovery to uninstall everything from the root over there..
Here i managed to delete my complete OS.... 8-|
After reading every tutorial and guide i figured out that on my phone my developper otions were NOT enabled...
So i contacted the oneplus support, who even remotely connected to my computer from Beijing to Belgium.. but never the less my problem was not solved and i was still stuck on the f*cking Linux logo...
So i started searching for a flashable ROM (in this case i found Pacman Nightly Signed) to flash on my phone through command on Windows.
After many hours and even more attempts i managed to go in adb en flash it by the sideload way.
So not through "adb push romname.zip /sdcard...." but by "adb sideload romname.zip /sdcard...."
And the pacman rom started to install and booted my phone to language selection...
PS: i cried :cyclops:

Glad to hear that you fixed your phone. I wouldn't contact oneplus support for things like this, chances are you'll get a reply back from xda faster as well as searching on your own to resolve the issue.
Sent from my One A0001 using Tapatalk

OnePlus One no OS, no Charge and that stupid lunix penguin
:crying:So basically I have the same issue, I tried to install Oxygen OS and managed to remove my Entire operating system and format my entire sdcard so I've managed to push a few possible ROMs to my device and they won't install and it won't let me install any mof them and now I've lost the charge on my device.
Please tell me theirs something I can do to fix this.:crying:

Ashleigh.17 said:
:crying:So basically I have the same issue, I tried to install Oxygen OS and managed to remove my Entire operating system and format my entire sdcard so I've managed to push a few possible ROMs to my device and they won't install and it won't let me install any mof them and now I've lost the charge on my device.
Please tell me theirs something I can do to fix this.:crying:
Click to expand...
Click to collapse
Fast boot flash a TWRP image. Flash CM12 nightly via OTG. You will be good from there.
Hastily spouted for your befuddlement

Ashleigh.17 said:
:crying:So basically I have the same issue, I tried to install Oxygen OS and managed to remove my Entire operating system and format my entire sdcard so I've managed to push a few possible ROMs to my device and they won't install and it won't let me install any mof them and now I've lost the charge on my device.
Please tell me theirs something I can do to fix this.:crying:
Click to expand...
Click to collapse
More info required. What recovery do you have installed? Exactly what error are you getting when flashing the ROMs? You probably just need to flash the right firmware first.
Transmitted via Bacon

timmaaa said:
More info required. What recovery do you have installed? Exactly what error are you getting when flashing the ROMs? You probably just need to flash the right firmware first.
Transmitted via Bacon
Click to expand...
Click to collapse
I'm using TWRP
When I did manage to push some files to the device and tried to install them it failed instantly. I tried Cyan Hacker V2 the new Oxygen os and cm-11 and one of my backups, but all of them had the same issue. I can only vaguely remember the command which I think said 'partitions updating' then under the completed tab at the top of the screen in Red text it said failed.
This isn't my main concern anymore the device has died and won't charge so I can't get it to boot into fast boot or Recovery all its done when connected to the charger is light up with a black screen, vibrate then turn off, it repetats that a couple of times then it goes off again and no life at all, if I leave it of the charger for bit and try plugging it in again I get the same flashing black screen but again no charge.
---------- Post added at 10:09 AM ---------- Previous post was at 09:58 AM ----------
Coug76 said:
Fast boot flash a TWRP image. Flash CM12 nightly via OTG. You will be good from there.
Hastily spouted for your befuddlement
Click to expand...
Click to collapse
I'm having an issue gettjngit into fastboot its died and all I'm getting is a black flashing screen!
Any tips on how to get it to charge?

Ashleigh.17 said:
I'm using TWRP
When I did manage to push some files to the device and tried to install them it failed instantly. I tried Cyan Hacker V2 the new Oxygen os and cm-11 and one of my backups, but all of them had the same issue. I can only vaguely remember the command which I think said 'partitions updating' then under the completed tab at the top of the screen in Red text it said failed.
This isn't my main concern anymore the device has died and won't charge so I can't get it to boot into fast boot or Recovery all its done when connected to the charger is light up with a black screen, vibrate then turn off, it repetats that a couple of times then it goes off again and no life at all, if I leave it of the charger for bit and try plugging it in again I get the same flashing black screen but again no charge.
Click to expand...
Click to collapse
Yep, it's almost definitely a case of not having flashed the right firmware after coming from Oxygen. Leave it plugged in for eight hours, don't touch it in that time, then try to power it on again.
Transmitted via Bacon

timmaaa said:
Yep, it's almost definitely a case of not having flashed the right firmware after coming from Oxygen. Leave it plugged in for eight hours, don't touch it in that time, then try to power it on again.
Transmitted via Bacon
Click to expand...
Click to collapse
Okay I'll leave it through the day. After I get it to charge how will I get an OS onto it and how will I ensure that its got the right firmware? And if it all goes caput is this a valid reason for a renewed device from oneplus?

Ashleigh.17 said:
Okay I'll leave it through the day. After I get it to charge how will I get an OS onto it and how will I ensure that its got the right firmware? And if it all goes caput is this a valid reason for a renewed device from oneplus?
Click to expand...
Click to collapse
If you want to flash a Lollipop ROM the best way is to first perform a full wipe (system, data, cache, dalvik cache) in TWRP, then flash this firmware:
https://docs.google.com/file/d/0B98G0KTJwnBFdVgxZ0x5RzNJSE0/edit?usp=docslist_api
Then flash this modem:
https://docs.google.com/file/d/0B98G0KTJwnBFU0Z1TUIyVE50WW8/edit?usp=docslist_api
Then go to the reboot menu and reboot back to recovery. Then flash whatever Lollipop ROM you want to use, and reboot your phone. If you still have no success after doing that then you'll need to try to flash the stock images with fastboot, I have a download and instructions in section 8 of my guide thread:
http://forum.xda-developers.com/showthread.php?t=2839471
If that gets your phone booting then you can go ahead and try the above steps again to flash a Lollipop ROM.
No, this wouldn't be covered by warranty. Unlocking the bootloader and rooting this device doesn't void the warranty but they've stated that if you brick the phone while flashing (or the like) then it isn't covered. This is a case of user error, you didn't ensure that you had the correct firmware before flashing.
Transmitted via Bacon

timmaaa said:
If you want to flash a Lollipop ROM the best way is to first perform a full wipe (system, data, cache, dalvik cache) in TWRP, then flash this firmware:
https://docs.google.com/file/d/0B98G0KTJwnBFdVgxZ0x5RzNJSE0/edit?usp=docslist_api
Then flash this modem:
https://docs.google.com/file/d/0B98G0KTJwnBFU0Z1TUIyVE50WW8/edit?usp=docslist_api
Then go to the reboot menu and reboot back to recovery. Then flash whatever Lollipop ROM you want to use, and reboot your phone. If you still have no success after doing that then you'll need to try to flash the stock images with fastboot, I have a download and instructions in section 8 of my guide thread:
http://forum.xda-developers.com/showthread.php?t=2839471
If that gets your phone booting then you can go ahead and try the above steps again to flash a Lollipop ROM.
No, this wouldn't be covered by warranty. Unlocking the bootloader and rooting this device doesn't void the warranty but they've stated that if you brick the phone while flashing (or the like) then it isn't covered. This is a case of user error, you didn't ensure that you had the correct firmware before flashing.
Transmitted via Bacon
Click to expand...
Click to collapse
okay
thank you for all your help hopefully I'll be posting later with some good news

So I have gained access to the device in both TRWP and fastboot mode but I have encountered more problems,
Theirs is no OS, but their is a recovery the logical thing here would be boot it in fast boot and push files to the device and install those using the recovery easy right!!
no the boot loader is locked and so I can't flash anything I've downloaded about 2 or 3 tools kits to get it unlocked, when I use them the device reboots but wont load into fastboot, I can get it to with some tampering it doesn't have an exact method
any ideas guys?

Ashleigh.17 said:
So I have gained access to the device in both TRWP and fastboot mode but I have encountered more problems,
Theirs is no OS, but their is a recovery the logical thing here would be boot it in fast boot and push files to the device and install those using the recovery easy right!!
no the boot loader is locked and so I can't flash anything I've downloaded about 2 or 3 tools kits to get it unlocked, when I use them the device reboots but wont load into fastboot, I can get it to with some tampering it doesn't have an exact method
any ideas guys?
Click to expand...
Click to collapse
Why did you lock your bootloader? You need to go here:
http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
Flash that through TWRP and your bootloader will be unlocked again.
PS. You can't push files to the device in fastboot mode, only adb can push files and adb doesn't work in fastboot mode. Once you've unlocked your bootloader again you'll need to flash the stock images with fastboot. Download and instructions are in section 8 of my guide thread:
http://forum.xda-developers.com/showthread.php?t=2839471
Transmitted via Bacon

timmaaa said:
Why did you lock your bootloader? You need to go here:
http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
Flash that through TWRP and your bootloader will be unlocked again.
PS. You can't push files to the device in fastboot mode, only adb can push files and adb doesn't work in fastboot mode. Once you've unlocked your bootloader again you'll need to flash the stock images with fastboot. Download and instructions are in section 8 of my guide thread:
http://forum.xda-developers.com/showthread.php?t=2839471
Transmitted via Bacon
Click to expand...
Click to collapse
You HERO!!!!!!!!!!!!!!!!!!!
I actually love you right now thank you so much

Ashleigh.17 said:
You HERO!!!!!!!!!!!!!!!!!!!
I actually love you right now thank you so much
Click to expand...
Click to collapse
Lol, no worries, glad to help.

timmaaa said:
Lol, no worries, glad to help.
Click to expand...
Click to collapse
This is better than the best soapserie
....
Is he going to make it?
Yes
Great! :good:
Oooooh nooooo!!!
He's got a locked bootloader
Damn F*ING
This will never turn out right
OH, look here comes @timmaaa again
He says what? :silly:Really is it possible
Yes YES YYEEEEESSS
I did it, it's working again
I loooove you
:highfive::highfive::highfive:

I have similar issues at the moment. I tried to flash over Oxygen OS and it kept failing. Upon factory wiping the current OS to put CM 12 Nightly, I accidentally deleted all of my data. Now 54,xxx MB is on my phone, meaning it wiped all internal memory, the system is only 20MB and data is 6MB. I tried to plug in my phone to fast boot mode, and my computer wouldn't read it. I did all I could to maybe get it to read, and not a single thing popped up. I do not believe my bootloader is locked, but there could be a possibility that it could. Any suggestions to get an OS pushed over through ADB or Fastboot??

ElmoRapz said:
I have similar issues at the moment. I tried to flash over Oxygen OS and it kept failing. Upon factory wiping the current OS to put CM 12 Nightly, I accidentally deleted all of my data. Now 54,xxx MB is on my phone, meaning it wiped all internal memory, the system is only 20MB and data is 6MB. I tried to plug in my phone to fast boot mode, and my computer wouldn't read it. I did all I could to maybe get it to read, and not a single thing popped up. I do not believe my bootloader is locked, but there could be a possibility that it could. Any suggestions to get an OS pushed over through ADB or Fastboot??
Click to expand...
Click to collapse
It looks like you did the same thing that I did.
Its a pretty easy fix your going to be able to avoid all of the unlocking boot loader issues I had.
To begin with when your try an turn the device on is the screen flashing black?

[q] please help!!!

Okay, so this is going to sound kind of foolish, but I was going to try out the Android Lollipop final Developer Preview when I made some very foolish decisions. Firstly, a friend rooted my Nexus 5 and put TWRP on here, so I have personally never done it to a Nexus 5 (although I have done it to an original Kindle Fire). I downloaded a flashable ZIP of the Developer Preview and followed the standard protocol of doing a complete backup of everything. I flashed Lollipop, used it for a bit, then decided I wanted to return to KitKat until the final release. This is where things went badly wrong. In TWRP, I wiped everything accidentally. I then realized that TWRP had no way to mount USB Mass Storage.
At this point, I pulled up this page: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
I ran the "flash-all.BAT" file, which proceeded to wipe my bootloader (took TWRP out), everything. Now all it does is start in Fastboot mode (everything still unlocked), which is good, but that's all it does. Please help!!!

Checking product... FAILED
Device product is hammerhead
update requires grouper
Looks like you downloaded the wrong factory image. Download the hammerhead KK factory image and run the flash-all.bat just like above and you should be fine.
As long as you can still access your boot loader, you're fine.
Edit: you said "took out your bootloader" It did not. As you can see in your first image, it failed to write the bootloader. In the second image it confirms your bootloader is HHZ11k. Bootloader was not overwritten. As long as you can press power + volume down (or power + volume up and down) and get to the screen that shows an android along with your device info with start, power off, recovery mode options, that is your bootloader and your device is not bricked.
Just make sure to download the correct file this time.

Thank you so much!
This is exactly what the problem was! Thanks again for all your help!
RoyJ said:
Checking product... FAILED
Device product is hammerhead
update requires grouper
Looks like you downloaded the wrong factory image. Download the hammerhead KK factory image and run the flash-all.bat just like above and you should be fine.
As long as you can still access your boot loader, you're fine.
Edit: you said "took out your bootloader" It did not. As you can see in your first image, it failed to write the bootloader. In the second image it confirms your bootloader is HHZ11k. Bootloader was not overwritten. As long as you can press power + volume down (or power + volume up and down) and get to the screen that shows an android along with your device info with start, power off, recovery mode options, that is your bootloader and your device is not bricked.
Just make sure to download the correct file this time.
Click to expand...
Click to collapse

Glad I could help!

Please post questions in the Q&A section
You may also want to edit your thread title to so people know what you mean
Thread moved

RoyJ said:
Checking product... FAILED
Device product is hammerhead
update requires grouper
Click to expand...
Click to collapse
Good thing it has a check for bootloader version and device, and he didn't try flashing separately.. Otherwise it would've probably been a brick lol

If the wrong bootloader was written then I don't see how it wouldn't have bricked. If there's a way to recover from a corrupt bootloader, it's beyond my knowledge lol

RoyJ said:
If the wrong bootloader was written then I don't see how it wouldn't have bricked. If there's a way to recover from a corrupt bootloader, it's beyond my knowledge lol
Click to expand...
Click to collapse
If the secondary bootloader didn't get overwritten and you can boot into it, you can clone the secondary one to the primary one's partition. They're the same as far as we know and only a few people have successfully done it.
If you can't boot into it or you corrupted the secondary bootloader too, only LG can fix it

So if you fastboot flash a bootloader img does it only write the primary bootloader or both?

RoyJ said:
So if you fastboot flash a bootloader img does it only write the primary bootloader or both?
Click to expand...
Click to collapse
Not sure

I am not sure either, but I wouldn't really understand the point of a secondary if it got written at the same time as the primary. That said, I have seen stranger things, so who knows.

Question No OS even after flashing stock

So I've been pulling hair for 2 days. I can flash everything fine recovery boots fastboot. But it consistently says no OS on either slots. Tried flashing stock to both went all the way through loading lineage and same thing. I'm at wits end. Also not a single password I put in decrypts data.

Also Metro/Tmob variant xt2131-1 bootloader unlocked.

Have you tied fastboot -w? It sounds like the partitions are messed up.

I have. I've done all of the above just still a persistent boot loop.

Fandroid Tech said:
Have you tied fastboot -w? It sounds like the partitions are messed up.
Click to expand...
Click to collapse
Currently retrying to flash stock firmware with a Motorola flashing program. Will let you know here in about 2 min.

Fandroid Tech said:
Have you tied fastboot -w? It sounds like the partitions are messed up.
Click to expand...
Click to collapse
Yep. Again boot loop. Says no OS. Stock recovery says last installation failed. Flashing the service flash package to see if that makes a difference. Hopefully because it says it reflashed my bootloader and stock recovery.

Spedwardo said:
Yep. Again boot loop. Says no OS. Stock recovery says last installation failed. Flashing the service flash package to see if that makes a difference. Hopefully because it says it reflashed my bootloader and stock recovery.
Click to expand...
Click to collapse
The motorola program formats the partitions before flash unlike an automated fastboot flash. The only issue I can see is a physical issue with the UFS/EMMC 5.1 chip, maybe even the ram(very unlikely). Had there been any warning signs such as the phone rebooting randomly or freezing? Motorola has a one year warranty for all devices.

No nothing of the sort. I did a factory reset because I was gonna try out lineage and this is where I'm at now. Still no OS. Even after flashing 3 times. I did have a remote access trojan that rewrote my partition data and resized one and added one and used the root hidden partition to store the data in while it was being transferred.

This drive folder has the system, system_ext, vandor and product of the xt2131-1 that can be flashed in twrp or orangefox. Make sure you make the partitions rw in twrp or OF using 100 rw zip (search for it) then mount as rw in terminal. Flash these images or image,whichever you believe to be needing. Then try and reboot. If all else fails then download the firmware from LMSA and use tinyfastboot tools to flash it. Always worked for me. Let me know how it goes. Heres the link to the files.
XT2131-1_Denver-Osaka_04-2022_RRE31.60-47-2-2 - Google Drive
drive.google.com
!!!!!Make Sure you have verity and verification disabled before trying to flash these. Hence the 100 rw zip is necessary. And must be flashed correctly. 73 error can be flashed with Ubuntu!!!!!!!!
**Edit**
Make sure you always
Fastboot -w then
Factory reset in recovery then format data for a full clean install. This vendor build is made for the boost mobile variant but it is universal. The firmware is incremental based as well so it knows which build to install or activate on the tmo/metro variant. I have all the apps and files for all carriers that have this model.

sosthenisRR said:
This drive folder has the system, system_ext, vandor and product of the xt2131-1 that can be flashed in twrp or orangefox. Make sure you make the partitions rw in twrp or OF using 100 rw zip (search for it) then mount as rw in terminal. Flash these images or image,whichever you believe to be needing. Then try and reboot. If all else fails then download the firmware from LMSA and use tinyfastboot tools to flash it. Always worked for me. Let me know how it goes. Heres the link to the files.
XT2131-1_Denver-Osaka_04-2022_RRE31.60-47-2-2 - Google Drive
drive.google.com
!!!!!Make Sure you have verity and verification disabled before trying to flash these. Hence the 100 rw zip is necessary. And must be flashed correctly. 73 error can be flashed with Ubuntu!!!!!!!!
**Edit**
Make sure you always
Fastboot -w then
Factory reset in recovery then format data for a full clean install. This vendor build is made for the boost mobile variant but it is universal. The firmware is incremental based as well so it knows which build to install or activate on the tmo/metro variant. I have all the apps and files for all carriers that have this model.
Click to expand...
Click to collapse
If this doesnt work you can try a blankfile flash via edl, if that does not work nothing will.

Fandroid Tech said:
The motorola program formats the partitions before flash unlike an automated fastboot flash. The only issue I can see is a physical issue with the UFS/EMMC 5.1 chip, maybe even the ram(very unlikely). Had there been any warning signs such as the phone rebooting randomly or freezing? Motorola has a one year warranty for all devices.
Click to expand...
Click to collapse
Not at home. Staying the night at my mom's. Get home early tomorrow and I will try the advised steps. I went through my previous flashing steps and am now just missing the persist partition. I'll report back as for the edl mode and I have 2 blank flash files just cannot get into edl mode. Have qfil rsd and motoflashpro

Spedwardo said:
just cannot get into edl mode.
Click to expand...
Click to collapse
What have you tried thus far? Have you tried fastboot commands to get into edl, I think it may also also a boot menu option in twrp but I don't remember. Also now that I think about, after flashing the firmware(to both lots as you say) have you tried fastboot set_active a (or) b? Also where did you find the firehose file for it, I could not find one on other forums?

So far im downloading the files and will try what you suggested now. I'll let you know in 30 min. But I've tried factory reset. Flash. Formatting then flashing. Blank flash. Formatting then flashing. I've also used fastboot --force -slot=all flash ***. *****. Etc. Tried flashing. Flashing the copy partitions and tried flashing a gsi an aosp. Got to lineages recovery but still the same issue. Some partition are unmountable. At this point now it refuses to charge while off.. and if I do plug it in while off it continues to boot loop from the battery/charging screen.

Spedwardo said:
At this point now it refuses to charge while off.. and if I do plug it in while off it continues to boot loop from the battery/charging screen.
Click to expand...
Click to collapse
Sorry to tell you this but the phone is definitely ****ed on a hardware level, no amount of reflashing the firmware will fix that. The partition issue is likely caused by the EMMC/UFS malfunctioning, however the charging issue is definitely not caused by software as the battery has a separate controller. Your best bet would be to replace the motherboard, your phone's warranty is however void anyways since you unlocked the bootloader so you would have to do it yourself.

Fandroid Tech said:
Sorry to tell you this but the phone is definitely ****ed on a hardware level, no amount of reflashing the firmware will fix that. The partition issue is likely caused by the EMMC/UFS malfunctioning, however the charging issue is definitely not caused by software as the battery has a separate controller. Your best bet would be to replace the motherboard, your phone's warranty is however void anyways since you unlocked the bootloader so you would have to do it yourself.
Click to expand...
Click to collapse
How do I disable anti-rollback???? Might be the issue with it not flashing vb* files. Assuming those control vendor persiste etc

Spedwardo said:
How do I disable anti-rollback???? Might be the issue with it not flashing vb* files. Assuming those control vendor persiste etc
Click to expand...
Click to collapse
You can't, the manufacture prevents you from doing so due to "security issues". Make sure you get the latest firmware at https://mirrors.lolinet.com/firmware/moto/denver/official/. This will restore all partitions including vendor and persist as it generates from the modem partition, also android 11 and up does not use regular persist partitions anymore, it is now in the "super" images so don't worry about it. When you extract the latest firmware from this site there will be an XML file, go to https://forum.xda-developers.com/t/...e-with-motorola-devices.4042039/post-82186933 and follow the instructions, before flashing made sure to select slot A, after you are done flashing slot A set it to slot B and flash again, then reboot regularly. To set the slot run the fastboot command before flashing, for example fastboot set_active a, flash firmware, fastboot set_active b, flash firmware, reboot.

Question Bricked with no recovery. Please help

Long story short I messed up and now I don't have recovery. Only fastboot. Was bricked too before the no recovery thing.
How do I try to sort this? I don't have a pc either.
Using my old OnePlus 8T I was able to unlock, root and install a custom kernel.
Any ideas?

shadowofdeth said:
Long story short I messed up and now I don't have recovery. Only fastboot. Was bricked too before the no recovery thing.
How do I try to sort this? I don't have a pc either.
the good news is your phone can very likely be fixed. however in my experience you will need a computer. Folks here would love to help but knowing what device you are having an issue with would probably help with response to your situation. from fastboot you can boot a recovery image for your device and go from there. from fastboot you can also likely flash stock firmware to your device and start over fresh. It's also common to have to perform a factory reset after flashing the device to get it to properly boot.
Click to expand...
Click to collapse

OnePlus 9.
I tried searching but there are so many dead ends for finding the stock recovery. Even with that I'd still be bricked.
Where would one find the stock recovery, kernel and fastboot ready update.zip?

You do realize the boot.img is both recovery and kernel. Just extract it from payload.bin

MrSteelX said:
You do realize the boot.img is both recovery and kernel. Just extract it from payload.bin
Click to expand...
Click to collapse
If only I thought of that. It's not like I've been trying all day without success extracting what I need from the payload.bin. Definitely no dead ends there. Thanks for the massive help.

shadowofdeth said:
If only I thought of that. It's not like I've been trying all day without success extracting what I need from the payload.bin. Definitely no dead ends there. Thanks for the massive help.
Click to expand...
Click to collapse
borrow a laptop from someone , use the msm tool

taintsx said:
borrow a laptop from someone , use the msm tool
Click to expand...
Click to collapse
Im so close I can smell it now. Managed to get Python installed (had to deep dive into the comments on articles and tutorials) and have everything extracted in the last hour.
Now, for flashing these images I have to use Termux and it's working for the most part. My issue is now that I can flash one batch of images but not the other as per the xda guide linked now:
Restore OnePlus 9 to Stock via Fastboot Commands
This guide assumes you have the SDK Platform Tools installed and working, along with USB drivers for your device (if needed), and have your full update zip which you've already extracted the payload.bin from, and then dumped the images using...
forum.xda-developers.com
I keep getting errors about the partition being locked or something.
So close man. So close.

Locked partitions can only be flashed in fastbootd (fastboot reboot fastboot to get there).

First of all... Hold the both volume and power button for around 2 minutes. It'll take you to the bootloader mode. Then from the bootloader mode turn off your device then boot into edl then flash with msm.

Lesson learned