Database Info

[Q] I think I bricked the xoom after 4g upgrade??

- This is pretty much an exact duplicate of a thread I posted on Xoomfoums, but I think it maybe better here...
Anyway, really looking for a miracle!! I got my xoom back from Moto yesterday for the 4G upgrade and I tried to root the device the same way I have done before. I got as far as unlocking it. The last thing I flashed was a “bootloader_patch” from a guide on Xoomforums. Now I’m stuck and I only found one person who had this issue …… he returned his device for a new one
So summary thus far.
- I can get into Fastboot support and flashing always yields “success”.
- I seem to have no ADB connectivity. (don’t know if I really need it for fixing this issue since I can fastboot and flash).
- I have tried, stock images, CWM recoveries, rogue recoveries, also some HLK75 imgs, etc!! All leave me at the same place.
Where am I stuck:
- I reboot and let it go normally and she hangs at “Moto screen”
- I reboot and tap the “volume down” leaves our three choices….
-- Android recovery -> tried to enter recovery and sits at the famous “Reading ODM fuse:1”
-- Fastboot -> That works, I can flash from here OK
-- RSD support -> Haven’t played with that, I have read people going to dark places when they screw with this. If I have to I’ll do so carefully.
All the methods of going back to OEM are epic fails. Nothing new happens, but I am always left with the same result.
Any help you could lend would be greatly appreciated!! I really would rather truck through this than return it however I’m afraid if I don’t get rid of it soon it will be harder for me to make an excuse to the retailer.
Thanks - John

jadkar said:
- This is pretty much an exact duplicate of a thread I posted on Xoomfoums, but I think it maybe better here...
Anyway, really looking for a miracle!! I got my xoom back from Moto yesterday for the 4G upgrade and I tried to root the device the same way I have done before. I got as far as unlocking it. The last thing I flashed was a “bootloader_patch” from a guide on Xoomforums. Now I’m stuck and I only found one person who had this issue …… he returned his device for a new one
So summary thus far.
- I can get into Fastboot support and flashing always yields “success”.
- I seem to have no ADB connectivity. (don’t know if I really need it for fixing this issue since I can fastboot and flash).
- I have tried, stock images, CWM recoveries, rogue recoveries, also some HLK75 imgs, etc!! All leave me at the same place.
Where am I stuck:
- I reboot and let it go normally and she hangs at “Moto screen”
- I reboot and tap the “volume down” leaves our three choices….
-- Android recovery -> tried to enter recovery and sits at the famous “Reading ODM fuse:1”
-- Fastboot -> That works, I can flash from here OK
-- RSD support -> Haven’t played with that, I have read people going to dark places when they screw with this. If I have to I’ll do so carefully.
All the methods of going back to OEM are epic fails. Nothing new happens, but I am always left with the same result.
Any help you could lend would be greatly appreciated!! I really would rather truck through this than return it however I’m afraid if I don’t get rid of it soon it will be harder for me to make an excuse to the retailer.
Thanks - John
Click to expand...
Click to collapse
When it sits at "Reading ODM Fuse1" can you press power to see if it will select that option and take you into CWM recovery (assuming you have that installed)?
When you say you are flashing from fastboot protocol, are you connected to your pc? What are you flashing? I'm a bit lost with your description...

^^^
Thanks for the reply. Good suggestion on the power button.. press as its sitting at "Reading ODM fuse:1" but....... not good
So I didn't list all the things I have flashed because I tried many many fixes from multiple guides. I could look through all the links if you want the exact names but none of the made a difference. Yes, flashing from my PC connected via USB.
So after the first root guide blew it up I tried to flash a bunch of recoveries and system images. I also tried to bring her all the way back to OEM using the appropriate guide. No matter what I flashed I was given a successful message but it still gets stuck at the same screens. Nothing gives me any different results. I'm wondering if the actual bootloader is hosed. If so can you flash a new bootloader?
Here's some stuff I have flashed along with some links....
recovery-Tiamat-R4c-100611-1150-cwm.img
MZ600_HRI66_OEM_Image
how to root guide that I origianlly followed.... http://www.xoomforums.com/forum/mot...ow-root-3g-4g-wifi-only-xoom-stock-3-1-a.html
Someone got the build img after the LTE upgrade, so I tried this....
http://www.xoomforums.com/forum/xoo...rade-stuck-recovery-reading-odm-fuse-1-a.html
I also tried from fastboot erasing all the partitions before I flashed them and that didn't help.
Thanks for your time!!

