Develop Bugs

Samsung i780 cannot remove the PIN lock!

Hi all,
One of the users in our company has locked himself out of his i780 by forgetting the 4-digit PIN he set on the device (not the SIM PIN).
The problem I have is that it is running one of the older ROM's that did not have the hard reset button combination on it so I cannot reset it at all. It also won't enter bootloader mode using the usual combination (although this may be because of the countdown timer on the device not accepting input).
Anyone got any ideas on what I can do next?
Thanks.

dcuk7 said:
Hi all,
One of the users in our company has locked himself out of his i780 by forgetting the 4-digit PIN he set on the device (not the SIM PIN).
The problem I have is that it is running one of the older ROM's that did not have the hard reset button combination on it so I cannot reset it at all. It also won't enter bootloader mode using the usual combination (although this may be because of the countdown timer on the device not accepting input).
Anyone got any ideas on what I can do next?
Thanks.
Click to expand...
Click to collapse
I wonder if you can short certain pins on the flash chip to destroy the checksum and thus cause the device to reset itself - this method was used in the LinkSys WRT54G router and some MP3 players..

did you try reflashing the phone with new firmware? might help since the pin is set on operating system level (afaik), the firmware upgrade is done on bootloader level.

bazzix said:
did you try reflashing the phone with new firmware? might help since the pin is set on operating system level (afaik), the firmware upgrade is done on bootloader level.
Click to expand...
Click to collapse
But he can't get into the loader mode, so Mirage is a no-go.. I suppose the phone doesent even connect to ActiveSync, hm? If it would then the official HL1/2 updaters are able to reset the phone into the loader mode and flash it

Correct, I cannot get it into bootloader mode because the usual key combo does not work and activesync refuses to recognise the phone until the PIN is entered so I cannot use Mirage or the official updaters!
Looks like I'll have to send it off to Samsung!
Cheers guys.

try contacting them first by phone and see if they can't help out. otherwise you'll have to wait for a looong time

Yeah, I've sent phones to them before, they do take a while.
They say they need them back to take the lock off so looks like it'll take a while!
Moral of this story: Don't forget that damn PIN!

dcuk7 said:
Yeah, I've sent phones to them before, they do take a while.
They say they need them back to take the lock off so looks like it'll take a while!
Moral of this story: Don't forget that damn PIN!
Click to expand...
Click to collapse
Doesn't it wipe itself after the 50th attempt?
How old is that version? before Nov2007? Can you post the version number? something like "i780XXHA4"

dcuk7 said:
Hi all,
One of the users in our company has locked himself out of his i780 by forgetting the 4-digit PIN he set on the device (not the SIM PIN).
The problem I have is that it is running one of the older ROM's that did not have the hard reset button combination on it so I cannot reset it at all. It also won't enter bootloader mode using the usual combination (although this may be because of the countdown timer on the device not accepting input).
Anyone got any ideas on what I can do next?
Thanks.
Click to expand...
Click to collapse
By Omnia this ok
1. type *7465625*638*# to set
2. type your MCC/MNC code (list here: http://en.wikipedia.org/wiki/Mobile_Network_Code), e.g.26003 for Polish ORANGE
3. type your new NCK (12345678), then OK
3. type *#7465625 to check your lock
4. type #7465625*638*# and type your NCK (12345678)
5. enjoy.

[Q] Nexus 7 Bricked due to 4.4.3 Update?

I'm hoping someone might be able to help me recover my Nexus 7 which appears to be bricked currently. It is the 2013 version, and it was never rooted initially and was running stock firmware. (By the way, I'm not the most proficient with messing with my Android devices or even with the terminology, so I apologize in advance if I might require clarification on some of the responses).
A few days ago, I woke up to discover that somehow my home screen had reverted back to the way it was upon initially getting the device. This wasn't a big deal since I didn't lose any data or apps, but I figured something might be wrong and even posted about it on Google's product forums. Then, last night, I attempted to update to 4.4.3 because it had been prompting me to do so for a week or two. It downloaded and attempted the update, but it failed. It then eventually restarted, but upon loading up Android I got an error message that stated:
System UID's Inconsistent
UIDs on the system are inconsistent, you need to wipe your data partition or your device will be unstable
with a button to click that says "I'm Feeling Lucky" - I clicked the button figuring I could at least get back in to back up my data, but after about 30 seconds the device just rebooted again (all I managed to do was accidentally click the Chrome icon) and now it is just stuck at the initial boot-up screen displaying the Google text logo.
I have tried to hold down the volume button and hit power, and I get to a screen with 4 options I can cycle through: Recovery mode (which will just put me back the Google text logo), Power off (which turns off the device), Start (which puts me back to the Google text logo), and Restart bootloader (which brings me right back to this menu options page). I'm attaching a screenshot of this page.
I spent about an hour on the phone with Google support, but they were basically useless. I then did some research and downloaded Skipsoft Unified Android Toolkit and was able to get the device to be recognized when it was in that 4-option mode by the Skipsoft Toolkit. However, all fastboot options I tried didn't seem to succeed because the Bootloader was locked. I figured I would try to unlock it, and it told me that in doing so it would wipe my device (so be it I figured since I had already pretty much kissed my data on there goodbye at this point). However, it seems to try and wipe it (even giving me a prompt on the actual Nexus 7), but then just sits and does nothing that I can see (see attached screenshots).
Anyone have any ideas/suggestions? Thanks so much!

