Phone flashed with unauthorized software. - General Questions and Answers

Hello everybody! I just joined and am basically a complete noob at this, so thanks for the help in advance. I bought a Samsung Galaxy S10 about a year and a half ago off of Amazon to replace my S9. However, whenever I booted it up, it would give me this message; "Security Error: This phone has been flashed with unauthorized software and is locked". I didn't return it at the time like I should have and now I'm stuck with it. I've already tried flashing it with Odin and using the latest firmware that I got off Frija, and hard resetting as well, and still the same damn message pops up whenever I turn it on. I'm pretty much at a loss here, I don't know what could be tripping the security error at this point. Any advice would be greatly appreciated, thanks in advance.

SteelSpoon00 said:
Hello everybody! I just joined and am basically a complete noob at this, so thanks for the help in advance. I bought a Samsung Galaxy S10 about a year and a half ago off of Amazon to replace my S9. However, whenever I booted it up, it would give me this message; "Security Error: This phone has been flashed with unauthorized software and is locked". I didn't return it at the time like I should have and now I'm stuck with it. I've already tried flashing it with Odin and using the latest firmware that I got off Frija, and hard resetting as well, and still the same damn message pops up whenever I turn it on. I'm pretty much at a loss here, I don't know what could be tripping the security error at this point. Any advice would be greatly appreciated, thanks in advance.
Click to expand...
Click to collapse
When you flashed the firmware, did Odin give you any errors?
Also, what is the specific model number of the device?

Droidriven said:
When you flashed the firmware, did Odin give you any errors?
Also, what is the specific model number of the device?
Click to expand...
Click to collapse
The specific model is GM973U and Odin gave me the green PASS message upon completion

SteelSpoon00 said:
The specific model is GM973U and Odin gave me the green PASS message upon completion
Click to expand...
Click to collapse
That isn't normal by any means. Are you sure that USB debugging was enabled in settings and are you sure you did everything correct?

Droidriven said:
That isn't normal by any means. Are you sure that USB debugging was enabled in settings and are you sure you did everything correct?
Click to expand...
Click to collapse
I did turn on developer mode and allow USB debugging, though I didn't turn off the OEM option because I didn't see it, if that matters. I followed the instructions online to the letter and used Frija and Odin, I'm not sure at all what could have went wrong in the whole process. I was thinking of trying to use ADB to disable Knox or anything else that could be getting in the way, but I'm still not really sure how that works.

Try flashing an older rom, like the build that the phone came with.

Please i beg you, i have exactly the same problem, with a samsung sm-t380, after telling my boss i know how to flash a phone, now the phone has been with me for up to 3 months, still showing blue screen with (Security Error: This phone has been flashed with unauthorized software & locked)...
Please everybody or anybody help me solve this. I beg you, thanks.

Related

[Completed] Q: Galaxy A8, "kernel is not seandroid enforcing" "custom binary blocked by frp" help

