Only official released binaries are allowed to be flashed Download Mode error message - Samsung Galaxy S9 Questions & Answers

So , I just tried to flash TWRP on a SM-G960F/DS via Odin v3.13.3 and I got the error from the title in the Download Mode. The phone works 100% but I really wanna get another UI . I forgot to mention I already unlocked the OEM from dev mode.
EDIT In a way or another the ODIN said PASS but after flashing the TWRP and trying to boot into recovery I was shocked to see the stock Recovery , just why?

Maybe you have Prenormal status. You'll have to wait few days without turning off your phone and then you'll be able to flash twrp.

ZoiraP said:
Maybe you have Prenormal status. You'll have to wait few days without turning off your phone and then you'll be able to flash twrp.
Click to expand...
Click to collapse
the prenormal is likely correct, unsure if the waiting 168 hours is still a thing or not tho.

Related

Unlocking the bootloader without access to the OS

My Nexus 5X just corrupted itself a couple days ago and unfortunately I did not enable OEM unlocking before that happened. I was running stock, un-rooted and from looking online the past couple days I see no way to unlock the bootloader so I can wipe everything and re-flash. I can get into fastboot, but not recovery mode. Recovery mode just says "No Command" with the little android on its side. I have tried all the fastboot commands that one would normally try and they all return some version of "device is locked" error messages. Is there any way at all to unlock the bootloader or flash stock, or otherwise get into recovery without checking that OEM unlocking option in the Developer Options of the OS? I don't care about my data, I just want to get my phone working again. It's out of warranty so I am willing to try anything to get it working again.
I'm in the same situation
This is why I always enable Oem unlocking on all devices I own regardless of security for things like this .
_Ghost said:
This is why I always enable Oem unlocking on all devices I own regardless of security for things like this .
Click to expand...
Click to collapse
Yeah, im going to be doing that from now on. I am pretty sure it was an OTA update that did it. It had just updated a day or two before. I was able to get into Recovery and sideload a different OTA update. The update failed and the phone rebooted, but it rebooted into Android. I was able to get my data off and all seems stable for now.
How did you fix it?!
coryrwest said:
Yeah, im going to be doing that from now on. I am pretty sure it was an OTA update that did it. It had just updated a day or two before. I was able to get into Recovery and sideload a different OTA update. The update failed and the phone rebooted, but it rebooted into Android. I was able to get my data off and all seems stable for now.
Click to expand...
Click to collapse
I am in this exact situation. Phone out of warranty, just want to get it back on, don't care about the data on it.. but the "device state" is locked. I can get it into recovery but the sideload fails, I think because the device is locked. How did you get your phone to work again??
I've tried following these instructions (I'm new and can't post a URL: [ttps://drive.google.com/file/d/0Bz6x7k-VkpUJam5Mc1hKa09PVGc/view) and it fails during step 19.
I've also tried these instructions (I can't post the URL but if you google this exact phrase, it's the first link: Nexus 5X Bootloop Fix - The Step-by-step DIY Guide - TechBii) but the phone is locked so I can't do it.
Help!
See this post please: https://forum.xda-developers.com/nexus-5x/general/petition-google-release-official-t3672987
Thanks
So did you ever get it to work or just thre the phone in the garbage, @coryrwest
See my latest post in the thread: https://forum.xda-developers.com/showpost.php?p=71241965&postcount=4
How?
coryrwest said:
Yeah, im going to be doing that from now on. I am pretty sure it was an OTA update that did it. It had just updated a day or two before. I was able to get into Recovery and sideload a different OTA update. The update failed and the phone rebooted, but it rebooted into Android. I was able to get my data off and all seems stable for now.
Click to expand...
Click to collapse
I'm having a similar issue, how did you exactly get it into recovery? Cause mine will simply keep rebooting if I select recovery mode from bootloader

Oneplus 3 Bricked - Unbrick doesn't work...

