Question Bricked please help. - OnePlus 9

I restored an earlier TWRP backup, then I restored my last one. Im stuck in a boot loop. Ive tried everything cant even get windows to recognize fastboot or adb while in fastboot or twrp.

TimmyP said:
I restored an earlier TWRP backup, then I restored my last one. Im stuck in a boot loop. Ive tried everything cant even get windows to recognize fastboot or adb while in fastboot or twrp.
Click to expand...
Click to collapse
This should have all you need to bring it back.
Unbrick OnePlus 9, 9 Pro Using EDL Firmware With MSM Download Tool
In this tutorial, we will show you how to unbrick your OnePlus 9 or 9 Pro using EDL Firmware with the MSM Download Tool. Once you step into the cus
www.getdroidtips.com

Surgemanxx said:
This should have all you need to bring it back.
Unbrick OnePlus 9, 9 Pro Using EDL Firmware With MSM Download Tool
In this tutorial, we will show you how to unbrick your OnePlus 9 or 9 Pro using EDL Firmware with the MSM Download Tool. Once you step into the cus
www.getdroidtips.com
Click to expand...
Click to collapse
Thank you. I just switched my slot from a to b and let it sit, and it boot! Ill definitely hang on to this for refernce.

What's going on I've been there. What can I do to help?

Okay, after hours I finally got it restored back to where I was. I guess TWRP doesn't like restoring backups from usb reader very much (writes them perfectly fine though, using leef reader and microsd card btw), but after getting the clean install running from the last post, I copied the TWRP backup off the card onto internal storage and it flashed. Thank god I dont want to go through that again.
I would really appreciate a walkthrough on getting to A13. I know I have to restore stock firmware which is fine, I just have no idea how to get back to "stock" to the point where I can OTA through Tmobile.

Huh. I gained about 17 gigs after this. I mustve had something on the device taking a ton of space (obviously). Ill remove this if I find something Im missing, but I cant think of or find anything missing, and I (usually) know where to look.
During this downtime, in TWRP I reformatted data, factory reset, and did the default wipe... I bet that had something to do with it. Only stating this because I did a straight root with Magisk on 11 after converting. I never added anything remotely large to the phone.
*and I did end up restoring the full twrp backup I made an hour before I started messing with this. No TWRP backups were stored on the phone at any point either, just on an external card.

Related

Bricked OnePlus 6

Hello all,
So here we go, I'll make it quick. I have wipe everything in the TWRP (vendor included) and now I'm stuck in the fastboot, I don't have access to the recovery and I can't access the TWRP because when I try to boot on it it tells me "Failed to authentificater/load image". I've been trying everything for 6 hours now and I've been looking for internet solutions. I don't even have internal storage anymore when I plug in the phone. I think it's dead but you never know so I'm trying my last card.
Thanks to all of you guys who're going to help me.
PS : Sorry If I got a bad english, like I said i did this very quickly
Flash factory firmware from fastboot odin. Make sure you have installed the required drivers. Let me know if that works.
Xspidera said:
Flash factory firmware from fastboot odin. Make sure you have installed the required drivers. Let me know if that works.
Click to expand...
Click to collapse
Thanks, it worked! https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
I used this thread and the "flash-system-boot-vendor" one, and the phone did reboot to OS.
Glad to be helpful ?

My OP 7 PRO(GM21AA) is being completely stuck at Fastboot.

