Database Users

[Q] Help needed after leak 3.1!!!

After updating to 3.1 with the leak one. Using fine for a few hours. And didn't rooted. Then ,
There are a lot of massage box said many functions have to" force close" such as bluetooth and so on.
Then I restarted it.
Problem comes !!!
While boosting, there is a massage box said " All pre-install process complete!"
Then ask me to enter a password "Enter your password" and cannot access to the OS. It keep my screen with this page.
And I did not set any password at all.
I tried 1.Re flashing the leak 3.1 via sd card , 2.flashing the FULL PACKAGE via sd card, (which is for 3.0) ..... and both are not the way to solve. Everything still the same, " All pre-install process complete!" every time I try to open the tab and "Enter your password"
Any suggestion ????

I guess this has to do with that recovery_install.sh script that you should delete before messing with self installing recoverys.
You should root your device (theres actually a howto in the dev section), install CWM then do a full wipe (System, Dalvik, etc.) and then install a stock rom from within CWM and you should be good to go again.
Oh hell sorry, just read that you cannot access the os at all. Well then try if you can connect via ADB?
Hard to say what else you could try as you already seem to have done most!

thanks for the advice.
BUT
I don't know how to do now as I cannot do anything with my tab coz it struck at the page "Enter Your Password".I can only volumn + and - .... That is. Cant even log into the OS.
Only something via external SD. (nothing happends when I connect my tab with PC also)

is it possible that you have encrypt your tablet ?
But there is a way that u can do by plugging keyboard and press home.. something like that.. that triggers factory reset

interqd said:
is it possible that you have encrypt your tablet ?
But there is a way that u can do by plugging keyboard and press home.. something like that.. that triggers factory reset
Click to expand...
Click to collapse
This works. Thanks so much

[Q] Bell D803 constant re-boot

A bit of an SOS situation if anyone knows the right steps please
Well, I restored a Titanium Backup and mistakenly toggled the "restore system apk". It ran fine, all restored and then when I rebooted got stuck.
By "stuck", it re-boots constantly. It shows the LG animation, then all I can see is two messages before it starts booting again:
1) "Unfortunately, Google Play Services Has Stopped"
2) "Unfortunately, System UI has stopped
... and then it does the entire boot sequence, animation, again, and again.
Here is what I can do:
* It is in USB debug mode.
* I have drivers on laptop
* I am able to connect with adb and also shell into phone.
* With adb, I have output to the file an "adb bugreport" as well as an "adb logcat".
* I have several backups:
a) The modemsst1.img and modemsst2.img created by Titanium Backup
b) Titanium backups (full apps and data)
c) an "adb backup - all" backup
* I managed to get it into firmware update mode by pressing the volume up button and the power button and then when it flashed red a few times, just the up button. So, I can get it into Firmware update mode.
Of course, I have never really used adb before, except to dabble a bit. So, I am encouraged that I can somehow get into with shell.
I am not unplugging it until I know what to do!

Since then I have been able to turn the phone off and also put it into charging on USB.
This is what worked:
* Hold down power and volume down button until booting stops and phone turns off completely.​
When it does shut down, I kept buttons down until it flashes logo again and then shuts down again. Then I let go. Phone is off and when I plugged in the charger it shows charging animation.
Now, after inspecting the bugreport, I noticed a lot of these messages for all the system apps like this one:
"I/PackageManager(21318): Expecting better updatd system app for com.lge.sizech"​
I think the cause of all this shralp is this, I did a LG Mobile Support Tool "Upgrade Recovery" and then in Titanium Backup I restored an older backup (incl system apks). At least that makes sense seeing all the "Expecting better apdat system app" messages in the bugreport.
Still not sure what to do next

I tried the very good instructions here:
[Guide] Unroot/Unbrick - flash official factory firmware with LG Launche
http://forum.xda-developers.com/showthread.php?t=2471370
The update succeeded. However, when I rebooted the phone it is in the same boot-loop with message that it was before.
I used the BELL D803B10D_00.kdz file. Now I will try with the earlier version BELL D803BA_00.kdz file.
We will see what happens ...

do you have nandroid backup from previous rom?