Hello guys,
my Oneplus 3 is hard bricked, I tried the methods in the Mega Unbrick guide, my device already gets shown as Qualcomm 9008 ... in Device Manager, so I started the MSM DownloadTool and it flashed anything without errors. But when the phone reboots I get a black screen and the white led is on.
I can't even boot to stock recovery (Volume down + power doesn't work and rebooting to recovery through fastboot doesn't work, too....) my bootloader is locked and all attempts to unlock the bootloader are failing with the error "remote: oem unlock is not allowed"
So at the moment I'm stuck in fastboot and nothing else works -.-
Can someone please help me?
The unbrick tool has an old firmware, can I replace the files with files from a newer firmware?
Thanks!
Have you tried the exact steps from Method 2? Maybe unzip it? If that doesn't work which is highly unlikely then there is not much you can do.
Puddi_Puddin said:
Have you tried the exact steps from Method 2? Maybe unzip it? If that doesn't work which is highly unlikely then there is not much you can do.
Click to expand...
Click to collapse
Yeah I tried it as I said, the MSM DownloadTool showed me Completed and the phone tried to boot up after that.
I'm now contacting the OP Customer Support, I've read a few times that they have other files to unbrick the phone with the MSM Tool.
min-dfreak said:
Yeah I tried it as I said, the MSM DownloadTool showed me Completed and the phone tried to boot up after that.
I'm now contacting the OP Customer Support, I've read a few times that they have other files to unbrick the phone with the MSM Tool.
Click to expand...
Click to collapse
Ye thats the only thing you can currently do... May i ask what you have done how did it get bricked?
I just updated AICP ota and after flashing the update my phone didn't boot up. The screen went black immediately.
So I thought that it is maybe a Problem with the ROM and I tried to go back to stock.
Flashed the stock recovery and locked the bootloader, but I couldn't boot to the stock recovery.
There it started...
Switch off the phone, connect usb ,open unbrick tool full ( method 2),Press vol up,down and power buttons same time ,tool will recognize phone then start , you must unbrick now.
NEVER LOCK YOUR PHONE.
drmuruga said:
Switch off the phone, connect usb ,open unbrick tool full ( method 2),Press vol up,down and power buttons same time ,tool will recognize phone then start , you must unbrick now.
NEVER LOCK YOUR PHONE.
Click to expand...
Click to collapse
Please read, I already did that.
The tool completed it successfully, but still black screen after a reboot.
Only the LED is flashing white.
I already contacted the support, they will do it remotely tomorrow.
min-dfreak said:
Please read, I already did that.
The tool completed it successfully, but still black screen after a reboot.
Only the LED is flashing white.
I already contacted the support, they will do it remotely tomorrow.
Click to expand...
Click to collapse
Never but never lock your bootloader...
If recovery, boot or system partition is modified. There's no harm in re locking otherwise..
Hi guy i have a big problem i buy a one plus 3 i was using it 1 month and there was a update i don't remember what it was oreo or nougat when the update downloaded i install it and the i got a bootloop 2 hours didn't boot and my device is not rooted and didn't enable developer option i tried to install stock rom by adb and fastboot with sideload it load but it stuck on 50% then it say failed tried to install recovery in fastboot i installed drive oneplus 3 ect but can't flash it i think because i have oem locked i trien to unlocked it says failed 00.6s ect and i don't have guarantee i have dash and cable charger i can charge it and go to fastboot and recovery but when i boot my phone normally i show logo one plus then the two red bullet who move then it power off
Dsn Fouad said:
Hi guy i have a big problem i buy a one plus 3 i was using it 1 month and there was a update i don't remember what it was oreo or nougat when the update downloaded i install it and the i got a bootloop 2 hours didn't boot and my device is not rooted and didn't enable developer option i tried to install stock rom by adb and fastboot with sideload it load but it stuck on 50% then it say failed tried to install recovery in fastboot i installed drive oneplus 3 ect but can't flash it i think because i have oem locked i trien to unlocked it says failed 00.6s ect and i don't have guarantee i have dash and cable charger i can charge it and go to fastboot and recovery but when i boot my phone normally i show logo one plus then the two red bullet who move then it power off
Click to expand...
Click to collapse
I'm assuming your device is OnePlus3 and not 3T
Okay. Firstly give a try to Oneplus3 openbeta Nougat special edition.
Oneplus3 : http://downloadmirror.co/Wa9/O2N_OBT_15801_OXYGEN_SIGN_wipe.zip
Method 1 : specific recovery for open beta24 available in Oneplus downloads
https://downloads.oneplus.com
Find legacy roms and find openbeta 24
Method 2: latest TWRP
If your bootloader is locked this isn't gonna work. But if it is still in unlocked .
Download TWRP for Oneplus3 from official TWRP site
Flash the recovery you choose using fast boot.
Now using asn command, try to flash the special edition.
Mostly this solves your issue. It helped me.
Let me know whether you face any issues.
Note: in this method you may lose every data you have on the phone. It boots up (if at all ? ) with fresh firmware and fresh storage (sometimes)
SivaMaxwell said:
I'm assuming your device is OnePlus3 and not 3T
Okay. Firstly give a try to Oneplus3 openbeta Nougat special edition.
Oneplus3 : http://downloadmirror.co/Wa9/O2N_OBT_15801_OXYGEN_SIGN_wipe.zip
Method 1 : specific recovery for open beta24 available in Oneplus downloads
https://downloads.oneplus.com
Find legacy roms and find openbeta 24
Method 2: latest TWRP
If your bootloader is locked this isn't gonna work. But if it is still in unlocked .
Download TWRP for Oneplus3 from official TWRP site
Flash the recovery you choose using fast boot.
Now using asn command, try to flash the special edition.
Mostly this solves your issue. It helped me.
Let me know whether you face any issues.
Note: in this method you may lose every data you have on the phone. It boots up (if at all ? ) with fresh firmware and fresh storage (sometimes)
Click to expand...
Click to collapse
Yeah i have oneplus 3 my bootloader is locked can't flash anything im going to try method 1
By the way why beta 24 why not lastest update ? And whene i download it do you want me to flash it with sideload like #adb sideload openbeta24.zip ?
Dsn Fouad said:
Yeah i have oneplus 3 my bootloader is locked can't flash anything im going to try method 1
By the way why beta 24 why not lastest update ? And whene i download it do you want me to flash it with sideload like #adb sideload openbeta24.zip ?
Click to expand...
Click to collapse
The file I gave link to is a special edition by Oneplus for Openbeta-Nougat. You can go to Nougat from any rom.
Rom: http://downloadmirror.co/Wa9/O2N_OBT_15801_OXYGEN_SIGN_wipe.zip
Specific recovery should be downloaded from Oneplus website.
You can sideload using adb or store internal storage and flash.
I tried with latest TWRP recently and it worked.
Note that all your data gets wiped if you use oneplus-recovey and asn sideload
SivaMaxwell said:
The file I gave link to is a special edition by Oneplus for Openbeta-Nougat. You can go to Nougat from any rom.
Rom: http://downloadmirror.co/Wa9/O2N_OBT_15801_OXYGEN_SIGN_wipe.zip
Specific recovery should be downloaded from Oneplus website.
You can sideload using adb or store internal storage and flash.
I tried with latest TWRP recently and it worked.
Note that all your data gets wiped if you use oneplus-recovey and asn sideload
Click to expand...
Click to collapse
The problem is i dont have store internal storage and when i try to flash anything it say oem locked not allowed and when i flash a rom with adb sideload jfjd.zip it stuck on 60% will it be complete if i use your beta ?
Dsn Fouad said:
The problem is i dont have store internal storage and when i try to flash anything it say oem locked not allowed and when i flash a rom with adb sideload jfjd.zip it stuck on 60% will it be complete if i use your beta ?
Click to expand...
Click to collapse
Yes, it won't stick at 60% with this beta. I'm not the owner. It was provided on Oneplus forums. Try that one and tell me the result. It is a signed zip. So it will work on official Oneplus-recovery
SivaMaxwell said:
Yes, it won't stick at 60% with this beta. I'm not the owner. It was provided on Oneplus forums. Try that one and tell me the result. It is a signed zip. So it will work on official Oneplus-recovery
Click to expand...
Click to collapse
Thanks i will download and give it a try
SivaMaxwell said:
Yes, it won't stick at 60% with this beta. I'm not the owner. It was provided on Oneplus forums. Try that one and tell me the result. It is a signed zip. So it will work on official Oneplus-recovery
Click to expand...
Click to collapse
Before that i downloaded msm download tool 3.0.8 i tested it and it boot but it say enter pin password i dont know what is the pin i didn't use a pin before it was working
Dsn Fouad said:
Before that i downloaded msm download tool 3.0.8 i tested it and it boot but it say enter pin password i dont know what is the pin i didn't use a pin before it was working
Click to expand...
Click to collapse
Simply reboot to recovery and say yes to wipe every data.
Note1:
all your internal data is wiped in the method I suggested. I can recall there is a method to recover data only if bootloader is unlocked. If your bootloader is locked there is no other way.
Note2: your data will be formatted to f2fs file system. If you want to flash any custom ROM, YOU SHOULD CHECK COMPATIBILITY WITH F2FS in that ROM forums.
It's better to always have EXT4 file system. You can change this file system with TWRP
SivaMaxwell said:
Simply reboot to recovery and say yes to wipe every data.
Note1:
all your internal data is wiped in the method I suggested. I can recall there is a method to recover data only if bootloader is unlocked. If your bootloader is locked there is no other way.
Note2: your data will be formatted to f2fs file system. If you want to flash any custom ROM, YOU SHOULD CHECK COMPATIBILITY WITH F2FS in that ROM forums.
It's better to always have EXT4 file system. You can change this file system with TWRP
Click to expand...
Click to collapse
Bootloader is locked i tryed to flash the 24 beta yoi give me but it stuck on 47 and say failed im just going to sell it
Dsn Fouad said:
Bootloader is locked i tryed to flash the 24 beta yoi give me but it stuck on 47 and say failed im just going to sell it
Click to expand...
Click to collapse
Even if the bootloader is locked, you can boot into the current rom and unlock simply by going to advanved options.
It is a very simple process.

