Question OnePlus 9 Pro: Unlocked, but unable to boot into recovery - OnePlus 9 Pro

Hi,
my LE2123 OnePlus 9 Pro is successfully resisting a boot into the recovery. This is not the first phone I flashed, but this time I am a little out of luck and ideas what to do next. Maybe someone would have an idea on what's going wrong - already many thanks in advance.
It's a Model LE2123 with OOS 11.2.2.2.LE15BA7.
As I got it, I did the following:
OEM Unlock
Reboot into Bootloader
fastboot boot twrp-installer-3.6.2_11-0-lemonadep.zip
TWRP puts the device into the "Fastboot Mode" Screen (the on with the icon in the middle) and that's it. Trying other recoveries, like from e.OS (recovery-e-1.1-r-20220629200015-dev-lemonadep.img), this make the phone boot OOS right away.
With that being unsuccessful, I reverted back to stock OOS 11.2.2.2 going through EDL and MsmDownloadTool V4.0.exe, pushing "rev_OverSeas_210324_2236_release_OTA-BLOCK_Signed_fp2103242236_cve2021-03-01_ufs_Oxygen-OS-11.2.2.2.LE15BA" from the forum here on it (Kudos!).
That I updated to OOS 11.2.10.10 through a local system update (using OnePlus9ProOxygen_22.E.13_OTA_0130_all_2111112110_a28e911b11ec5.zip from here as well. Kudos again!).
After that I tried the various recoveries available (twrp-installer-3.6.2 (no other version), e.os recovery (all available), lineageOS recovery (both 18.1 available)). But all of the fail to boot, same as before: TWRP does not start, e.OS and lineageOS recovery hang shortly, then boot the OS (which then takes like 3 minutes to boot, but does so successfully).
So I am right out of clues. If anyone would have an advice what else I could try - greatly appreciated!
Many thanks for your help.

Mjammjam said:
Hi,
my LE2123 OnePlus 9 Pro is successfully resisting a boot into the recovery. This is not the first phone I flashed, but this time I am a little out of luck and ideas what to do next. Maybe someone would have an idea on what's going wrong - already many thanks in advance.
It's a Model LE2123 with OOS 11.2.2.2.LE15BA7.
As I got it, I did the following:
OEM Unlock
Reboot into Bootloader
fastboot boot twrp-installer-3.6.2_11-0-lemonadep.zip
TWRP puts the device into the "Fastboot Mode" Screen (the on with the icon in the middle) and that's it. Trying other recoveries, like from e.OS (recovery-e-1.1-r-20220629200015-dev-lemonadep.img), this make the phone boot OOS right away.
With that being unsuccessful, I reverted back to stock OOS 11.2.2.2 going through EDL and MsmDownloadTool V4.0.exe, pushing "rev_OverSeas_210324_2236_release_OTA-BLOCK_Signed_fp2103242236_cve2021-03-01_ufs_Oxygen-OS-11.2.2.2.LE15BA" from the forum here on it (Kudos!).
That I updated to OOS 11.2.10.10 through a local system update (using OnePlus9ProOxygen_22.E.13_OTA_0130_all_2111112110_a28e911b11ec5.zip from here as well. Kudos again!).
After that I tried the various recoveries available (twrp-installer-3.6.2 (no other version), e.os recovery (all available), lineageOS recovery (both 18.1 available)). But all of the fail to boot, same as before: TWRP does not start, e.OS and lineageOS recovery hang shortly, then boot the OS (which then takes like 3 minutes to boot, but does so successfully).
So I am right out of clues. If anyone would have an advice what else I could try - greatly appreciated!
Many thanks for your help.
Click to expand...
Click to collapse
Alright, so this is what you're going to want to do (please tell me if you attempted this)
1. MSM back to stock, then unlock bootloader
2. Update to 11.2.10.10, then flash recovery (make sure you do fastboot flash boot lineage.img from bootloader, not fastbootd)
3. Then, make sure you type "fastboot reboot recovery"
It should work after that.