I have three backups:
1) Titanium Backup (full)
* This was my first backup performed right after rooting device and installing Titanium Backup.
2) Titanium Backup (full)
* Did this 2 days ago. Device was working OK and did as precaution.
3) ADB BACKUP. I did this one before my Titanium restore.
I restored the first titanium backup and that (ooooppps!) was after I did an LG Firmware update.
ALSO:
I am on Windows 7 64 and although adb works fine, fastboot does not. I understand that might be a problem with windows 7 64.
So, unless anyone objects, I am going to redo on my windows 32 machine and also "fastbook oem unlock".
Since firmware is OK, if I do the fastboot oem unlock, that will wipe everything. But I can still boot and re-setip the phone, right?
Just checking before I fudge everything up here ..
ALSO ALSO:
I had antivirus/theft security installed and I disabled it partway through last restore.
Maybe that has somethng to do with this all .
But I am still cool because I can ADB and also firmware install seems ok.
ADB works and that is the one good sign.

or you can follow ADB Sideload method
http://forum.xda-developers.com/showthread.php?t=2318497

zekurosu said:
or you can follow ADB Sideload method
http://forum.xda-developers.com/showthread.php?t=2318497
Click to expand...
Click to collapse
I don't (didn't) have TWRP installed. How can I sideload without it?
Also, should I adb oem unlock to get it wiped at this point?

I'm having a similar problem on a Bell D803. Just happened very randomly today. I turned my phone off for an exam, then turned it back on after.. initially had no signal and a black background. Settings for factory reset wouldn't work. My phone is rooted and has TWRP. I went into recovery and formatted.
Bootloop.
Bootloop.
Bootloop x 20.
I however, don't get the same two messages. I just keep bootlooping.
Got home, tried to go through download mode to unbrick it, but for some reason my computer isn't picking it up. I have all the drivers, and before this incident, it was recognized.
Any solutions?
I'm thinking of buying an OTG USB and then just flashing a stock zip from recovery. Would that be a possible viable solution?

asdfvtn said:
I'm having a similar problem on a Bell D803. Just happened very randomly today. I turned my phone off for an exam, then turned it back on after.. initially had no signal and a black background. Settings for factory reset wouldn't work. My phone is rooted and has TWRP. I went into recovery and formatted.
Bootloop.
Bootloop.
Bootloop x 20.
I however, don't get the same two messages. I just keep bootlooping.
Got home, tried to go through download mode to unbrick it, but for some reason my computer isn't picking it up. I have all the drivers, and before this incident, it was recognized.
Any solutions?
I'm thinking of buying an OTG USB and then just flashing a stock zip from recovery. Would that be a possible viable solution?
Click to expand...
Click to collapse
Well, I am able to connect with adb fine on my laptop (Win 7 64) but not on my desktop (Win 7 32)
But on my Win 7 64 I cannot get into fastboot.
I am wondering if the driver install on my desktop went foo-bar and needs reinstall. Also, I noticed that the website drivers are more recent USB drivers than some of the ones linked on this site.

I used adb uninstall package for many user packages and it was success. But I still see the packages listed in the bugreport?
For example: I already uninstalled "com.benhirashima.skiplock" and also "com.lookout".
Why? What to do to really zap them for good?

Sorry, I posted the wrong link earlier.
This was the guide I used which succeeded but made no difference to the boot-loop.
LG G2 Stock Firmware (Go Back to Stock)
http://forum.xda-developers.com/showthread.php?t=2432476&highlight=d803

Just figured out how to do a factory reset.
http://www.youtube.com/watch?v=3ogBvzbPikc
The hard reset worked and now I am configuring the phone settings!
So, again, this is what I did:
1) http://forum.xda-developers.com/showthread.php?p=45293512
2) http://www.youtube.com/watch?v=3ogBvzbPikc
Not sure if it all worked but I am setting the phone up as we speak (or as I type)

natureburger said:
Well, I am able to connect with adb fine on my laptop (Win 7 64) but not on my desktop (Win 7 32)
But on my Win 7 64 I cannot get into fastboot.
I am wondering if the driver install on my desktop went foo-bar and needs reinstall. Also, I noticed that the website drivers are more recent USB drivers than some of the ones linked on this site.
Click to expand...
Click to collapse
Hmm that's strange. Unfortunately for me, I'm already on 64-bit and it still isn't picking it up.