jadkar said:
^^^
Thanks for the reply. Good suggestion on the power button.. press as its sitting at "Reading ODM fuse:1" but....... not good
So I didn't list all the things I have flashed because I tried many many fixes from multiple guides. I could look through all the links if you want the exact names but none of the made a difference. Yes, flashing from my PC connected via USB.
So after the first root guide blew it up I tried to flash a bunch of recoveries and system images. I also tried to bring her all the way back to OEM using the appropriate guide. No matter what I flashed I was given a successful message but it still gets stuck at the same screens. Nothing gives me any different results. I'm wondering if the actual bootloader is hosed. If so can you flash a new bootloader?
Here's some stuff I have flashed along with some links....
recovery-Tiamat-R4c-100611-1150-cwm.img
MZ600_HRI66_OEM_Image
how to root guide that I origianlly followed.... http://www.xoomforums.com/forum/mot...ow-root-3g-4g-wifi-only-xoom-stock-3-1-a.html
Someone got the build img after the LTE upgrade, so I tried this....
http://www.xoomforums.com/forum/xoo...rade-stuck-recovery-reading-odm-fuse-1-a.html
I also tried from fastboot erasing all the partitions before I flashed them and that didn't help.
Thanks for your time!!
Click to expand...
Click to collapse
Well, you are flashing wildly but not well, (JK)
This thread should help you:
http://forum.xda-developers.com/showthread.php?t=1299485
Here is a great post by Saintfyre (I think it fits the bill):
"Yeah join the FUBAR Club.
I was in the same boat as you did the same thing.
I now have my Xoom back to HLK75C and have 4G/3G and Wifi connectivity again so all is not lost!
What I did to fix my situation:
-I wiped the Device and just went through Solarnz's Root Method here: http://forum.xda-developers.com/showthread.php?t=1074979.
-Download the HLK75C (This is the build the 4G Xoom's shipped back with) file that AceXMachine provided here, post #6
-Extract the File to your Android SDK Platform-Tools folder, password is AceXMachine
-Follow his instructions to apply the images. I copy pasted but all credit goes to him for putting this out there.
On Windows shift and right click the Platform-Tools folder -> Open Command Window here.
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot erase cache
fastboot reboot
After following all of this I had my Xoom back just like it had come back from Moto after the upgrade. I've since then flashed the Tiamat Tachi OC GPU Kernel to have Overclocking again. No issues since then, have full 4G/3G Connectivity and Wifi has no issues as well."
From this thread:

Yup.....I tried that one as well, it didn't work either.
I really think the bootloader is shot. Is there a way to repair it? I think what killed this was the last .zip file I updated as part of the root guide I was using, it was "bootloader_patch.zip" found here..... Bootloader_patch Does anyone know what this does??
**edit: Is the boot.img the bootloader?? If so ... forget it as I already tried flashing a couple new ones during my attempts to bring it back to OEM.

So my logic now is rather than keep flashing like crazy let me try and get recovery working. For this I will try and erase everything using fastboot (my only option) and then flash a boot.img and a recovery.img
Questions:
- Will keeping everything earsed from the device except for a boot.img and a recovery.img allow me to get into recovery? I want the minimum amount of partitions flashed. I want to just work slowly and systematically trying to get into recovery first.
- I do not have ADB support, can this be a hint? Shouldn't adb support be working or do you need to have somthing in the system / app partition for ADB to communicate with. I know its called Android debugging bridge so the name makes me believe that I need an android OS loaded and this is why my ADB doesn't work.
Please take a look below and let me know if anyone has any suggestions on different boot.img or recovery.img Ihave not tried. Also, I'm wodnering which ones I should try in combination.
Going forward I'm going to keep track of each combination I try as to avoid duplicated / wasted effort.
recoveries I have tried:recovery-Tiamat-R4c-100611-1150-cwm.img
recovery image from steady Hawkin (3g/4g Stock Images for HR166)
Rogue-recovery image from rogue-recovery-1.2.0
Boot images I have tried:boot from steady Hawkin (3g/4g Stock Images for HR166)
boot from AxeMachine HLK75Csystemboot
boot from AxeMachine HLK42Bsystemboot4g

jadkar said:
So my logic now is rather than keep flashing like crazy let me try and get recovery working. For this I will try and erase everything using fastboot (my only option) and then flash a boot.img and a recovery.img
Questions:
- Will keeping everything earsed from the device except for a boot.img and a recovery.img allow me to get into recovery? I want the minimum amount of partitions flashed. I want to just work slowly and systematically trying to get into recovery first.
- I do not have ADB support, can this be a hint? Shouldn't adb support be working or do you need to have somthing in the system / app partition for ADB to communicate with. I know its called Android debugging bridge so the name makes me believe that I need an android OS loaded and this is why my ADB doesn't work.
Please take a look below and let me know if anyone has any suggestions on different boot.img or recovery.img Ihave not tried. Also, I'm wodnering which ones I should try in combination.
Going forward I'm going to keep track of each combination I try as to avoid duplicated / wasted effort.
recoveries I have tried:recovery-Tiamat-R4c-100611-1150-cwm.img
recovery image from steady Hawkin (3g/4g Stock Images for HR166)
Rogue-recovery image from rogue-recovery-1.2.0
Boot images I have tried:boot from steady Hawkin (3g/4g Stock Images for HR166)
boot from AxeMachine HLK75Csystemboot
boot from AxeMachine HLK42Bsystemboot4g
Click to expand...
Click to collapse
How have you flashed zip files without ClockworkMod recovery? It's hard to brick a Xoom but you may be close.
If there is anyway to flash your device's stock images through fastboot, that is your best hope at this point.

okantomi said:
How have you flashed zip files without ClockworkMod recovery? It's hard to brick a Xoom but you may be close.
If there is anyway to flash your device's stock images through fastboot, that is your best hope at this point.
Click to expand...
Click to collapse
Yeah, so I have another thread running on xoomforums and I have explained over there that just about 30 minutes ago I erased everything and reflashed the "HRI66" files. I used everything from that build so there was just the stock recovery, etc. I even did a fastboot oem lock. This didn't work either.
After this I was able to return to fastboot and "unlock", so now I am just back to where I was before.
Me and one other dude think I have a corrupetd / damaged partition or semi-destroyed bootloader. The thing is I can't get an answer to a real simple question.....
is the bootloader a "flashable" component?? I'm not sure if the boot.img IS the bootloader or the bootloader is something else that's not flashable at all. If the later is true then maybe my bootloader is FUBAR.
Thanks!! John

I'm the other guy jadkar was referring to from Xoomforums. He's pretty much put it succinctly but here's my version
ggrant & fish over at Xoomforums suggested we PM solarnz (etal) or post over here for help. I am writing this for myself and another Xoom user. We've both sent our Xoom's to Moto for the 4G upgrade, received them back with 3.2.2, and then proceded to root the wrong ROM over the top. The result was a hang at the red Logo. In hindsight, we should have used Universal Root.
We've both exhausted the experience at Xoomforum (hence our plea here Anything you can suggest would be most appreciated. Personally, I think something is awry in the recovery partition size (perhaps changed by Moto at the upgrade?):
To save the basic suggestions off the bat, we've done the expected already: Installed moto's drivers, tried new cables, AND an entirely different computer. We've tried completely erasing boot, system, recovery, cache and userdata partitions, and flashing back the stock HRI66 images with fastboot.
ADB doesn't recognize the 'devices' command, only fastboot see's the Xoom. Accordingly, the only way to get into fastboot protocol is to Vol Up + power, and wait the three seconds and toggle. We can both toggle (with Vol) into Recovery, RSD and Fastboot). After flashing MULTIPLE flavours of Recovery images, the result is always the same: Recovery hangs reading fuse: 1. There's never the Recovery menu or graphic of the the Droid robot.
As for RSD, I've tried all the way through RSD Lite 5.0 with the thought of using solarnz' (I think) recovery.SBF. The result there is always the same as well: By toggling into RSD mode (Vol+Power into RSD), RSD Lite see's the device OK, but shows an error stating initialization values cannot be read. Note this occurs immediately upon plugging the Xoom in, even before TRYING the SBF file, which BTW, fails even if you try.
Via fastboot, we can oem lock and unlock (note however that in the command window, it states that it failed due to too many links, the the action seems to have worked on the Xoom anyway.)
So, it's down to THIS; the common thread for both of us is that we cannot successfully get into recovery, no way, no how. Again, ADB won't recognize the Xoom, only Fastboot
Any help would be APPRECIATED!
P.S. John, if we don't get help here, I have a 9mm with two spare rounds (for the Xoom's, not us!)

^^^
Thanks .... we'll see if anyone bites.... I hope so
As for the 9mm ........ Thanks but I have a flight this morning and I'm seriously thinking about dropping the Xoom out my plane from lets say 3500ft!!

LOL! Safe flight.

Guys, you all are crazy!
I appreciate your resourcefulness, but it sounds like you're almost out of options, lol.
If you can get to 'starting fastboot protocol' you are not bricked. If you cannot connect your Xoom via adb while your Xoom is in fastboot, it usually indicates that there is something wrong /missing from your setup.
Are you sure you have all your moto drivers installed and the proper image files in your platform tools (or tools folder) and you are actually in the right directory when opening the command window?
Please try to follow the instructions in the following
thread before you commit mayhem on your innocent Xooms.
http://forum.xda-developers.com/showthread.php?t=1249798 for setting up everything you need to ensure that adb will work and a proven method to install cwm recovery and root once you have been able to get back to a proper stock image. What I can't find at this moment are the 4G stock image files. You need the following to flash through adb/fastboot: system.img, boot.img, recovery.img, and userdata.img.from the Honeycomb 3.2.2 4G Xoom.
Commands to use:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot reboot
Don't give up...good luck!

Found out another guy tried 2 different PC's and it did the same thing. He even reloaded android sdk. He decided to try a 3rd PC that he had to load sdk to. It worked! So he found there is an issue somewhere with his 2 PC's sdk or windows install. When I got my xoom in June sdk would see it, but I never rooted at that time. However I did update and install all the new stuff for sdk.
Sent from my Xoom using xda premium