Thanks for your reply razor.
I did it similarly, but not identical:
- Instead of flashing the recovery, I just booted into it. (fastboot boot .\lineage-18.1-20220524-recovery-lemonadep.img). In the past this had always worked out as a good way to try it out first.
- I did not not to fastboot reboot recovery, as that happened automatically when fastboot boot was done.
The phone is right now still on 11.2.10.10. It was flashed back to stock 11.2.2.2 using MSM and then from android settings locally updated to 11.2.10.10.
So right now I could go ahead and do as you said:
- fastboot flash boot lineage.img: Which recovery should I use? LineageOS proposes to match it with the Android version, so that should be LOS 18.1: lineage-18.1-20220524-recovery-lemonadep.img ?
- fastboot reboot recovery (I guess that will happen automatically again)
Thanks!
One thing that I checked is that slot B seems to be all empty right now. Setting this as active goes into bootloader right away. Maybe that confuses the recovery.

I managed to get into recovery now, fastboot using twrp.img word.
fastboot boot twrp-3.6.2_11-0-lemonadep.img
With both of these I had no luck getting into recovery, instead they start into OOS right away:
fastboot boot recovery-e-1.1-r-20220629200015-dev-lemonadep.img
fastboot boot lineage-18.1-20220524-recovery-lemonadep.img
LE2123 with OOS 11.2.10.10.LE15BA

Related

Stuck on team win recovery project please help