To be safe, with a stock device that was not rooted... I would go ahead and use the Skipsoft program to flash the stock image back on the device. This should alleviate any future issues with the OS on your device.
I believe it to be Option #9 on Skipsoft.

xbi0s said:
To be safe, with a stock device that was not rooted... I would go ahead and use the Skipsoft program to flash the stock image back on the device. This should alleviate any future issues with the OS on your device.
I believe it to be Option #9 on Skipsoft.
Click to expand...
Click to collapse
Thanks for the reply - I attempted your suggestion, but it didn't work because the Bootloader is still locked; and attempting to unlock the Bootloader seems to stall on erasing userdata.
Any other thoughts? Thanks!

Anyone else have any suggestions/ideas? Thanks!

mbressman said:
Anyone else have any suggestions/ideas? Thanks!
Click to expand...
Click to collapse
Download ADB from my signature.
Put the device in bootloader mode (power+vol down), open fastboot.exe and type fastboot oem unlock.

Aerowinder said:
Download ADB from my signature.
Put the device in bootloader mode (power+vol down), open fastboot.exe and type fastboot oem unlock.
Click to expand...
Click to collapse
When I try that, I get:
Code:
C:\Users\User\Desktop\ADB & Fastboot API 19 (19.0.1)>fastboot oem unlock
...
(bootloader) Unlocking bootloader...
(bootloader) erasing userdata...
And it just hangs there....
The Nexus 7 did prompt me whether I want to unlock the bootloader and I selected yes (with the volume and power keys), but then it just hangs at that selection screen as well...
Any ideas??
Thanks!

mbressman said:
When I try that, I get:
Code:
C:\Users\User\Desktop\ADB & Fastboot API 19 (19.0.1)>fastboot oem unlock
...
(bootloader) Unlocking bootloader...
(bootloader) erasing userdata...
And it just hangs there....
The Nexus 7 did prompt me whether I want to unlock the bootloader and I selected yes (with the volume and power keys), but then it just hangs at that selection screen as well...
Any ideas??
Thanks!
Click to expand...
Click to collapse
I changed the wrong link in my signature. The ADB link correctly points to version 19.0.2 now. Try that one. Try a different cable if you have one, try a different USB port if you can.

Aerowinder said:
I changed the wrong link in my signature. The ADB link correctly points to version 19.0.2 now. Try that one. Try a different cable if you have one, try a different USB port if you can.
Click to expand...
Click to collapse
Tried two different cables on two different USB ports with the new 19.0.2 downloads you posted - still having the same thing happen. Could it be the computer I'm using, or the drivers I installed (I used the Skipsoft Unified Android Toolkit drivers)? Or is my device just totally bricked and unrecoverable?
Thanks!

mbressman said:
Tried two different cables on two different USB ports with the new 19.0.2 downloads you posted - still having the same thing happen. Could it be the computer I'm using, or the drivers I installed (I used the Skipsoft Unified Android Toolkit drivers)? Or is my device just totally bricked and unrecoverable?
Thanks!
Click to expand...
Click to collapse
You can try different drivers. Uninstall current ones, and install the ones from my signature.

