Hi im having a hard time figuring this out, this is a brand new 5t that bricked itself while ota updating
the device is in a boot loop (wont go any further than the oneplus logo)
if i enter to the recovery it says LOCKED, and the oem unlock option on android is not enabled
im in argentina so i cant send the phone to oneplus rma
{
"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"
}
is there any way to unlock the bootloader? then i would be able to flash it and save the phone
Ps: a level 2 OnePlus tech guy tried a remote fix with the official brand software and it did not work
https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unbricking-tool-confirmation-t3733012
Hope that helps. If you can get it to load in that mode, it'll fix about anything.
es0tericcha0s said:
https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unbricking-tool-confirmation-t3733012
Hope that helps. If you can get it to load in that mode, it'll fix about anything.
Click to expand...
Click to collapse
Thanks a lot! i think that oneplus did use that file and did not work but i will try it again (at least 10 times)
I think it might be tricky to get it into the QHUSB mode unless it's hard bricked. I've fixed a 3t like that but luckily haven't had issues on the 5t yet. I think the only way might be via test point (which would require some hardware work that's not recommended for beginners). Thinking about it now, this might not have been the best solution to provide for your particular issue.
Just thought about this after re-reading your post. When you say that you booted into Recovery and it says locked but you posted a picture of the Fastboot screen showing just that the bootloader is locked - which is to be expected unless you went through the bootloader unlock process.
What happens when you actually boot to recovery? Have you tried factory resetting it there? I imagine the remote desk guy might have tried to adb sideload the update?
This is why I wish we had a fastboot OEM image install option like Google provides.
Maybe we do though and I just haven't found it yet.
Haven't looked very hard.
es0tericcha0s said:
I think it might be tricky to get it into the QHUSB mode unless it's hard bricked. I've fixed a 3t like that but luckily haven't had issues on the 5t yet. I think the only way might be via test point (which would require some hardware work that's not recommended for beginners). Thinking about it now, this might not have been the best solution to provide for your particular issue.
Just thought about this after re-reading your post. When you say that you booted into Recovery and it says locked but you posted a picture of the Fastboot screen showing just that the bootloader is locked - which is to be expected unless you went through the bootloader unlock process.
What happens when you actually boot to recovery? Have you tried factory resetting it there? I imagine the remote desk guy might have tried to adb sideload the update?
Click to expand...
Click to collapse
if i boot to recovery and press the power button to select factory reset or any usefull option, the phone resets, i think that the problem is a corrupt recovery, thats why i want to unlock it, install TWRP and then try to flash android
CZ Eddie said:
This is why I wish we had a fastboot OEM image install option like Google provides.
Maybe we do though and I just haven't found it yet.
Haven't looked very hard.
Click to expand...
Click to collapse
maybe this is an anti thief security measure? (since android 6.0 )
es0tericcha0s said:
I think it might be tricky to get it into the QHUSB mode unless it's hard bricked. I've fixed a 3t like that but luckily haven't had issues on the 5t yet. I think the only way might be via test point (which would require some hardware work that's not recommended for beginners). Thinking about it now, this might not have been the best solution to provide for your particular issue.
Just thought about this after re-reading your post. When you say that you booted into Recovery and it says locked but you posted a picture of the Fastboot screen showing just that the bootloader is locked - which is to be expected unless you went through the bootloader unlock process.
What happens when you actually boot to recovery? Have you tried factory resetting it there? I imagine the remote desk guy might have tried to adb sideload the update?
Click to expand...
Click to collapse
why would i have a problem putting the 5t on qhusb? i did not know that it could be done via testpoint
the phone works, the problem seems to be a faulty file on the bootloader or maybe an internal damage from factory (i hope this is not the case)
in a few hours i will try it all and post the result
Typically a phone will only go into the Qualcomm QHUSB mode when it's hard bricked. You're only soft bricked. What happens when you actually get into Recovery?
es0tericcha0s said:
Typically a phone will only go into the Qualcomm QHUSB mode when it's hard bricked. You're only soft bricked. What happens when you actually get into Recovery?
Click to expand...
Click to collapse
I did the entire process and the result is the same as before doing it, the phone turns on and gets stuck on the oneplus logo, it does nothing else, the recovery works but doesnt do anything usefull
Do you get any errors when performing a factory reset? As in a partition not mounting? Since your baseband doesn't show in the fastboot mode, I'm thinking maybe an /efs error. If you got it new, I'd talk to 1+ about an RMA since this was caused by an official update and one of their technicians already failed to fix it.
es0tericcha0s said:
Do you get any errors when performing a factory reset? As in a partition not mounting? Since your baseband doesn't show in the fastboot mode, I'm thinking maybe an /efs error. If you got it new, I'd talk to 1+ about an RMA since this was caused by an official update and one of their technicians already failed to fix it.
Click to expand...
Click to collapse
It may well be a partition error, one+ is not being helpfull right now
I did comit an error saying that the recovery works, it doesnt work, the pone only goes into fastboot and qhusb mode, after that it will allways get stuck on the oneplus logo
On adb i get feedback if i try to flash the phone says "not allowed, locked device"
I think that the problem is a corrupt bootloader
The msmdownloader tool works, i dont know what It copies on to the terminal but i want to flash the recovery and bootloader using that tool, i dont know if it is possible
this the md5sum file that i found in a compilation for oneplusone (msmdownloader tool)
so i shoud be able to do the same with the 5t
es0tericcha0s said:
Typically a phone will only go into the Qualcomm QHUSB mode when it's hard bricked. You're only soft bricked. What happens when you actually get into Recovery?
Click to expand...
Click to collapse
that is no true, u just have the phone powered off and then hold the volume + and plug the device in, if u saw the video in the unbrick post he was not bricked at all and everything was working good and still did a restore, not sure why it is not working for the OP but it should fix it.
Yes i can enter into qhusb, and i can flash the phone with msm downloader, but i used the origibal file that oneplus technicians use amd it didnt work, now i want to flash hydrogen os or the recovery file only into the terminal but i dont know how to modify the msm downloader (the unbrick tool)
Had the same error message tonight after spontaneous reboot of my (unmodified and locked) device. Fortunately, reimaging with stock ROM from downloads.oneplus.net via adb sideload worked for me, without losing any data. Tried that?
sascha224 said:
Had the same error message tonight after spontaneous reboot of my (unmodified and locked) device. Fortunately, reimaging with stock ROM from downloads.oneplus.net via adb sideload worked for me, without losing any data. Tried that?
Click to expand...
Click to collapse
I remember that the device wouldnt flash anything because it was locked, but I will try the sideload right away
It has been impossible to fix, this is the best i got doing fastboot boot recovery.img
Related
Would someone mind helping me out, I cant use my phone any more. The last thing I did was install Emotion OS and then I installed the Emotion Kernel, upon reboot the phone was stuck on the emotion boot screen after restarting the phone Im not sure how it happened however the phone went from TWRP to some recovery that looks like the lineageos logo, I cant install any updates from this recovery and my phone via USB in download mode or ADB is not detected by any computer I have tried 3 computers in my house. I have never seen this recovery screen and I do not know what to do. I downloaded a stock MM firmware and converted it to a zip file from a tutorial on here however I keep getting an error message from this recovery. I really need my phone back up and running Im not sure what the heck happened.
Continued from other posts
Quote:
Originally Posted by shadeau
Do you have any options in recovery? Even if you could perform a "factory reset" with lineage OS you'd at least be able to enable ADB and reinstall TWRP. Also, when you say that the phone isn't recognized by the computer does that mean ADB, ODIN, and your OS don't recognize the phone?
So I do have options in this Lineage Recover but I cant get anything to work, Here are my options Reboot System Now, Apply Update, Factory Reset, Advanced. I have already tried factory reset however I may have deleted the OS all together with the Wipe Data Option. When I reboot the phone it stays on the the Samsung Galaxy Note 4 Screen with the little padlock that shows my bootloader is unlocked. I was messing around with flashing betwen several roms, I went from CM 14.1 to Lineage to Emotion OS, I then flashed the emotion kernel. If I select Apply update it gives me these several options, Apply from ADB choose from emulated (no typo) choose from sdcard1. I have tried to sideload via adb shell and my pc ( have tried multiple computers) does not detect the device. I even went to the extent of reinstalling windows and all Samsung USB and ADB drivers. Selecting choose from sdcard1 I can see the various zip files on my sd card however when it goes to install any roms it fails and just says error. There is a error log however it will not let me view these. My phone before this stopped connecting to any pc's I could plug the phone in via usb and it would charge but I would not get any notifications from windows! I will seriously send money to who ever can hlep me out I do not want to shell out for a new phone. Placing the phone in download mode still works however odin will not detect the phone either lol what the heck is going on here. I do have a micro sd card reader for the mc so i can place files on the phones card but I dont know what kind of file this recovery is looking for. I do not know how this recovery even got on here as I have been using TWRP from the very beginning. Please help me
I have never seen this recovery it has the lineage os logo and just says RECOVERY. I wish I could take a picture of the screen.
I have also tried renaming files on my sd card as update.zip and this does not help. It comes back with an error every time.
ziggsta2 said:
I have also tried renaming files on my sd card as update.zip and this does not help. It comes back with an error every time.
Click to expand...
Click to collapse
Are you using the Samsung OEM USB cord?
quinciebee said:
Are you using the Samsung OEM USB cord?
Click to expand...
Click to collapse
good questions will try another usb cable all I have is 1 for right now
quinciebee said:
Are you using the Samsung OEM USB cord?
Click to expand...
Click to collapse
Do you know what recovery this is? It has the lineage symbol! I cant find a picture of it any where if someone knew what recovery it was maybe then I could research info from the name
ziggsta2 said:
Do you know what recovery this is? It has the lineage symbol! I cant find a picture of it any where if someone knew what recovery it was maybe then I could research info from the name
Click to expand...
Click to collapse
It sounds likes it's the default factory recovery, you probably lost TWRP when you flashed the rom. When Odin recognizes your phone again, just Odin TWRP in there through download mode and you should be good to go.
quinciebee said:
It sounds likes it's the default factory recovery, you probably lost TWRP when you flashed the rom. When Odin recognizes your phone again, just Odin TWRP in there through download mode and you should be good to go.
Click to expand...
Click to collapse
When I plug my phone into a USB port I get a grey battery icon however it doesn't appear that its doing anything, is it possible I have a bad usb port on my phone? Odin wont recognize it, I have yet to find a single computer to see my phone, and I have now tried multiple USB cables.
ziggsta2 said:
When I plug my phone into a USB port I get a grey battery icon however it doesn't appear that its doing anything, is it possible I have a bad usb port on my phone? Odin wont recognize it, I have yet to find a single computer to see my phone, and I have now tried multiple USB cables.
Click to expand...
Click to collapse
Try unplugging your phone completely, pull the battery, boot into download mode, then plug it into your computer using the Samsung USB cord.
quinciebee said:
Try unplugging your phone completely, pull the battery, boot into download mode, then plug it into your computer using the Samsung USB cord.
Click to expand...
Click to collapse
I wish that was the fix, I have tried everything at this point, for the life of me i cannot get any pc to recognize this phone. If I could get odin to detect the phone I would be all set
ziggsta2 said:
I wish that was the fix, I have tried everything at this point, for the life of me i cannot get any pc to recognize this phone. If I could get odin to detect the phone I would be all set
Click to expand...
Click to collapse
CHECK THIS OUT People are having the same issues
https://forum.xda-developers.com/android/help/phone-stuck-bootloop-t3510266
{
"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"
}
ziggsta2 said:
Click to expand...
Click to collapse
In the advanced menu is there an option to "mount system" or something? Also see if there's a setting in there for chmod
I actually ordered a new note 4 I believe my device is dead I will have to charge it as when I try to boot into recovery the words no command flash very quickly on the bottom of the screen, I do know I saw mount system I remember trying it and it didn't do anything but I will charge it tonight and try it. I have read about the nexus 6p and how 7.1.1 has bricked alot of devices, do you think upgrading to Emotion Os 7.1 was the culprit?
ziggsta2 said:
I actually ordered a new note 4 I believe my device is dead I will have to charge it as when I try to boot into recovery the words no command flash very quickly on the bottom of the screen, I do know I saw mount system I remember trying it and it didn't do anything but I will charge it tonight and try it. I have read about the nexus 6p and how 7.1.1 has bricked alot of devices, do you think upgrading to Emotion Os 7.1 was the culprit?
Click to expand...
Click to collapse
I just tried EmotionOS over the weekend and had no issues so I'm not sure that's the culprit. I think you accidentally flashed something into the recovery partition that broke it. Another possibility is that the latest EmotionOS build is specifically designed for the custom TWRP that @hsbadr made. I used that to flash EmotionOS then returned to stock TWRP to flash a different ROM.
shadeau said:
I just tried EmotionOS over the weekend and had no issues so I'm not sure that's the culprit. I think you accidentally flashed something into the recovery partition that broke it. Another possibility is that the latest EmotionOS build is specifically designed for the custom TWRP that @hsbadr made. I used that to flash EmotionOS then returned to stock TWRP to flash a different ROM.
Click to expand...
Click to collapse
You know what you might be right I don't remember ever changing TWRP, what is weird is that I lost all usb connectivity too a point that could be due to a damaged usb port, too many unknowns at this point. It was a little embarrassing in the household when I had to admit that I bricked my phone. I was asked if I was going to mess with my new phone......I will have it rooted and unlocked TONIGHT lol
ziggsta2 said:
You know what you might be right I don't remember ever changing TWRP, what is weird is that I lost all usb connectivity too a point that could be due to a damaged usb port, too many unknowns at this point. It was a little embarrassing in the household when I had to admit that I bricked my phone. I was asked if I was going to mess with my new phone......I will have it rooted and unlocked TONIGHT lol
Click to expand...
Click to collapse
Well, good luck! Send me a PM if you have trouble finding the links to unlocking and rooting.
Ha I got there too man . pretty cool recovery wish I wouldn't have fixed it so fast might try duplicate your accident. OK its an easy fix just flash twrp in Odin for our device then boot back into twrp and do a complete wipe (might not be possible if u can't see sdcard if that is case wipe data system cache art/cache then install then wipe the internal after ROM flash . at this point I would factory reset and backup but hey that's me . anyway should be fine from here. BTW did you select the DL recovery option in dev options? I was wondering if that's how I got there the (lineage recovery) the first time. Lol your post made me want to check it out. Omg bud i almost forgot and this is crucial. Aosp ROMs like emotion take a long long time to boot the first time(damn near 15 mins) ! The last thing you want to do is mistake this for a bootloop
mojoswagger1980 said:
Ha I got there too man . pretty cool recovery wish I wouldn't have fixed it so fast might try duplicate your accident. OK its an easy fix just flash twrp in Odin for our device then boot back into twrp and do a complete wipe (might not be possible if u can't see sdcard if that is case wipe data system cache art/cache then install then wipe the internal after ROM flash . at this point I would factory reset and backup but hey that's me . anyway should be fine from here. BTW did you select the DL recovery option in dev options? I was wondering if that's how I got there the (lineage recovery) the first time. Lol your post made me want to check it out. Omg bud i almost forgot and this is crucial. Aosp ROMs like emotion take a long long time to boot the first time(damn near 15 mins) ! The last thing you want to do is mistake this for a bootloop
Click to expand...
Click to collapse
Ouch ! I kinda failed to take into account the very real possibility the ROM you wished to flash might not be on your device and you may have no means to get it there.....in which case flash twrp then you need (if you don't want relock bootloader) to flash a system only image . vague I know I'm thinking .....bottom line is whatever you flash cannot contain aboot image or you will relock boot loader. If on 6.0.1 boot loader there is a safeupgrade to the most recent firmware that won't relock if on 5.1.1 (bpa1 ) idk if there is one . I think there is . in fact I'm sure there is hsbrad made Odin flashable IMG for all Verizon note 4 firmware broth dev and retail . look under his profile on XDA should link you to it
ziggsta2 said:
Do you know what recovery this is? It has the lineage symbol! I cant find a picture of it any where if someone knew what recovery it was maybe then I could research info from the name
Click to expand...
Click to collapse
That is the lineage os recovery it comes in every build, you must have hit update recovery in the developer options of the settings menu. You just need to reflash twrp like you did when you unlocked your bootloader.
weard1212 said:
That is the lineage os recovery it comes in every build, you must have hit update recovery in the developer options of the settings menu. You just need to reflash twrp like you did when you unlocked your bootloader.
Click to expand...
Click to collapse
Yeah ty I went ahead and tried last night cause I was bored ....meh lack luster . oh and I did it intentionally and just restored recovery with flashify and I just realized this probably wasn't directed at me but yep lineage
So, was thinking to give dp5 a try since I have a OnePlus 6 as a main phone now, and get the pixel with a fresh Android 9 flavour before putting it up for sale.
But, don't know why I thought it's a good idea to lock the bootloader first then get the OTA.
But since I was running nitrogenOS, after locking the bootloader, the phone won't boot, giving the "No valid os to boot" screen.
Stock recovery is inexistent as well, can only boot to fastboot but I've tried to boot/flash with no lock, it tells me it cannot be done on a locked state.
If anyone can help me saving the phone, I'd be really thankful, can even pay for a couple of beers too.
The phone was bought 2nd hand and I can't RMA it. Please let me know if there's anything else I could try to bring it back to life. Thank you everyone.
Sent from my ONEPLUS A6003 using Tapatalk
Blue305 said:
So, was thinking to give dp5 a try since I have a OnePlus 6 as a main phone now, and get the pixel with a fresh Android 9 flavour before putting it up for sale.
But, don't know why I thought it's a good idea to lock the bootloader first then get the OTA.
But since I was running nitrogenOS, after locking the bootloader, the phone won't boot, giving the "No valid os to boot" screen.
Stock recovery is inexistent as well, can only boot to fastboot but I've tried to boot/flash with no lock, it tells me it cannot be done on a locked state.
If anyone can help me saving the phone, I'd be really thankful, can even pay for a couple of beers too.
The phone was bought 2nd hand and I can't RMA it. Please let me know if there's anything else I could try to bring it back to life. Thank you everyone.
Click to expand...
Click to collapse
You should have returned to full stock before locking the bootloader my friend. You should be able to unlock it again, and then fastboot the factory image with the flash-all.bat script to get you up and running.
Badger50 said:
You should have returned to full stock before locking the bootloader my friend. You should be able to unlock it again, and then fastboot the factory image with the flash-all.bat script to get you up and running.
Click to expand...
Click to collapse
Agreed, as long as the OP did not also uncheck the oem switch...
Please, anyone reading this... Do Not RELOCK your boot loader unless you are 100% back to stock. Again, not stock... No RELOCK!!
To the OP, please report back how you make out!
CyberpodS2 said:
Agreed, as long as the OP did not also uncheck the oem switch...
Please, anyone reading this... Do Not RELOCK your boot loader unless you are 100% back to stock. Again, not stock... No RELOCK!!
To the OP, please report back how you make out!
Click to expand...
Click to collapse
Well bruh, if he did uncheck OEM unlocking, it's....
"Turn out the lights the party's over" You are now the proud owner of a fancy paperweight! ?
I didn't messed up with the OEM unlock from developer options, but I can't unlock the bootloader from fastboot unfortunately.. tried the flash.all as well, but I'd doesn't do much , keeps telling me that the phone is in a lock state...
Sent from my ONEPLUS A6003 using Tapatalk
Blue305 said:
I didn't messed up with the OEM unlock from developer options, but I can't unlock the bootloader from fastboot unfortunately.. tried the flash.all as well, but I'd doesn't do much , keeps telling me that the phone is in a lock state...
Click to expand...
Click to collapse
Which command did you use when you locked it?
You may want to look into Deuces recovery script as well to get you out of this pickle.
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Badger50 said:
Which command did you use when you locked it?
You may want to look into Deuces recovery script as well to get you out of this pickle.
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Click to expand...
Click to collapse
Thank you, but unfortunately I've ran the script but nothing happened, still cannot get it unlocked or boot to recovery
Sent from my ONEPLUS A6003 using Tapatalk
Blue305 said:
Thank you, but unfortunately I've ran the script but nothing happened, still cannot get it unlocked or boot to recovery
Click to expand...
Click to collapse
Then possibly try different cables and USB ports. Again, which command(s) did you use to lock the bootloader???
Sometimes you have to run Deuces a few times to get it too work.
Badger50 said:
Then possibly try different cables and USB ports. Again, which command(s) did you use to lock the bootloader???
Sometimes you have to run Deuces a few times to get it too work.
Click to expand...
Click to collapse
I'll try different cables then.
I've used fastboot flashing lock, and now is locked, and can't boot to recovery or start os, just boot to bootloader.n
Sent from my ONEPLUS A6003 using Tapatalk
in fastboot, do:
fastboot flashing unlock
then
fastboot flashing unlock_critical
Blue305 said:
So, was thinking to give dp5 a try since I have a OnePlus 6 as a main phone now, and get the pixel with a fresh Android 9 flavour before putting it up for sale.
But, don't know why I thought it's a good idea to lock the bootloader first then get the OTA.
But since I was running nitrogenOS, after locking the bootloader, the phone won't boot, giving the "No valid os to boot" screen.
Stock recovery is inexistent as well, can only boot to fastboot but I've tried to boot/flash with no lock, it tells me it cannot be done on a locked state.
If anyone can help me saving the phone, I'd be really thankful, can even pay for a couple of beers too.
The phone was bought 2nd hand and I can't RMA it. Please let me know if there's anything else I could try to bring it back to life. Thank you everyone.
Click to expand...
Click to collapse
You can give a try for RMA... they sometimes accept RMA for 2nd hand devices as well
ram4ufriends said:
You can give a try for RMA... they sometimes accept RMA for 2nd hand devices as well
Click to expand...
Click to collapse
Thanks, I didnt know that. Is there a specific number I need to call? Thanks again.
Sent from my ONEPLUS A6003 using Tapatalk
uicnren said:
in fastboot, do:
fastboot flashing unlock
then
fastboot flashing unlock_critical
Click to expand...
Click to collapse
I've tried that but it doesnt allow me to do it
Sent from my ONEPLUS A6003 using Tapatalk
Blue305 said:
I've tried that but it doesnt allow me to do it
Sent from my ONEPLUS A6003 using Tapatalk
Click to expand...
Click to collapse
What specifically is the error you receive?
If you want help, you should provide as much detail as possible.
Have you tried recovery and sideloading a full OTA image? I know you said 'stock recovery is inexistent' what does that mean, you get the 'no command' screen with red triangle?
uicnren said:
What specifically is the error you receive?
If you want help, you should provide as much detail as possible.
Have you tried recovery and sideloading a full OTA image? I know you said 'stock recovery is inexistent' what does that mean, you get the 'no command' screen with red triangle?
Click to expand...
Click to collapse
I'm sorry, you're right, I should have been more specific.
The error looks like this:
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.001s
Also, when I try to boot in the recovery, Nothing happens, the device reboots, Showing me the normal screen "Can't find valid operating system, The device will not start".
I can only get to fastboot, I've tried "adb devices" while in fastboot but nothing is detected.
Thank you for the help so far, if there's anythiing else I could try, please tell me.
This is what it looks like.
View attachment 4562979
{
"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"
}
Sent from my ONEPLUS A6003 using Tapatalk
Blue305 said:
I'm sorry, you're right, I should have been more specific.
The error looks like this:
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.001s
Also, when I try to boot in the recovery, Nothing happens, the device reboots, Showing me the normal screen "Can't find valid operating system, The device will not start".
I can only get to fastboot, I've tried "adb devices" while in fastboot but nothing is detected.
Thank you for the help so far, if there's anythiing else I could try, please tell me.
Click to expand...
Click to collapse
adb commands will never work in bootloader.
try: fastboot devices
if the unlocking commands are denied, then it seems like OEM unlocking has defaulted to locked without there being a valid OS and/or no recovery.
if that is the case and you cannot unlock the bootloader, you wont be able to install an OS.
Also how are you trying to get to recovery, I will assume from the hardware buttons while in fastboot?
for fun (not that it should make a difference) try: fastboot reboot recovery
Also out of curiosity, what version of fastboot are you currently using?
uicnren said:
adb commands will never work in bootloader.
try: fastboot devices
if the unlocking commands are denied, then it seems like OEM unlocking has defaulted to locked without there being a valid OS and/or no recovery.
if that is the case and you cannot unlock the bootloader, you wont be able to install an OS.
Also how are you trying to get to recovery, I will assume from the hardware buttons while in fastboot?
for fun (not that it should make a difference) try: fastboot reboot recovery
Click to expand...
Click to collapse
YEs, the unlocking comands are denied.
I used the volume keys to try and get to recovery, but no luck..
That command doesn't work either.
I really don't know what else to do, im quite desperate
Blue305 said:
YEs, the unlocking comands are denied.
I used the volume keys to try and get to recovery, but no luck..
That command doesn't work either.
I really don't know what else to do, im quite desperate
Click to expand...
Click to collapse
Sorry, I added some questions to previous reply, what version of fastboot are you using?
try: fastboot --version
uicnren said:
Sorry, I added some questions to previous reply, what version of fastboot are you using?
try: fastboot --version
Click to expand...
Click to collapse
it's this one:
fastboot version 0.0.1-4500957
Installed as G:\platform-tools\fastboot.exe
Hi
"Can't find valid operating system. The device will not start."
Then shows the visit g.co/ABH link.
I am not even able to boot into recovery. When selecting recovery from fastboot mode it just goes right to the same "Can't find valid operating system..." screen.
Device State: Locked
Developer Mode : Not Enabled and not possible to do now
PLease help me. As i am from Nepal , there is nothing i can't claim for warranty.
{
"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"
}
senbros said:
Hi
"Can't find valid operating system. The device will not start."
Then shows the visit g.co/ABH link.
I am not even able to boot into recovery. When selecting recovery from fastboot mode it just goes right to the same "Can't find valid operating system..." screen.
Device State: Locked
Click to expand...
Click to collapse
Sorry, but with no working recovery and a locked bootloader you are dead in the water. There is nothing that can be done.
Are you able to unlock your bootloader? Might be able to download the factory image do it that way. Fastboot flashing unlock it something. Then run the flash all.bat from the factory image once you download it and unzipped it.
mammothjojo88 said:
Are you able to unlock your bootloader? Might be able to download the factory image do it that way. Fastboot flashing unlock it something. Then run the flash all.bat from the factory image once you download it and unzipped it.
Click to expand...
Click to collapse
I tried nothing works to unlock bootloader.. Still looking for solution..
Thank you for your time
Can't find valid operating system
senbros said:
Hi
"Can't find valid operating system. The device will not start."
Then shows the visit g.co/ABH link.
I am not even able to boot into recovery. When selecting recovery from fastboot mode it just goes right to the same "Can't find valid operating system..." screen.
Device State: Locked
Developer Mode : Not Enabled and not possible to do now
PLease help me. As i am from Nepal , there is nothing i can't claim for warranty.
Click to expand...
Click to collapse
Hi Mate,
I had the same thing happen Last Friday morning. I was just applying an OTA update, then when phone rebooted I got the same message on my Pixel 3 ( 2 weeks old ). I spent many hours over the weekend trying to figure out how to get a factory image on it. However without unlocking the bootloader ( which is not possible ), also having the recovery also corrupted, there is nothing we can do, except send it to a friend or someone we know and trust to get the phone repaired or if its under warranty still, possibly replaced by google. Sorry to be the giver of bad news. These are now expensive paper weights. It seems it becoming more common.
This is happening for more pixels. Google is must fix it remotely or pixel 4 might fail on landing.
issue resolved by google support
Hi,
i am having same issue with my pixel 3 last week, so i called Indian google service center ( 1800-419-0655 ) they pick up my phone from my place and resolve the issue.
so i will suggest you to visit/call google support team so they will resolve you issue.
---------- Post added at 06:03 AM ---------- Previous post was at 05:59 AM ----------
slysurfer said:
Hi Mate,
I had the same thing happen Last Friday morning. I was just applying an OTA update, then when phone rebooted I got the same message on my Pixel 3 ( 2 weeks old ). I spent many hours over the weekend trying to figure out how to get a factory image on it. However without unlocking the bootloader ( which is not possible ), also having the recovery also corrupted, there is nothing we can do, except send it to a friend or someone we know and trust to get the phone repaired or if its under warranty still, possibly replaced by google. Sorry to be the giver of bad news. These are now expensive paper weights. It seems it becoming more common.
Click to expand...
Click to collapse
hi there,
i had same issue last week, so i called google support. they pick up my pixel from my place and resolve the issue.
so please do the same contact google support. they will help you.
Problem in Pixel 3
They gave you a replacement or repaired the original device?? And how many days B2X took from pickup to delivering it back??
tailorhardik94 said:
Hi,
i am having same issue with my pixel 3 last week, so i called Indian google service center ( 1800-419-0655 ) they pick up my phone from my place and resolve the issue.
so i will suggest you to visit/call google support team so they will resolve you issue.
---------- Post added at 06:03 AM ---------- Previous post was at 05:59 AM ----------
hi there,
i had same issue last week, so i called google support. they pick up my pixel from my place and resolve the issue.
so please do the same contact google support. they will help you.
Click to expand...
Click to collapse
Not sure if anyone still needs help with this, but I just ran into this issue on my Pixel 4 XL and I held down the volume down button and power button to reboot into fastboot. From there you can connect to a PC and flash images or unlock/lock bootloader, etc.
From there I was able to use the flash.android.com site and flash the latest OTA to my phone and now I'm back up and running.
Hope this helps someone down the road.
bradwatson said:
Not sure if anyone still needs help with this, but I just ran into this issue on my Pixel 4 XL and I held down the volume down button and power button to reboot into fastboot. From there you can connect to a PC and flash images or unlock/lock bootloader, etc.
From there I was able to use the flash.android.com site and flash the latest OTA to my phone and now I'm back up and running.
Hope this helps someone down the road.
Click to expand...
Click to collapse
You can't do anything if you come across this problem whilst your bootloader is locked. I had a Pixel 3, applied ota via recovery and I got that error message. Couldn't do anything, flash factory image etc due to locked bootloader and recovery being corrupted.
Quite simply if it's under warranty, contact google.
kartikb said:
You can't do anything if you come across this problem whilst your bootloader is locked. I had a Pixel 3, applied ota via recovery and I got that error message. Couldn't do anything, flash factory image etc due to locked bootloader and recovery being corrupted.
Quite simply if it's under warranty, contact google.
Click to expand...
Click to collapse
Not entirely true. If OEM unlocking was previously enabled, then despite your phone being locked, it will still accept the unlocking command. Just happened to me. I am trading in my phone. I uninstalled Magisk, booted to bootloader, locked the bootloader and got the dreaded "Can't find valid operating system" alert. I thought it was toast since no response to adb at that point. The screen looked like the bootloader screen but with less text. Finally used vol down/pwr to get to bootloader, re-unlocked and re-flashed the OS. Back in business, at least getting my full trade-in price!
flash.android.com really helped, thank you!
device locked (locking the device is what caused this for me) and windows saying it doesnt recognize the device when I plugged it in while in the bootloader. For some reason flash.android.com recognized the device, not sure why
same thing happened with right now
i was trying to lock bootloader on custom rom (nonsense,i know)
so,phone wasnt being recognized by pc,and somehow android flash tool recognized and i clicked flashing and it needed bootloader to be unlocked so it did,and phone booted back on custom rom.
nice
yearn2burn said:
Not entirely true. If OEM unlocking was previously enabled, then despite your phone being locked, it will still accept the unlocking command. Just happened to me. I am trading in my phone. I uninstalled Magisk, booted to bootloader, locked the bootloader and got the dreaded "Can't find valid operating system" alert. I thought it was toast since no response to adb at that point. The screen looked like the bootloader screen but with less text. Finally used vol down/pwr to get to bootloader, re-unlocked and re-flashed the OS. Back in business, at least getting my full trade-in price!
Click to expand...
Click to collapse
Just happened to my Pixel 4a5G trade-in for Pixel 7. Completely uninstalled magisk and then tried to re-lock the bootloader. Bootloader locked and got the no operating system error. Called google and they said send it in as and I will get full amount. The dude did not sound very reassuring. I luckyly stumbled on this thread. tried to unlock the bootloader but it failed. I reset my computer and tried it again and it worked. Phone booted up. I took and OTA and tried to re-lock the bootloader and SUCCESS. This phone never had an OTA so I believe the one slot was empty, maybe that is why this happened. Moral to the story, make sure both slots has an OS on them.
Thanks
BB
bradwatson said:
Not sure if anyone still needs help with this, but I just ran into this issue on my Pixel 4 XL and I held down the volume down button and power button to reboot into fastboot. From there you can connect to a PC and flash images or unlock/lock bootloader, etc.
From there I was able to use the flash.android.com site and flash the latest OTA to my phone and now I'm back up and running.
Hope this helps someone down the road.
Click to expand...
Click to collapse
Thanks! This was exactly what I needed. I didn't realize you could get into fastboot with hardware controls and I was trying through adb
I'm an idiot and did this same thing.
bradwatson said:
Not sure if anyone still needs help with this, but I just ran into this issue on my Pixel 4 XL and I held down the volume down button and power button to reboot into fastboot. From there you can connect to a PC and flash images or unlock/lock bootloader, etc.
From there I was able to use the flash.android.com site and flash the latest OTA to my phone and now I'm back up and running.
Hope this helps someone down the road.
Click to expand...
Click to collapse
Just wanted to say thanks - had a panic moment until I read this and realized I could do that. Pixel 4 wiped and ready to go back. Thanks again, years later.
I got an error at the begining of the flash, something like "too many files opened" and stop flashing. I aborted the process and now my f3 is dead, black screen, not recovery or fastboot. Windows desn't detects anything. Some help would be appreciated.
I am afraid you must put your F3 in EDL mode(Google it) basically it involves shorting of two pins in the phone to activate the EDL mode, you need to remove the back panel for that. After you put your phone in edl mode it will be recognised by your pc and you can restore it from there
{
"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"
}
What have you tried to flash? Using what?
Once you put the device in EDL mode you can use a fastboot rom to reflash the device, I have done this to Mi A1 which was in similar situation as described above.
Once you put the device in EDL mode you can use a fastboot rom to reflash the device, I have done this to Mi A1 which was in similar situation as described above
hexisg said:
What have you tried to flash? Using what?
Click to expand...
Click to collapse
I was flashing last xiaomi.eu by fastboot
Skynet75 said:
Once you put the device in EDL mode you can use a fastboot rom to reflash the device, I have done this to Mi A1 which was in similar situation as described above
Click to expand...
Click to collapse
Thx a lot, I've been reading about edl connection but didn't find this info. My doubt now is to do this and lost my waranty or send it to SAT and asume the risk to be charged.
muil said:
Thx a lot, I've been reading about edl connection but didn't find this info. My doubt now is to do this and lost my waranty or send it to SAT and asume the risk to be charged.
Click to expand...
Click to collapse
If it's under warranty give to the store they may repair it for free(possibly change the whole motherboard), if it's not under warranty or if they charge you with some insane amount try to go to a third party repair shop ask them to open the back panel and ask them to put it in edl mode and reflash it(if they don't know how to do it, just get the phone opened and do the other steps yourself). I am asking you to visit a third party store to open up the phone because the back panel is glass (glass is glass and glass breaks if not removed properly)
muil said:
Thx a lot, I've been reading about edl connection but didn't find this info. My doubt now is to do this and lost my waranty or send it to SAT and asume the risk to be charged.
Click to expand...
Click to collapse
In future don't flash xiaomi.eu with fastboot...
I remember reading that it overwrites critical partitions during flashing , there's a high likelihood to fk stuff up with that , use twrp instead
No twrp for android 12 yet, so...
Same thing happened to me last month. But i ended up fixing it. Its a pretty tricky process
mucha.k1994 said:
No twrp for android 12 yet, so...
Click to expand...
Click to collapse
Don't flash ...
TormentedHeart said:
Same thing happened to me last month. But i ended up fixing it. Its a pretty tricky process
Click to expand...
Click to collapse
Did you jumper the EDL test points? Did you need special tools to remove the back cover?
Rstment ^m^ said:
In future don't flash xiaomi.eu with fastboot...
I remember reading that it overwrites critical partitions during flashing , there's a high likelihood to fk stuff up with that , use twrp instead
Click to expand...
Click to collapse
Well...I flashed xiaomi.eu on this phone a cuple of times by fastboot before twrp was ready and everything went ok. The difference this time is my PC was overloaded with other tasks and the error "many files opened" I got, make me think this could be de cause.
Skynet75 said:
If it's under warranty give to the store they may repair it for free(possibly change the whole motherboard), if it's not under warranty or if they charge you with some insane amount try to go to a third party repair shop ask them to open the back panel and ask them to put it in edl mode and reflash it(if they don't know how to do it, just get the phone opened and do the other steps yourself). I am asking you to visit a third party store to open up the phone because the back panel is glass (glass is glass and glass breaks if not removed properly)
Click to expand...
Click to collapse
Finally I will send it to Xiaomi service. It looks easy the EDL method but as you say I would probably break the back cover. I'm crossing fingers to not be charged.
Hello I think I can help them I had the same problem
I had the Android 12 DP 5 Flashed by Munchy's Youtube channel
I had them running well until the day before yesterday but when I got up in the morning it told me that update is installed I should reboot
wtf what for update it sucked the update for the Pixel 5 and installed it I thought
ok reboot via ADB in fastboot boot ......and EDL Mode ....
then I researched and found this nice gentleman ..... I got in touch via whatsapp and the next day he did it.... it cost me 35 Euros but I think it's better than buying a new one
I give his data if someone has a problem I would try it here
https://www.unbrickmi(.)com/
I hope I could help someone else
noobstyle1337 said:
Hello I think I can help them I had the same problem
I had the Android 12 DP 5 Flashed by Munchy's Youtube channel
I had them running well until the day before yesterday but when I got up in the morning it told me that update is installed I should reboot
wtf what for update it sucked the update for the Pixel 5 and installed it I thought
ok reboot via ADB in fastboot boot ......and EDL Mode ....
then I researched and found this nice gentleman ..... I got in touch via whatsapp and the next day he did it.... it cost me 35 Euros but I think it's better than buying a new one
I give his data if someone has a problem I would try it here
https://www.unbrickmi.com/
whatsapp +91 76449 33731
I hope I could help someone else
Click to expand...
Click to collapse
But what did he do or what did you do by his guidance to fix it?
muil said:
But what did he do or what did you do by his guidance to fix it?
Click to expand...
Click to collapse
@ABHIROOP90
Download telegram and message this guy .
He does it for maybe 7-10$ ...
That's what he told me at least , some users say he's legit but you'll have to pay and see for yourself.
Don't know if you can't do edl by yourself as some say you need edl authorised account
That's if you want edl... But if you open the device you'll have troubles getting warranty 100% if the edl fails for whatever reason.
I'd go and give it to warranty myself...
muil said:
But what did he do or what did you do by his guidance to fix it?
Click to expand...
Click to collapse
The gentleman has an Xiaomi auth account and can do the EDL ..... I think not everyone has such an account
Rstment ^m^ said:
@ABHIROOP90
Download telegram and message this guy .
He does it for maybe 7-10$ ...
That's what he told me at least , some users say he's legit but you'll have to pay and see for yourself.
Don't know if you can't do edl by yourself as some say you need edl authorised account
That's if you want edl... But if you open the device you'll have troubles getting warranty 100% if the edl fails for whatever reason.
I'd go and give it to warranty myself...
Click to expand...
Click to collapse
I didn't have to open my Poco If you hang in EDL mode then you can also press 20 sec power then the Edl mode restarts and then you can flash
I recently got a used Samsung Galaxy S9 (G960F/DS) with a broken screen (shattered glass and a black spot on the LCD). I was preparing to replace its screen, however, I'm currently not getting the device to boot.
When connected to power, the phone turns on automatically and ends up stuck on the "Samsung Galaxy S9 Secured by Knox Powered by android" screen. When disconnecting power, it turns off after 1-2 seconds.
By pressing power + bixby + volume down, the device enters download mode. When trying to flash stock firmware (BL + AP + CP + CSC) downloaded through Frija (SM-G960F_2_20211021052205_oql3mv17br_fac) the process fails and the phone shows "An error has occured while updating the device software. Use the Emergency recovery function in the Smart Switch PC software". However, I was able to flash the four parts separately by rebooting in between.
This doesn't change anything about the booting problem though. Holding power + bixby + volume up doesn't boot recovery either.
I'd be happy to hear any suggestions. If any more information is required, I'm happy to send you everything I know.
Jogius said:
I recently got a used Samsung Galaxy S9 (G960F/DS) with a broken screen (shattered glass and a black spot on the LCD). I was preparing to replace its screen, however, I'm currently not getting the device to boot.
When connected to power, the phone turns on automatically and ends up stuck on the "Samsung Galaxy S9 Secured by Knox Powered by android" screen. When disconnecting power, it turns off after 1-2 seconds.
By pressing power + bixby + volume down, the device enters download mode. When trying to flash stock firmware (BL + AP + CP + CSC) downloaded through Frija (SM-G960F_2_20211021052205_oql3mv17br_fac) the process fails and the phone shows "An error has occured while updating the device software. Use the Emergency recovery function in the Smart Switch PC software". However, I was able to flash the four parts separately by rebooting in between.
This doesn't change anything about the booting problem though. Holding power + bixby + volume up doesn't boot recovery either.
I'd be happy to hear any suggestions. If any more information is required, I'm happy to send you everything I know.
Click to expand...
Click to collapse
May I'm wrong, but the first impression seems that not only the screen is defective, keep in mind that a device with that broken screen had to receive a severe shock (or various of them), to this can happen, in the incident -of course- other hardware could be damaged.
But taking apart the hardware thing, did you try to format data through stock recovery? Or could you see in the recovery screen (if something is visible) the current build number, so you can flash the right firmware instead of a lower version or the first you found out there?
SubwayChamp said:
May I'm wrong, but the first impression seems that not only the screen is defective, keep in mind that a device with that broken screen had to receive a severe shock (or various of them), to this can happen, in the incident -of course- other hardware could be damaged.
But taking apart the hardware thing, did you try to format data through stock recovery? Or could you see in the recovery screen (if something is visible) the current build number, so you can flash the right firmware instead of a lower version or the first you found out there?
Click to expand...
Click to collapse
I feel like the phone might have another hardware defect, but I'd still like to try my best to fix it.
Unfortunately, the previous owner already tinkered with the device aswell, when I received it, it was not booting stock recovery. However, I only tried flashing the newest update of the firmware - was that the wrong approach? How (and where) can I find a lower version without knowing the exact version details?
Thank you for the input!
Jogius said:
I feel like the phone might have another hardware defect, but I'd still like to try my best to fix it.
Unfortunately, the previous owner already tinkered with the device aswell, when I received it, it was not booting stock recovery. However, I only tried flashing the newest update of the firmware - was that the wrong approach? How (and where) can I find a lower version without knowing the exact version details?
Thank you for the input!
Click to expand...
Click to collapse
Not sure if as the screen is broken you can see something through it, in the recovery screen you'll find the build number version for your device.
Flashing the latest update is always the best bet to not fail. Flashing lower version is not a good idea. You also have to check what is the input in the download screen, if something like KG prenormal warning is there, then you can't flash something in this state.
Also, as the previous owner seems to be not so careful with this device, it is probable that the latest Google account is still there that will trigger the FRP protection.
SubwayChamp said:
Not sure if as the screen is broken you can see something through it, in the recovery screen you'll find the build number version for your device.
Flashing the latest update is always the best bet to not fail. Flashing lower version is not a good idea. You also have to check what is the input in the download screen, if something like KG prenormal warning is there, then you can't flash something in this state.
Also, as the previous owner seems to be not so careful with this device, it is probable that the latest Google account is still there that will trigger the FRP protection.
Click to expand...
Click to collapse
I attached an image of what information download mode has. The second image shows what happens when I try to boot recovery (or anything except download mode for that matter).
You are right that the FRP ist still turned on. Does that mean there is no way to go around this?
{
"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"
}
Jogius said:
I attached an image of what information download mode has. The second image shows what happens when I try to boot recovery (or anything except download mode for that matter).
You are right that the FRP ist still turned on. Does that mean there is no way to go around this?
View attachment 5478243View attachment 5478245
Click to expand...
Click to collapse
Yes, I suspected that, FRP is active, try to find the guy that sold to you this device, and ask him to log out from his Google account. Also the FRP trigger can be a false positive in the instance that you can enable OEM unlock toggle (what it is not actually enabled), and if Odin allow you to flash something on it and from there you could set it up your device normally.
SubwayChamp said:
Yes, I suspected that, FRP is active, try to find the guy that sold to you this device, and ask him to log out from his Google account. Also the FRP trigger can be a false positive in the instance that you can enable OEM unlock toggle (what it is not actually enabled), and if Odin allow you to flash something on it and from there you could set it up your device normally.
Click to expand...
Click to collapse
I'll try to get in touch with the seller, thank you! However, does FRP change anything about the device not being able to boot at all? Do you have any tips for me how to troubleshoot the fact that not even recovery mode is working?
Jogius said:
I'll try to get in touch with the seller, thank you! However, does FRP change anything about the device not being able to boot at all? Do you have any tips for me how to troubleshoot the fact that not even recovery mode is working?
Click to expand...
Click to collapse
frp still allows you to boot, it just will ask for your google account when setting the phone up
Jogius said:
I'll try to get in touch with the seller, thank you! However, does FRP change anything about the device not being able to boot at all? Do you have any tips for me how to troubleshoot the fact that not even recovery mode is working?
Click to expand...
Click to collapse
FRP works mainly in two ways, when you didn't enable OEM unlock and of course USB debugging then FRP detects an unofficial attempt to inject some custom binary rejecting to boot to system, (What would be the purpose of FRP if you could flash a custom binary, rooting it and then pulling all the data you want?) sometimes this is bypassed by formatting data either booting to recovery (that you say you can't do at this time) or flashing the CSC different from the CSC_HOME, this will wipe/format all your data. And the second instance where FRP can be trigger is when the device was black listed (plus the Samsung account if the last owner didn't log out). The first thing you have to do when buying a Samsung device is logging into the two accounts, then formatting data, and from there you can do what you want.