I have no idea how to root or anything like that, I bought this oneplus 3 and had a update a week later.. so when I did the software update it took me into teamwin recovery mode and now I don't know how to get back into my phone please help....
Did you buy the phone second hand or did you try to flash TWRP yourself? It shouldn't have TWRP installed by default.
Regardless, you can use TWRP to flash the latest update.
Given that you have TWRP, I'm assuming that you have an unlocked bootloader. Did you notice a warning pop up everytime you reboot your phone before? It should say something along the lines of "your device has been unlocked and can't be trusted". If not, you'll have to unlock it (it wipes your phone in the process).
If the bootloader is unlocked, you can simply download and flash the latest zip for OOS 4.0.3 in TWRP. This will update you phone and replace TWRP with the stock recovery (so you don't run into this problem again in the future when installing an OTA). If you don't intend to modify your phone in any way, then this is all you need to do, your phone should be functional.
There are plenty of threads with detailed guides on how to do all of this.
I'm also stuck on TWRP after stupidly downloading the latest OTA and I don't know what to do!
Phone won't boot normal, just goes off.
Situation:
- Bootloader, Fastboot and TWRP wil load.
- Device seen by windows
- Zip install in TWRP gets stuck at 'patching zip unconditiontally'
- Another zip flashes, but gets stuck at the end, no reboot option (manually but that's not the way)
Can someone please point me in the right direction? I don't care if I lose data, just want my phone back!
not helping:
Saying i'm a dipsh-t I know, I know, I will do better in the future, for now, help a brother out please
sndr1384 said:
I'm also stuck on TWRP after stupidly downloading the latest OTA and I don't know what to do!
Phone won't boot normal, just goes off.
Situation:
- Bootloader, Fastboot and TWRP wil load.
- Device seen by windows
- Zip install in TWRP gets stuck at 'patching zip unconditiontally'
- Another zip flashes, but gets stuck at the end, no reboot option (manually but that's not the way)
Can someone please point me in the right direction? I don't care if I lose data, just want my phone back!
not helping:
Saying i'm a dipsh-t I know, I know, I will do better in the future, for now, help a brother out please
Click to expand...
Click to collapse
Simple, check the OnePlus D/L sites for this one http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3.img and flash it by TWRP or fastboot to RECOVERY. Boot once with the official Recovery and all ist fine again.
This is issue of using a faulty twrp so for that when ur phone us booting up go to fastboot and flash twrp 3.0.4-1 and everything will work
emuandco said:
Simple, check the OnePlus D/L sites for this one http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3.img and flash it by TWRP or fastboot to RECOVERY. Boot once with the official Recovery and all ist fine again.
Click to expand...
Click to collapse
Similar Problem here:
just wanted to flash latest OOS 4.0.3, so I flashed back stock recovery with flashify and rebooted into recovery mode to flash the already downloaded OOS 4.0.3. zip. That's when it began to go poop! After rebooting it just went dark with no Chance to power it on again! No dice with power button, Volume up/down + power button, nothing! Not even the LED's are blinking when plugged in. So this one seems to be basically dead!
I got it once booting again after randomly pushing the buttons (after x minutes!?), but everytime I reboot the phone it just shuts off without beeing able to power it on again. At the Moment it's dead!
Any ideas what might happened? If I get it on again, should I immediately reset it to factory Settings?
I am kinda lost here! Any help/ideas would be much appreciated!
Flashify? Never used it and never trusted apps which flash stuff on a running system. Use fastboot and reflash the recovery partition. Link to recovery is in my former post.
fastboot flash recovery PATHTOIMGFILE
Thank you for your advice! Still a lot to learn! Got it up again, will try as you suggested!
It appeared that my stock recovery file was corrupted , but all is fine again! Thank you very much!
Mannycolon85 said:
I have no idea how to root or anything like that, I bought this oneplus 3 and had a update a week later.. so when I did the software update it took me into teamwin recovery mode and now I don't know how to get back into my phone please help....
Click to expand...
Click to collapse
I may have been the person you traded with to get the OnePlus 3, but I took the phone back and after 5 hours I got it up and running.
The phone would boot to TWRP, but even after wiping the entire system and dragging a ROM zip to the internal storage, reinstalling did nothing. It just kept booting back to recovery.
The solution entailed the following.
Download stock recovery IMG. Flashed through TWRP. Rebooted recovery and now was back to stock recovery.
Download the official OxygenOS ROM zip from the OnePlus website and changed the name to update.zip
Next I downloaded Android studio for access to ADB. I had never used ADB before, but I knew this was needed to push a file to the phone.
Needless to say, ADB kept freezing my computer when I would type in the commands to side load.
I deleted Android studio and installed a minimal ADB/Fastboot I found online. I opened my command prompt, typed the command for sideloading, and immediately got my installation starting. It took about 10 minutes to fully install. When it was finished, I rebooted and had a fully functioning OnePlus 3
Sent from my ONEPLUS A3000 using Tapatalk

Swift won't boot into system - straight back to bootloader fastboot mode

I'm trying to be helpful to someone and failing . I've not seen this issue before.
I have a WileyFox Swift that has been unlocked and has TWRP as custom recovery. Internal storage has an installation zip in it so looks like an attempt has been made to flash it. Can't Restore, not sure if a Backup was done. When powered-on it jumps straight to bootloader - fastboot mode. (Start/Power off/Recovery mode/Restart bootloader). Options all work as expected except Start which goes back to bootloader. I can also connect to the handset via usb and receive a response to 'fastboot devices' and other commands.
From TWRP I have installed Lineage nightly rom and the installation has completed successfully. Same for Gapps but the reboot option jumps straight back to bootloader (no sign of a system splash screen). A 'Fastboot continue' command at this point causes a flickering recovery splash screen and then back into bootloader again. I've been in bootloops before but usually a step further on than this. Anybody seen this before - am I missing something obvious?
Hi
Method 1
-if u want to install lineage os
install lineage and reboot it without installing gapps after that install gapps . Hope it works
Method 2
- if method 1 doesn't work for you you need to download and install stock rom for wileyfox swift by adb (fastboot)
See ya
Thanks for the reply. The problem with finding a stock rom is that the Swift shipped with Cyanogen OS 12 (not CyanogenMod). Cyanogen is no more and all links to their website have gone so it's hard to track them down.
I removed the battery from my Swift earlier today and forgot about it for about one hour- I think this has made the difference as I flashed a CyanogenMod 14 rom, rebooted to system and it worked :good:. Went back and flashed Gapps and it worked again :good:. I have an older OS than I want but am fine for the moment.
Good for you

Wiped OS now stuck in TWRP and recovery mode Razer phone 1

This is my first post in the forum and I would definitely appreciate some help. I have a razer phone 1 which I was in the process of rooting. Somewhere in the process I wiped off the OS and now the phone only goes to TWRP and download mode. The bootloader is still unlocked so I tried to follow the steps on the Razer official page
https://developer.razer.com/razer-phone-dev-tools/general-instructions/
However, after running the flash_all.bat command and it goes through the process, the phone reboots back into download mode. To exit download mode I have used the command "fastboot set_active a && fastboot reboot" from the XDA article https://forum.xda-developers.com/t/stuck-on-download-mode-screen.3780764/ but that only gets me back to TWRP not to Razer OS.
I have tried to flash several versions of the factory image that Razer lists here: https://developer.razer.com/razer-p...69.295441011.1615066948-1663073883.1615066948 but keep getting the same result.
I have also followed this post https://forum.xda-developers.com/t/razer-phone-with-no-os-system.3772424/ but I see the OP using adb commands, whereas from download mode I can only use fastboot commands. Regardless I tried following the steps listed there but still no success.
So my questions are:
1) Does it matter which version of the factory image I flash? I know my bootloader is still unlocked so I should be able to flash the OS but for some reason I cannot boot into it.
2) If I correctly flashed the image how can I check from TWRP? In case that the image is flashed but for some reason I just can't access it.
3) If the above questions don't apply/are irrelevant is there something I am doing wrong?
I would appreciate any help.
Just throwing some ideas out there. I haven't used TWRP since my OnePlus One (been using Lineage recovery).
If I understand TWRP correctly from my OnePlus One days, if you can get into TWRP, then I thought you can just flash the ROM of your choosing there (maybe copying the ROM to SD card).