OEM unlock issue

Hello
I was on an android 9.0 GSI image.
After disabling developer options in settings the device couldn't boot.
It was showing "custom firmware blocked by FRP lock" error.
I couldn't enter TWRP recovery as well. So I restored stock firmware through odin.
I tried to toggle on OEM unlock in settings with no result, after reboot it remains OEM and FRP locked. I also tried to OEM unlock through combination firmware but the toggle doesn't work.
Does anyone know if there is a solution to this problem ?
Thanks in advance,
NoirX said:
Hello
I was on an android 9.0 GSI image.
After disabling developer options in settings the device couldn't boot.
It was showing "custom firmware blocked by FRP lock" error.
I couldn't enter TWRP recovery as well. So I restored stock firmware through odin.
I tried to toggle on OEM unlock in settings with no result, after reboot it remains OEM and FRP locked. I also tried to OEM unlock through combination firmware but the toggle doesn't work.
Does anyone know if there is a solution to this problem ?
Thanks in advance,
Click to expand...
Click to collapse
Probably going to have to wait 7 days
*Detection* said:
Probably going to have to wait 7 days
Click to expand...
Click to collapse
I tried that too but i think the issue is a little bit more complicated. The toggle is there but it does nothing. On stock firmware it goes through a factory reset as expected but the device remains oem locked. On combination firmware the toggle is there too, but it won't switch on. Thank you.
I have a similar issue....
Waited a full week for the OEM Unlock.
Ticked it last night.
Rebooted to download mode > Flashed TWRP > Passed.
Rebooted to TWRP, it showed up, then it presented a bunch of red code errors before quickly resetting and defaulting back to normal Recovery again..... WTF
Looks like ill have to wait another 7 days because in Download mode it now says OEM Mode is Unlocked but its still RMM State: PreNormal mode on... no OEM Unlock setting in my Developer settings.
Anyone else had an issue with TWRP randomly throwing up errors upon first boot and then restarting before you can do anything???
I used the Patched ODIN here: https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
Combined with TWRP 3.2.3-0 recovery....
AMDPOWERFIST said:
I have a similar issue....
Waited a full week for the OEM Unlock.
Ticked it last night.
Rebooted to download mode > Flashed TWRP > Passed.
Rebooted to TWRP, it showed up, then it presented a bunch of red code errors before quickly resetting and defaulting back to normal Recovery again..... WTF
Looks like ill have to wait another 7 days because in Download mode it now says OEM Mode is Unlocked but its still RMM State: PreNormal mode on... no OEM Unlock setting in my Developer settings.
Anyone else had an issue with TWRP randomly throwing up errors upon first boot and then restarting before you can do anything???
I used the Patched ODIN here: https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
Combined with TWRP 3.2.3-0 recovery....
Click to expand...
Click to collapse
Why are you using a patched ODIN?
Uncheck "Auto Reboot" in ODIN settings, once TWRP has flashed disconnect USB then power off the phone and immediately boot into recovery, do not let it reboot first
*Detection* said:
Why are you using a patched ODIN?
Uncheck "Auto Reboot" in ODIN settings, once TWRP has flashed disconnect USB then power off the phone and immediately boot into recovery, do not let it reboot first
Click to expand...
Click to collapse
I'll try with normal Odin next time. I do suspect this might have been the issue.
AMDPOWERFIST said:
I have a similar issue....
Waited a full week for the OEM Unlock.
Ticked it last night.
Rebooted to download mode > Flashed TWRP > Passed.
Rebooted to TWRP, it showed up, then it presented a bunch of red code errors before quickly resetting and defaulting back to normal Recovery again..... WTF
Looks like ill have to wait another 7 days because in Download mode it now says OEM Mode is Unlocked but its still RMM State: PreNormal mode on... no OEM Unlock setting in my Developer settings.
Anyone else had an issue with TWRP randomly throwing up errors upon first boot and then restarting before you can do anything???
I used the Patched ODIN here: https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
Combined with TWRP 3.2.3-0 recovery....
Click to expand...
Click to collapse
@*Detection*, I had the exact same issue as yours tonight when I tried to install TWRP for the first time. Red code errors then an automatic restart and then default back to normal Recovery. As far as I know I used normal Odin and I followed installation instructions to the letter. So back to square one for me. I'll definitely have another crack in 7 days. Interested to know how you went with your second effort. If you had success please post what you did step by step.
And @AMDPOWERFIST, out of interest, how do you power the phone OFF from the Download screen? I know how to restart. Thanks.
bulky68 said:
@*Detection*, I had the exact same issue as yours tonight when I tried to install TWRP for the first time. Red code errors then an automatic restart and then default back to normal Recovery. As far as I know I used normal Odin and I followed installation instructions to the letter. So back to square one for me. I'll definitely have another crack in 7 days. Interested to know how you went with your second effort. If you had success please post what you did step by step.
And @AMDPOWERFIST, out of interest, how do you power the phone OFF from the Download screen? I know how to restart. Thanks.
Click to expand...
Click to collapse
Just realised that I got the 2 posters mixed up in my previous post. My apologies @*Detection* and @AMDPOWERFIST.