ALL FIXED UP
WORKING 110%
:good:

natureburger said:
ALL FIXED UP
WORKING 110%
:good:
Click to expand...
Click to collapse
I have followed this to a t.
Succesfully flashed the stock firmware that came with the phone when sold.
Did hard reset using the the power button and volume down
= phone rebooting every 10 seconds, no wifi, imei = null
adb devices = offline.
Really depressed right now. If anybody can help me I would appreciate it.

zprovo said:
I have followed this to a t.
Succesfully flashed the stock firmware that came with the phone when sold.
Did hard reset using the the power button and volume down
= phone rebooting every 10 seconds, no wifi, imei = null
adb devices = offline.
Really depressed right now. If anybody can help me I would appreciate it.
Click to expand...
Click to collapse
Press the power button down and hold it.
It should turn off, then look like it is turning on, (flash logo very briefly) and then turn off.
Let go of power button and it should stay off.
Do that. Now, does it work to turn off completely?
Let's see if you can do that first.
Then .. do hard reset, exactly like this:
http://www.youtube.com/watch?v=3ogBvzbPikc
Does the hard reset screen show and give you hard reset options?

natureburger said:
Press the power button down and hold it.
It should turn off, then look like it is turning on, (flash logo very briefly) and then turn off.
Let go of power button and it should stay off.
Do that. Now, does it work to turn off completely?
Let's see if you can do that first.
Click to expand...
Click to collapse
Yup. I totally understand what you are saying and have done it many times. I had to use that method to get into download mode and also had to use it to do hard reset.
I just reflashed the phone all over again a second time succesfully.
Reboots every 5 seconds. Keyboard came up for a few seconds for the first time in 48 hours during the initial setup phase. 5 seconds later as I was trying to input a wifi code it would not appear. then it rebooted as usual.
I really appreciate any input right now. :cyclops::crying:

zprovo said:
Yup. I totally understand what you are saying and have done it many times. I had to use that method to get into download mode and also had to use it to do hard reset.
I just reflashed the phone all over again a second time succesfully.
Reboots every 5 seconds. Keyboard came up for a few seconds for the first time in 48 hours during the initial setup phase. 5 seconds later as I was trying to input a wifi code it would not appear. then it rebooted as usual.
I really appreciate any input right now. :cyclops::crying:
Click to expand...
Click to collapse
1) Are you able to completely turn it off using my instructions?
2) When you hard reset (2nd half of this video), http://www.youtube.com/watch?v=3ogBvzbPikc
a) Does the hard reset screen show?
b) Does it give you the hard reset options?
3) Before it was bricked, was it in 'usb debug mode' in developer options?
4) Which kpz version did you restore to?
5) Did your "adb devices" ever work? Did your "adb shell" ever work?

natureburger said:
1) Are you able to completely turn it off using my instructions?
2) When you hard reset (2nd half of this video), http://www.youtube.com/watch?v=3ogBvzbPikc
a) Does the hard reset screen show?
b) Does it give you the hard reset options?
3) Before it was bricked, was it in 'usb debug mode' in developer options?
Click to expand...
Click to collapse
1) Yes absolutely. It is sitting next to me right now doing nothing at all because I turn it off when I am not trying to fix it, otherwise it keeps rebooting relentlessly.
2) a) Yes, same as the video. b) Yes it says the same exact thing as the video. I press power key twice and it begins. The stock recovery android appears with a loading bar on the bottom for ~1 minute then it goes to the boot "lg animation".
3) Yes it was. Before it was bricked I essentially always had it in debug mode because I successfully rooted it and simply left it on debugging mode after having to activate it to root.
4) D801V11B_00.kdz The EXACT same as the original. This is a Videotron (canadian) phone. I can clearly remember without a doubt going into about phone and this is what it was running before all of this happened.
5) I am having a bit of memory strain here, but I do believe it also said adb devices before any of the issues came. It is a good point I will try "adb device" from another trusted computer.
Other notes: I can browse the android os for a few seconds. Sometimes sound does not work, wifi is non functional (even though the keyboard never appears, I managed to have a security free wifi in my proximity and it would not connect (was saying: temporarily avoiding bad signal)) and also I do have modemstat1.img and modemstat2.img backups for EFS.
adb devices consistently shows "offline" but it is definitely recognizing the phone. I have also tried using usb debugging activated and still "offline". Drivers are up to date and all.
The upper drawer in the usual g2 user interface is strange now. it doesnt have anything except for the date (1970 something...) and a "gear" icon for system settings. I am talking the drawer you drag down from the top of the screen.
This phone was working with absolutely no problems 2 days ago.
Thank you so much for looking into this. I have certainly exhausted my repairing capacities. I am entirely dependent upon the knowledgeable individuals in here from here on out.