okantomi said:
Guys, you all are crazy!
Click to expand...
Click to collapse
Probably... That's half the fun!
okantomi said:
Are you sure you have all your moto drivers installed and the proper image files in your platform tools (or tools folder) and you are actually in the right directory when opening the command window?
Click to expand...
Click to collapse
Most assuredly. I develop Android apps with Eclipse. I know how to use SDK.
okantomi said:
Please try to follow the instructions in the following
thread before you commit mayhem on your innocent Xooms.
http://forum.xda-developers.com/showthread.php?t=1249798
Click to expand...
Click to collapse
Too late, mayhem already commited!
okantomi said:
What I can't find at this moment are the 4G stock image files.
Click to expand...
Click to collapse
That would be the ONLY thing we haven't tried. I know how to lock/unlock, flash images, etc. We've both done all of your above instructions to the letter. I've already replaced my Xoom and it's at Moto having 4G surgery, so I can't do any more of this now. John will have to try again, but as (I hope) you've already read above, the status quo techniques are not working.
Any clues about why a successfully flashed recovery image isn't working?

okantomi said:
..... If you cannot connect your Xoom via adb while your Xoom is in fastboot, it usually indicates that there is something wrong /missing from your setup.
Are you sure you have all your moto drivers installed and the proper image files in your platform tools (or tools folder) and you are actually in the right directory when opening the command window?
Please try to follow the instructions in the following
thread before you commit mayhem on your innocent Xooms.
http://forum.xda-developers.com/showthread.php?t=1249798 for setting up everything you need to ensure that adb will work and a proven method to install cwm recovery and root once you have been able to get back to a proper stock image. What I can't find at this moment are the 4G stock image files. You need the following to flash through adb/fastboot: system.img, boot.img, recovery.img, and userdata.img.from the Honeycomb 3.2.2 4G Xoom.
Commands to use:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot reboot
Don't give up...good luck!
Click to expand...
Click to collapse
Lots of stuff to answer back here, please don't mind the bullet points....
from your guide... "Did your device not show up? Make sure that you have USB debugging enabled in Settings/Applications/Development on your Xoom."
- I have no devices connected when typing ADB devices and based on the above how can I make sure I have USB debugging enabled if I can't even get to the Android OS??? I have fastboot support that's it, I don't think its possible for me to get ADB to connect with all the partitions erased. ADB or "Android Debugging Bridge", the name implies you NEED android on the device to use it. I don't have android since the system partition was erased.
- I have two different 4g images from AceXMachine's posts. However his build posts only have system.img and boot.img. So based on your instructions I need to know what userdata.img and recovery.img I should use.
- I keep asking and I will continue until I get an answer on the next question..... I think the bootloader is screwed up. I want a new one (or at least the one that came from my 4g upgrade). Where can I find one? How do I flash it? Is this synonymous with the boot.img?
Thanks!!!

Well, your issues are way, way, way beyond the scope of my limited knowledge, lol!
Have you tried to chat with the developers on #Xoom on freenode.net? Bigrushdog and solarnz are both really nice and so is SteadyHawkin, if he's on there. Someone may be able to help.
Good luck!

Flash it back to stock moto!!!! Then start over with bringing your xoom to 3.2.2!!!! That is why you can't get anywhere! You keep killing off everything! AceXMachine did the same as you and he has his xoom back to 3.2.2. Or send it to moto and pay them to flash you back. You are not doing it right period! You have posted the same issue and people have tried helping, but you seem to want to keep going into rsd and other crap you don't need. The baseband is in the boot.img. Flash the hir66 then update to the hlk75c.
Sent from my ADR6400L using xda premium

hammer4203 said:
Flash it back to stock moto!!!! Then start over with bringing your xoom to 3.2.2!!!! That is why you can't get anywhere! You keep killing off everything! AceXMachine did the same as you and he has his xoom back to 3.2.2. Or send it to moto and pay them to flash you back. You are not doing it right period! You have posted the same issue and people have tried helping, but you seem to want to keep going into rsd and other crap you don't need. The baseband is in the boot.img. Flash the hir66 then update to the hlk75c.
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
mmmkay... well THAT was a little terse. Don't you think returning to the HRI66 stock was the FIRST thing we tried? We downloaded the stock images from the provided links, checked the MD5, and then did this:
adb reboot bootloader
Xoom will then reboot into bootloader screen
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
Use volume rocker to select ok and then xoom will reboot. At this point you should be back to a factory state which includes being locked and unrooted.
Click to expand...
Click to collapse
Isn't THAT what you suggested? Yes? No?

^^Hammer....
I know this threads is really long and probably didn't read all of it (don't blame you) but a while back I explained that I did try and flash everything in Steadyhawkn' HIR66 build. I flashed the 4 images included (boot, system, userdata, recovery) I also went as far as an OEM lock at the end. This did nothing. I tried this a couple times.

Can someone lead me to the patience pool; I need a drink.

[GUIDE]Fix!!! Brickloop/Audio FX FC/EFS Corrupt!!!