stuck on samsung logo boot screen - help

Hi,
I'm stuck on 'samsung' logo screen after flashing stock rom. Please see details below if you can assist.
1. I have sm-505fn from carphone warehouse uk with jan/feb 2020 update..
2. I did oem unlock and flashed twrp
3. this gave bootloader warnings, but eventually went into twrp.
4. I didn't do the dm verify installation and after couldn't get into twrp again. (not sure how to sideload this at this stage)
because i didn't do above step and rebooted, i think i tripped the knox and SG/RMM state became 'prenormal'.
kept getting error: "Only official released binaries are allowed to be flashed" if i tried installing twrp again.
5. tried installing stock rom btu for march 2019, but odin gave errors as couldn't install older stock.
6. then installed feb 2020 stock from sammobile rom A505FNXXS4ATB1 which is the btu version.
7. above worked fine with odin and everything succeeded.
8. On reboot the first warning vanished, and I only got the 2nd bootloader warning. phone went through a 5 second update screen, then rebooted.
9. then got samsung a50 logo and system started booting with plain samsung logo.
10. been stuck at plain samsung logo for 40 min. tried restarting but same problem.
Can you please advise what i should do?
Can't believe its such a headache to install twrp this device (and then later remove the bl warnings
Thanks
ok, I got stock reinstalled and it worked in the end.
the bootloader was unlocked, and developer option to unlock was greyed out.
as it still gave the bootlocker warning, i turned oem lock on again via long press up on download mode. this fixed all warnings and i can boot now without warnings.
when i go into developer mode now, there is no option to oem unlock again.
if i go into download mode, there is no option to long press up and unlock again
on download mode it says:
KG State: prenormal
OEM Lock: ON (U1)
how can I turn oem lock off again, so I can try to install twrp?
Please assist.
thanks
SOLVED -
managed to turn oem unlock option again by turning off auto time update and setting clock back 10 days.
then on restart, the option appeared again and was set to oem unlock ticked.
went into download mode and i could see option again to unlock booloader.
long pressed up and it unlocked bootloader, erased data and restarted to system....
now... lets try to install twrp again and hope it doesn't give me 'unofficial binary' error due to SG prenormal state.
lol.. its KG STATE not SG fyi
Typo
lawmanukdc said:
Typo
Click to expand...
Click to collapse
lol id believe that in 1 comment but everywhere? oh well no biggie lol.. hope ur enjoyin ur phone now
How did you succeed to get the stock reinstalled ? Was it different version ?
lawmanukdc said:
ok, I got stock reinstalled and it worked in the end.
the bootloader was unlocked, and developer option to unlock was greyed out.
Click to expand...
Click to collapse

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