zprovo said:
1) Yes absolutely. It is sitting next to me right now doing nothing at all because I turn it off when I am not trying to fix it, otherwise it keeps rebooting relentlessly.
2) a) Yes, same as the video. b) Yes it says the same exact thing as the video. I press power key twice and it begins. The stock recovery android appears with a loading bar on the bottom for ~1 minute then it goes to the boot "lg animation".
3) Yes it was. Before it was bricked I essentially always had it in debug mode because I successfully rooted it and simply left it on debugging mode after having to activate it to root.
4) D801V11B_00.kdz The EXACT same as the original. This is a Videotron (canadian) phone. I can clearly remember without a doubt going into about phone and this is what it was running before all of this happened.
5) I am having a bit of memory strain here, but I do believe it also said adb devices before any of the issues came. It is a good point I will try "adb device" from another trusted computer.
Other notes: I can browse the android os for a few seconds. Sometimes sound does not work, wifi is non functional (even though the keyboard never appears, I managed to have a security free wifi in my proximity and it would not connect (was saying: temporarily avoiding bad signal)) and also I do have modemstat1.img and modemstat2.img backups for EFS.
adb devices consistently shows "offline" but it is definitely recognizing the phone. I have also tried using usb debugging activated and still "offline". Drivers are up to date and all.
The upper drawer in the usual g2 user interface is strange now. it doesnt have anything except for the date (1970 something...) and a "gear" icon for system settings. I am talking the drawer you drag down from the top of the screen.
This phone was working with absolutely no problems 2 days ago.
Thank you so much for looking into this. I have certainly exhausted my repairing capacities. I am entirely dependent upon the knowledgeable individuals in here from here on out.
Click to expand...
Click to collapse
Hmmmm..... why your adb devices is not working? But the re-pair works and you can then do hard reset.
But that is good information you shared.
Maybe someone else can chime in.
From my experience:
1) adb usb access seems spotty. My win 7 64 connected fine and it even kept the shell through the reboot cycle. But on my win 7 32 machine it was only detecting device and then not able to shell.
2) I was also able to use from the LG website LG MOBILE SUPPORT TOOLS.
Download the LG MOBILE SUPPORT TOOL
I downloaded the most recent one from the LG website and make sure to select your options >> country and then the correct phone model at the upper right hand corner of the tool.
Then install USB driver for correct phone model.
Then see if USB works, "adb device" should return the device code.
"adb shell" should show the shell prompt.
3) There is always fastboot. But I an noob and know 0% about how to properly connect and use it.
Some others please chime in and help this droid bro!

S5 cant turn off reactivation lock

Hello
I was searching and trying a lot but didnt found any solution.
My s5 is not turning on so i cant turn off reactivation lock. I tried hard reset, didnt help. Tried root but r/l is blocking odin.
Please help

Dobryskun said:
My s5 is not turning on so i cant turn off reactivation lock. I tried hard reset, didnt help.
Click to expand...
Click to collapse
Which of S5s? (Product name string on display in Odin mode)

G900F

Dobryskun said:
G900F
Click to expand...
Click to collapse
I'd do the next:
1. Get an OTG cable and a USB stick. Format the stick to FAT32 and throw any .apk file on it.
2. Download some 4.4.2, say, G900FXXU1ANCE and flash it with Odin.
3. Reboot to recovery and perform a factory reset.
4. Reboot to system and enter Setup Wizard.
5. Connect the OTG cable with USB stick attached. When the phone detects the stick you will see a pop-up window of file explorer.
6. Navigate to your .apk file (from p.1) and tap on it. You don't really need to install it, you only need a security request after your tap.
7. Tap "settings" and voila, you are in the security settings menu now.
8. Navigate to "reactivation lock" and untick it. You'll be asked to enter your Samsung account credentials or to register a new account.
9. Register a new account, log in to it an you'll be able to untick Reactivation Lock and disable it completely.
The trick will work on early 4.4.2 only.

