Develop Bugs

OEM unlock not showing for the second time, RMM state prenormal again

I have a G960F/DS, I tried to root after the 7 days waiting so when I had the option I enabled OEM unlock, BUT it asked me to do a factory reset so I did, but I didn't know that I should have to enter download mode before rebooting, so now I have OEM lock and FRP on OFF, but I've got the RMM state again in prenormal. I waited again 7 more days but the OEM unlock option is not showing again, what should I do? Wait more time? Do another factory reset? Install again the stock rom?

That's weird. Maybe re-flash stock firmware, wait 7 days. When enabling OEM unlock and it requests to factory reset, once it reboots go straight into download mode and flash TWRP. From there in my experience OEM unlock will always then be there, even when I did re-flash stock ROM at a later date.

InteliDroid said:
That's weird. Maybe re-flash stock firmware, wait 7 days. When enabling OEM unlock and it requests to factory reset, once it reboots go straight into download mode and flash TWRP. From there in my experience OEM unlock will always then be there, even when I did re-flash stock ROM at a later date.
Click to expand...
Click to collapse
Should I flash CSC or HOME CSC?

Legasx said:
I have a G960F/DS, I tried to root after the 7 days waiting so when I had the option I enabled OEM unlock, BUT it asked me to do a factory reset so I did, but I didn't know that I should have to enter download mode before rebooting, so now I have OEM lock and FRP on OFF, but I've got the RMM state again in prenormal. I waited again 7 more days but the OEM unlock option is not showing again, what should I do? Wait more time? Do another factory reset? Install again the stock rom?
Click to expand...
Click to collapse
When you first had the OEM unlock, did you ODIN install TWRP and then flash the NoVerify file immediately after doing the Factory reset. I waited the 7 days, did the above and OEM unlock always shows up now in developer options even after trying other ROMs and just going back to stock rooted setup.

Docmjldds said:
When you first had the OEM unlock, did you ODIN install TWRP and then flash the NoVerify file immediately after doing the Factory reset. I waited the 7 days, did the above and OEM unlock always shows up now in developer options even after trying other ROMs and just going back to stock rooted setup.
Click to expand...
Click to collapse
I know that I should have installed twrp and the fix before rebooting, now I have unlocked bootloader but RMM state is prenormal again.

Legasx said:
Should I flash CSC or HOME CSC?
Click to expand...
Click to collapse
Any ideas?