[Solved]Requesting Help Regarding Mi A2 Lite (Stuck in Unlocked Boot loop, No OS installed)

Just this day, November 23, 2021, I have been trying to flash a custom rom named Syberia OS for daisy(Mi A2 Lite variant). As I have done booting up the device to fastboot(thru cmd command since my power button is jammed), I installed the twrp after booting the image to the device, making it as my recovery.
Now I am set and excited to install the rom, so I went to fastboot again and tried to flash the rom, but it always errors and not installing the rom. It is said "to flash multiple zips, reboot recovery before..." (correct me if I'm wrong), so I rebooted to recovery thru the twrp (since its in fastboot). Now, I did the same, I installed the rom again and experienced the same error so I dont know what to do, I did wiped system, data, dalvik and internal storage (a lot of times and tried to install the rom again), but I get the same error.
Then since I cant install the rom, I went to reboot to system thru twrp, and then I forgot, that I have no OS installed.
So now I'm stuck with the "Your device software can't be checked for corruption. Please lock the bootloader. Please visit this link..." plus arriving to the AndroidOne logo, and it turns off and turns on again with the message and logo, repeats until the battery is completely empty.
Is there anything I could do to go to fastboot again for a clean install of the stock rom? (I promise to not unlock the bootloader and experiment on custom roms again)
(I am sorry if you find it hard to understand, I am willing to edit this thread for better understanding if there are things you dont understand.)
This is what I see after all that happened...:
Your browser is not able to display this video.
Any form of response and acknowledgements will be much appreciated )
@hachi_eight
Please read the guidances that are stuck on top of every forum prior to your next posting like
Note: Questions go in Q&A Forum
If you are posting a Question Thread post it in the Q&A forum. Technical discussion of Android development and hacking. No noobs, please. Device-specific releases should go under the appropriate device forum...
forum.xda-developers.com
I've moved the thread to Q&A.
Regards
Oswald Boelcke
Senior Moderator
hachi_eight said:
Just this day, November 23, 2021, I have been trying to flash a custom rom named Syberia OS for daisy(Mi A2 Lite variant). As I have done booting up the device to fastboot(thru cmd command since my power button is jammed), I installed the twrp after booting the image to the device, making it as my recovery.
Now I am set and excited to install the rom, so I went to fastboot again and tried to flash the rom, but it always errors and not installing the rom. It is said "to flash multiple zips, reboot recovery before..." (correct me if I'm wrong), so I rebooted to recovery thru the twrp (since its in fastboot). Now, I did the same, I installed the rom again and experienced the same error so I dont know what to do, I did wiped system, data, dalvik and internal storage (a lot of times and tried to install the rom again), but I get the same error.
Then since I cant install the rom, I went to reboot to system thru twrp, and then I forgot, that I have no OS installed.
So now I'm stuck with the "Your device software can't be checked for corruption. Please lock the bootloader. Please visit this link..." plus arriving to the AndroidOne logo, and it turns off and turns on again with the message and logo, repeats until the battery is completely empty.
Is there anything I could do to go to fastboot again for a clean install of the stock rom? (I promise to not unlock the bootloader and experiment on custom roms again)
(I am sorry if you find it hard to understand, I am willing to edit this thread for better understanding if there are things you dont understand.)
This is what I see after all that happened...:
View attachment 5466081
Any form of response and acknowledgements will be much appreciated )
Click to expand...
Click to collapse
Hey brother, I had the same situation a few months ago. My device - Redmi 6 (Cereus).
So, I was trying to install TWRP in Redmi 6 and then after trying many times TWRP successfully got installed. But when I tried to boot the device, It stuck in bootloop (Going to fastboot and again booting...). So, the answer is that you first boot into fastboot mode of your device and then download the fastboot Rom of your device, (link of fastboot rom of your device - https://xiaomifirmware.com/download/18010/ ) . Then go to your PC and then extrac
the fastboot file, then connect your phone to pc and go to fastboot mode then open the extracted folder and then click on flash-all (The batch file) and then a new command window will open automatically and flashing process will start. After it's done your phone will reboot automatically. For reference, go ahead. Best of luck!
hachi_eight said:
Just this day, November 23, 2021, I have been trying to flash a custom rom named Syberia OS for daisy(Mi A2 Lite variant). As I have done booting up the device to fastboot(thru cmd command since my power button is jammed), I installed the twrp after booting the image to the device, making it as my recovery.
Now I am set and excited to install the rom, so I went to fastboot again and tried to flash the rom, but it always errors and not installing the rom. It is said "to flash multiple zips, reboot recovery before..." (correct me if I'm wrong), so I rebooted to recovery thru the twrp (since its in fastboot). Now, I did the same, I installed the rom again and experienced the same error so I dont know what to do, I did wiped system, data, dalvik and internal storage (a lot of times and tried to install the rom again), but I get the same error.
Then since I cant install the rom, I went to reboot to system thru twrp, and then I forgot, that I have no OS installed.
So now I'm stuck with the "Your device software can't be checked for corruption. Please lock the bootloader. Please visit this link..." plus arriving to the AndroidOne logo, and it turns off and turns on again with the message and logo, repeats until the battery is completely empty.
Is there anything I could do to go to fastboot again for a clean install of the stock rom? (I promise to not unlock the bootloader and experiment on custom roms again)
(I am sorry if you find it hard to understand, I am willing to edit this thread for better understanding if there are things you dont understand.)
This is what I see after all that happened...:
View attachment 5466081
Any form of response and acknowledgements will be much appreciated )
Click to expand...
Click to collapse
Check in the guides section for mi a2 lite. Do a little search before asking. This one
user-001 said:
Check in the guides section for mi a2 lite. Do a little search before asking. This one
Click to expand...
Click to collapse
i fixed it, i opened the back of the phone and managed to fix the power button, and used the combo to get to fastboot mode, and reinstalled the stock OS. so, now I fixed it!
hachi_eight said:
i fixed it, i opened the back of the phone and managed to fix the power button, and used the combo to get to fastboot mode, and reinstalled the stock OS. so, now I fixed it!
Click to expand...
Click to collapse
I am having same issue. What did you do fix the power button?

Cant get back to factory

i am on PE and been on Linage and then Derp but for 2 weeks now ive tried to go back to factory and for the life of me nothing works ive tried the All N One Tool and MSM Tool and nothing i constantly end up back where i started.
Ive downloaded the latest os firmware from oneplus All N One Tool Downloads the firmware extrasts it the pops up a error saying flash all .bat is missing so dead end there.
could someone lead me in the right direction or explain to me if im doing something wrong.... thanks
[CLOSED] T-Mobile 7T Conversion to International WITHOUT unlocked bootloader/SIM unlock!
Here is a patched MSM download tool for TMobile OP7T. It will bypass the need to sim unlock before unlocking the bootloader, and will also bypass the need of an unlock token file from OnePlus (hence skip the wait period of 1 week to get the...
forum.xda-developers.com
this will be my last onepluse thatr for sure going back to Pixel 4 XL didnt have no issues going back to stock this is crazy
I'm having the same issue, so I'm gonna piggyback this in hopes of a different direction.. Long story, short, I've spent hours trying to get back to OOS from crdroid 11. the link above got me back to booting up t-mobile and relocks the bootloader, but wifi radio doesnt work & restarting brings me to being stuck on the boot logo. none of the other MSMtools work, unlocked or TMO from the unbrick page.
what step am i missing after going through the tmo to int. guide? since that's the only thing that's working.. thanks in advance, i'm attempting round 2 in the meantime.
When u r stuck on pink TMobile screen, force reboot to bootloader by holding vol+, vol-, & power buttons for 10 sec. Once you see phone rebooting, let go of power button only to enter bootloader mode. Then type "fastboot reboot fastboot" on PC while USBC cable is plugged into phone. This will kick phone into fastbootD mode. Then fastboot flash all stock rom files.
When wifi and 4g not working, u did not enter fastbootD mode, so system did not flash right
SageChrono said:
I'm having the same issue, so I'm gonna piggyback this in hopes of a different direction.. Long story, short, I've spent hours trying to get back to OOS from crdroid 11. the link above got me back to booting up t-mobile and relocks the bootloader, but wifi radio doesnt work & restarting brings me to being stuck on the boot logo. none of the other MSMtools work, unlocked or TMO from the unbrick page.
what step am i missing after going through the tmo to int. guide? since that's the only thing that's working.. thanks in advance, i'm attempting round 2 in the meantime.
Click to expand...
Click to collapse
Above
HueyT said:
Above
Click to expand...
Click to collapse
i was just coming to edit my post. rookie mistake - i forgot to overwrite adb/fastboot tools everytime i moved the OS files to my adb folder lol... somehow i forgot a bunch of times
phone is booting up without that userspace error, so i may be back in good shape!
edit 2.0: all booted up with wifi/camera working again
well gonna try again for the 4th time this time im gonna use a different computer and see if that works..... UUUGGGG
well the 4th time fail to restore back to stock OOS.. its gotta be something im doing bc i even used a different computer. but gonna keep looking around for another route.
msmdownloaderTool says this (Device Not Match Image) the device seems to time out and disconnects from MSMDownloaderTool every time. any advice i have the global version 7T 1905
HueyT said:
[CLOSED] T-Mobile 7T Conversion to International WITHOUT unlocked bootloader/SIM unlock!
Here is a patched MSM download tool for TMobile OP7T. It will bypass the need to sim unlock before unlocking the bootloader, and will also bypass the need of an unlock token file from OnePlus (hence skip the wait period of 1 week to get the...
forum.xda-developers.com
Click to expand...
Click to collapse
this would not work for me im assuming bc i have the global HD1905 not the T Mobile branded. u can read above why it wouldn't work . but i seem to have made some progress using the All in One Tool i clicked on flash factory image tab and at first it keep error out saying no Flash-All.bat found after unzipping it. so i kelp looking around and finally foud a factory zip that had the Flash-All.bat file in it so tried again using the Allin One Tool clicked Flash Factory image and it unzipped it and flashed fine but now i cant boot to the OOS it just reboots to the " your bootloader is unlocked integrity screen and stays . but i can boot in fastboot mode and recovery which is now factory recovery. i noticed that it flashed the OOS zip on slot A so i think the reason its not booting up to OOS is bc i need it flased on both slots ??
scoot0073 said:
this would not work for me im assuming bc i have the global HD1905 not the T Mobile branded. u can read above why it wouldn't work . but i seem to have made some progress using the All in One Tool i clicked on flash factory image tab and at first it keep error out saying no Flash-All.bat found after unzipping it. so i kelp looking around and finally foud a factory zip that had the Flash-All.bat file in it so tried again using the Allin One Tool clicked Flash Factory image and it unzipped it and flashed fine but now i cant boot to the OOS it just reboots to the " your bootloader is unlocked integrity screen and stays . but i can boot in fastboot mode and recovery which is now factory recovery. i noticed that it flashed the OOS zip on slot A so i think the reason its not booting up to OOS is bc i need it flased on both slots ??
Click to expand...
Click to collapse
[OP7T][OOS 11.0.5.1 HD65AA/BA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
using the " All in One Tool "
Flashing is not allowed for Critical Partitions
is this normal error when flashing back to stock OOS ? when the flashing starts it says this for the first 4 or 5 flashing parts then it stats flashing as described in OP. then it reboots out of fastboot and boots to stock recovery then it finishes the flashing . then at the end it says to press any key to continue and the phone reboots and hangs at the screen that lets me know the bootloader is unlock screen. i flashed both a \b partitions and still does the same thing. its like the boot image is not flashing or im missing something else in the OP to get back to stock OOS.
anyone can help me please ?
"Fastboot reboot fastboot" will enter fastbootD mode to allow flashing system parts
HueyT said:
"Fastboot reboot fastboot" will enter fastbootD mode to allow flashing system parts
Click to expand...
Click to collapse
ok that command worked it successfully Flashed all partitions and when it it it finished it said to press any key to continue .... i did and it rebooted into stock recovery and finished the flashing . then it reboots to the Your Bootloader is unlocked warning and stays there . so i went into recovery and factory reset everything and still hangs at the bootloder unlocked warningthat was all on Slot b so i was like maybe i need to flash both Slots so i switched to slot a active and repeated the whole process above and still nothing hangs again at the bootloader is unlocked warning... ggggrrrrr
what gives..... this is all done using the All in One Tool ... i know im getting close to getting it back to Stock OOS as i made progress with your help.
i then downloaded the factory image from OnePlus site but that was a no go as the zip had only something called Payload which wouldn't flash ..
anymore knowledge u might can share and thank you very much for your help
Go back to fastbootD and flash-all parts manually on A slot, then go to bootloader, type "fastboot set_active other" to go into B slot and repeat fastbootD flashing all parts again. Then go into stock recovery to format data and then reboot
HueyT said:
Go back to fastbootD and flash-all parts manually on A slot, then go to bootloader, type "fastboot set_active other" to go into B slot and repeat fastbootD flashing all parts again. Then go into stock recovery to format data and then reboot
Click to expand...
Click to collapse
that did it im back to all stock oos thank you so much buddy couldn't have doe it without your knowledge. crazy that none of the tools didn't work mine must have been a rare odd ball that i had to flash everything manually.
again thank you.

Categories

Resources