bbsc said:
I'd do the next:
1. Get an OTG cable and a USB stick. Format the stick to FAT32 and throw any .apk file on it.
2. Download some 4.4.2, say, G900FXXU1ANCE and flash it with Odin.
3. Reboot to recovery and perform a factory reset.
4. Reboot to system and enter Setup Wizard.
5. Connect the OTG cable with USB stick attached. When the phone detects the stick you will see a pop-up window of file explorer.
6. Navigate to your .apk file (from p.1) and tap on it. You don't really need to install it, you only need a security request after your tap.
7. Tap "settings" and voila, you are in the security settings menu now.
8. Navigate to "reactivation lock" and untick it. You'll be asked to enter your Samsung account credentials or to register a new account.
9. Register a new account, log in to it an you'll be able to untick Reactivation Lock and disable it completely.
The trick will work on early 4.4.2 only.
Click to expand...
Click to collapse
Thank you!
I think i had a lollipop on it so it will probably not work but ill try anyway since there is no other way.
I know my password for samsung account, i just cant turn on the phone.
I will get otg cable monday so i will post how it went with your solution.
Btw by usb stick you mean pendrive?

Dobryskun said:
Thank you!
I think i had a lollipop on it so it will probably not work but ill try anyway since there is no other way.
I know my password for samsung account, i just cant turn on the phone.
I will get otg cable monday so i will post how it went with your solution.
Btw by usb stick you mean pendrive?
Click to expand...
Click to collapse
It will work in any case.
There are other ways too.
Yes, a pendrive or something like a USB cardreader with a card, just to connect it as external OTG storage.
You are saying you cannot turn the phone on. What does it mean? What you do and what you see?

bbsc said:
It will work in any case.
There are other ways too.
Yes, a pendrive or something like a USB cardreader with a card, just to connect it as external OTG storage.
You are saying you cannot turn the phone on. What does it mean? What you do and what you see?
Click to expand...
Click to collapse
When i push power button it shows samsung logo and stays like that. Sometimes it restarts over and over again, sometimes it freeze on samsung logo.
Tell me more about other ways please.

Dobryskun said:
When i push power button it shows samsung logo and stays like that. Sometimes it restarts over and over again, sometimes it freeze on samsung logo.
Tell me more about other ways please.
Click to expand...
Click to collapse
1. You should know that the first boot after a factory reset takes a long time, say, up to 15 min. I'd suggest waiting 20 min. and then make a conclusion.
2. If your phone freezes and restarts after a factory reset, it's a good idea to flash a stock ROM. Reactivation lock will not block flashing a stock ROM via Odin.
3. If your phone still behaves abnormally, it's more likely a hw memory problem (rather often for G900), not a reactivation lock problem. Reactivation lock would not prevent the phone from booting.
4. If you still interested in "other methods", have a look at this my thread. It's for SM-G900V and the files will not work for SM-G900F, but there are another files and the main idea will work.
But I'd like to say it again: seems, it's not your case.

bbsc said:
1. You should know that the first boot after a factory reset takes a long time, say, up to 15 min. I'd suggest waiting 20 min. and then make a conclusion.
2. If your phone freezes and restarts after a factory reset, it's a good idea to flash a stock ROM. Reactivation lock will not block flashing a stock ROM via Odin.
3. If your phone still behaves abnormally, it's more likely a hw memory problem (rather often for G900), not a reactivation lock problem. Reactivation lock would not prevent the phone from booting.
4. If you still interested in "other methods", have a look at this my thread. It's for SM-G900V and the files will not work for SM-G900F, but there are another files and the main idea will work.
But I'd like to say it again: seems, it's not your case.
Click to expand...
Click to collapse
1. I will try to wait longer time.
2. Where should i find stock ROM? My phone is in Telenor (Norway)
3. Beggining of the problem with my phone was that one day after turning phone on it came to samsung logo and start to scream ( wery loud noise ) and turned itself off. Since then it didnt pass trough samsung logo ever again. Then i started with factory resets and when it didnt help i tried to root it and put new ROM but all was blocked by R/L.