Oneplus Bricklooping, Never ending Audio FX FC error, No IMEI/Baseband unknown, Corrupt EFS
READ THIS!!! ​
I cannot guarantee that this will work for everyone. However It has proven to be a solution for almost everyone that have used it. So if it does not work I ask that you be respectful in posting as such. Keep in mind that I myself am not having this issue. I was however compelled to try to help you guys, my fellow user. My hope is that I have given you a second chance. If it does work please be more careful!!!
Ok guys so I've read a lot of posts that say some of you guys are experiencing the above problems, and have tried what seems like everything to fix your baby. I've read the "flash color os" fix which seems to work for some but not all.
So I myself do not have this issue but a buddy of mine did so I was really wanted to not only help him fix his baby, but also anyone out here who is experiencing this issue.
Please note that if you have twrp installed you can skip down to "part 2" and simply run the command in terminal command via twrp
I am making a package for you to download which contains all files needed to make this happen.
Please note the methods here are not for fixing issues resulting from flashing various zips associated with any lollipop Roms or mods, nor is this thread a support thread for such problems
So inside it you will have a few files:
persist.img
reserve4.img (update: this file is not needed so ignore it!)
cm-11.0-XNPH30O-bacon-signed-fastboot_64GB.zip
adb-setup- 1.3.exe
please note that any commands run in fastboot mode require you to have an unlocked boot loader. If you are not sure if you are unlocked then that means you aren't! So to do so put the device in fastboot mode and type: "fastboot oem unlock"
Update: you don't need to worry about the reserve4.img or the 30O zip. if you have no O.S. then you can flash the 30O but we now know all that is needed is to flash the persist.img
INSTRUCTIONS:
EXTRACT ZIP
IF YOU HAVEN'T INSTALLED ADB/FASTBOOT DRIVERS RUN THE adb-setup- 1.3.exe FILE TO INSTALL ADB SYSTEM WIDE
IF YOU ALREADY HAVE ADB INSTALLED SKIP THAT STEP
OPEN A CMD WINDOW WHEREVER YOU HAVE THESE FILES EXTRACTED
TYPE THE FOLLOWING COMMANDS IN YOUR CMD WINDOW WITH DEVICE IN FASTBOOT MODE:
fastboot erase persist
fastboot flash persist persist.img
now reboot and check if all is working. If you have no O.S. installed then you will need to flash something to get back up in running: see below
Note that this will wipe your device 100% so if anything is on your phone back it up to your PC!
This next part (in green text) is only if you have no os installed and not necessary for most people:
[*]WE ARE NOW GOING TO FLASH 30O AND THEN ALL SHOULD BE FORGIVEN
[*]SO EXTRACT THE cm-11.0-XNPH30O-bacon-signed-fastboot_64GB.zip
[*]RUN THE flash-all.bat FILE FROM FASTBOOT AND YOU SHOULD BE CURED!!!
[*] Please note that some users may get an error from running the flash-all.bat/.sh
If so simply extract the .zip and flash all manually and you will get the desired result.
Part 2
If for some reason you have relocked your bootloader and still have twrp ( you'll know if its locked if you flash these images and it says "failed, device not unlocked"
So in this case reboot to twrp and run a terminal command with the following exactly as written
make_ext4fs /dev/block/mmcblk0p15
Then reboot and you should be all set!
Below are two different files for you to use. the first one contains the persist.img . I am uploading it seperate for those of you who already have a copy of 30O. I see no need in making you wait longer to dl this if you already have 30O.
I am uploading the full package which contains everything for those who need it all
If you found this helpful all I ask is you hit the thanks button!
Downloads ↓
NEVER SETTLE!
Full Package
If you are unable to use fastboot for whatever reason check this post for a flashable zip via custom recovery http://forum.xda-developers.com/showthread.php?p=55981898
Big shout out to my buddy AddisG for testing and confirming this works! We've been working on this for a long time and it's finally paid off
Also thanks to @Vonnegut for helping me maintain this thread and providing valuable information
Now once you are up and running again it's a good idea to not only backup your efs, but also copy that backup to your pc/cloud.
To do so is very easy. You'll need the app "terminal emulator" or alternatively you can do this on your Linux box too!
Issue the following commands to back them up:
open terminal
su
dd if=/dev/block/mmcblk0p10 of=/sdcard/modemst1.bin bs=512
dd if=/dev/block/mmcblk0p11 of=/sdcard/modemst2.bin bs=512
That will create two efs backups on your sd card. Make sure you copy them somewhere. DO NOT FORGET!!!
Now to restore your efs simply enter fastboot mode and flash the two efs files you backed up.
the commands are:
fastboot flash modemst1 modemst1.bin
fastboot flash modemst2 modemst2.bin
If you've tried all of the above and still have no baseband you can try this:
fastboot erase modemst1
fastboot erase modemst2
Please report if this works for you!!!
I sure hope it does!!!

Thanks bro Mark for all the time you spent helping me on this!!
PEOPLE PLEASE SMASH HIS THANKS BUTTON!!!

Are the persist and reserve partitions not unique to devices?

dmo580 said:
Are the persist and reserve partitions not unique to devices?
Click to expand...
Click to collapse
No, If you're having those nasty AudioFX FC when you turn on your phone use those two files or If not then follow the other instructions. I was going through the same but this fixed my problem.

AddisG said:
No, If you're having those nasty AudioFX FC when you turn on your phone use those two files or If not then follow the other instructions. I was going through the same but this fixed my problem.
Click to expand...
Click to collapse
Flashing 33R (not 30O) factory image did not fix my issues earlier. Sure I can try the 30O suggested here, but not too sure it'll do anything. But you're saying the persist and reserve files are not related to corrupt EFS/IMEI?

dmo580 said:
Flashing 33R (not 30O) factory image did not fix my issues earlier. Sure I can try the 30O suggested here, but not too sure it'll do anything. But you're saying the persist and reserve files are not related to corrupt EFS/IMEI?
Click to expand...
Click to collapse
I can tell you exactly what i had done.. i was having AudioFX FC because of that i couldn't do anything on my phone.. so i flashed the persist and reserve files in fastboot.. that got rid of my AudioFX issues and fixed the WIFI issue also.. i was on R33.. no luck with data or network.. and had no IMEI.. so i flashed 30O then i got Data/Network back. Try Persist and reserve first.. on R33, if they don't work then flash 30O and see if it does it.
P.S once you get data and everything else working you can update to the latest version of CM11 (which i already done)

dmo580 said:
Flashing 33R (not 30O) factory image did not fix my issues earlier. Sure I can try the 30O suggested here, but not too sure it'll do anything. But you're saying the persist and reserve files are not related to corrupt EFS/IMEI?
Click to expand...
Click to collapse
Just try it and let us know if it works for you.

markbencze said:
Just try it and let us know if it works for you.
Click to expand...
Click to collapse
I followed your steps and no go. no cellular. Oddly Bluetooth works now. No Wifi, No cell.

dmo580 said:
I followed your steps and no go. no cellular. Oddly Bluetooth works now. No Wifi, No cell.
Click to expand...
Click to collapse
Is your SIM inserted? And are you on 30O?

dmo580 said:
I followed your steps and no go. no cellular. Oddly Bluetooth works now. No Wifi, No cell.
Click to expand...
Click to collapse
Try again.
Did you flash 30O also?
{
"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"
}

markbencze said:
Try again.
Did you flash 30O also?
Click to expand...
Click to collapse
I flashed 33R like 2 days ago. Today I flashed 30O per your instructions. Got the 64GB version from this thread.
Yes SIM inserted.

Ok.. try this.. If you have ColorOS Rom try flashing that in recovery then flash 30O afterwards (must factory reset first).

dmo580 said:
I flashed 33R like 2 days ago. Today I flashed 30O per your instructions. Got the 64GB version from this thread.
Click to expand...
Click to collapse
I made no mention of 33R
Tell me step by step what you just tried. Being vague helps no one

markbencze said:
I made no mention of 33R
Tell me step by step what you just tried. Being vague helps no one
Click to expand...
Click to collapse
I flashed 33R as a part of my own debugging 2 days ago to try to recover the IMEI/EFS using the factory image. It is not part of what I tried today.
This morning I found that Nandroid restoring my CM11 Nightly backup made with TWRP 2.8.0.1 would give me WiFi and BT on boot.
Upon rebooting though no connectivity again. Cellular was never available, and IMEI was always unknown
I stumbled upon this thread, followed the steps in the OP regarding wiping and flashing both persist and reserve4 partitions
I then proceeded to use the flash-all.bat script for 30O
Booted up, and nothing connects. No WiFi, no BT, no cellular.
Upon rebooting (for the hell of it) it seems Bluetooth works now. Nothing more though. Further reboots show BT sticks.
Upon further inspection BT may not work. Somehow it shows as in the Settings menu and the toggle is switched on but it cannot see my Nexus 5. Further toggling off and on fails to turn BT back on. I suspect its a bug or something.
Edit: Forget the BT. No MAC address in Settings > Status. I bet the toggle is just faulty and switches on even if BT radio is messed up.

I have the AudioFix no SD issue. Going to try this when I get home. Will report.

joshyy_rey said:
I have the AudioFix no SD issue. Going to try this when I get home. Will report.
Click to expand...
Click to collapse
I can assure you that this will fix those issues.. for the AudioFX problem grab the two files from the OP "persist.img" and "reserve4.img" flash them in fastboot using the following commands:
fastboot erase persist
fastboot flash persist persist.img
fastboot erase reserve4
fastboot flash reserve4 reserve4.img
Hope this helps.

AddisG said:
I can assure you that this will fix those issues.. for the AudioFX problem grab the two files from the OP "persist.img" and "reserve4.img" flash them in fastboot using the following commands:
fastboot erase persist
fastboot flash persist persist.img
fastboot erase reserve4
fastboot flash reserve4 reserve4.img
Hope this helps.
Click to expand...
Click to collapse
WHOA IT WORKED....omg....thank you.

only have 12GB now of available storage... I need to see what went wrong... i only flashed the fix files

joshyy_rey said:
only have 12GB now of available storage... I need to see what went wrong... i only flashed the fix files
Click to expand...
Click to collapse
flash userdata 64GB img. find it via google or xda.

joshyy_rey said:
only have 12GB now of available storage... I need to see what went wrong... i only flashed the fix files
Click to expand...
Click to collapse
I have linked the 64 g factory image in the op. Try that

[Q] I guess I messed up pretty bad.

Hey there. I hate to bother everyone, i really do, but after searching countless forums, and trying infinite solutions, i'm at a loss of what to do. I want to flash to stock rom, I'm on paranoid android at the moment. Now normally this wouldn't be an issue- but somehow, someway, my bootloader is locked, and i cannot get it to unlock again at all. i've tried doing it with the OPO tool, tried through cmd, nothing. all that happens upon running fastboot oem unlock is my device boots into recovery (philz). i have no idea what to do, but it's really bumming me out. My model is the 64gb one.
also as a side problem, i originally tried flashing THIS ROM, and ever since then my fastboot is in the chinese version. I couldn't flash to stock before hand because it kept telling me my fastboot was outdated. how can i fix this as well?
i really, really, REALLY appreciate any help i can get. i always surf for hours on forums trying to resolve the problem myself before making a new thread, but i have no other options now.

You did mess up pretty bad (by posting in the wrong section).
Does the command prompt give you any error when you try to unlock the bootloader?
Try reading through this thread, it may help (read all of it before you attempt anything)
http://forum.xda-developers.com/oneplus-one/help/oneplus-one-unable-to-unlock-bootloader-t2845626

sahil04 said:
You did mess up pretty bad (by posting in the wrong section).
Does the command prompt give you any error when you try to unlock the bootloader?
Click to expand...
Click to collapse
my sincerest apologies. i haven't actually used XDA in a while. give me a little bit though, upon trying again, apparently my abd isn't working right and isn't recognized as an internal command.
update: those threads always result in telling me to do this which is what i'm trying to do right now, though i've tried before and still tend to get a straight boot into recovery.

Sounds like you are not in the correct directory to run adb.
Try this:
cd (location of adb.exe)
example:
cd C:\android\platform-tools\
Then try to run this command with your device plugged in:
adb.exe devices

sahil04 said:
Sounds like you are not in the correct directory to run adb.
Try this:
cd (location of adb.exe)
example:
cd C:\android\platform-tools\
Then try to run this command with your device plugged in:
adb.exe devices
Click to expand...
Click to collapse
i'm in the right directory. i'm following this guide and i'm at the part where it tells me to type "fastboot oem unlock" it then tells me to do a fastboot reboot after that script finishes running which is where the problem comes in. the phone reboots into recovery IMMEDIATELY after inputting the oem unlock command, not giving me the chance to do anything else.

dokibot said:
i'm in the right directory. i'm following this guide and i'm at the part where it tells me to type "fastboot oem unlock" it then tells me to do a fastboot reboot after that script finishes running which is where the problem comes in. the phone reboots into recovery IMMEDIATELY after inputting the oem unlock command, not giving me the chance to do anything else.
Click to expand...
Click to collapse
try sideloading... Adb sideload "name of rom".zip
Sent from my A0001 using XDA Premium 4 mobile app

sahil04 said:
You did mess up pretty bad (by posting in the wrong section).
Does the command prompt give you any error when you try to unlock the bootloader?
Try reading through this thread, it may help (read all of it before you attempt anything)
http://forum.xda-developers.com/oneplus-one/help/oneplus-one-unable-to-unlock-bootloader-t2845626
Click to expand...
Click to collapse
this is what the cmd shows when i run oem unlock. then the phone just boots into recovery.
{
"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"
}

Setting.Out said:
try sideloading... Adb sideload "name of rom".zip
Sent from my A0001 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
i've never side loaded before? i can't find anything specific for the opo
edit: all i can find is how to flash roms with it, when i really wanna get my bootloader unlocked

dokibot said:
i've never side loaded before? i can't find anything specific for the opo
edit: all i can find is how to flash roms with it, when i really wanna get my bootloader unlocked
Click to expand...
Click to collapse
Try the following links:
Link1
Link2

KDurantula said:
Try the following links:
Link1
Link2
Click to expand...
Click to collapse
surely there's something other than using a ubuntu virtual box? i don't have a lot of disk space right now, and i'd much rather have some other solution. anything else.

dokibot said:
surely there's something other than using a ubuntu virtual box? i don't have a lot of disk space right now, and i'd much rather have some other solution. anything else.
Click to expand...
Click to collapse
I was kind of in the same situation as you, nothing else would work for me lol. If all else fails, give it a shot!

Go back to stock and start over, please see this guide to go back to stock:
Download the official CM11S from cyanogen website http://builds.cyngn.com/factory/bacon/cm-11.0-XNPH33R-bacon-signed-fastboot.zip and follow this guide:
First time flashing CyanogenMod 11S on your device, or coming from another ROM (e.g. ColorOS)?
WARNING: This procedure will factory reset your device! Accounts, applications, settings, everything will be lost! This is really a factory reset.
Download the file cm-11.0-XNPH33R-bacon-signed-fastboot.zip to your PC from the link above
Reboot your device into Fastboot mode by holding PWR+VOL-UP
Connect your device via USB to your PC
Unpack the downloaded zip
Open a command prompt (Windows) or terminal (Linux/Mac) and perform the following fastboot commands:
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot update -w cm-11.0-XNPH33R-bacon-signed-fastboot.zip (file used to extract the files above)
This will make you device go back to stock, check if it works now.
Hope this helps.

i can't flash anything. my bootloader isn't unlocked. this is my problem.

dokibot said:
i can't flash anything. my bootloader isn't unlocked. this is my problem.
Click to expand...
Click to collapse
Do you have a custom recovery? If you do, your bootloader is unlocked.
Just sideload a XNPH38R.zip, Calkulin's one, or the official. Then try to use fastboot once more.
My guess is that this fixes your problem and that fastboot will work again.
P.S. Even if you haven't been on XDA for a while how in God's name would you post in "Original Android Development"...?

TiVON said:
Do you have a custom recovery? If you do, your bootloader is unlocked.
Just sideload a XNPH38R.zip, Calkulin's one, or the official. Then try to use fastboot once more.
My guess is that this fixes your problem and that fastboot will work again.
P.S. Even if you haven't been on XDA for a while how in God's name would you post in "Original Android Development"...?
Click to expand...
Click to collapse
**** i didn't even realize i was in original. my bad wow. Yeah i have philz right now. do i need to wipe everything to do this. i'm scared of wiping because if i do, since i can't flash anything, i'll be stuck without a rom at all. i'm downloading the official zip, and i'm about to try sideloading it.
edit: sideload failed. might be because i didn't wipe. error in /tmp/update.zip (status 7). it suggested i do a factory reset, tried that, still same error.

dokibot said:
**** i didn't even realize i was in original. my bad wow. Yeah i have philz right now. do i need to wipe everything to do this. i'm scared of wiping because if i do, since i can't flash anything, i'll be stuck without a rom at all. i'm downloading the official zip, and i'm about to try sideloading it.
edit: sideload failed. might be because i didn't wipe. error in /tmp/update.zip (status 7). it suggested i do a factory reset, tried that, still same error.
Click to expand...
Click to collapse
Have you tried flashing the stock rom with the stock recovery through the custom recovery and then trying to re-unlock the bootloader?

sahil04 said:
Have you tried flashing the stock rom with the stock recovery through the custom recovery and then trying to re-unlock the bootloader?
Click to expand...
Click to collapse
i can't flash stock. it tells me the bootloader is locked, and stops the process.

hugoprh said:
Go back to stock and start over, please see this guide to go back to stock:
Download the official CM11S from cyanogen website http://builds.cyngn.com/factory/bacon/cm-11.0-XNPH33R-bacon-signed-fastboot.zip and follow this guide:
First time flashing CyanogenMod 11S on your device, or coming from another ROM (e.g. ColorOS)?
WARNING: This procedure will factory reset your device! Accounts, applications, settings, everything will be lost! This is really a factory reset.
Download the file cm-11.0-XNPH33R-bacon-signed-fastboot.zip to your PC from the link above
Reboot your device into Fastboot mode by holding PWR+VOL-UP
Connect your device via USB to your PC
Unpack the downloaded zip
Open a command prompt (Windows) or terminal (Linux/Mac) and perform the following fastboot commands:
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot update -w cm-11.0-XNPH33R-bacon-signed-fastboot.zip (file used to extract the files above)
This will make you device go back to stock, check if it works now.
Hope this helps.
Click to expand...
Click to collapse
none of this works. cant even get it to open NON-HLOS.bin everytime i try it just gives me "error: cannot open "NON-HLOS.bin'" i have my path set to
cd desktop/sdk/platform-tools/(folder i named with all the zip files)
is that right?

dokibot said:
none of this works. cant even get it to open NON-HLOS.bin everytime i try it just gives me "error: cannot open "NON-HLOS.bin'" i have my path set to
cd desktop/sdk/platform-tools/(folder i named with all the zip files)
is that right?
Click to expand...
Click to collapse
Try this:
cd C:\Users\(username)\Desktop\SDK\platform-tools\
Also, did you extract the files out of the zip file?

dokibot said:
none of this works. cant even get it to open NON-HLOS.bin everytime i try it just gives me "error: cannot open "NON-HLOS.bin'" i have my path set to
cd desktop/sdk/platform-tools/(folder i named with all the zip files)
is that right?
Click to expand...
Click to collapse
Install this http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
So you can get the adb and fastboot from anywhere on the command line, then open the command prompt and navigate to that folder and copy line by line from the above tutorial.
The last line will require the original ZIP file to be in the same folder has the extracted files.
Hope this helps.

Help!! Daily driver OnePlus 8 pro has messed up!!

Hi guys I hope I don't get too much scorn for this... I tried to install the pixel experience using this YouTube link and enclosed
I used the command prompts in the description, something didn't seem quite right as I got some errors. struggle to get the phone to come on but eventually when it does it loads up the pixel experience menu? I have to choose advanced format to get my phone to come back on on but the resolution is all weird.
Things look really small buttons merge over each other
I just want to wipe this phone get the pixel experience off and go back to my original software can anyone help
Much Appreciated
Matt

matt55325 said:
Hi guys I hope I don't get too much scorn for this... I tried to install the pixel experience using this YouTube link and enclosed
I used the command prompts in the description, something didn't seem quite right as I got some errors. struggle to get the phone to come on but eventually when it does it loads up the pixel experience menu? I have to choose advanced format to get my phone to come back on on but the resolution is all weird.
Things look really small buttons merge over each other
I just want to wipe this phone get the pixel experience off and go back to my original software can anyone help
Much Appreciated
Matt
Click to expand...
Click to collapse

Anyone able to help?

matt55325 said:
Anyone able to help?
Click to expand...
Click to collapse
Oh my... you believed a Utube vid? They censor all the good ones out and put warnings on all the ones distributing facts
So you need to reflash it to stock firmware or was it just an app you loaded?
The former is easy. A hard reset at the worst.
Either way get rid of it before it crashes the phone... an unstable launcher is real bad news.

blackhawk said:
Oh my... you believed a Utube vid? They censor all the good ones out and put warnings on all the ones distributing facts
So you need to reflash it to stock firmware or was it just an app you loaded?
The former is easy. A hard reset at the worst.
Either way get rid of it before it crashes the phone... an unstable launcher is real bad news.
Click to expand...
Click to collapse
Yes it boots up when I hold.power and volume, it was the key strokes on the YouTube videos comments in the description I used....now I get this stupid pixel experience menu I want it gone .
How should I proceed ?

matt55325 said:
Yes it boots up when I hold.power and volume, it was the key strokes on the YouTube videos comments in the description I used....now I get this stupid pixel experience menu I want it gone .
How should I proceed ?
Click to expand...
Click to collapse
Should I try a reflash first?

matt55325 said:
Should I try a reflash first?
Click to expand...
Click to collapse
On the video description I just used ADB and injected the code used the img files
I think like you say try a reflash and pray!

matt55325 said:
Should I try a reflash first?
Click to expand...
Click to collapse
So you didn't flash firmware, you edited it with ADB?
If so, piece of cake...
Undo the changes you made using ADB or...
Do a hard reset; wipe the OS and restore the original factory load.
A 3rd party launcher boot looped my phone twice resulting in me having to do 2 hard resets in 2 weeks. Be careful with this type of apk...

I did commands like this I think it started with a -w to wipe then
fastboot flash recovery recovery.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot flash opproduct opproduct.img
fastboot reboot fastboot
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash product product.img
fastboot reboot
Similar to these commands at the end of each command like I dragged and dropped the file from pixel experience folder to match each one then rebooted

matt55325 said:
I did commands like this I think it started with a -w to wipe then
fastboot flash recovery recovery.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot flash opproduct opproduct.img
fastboot reboot fastboot
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash product product.img
fastboot reboot
Similar to these commands at the end of each command like I dragged and dropped the file from pixel experience folder to match each one then rebooted
Click to expand...
Click to collapse
Pretty sure that only applies to the current load so a hard reset do it.
You can give reediting it a shot as failure just means needing to reload.
Lol, do they have a how to undo vid?
Don't feel bad... I'm on my 2nd reload

Lol mate no! First thing I look for was a video to reverse it but no luck lol......can you link me to a video or a instruction guide that will help me to hard reset it. Scared of breaking it now after this near miss
Thanks for the help as well much appreciated
Happy New year

matt55325 said:
Lol mate no! First thing I look for was a video to reverse it but no luck lol......can you link me to a video or a instruction guide that will help me to hard reset it. Scared of breaking it now after this near miss
Thanks for the help as well much appreciated
Happy New year
Click to expand...
Click to collapse
Just make sure all your data, bookmarks, texts, pics,etc are backed up on the PC and you have the Google email password written down.
Simply do the hard reset from the boot menu.
Maybe someone here will post a way to undo it with ADB as I'm sure it's possible. I have zero experience with it so far... sorry.

Coming from an OP3T need help regarding the new partitions

I own a 3T currently and am planning to get an 8T as it is getting good custom rom traction. One thing I am really confused about the is the new partitioning scheme. Can someone please link me an article where I can read more about it? Also what's with the specific twrp's and installer zips for each rom and how does one flash magisk, xposed and other things?
What I am used to doing on my 3t is, wipe data, system, cache and then flash rom zip + gapps + magisk. I would really appreciate it if anyone can explain the additional steps that would be required to do this on the 8T

It's a very different world with the 8T (I also come from a 3T).
The 8T has A/B partitions as well as virtual A/B partitions. It also supports streaming OTA and seamless OTA updates. It has fastboot and fastbootd.
There's lots of good information on all of this in:
Virtual A/B Overview | Android Open Source Project
source.android.com
A/B (Seamless) System Updates | Android Open Source Project
source.android.com
platform/system/update_engine - Git at Google
Moving Fastboot to Userspace | Android Open Source Project
source.android.com
And more on this at the same site.
And, if you get into serious trouble, the unbricking tool is really easy to use and works wonderfully.

pratyush28 said:
I own a 3T currently and am planning to get an 8T as it is getting good custom rom traction. One thing I am really confused about the is the new partitioning scheme. Can someone please link me an article where I can read more about it? Also what's with the specific twrp's and installer zips for each rom and how does one flash magisk, xposed and other things?
What I am used to doing on my 3t is, wipe data, system, cache and then flash rom zip + gapps + magisk. I wouls really appreciate it if anyone can explain the additional steps that would be required to do this on the same thing on an 8T.
Click to expand...
Click to collapse
I'm going to try to give you a brief, yet precise enough guide to doing the basics on a device with partitions like the 8T.
Okay, so basically, the 8T custom ROMs, when flashed, are going to consist of the following partitions:
boot
dtbo
system
system_ext
product
recovery
vendor
odm
vbmeta
vbmeta_system
So when performing fastboot/adb commands with these newer devices, you're going to start off in the normal bootloader (i use the volume +/- and power at the same time command to enter this from a powered off state).
Now there's also a mode called fastbootd mode. It's often just called fastboot, especially when booting from bootloader (fastboot reboot fastboot now takes you to this fastbootd mode). This is where you're going to do the majority of flashing/modding from.
So to start off, enter bootloader, then perform this command in terminal to do a wipe of data:
fastboot -w
Then, flash recovery partition:
fastboot flash recovery recovery.img (this is the recovery.img from the ROM zip you are attempting to flash)
Then, reboot to fastbootd:
fastboot reboot fastboot
Next, I like to make sure I'm on partition A for flashing. This is just something I've been told to do and it works so I stick with it. So do this by:
fastboot set_active a
Now you can start flashing the paritions:
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash product product.img
fastboot flash vendor vendor.img
fastboot flash odm odm.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
Then, boot up the ROM:
fastboot reboot
So that's the basic rundown.
Now for a few things to keep in mind:
Always make sure you're on the latest version of OxygenOS before doing any of this. I like to start off by unlocking bootloader, then setting up phone. Then I do an update to both partitions to the latest version of OOS (must be on both partitions. Not just on one). So I just put the latest OOS zip on my phone via USB transfer from PC, do an upgrade with that file (Settings > System > Update > Top right menu button > Select Internal Storage or whatever it says like that, then select the file (make sure the OOS zip file is in the MAIN root directory of your phone. So basically, the folder that contains the Pictures, Downloads, Music, etc. folders.
So after you do this system update, it will prompt you to reboot phone. Do this. Then, go to settings and do the same thing again. Select the OOS zip and do an internal storage update, let it do its thing, it'll ask to reboot, go ahead and do so. Now this second update you do will either start from 0% and go to 100% like the first time, or it will go from 0% directly to 99%, then 100% after a few seconds. This is okay, it just means you already had the latest OOS on one of your partitions. So anyway, go ahead and do that reboot when it tells you. Now you are unlocked and on the latest firmware and ready to flash.
Oh, and btw, to unlock bootloader, do the normal steps through developer options, then reboot to bootloader and this is the command used:
fastboot flashing unlock
That will let you confirm to unlock bootloader, etc. like I'm sure you've done on the 3T.
So anyway, after unlocking and updating to latest OOS (Open Beta or Stable usually both work fine btw), you can reboot to bootloader, then do the steps I told you above for wiping, flashing recovery, flashing partitions, booting, etc.
Oh, and to get these partition images from the custom ROM zip you choose to flash, you need to first unzip the ROM zip file, then take the payload.bin file that will result of the unzip, and use a payload_dumper script. Those are linked all over or can be found on a google search or Github. It'll take your payload.bin and turn it into these .IMG files that I list in the flashing steps. Each partition will have a file named PARTITIONNAME.img. These are all you need to flash a custom ROM over OOS.
To flash an update to a rom, do all the same stuff but don't do the
fastboot -w
and you also don't need to do the
fastboot flash recovery recovery.img
part because the recovery partition is already there from the ROM when you originally flashed.
I realize this is all a bunch of random notes and guides, and my brain kind of works in a weird way, but it's pretty much all there I think. If you need help clarifying any of this or just have any questions in general, PM me or respond back here and tag me. I'll help as much as I can or point you to someone who can help if I can't.
Hope this helps. Take care.

dpryor88 said:
I'm going to try to give you a brief, yet precise enough guide to doing the basics on a device with partitions like the 8T.
Okay, so basically, the 8T custom ROMs, when flashed, are going to consist of the following partitions:
boot
dtbo
system
system_ext
product
recovery
vendor
odm
vbmeta
vbmeta_system
So when performing fastboot/adb commands with these newer devices, you're going to start off in the normal bootloader (i use the volume +/- and power at the same time command to enter this from a powered off state).
Now there's also a mode called fastbootd mode. It's often just called fastboot, especially when booting from bootloader (fastboot reboot fastboot now takes you to this fastbootd mode). This is where you're going to do the majority of flashing/modding from.
So to start off, enter bootloader, then perform this command in terminal to do a wipe of data:
fastboot -w
Then, flash recovery partition:
fastboot flash recovery recovery.img (this is the recovery.img from the ROM zip you are attempting to flash)
Then, reboot to fastbootd:
fastboot reboot fastboot
Next, I like to make sure I'm on partition A for flashing. This is just something I've been told to do and it works so I stick with it. So do this by:
fastboot set_active a
Now you can start flashing the paritions:
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash product product.img
fastboot flash vendor vendor.img
fastboot flash odm odm.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
Then, boot up the ROM:
fastboot reboot
So that's the basic rundown.
Now for a few things to keep in mind:
Always make sure you're on the latest version of OxygenOS before doing any of this. I like to start off by unlocking bootloader, then setting up phone. Then I do an update to both partitions to the latest version of OOS (must be on both partitions. Not just on one). So I just put the latest OOS zip on my phone via USB transfer from PC, do an upgrade with that file (Settings > System > Update > Top right menu button > Select Internal Storage or whatever it says like that, then select the file (make sure the OOS zip file is in the MAIN root directory of your phone. So basically, the folder that contains the Pictures, Downloads, Music, etc. folders.
So after you do this system update, it will prompt you to reboot phone. Do this. Then, go to settings and do the same thing again. Select the OOS zip and do an internal storage update, let it do its thing, it'll ask to reboot, go ahead and do so. Now this second update you do will either start from 0% and go to 100% like the first time, or it will go from 0% directly to 99%, then 100% after a few seconds. This is okay, it just means you already had the latest OOS on one of your partitions. So anyway, go ahead and do that reboot when it tells you. Now you are unlocked and on the latest firmware and ready to flash.
Oh, and btw, to unlock bootloader, do the normal steps through developer options, then reboot to bootloader and this is the command used:
fastboot flashing unlock
That will let you confirm to unlock bootloader, etc. like I'm sure you've done on the 3T.
So anyway, after unlocking and updating to latest OOS (Open Beta or Stable usually both work fine btw), you can reboot to bootloader, then do the steps I told you above for wiping, flashing recovery, flashing partitions, booting, etc.
Oh, and to get these partition images from the custom ROM zip you choose to flash, you need to first unzip the ROM zip file, then take the payload.bin file that will result of the unzip, and use a payload_dumper script. Those are linked all over or can be found on a google search or Github. It'll take your payload.bin and turn it into these .IMG files that I list in the flashing steps. Each partition will have a file named PARTITIONNAME.img. These are all you need to flash a custom ROM over OOS.
To flash an update to a rom, do all the same stuff but don't do the
fastboot -w
and you also don't need to do the
fastboot flash recovery recovery.img
part because the recovery partition is already there from the ROM when you originally flashed.
I realize this is all a bunch of random notes and guides, and my brain kind of works in a weird way, but it's pretty much all there I think. If you need help clarifying any of this or just have any questions in general, PM me or respond back here and tag me. I'll help as much as I can or point you to someone who can help if I can't.
Hope this helps. Take care.
Click to expand...
Click to collapse
I cannot thank you enough for taking out so much time and explaining everything in detail. I really appreciate it and this will be very very helpful for me.
Unfortunately, I purchased the 8T from OnePlus' official website and they sent me a refurbished piece with a cracked back panel and scratched screen. I was stupid to opt for OnePlus' site just because there was a small discount, now to get a replacement I have to go through a painful process of contacting their incompetent support and an eternal wait until they decide to revert. I'm glad that I recorded the unboxing video, so at least they cannot blame this on me.

pratyush28 said:
I cannot thank you enough for taking out so much time and explaining everything in detail. I really appreciate it and this will be very very helpful for me.
Unfortunately, I purchased the 8T from OnePlus' official website and they sent me a refurbished piece with a cracked back panel and scratched screen. I was stupid to opt for OnePlus' site just because there was a small discount, now to get a replacement I have to go through a painful process of contacting their incompetent support and an eternal wait until they decide to revert. I'm glad that I recorded the unboxing video, so at least they cannot blame this on me.
Click to expand...
Click to collapse
Ah man! I'm so sorry to hear that! Their support is horrible I must admit. Not as bad as Google Fi's support haha (that's another story), but it's bad yeah.
I got mine from the OP website also (North America model as I live in California) but I got it shortly after the phone was released. I can't believe they're selling refurbished, broken devices now. That's horrible. The company has been going a bit downhill with some aspects I've realized in the past few years.
Anyway, I really hope you get that sorted out (sooner than later hopefully). It's a nice device. Software support/updates are a little iffy with OP these days, but no one's perfect. But once you start flashing some custom goodness on the phone, it really shines. Nothing wrong with Oxygen in my opinion, but choice is nice
Let me know if/when you get the device if you need any help with anything.

dpryor88 said:
Ah man! I'm so sorry to hear that! Their support is horrible I must admit. Not as bad as Google Fi's support haha (that's another story), but it's bad yeah.
I got mine from the OP website also (North America model as I live in California) but I got it shortly after the phone was released. I can't believe they're selling refurbished, broken devices now. That's horrible. The company has been going a bit downhill with some aspects I've realized in the past few years.
Anyway, I really hope you get that sorted out (sooner than later hopefully). It's a nice device. Software support/updates are a little iffy with OP these days, but no one's perfect. But once you start flashing some custom goodness on the phone, it really shines. Nothing wrong with Oxygen in my opinion, but choice is nice
Let me know if/when you get the device if you need any help with anything.
Click to expand...
Click to collapse
Thanks mate, I won't hesitate to ask if I need help once I get the new device

@dpryor88 Finally after a 21 day battle with the OnePlus support, today I received my replacement device.
It happens to have LPDDR5 ram. I checked this xda article where they mentioned that the unbrick tool fails on this variant.
https://www.xda-developers.com/oneplus-8t-oneplus-9r-shipping-faster-ram/amp/
Which variant do you have? Also, did you try using the unbrick tool?

pratyush28 said:
@dpryor88 Finally after a 21 day battle with the OnePlus support, today I received my replacement device.
It happens to have LPDDR5 ram. I checked this xda article where they mentioned that the unbrick tool fails on this variant.
https://www.xda-developers.com/oneplus-8t-oneplus-9r-shipping-faster-ram/amp/
Which variant do you have? Also, did you try using the unbrick tool?
Click to expand...
Click to collapse
I have the other model. Unbrick tool works fine on mine.

pratyush28 said:
@dpryor88 Finally after a 21 day battle with the OnePlus support, today I received my replacement device.
It happens to have LPDDR5 ram. I checked this xda article where they mentioned that the unbrick tool fails on this variant.
https://www.xda-developers.com/oneplus-8t-oneplus-9r-shipping-faster-ram/amp/
Which variant do you have? Also, did you try using the unbrick tool?
Click to expand...
Click to collapse
My 8T has ddr_type of 1 and I've had no problems using the unbrick tool (and I've used it a lot as I've been testing/learning lots of stuff with TWRP) on my KB2000.

BillGoss said:
My 8T has ddr_type of 1 and I've had no problems using the unbrick tool (and I've used it a lot as I've been testing/learning lots of stuff with TWRP) on my KB2000.
Click to expand...
Click to collapse
That's some good news, mine is KB2001 I wonder if that will make a difference. Also, have you tried flashing custom roms? If yes, was there any firmware incompatibility?

pratyush28 said:
That's some good news, mine is KB2001 I wonder if that will make a difference. Also, have you tried flashing custom roms? If yes, was there any firmware incompatibility?
Click to expand...
Click to collapse
Yes, I installed a couple of custom ROMs and they were fine.
The only place I know that matters is the xbl and xbl_config partitions. The full OOS ROMs have an extra -lp5 set of files that get flashed on lp5 phones instead of the "normal" xbl files.
But since this only applies to firmware and the xbl partitions are never touched by custom ROMs, there cannot, therefore, be incompatibilities due to lp4 vs lp5.