Aerowinder said:
You can try different drivers. Uninstall current ones, and install the ones from my signature.
Click to expand...
Click to collapse
Ok, so I removed the Clockworkmod ADB drivers from add/remove programs (or uninstall programs - whatever it is called now on Win7), then I went into device manager and deleted the driver for Google Nexus BootLoader Interface, and then I rebooted. After the reboot, plugging the Nexus 7 in showed no driver detected, so I downloaded your Koush Universal ADB drivers, extracted them, and used them to install the Google Nexus Bootloader Interface drivers again (that's what it detected for my Android when I pointed the device listed in device manager to the extracted folder).
I then ran "fastboot oem unlock" but it's still getting stuck at the same place: (bootloader) erasing userdata...
Anything else I can try?
Thanks!

Hi,
I have the same issue since yesterday. When I pulled my nexus from my backpack (charged 12 hours earlier) its battery was drained. After charging it nexus stucked on google screen during normal or recovery boot. Oem unlock also hangs on erasing userdata. I'm looking forward for any solution to this.
Maybe some ****ty update? I've got the LTE version.

Anyone have anything else I can try?
I'm currently working on getting ASUS to replace the device under warranty - but they want me to send it in first, and I'm concerned that while I can't access any of my data on it, the data might still be there and potentially accessible to others (and I'd prefer to not have all of my confidential data that I stored on there accessible to anyone else). Unfortunately, ASUS won't replace/repair it unless I send it in, so I'm between a rock and a hard place...
Any help or advice is greatly appreciated!
Thanks.

mbressman said:
Anyone have anything else I can try?
I'm currently working on getting ASUS to replace the device under warranty - but they want me to send it in first, and I'm concerned that while I can't access any of my data on it, the data might still be there and potentially accessible to others (and I'd prefer to not have all of my confidential data that I stored on there accessible to anyone else). Unfortunately, ASUS won't replace/repair it unless I send it in, so I'm between a rock and a hard place...
Any help or advice is greatly appreciated!
Thanks.
Click to expand...
Click to collapse
I've tried every single way to unbrick my nexus. After 2 days of searching send it for repair. Without any questions they replaced mainboard. Problem solved hard way.

Gawson said:
I've tried every single way to unbrick my nexus. After 2 days of searching send it for repair. Without any questions they replaced mainboard. Problem solved hard way.
Click to expand...
Click to collapse
Gawson - when you got it back did it still have your data on it, or was it wiped?

mbressman said:
Gawson - when you got it back did it still have your data on it, or was it wiped?
Click to expand...
Click to collapse
When I got it was wiped. Flash is on the mainboard so there was no way they could save my data. They do not migrate your personal stuff.
Now its working like new. In fact it has all new guts except battery and screen.
Only problem is that now auto brightness sensor is giving crap instead of useful data. I don't know if its hardware related or just 4.4.3 issue.

Samsung note 2: need to recover with LCD broken and password. Help (or miracle?).