Dobryskun said:
Where should i find stock ROM? My phone is in Telenor (Norway)
Click to expand...
Click to collapse
https://updato.com/firmware-archive-select-model?q=sm-g900f&exact=1&r=TEN&v=&rpp=15

@bbsc
I have tried to put stock ROM and it didnt help. I was not sure which version should i use so i started with first one from the list. Odin says it was succesfull but phone is stopping now with recovery booting welcome page. It takes about one minute and the phone is off. I tried four versions of stock ROM and result is exactly the same.
Phone is not starting at all.
Should i try all versions of stock rom?

Dobryskun said:
@bbsc
I have tried to put stock ROM and it didnt help. I was not sure which version should i use so i started with first one from the list. Odin says it was succesfull but phone is stopping now with recovery booting welcome page. It takes about one minute and the phone is off. I tried four versions of stock ROM and result is exactly the same.
Phone is not starting at all.
Should i try all versions of stock rom?
Click to expand...
Click to collapse
Hi,
I don't want to make you afraid but I was facing very similar problem and nothing helped but replacement of phone's motherboard at Samsung service centre -> my eMMc memory got corrupted for some reason.
Hopefully it is not your case but after reading your symptoms I wouldn't be much optimistic.

Dobryskun said:
Should i try all versions of stock rom?
Click to expand...
Click to collapse
Any one is enough.
If you flashed a stock rom, performed a factory reset and the phone still restarts it is not a good sympthom.
I think, Many40 is right and it's time for a new motherboard.
There's nothing to be afraid of, it's just about $30 if DIY.

@Many40 @bbsc
Ok so i give up. I realy like this phone so i will give it to service for motherboard replacement since i have no idea how to do it by myself.
Thank you guys for help!
Cheers!

Deleted

deleted

bbsc said:
Solution of what? Replacing the motherboard?
Or you simply found a stolen z3x? No need of it to disable RL on S5.
Click to expand...
Click to collapse
Solution to turn off the activation lock. No need for hostility, just trying to help here.

deleted

Ok I will remove the link and the post. Thanks for the input.

Factory reset has me stuck on "Checking for updates" - Can I re-flash?

