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.
Related
{
"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"
}
Not too sure what the error message in the green means.
Flashed to the 0.84spl. Could that be the problem? Also, when I try to flash from the sd card it gets stuck on a gray screen saying loading and stuck at 0% when flashing from usb.
The phone does not even get the splash screens or anything, just right to the bootloader.
Any thoughts?
happened to me after a reboot. just took the battery off and put it back in, worked.
d412k5t412 said:
happened to me after a reboot. just took the battery off and put it back in, worked.
Click to expand...
Click to collapse
I tried that already.
I searched for any info on the error message in the green but couldn't find anything.
Manual hard reset.
Hard Reset (This cannot be performed while the device is connected/charging)
* With the device turned off, press and hold the TALK/SEND and END/HANG UP buttons, then the press and hold the POWER button until you see this message on the screen.
* "This operation will delete all your personal data, and reset all settings to manufacturer default. Press ?VolUp to restore manufacturer default, or press other keys to cancel."
* Release the TALK/SEND, END and POWER buttons.
* Press the VOLUME UP button to perform the hard reset, or press any other button to cancel the reset.
If you have a Telus or Verizon TP2 (Sprint not tested but likely the same), the combination is different.
* Power off the phone using the 'end' key.
* Hold 'volume down' and 'send', the press 'end' till you see blue text. Follow hard reset prompts.
stesul411 said:
Manual hard reset.
Hard Reset (This cannot be performed while the device is connected/charging)
* With the device turned off, press and hold the TALK/SEND and END/HANG UP buttons, then the press and hold the POWER button until you see this message on the screen.
* "This operation will delete all your personal data, and reset all settings to manufacturer default. Press ?VolUp to restore manufacturer default, or press other keys to cancel."
* Release the TALK/SEND, END and POWER buttons.
* Press the VOLUME UP button to perform the hard reset, or press any other button to cancel the reset.
If you have a Telus or Verizon TP2 (Sprint not tested but likely the same), the combination is different.
* Power off the phone using the 'end' key.
* Hold 'volume down' and 'send', the press 'end' till you see blue text. Follow hard reset prompts.
Click to expand...
Click to collapse
Tried that as well, it goes to the gray loading screen and tells me to reboot but the phone just loads back into the tri-colored screen.
If it was a Hermes or Kaiser I'd be able to help more but, I'm new to the Rhodium myself.
Can you get to the boot screen (tricolor) manually???
IF you can get to the boot screen may try loading one of the stock roms onto it. That MAY NOT work but it might be worth a try.
Hi !
I had this error, too. It happened, because the image i wanted to flash was corrupt and i had to take out the battery to stop the flash. After that the phone showed the mentioned error.
In your case perhaps the data transfer between PC and phone was interrupted for a moment.
I always flash by storage card. This way is much more safer.
Solution : Take out the storage card (if you have one) and copy another image on it. After I had done this could flash again and the error disappeared.
Greets
The storage card option may work, just make sure the card is formatted as fat32.
stesul411 said:
Can you get to the boot screen (tricolor) manually???
Click to expand...
Click to collapse
Nope, it does that itself.
stesul411 said:
IF you can get to the boot screen may try loading one of the stock roms onto it. That MAY NOT work but it might be worth a try.
Click to expand...
Click to collapse
I've tried the recent Tilt 2 stock rom to no results. I will try the rom again on a different card tho.
yoda2000 said:
Hi !
I had this error, too. It happened, because the image i wanted to flash was corrupt and i had to take out the battery to stop the flash. After that the phone showed the mentioned error.
In your case perhaps the data transfer between PC and phone was interrupted for a moment.
I always flash by storage card. This way is much more safer.
Solution : Take out the storage card (if you have one) and copy another image on it. After I had done this could flash again and the error disappeared.
Greets
Click to expand...
Click to collapse
Thats not a bad idea. I have another SD with me that I can format and put another image on it. Now would I try the SPL flash again or just a rom of some sort?
You need to have HardSPL to use the stock AT&T rom, it's a cooked rom for warranty recovery and not from AT&T. AT&T hasn't released a OEM rom for the T2 yet. I'd try one of the other OEM roms.
THREAD HERE:
http://forum.xda-developers.com/showthread.php?t=570366
stesul411 said:
You need to have HardSPL to use the stock AT&T rom, it's a cooked rom for warranty recovery and not from AT&T. AT&T hasn't released a OEM rom for the T2 yet. I'd try one of the other OEM roms.
THREAD HERE:
http://forum.xda-developers.com/showthread.php?t=570366
Click to expand...
Click to collapse
Yup. I had it HSPL'd already but I have to return it due to a blown speaker. I was worried that they would check the SPL and then I'd be screwed. But I read in the giant SPL thread that the 0.84SPL would work just fine. I'm thinking there is a problem going to a HSPL to a stock one.
I've tried a different card with a different rom and its the same, just stuck saying "loading". I have an idea that I may need to Hard SPL it again due to the fact that I cant flash an official ATT rom yet.
the 0.84 is a stock SPL, you may wanna try the the HardSPL then flash the cooked "stock ROM", then run the relocker in the HardSPL thread to return it to stock.
The instructions are in the AT&T stock ROM thread.
OR just turn it in like it is, tell them you dont know what happened, it was like that when you turned it on this morning. LOL
I bricked my first Hermes 2 days after I got it, took it back to the AT&T store, they had no idea what the boot screen was, and gave me a brand new one.
stesul411 said:
the 0.84 is a stock SPL, you may wanna try the the HardSPL then flash the cooked "stock ROM", then run the relocker in the HardSPL thread to return it to stock.
The instructions are in the AT&T stock ROM thread.
OR just turn it in like it is, tell them you dont know what happened, it was like that when you turned it on this morning. LOL
I bricked my first Hermes 2 days after I got it, took it back to the AT&T store, they had no idea what the boot screen was, and gave me a brand new one.
Click to expand...
Click to collapse
Haha, I could try that. I know the sales people at the att store I got to are not the brightest around. I'll try the HSPL again although I will have to get another license I think.
See how it says RUUNBH at the top, that's your problem. The RUU flag is set, and the bootloader thinks a nonexistant ROM is being flashed. You won't be able to flash anything, or even do anything, until that is unset.
Now, I remember you could reset the RUU Flag by typing set 16 0, then task 8, then task 0 into MTTY on the Kaiser, but since commands change with SPL versions, you shouldn't run them until you are absolutely sure they are safe, since you CAN brick your device wth MTTY. This is an issue best left to those who know the Rhodium SPL .84 commands, since that's what you need right now.
However, you appear to be on AT&T stock SPL, so unless you have a cooked ROM on the device, you should be able to return it as is.
DaveTheTytnIIGuy said:
See how it says RUUNBH at the top, that's your problem. The RUU flag is set, and the bootloader thinks a nonexistant ROM is being flashed. You won't be able to flash anything, or even do anything, until that is unset.
Click to expand...
Click to collapse
A successful ROM flash should clear the RUUNBH, but it's often eaiser to do it yourself .
DaveTheTytnIIGuy said:
Now, I remember you could reset the RUU Flag by typing set 16 0, then task 8, then task 0 into MTTY on the Kaiser, but since commands change with SPL versions, you shouldn't run them until you are absolutely sure they are safe, since you CAN brick your device wth MTTY. This is an issue best left to those who know the Rhodium SPL .84 commands, since that's what you need right now.
Click to expand...
Click to collapse
set 16 0 works on the TP2 also.
DaveTheTytnIIGuy said:
However, you appear to be on AT&T stock SPL, so unless you have a cooked ROM on the device, you should be able to return it as is.
Click to expand...
Click to collapse
That's what I thought all the way down this thread.
Just send it in. It's standard phone, just tell them it did this when your turned it on .
Ta
Dave
Thanks for the help guys. It seems like I will just bring it into a store and act like a helpless customer lol. Although, it is tempting to see if I could unset the RUU with MTTY but I know very little about the SPL commands and how to work them.
Request detailed instructions for a newbee
Hi,
I have the exact same problem as the one described above. The only difference being that I bought the phone from Ebay and therefore will not have recourse to official servicing. It is a T-Mobile HTC Touch pro 2. Request if you could provide me with some instructions as to how I can get the phone working once again.
From the little that I read on the site, I tried to connect the phone to MTTY from the computer but I was unable to access the phone from the computer.
I have bought a similar phone for my wife (AT&T Tilt2) so I am worried that I might end up bricking her phone as well.
Thanks in anticipation
Phiroze
Is it still under warranty? You could try that route, sorry i cant be of more direct help.
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
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.
After years of flashing roms (and lurking here, especially DrKetan´s thread), I hard bricked my brand new SM-N975F. When I power it on, it goes to the screen that tells me the bootloader is unlocked, then to a welcome screen, and that is where it stays. (see pics).
I have tried the following:
1) All possible hardware combinations. (I tried at least 100 times all combinations between the keys): always the same.
2) Odin3 does not detect the phone in either screen.
3) Samsung Tool 300K does not detect the phone.
4) ADB does not detect the phone. (adb devices comes empty)
I am about to get a hammer and wreck the little guy, but I decided to ask you first.
Any ideas?
{
"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"
}
i think if u post what firmware u was and what did u flashed or what u did ,,, its better that maybe someone can help
Sent from my SM-N975F using Tapatalk
carlitobahsoun said:
i think if u post what firmware u was and what did u flashed or what u did ,,, its better that maybe someone can help
Click to expand...
Click to collapse
Thank you! I was on stock ROM (Q), with an unlocked bootloader. I was flashing TWRP for Android Q with Odin. It "Pass"ed, and when I rebooted it bricked. Tried every key combination, I can´t get into download mode and the phone is not recognized when connected to the laptop. Tried several cables, too.
dk1965 said:
Thank you! I was on stock ROM (Q), with an unlocked bootloader. I was flashing TWRP for Android Q with Odin. It "Pass"ed, and when I rebooted it bricked. Tried every key combination, I can´t get into download mode and the phone is not recognized when connected to the laptop. Tried several cables, too.
Click to expand...
Click to collapse
i think ur fault was when u let it reboot / u must after odin twrp forced to reboot to custom twrp recovery and do as i think format data , well never root my samsung mobiles 3 years ago , i advice u to be cool + send private msg to dr ketan to get help OR if u have telegrams u can join many group and i know u will get help.
iam out of telegram 1 years ago too so i dont know any groups for n10+ .
try first dr ketan by pm him and wait till anyone read here and help
Sent from my SM-N975F using Tapatalk
you should put the phone in download mode and reflash stock from odin.
reboot [down+pwr] when the screen shut down immediately put the usb cable in the phone usb port (the other already in the port of the pc) keeping the vol down till enters in download mode.
you cannot flash just the twrp partition, you have to flash the disable verity check as well. otherwise the bootloader dont't allow the bootstrap as the integrity check fails.
follow the dr.ketan instructions (carefully).
Inviato dal mio SM-N975F utilizzando Tapatalk
ziotom2 said:
you should put the phone in download mode and reflash stock from odin.
reboot [down+pwr] when the screen shut down immediately put the usb cable in the phone usb port (the other already in the port of the pc) keeping the vol down till enters in download mode.
you cannot flash just the twrp partition, you have to flash the disable verity check as well. otherwise the bootloader dont't allow the bootstrap as the integrity check fails.
follow the dr.ketan instructions (carefully).
Inviato dal mio SM-N975F utilizzando Tapatalk
Click to expand...
Click to collapse
Thank you! I tried Dr Ketan´s instructions, but no matter how hard I try, I can´t get to the download mode. I followed your instructions but the phone does not go to download mode, it just shows the "bootloader modified" screen, then the other one. Odin (nor Samsung Tool 300K) do not recognize the phone at any time, not even for a second, so I can´t flash anything to it.
Sm-n975f hard brick - solved
I hard bricked my SMN975F by uploading the wrong TWRP. The bootloader was already unlocked, but the new TWRP for Q bricked it.
I solved it by sending the phone to a Samsung repair shop. It took them 24 hours (and about 70 dollars), but they were able to flash the bootloader, and the stock Q rom.
Moral of the story: if your Note 10+ is hard bricked, there is a solution. You can try the advice given to me above by these useful members, but if that fails do not toss the phone. Go to a Samsung service store, and they will be able to fix it. Thank you all for their help!
dk1965 said:
I hard bricked my SMN975F by uploading the wrong TWRP. The bootloader was already unlocked, but the new TWRP for Q bricked it.
I solved it by sending the phone to a Samsung repair shop. It took them 24 hours (and about 70 dollars), but they were able to flash the bootloader, and the stock Q rom.
Moral of the story: if your Note 10+ is hard bricked, there is a solution. You can try the advice given to me above by these useful members, but if that fails do not toss the phone. Go to a Samsung service store, and they will be able to fix it. Thank you all for their help!
Click to expand...
Click to collapse
happy they solve it but let me be honest with u , in my country LEBANON middle east i KNOW and more knowledge than SAMSUNG'S guys inside , some small questions they wasent able to answer....so u are lucky guys that in ur country they are good knowledge to fix....
happy new year and keep enjoy ur n10+
Sent from my SM-N975F using Tapatalk
You f##ked it real good but not a hard brick as far as I'm aware. (I may be wrong)
Hard brick is only fixable with a new motherboard.
Well done on getting it sorted and that's great service from sammy
I know you said you tried 100 times, different combinations, by any chance was this - Press and hold the Volume Up + Bixby / Power buttons. - one of them? It should boot into recovery mode not download mode. I had a similar issue, I had to try and try until I was able to get into recovery, from there did wipe data/factory reset several time, and then select reboot to bootloader, then flash the latest firmware(since you probably wont know which booltloader you have on it). Also remember to used the recommended Odin by the XDA team.
Try following alternate way.
- Turn Off Phone, if unable to turn off, wait till battery drain and off itself.
- Press and hold the Volume up and the Power keys at the same time for 3-4 seconds.
- This will bring you to Recovery Screen.
- Use Volume Up and Down Button to Navigate and choose Reboot to bootloader by pressing the power button.
- You are now at Download Mode.
Note 10+ SM-N975F/DS very very HARD BRICK --- Advice?
Andrewtst said:
Try following alternate way.
- Turn Off Phone, if unable to turn off, wait till battery drain and off itself.
- Press and hold the Volume up and the Power keys at the same time for 3-4 seconds.
- This will bring you to Recovery Screen.
- Use Volume Up and Down Button to Navigate and choose Reboot to bootloader by pressing the power button.
- You are now at Download Mode.
Click to expand...
Click to collapse
Thank you for your feedback. I had tried that, but the recovery screen did not come up. The method you suggest will work for most cases, but in my case I had screwed up the recovery itself by flashing the wrong TWRP.
Moral of the story: do not flash the wrong TWRP, because it may corrupt your recovery, and then getting to download mode is a lot more complicated.
exocetdj said:
You f##ked it real good but not a hard brick as far as I'm aware. (I may be wrong)
Hard brick is only fixable with a new motherboard.
Well done on getting it sorted and that's great service from sammy
Click to expand...
Click to collapse
I agree with you, real good. It may not be a complete hard brick, as the repair guys did not open the phone nor changed the motherboard. Still, it was as bad as a soft brick can get....
ust buy a z3 and fix it lol
Samsung Smart Switch
As far as I know, Samsung Smart Switch is the only method to recover your phone. Download it on your pc. Launch the app and connect your phone. Choose to recover bricked phone.
I bricked about 8 different phones with the new A/B thing before I learned TWRP doesn't work and the fix was to flash the stock boot.img to both partitions with:
./fastboot flash boot --slot all <nameofboot.img>
Download the modded version of Odin. Here's a link to it in my Google Drive: https://drive.google.com/folderview?id=10F5bh4YmD0vAduSMfuqF7jQl4ho1s83a
Sent from my [device_name] using XDA-Developers Legacy app
Did it work buddy?
Sent from my [device_name] using XDA-Developers Legacy app
I have the same issue
Sm-n975f hard brick - solved
Guys I solved it. I pressed Volume down + Power, as soon as the screen turned off I quickly pressed Volume up +Volume down as I inserted the cable and voila! Download mode. Now I can reflash stock firmware
That was a very close call.
Plz delete
---------- Post added at 06:20 PM ---------- Previous post was at 06:03 PM ----------
vs|porkchop said:
Sm-n975f hard brick - solved
Guys I solved it. I pressed Volume down + Power, as soon as the screen turned off I quickly pressed Volume up +Volume down as I inserted the cable and voila! Download mode. Now I can reflash stock firmware
That was a very close call.
Click to expand...
Click to collapse
YEAH you saved my ass!!!
Thank you wherever your are :victory:
God bless you :angel:
Hi, is it possible to flash a new firmware of this device while the samsung account still present on the device?
Can anyone tell me what would happen if i would simply flash a new firmware and root it without logging out the samsung account beforehand?
sarf2k4 said:
Hi, is it possible to flash a new firmware of this device while the samsung account still present on the device?
Can anyone tell me what would happen if i would simply flash a new firmware and root it without logging out the samsung account beforehand?
Click to expand...
Click to collapse
I'm not sure exactly what you're asking. If you dirty flash firmware (no data wipe) and root it, then you'd be updated with root and still have all your credentials on the device.
V0latyle said:
I'm not sure exactly what you're asking. If you dirty flash firmware (no data wipe) and root it, then you'd be updated with root and still have all your credentials on the device.
Click to expand...
Click to collapse
Sorry for not clarifying. What I meant is to simply flash a new firmware with odin while the samsung account still in the phone, as in, if we want to do a factory data reset from the settings interface, we have to key in the password or unbind the device from the account
sarf2k4 said:
Sorry for not clarifying. What I meant is to simply flash a new firmware with odin while the samsung account still in the phone, as in, if we want to do a factory data reset from the settings interface, we have to key in the password or unbind the device from the account
Click to expand...
Click to collapse
Are you asking whether flashing factory firmware will get rid of FRP?
I typically use Odin to flash firmware, and there's two ways to do it. In the firmware package, you have the BL, AP, CP, CSC, and HOME_CSC files. If you want to dirty flash without wiping user data (including a Samsung account), use the HOME_CSC file in the CSC slot. If however you want to force a data wipe, use the CSC file.
V0latyle said:
Are you asking whether flashing factory firmware will get rid of FRP?
I typically use Odin to flash firmware, and there's two ways to do it. In the firmware package, you have the BL, AP, CP, CSC, and HOME_CSC files. If you want to dirty flash without wiping user data (including a Samsung account), use the HOME_CSC file in the CSC slot. If however you want to force a data wipe, use the CSC file.
Click to expand...
Click to collapse
Erm... I don't know what an FRP really is, it has been a while since I last do phone rooting and flashing
I am asking because I saw a warning of odin v3.14.4 with the following message
{
"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"
}
sarf2k4 said:
Erm... I don't know what an FRP really is, it has been a while since I last do phone rooting and flashing
I am asking because I saw a warning of odin v3.14.4 with the following message
View attachment 5812713
Click to expand...
Click to collapse
Did you have a Samsung account on the device already?
FRP = Factory Reset Protection. Requires the Google account login information that was previously on the device before factory reset in order to continue setup; this is an anti-theft measure.
Your bootloader has to be unlocked to use Odin.
V0latyle said:
Did you have a Samsung account on the device already?
FRP = Factory Reset Protection. Requires the Google account login information that was previously on the device before factory reset in order to continue setup; this is an anti-theft measure.
Your bootloader has to be unlocked to use Odin.
Click to expand...
Click to collapse
Yeah, you could say get rid of FRP
It has the account of the previous owner (it was given out). The previous owner kept telling me to bring it to a samsung center to reformat/factory reset it because the previous owner forgot his password
By unlocked, did you mean from the developer menu?
sarf2k4 said:
Yeah, you could say get rid of FRP
It has the account of the previous owner (it was given out). The previous owner kept telling me to bring it to a samsung center to reformat/factory reset it because the previous owner forgot his password
By unlocked, did you mean from the developer menu?
Click to expand...
Click to collapse
That's where you start - you enable OEM Unlocking in Developer Options, then you reboot to download mode and unlock the bootloader.
A clear indication of whether the bootloader is unlocked is the "OEM LOCK" line in download mode; if the bootloader is locked it'll say ON, if unlocked it'll say OFF
Are you able to get into the device at all? Is it locked by a password or pattern? If I were you I'd try to get the previous owner to unlock it; it's their responsibility to remove FRP before they sell the device.
V0latyle said:
That's where you start - you enable OEM Unlocking in Developer Options, then you reboot to download mode and unlock the bootloader.
A clear indication of whether the bootloader is unlocked is the "OEM LOCK" line in download mode; if the bootloader is locked it'll say ON, if unlocked it'll say OFF
Are you able to get into the device at all? Is it locked by a password or pattern? If I were you I'd try to get the previous owner to unlock it; it's their responsibility to remove FRP before they sell the device.
Click to expand...
Click to collapse
I don't know how to get into download mode and unlock the bootloader. From what I've read, I need to turn off the phone, press power/bixby? + volup then plug usb? This is the actual part that I somewhat confused because I already have the required file in order to root, twrp, and ketan's rom. Just the instruction wasn't very clear on what exactly what I must do, more below
Yes I'm able to get into the device, it is just that I can't get rid of the samsung account of the previous owner that enforces the FRP from the settings page because the device asks for the password of the previous owner's account in order to remove it
The flashing/rooting instruction were from http://www.mediafire.com/folder/d4ugie4yadxu6/N975F which is:
Section 2
Instructions for users who are on Stock Q/R/S Non rooted/Other ROMS or running trouble like boootloop
- First install stock latest stock S (A12) firmware (recommended same base if available, base info can be found in changelog post on XDA)
- Download ROM N975F_N976B_DrKetanROM_S*.zip and copy to SD card/USB & Check MD5
- Download & Extract N97*_TWRP_*_tar.md5 + Booloader and Modem according your device variant.
- Flash TWRP file with AP tab of Odin
- Again Reboot to Download mode
- Flash Bootloader and Modem
- Reboot to TWRP(DON't REBOOT TO SYSTEM) - Wipe - Format DATA (Full wipe) This will erase all data from your device
- Reboot TWRP - Flash N975F_N976B_DrKetanROM_S*.zip
- Reboot to System
Read Instrcutiona at end "After rebooting to System"
Click to expand...
Click to collapse
The part where I don't get is, "again reboot to download mode" and "reboot to twrp". I read on other thread, I have to untick "auto-reboot" option in odin?
sarf2k4 said:
I don't know how to get into download mode and unlock the bootloader. From what I've read, I need to turn off the phone, press power/bixby? + volup then plug usb?
Click to expand...
Click to collapse
No, don't press power. Just turn phone off, don't connect USB yet, and hold both Volume buttons while plugging in USB cable. It should start with a prompt for download mode, device unlocking, or cancel. Select device unlocking.
sarf2k4 said:
This is the actual part that I somewhat confused because I already have the required file in order to root, twrp, and ketan's rom.
Click to expand...
Click to collapse
What file? What exactly is your end goal here?
sarf2k4 said:
Just the instruction wasn't very clear on what exactly what I must do, more below
Yes I'm able to get into the device, it is just that I can't get rid of the samsung account of the previous owner that enforces the FRP from the settings page because the device asks for the password of the previous owner's account in order to remove it
Click to expand...
Click to collapse
Hmm. Hopefully a clean flash in Odin will do the trick.
sarf2k4 said:
The flashing/rooting instruction were from http://www.mediafire.com/folder/d4ugie4yadxu6/N975F which is:
The part where I don't get is, "again reboot to download mode" and "reboot to twrp". I read on other thread, I have to untick "auto-reboot" option in odin?
Click to expand...
Click to collapse
Yes. The idea here is that after you flash TWRP, you can't let the device boot into system, because if it does, it'll overwrite TWRP with the stock recovery.
But let's just focus on one step at a time; you first need to unlock the bootloader. Use the key combo I described above, and select whatever option mentions device unlocking. Should be a blue warning screen asking if you want to unlock the bootloader (may have an option for Device Unlock mode). Follow the prompt to unlock the bootloader. Once done report back here and we'll go to the next step.
V0latyle said:
No, don't press power. Just turn phone off, don't connect USB yet, and hold both Volume buttons while plugging in USB cable. It should start with a prompt for download mode, device unlocking, or cancel. Select device unlocking.
What file? What exactly is your end goal here?
Hmm. Hopefully a clean flash in Odin will do the trick.
Yes. The idea here is that after you flash TWRP, you can't let the device boot into system, because if it does, it'll overwrite TWRP with the stock recovery.
But let's just focus on one step at a time; you first need to unlock the bootloader. Use the key combo I described above, and select whatever option mentions device unlocking. Should be a blue warning screen asking if you want to unlock the bootloader (may have an option for Device Unlock mode). Follow the prompt to unlock the bootloader. Once done report back here and we'll go to the next step.
Click to expand...
Click to collapse
I followed your instruction, I wasn't sure connect to which, a charger outlet or pc/laptop. I decided to connect to a laptop anyway while holding both volume buttons. As you described, a cyan warning screen appeared, I proceeded by holding volup and another volup again to proceed with unlocking bootloader. It states that the phone will be wiped during the process.
The phone rebooted twice, first one says there's a yellow triangle that the bootloader has been unlocked, it shows the android with "preparing" message. It then rebooted once again and I pressed the power button to proceed when there yellow triangle appeared on this second boot up.
The phone stuck at SAMSUNG text for like about 5 minutes? I thought it got bricked or something so I detached the usb. After a while the phone booted up like a new phone with the first time setup wizard. I skipped everything.
Going into settings, the account of the previous owner is not there anymore, checking software information shows the latest build of N975FXXS8HVJ1, oneui 4.1, android 12
sarf2k4 said:
I followed your instruction, I wasn't sure connect to which, a charger outlet or pc/laptop. I decided to connect to a laptop anyway while holding both volume buttons. As you described, a cyan warning screen appeared, I proceeded by holding volup and another volup again to proceed with unlocking bootloader. It states that the phone will be wiped during the process.
Click to expand...
Click to collapse
Sorry, I should have been more specific.
sarf2k4 said:
The phone rebooted twice, first one says there's a yellow triangle that the bootloader has been unlocked, it shows the android with "preparing" message. It then rebooted once again and I pressed the power button to proceed when there yellow triangle appeared on this second boot up.
The phone stuck at SAMSUNG text for like about 5 minutes? I thought it got bricked or something so I detached the usb. After a while the phone booted up like a new phone with the first time setup wizard. I skipped everything.
Going into settings, the account of the previous owner is not there anymore, checking software information shows the latest build of N975FXXS8HVJ1, oneui 4.1, android 12
Click to expand...
Click to collapse
Alright, success. So what is your end goal here? Are you trying to install a custom ROM? Let me know what you're ultimately trying to accomplish so I can help you with the next steps.
V0latyle said:
Sorry, I should have been more specific.
Alright, success. So what is your end goal here? Are you trying to install a custom ROM? Let me know what you're ultimately trying to accomplish so I can help you with the next steps.
Click to expand...
Click to collapse
Thank you for the help.
I actually came from samsung galaxy note 1, gt-n7000, hard bricked accidentally 2 years ago because of the brickbug present if I'm not careful, but it got me. So I am using a vivo phone for almost a year, for which I can't even flash any firmware let alone running adb commands to grant permission on the phone. It is running android one and it has full locked down in my opinion.
I actually missed the viper4android that I tweaked on my note 1 for a very good sound quality I achieved back then although viper4android wasn't the only reason I wanted to root it. I would like to have adaway at least as well. Perhaps some other 'extra' features that stock can't offer.
I'm not sure how do I put it during the use of this device while still in the previous owner's account is that, when I launched netflix or youtube (respecting the privacy of course), the phone screen became brighter than I would like. Even if it is slightly dimmed, launching one of these app would make it brighter, then go back down to previous brightness when exiting them.
There's already a screen burn-in from excessive youtubing from the previous owner and I can see why, 3 years later this phone has burn-in already because of the app's behavior of 'boosting' the brightness. Not sure if some of the rooted modules 'can' prevent these brightness adjustments by the app or not.
I also never used any banking/financial app on any of my mobile devices
edit:
I often go for stock rom most of the time.
Coming from note 1 that has the potential brick bug during that era especially exynos variants, this note 10+ don't have any potential brick bug do they?
I also tried to restart the phone, I still get that yellow triangle warning saying bootloader has been unlocked and can't be verified, would like to get rid of that as well. Furthermore, I checked the developer menu, "oem unlocking" is now missing
You didn't answer my question, bud. What are you trying to do? What is your goal? For example, are you trying to get a custom ROM installed? Or were you just trying to get the Samsung account removed?
V0latyle said:
You didn't answer my question, bud. What are you trying to do? What is your goal? For example, are you trying to get a custom ROM installed? Or were you just trying to get the Samsung account removed?
Click to expand...
Click to collapse
Sorry if I veered off, yes I would like to have custom rom installed which is to have root in mind. I'm eyeing for drketan's mostly stock rom