Q: Galaxy A8, "kernel is not seandroid enforcing" "custom binary blocked by frp" help
Hi,
This is Ejaz from Afghanistan. Yeah! from Afghanistan.
I bought a new Galaxy A8 and I tried to root it. I used space x kernel and Odin to root my phone. It didn't work. Some thread in XDA said, after rooting your phone, install Supersu from playstore. I did it and then tried to update binary files. It restarted my phone and this freaky android icon showed up with something moving in its belly. And then this message showed up, "kernel is not seandroid enforcing" "custom binary blocked by frp". Then the phone turned off. Now the same message shows up, when I turn on the phone and then it goes back off. I wiped the phone and the cache partition, still no good result.
Someone in the web said, download the Stock firmware and reinstall it using Odin. I am downloading it, and it takes hours. Yeah, I said I am from Afghanistan, that's why it takes hours. The internet is slow.
So anyone with good heart, please save my life. Coz I spent 600$ to buy this phone.
Thanks in advance.
ejazi said:
Hi,
This is Ejaz from Afghanistan. Yeah! from Afghanistan.
I bought a new Galaxy A8 and I tried to root it. I used space x kernel and Odin to root my phone. It didn't work. Some thread in XDA said, after rooting your phone, install Supersu from playstore. I did it and then tried to update binary files. It restarted my phone and this freaky android icon showed up with something moving in its belly. And then this message showed up, "kernel is not seandroid enforcing" "custom binary blocked by frp". Then the phone turned off. Now the same message shows up, when I turn on the phone and then it goes back off. I wiped the phone and the cache partition, still no good result.
Someone in the web said, download the Stock firmware and reinstall it using Odin. I am downloading it, and it takes hours. Yeah, I said I am from Afghanistan, that's why it takes hours. The internet is slow.
So anyone with good heard, please save my life. Coz I spent 600$ to buy this phone.
Thanks in advance.
Click to expand...
Click to collapse
Before rooting your device you have to go into your settings/about device and tap the build number until developer options is unlocked. The go into developer options and click the OEM UNLOCKING toggle. After that then proceed to root your device. You did everything correct but not having OEM unlocking ticked it stopping the phone from booting since it's not a stock kernal. What your gonna need to do now is Odin back to complete stock uprooted and then do what I said above then you will be able to proceed to root your device as you did before.
SICKMADE said:
Before rooting your device you have to go into your settings/about device and tap the build number until developer options is unlocked. The go into developer options and click the OEM UNLOCKING toggle. After that then proceed to root your device. You did everything correct but not having OEM unlocking ticked it stopping the phone from booting since it's not a stock kernal. What your gonna need to do now is Odin back to complete stock uprooted and then do what I said above then you will be able to proceed to root your device as you did before.
Click to expand...
Click to collapse
Thanks God, my phone is alive. I downloaded the stock firmware and I flashed it. Rooted my phone again. And did whatever you said. But now the SU Binary wouldn't update. PLease help. By the way, I am running 5.1.1.
Thanks for the pro steps on the OEM Unlocking toggle. :good: :good: :good: wish you were close, I would buy you a pizza.
ejazi said:
Thanks God, my phone is alive. I downloaded the stock firmware and I flashed it. Rooted my phone again. And did whatever you said. But now the SU Binary wouldn't update. PLease help. By the way, I am running 5.1.1.
Thanks for the pro steps on the OEM Unlocking toggle. :good: :good: :good: wish you were close, I would buy you a pizza.
Click to expand...
Click to collapse
So your opening au and it's saying it needs to update binaries? Instead of choosing custom recovery method use stock recovery method when it pops up and see if that works

Help, I can't get past the WIFI screen and I can't flash a new rom on this phone