Hi all,
:crying: - Looking for a way to get my Mi Note 2 back to life!
This device has never been unlocked or ROMed before (although it has been re-flashed successfully via Xiaomi's own pushed updates).
It is running MIUI 10.0.something (cannot access menus to verify exact).
The problem
----------------
I did a standard factory reset on the phone.
Once restarted, it takes you through the normal setup screens such as 'language', 'region', 'wifi network' after which I am given the option to select "copy your data from an old phone" or "set up as new", no matter which I select, my phone goes to the next screen which shows "Checking for updates". Here it stays - endlessly...
What have I tried?
----------------------
I have tried a different wifi network but it does the same.
I have also tried selecting "copy your data" instead of "set up as new" but it does the same.
Thoughts
------------
I thought I would try to install a new stock ROM to see if that would fix the issue. However, in order to unlock with the Mi bootloader unlock tool (and then use their flashing tool), apparently to do this, I need to enable something under developer options - clearly impossible when I cannot get to any android menus.
The phone *can* be re-started into the fastboot screen but does this help me at all?
On the MIUI website I noticed the following in the tips and tutorials forum: How to install a MIUI update without unlocking the bootloader: https://en.miui.com/thread-3852597-1-1.html
The above got me slightly excited before I realised that I have no way to place a ROM into the ‘downloaded_rom’ folder in the internal storage of my device (as the article instructs). Note that the reason for this (on my phone at least) is that although a Windows explorer window does open when I connect the phone to my laptop, it is empty (i.e. you cannot see any files/folders in it). BTW - I know what causes that specific issue as that bug was present in the device ages ago - basically, the phone seems to default to be in USB charge mode and in order to see the folders in Windows Explorer, you have to go into developer options and manually change the USB mode and then change it back to MTP mode. Once that is done, you can see the files/folder structures. However, I cannot get to any developer options as I cannot get to Settings at all.
What can I do?
------------------
So my burning question is this: How can I re-ROM this theoretically 'working' device, given the above constraints?
Is there any way to do anything while the phone is in the fastboot mode perhaps?
Is there some method maybe used to recover a bricked device that I could employ here?
Thank you for any help offered!
Cheers!

MDM Locked Galaxy Tab A

I have a Samsung Galaxy Tab A (2020, SN-T307U) that I got from work. It's an old Doordash tablet that Doordash didn't want back, so I'm trying to reset it and it's driving me crazy. I have followed so many tutorials trying to get this thing to work, I keep getting caught on something.
- Simply factory resetting does not work, gives an error that MDM does not allow it.
- I cannot put in the wrong password 15 times to factory reset, even though I get a warning it just lets me continue trying after 15 fails.
- I cannot enter the bootloader, rebooting to bootloader just reboots to the OS.
- I cannot enter safemode, same as above.
- I cannot enable developer options, so no OEM unlock or USB debugging. Tapping build number gives me an error that the MDM does not allow this option.
The device is recognized by Odin, can I just brick this thing and repartition from scratch? Can someone who knows what they're talking about walk me through that? I'm not really sure what I'm doing here, learning as I go over these last 2 days.

Hello,
I have the same exact same issue, have you been able to unlock it?
Thank you!

I can fix it remotely the last hope

Same Issue here,

Any one had any luck with MDM T307U. Please assist.

rittnerb said:
I have a Samsung Galaxy Tab A (2020, SN-T307U) that I got from work. It's an old Doordash tablet that Doordash didn't want back, so I'm trying to reset it and it's driving me crazy. I have followed so many tutorials trying to get this thing to work, I keep getting caught on something.
- Simply factory resetting does not work, gives an error that MDM does not allow it.
- I cannot put in the wrong password 15 times to factory reset, even though I get a warning it just lets me continue trying after 15 fails.
- I cannot enter the bootloader, rebooting to bootloader just reboots to the OS.
- I cannot enter safemode, same as above.
- I cannot enable developer options, so no OEM unlock or USB debugging. Tapping build number gives me an error that the MDM does not allow this option.
The device is recognized by Odin, can I just brick this thing and repartition from scratch? Can someone who knows what they're talking about walk me through that? I'm not really sure what I'm doing here, learning as I go over these last 2 days.
Click to expand...
Click to collapse
If you look at all of the previous post, it should tell you that no one has found a way to disable an MDM lock. Which is as it should be. Otherwise the lock would be useless.

lewmur said:
If you look at all of the previous post, it should tell you that no one has found a way to disable an MDM lock. Which is as it should be. Otherwise the lock would be useless.
Click to expand...
Click to collapse
That's not true as of today's date. (In the event this post is viewed after this exploit can be successful).
I am not taking credit and perhaps the op has discovered it. Anyway...
I am in Canada and noticed the carriers here stop at BL 8 while the USA has BL 9.
The unit i had was on BL 9 (csc TMB).
This probably works for Canadians on BL 8. I don't recommend flashing to BL 9 as that may affect your service or experience.
ANYWAY! This guide won't explain any prerequisites. They are adb, installing unsigned drivers, and you aren't able to use the device and are the owner
1) if not already, power off device with vol down+power and ensure battery is at least 50%.
2) enter recovery and factory reset. If you're having difficulty entering recovery, plug into your pc and as soon as you hear the audible disconnect, switch to vol up+power. Or jam on all three buttons for dl mode.
If in dl mode you can check firmware version and just flash it with bl, ap, cp and csc (NOT home csc). Use exact current version. Don't worry about userdata if it is USA
3) at welcome, connect wifi and imnediately go back to first screen. Don't use data sim
4) dl samfw app and on misc tab, check driver status and your pc will reboot.
*you must not have secure boot enabled
5) plug phone into pc. In the app, mtp and select youtube. If done right, click the pop up on your phone and navigate to chrome. Should be automatic.
6) search for vnrom frp. Once there download package disabler pro and notification app. They are side by side. Install notification app and set it up so you can swipe quick settings from top of screen.
5) unplug your phone from pc and plug it back in. Should be able to get back to the package app various ways to install it. Before install, turn wifi off. Now run package disabler and when it prompts for device admin, turn wifi on. It'll glitch a bit but should start.
6) locate samsung setup wizard. Don't confuse with the other. It'll have a green icon. Disable it and clear the storage. At bottom left, tap the back arrow and you should be back at final setup.
7) when asked to add samsung account, turn off wifi. Complete setup and don't add any accounts.
8) you should arrive at home screen. Your phone is re-plugged right? Good. Now turn on usb debugging and use the remove knox from the app. Done.
*i think i turned wifi on just before enabling debugging. I forget.
*if you are sloppy... you'll need to start over. You'll see, or already know
*you can do ota (if there still is any) but factory resetting or odin flashing will put you back to managed.