I'm pretty sure everything I just read there was wrong... W. R. O. N. G.
Firstly.. If you're unlucky enough to have a phone that's going to have the RMM state.. It's a 2 week wait MINIMUM.
When you first get the phone, select the OEM unlock and be prepared for it to reset the phone and reboot... This is NOT OPTIONAL... And at this point if you see the RMM state as PRENORMAL you can forget about flashing twrp or anything else for at least another 7 days.
Anybody that tells you that you should have flashed twrp before you restarted the phone doesn't know what they are talking about.. When you press that OEM unlock button for the first time.. That bloody phone WILL REBOOT, It WILL RESET... There is no way to get to ODIN MODE and even if there was, the RMM state is triggered straight away if you have one of those phone.
I have an S9 that had no RMM state period.. I was able to to flash twrp straight away.
I also have an S9+ where the RMM state was triggered the moment you accept the phones request to restart after selecting the OEM unlock.
Secondly, after you've selected OEM unlock and the phone has reset and restarted, I'd suggest leaving it on for 7 days... Some people say it doesn't matter if you turn it off, but to be safe.. Just wack it on the charger and leave it.
Once the 7 days is up, the OEM option will reappear... Ignore it.
Boot the phone into ODIN MODE and see if the RMM STATE has vanished.
Understand... It's a 14 day wait... Not a 7 day wait.
Wait 7 days from purchase for oem option.
Unlock oem.. Reboot/reset phone.
Wait 7 more days for oem option to reappear.. Ignore it and boot into Odin mode.
Flash TWRP... For the love of God turn off the Auto restart in Odin.
Prepractice the art of restarting the phone into TWRP manually.. If you miss your window of opportunity and it restarts into android one of two things will happen.
Best case scenario.. You have to reflash TWRP.
Worst case scenario.. The RMM state comes back for another 7 days.
To get out of download mode
Hold volume down and power for 7 seconds.
The moment you feel the phone vibrate (a fraction of a second before the Samsung logo appears) boot into TWRP by
Quickly releasing all the buttons then very quickly press the power, up volume and bixby... And you need to do it BEFORE the screen initialises.. If you see the Samsung logo and you haven't got those buttons down.. You've missed it.
Make sure you have all your files ready to go... With this phone being so *****y I had all my files on both the sd card and a usb with OTG.
RMM STATE BYPASS
N96X ROOT FOR OEM ISSUES.
MAGISK (I'm using the Lineage AOSP 16.4 version, it works on Samsung touchwiz)
A selection of firmwares
Flashable modems.
With this phone you have to be prepared.

batfink1 said:
I'm pretty sure everything I just read there was wrong... W. R. O. N. G.
Firstly.. If you're unlucky enough to have a phone that's going to have the RMM state.. It's a 2 week wait MINIMUM.
When you first get the phone, select the OEM unlock and be prepared for it to reset the phone and reboot... This is NOT OPTIONAL... And at this point if you see the RMM state as PRENORMAL you can forget about flashing twrp or anything else for at least another 7 days.
Anybody that tells you that you should have flashed twrp before you restarted the phone doesn't know what they are talking about.. When you press that OEM unlock button for the first time.. That bloody phone WILL REBOOT, It WILL RESET... There is no way to get to ODIN MODE and even if there was, the RMM state is triggered straight away if you have one of those phone.
I have an S9 that had no RMM state period.. I was able to to flash twrp straight away.
I also have an S9+ where the RMM state was triggered the moment you accept the phones request to restart after selecting the OEM unlock.
Secondly, after you've selected OEM unlock and the phone has reset and restarted, I'd suggest leaving it on for 7 days... Some people say it doesn't matter if you turn it off, but to be safe.. Just wack it on the charger and leave it.
Once the 7 days is up, the OEM option will reappear... Ignore it.
Boot the phone into ODIN MODE and see if the RMM STATE has vanished.
Understand... It's a 14 day wait... Not a 7 day wait.
Wait 7 days from purchase for oem option.
Unlock oem.. Reboot/reset phone.
Wait 7 more days for oem option to reappear.. Ignore it and boot into Odin mode.
Flash TWRP... For the love of God turn off the Auto restart in Odin.
Prepractice the art of restarting the phone into TWRP manually.. If you miss your window of opportunity and it restarts into android one of two things will happen.
Best case scenario.. You have to reflash TWRP.
Worst case scenario.. The RMM state comes back for another 7 days.
To get out of download mode
Hold volume down and power for 7 seconds.
The moment you feel the phone vibrate (a fraction of a second before the Samsung logo appears) boot into TWRP by
Quickly releasing all the buttons then very quickly press the power, up volume and bixby... And you need to do it BEFORE the screen initialises.. If you see the Samsung logo and you haven't got those buttons down.. You've missed it.
Make sure you have all your files ready to go... With this phone being so *****y I had all my files on both the sd card and a usb with OTG.
RMM STATE BYPASS
N96X ROOT FOR OEM ISSUES.
MAGISK (I'm using the Lineage AOSP 16.4 version, it works on Samsung touchwiz)
A selection of firmwares
Flashable modems.
With this phone you have to be prepared.
Click to expand...
Click to collapse
I have done that, activated oem unlock, it asked to do a factory reset so I did, got rmm state prenormal again, then waited 7 days again but still no oem unlock switch for the second time, now I've tried the method that involves changing date and checking for new updates without results, now yesterday I've re installed firmware, bl, modem and CSC, factory new, and still no oem switch, still prenormal

Ok, I went through the same thing determined to find a way around the 14 day wait period... That included downloading 9 different Samsung firmwares from Sammobile all different versions from different counties.. It didn't work, and each time I installed a new firmware it reset the 7 day RMM state counter... I lost 3 days trying that on the S9+.
After the first OEM unlock /reboot /reset did you just leave it on, not touch it except to check the uptime in the settings... I know other people said you can turn it off, but I've been through this on an S8+ and s9+ and it definitely worked better just leaving it on and making sure it got charged occasionally.
I can tell you now, installing that new firmware just reset the RMM state back to 7 days.
---------- Post added at 06:15 PM ---------- Previous post was at 06:13 PM ----------
I mean some people cant wait and reboot into ODIN mode to check before the time is up... Did you wait the full 168 hours.

batfink1 said:
Ok, I went through the same thing determined to find a way around the 14 day wait period... That included downloading 9 different Samsung firmwares from Sammobile all different versions from different counties.. It didn't work, and each time I installed a new firmware it reset the 7 day RMM state counter... I lost 3 days trying that on the S9+.
After the first OEM unlock /reboot /reset did you just leave it on, not touch it except to check the uptime in the settings... I know other people said you can turn it off, but I've been through this on an S8+ and s9+ and it definitely worked better just leaving it on and making sure it got charged occasionally.
I can tell you now, installing that new firmware just reset the RMM state back to 7 days.
---------- Post added at 06:15 PM ---------- Previous post was at 06:13 PM ----------
I mean some people cant wait and reboot into ODIN mode to check before the time is up... Did you wait the full 168 hours.
Click to expand...
Click to collapse
The first time, before ticking oem unlock switch, I even turned it off some times and checked download mode to see rmm state, even after that I got the oem unlock switch after 7 days, then I switched it and now I got oem unlocked but rmm state prenormal again, but I have waited 7 days again with no results, yesterday I reinstalled firmware, CSC and everything, guess I need to wait 7 more days without turning it off.
Could it be that I bought my phone from ebay and my service provider and CSC are AFG (Afganistan)? But my phone is unlocked, I use it in Mexico

Legasx said:
The first time, before ticking oem unlock switch, I even turned it off some times and checked download mode to see rmm state, even after that I got the oem unlock switch after 7 days, then I switched it and now I got oem unlocked but rmm state prenormal again, but I have waited 7 days again with no results, yesterday I reinstalled firmware, CSC and everything, guess I need to wait 7 more days without turning it off.
Could it be that I bought my phone from ebay and my service provider and CSC are AFG (Afganistan)? But my phone is unlocked, I use it in Mexico
Click to expand...
Click to collapse
My phone is SAME as yours except I use Tmobile in US. My phone is an S9. Unlocked from a third party Net I purchased from as new and it has the same AFG CSC. I waited exactly 7 days. But installed TRWP immediately by holding Pwr Vol dwn and Bixby from the Format data answer yes etc after seeing the OEM unlock after that 7 days. This was my experience all I can say.

Docmjldds said:
My phone is SAME as yours except I use Tmobile in US. My phone is an S9. Unlocked from a third party Net I purchased from as new and it has the same AFG CSC. I waited exactly 7 days. But installed TRWP immediately by holding Pwr Vol dwn and Bixby from the Format data answer yes etc after seeing the OEM unlock after that 7 days. This was my experience all I can say.
Click to expand...
Click to collapse
So did you not format the data and just reboot into the bootloader after clicking OEM unlock?

jal3223 said:
So did you not format the data and just reboot into the bootloader after clicking OEM unlock?
Click to expand...
Click to collapse
When you toggle OEM unlock it will ask to reboot. At that point power down the phone, DO NOT REBOOT IT. Then hold volume down, bixby and power to get into the bootloader. Once there, you will see your RMM state is NORMAL. Now confirm by pressing volume up or whatever it was and you will be able to flash TWRP with ODIN.
This is where it gets tricky. Once the flash is complete the phone will reboot. You will need to hold volume up, bixby, and power for about 5 seconds to boot directly into TWRP. Once there you will need to wipe, then reboot recovery and flash no-verity, then reboot and flash RMM fix.
If you don't follow above, and the phone reboots you are screwed into waiting another 7 days if your lucky, otherwise you will need to flash stock firmware again and the whole process starts over.

shiftr182 said:
When you toggle OEM unlock it will ask to reboot. At that point power down the phone, DO NOT REBOOT IT. Then hold volume down, bixby and power to get into the bootloader. Once there, you will see your RMM state is NORMAL. Now confirm by pressing volume up or whatever it was and you will be able to flash TWRP with ODIN.
This is where it gets tricky. Once the flash is complete the phone will reboot. You will need to hold volume up, bixby, and power for about 5 seconds to boot directly into TWRP. Once there you will need to wipe, then reboot recovery and flash no-verity, then reboot and flash RMM fix.
If you don't follow above, and the phone reboots you are screwed into waiting another 7 days if your lucky, otherwise you will need to flash stock firmware again and the whole process starts over.
Click to expand...
Click to collapse
This has got to be the most concise write up of the situation. Thank you for clearing it up!

I've been RMM Prenormal with OEM unlocked for about 10 days now; no new firmware or wipes or anything, just waiting it out. I have no idea when it will be back to Normal; should I wipe it to reset the counter to wait the 7 full days anew, or should I just continue to wait, checking the recovery every day until it is Normal?

There is only one thing I can say... THANKS a lot, Samsung... This was my last SAMSUNG phone !

batfink1 said:
I'm pretty sure everything I just read there was wrong... W. R. O. N. G.
Firstly.. If you're unlucky enough to have a phone that's going to have the RMM state.. It's a 2 week wait MINIMUM.
When you first get the phone, select the OEM unlock and be prepared for it to reset the phone and reboot... This is NOT OPTIONAL... And at this point if you see the RMM state as PRENORMAL you can forget about flashing twrp or anything else for at least another 7 days.
Anybody that tells you that you should have flashed twrp before you restarted the phone doesn't know what they are talking about.. When you press that OEM unlock button for the first time.. That bloody phone WILL REBOOT, It WILL RESET... There is no way to get to ODIN MODE and even if there was, the RMM state is triggered straight away if you have one of those phone.
I have an S9 that had no RMM state period.. I was able to to flash twrp straight away.
I also have an S9+ where the RMM state was triggered the moment you accept the phones request to restart after selecting the OEM unlock.
Secondly, after you've selected OEM unlock and the phone has reset and restarted, I'd suggest leaving it on for 7 days... Some people say it doesn't matter if you turn it off, but to be safe.. Just wack it on the charger and leave it.
Once the 7 days is up, the OEM option will reappear... Ignore it.
Boot the phone into ODIN MODE and see if the RMM STATE has vanished.
Understand... It's a 14 day wait... Not a 7 day wait.
Wait 7 days from purchase for oem option.
Unlock oem.. Reboot/reset phone.
Wait 7 more days for oem option to reappear.. Ignore it and boot into Odin mode.
Flash TWRP... For the love of God turn off the Auto restart in Odin.
Prepractice the art of restarting the phone into TWRP manually.. If you miss your window of opportunity and it restarts into android one of two things will happen.
Best case scenario.. You have to reflash TWRP.
Worst case scenario.. The RMM state comes back for another 7 days.
To get out of download mode
Hold volume down and power for 7 seconds.
The moment you feel the phone vibrate (a fraction of a second before the Samsung logo appears) boot into TWRP by
Quickly releasing all the buttons then very quickly press the power, up volume and bixby... And you need to do it BEFORE the screen initialises.. If you see the Samsung logo and you haven't got those buttons down.. You've missed it.
Make sure you have all your files ready to go... With this phone being so *****y I had all my files on both the sd card and a usb with OTG.
RMM STATE BYPASS
N96X ROOT FOR OEM ISSUES.
MAGISK (I'm using the Lineage AOSP 16.4 version, it works on Samsung touchwiz)
A selection of firmwares
Flashable modems.
With this phone you have to be prepared.
Click to expand...
Click to collapse
I face the same problem. 7 days are not sufficient on my phone. Have been waiting 169 hors and do NOT see the OEM unlock at all. So will have to wait 7 more days... I doubt it will then appear
Then I have to reboot to odin-mode, see the RMM state and reboot and wait againe 7 (or maybe 14 ??) days ???
GREAT feature from Samsung...
If it is not possible to root the phone, I will sell it and never again buy anything from Samsung..

after the 7 days or 168 hrs, just reboot and check again on dev settings. That worked for me.

Two oposing instructions
1st.
shiftr182 said:
When you toggle OEM unlock it will ask to reboot. At that point power down the phone, DO NOT REBOOT IT.
Click to expand...
Click to collapse
2nd.
batfink1 said:
select the OEM unlock and be prepared for it to reset the phone and reboot... This is NOT OPTIONAL.
Click to expand...
Click to collapse
Could somebody clarify?

Sure, I'll clarify in about 1 week when my Note 9 512 gig phone arrives.
I'll try his way first, however what I stated about being ready is vitally important.
Make sure you have everything you need on an SDCARD AND on a USB stick if you have an OTG adapter.
You can't put any of it internally on the phone because to remove the encryption you need to wipe the internal storage completely.
So make sure you have
no-verity-opt-encrypt-6.0-star.zip
RMM STATE BYPASS
A selection of custom firmwares.. Alexandr's excellent devbased roms have RMM STATE BYPASS built in, they also have Xposed built in by renaming the rom slightly such as N960Fxxx_DevBase_v6.x_xposed.zip
Will install Xposed framework.
Renaming the rom as N960Fxxx_DevBase_v6.x_noroot.zip
Will install the rom without root or Magisk being installed.
I use his rom on both an S9 and an S9+ and they work perfectly.
So read and read and read, and when you've collected everything you need on two different media.... READ SOME MORE.
I'll update this thread when I try out shiftr182 method.
Most importantly, before you do anything.. Practice booting into recovery and Odin mode till you get it down pat.. You really only get one go at it.
Now mind you, I'm really cavalier, I'm a computer technician and I can't sit around wringing my hands together worrying about what's going to happen or I'll never get anything done, so to do this you do your homework, lots of homework and then you take your balls in your hand and do it and accept that if it all goes arse up... Well you tried.
It's actually pretty hard to totally brick these phones.. It just means more waiting, more reading and more asking questions.
I hope this has not only qualmed (not the urban dictionary meaning) your fears but also put the fear of God in you.
DO YOUR RESEARCH :angel:

Google Pixel 3XL fastboot locked and Recovery not working

Hello guys, I just got a Pixel 3XL from somebody and I thought I could make it to work, but now I'm stucked. The phone is stucked in fastboot and the bootloader is LOCKED. I tried to unlock it using GUIDE for Google Pixel 3 XL unlock bootloader, but I cannot do this task 100% because I cannot enable OEM unlock and USB debugging since the phone is stucked in fastbood mode. Also, if I try to get into recovery mode, when I press the power button to get into recovery, the phone turns off. I ust want to make it stock.
Any idea how to solve this? Thank you

try sideloading the full OTA.
https://developers.google.com/android/ota

robertoancini51 said:
Hello guys, I just got a Pixel 3XL from somebody and I thought I could make it to work, but now I'm stucked. The phone is stucked in fastboot and the bootloader is LOCKED. I tried to unlock it using GUIDE for Google Pixel 3 XL unlock bootloader, but I cannot do this task 100% because I cannot enable OEM unlock and USB debugging since the phone is stucked in fastbood mode. Also, if I try to get into recovery mode, when I press the power button to get into recovery, the phone turns off. I ust want to make it stock.
Any idea how to solve this? Thank you
Click to expand...
Click to collapse
The answer is the same as in your other thread. If you cannot get into recovery mode and your bootloader is locked there is nothing you can do. The mystery is how you lost recovery with a locked bootloader... it may have been unlocked at one time and someone re-locked it?

v12xke said:
The answer is the same as in your other thread. If you cannot get into recovery mode and your bootloader is locked there is nothing you can do. The mystery is how you lost recovery with a locked bootloader... it may have been unlocked at one time and someone re-locked it?
Click to expand...
Click to collapse
that's the mistery. so I cannot do nothing with the phone? Is no any solution to put the recovery mode back into the phone to work?

robertoancini51 said:
that's the mistery. so I cannot do nothing with the phone? Is no any solution to put the recovery mode back into the phone to work?
Click to expand...
Click to collapse
Not if you can't fastboot the boot.img there isn't. Like the others said, if you can't get into stock recovery to side load the OTA, your kinda hosed.

robertoancini51 said:
that's the mistery. so I cannot do nothing with the phone? Is no any solution to put the recovery mode back into the phone to work?
Click to expand...
Click to collapse
No, nothing you can do because you cannot fastboot flash any partition when the bootloader is locked, and without a working recovery you cannot use adb to sideload an OTA. My guess is your friend at one time had the bootloader unlocked but he later locked it back before giving it to you. Once the bootloader is unlocked it should never be locked again... unless you know exactly what you are doing and have good reason to do so. If you have tried multiple times to unlock the bootloader using fastboot -and- exhausted all means of booting to recovery (you are positive you know how to get there and cannot) then there is no way to recover. Until one of these two things changes you cannot get back in. Sorry man!

Badger50 said:
Not if you can't fastboot the boot.img there isn't. Like the others said, if you can't get into stock recovery to side load the OTA, your kinda hosed.
Click to expand...
Click to collapse
ok, thank you

v12xke said:
No, nothing you can do because you cannot fastboot flash any partition when the bootloader is locked, and without a working recovery you cannot use adb to sideload an OTA. My guess is your friend at one time had the bootloader unlocked but he later locked it back before giving it to you. Once the bootloader is unlocked it should never be locked again... unless you know exactly what you are doing and have good reason to do so. If you have tried multiple times to unlock the bootloader using fastboot -and- exhausted all means of booting to recovery (you are positive you know how to get there and cannot) then there is no way to recover. Until one of these two things changes you cannot get back in. Sorry man!
Click to expand...
Click to collapse
I just cannot believe that the phone is unusable

robertoancini51 said:
I just cannot believe that the phone is unusable
Click to expand...
Click to collapse
Just to be sure I am reading this right, instead of seeing the "no command" screen when you toggle the smart menu option to recovery and hitting the power button, the device shuts down?

sliding_billy said:
Just to be sure I am reading this right, instead of seeing the "no command" screen when you toggle the smart menu option to recovery and hitting the power button, the device shuts down?
Click to expand...
Click to collapse
Yes

robertoancini51 said:
Yes
Click to expand...
Click to collapse
You mention not being able to toggle OEM unlock or USB debugging, but are you sure they are not already toggle? Have you tried locking or unlocking the bootloader from fastboot (hopefully you can see the device on your computer when plugged in)? Your issue reminded me of another thread https://forum.xda-developers.com/showpost.php?p=78277194&postcount=260 where it looked like an unlock only partially worked. I assume you are not the registered owner and cannot contact Google about the issue.

sliding_billy said:
You mention not being able to toggle OEM unlock or USB debugging, but are you sure they are not already toggle? Have you tried locking or unlocking the bootloader from fastboot (hopefully you can see the device on your computer when plugged in)? Your issue reminded me of another thread https://forum.xda-developers.com/showpost.php?p=78277194&postcount=260 where it looked like an unlock only partially worked. I assume you are not the registered owner and cannot contact Google about the issue.
Click to expand...
Click to collapse
I'm not sure if they are already toggle. Yes, I've tried to lock/unlock bootloader from fastboot, but nothing. The PC sees it from device manager. No,I'm not registered.

robertoancini51 said:
I'm not sure if they are already toggle. Yes, I've tried to lock/unlock bootloader from fastboot, but nothing. The PC sees it from device manager. No,I'm not registered.
Click to expand...
Click to collapse
Might be worth posting something on the Google forum. If an agent isn't checking registration, you might get some ideas. The only thing else I can think is that there may be some key combination (vol down or up and hold) when pressing the power button to get to recovery to keep it from shutting down. Good luck.

sliding_billy said:
Might be worth posting something on the Google forum. If an agent isn't checking registration, you might get some ideas. The only thing else I can think is that there may be some key combination (vol down or up and hold) when pressing the power button to get to recovery to keep it from shutting down. Good luck.
Click to expand...
Click to collapse
I Have written to ghem, I wait an answer from them. I will try some combination and come back with an answer

i have the same problem
robertoancini51 said:
I Have written to ghem, I wait an answer from them. I will try some combination and come back with an answer
Click to expand...
Click to collapse
who did you write to? can you share please? also if you manage to solve the problem, please share the solution.
many thanks,

Cant you take the back of and use EDL Mode? its qualcomm so its available.? wheres all the master techys in the pixel thread?You can push the entire factory image whether its locked or unlocked with EDL.
---------- Post added at 04:56 PM ---------- Previous post was at 04:50 PM ----------
https://www.leakite.com/revised-how-to-unbrick-qualcomm-android/
Remember to change any images to googles.

Bootloop (?) dm-verity corruption

So my phone is stuck on this issue. I haven't done anything wrong. My phone was just peacefully charging then the phone switches off by itself then the bootloop happened.
This showed on the screen:
dm-verity corruption
your device is corrupt.
it can't be trusted and my not work properly.
press enter button to continue.
Or, device will power off in 5s.
(written in white)
Although it does turn off by itself if I ignore it, after I turn it on again and press enter or power button it boot until lockscreen and if I try to do something like unlocking, scrolling down notifs bar, and sliding through different page on home screen it will turn off again. It seem like it's crashing. The thing is I am not trying to root or flash something. I haven't done anything on my phone. I only have one phone and I badly need your help. I hope wiping or reformatting the phone is my last resort. My phone is updated to Android 11 and lateset MIUI (provided by the system itself and not downloaded somewhere). Thank you.

Well seems like something is corrupt.
It reboots when you touches the screen(or do anything)?

LR7875 said:
It reboots when you touches the screen(or do anything)?
Click to expand...
Click to collapse
It's more like it turns itself off again and if I try to press again power button if the problem show again, same thing happen. Sometimes MIUI logo appears and shuts down again it can't even go to lock screen.

Is there any chance you can unlock it?
It seems like your internal storage is corrupted.

LR7875 said:
Is there any chance you can unlock it?
It seems like your internal storage is corrupted.
Click to expand...
Click to collapse
At some point I did manage to unlock it but it happened only once and when I tried to open the notifs by scrolling down or tried to different part of homescreen it just shuts down. After that, it can't even go to the lockscreen after reboot. It's a never ending cycle. I can go to fastboot mode but I don't know if I can do miracle with that.

Well immediately plug into a computer and pull photos amd videos from it if you get it unlocked.

LR7875 said:
Well immediately plug into a computer and pull photos amd videos from it if you get it unlocked.
Click to expand...
Click to collapse
I reformatted it hoping that it will fix the problem. I was wrong. *sigh*

hyung_z said:
I reformatted it hoping that it will fix the problem. I was wrong. *sigh*
Click to expand...
Click to collapse
Well most likely your EMMC internal storage chip went bad R.I.P. (well maybe you sending those emojis will be more appropriate, but, oh well)
Maybe search more on google, I can't help you more

LR7875 said:
Well most likely your EMMC internal storage chip went bad R.I.P. (well maybe you sending those emojis will be more appropriate, but, oh well)
Maybe search more on google, I can't help you more
Click to expand...
Click to collapse
Do you think service center can help me with this or they'll probably just say to replace the phone if a bad chip is the case?

Maybe they will replace the motherboard with some fee. Or they will try to convince you to buy a new fancy phone just purely because xiaomi could earn more.
Thats all about luck (and problem is on xiaomi side, not your fault)

what's the smartphone model?

Redmi note 8 pro is the OP's phone.
Wait Wait just found some interesting lead.
Xiaomi needs a better way to unbrick its devices instead of Authorized Mi Accounts
Xiaomi has locked down the EDL mode on all of its devices, making it nigh impossible to unbrick a device without an Authorized Mi Account. Read on for more!
www.xda-developers.com
Patched SP flash tool!

heh, i have the same phone. reflash yours with the firmware that was on it before everything that happened. but don't flash userdata if you want your data on it
flashing it is simple process

LR7875 said:
Redmi note 8 pro is the OP's phone.
Wait Wait just found some interesting lead.
Xiaomi needs a better way to unbrick its devices instead of Authorized Mi Accounts
Xiaomi has locked down the EDL mode on all of its devices, making it nigh impossible to unbrick a device without an Authorized Mi Account. Read on for more!
www.xda-developers.com
Patched SP flash tool!
Click to expand...
Click to collapse
there is already a way to flash it with SPFT without authorization
also he must try to flash it in fastboot because it's not bricked

AsyJAIZ said:
there is already a way to flash it with SPFT without authorization
also he must try to flash it in fastboot because it's not bricked
Click to expand...
Click to collapse
He probably doesn't have his bootloader unlocked.
Fastboot OEM unlock wont work as oem unlock is probably not enabled in settings dev options.

LR7875 said:
He probably doesn't have his bootloader unlocked.
Fastboot OEM unlock wont work as oem unlock is probably not enabled in settings dev options.
Click to expand...
Click to collapse
ok i got it, then he should somehow put it in download mode...

Do you guys think I need to go to the service center because I don't know what to do. I really don't want to brick my phone. But a while ago my phone booted. I set it up just like buying a new phone but after I finished setting up, I just wait for the phone to catch up because I was afraid the phone will just shut down suddenly. And then, it happened again the phone shut downs without me doing anything. Now I tried to boot it up again but it is currently stuck at Redmi logo (plus "powered by android" at the bottom").

hyung_z said:
Do you guys think I need to go to the service center because I don't know what to do. I really don't want to brick my phone. But a while ago my phone booted. I set it up just like buying a new phone but after I finished setting up, I just wait for the phone to catch up because I was afraid the phone will just shut down suddenly. And then, it happened again the phone shut downs without me doing anything. Now I tried to boot it up again but it is currently stuck at Redmi logo (plus "powered by android" at the bottom").
Click to expand...
Click to collapse
SPFT enables when phone is a brick, so there's no need in service center.
they will flash it like we are going to do

Help, does anyone know how to fix dm-verity corruption? I was using my tab normally, then it suddenly shuts down and this error keeps popping up whenever my device boots. It goes on a loop unless I press the power button again.

deleted

Question Unlocked Pixel 6 Pro - "Your Device is corrupted and cannot be trusted" error after trying to manually flash Dec 2021 factory image

I got impatient and decided to flash the Dec 2021 US Carrier factory image on my unlocked Pixel 6 Pro.
I set my device to OEM unlocking, grabbed the latest ABD/Fastboot files from Google, went into the bootloader and unlocked it w/ "fastboot flashing unlock", and then proceeded to flash my device. However, I now get a "Your device is corrupt. It can't be trusted and may not work properly" error w/ a red triangle exclamation mark upon boot. I can click the power button to get past it and the device will appear to boot, but it stays stuck on the Google screen w/ white background.
I'm able to manually restart into fastboot and fastboot devices recognizes the device.
I've flashed all my previous Pixel's many times before and never came across this error. Any ideas?

Deleted

You're going to have to use the Android flash tool now. Just follow the link in the Google factory image site. You'll be able to get back to December at the very end. It'll tell you to relock your bootloader Don't do it if you don't want to.
lil_michelle said:
Did you flash disable dm verity first after unlocking the bootloader before flashing a patched system image?
Click to expand...
Click to collapse

mac796 said:
You're going to have to use the Android flash tool now. Just follow the link in the Google factory image site. You'll be able to get back to December at the very end. It'll tell you to relock your bootloader Don't do it if you don't want to.
Click to expand...
Click to collapse
thank you! Using the Android Flash Tool resolved my issue.

I did this exact same thing, unlocked device, and flash-all.bat the December update, except my device was a hard brick. I could get zero response from the device, no matter how long I would hold in the power button. Connecting to computer would chime connected, then disconnect a second later. After the flash-all.bat command, it finished successfully, the phone rebooted to a screen that said software was corrupt and would not boot. Pressed power to move passed it and phone went black forever. Had 98% battery too. Had to send back to google for replacement. Did I miss something, or was it just the super buggy December update that did it. I am now scared to death to root this phone again fearing that I did something wrong, and that it will do this again. Is fastboot flashing the factory image a bad thing now, did I miss something, or was it just some weird glitch?

summitfox said:
I did this exact same thing, unlocked device, and flash-all.bat the December update, except my device was a hard brick. I could get zero response from the device, no matter how long I would hold in the power button. Connecting to computer would chime connected, then disconnect a second later. After the flash-all.bat command, it finished successfully, the phone rebooted to a screen that said software was corrupt and would not boot. Pressed power to move passed it and phone went black forever. Had 98% battery too. Had to send back to google for replacement. Did I miss something, or was it just the super buggy December update that did it. I am now scared to death to root this phone again fearing that I did something wrong, and that it will do this again. Is fastboot flashing the factory image a bad thing now, did I miss something, or was it just some weird glitch?
Click to expand...
Click to collapse
Hard to say, for those of us who haven't had any problems...yet. I've flashed the full factory image at least twice so far.
Normally, the USB cable and to a lesser extent, the USB port used on the computer, would be my first suspects as to the problem, but since you said it finished successfully, I have no clue.

Do I need to disable dm verity at least once, or is that just completely obsolete now.

summitfox said:
Do I need to disable dm verity at least once, or is that just completely obsolete now.
Click to expand...
Click to collapse
When using Magisk 23016 for rooting it is not necessary at all.

summitfox said:
Do I need to disable dm verity at least once, or is that just completely obsolete now.
Click to expand...
Click to collapse
The *only* time you *might* still need to disable verity and verification are for some custom kernels - until those kernels are updated the same way Magisk Canary 23016 was, and then they won't need it. If you're not planning on using custom kernels, and just rooting the stock kernel instead, then there's no reason to disable them anymore.

tuffCookie said:
I got impatient and decided to flash the Dec 2021 US Carrier factory image on my unlocked Pixel 6 Pro.
I set my device to OEM unlocking, grabbed the latest ABD/Fastboot files from Google, went into the bootloader and unlocked it w/ "fastboot flashing unlock", and then proceeded to flash my device. However, I now get a "Your device is corrupt. It can't be trusted and may not work properly" error w/ a red triangle exclamation mark upon boot. I can click the power button to get past it and the device will appear to boot, but it stays stuck on the Google screen w/ white background.
I'm able to manually restart into fastboot and fastboot devices recognizes the device.
I've flashed all my previous Pixel's many times before and never came across this error. Any ideas?
Click to expand...
Click to collapse
summitfox said:
I did this exact same thing, unlocked device, and flash-all.bat the December update, except my device was a hard brick. I could get zero response from the device, no matter how long I would hold in the power button. Connecting to computer would chime connected, then disconnect a second later. After the flash-all.bat command, it finished successfully, the phone rebooted to a screen that said software was corrupt and would not boot. Pressed power to move passed it and phone went black forever. Had 98% battery too. Had to send back to google for replacement. Did I miss something, or was it just the super buggy December update that did it. I am now scared to death to root this phone again fearing that I did something wrong, and that it will do this again. Is fastboot flashing the factory image a bad thing now, did I miss something, or was it just some weird glitch?
Click to expand...
Click to collapse
Did either of you verify the hash of the download before flashing?
Before flashing any image, the hash should always be verified as it ensures the file is secure and not corrupted.

JW09I4 said:
Before flashing any image, the hash should always be verified as it ensures the file is secure and not corrupted.
Click to expand...
Click to collapse
^ This. For years now, I've just gotten used to verifying the hash of every important thing that I download that has the hash value made available. Saves a lot of hassle later on since if the downloaded file is corrupted just slightly, everything will go wrong down the road in the process.
I also check for new Platform Tools and Google's USB driver each and every time I flash a new update. It's just habit and again, saves a lot of trouble.

To add on the previously said:
Windows has a built-in hash checker, you just need to open CMD and type
Get-FileHash <Drag'n'Drop'le'File'here>
Click to expand...
Click to collapse
Then just copy the hash (strg+c) into your browser search window where you downloaded the OTA/firmware (strg f to open search, strg v to paste) and if you get a match (1/1), the hash checks out.
It's easy, it's fast, it's reliable. It will only cost you a few seconds. No hassle involved.

Morgrain said:
Windows has a built-in hash checker, you just need to open CMD and type
Click to expand...
Click to collapse
For anyone who doesn't know, this is referencing Windows' built-in PowerShell. It may be the default these days as Microsoft pushes it and it's more capable than Command Prompt, but you can still open CMD and the "Get-FileHash" won't be available there.

Morgrain said:
To add on the previously said:
Windows has a built-in hash checker, you just need to open CMD... Then just copy the hash (strg+c) into your browser search window where you downloaded the OTA/firmware (strg f to open search, strg v to paste) and if you get a match (1/1), the hash checks out.
Click to expand...
Click to collapse
roirraW edor ehT said:
For anyone who doesn't know, this is referencing Windows' built-in PowerShell. It may be the default these days as Microsoft pushes it and it's more capable than Command Prompt, but you can still open CMD and the "Get-FileHash" won't be available there.
Click to expand...
Click to collapse
It's often better to use a program that will compare the hashes, else a SHA256 or SHA512 hash becomes tedious to manually compare - I'm partial to QuickHash [GitHub] due to its broad functionality (drag and drop file for it to auto-compute hash and you can paste what the hash should be either before or after)

For quick one or two-file comparisons, I prefer Implebits' HashTab, which adds a new configurable tab to the file properties dialog in Windows. I originally got turned onto the program when it was Beeblebrox.org, which being a Douglas Adams fan definitely got my attention back then but I stuck with it after they sold it.
Edit: I see Implebits is going out of business and HashTab will go to GitHub and be open source, so exciting times!
Implbits Software, LLC is going out of business
We will soon release Hashtab as an Open Source project on Github. Until we do... you can download the last build of Hashtab that we made using the link below:
Click to expand...
Click to collapse

Actually the same situation here. What's the version of your adb tool. Do I have to use the web tool to flash in the future? Could I use adb with flash.bat as always？

mac796 said:
You're going to have to use the Android flash tool now. Just follow the link in the Google factory image site. You'll be able to get back to December at the very end. It'll tell you to relock your bootloader Don't do it if you don't want to.
Click to expand...
Click to collapse
That's what I had to do and agree to relock bootloader

Joynaruto said:
Actually the same situation here. What's the version of your adb tool. Do I have to use the web tool to flash in the future? Could I use adb with flash.bat as always？
Click to expand...
Click to collapse
Tried that with no joy as future idk. My situation was different after flashing Los the recovery was overwritten and flashing stock said something about timestamp error

summitfox said:
I did this exact same thing, unlocked device, and flash-all.bat the December update, except my device was a hard brick. I could get zero response from the device, no matter how long I would hold in the power button. Connecting to computer would chime connected, then disconnect a second later. After the flash-all.bat command, it finished successfully, the phone rebooted to a screen that said software was corrupt and would not boot. Pressed power to move passed it and phone went black forever. Had 98% battery too. Had to send back to google for replacement. Did I miss something, or was it just the super buggy December update that did it. I am now scared to death to root this phone again fearing that I did something wrong, and that it will do this again. Is fastboot flashing the factory image a bad thing now, did I miss something, or was it just some weird glitch?
Click to expand...
Click to collapse
I think you should of used the full image not the update with flashall.bat

tuffCookie said:
I got impatient and decided to flash the Dec 2021 US Carrier factory image on my unlocked Pixel 6 Pro.
I set my device to OEM unlocking, grabbed the latest ABD/Fastboot files from Google, went into the bootloader and unlocked it w/ "fastboot flashing unlock", and then proceeded to flash my device. However, I now get a "Your device is corrupt. It can't be trusted and may not work properly" error w/ a red triangle exclamation mark upon boot. I can click the power button to get past it and the device will appear to boot, but it stays stuck on the Google screen w/ white background.
I'm able to manually restart into fastboot and fastboot devices recognizes the device.
I've flashed all my previous Pixel's many times before and never came across this error. Any ideas?
Click to expand...
Click to collapse
I had this before as well after manually flashing the November update. Got the device cannot be trusted. Rebooted, flashed again, and device completely fried. Wouldn't turn on, not recognized by computer, nothing. Complete brick. Suspect system board fried. I'll never try to manually flash an update with a Google device again. Hopefully it ends better for you.

Flashing firmware while samsung account still present?

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