Hello guys,
I need your assistance with this issue. I got this Boost Mobile LG LS770/Stylo phone from eBay and when I wiped/restored it to clean everything from the other person, the phone still wants me to enter the information from the previous person before I can use it. Of course that is not an option. I tried.
Also, since I am unable to get to the Android OS, I cannot put it in debug mode either. So I tried a few things to no avail. This is what I have done so far:
Put the phone in ADB mode via recovery - Done, but I am unable to sideload anything. I get this error.. "* cannot read 'sideload' *"
Put the phone in download mode "Fireware Update" - Done, and I can see my port as COM3, but when I run the next step, I get a message that says... "Hello, my name is LAF....." and nothing happens.
I tried using the LG one click root tool, but that requires the phone to be in USB debug mode and like I said before, I am unable to even get to the welcome screen in android. I can't get past wifi setup in reality, I can't even skip it.
I have been at this all day today. Can you please help me out? I really appreciate any help you can provide.
Thanks
You need a USB-OTG cable and some files. If you have a USB-OTG i'll reply with what you'll need to do. Also, have you contacted the eBay member letting them no they FRP screwed you and you basically own a brick now?
revulv said:
You need a USB-OTG cable and some files. If you have a USB-OTG i'll reply with what you'll need to do. Also, have you contacted the eBay member letting them no they FRP screwed you and you basically own a brick now?
Click to expand...
Click to collapse
I have OTG cable... Can you help me out??
revulv said:
You need a USB-OTG cable and some files. If you have a USB-OTG i'll reply with what you'll need to do. Also, have you contacted the eBay member letting them no they FRP screwed you and you basically own a brick now?
Click to expand...
Click to collapse
Thank you for your response. I have one. Please go ahead with the steps.
revulv said:
You need a USB-OTG cable and some files. If you have a USB-OTG i'll reply with what you'll need to do. Also, have you contacted the eBay member letting them no they FRP screwed you and you basically own a brick now?
Click to expand...
Click to collapse
Also, I forgot to respond to your question. I did contact the eBay guy or lady that sold it to me, but since I'm the one that did the wipe, they are not taking responsibility and I get it. I just would like to be able to use the phone and not waste the money I spent on it. I really appreciate any help you or others can provide.
Have OTG cable & flashdrive
revulv said:
You need a USB-OTG cable and some files. If you have a USB-OTG i'll reply with what you'll need to do. Also, have you contacted the eBay member letting them no they FRP screwed you and you basically own a brick now?
Click to expand...
Click to collapse
I am stuck in the same boat, bought what appears to be a brick. Would be most grateful if I could get the files/procedure you mentioned as well.
Sorry guys!
https://www.youtube.com/watch?v=xNSBbpVOmb4
Thank you for the suggestion , but this method does not work. I have already tried this and after the tool went through all the steps, it still asks for the previous account. I have found on some other forums that LG patched this flaw a few months ago and it is no longer possible to bypass FRP Factory Reset Protection. I guess I have a rock until someone can figure out how to bypass this "Feature", which in my opinion should be illegal because it forces people to buy devices from carriers only and you can no longer sell your phone online to anyone, as you cannot give them the account.
webmanny said:
but this method does not work..
Click to expand...
Click to collapse
It didn't work for me either... the last security patch disabled user from the settings menu. I did find a way after many hours of work.
Basically once I got to settings I clicked unknown sources and then enabled USB debugging and oem unlock. After that I flashed twrp and then a rooted system image. After that I used http://androiding.how/bypass-google-account-verification-on-lg-g4-g3-and-others and it worked
Sent from my HTC One M9 using XDA-Developers mobile app
bigp951 said:
Basically once I got to settings I clicked unknown sources and then enabled USB debugging and oem unlock. After that I flashed twrp and then a rooted system image. After that I used http://androiding.how/bypass-google-account-verification-on-lg-g4-g3-and-others and it worked
Click to expand...
Click to collapse
How did you get to settings? I am only able to get to the accessibility to turn on the voice stuff.
webmanny said:
How did you get to settings? I am only able to get to the accessibility to turn on the voice stuff.
Click to expand...
Click to collapse
I honestly don't remember. I'll try to figure it out and get back to you. I think it was through the keyboard. I returned the phone already so I do t have it on front of me.
Look for anything with terms of service. Once you're on the internet you can download the settings app that everyone uses on the internet.
Sent from my HTC One M9 using XDA-Developers mobile app
Web trust me i went crazy with this for 3 days. My friend gave me his Stylo from work to unlock and i had this same issue. Flashed back to 5.1.1e,i,j, using kdz files and all the exploits that these guys are using have been shut down. If your on MM forget it. The only thing that worked for me was that tool i linked in the other thread. I hope your wrong on the virus part, ill check my laptop, but your the first person to mention that. Either way i flashed back to 5.1.1 from MM, used the tool, rebooted and it worked i signed in with his gmail.
sshafranko said:
Web trust me i went crazy with this for 3 days. My friend gave me his Stylo from work to unlock and i had this same issue. Flashed back to 5.1.1e,i,j, using kdz files and all the exploits that these guys are using have been shut down. If your on MM forget it. The only thing that worked for me was that tool i linked in the other thread. I hope your wrong on the virus part, ill check my laptop, but your the first person to mention that. Either way i flashed back to 5.1.1 from MM, used the tool, rebooted and it worked i signed in with his gmail.
Click to expand...
Click to collapse
I understand and I apologize if I sounded like I was shutting your advise down. That was not my intention. I was just stating what my virus tools detected and my experience. Regardless, I decided to ignore the virus warning and let the tool run and do what the steps on the word document stated. It went through all the steps without issues and I got the same matching screen as in the tutorial document. However, after I reboot, I still get the same screen that reads, login with a google account previously associated with this device.
Now, the one piece I'm not sure I understand from your message above is the part about flashing to 5.1.1 from MM using kdz files. How can you flash the phone when you cannot get into the settings to enable usb debug mode? I have tried everything. I even downloaded a rom file image that I placed on an Micro SD card and tried running it from recovery to no avail.
Maybe you are correct and I am just missing a step. Would you mind expanding on the flashing 5.1.1 from MM part? Maybe what steps and files you had to use?
Also, I'm not sure I understand this portion of your message. You signed in with who's gmail?
sshafranko said:
i signed in with his gmail.
Click to expand...
Click to collapse
Thank you in advance for your assistance.
is there a software older than 5.1.1 that can be flashed to the device?
You can use touch assistant to get in to settings and then disable all google aps, works for me on lg stylo 6.0, PaulieP he is the person that found this method

ODIN Fails Every Time