Hey,
It's been always a huge headache since when the Android 10 beta and stables updates are out to root and install twrp. I've tried almost every way possible but every-time, end up being stuck at TWRP or being half way rooted. This time I've tried doing that again :
* I was at OxygenOs Android 10 stable version,
* My bootloader was unlocked as well as OEM unlocking and usb debugging was on,
* I turned my phone into fastboot, and flash the twrp image as:
fastboot flash boot file.img
Then after my phone booted into TWRP since once or twice showing that 0mb internal storage, I flashed the Magisk.zip from adb command, and rebooted it.
Since then, my phone is completely stucked at fastboot, I've tried and followed almost every xda suggestion and everything, I've tried flashing flash.bat file, I've tried flashing stock recovery, In fact I've tried flashing complete fastboot Rom (with all in one app)and it everytime boots me into Fatboot.
Please, help me out guys. I'm stressed out of this problem since yesterday's night.
Let me know your suggestions.
Maybe THIS can help you?
Actually this thread helped me just now in the same situation:
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
That thread Jonsat mentioned didn't help me either, at all. Its not very clear that thread, telling in the thread to unbrick a OP7 to look at the thread of the OP6, there send them to OP5 and so on, eventually having to use a short written manual for the OP3 which mentions different versions and so on, its not the best for inexperienced people like me, it just send me on a wild chase downloading drivers and other things that eventually didnt work at all. Maybe I will try to rewrite it, as soon as I have enough experience to do so, i own this device for just a week.
Next time, read before you peform the install steps. It's nowhere like the older devices due to the A/B Recovery.
1. Use MSM Downloader to put you back to stock.
2. Upgrade to Android 10
3. Factory Reset to Clean out your phone (don't forget to unlock bootloader)
4. Initialize phone
5. Boot twrp (specific to Android Q + OP7 Pro)
6. Install TWRP and Magisk from TWRP
7. reboot and enjoy your rooted phone
lloydlim996 said:
Next time, read before you peform the install steps. It's nowhere like the older devices due to the A/B Recovery.
1. Use MSM Downloader to put you back to stock.
2. Upgrade to Android 10
3. Factory Reset to Clean out your phone (don't forget to unlock bootloader)
4. Initialize phone
5. Boot twrp (specific to Android Q + OP7 Pro)
6. Install TWRP and Magisk from TWRP
7. reboot and enjoy your rooted phone
Click to expand...
Click to collapse
What is MSM download tool? I'm going to try using All in One.
On searching for MSM tool, I found https://www.techoxygen.com/msm-download-tool/ is that correct?
Scratch this, MSMdownload is part of zip, I'll read through https://forum.xda-developers.com/showpost.php?p=79972789&postcount=50 and see how it goes

OnePlus 8T a Complete Brick; help.

Hello! I'm very new to writing on forums so I'm hopefully doing it correctly. But I used to root OnePlus phones back when it was 2, 3 and 4. Things have changed a bit and I lost some knowledge of it. I rooted my OnePlus 8T using Magisk, no TWRP. I used the installation with a patched image on Magisk and my wifi, calling, and Android auto and sound all went out. I tried to revert it by putting the actual boot.img from extracting it using python, after downloading the payload.bin zipfile from OnePlus.com. I flashed it back and it went kaput. I was dumber than ever, and decided to use fastboot to erase the boots and recovery and flashed them back on and it still won't get passed the T-mobile logo. If I boot into recovery, I get the crashdump. Fastboot is fine, I can use that, but I haven't been able to achieve anything using it. I can get into edl, but I keep getting the Sahara communications failed error in the msmdownloadtool. I guess, if someone knows an answer, please help me out. If not, and it's not possible to fix, I just need second opinions to confirm whether it's fixable or not. I'd answer any help from you all. Thanks!
Fix the drivers on your computer and try MSM tool again.
Other than that, if fastboot is fine, try flashing a custom ROM and see if it boots, or you can also try flashing a full OTA of OOS.
This is totally fixable.
The OP in this thread has a suggestion regarding the Shara problem: Thread '[OP8T][OOS KB05AA/BA/DA] Unbrick tool to restore your device to OxygenOS' https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4180837/

Well I screwed up... (lineage os 19.1 install)

Started to go down the Lineage 19.1 route. Despite the warning, I forgot to update firmware to 12, realized this halfway through the flash.
Thought no worries, I will just flash 18.1 again as I still have the files, but now I can't get into recovery. Any booting leads only to the crash dump screen
Is an MSM tool reset the only way?
Now I am pretty much an amateur when it comes to this stuff, but I want to think that I did a lineage19 upgrade on another device I didn't have to do a firmware upgrade.
I downloaded the files a while ago and I definitely read the instructions then, so I can only assume I forgot about the firmware update in the time since.
UPDATE EDIT 11/6: So now I can get into Recovery and have access to an older Lineage Recovery for 18.1 and TWRP but neither allows me to flash any of the Lineage 18.1 OTA files I had extracted from my phone, resulting in a Code:: kInstallDeviceOpenError.
Did I mess up the firmware by trying to install 19.1 without updating the firmware?
I am trying to preserve some files so don't want to wipe the phone completely if at all possible.
LOSXDA98 said:
Started to go down the Lineage 19.1 route. Despite the warning, I forgot to update firmware to 12, realized this halfway through the flash.
Thought no worries, I will just flash 18.1 again as I still have the files, but now I can't get into recovery. Any booting leads only to the crash dump screen
Is an MSM tool reset the only way?
Now I am pretty much an amateur when it comes to this stuff, but I want to think that I did a lineage19 upgrade on another device I didn't have to do a firmware upgrade.
I downloaded the files a while ago and I definitely read the instructions then, so I can only assume I forgot about the firmware update in the time since.
Click to expand...
Click to collapse
Try to boot the recovery file from bootloader mode with fastboot.
LOSXDA98 said:
Started to go down the Lineage 19.1 route. Despite the warning, I forgot to update firmware to 12, realized this halfway through the flash.
Thought no worries, I will just flash 18.1 again as I still have the files, but now I can't get into recovery. Any booting leads only to the crash dump screen
Is an MSM tool reset the only way?
Now I am pretty much an amateur when it comes to this stuff, but I want to think that I did a lineage19 upgrade on another device I didn't have to do a firmware upgrade.
I downloaded the files a while ago and I definitely read the instructions then, so I can only assume I forgot about the firmware update in the time since.
Click to expand...
Click to collapse
You can manually update your firmware and flash the ROM with fastboot.
This thread should have been started in the 8T Q&A forum.
Depending on what you've done, you can sometimes switch slots in bootloader and then boot recovery.
But as recommended by the other responses, reflashing in bootloader is also a good option.
If neither work, then the MSM Tool is the best option to get things going again.
The problem is I can't get into fastboot mode from the hardware buttons, it still results in crash dump screen. Trying to get into recovery the same way results in the same.
LOSXDA98 said:
The problem is I can't get into fastboot mode from the hardware buttons, it still results in crash dump screen. Trying to get into recovery the same way results in the same.
Click to expand...
Click to collapse
No fastboot means the only solution is the MSM Tool. You should feel lucky that you are not on the 10 Pro.
Can I use MSM tool to reflash lineage or is the only option a factory reset?
Not sure if there is any other way to access the data on the device.
LOSXDA98 said:
Can I use MSM tool to reflash lineage or is the only option a factory reset?
Not sure if there is any other way to access the data on the device.
Click to expand...
Click to collapse
I don't know any. Even the firehose readback feature of MSM Tool doesn't allow to backup the data partition.
LOSXDA98 said:
The problem is I can't get into fastboot mode from the hardware buttons, it still results in crash dump screen. Trying to get into recovery the same way results in the same.
Click to expand...
Click to collapse
You can't go straight to fastboot from Crash Dump mode.
You must first get out of Crash Dump using power + vol up (see https://community.oneplus.com/wap/thread/1316587) and then use the keys to get into fastboot.
If you wait too long after getting out of Crash Dump the phone tries to boot again and you'll end up back in CD.
I can get it to shut down using the volume up and power.
So starting from a completely shutdown phone, and holding Volume up and power to go to fast boot, results in crash dump.
Holding volume up and releasing power when the logo appears also results in a crash dump.
Lastly holding both Volume up and Power the entire time results in crash dump.
If there is another combination or I am doing something wrong, I am happy to try again.
Sadly I'm out of ideas.
Well I managed to get into fastboot. I had to hold all buttons down until it loaded.
So I was able to reinstall TWRP, thinking I could use the access to the root to reinstall OS 18.1 from the OTA folder. I just get errors Failed to Mount, 'system root' invalid and 'vendor.'
So now I cannot reinstall 18.1.
Trying to use Lineage Recovery it would not even start the install process.
So now I am not sure what I should try next
LOSXDA98 said:
Well I managed to get into fastboot. I had to hold all buttons down until it loaded.
So I was able to reinstall TWRP, thinking I could use the access to the root to reinstall OS 18.1 from the OTA folder. I just get errors Failed to Mount, 'system root' invalid and 'vendor.'
So now I cannot reinstall 18.1.
Trying to use Lineage Recovery it would not even start the install process.
So now I am not sure what I should try next
Click to expand...
Click to collapse
The first thing I would do is backup important data if you have any using adb from TWRP. Then you could factory reset with MSM Tool or try to flash LOS from fastboot.
Pictures and texts are the important files and to my knowledge TWRP doesn't back those up
I am trying to figure out what the failed install might have corrupted and what I can reflash.
Do I need to reflash dtbo and vbm?
Can I use the newer 19.1 recovery with older OS files?
None of the older 18.1 official build files seem to exist online anymore.
Did I somehow switch partitions, and how would I know this?
LOSXDA98 said:
Pictures and texts are the important files and to my knowledge TWRP doesn't back those up
I am trying to figure out what the failed install might have corrupted and what I can reflash.
Do I need to reflash dtbo and vbm?
Can I use the newer 19.1 recovery with older OS files?
None of the older 18.1 official build files seem to exist online anymore.
Did I somehow switch partitions, and how would I know this?
Click to expand...
Click to collapse
You can use adb to backup files in the internal sdcard while being in TWRP.
Regarding switching partitions, in the reboot menu of TWRP you can see which slot you have activate and switch it.
Does that include texts?
What slot should I be installing in?
I want to say active slot was A
LOSXDA98 said:
Does that include texts?
What slot should I be installing in?
I want to say active slot was A
Click to expand...
Click to collapse
With texts do you mean whatsapp messages or sms?
I would try to install in both slots (first A and if it doesn't work B)
Sms
LOSXDA98 said:
Sms
Click to expand...
Click to collapse
For sure a backup of the data partition will include them but the problem is to be able to restore them afterwards. You can try to find a guide on the internet like this (although this one is old and may be outdated).

Question Deleted recovery mode, need boot.img files plz

please help!
My friend flashed Lineage OS onto my OnePlus 9 5G to try and fix a fingerprint reader problem. It didn't fix the problem so they tried to flash Oxygen 13 back onto the phone. Unfortunately, in Lineage recovery mode, they clicked format and it deleted A and B partitions. The phone now has no recovery mode, which we need to flash any OS onto the phone. The phone now is basically soft bricked and has no OS. We are trying to get oxygen 13 global back on to the phone. We are looking for boot.img files. The phone is rooted and the bootloader is unlocked.
We hav already read through most of the threads on this topic and OnePlus in general. Any recommendations would be helpful, but if you can upload your boot.img files that would be even better. Plz help because this soft bricked phone is STRESSING me.
Have you tried to use an MSM back to stock? That will reflash your partitions. It is essentially plug and click a couple times afaik. Look for an MSM toolkit, but make sure it's the right one for your device region/carrier. Once you MSM to stock you can update to latest OOS. Happy hunting!
Edit: to clarify, using MSM toolkit will get you back to stock; if you are unlocked and rooted I'm assuming you already have drivers installed and working. You do not need anyone to upload their boot.img, MSM will restore your boot image, as well as everything else needed to get oxygen os back on your device.

Categories

Resources