mindlery said:
That's not true as of today's date. (In the event this post is viewed after this exploit can be successful).
I am not taking credit and perhaps the op has discovered it. Anyway...
I am in Canada and noticed the carriers here stop at BL 8 while the USA has BL 9.
The unit i had was on BL 9 (csc TMB).
This probably works for Canadians on BL 8. I don't recommend flashing to BL 9 as that may affect your service or experience.
ANYWAY! This guide won't explain any prerequisites. They are adb, installing unsigned drivers, and you aren't able to use the device and are the owner
1) if not already, power off device with vol down+power and ensure battery is at least 50%.
2) enter recovery and factory reset. If you're having difficulty entering recovery, plug into your pc and as soon as you hear the audible disconnect, switch to vol up+power. Or jam on all three buttons for dl mode.
If in dl mode you can check firmware version and just flash it with bl, ap, cp and csc (NOT home csc). Use exact current version. Don't worry about userdata if it is USA
3) at welcome, connect wifi and imnediately go back to first screen. Don't use data sim
4) dl samfw app and on misc tab, check driver status and your pc will reboot.
*you must not have secure boot enabled
5) plug phone into pc. In the app, mtp and select youtube. If done right, click the pop up on your phone and navigate to chrome. Should be automatic.
6) search for vnrom frp. Once there download package disabler pro and notification app. They are side by side. Install notification app and set it up so you can swipe quick settings from top of screen.
5) unplug your phone from pc and plug it back in. Should be able to get back to the package app various ways to install it. Before install, turn wifi off. Now run package disabler and when it prompts for device admin, turn wifi on. It'll glitch a bit but should start.
6) locate samsung setup wizard. Don't confuse with the other. It'll have a green icon. Disable it and clear the storage. At bottom left, tap the back arrow and you should be back at final setup.
7) when asked to add samsung account, turn off wifi. Complete setup and don't add any accounts.
8) you should arrive at home screen. Your phone is re-plugged right? Good. Now turn on usb debugging and use the remove knox from the app. Done.
*i think i turned wifi on just before enabling debugging. I forget.
*if you are sloppy... you'll need to start over. You'll see, or already know
*you can do ota (if there still is any) but factory resetting or odin flashing will put you back to managed.
Click to expand...
Click to collapse
This method works up to step 7 for me. I can't seem to enable usb debugging before knox kicks in. With or without wifi. I'm experimenting to see if I can get past that step.

How to Remove MDM Control from Android?​For anyone suffering from this issue, the following are the steps to bypass Samsung Knox factory reset protection:
First of all, create a password for the device.
Make sure that your device is charged to an 80% or greater charge.
Next, you’ll need to go to Settings and Security Encrypt Device tabs respectively.
Set a PIN/password for your device.
After you have secured your device and it’s gone through. Reboot the device, and when it boots, it will ask you to enter a password in order to access your device to view encrypted data. If you type the wrong password 15-20 times (it depends on your device), it’ll wipe your device of any information and will restart and then appear like you’re registering as a brand new device after a factory reset.

Thats the 2th!!! Try it
Video - Samsung SM-T307U Galaxy Tab A 8.4 2020 Knox Remove || Tab a 8.0 MDM Remove
the Tool from the Video Tutorial is here >> SamFwToolSetup_4.3