Hi,
So I was trying to root my phone and it all went wrong. I have rooted tons of phones before, but never a Samsung (never again).
The phone will show the Samsung Boot screen, but then it either goes black, with a flashing blue LED, or it boots itself into recovery.
When I use ODIN, the flash fails at "system.img.ext4" whenever I use just the AP field. If I load all the fields in, it fails at "xbl.elf"
I got the firmware file from SamMobile, so I don't think that is the issue, but who knows. It's as if the phone no longer has an OS on it. I also tried using SmartSwitch as well, but I have no idea what the S/N on this phone is. It was originally a Sprint phone and was working fine, but I could never find the S/N. It is nowhere on the phone itself, and was not listed when I typed #*06#. All I have is the IMEI.
Finally, when it is in recovery, there is a message at the bottom that reads, "dm-verity verification failed".
Sorry for the bullet point style here, I am on mobile. If anyone can assist, I would be very grateful!
ebercon said:
Hi,
So I was trying to root my phone and it all went wrong. I have rooted tons of phones before, but never a Samsung (never again).
The phone will show the Samsung Boot screen, but then it either goes black, with a flashing blue LED, or it boots itself into recovery.
When I use ODIN, the flash fails at "system.img.ext4" whenever I use just the AP field. If I load all the fields in, it fails at "xbl.elf"
I got the firmware file from SamMobile, so I don't think that is the issue, but who knows. It's as if the phone no longer has an OS on it. I also tried using SmartSwitch as well, but I have no idea what the S/N on this phone is. It was originally a Sprint phone and was working fine, but I could never find the S/N. It is nowhere on the phone itself, and was not listed when I typed #*06#. All I have is the IMEI.
Finally, when it is in recovery, there is a message at the bottom that reads, "dm-verity verification failed".
Sorry for the bullet point style here, I am on mobile. If anyone can assist, I would be very grateful!
Click to expand...
Click to collapse
I'm new to the s7. long time lg man
on lg ussally means either ure trying to flash a non signed image or downgrade a qfused bootloader anti rollback which sprint is good for.
in dl mode after fail its not showing anything about binary and stuff in red is it
TheMadScientist420 said:
I'm new to the s7. long time lg man
on lg ussally means either ure trying to flash a non signed image or downgrade a qfused bootloader anti rollback which sprint is good for.
in dl mode after fail its not showing anything about binary and stuff in red is it
Click to expand...
Click to collapse
It does say something about binary in there. Binary 3 I believe. I'll have to try again to get the error.
ebercon said:
It does say something about binary in there. Binary 3 I believe. I'll have to try again to get the error.
Click to expand...
Click to collapse
sounds the firmware u are flashing is older than what you have on the device hence the fail
try to find newer firmware and try flashing it
download
Download official nougat from sam mobile then flash with Odin. It will definitely solve your problem
amol6630 said:
Download official nougat from sam mobile then flash with Odin. It will definitely solve your problem
Click to expand...
Click to collapse
I may try this as well. I flashed the newest firmware I could find other than Nougat and I now have it booting all the way up and then after about a minute, it loops again. It is at least further along than before.
I just remembered one detail: The original issue began when I flashed a modified boot.img to the phone during a rooting attempt. Could this be what is still causing the issue and preventing a reformatting of the phone from solving the issue? So lost with this thing...
Try with latest firmware + pit file + tick re-partition
ebercon said:
I may try this as well. I flashed the newest firmware I could find other than Nougat and I now have it booting all the way up and then after about a minute, it loops again. It is at least further along than before.
I just remembered one detail: The original issue began when I flashed a modified boot.img to the phone during a rooting attempt. Could this be what is still causing the issue and preventing a reformatting of the phone from solving the issue? So lost with this thing...
Click to expand...
Click to collapse
Sorry to revive this thread but did this work cause its currently happening to me
If your phone is an original, S/N may be engraved in the back... it's a little bit hard to note but put a spotlight near it so that you can identify it better.
hhh ^^

SM-G955U1. XAA version. Bootloop problem, any help?