Hello,
I'm in a dire situation.
my Samsung note 2 (N7100) has a faulty display (LCD started blacking out and now is completely black).
I am trying to access it via [email protected] but unsuccessfully - this could be due to the fact I have a PIN to access my phone and/or USB debug not being activated.
I have tried to enter the PIN but not sure whether that was successful or not (I tried to get an idea of where the numbers are by looking at another samsung..).
I am following this thread to find out how to get [email protected] to work (http://forum.xda-developers.com/showthread.php?t=2786395&nocache=1 ) but I'm not sure how to proceed.
- where do the instructions need to be put? is that ADB shell?
- how to bypass the PIN? is there any way or do I have to keep trying to guess?
- are there any other ways to recover the contents of my phone?
thank you very much for your help!

thanks for your reply.
I am not sure how to use ADB.. any quick and dirty guide on how to do that?
About the screen: the samsung note 2 LCD screen is more expensive than buying a used one! all I care at this stage are my photos and data.. I will get a new one as it's the cheapest way..
Thanks

Galaxy S20 Ultra stuck in Recovery Mode after failed Smwart Switch Update

Hi guys,
I attached my brand new Galaxy S20 Ultra to my PC and started Smart Switch today. The Software showed an update for my device so I downloaded it and started the update process. Unfortunately, Smart Switch got stuck during the update process at 68%. Nothing happened, cables and all still attached. It just didn't proceed any further for hours.
I decided to take the path of stopping the process, using the key combination shown on my device. It now said, recover your device software with Smart Switch Emergency recovery function. I started this and guess what: it also stopped at 68%.
I "rebooted" the device (volume down + power for approx. 10 seconds) and it starts again in recovery mode.
I manually filled in the recovery code and it seemed like Smart Switch was downloading the OS again. Started the recovery process and it is stuck at 68% again.
Now I am just super afraid that I bricked the device by using Samsungs original software.
Anyone her to help or have similar experiences?
Thanks for any advice on how to proceed.
Julius

What exactly were you trying to do? I mean normally you hook up old phone and use smart switch to update new phone. So why was you connected to a PC? It does sound like you bricked it.
So now you probably need to flash the ROM.

I read that smart switch is a good and valid source to check for updates. I never thought that an official Samsung software can be so bad at something so basic, resulting in bricking my phone...

Stop using smart switch to update your phone. You haven't hard bricked it because you still have recovery. It's called a soft brick. Download Odin 13.3_3B from here on xda. Do not use the 13.4 because it's suspected to have a fishy call back to a server from a dll that's in the program folder. Download the atch firmware for your model from sammobile or get it in this s20 ultra forum. You should be able to flash the new firmware.

Thanks @freebee269. Does flashing the firmware with Odin void my warranty or does this only count for rooting devices? (Sorry for stupid questions)

Julius_GER said:
Thanks @freebee269. Does flashing the firmware with Odin void my warranty or does this only count for rooting devices? (Sorry for stupid questions)
Click to expand...
Click to collapse
Odin uses official firmware from Samsung so no warranty voided.

Julius_GER said:
Hi guys,
I attached my brand new Galaxy S20 Ultra to my PC and started Smart Switch today. The Software showed an update for my device so I downloaded it and started the update process. Unfortunately, Smart Switch got stuck during the update process at 68%. Nothing happened, cables and all still attached. It just didn't proceed any further for hours.
I decided to take the path of stopping the process, using the key combination shown on my device. It now said, recover your device software with Smart Switch Emergency recovery function. I started this and guess what: it also stopped at 68%.
I "rebooted" the device (volume down + power for approx. 10 seconds) and it starts again in recovery mode.
I manually filled in the recovery code and it seemed like Smart Switch was downloading the OS again. Started the recovery process and it is stuck at 68% again.
Now I am just super afraid that I bricked the device by using Samsungs original software.
Anyone her to help or have similar experiences?
Thanks for any advice on how to proceed.
Julius
Click to expand...
Click to collapse
What kind of USB Port did you use?
Try again using a USB 2.0 port, Samsung always had problems with it's software and USB 3.0 ports.
Use USB 2.0 and try again.

Hi guys, i have a similar problem as (xReem).
Attached my GT SM-T515/10.1 tab to smart switch where the software was unable to recognise my device!? Was advised to use the Emergency Code function but i have no code due to backing up my data to sd card! I have Magisk and TWRP installed where my device was working beforehand, but since attaching to smart switch, my device is now totally "dysfunctional"!!!
Error message as follows...
...An error as occurred while updating the software. Use the Emergency Recovery function in the Smart Switch PC software. ...
Like i sad, i have no code!!!
I am able to get to the device unlock choice screen and if i choose to restart, my device always boots to the Smart Switch Emergency Code screen?! If i choose the device unlock or download screens, both screens are accessible! Tried to flash my original firmware (BTU-T515XXU3ASK5-20191224095700) using Odin3_v3.14.1 and twrp-3.3.1-6-T515XXU3ASK5-20200215 with no joy (Fail!)
Although i'm totally @"#$%* off about this, as its a new device, i am also curious if someone has ever cracked this... 'Smart Switch No Code' problem before. Hmm...
Anyways, any help appriciated...
Oh! Cannot access recovery at all...
Any help appriciated.

klantee said:
Hi guys, i have a similar problem as (xReem).
Attached my GT SM-T515/10.1 tab to smart switch where the software was unable to recognise my device!? Was advised to use the Emergency Code function but i have no code due to backing up my data to sd card! I have Magisk and TWRP installed where my device was working beforehand, but since attaching to smart switch, my device is now totally "dysfunctional"!!!
Error message as follows...
...An error as occurred while updating the software. Use the Emergency Recovery function in the Smart Switch PC software. ...
Like i sad, i have no code!!!
I am able to get to the device unlock choice screen and if i choose to restart, my device always boots to the Smart Switch Emergency Code screen?! If i choose the device unlock or download screens, both screens are accessible! Tried to flash my original firmware (BTU-T515XXU3ASK5-20191224095700) using Odin3_v3.14.1 and twrp-3.3.1-6-T515XXU3ASK5-20200215 with no joy (Fail!)
Although i'm totally @"#$%* off about this, as its a new device, i am also curious if someone has ever cracked this... 'Smart Switch No Code' problem before. Hmm...
Anyways, any help appriciated...
Oh! Cannot access recovery at all...
Any help appriciated.
Click to expand...
Click to collapse
Did you ever get things working ? If not, when you flashed with Odin - did you use the PATCHED Version ? THis is necessary when flashing firmware via Odin on the S20 Ultra.....
You can download Odin 3.14.1_3b here: https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
Be sure to download the PATCHED version of 3.14.1_3b (it is located as an attached file at the bottom of the first post in the OP at the link above. Hope this helps.

Geekser said:
Did you ever get things working ? If not, when you flashed with Odin - did you use the PATCHED Version ? THis is necessary when flashing firmware via Odin on the S20 Ultra.....
You can download Odin 3.14.1_3b here: https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
Be sure to download the PATCHED version of 3.14.1_3b (it is located as an attached file at the bottom of the first post in the OP at the link above. Hope this helps.
Click to expand...
Click to collapse
No, to answer your first question, and yes used the patched version of Odin you state but with no joy.
(would another version of Odin be better for my device model?)
I just need to find a way to flash the original stock recovery. Having the TWRP installed as mentioned earlier is blocking my path, and I have now tripped knox! So no more options available to access the unlock oem screen. Now frp is off, oem is on!
Also, I was wondering if anyone had thought about a totally updated version of the old "ALL IN ONE TOOL" which was available for some earlier makes of phone devices? I think due to manufacturers security upgrades of today's phones we could all do with something like this?
I heard you can do a NAND/Reset wipe via the Odin options screen which would allow you to install a new rom???
Oh, my predicament was based on Julius's post, not xReem. Sorry for the confusion.

klantee said:
No, to answer your first question, and yes used the patched version of Odin you state but with no joy.
(would another version of Odin be better for my device model?)
I just need to find a way to flash the original stock recovery. Having the TWRP installed as mentioned earlier is blocking my path, and I have now tripped knox! So no more options available to access the unlock oem screen. Now frp is off, oem is on!
Also, I was wondering if anyone had thought about a totally updated version of the old "ALL IN ONE TOOL" which was available for some earlier makes of phone devices? I think due to manufacturers security upgrades of today's phones we could all do with something like this?
I heard you can do a NAND/Reset wipe via the Odin options screen which would allow you to install a new rom???
Oh, my predicament was based on Julius's post, not xReem. Sorry for the confusion.
Click to expand...
Click to collapse
Sorry for your troubles - wish I could help you but you have done everything I would have tried. Maybe, if you haven't already done this - leave the phone on until the battery runs out completely. Then, recharge the phone for a while so the battery has some juice again and then get the phone back into download mode by pressing volume up and volume down at the same time - then plug in the USB - it shoul.d launch into download mode again - then try flashing again with the patched odin.
If you have already done this - then I don't know how what else to suggest.
I wish you luck and hope you are able to get things working again.

Geekser said:
Sorry for your troubles - wish I could help you but you have done everything I would have tried. Maybe, if you haven't already done this - leave the phone on until the battery runs out completely. Then, recharge the phone for a while so the battery has some juice again and then get the phone back into download mode by pressing volume up and volume down at the same time - then plug in the USB - it shoul.d launch into download mode again - then try flashing again with the patched odin.
If you have already done this - then I don't know how what else to suggest.
I wish you luck and hope you are able to get things working again.
Click to expand...
Click to collapse
Thanks for the advice. I'll try what you suggest and see what happens. Stay well!

Julius_GER said:
Hi guys,
I attached my brand new Galaxy S20 Ultra to my PC and started Smart Switch today. The Software showed an update for my device so I downloaded it and started the update process. Unfortunately, Smart Switch got stuck during the update process at 68%. Nothing happened, cables and all still attached. It just didn't proceed any further for hours.
I decided to take the path of stopping the process, using the key combination shown on my device. It now said, recover your device software with Smart Switch Emergency recovery function. I started this and guess what: it also stopped at 68%.
I "rebooted" the device (volume down + power for approx. 10 seconds) and it starts again in recovery mode.
I manually filled in the recovery code and it seemed like Smart Switch was downloading the OS again. Started the recovery process and it is stuck at 68% again.
Now I am just super afraid that I bricked the device by using Samsungs original software.
Anyone her to help or have similar experiences?
Thanks for any advice on how to proceed.
Julius
Click to expand...
Click to collapse
Hey Julius, did you get your phone to work. I am having the same issue.
Update:
I am good now. I was using the thunderbolt cable that came with the phone and update would get stuck at the same point everything with odin 3.13 and 3.14.
I used a USB 3 to thunderbolt cable that I had from an older phone and it work.
What I used:
Windows 10 x64 1909
USB 3 to thunderbolt cable
USB driver downloaded from Samsung support. I think it is the same driver that comes with smart switch because when I installed it, it prompted
to reinstall driver.
Odin3 v3.13.3_3B_PatcheD from here https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572. ( I think 3.14 will work too.
I really think the cable was the only problem)
Firmware downloaded with SamFirm

klantee said:
Thanks for the advice. I'll try what you suggest and see what happens. Stay well!
Click to expand...
Click to collapse
Open Odin as administrator and if using a stock AP file always use the HOME-CSC of the same firmware in CSC slot. Sometimes Odin plays the fool and gets stuck.

ASHLEY117 said:
Open Odin as administrator and if using a stock AP file always use the HOME-CSC of the same firmware in CSC slot. Sometimes Odin plays the fool and gets stuck.
Click to expand...
Click to collapse
Wow! This nearly worked!!!
Managed to get a (((PASS))) on Odin and my tab actually rebooted into the Samsung logo!!!
Soon after this though tab immediately Boots back into download mode??? Tried the same steps but without any progress???
I feel I'm close to cracking this but need some more advice on how to build on such "progress"!?
Many thanks for your advice...

klantee said:
Wow! This nearly worked!!!
Managed to get a (((PASS))) on Odin and my tab actually rebooted into the Samsung logo!!!
Soon after this though tab immediately Boots back into download mode??? Tried the same steps but without any progress???
I feel I'm close to cracking this but need some more advice on how to build on such "progress"!?
Many thanks for your advice...
Click to expand...
Click to collapse
Try with all slots filled but with CSC file not HOME-CSC. That may help as it flashes pit file to factory reset

ASHLEY117 said:
Try with all slots filled but with CSC file not HOME-CSC. That may help as it flashes pit file to factory reset
Click to expand...
Click to collapse
Tried your suggestion with no joy. Will keep trying though as I feel this issue can be cracked. Many thanks...

Geekser said:
Sorry for your troubles - wish I could help you but you have done everything I would have tried. Maybe, if you haven't already done this - leave the phone on until the battery runs out completely. Then, recharge the phone for a while so the battery has some juice again and then get the phone back into download mode by pressing volume up and volume down at the same time - then plug in the USB - it shoul.d launch into download mode again - then try flashing again with the patched odin.
If you have already done this - then I don't know how what else to suggest.
I wish you luck and hope you are able to get things working again.
Click to expand...
Click to collapse
(((SUCCESS)))!!! :laugh::laugh::laugh:
Done what you suggested by waiting until my battery ran out!
I downloaded a different software version and as soon as I plugged my tab into my PC with USB, i flashed the new software with no problems!!!
Flashed TWRP, Magisk and Multidisabler problemless the same!
The lesson learnt here...
...(ONLY FOR THOSE WHO KNOW WHAT THEY ARE DOING)...
...is to probably only have 30% battery when flashing!!! This way you won't have to wait weeks for such a large capacity battery to run down, like I did!
I knew I'd crack it!

klantee said:
(((SUCCESS)))!!! :laugh::laugh::laugh:
Done what you suggested by waiting until my battery ran out!
I downloaded a different software version and as soon as I plugged my tab into my PC with USB, i flashed the new software with no problems!!!
Flashed TWRP, Magisk and Multidisabler problemless the same!
The lesson learnt here...
...(ONLY FOR THOSE WHO KNOW WHAT THEY ARE DOING)...
...is to probably only have 30% battery when flashing!!! This way you won't have to wait weeks for such a large capacity battery to run down, like I did!
I knew I'd crack it!
Click to expand...
Click to collapse
Glad I could hel;p- I know how frustrating it is when things seem like you can never get things to work - anyway - best of luck - and be sure to hit thanks If I helped you.

Hi Do you lose your data (vids and pics) via this method? i have had same thing happen on my s20+

OEM Unlock Doesn't Exist | Galaxy Note 10+

Hey guys I have finally admitted defeat, Im not really sure what else to do at this point, as I have tried a lot;
- Flashed the base android pie (12.0) OS
- Hard reset
- Changed Date and Time back 7 days to prevent jail
- Disabled automatic system updates
- Disabled things such as updates, timezone change, etc.
Enable Developer options: and OEM doesn't appear at all, simply doesnt exist, not even grayed out or anything
The only thing I could find online explaining this issue is that the reason this happens is because my device is SIM-locked. Which it isn't. It's fully unlocked (XAG/XAG/XAA)
Model: SM-N975U1 Region: XAA
Any help would be great thanks

and yes it is connected to the wifi, and tried updating also (im on the latest), still nothing has changed

jacobjake7 said:
Hey guys I have finally admitted defeat, Im not really sure what else to do at this point, as I have tried a lot;
- Flashed the base android pie (12.0) OS
- Hard reset
- Changed Date and Time back 7 days to prevent jail
- Disabled automatic system updates
- Disabled things such as updates, timezone change, etc.
Enable Developer options: and OEM doesn't appear at all, simply doesnt exist, not even grayed out or anything
The only thing I could find online explaining this issue is that the reason this happens is because my device is SIM-locked. Which it isn't. It's fully unlocked (XAG/XAG/XAA)
Model: SM-N975U1 Region: XAA
Any help would be great thanks
Click to expand...
Click to collapse
Your device is probably RMM locked. Please take a look at this thread.

nxmryada said:
Your device is probably RMM locked. Please take a look at this thread.
Click to expand...
Click to collapse
Thanks,
I don't quite understand this part;
"
When Odin shows "PASS", take your device in hands, disconnect the usb cable and press simultaneously the "Power" + "Vol. Down" + "Vol. Up" buttons until the downoad mode disappears
At the precise moment the screen becomes black, immediately release the "Vol.Down" button and press the "Vol. Up" + "Power" buttons during 10 to 15sec to forcefully enter TWRP
***Don't boot into rom because it will lock your device again!!!!
Once the custom recovery booted, swipe to "Allow modification" and flash RMM-State_Bypass.zip as normal zip"
I flashed then did as it said but it just sends back to the original recovery screen

jacobjake7 said:
Thanks,
I don't quite understand this part;
"
When Odin shows "PASS", take your device in hands, disconnect the usb cable and press simultaneously the "Power" + "Vol. Down" + "Vol. Up" buttons until the downoad mode disappears
At the precise moment the screen becomes black, immediately release the "Vol.Down" button and press the "Vol. Up" + "Power" buttons during 10 to 15sec to forcefully enter TWRP
***Don't boot into rom because it will lock your device again!!!!
Once the custom recovery booted, swipe to "Allow modification" and flash RMM-State_Bypass.zip as normal zip"
I flashed then did as it said but it just sends back to the original recovery screen
Click to expand...
Click to collapse
RMM locking prevents flashing AFAIK. Please check for "RMM state" in download mode, if it's "Prenormal" then you're locked out.

nxmryada said:
RMM locking prevents flashing AFAIK. Please check for "RMM state" in download mode, if it's "Prenormal" then you're locked out.
Click to expand...
Click to collapse
I am unable to find any display info on this device, like such as in downloader. Where can I find my RMM state?

nxmryada said:
RMM locking prevents flashing AFAIK. Please check for "RMM state" in download mode, if it's "Prenormal" then you're locked out.
Click to expand...
Click to collapse
Wait isn't RMM state just that 7 day jailing? I tried doing this before I flashed/hard reset my phone was on months before I reset it and was still unable to get that OEM option

nxmryada said:
RMM locking prevents flashing AFAIK. Please check for "RMM state" in download mode, if it's "Prenormal" then you're locked out.
Click to expand...
Click to collapse
I understand the lingo a bit more now after reading up, but that article is a flat circle. It wants me to Install twrp to flash a RMM bypass zip (which you need to disable bootloader to even do in the first place), and you need root access to use twrp.
Yet the information provided below of how to root tells me I need to install twrp and boot into it's recovery, but you need to be root to do that?!?
Make it make sense!

Probably by flashing a combination without etoken or something of that sort?
Locked bootloader prevents booting unsigned boot stages.
What about disable Knox through ADB with the SamFwTool ?
I think you may need to remove google account and screenlocks first, not sure.

Network_Pro said:
Probably by flashing a combination without etoken or something of that sort?
Locked bootloader prevents booting unsigned boot stages.
What about disable Knox through ADB with the SamFwTool ?
I think you may need to remove google account and screenlocks first, not sure.
Click to expand...
Click to collapse
Disabling Knox within SamFw works, however I am still KG/RMM locked

Hit a brick road here not really sure where else to go...
I have a Galaxy Note 10+ (SM-N975U1 XAG) that is RMM locked an unable to get the OEM option in dev settings,
Since Knox is one responsible for the valutmanager line that releases the RMM check, I tried disabling Knox completely through SamFW tool, disabling works, however I am still locked.
Any help would be apricated...

jacobjake7 said:
Hit a brick road here not really sure where else to go...
I have a Galaxy Note 10+ (SM-N975U1 XAG) that is RMM locked an unable to get the OEM option in dev settings,
Since Knox is one responsible for the valutmanager line that releases the RMM check, I tried disabling Knox completely through SamFW tool, disabling works, however I am still locked.
Any help would be apricated...
Click to expand...
Click to collapse
This video may help...
youtu.be/6RTbx2jTkpQ
as the person said only Exynos versions can be unlocked and not Snapdragon ones.
and also this video below shows how to unhide the hidden oem unlock button
youtu.be/mF2Nxck4FtM

aiSanaul said:
This video may help...
youtu.be/6RTbx2jTkpQ
as the person said only Exynos versions can be unlocked and not Snapdragon ones.
and also this video below shows how to unhide the hidden oem unlock button
youtu.be/mF2Nxck4FtM
Click to expand...
Click to collapse
I have a Exynos, OEM doesn't exist in Dev options, since im RMM locked....

jacobjake7 said:
I have a Exynos, OEM doesn't exist in Dev options, since im RMM locked....
Click to expand...
Click to collapse
check out methods here
www (dot) 99mediasector.com/how-to-disable-rmm-state-lock-in-samsung-galaxy-devices/

aiSanaul said:
check out methods here
www (dot) 99mediasector.com/how-to-disable-rmm-state-lock-in-samsung-galaxy-devices/
Click to expand...
Click to collapse
Thanks,
First option I can't do TWRP since I need root and unlocked bootloader, so next step;
Miracle Box Thunder ive been messing around with before, is interesting, can only get it to work for the first half second it connects to my phone and then the stop button grays out :/
Though I got it do to this for the "Reset Reactivation/EE Locks":
Start Detect device.
Device detected OK.
Downloading..
Get phone data..
Reactivation Lock Reset Launched...
Searching For Reactivation Data 1...
Loading Data Please wait..
Rc Block Update ok...
Processing Data...
Done..
EE Lock Reset Launched...
Searching For EE Data 1...
Loading Data Please wait..
Error Data Not Found...
>>All Done..
I am unable to view my download mode info in the top left. Would you know how to "enable" it or how I can go about viewing it another way?

aiSanaul said:
check out methods here
www (dot) 99mediasector.com/how-to-disable-rmm-state-lock-in-samsung-galaxy-devices/
Click to expand...
Click to collapse
Actually while doing the "Reset Reactivation/EE Locks" it gave me a text top left of the download mode, saying "ODIN: TOKEN Size is too large [-13]"

Update...I was able to bypass the RMM/KG lock by first doing a fresh install;
skip through all intro and setup (or just FRP skip)
DONT SET A SCREEN LOCK, must be unlocked or swipe otherwise you will be softbricked in a infinite "starting device..."
next you use Minimal ADB and Fastboot terminal and type "adb shell pm disable-user --user 0 com.android.systemui"
your phone is gonna freak out now dont worry about it and open up FRP Samsung by NKTEAM and click "Kill update" (this is important)
then after kill update is complete you can run "Disabled KG Locked MTK ADB" which will lock your phone saying you uninstalled a samsung service etc....just reboot your device and your good!
Though, I don't understand how to unlock OEM still? I still don't have the option?
Should I flash oreo or something? Though flashing causes it all to relock again

Not to give up and never admit defeat, here is what I would do since I am not sure what that RMM is, I am not actively reversing this technology just collecting information from the web.
I would ask the tools creators through their support chats if they can extend the tools to deal with the faulting security mechanisms. At the same time I will check where is a cheap replacement board, just in case help it brick itself (yes the security mechanism design is self-destructing, I do not admit I break it it breaks itself).
I will flash with Odin with pit file with format to try to truly revert to factory. If I am not happy with the result I start becoming creative with the tools at hand LOL:
Then I will start flashing Bin-compatible official files with patched Odin, until the device resets itself to factory at least two times. The idea being due to crypto differences in the versions, the entire partitions gets rewritten during flashing. I would try this by removing all locks and protections (accounts), resetting to defaults, and flashing the first and the last bin-compatible firmware from samfw site.
Someone mentioned they achieved not-keeping previous things by mixing their firmware files AP BL CSC etc this is something I would try to try and get the device to confuse the crypto and overwrite things.
The idea is that the second stage bootloader BL will always be able to get you to download mode to flash with Odin so messing and even triggering with the later boot and protection stages should not erase the XBL. If it does then I will need the emergency_download_debug whatever package for the Bin version.
What Bin version is the device anyway ?

SM-N975U1 is Snapdragon. Why did you think it was Exynos?

Ask @afaneh92 he is unlocking specific versions of bootloaders for US/Canada devices since the SamPWN team are missing from the forums. https://forum.xda-developers.com/t/...unlock-for-samsung-us-canada-devices.4215101/