MY BAD, PLEASE MOVE THIS TO THE CORRECT SECTION. I'M REALLY SORRY.
Hello!, my mother bought this phone for her in the US and from day 0 it has been having problems. She couldn't use wifi or bluetooth for example, and sometimes it just kept restarting till it worked again, but without any connectivity functions, except mobile data.
I tried to fix this updating the phone using Samsung Smart Switch to the last build (AQL1) but now the phone is stuck on the boot screen no matter what I do.
Tried flashing with Odin, it worked, but the phone is still on boot loop. I read somewhere in this forum that you can install an older version of the bootloader to take the phone out of this hell and I did it, using the build AQK2 bootloader but no luck, same problem.
Also, the phone doesn't have USB debugging enable nor OEM unlock either. I can access both recovery and download mode though.
At this point I'm out of ideas, can someone help me with this one?
Thanks in advanced.
fefin
fefin said:
MY BAD, PLEASE MOVE THIS TO THE CORRECT SECTION. I'M REALLY SORRY.
Hello!, my mother bought this phone for her in the US and from day 0 it has been having problems. She couldn't use wifi or bluetooth for example, and sometimes it just kept restarting till it worked again, but without any connectivity functions, except mobile data.
I tried to fix this updating the phone using Samsung Smart Switch to the last build (AQL1) but now the phone is stuck on the boot screen no matter what I do.
Tried flashing with Odin, it worked, but the phone is still on boot loop. I read somewhere in this forum that you can install an older version of the bootloader to take the phone out of this hell and I did it, using the build AQK2 bootloader but no luck, same problem.
Also, the phone doesn't have USB debugging enable nor OEM unlock either. I can access both recovery and download mode though.
At this point I'm out of ideas, can someone help me with this one?
Thanks in advanced.
fefin
Click to expand...
Click to collapse
Have you reached out to Samsung yet?
Mr. Orange 645 said:
Have you reached out to Samsung yet?
Click to expand...
Click to collapse
Thanks for answering. Where I live there is not a single Samsung Service, only at like 1800km from here, that's why I'm trying to solve this by myself but seems that this is a hard one... I hope someone can help me to deal with this as it was a big investment :/
Thanks again!, if someone knows a way to help please tell me.
fefin
fefin said:
Thanks for answering. Where I live there is not a single Samsung Service, only at like 1800km from here, that's why I'm trying to solve this by myself but seems that this is a hard one... I hope someone can help me to deal with this as it was a big investment :/
Thanks again!, if someone knows a way to help please tell me.
fefin
Click to expand...
Click to collapse
I mean have you called or emailed Samsung?
Mr. Orange 645 said:
I mean have you called or emailed Samsung?
Click to expand...
Click to collapse
No I haven't, I will give a try soon through web chat.
I mean, this shouldn't be happening, it's a brand new phone, all over the internet are people with the same problems as me and looks like so far there is no solution.
Maybe it's a faulty phone/hardware? My knowledge is not enough in this matter.
See you!,
Federico.
I need a couple things from you
1. What model does it say on the back of the phone i understand you posted it in the header but please for safety sake .
2. Go into download mode for me so i can see what carrier it lists
3. Try wiping data cache in recovery
Sent from my SM-G955U1 using XDA-Developers Legacy app
allenjthomsen said:
I need a couple things from you
1. What model does it say on the back of the phone i understand you posted it in the header but please for safety sake .
2. Go into download mode for me so i can see what carrier it lists
3. Try wiping data cache in recovery
Sent from my SM-G955U1 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Thanks for answering!, here it goes:
1. It says SM-G955U1
2. Carrier: XAA
3. Done, still the same.
An update from my last post:
After a few bootloops the FRP screen showed up, as the phone can't use wifi yet I managed to access using mobile data and enabled the USB debugging, but after trying to enable wifi the phone froze and went on bootloop again, so still the same but with the USB debugging enabled. I'm currently on the build AQK2.
Thanks again, and I hope we can fix this.
Update 2:
I cleared the cache, after a few bootloops the phone actually boots (gets to the lock screen), and it restarts again while the message "Android is starting" is loading, so now it's a different type of bootloop I guess. It does the same even in safe mode.
I will turn it off for now.
fefin said:
Thanks for answering!, here it goes:
1. It says SM-G955U1
2. Carrier: XAA
3. Done, still the same.
An update from my last post:
After a few bootloops the FRP screen showed up, as the phone can't use wifi yet I managed to access using mobile data and enabled the USB debugging, but after trying to enable wifi the phone froze and went on bootloop again, so still the same but with the USB debugging enabled. I'm currently on the build AQK2.
Thanks again, and I hope we can fix this.
Update 2:
I cleared the cache, after a few bootloops the phone actually boots (gets to the lock screen), and it restarts again while the message "Android is starting" is loading, so now it's a different type of bootloop I guess. It does the same even in safe mode.
I will turn it off for now.
Click to expand...
Click to collapse
Ok i want you to do a couple things for me
1.Download this file http://updato.com/firmware-archive-select-model?record=F837B5F2EC0611E7A5F9FA163EE8F90B this is the latest update for the G955U1
2. extract the zip file using 7zip so you have 5 .tar.md5 files
3. go to the CSC_OYM_G955U1OYM2AQL1_CL12513005_QB15986651_REV00_user_low_ship_MULTI_CERT.tar.md5 and right click on the file and goto 7-zip and then click open archive
4. you will see a file called DREAM2QLTE_USA_SINGLE.pit i want you to extract it to the folder you have Odin in if not quick search forums for it
5. Open odin and go to the the pit tab it will do a pop up just click ok and ignore
6. click the pit button and find the pit file that you extracted and select it
7. now go to options tab
8.check to make sure you have auto reboot, re-partition, and f reset timer checked
9.Load BL,AP,CP,CSC in respective slots on right side
10. click start and let the phone flash, as soon as it is done hold volume up bixby and power button wait for recovery to load and wipe data and factory reset.
11. reboot and let it boot if you are still in a bootloop after these steps pm me and i will help you the last way i know how to fix these phones.
allenjthomsen said:
Ok i want you to do a couple things for me
1.Download this file http://updato.com/firmware-archive-select-model?record=F837B5F2EC0611E7A5F9FA163EE8F90B this is the latest update for the G955U1
2. extract the zip file using 7zip so you have 5 .tar.md5 files
3. go to the CSC_OYM_G955U1OYM2AQL1_CL12513005_QB15986651_REV00_user_low_ship_MULTI_CERT.tar.md5 and right click on the file and goto 7-zip and then click open archive
4. you will see a file called DREAM2QLTE_USA_SINGLE.pit i want you to extract it to the folder you have Odin in if not quick search forums for it
5. Open odin and go to the the pit tab it will do a pop up just click ok and ignore
6. click the pit button and find the pit file that you extracted and select it
7. now go to options tab
8.check to make sure you have auto reboot, re-partition, and f reset timer checked
9.Load BL,AP,CP,CSC in respective slots on right side
10. click start and let the phone flash, as soon as it is done hold volume up bixby and power button wait for recovery to load and wipe data and factory reset.
11. reboot and let it boot if you are still in a bootloop after these steps pm me and i will help you the last way i know how to fix these phones.
Click to expand...
Click to collapse
Sadly it didn't work. The phone is still loading till "android is starting" sign and then restarting again.
I will write you so you can help me through pm, could this be a faulty hardware?
I'd like to know the other solution too.
I will tell you all what todo as a last resort.
IF YOU CHOOSE TO DO THIS I TAKE NO RESPONSIBILITY IF YOUR DEVICE STOPS WORKING OR DOES NOT TURN ON!!!
Follow all previously said steps i outlined but when you go into the options tab select nand erase all also then flash device.
Sent from my SM-G955U1 using XDA-Developers Legacy app
try installing PartCyborgRom
@fefin -Sorry to hear that you're having issues - But I'd like to clear one thing up - Your comment that this is an issue "all over the internet" sim isn't true... I don't know how many Millions of S8 / S8+ have been sold - But your post is the first that I've ever heard of anything like this... I concur with the recommendation that you call or Chat with Samsung Technical Support - Preferably before you find the phone completely unable to Boot into Download Mode - Get Samsung to help you - or you may risk voiding the warranty if Samsung determines that you are ultimately responsible for the state of the phone ??
Sent from my SM-G955W ??
allenjthomsen said:
I will tell you all what todo as a last resort.
IF YOU CHOOSE TO DO THIS I TAKE NO RESPONSIBILITY IF YOUR DEVICE STOPS WORKING OR DOES NOT TURN ON!!!
Follow all previously said steps i outlined but when you go into the options tab select nand erase all also then flash device.
Sent from my SM-G955U1 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Thanks for your help! Much appreciated.
DR25 said:
try installing PartCyborgRom
Click to expand...
Click to collapse
Thanks for your suggestion, I will look into it.
shaggyskunk said:
@fefin -Sorry to hear that you're having issues - But I'd like to clear one thing up - Your comment that this is an issue "all over the internet" sim isn't true... I don't know how many Millions of S8 / S8+ have been sold - But your post is the first that I've ever heard of anything like this... I concur with the recommendation that you call or Chat with Samsung Technical Support - Preferably before you find the phone completely unable to Boot into Download Mode - Get Samsung to help you - or you may risk voiding the warranty if Samsung determines that you are ultimately responsible for the state of the phone
Sent from my SM-G955W
Click to expand...
Click to collapse
Thanks for answering!, sorry for my late response.
Well, if you check samsung's official forum there are a few threads with 15+ pages of people complaining about wifi issues (https://us.community.samsung.com/t5/forums/v3_1/forumtopicpage/board-id/GS8QA/thread-id/862/page/1 and https://us.community.samsung.com/t5/forums/v3_1/forumtopicpage/board-id/GS8QA/thread-id/30601/page/1) about bootloop problems, (https://us.community.samsung.com/t5...id/GS8QA/thread-id/3920/highlight/true/page/1) also there is a post on another webpage talking about bootloops on this model and how to fix them (https://thedroidguy.com/2017/12/sol...p-issue-s8-turns-screen-remains-black-1079013).
I know it's not representative, as you said, millions of phones has been sold, but what I meant when I said "all over the internet" is that you can easily find people with this same problem. This shouldn't be happening, not on any phone even less on such an expensive phone.
I think the phone is officially dead, I took it to a well known local technician and even him couldn't fix it. My nearest official samsung service is 1600km away. On the other hand, my aunty got for herself an S8 and it's working perfect, so it's just bad luck for my mom I guess.
The phone had issues since she bought it (wifi and bluetooth didn't worked at all, but she is not really a tech person so she thought it was fine), the phone was working with some bootloops from time to time and after a while it fell from and got a little crack on the top but it didn't change the behavior of the phone, it was still ****ed up. That's the thing, because of the crack I'm pretty sure they won't take it back or even try to fix it (for free at least), they will say the problem is because of the fall. I'd been reading a lot about this and seems that I'm pretty screwed D:
I will sell the phone for parts. At least I will recover 60% of the initial investment.
fefin said:
That's the thing, because of the crack I'm pretty sure they won't take it back or even try to fix it (for free at least), they will say the problem is because of the fall. I'd been reading a lot about this and seems that I'm pretty screwed D:
I will sell the phone for parts. At least I will recover 60% of the initial investment.
Click to expand...
Click to collapse
If you have some 'proof' the problem existed, before the crack, and can prove when the crack occurred, or reasonable determinate approximation, small claims court will vindicate you, and Samsung will have to pay.
Sad to say would take a little time of yours to get them there, but it is an easy process, and with reasonable ability to determine/evidence those two things, a sure win.
But still a PITA.

Question Desperately need assistance

Hello everyone, I desperately need assistance because I think I may have soft bricked my work provided SM-A536B/DS.
What I tried to do initially is to install TWRP so I unlocked the bootloader successfully. Then, I saw different posts here on XDA where people have successfully installed cust ROMs so i tried to do that. This is when the problems started...
Right now my phone is bricked, I assume it is a soft brick because I can still get it to download mode. I did some research prior writing here, and everyone is mentioning to flash the stock ROM. That does not work.
Right now, the phone has bootloader unlocked: (Screen1)
It is asking me to lock it, so that means it's already unlocked.
Tried to access TWRP but I cannot since I get this screen when I do vol up + power: (Screen 2)
My phone was bought in Europe. I am not entirely sure whick ROM is the right one. Is there a way to check which is the right one to download? There are multiple ROMs I can download for Europe: (Screen3)
My country is not in the list so i downloaded the 2 generic for Europe. I put my phone in download mode: (Screen4)
However Odin fails everytime, no matter what files I add: (Screen5), (Screen6)
Since TWRP is not working, I locked the bootloader again to see if I could get Samsung bootloader to show up. I think i might have deleted it somehow, because I get the same thing as before when i do vol up + power. And as you can see, the bootloader is not locked: (Screen7)
I am now stuck and screwed, because this is my work phone. Any help is greatly appreciated.
psorincatalin87 said:
Hello everyone, I desperately need assistance because I think I may have soft bricked my work provided SM-A536B/DS.
What I tried to do initially is to install TWRP so I unlocked the bootloader successfully. Then, I saw different posts here on XDA where people have successfully installed cust ROMs so i tried to do that. This is when the problems started...
Right now my phone is bricked, I assume it is a soft brick because I can still get it to download mode. I did some research prior writing here, and everyone is mentioning to flash the stock ROM. That does not work.
Right now, the phone has bootloader unlocked: (Screen1)
It is asking me to lock it, so that means it's already unlocked.
Tried to access TWRP but I cannot since I get this screen when I do vol up + power: (Screen 2)
My phone was bought in Europe. I am not entirely sure whick ROM is the right one. Is there a way to check which is the right one to download? There are multiple ROMs I can download for Europe: (Screen3)
My country is not in the list so i downloaded the 2 generic for Europe. I put my phone in download mode: (Screen4)
However Odin fails everytime, no matter what files I add: (Screen5), (Screen6)
Since TWRP is not working, I locked the bootloader again to see if I could get Samsung bootloader to show up. I think i might have deleted it somehow, because I get the same thing as before when i do vol up + power. And as you can see, the bootloader is not locked: (Screen7)
I am now stuck and screwed, because this is my work phone. Any help is greatly appreciated.
Click to expand...
Click to collapse
This is why it's a bad idea to screw with work provided devices. You don't own the phone, and you will be held financially responsible for it if it's damaged or broken.
You're trying to flash the wrong firmware. You have G925F selected; your device is an A536B. The latest firmware for your device is A536BXXU4BVL2. Use Frija to download the latest firmware.
Since this is a work owned device, the only advice I will offer is this: Return the phone to stock with the correct software, re-lock the bootloader, and do not attempt to modify it as it is most likely in violation of your company's technology acceptable use policy.
V0latyle said:
This is why it's a bad idea to screw with work provided devices. You don't own the phone, and you will be held financially responsible for it if it's damaged or broken.
You're trying to flash the wrong firmware. You have G925F selected; your device is an A536B. The latest firmware for your device is A536BXXU4BVL2. Use Frija to download the latest firmware.
Since this is a work owned device, the only advice I will offer is this: Return the phone to stock with the correct software, re-lock the bootloader, and do not attempt to modify it as it is most likely in violation of your company's technology acceptable use policy.
Click to expand...
Click to collapse
Yes, this is what I am trying to do, to return to stock ROM. I downloaded A536BXXU4BVL2 for my phone, not G925F (this is what Odin uses as an example).
psorincatalin87 said:
Yes, this is what I am trying to do, to return to stock ROM. I downloaded A536BXXU4BVL2 for my phone, not G925F (this is what Odin uses as an example).
Click to expand...
Click to collapse
What version of Odin are you using?
Your bootloader is still unlocked, correct?
If you're unable to reflash the OEM firmware in Odin, I don't think there's anything else that can be done.
To be completely honest with you, I'm not sure trying to help you is worth the effort, because you did something you shouldn't be doing anyway, and any consequences you may face are entirely of your own doing.
V0latyle said:
What version of Odin are you using?
Your bootloader is still unlocked, correct?
If you're unable to reflash the OEM firmware in Odin, I don't think there's anything else that can be done.
To be completely honest with you, I'm not sure trying to help you is worth the effort, because you did something you shouldn't be doing anyway, and any consequences you may face are entirely of your own doing.
Click to expand...
Click to collapse
Yes, i know I did something bad and I learned my lesson.
I'm using Odin 3.14 and indeed, bootloader is still unlocked. I really appreciate the help!
psorincatalin87 said:
Yes, i know I did something bad and I learned my lesson.
I'm using Odin 3.14 and indeed, bootloader is still unlocked. I really appreciate the help!
Click to expand...
Click to collapse
I downloaded the firmware with Frija and I get the same issue with Odin.
psorincatalin87 said:
I downloaded the firmware with Frija and I get the same issue with Odin.
Click to expand...
Click to collapse
What options do you have checked in Odin?
V0latyle said:
What options do you have checked in Odin?
Click to expand...
Click to collapse
I haven't touched any of the options, everything is on default.
While reading this post something popped in my head.
I dont have this phone, but a Xiaomi Mi8.
When I want to adb push or sideload stuff into phone while it is in recovery or download mode, certain usb ports will work and others wont. And there is not a clear error when it's plugged to non-working usb port, just fails in the middle of a transfer with a generic error message.
Maybe totally irrelevant, just wanted to share.
nsfnd said:
While reading this post something popped in my head.
I dont have this phone, but a Xiaomi Mi8.
When I want to adb push or sideload stuff into phone while it is in recovery or download mode, certain usb ports will work and others wont. And there is not a clear error when it's plugged to non-working usb port, just fails in the middle of a transfer with a generic error message.
Maybe totally irrelevant, just wanted to share.
Click to expand...
Click to collapse
OH.MY.GOD! Thank you very much, man! I love you! I could kiss you right now, stranger!
Haha I'm glad it worked.
Hope you get better luck on your future rom adventures.
nsfnd said:
Haha I'm glad it worked.
Hope you get better luck on your future rom adventures.
Click to expand...
Click to collapse
Nah, this is my last one.
psorincatalin87 said:
Nah, this is my last one.
Click to expand...
Click to collapse
don't be that way lol, it's fun, just do it on hardware you own. get a cheap phone off ebay to play with

Categories

Resources