Related
Hi,
Oke i will save you most of the details which is normally not the best part but i think it doesn't matter how i got here anymore. Basically i tried to update my phone to nougat. So i installed TWRP. Before i could install that i had to unlock bootloader and my phone which i did. After that i succesfully installed TWRP and directly my problems started...
I couldnt get my phone booted into recovery. Finally after hours spending i managed to hook it up on the adb tools via the command line. Long story short, the only thing my phone does right now is boot, where i get the warning that my device is unlocked. If i do a normal boot, nothing happens, if i go to fastboot i can do nothing there because my PC doesn't see the device anymore. I cant use HiSuite to recover it because it shows me a warning that i dont have right for support. When i go to erecovery and connect to my wifi and recover the phone, the package info always fails.
So is there anything i can do to get my phone back to work? Because i am really out of options, somehow sometimes i managed to get into that "installing update" part but appearantly the file in my dload is not the right version so the update always fails.
What to do i? I am really about to smash my phone because i am so mad at myself that i bricked my dive :crying:
Try to get the right firmware for your device or if you remember your old one.
Flash stock recovery and then lock your bootloader also.
Put the firmware inside of your sd card and make a folder called 'dload' push the update.app there inside and make the 3 button way
Good luck.
And if its gonna end badly, Huawei have a VIP service which they will repair it for free IF it is still under warranty.
https://forum.xda-developers.com/hu...huawei-p9-lite-firmware-compilations-t3517124
Get correct firmware from this page & put update.app in dload folder
if you can boot into fastboot, the pc should be able to see it. have you tried looking into device manager to see if the driver is working?
anyway, if you were on stock marshmallow, you should be able use the 3 button combo to reflash the stock rom. after that the phone should be in factory state, with stock recovery and locked bootloader (eventhough in fastboot it still says unlocked).
Hi all !
I have a Samsung A8 (model SM-A800F) which was working great. I ran Kingo Root to try to install Youtube ad free. The next time I restarted it, it didn't load, and restarted in an endless loop to where "Samsung" logo appears (then restarted again). I booted into System Recovery and chose to reset to factory, but it didn't help. Then I tried flash it using Odin in Download mode. I installed the Windows drivers, downloaded the 6.0.1 firmware for Vietnam (where it was purchased), loaded the file into the AP field, and once verified clicked Start. The progress was frozen when reaching mid-way every time I tried, until it said "an error occured while updating the device software. Use the Emergency recovery function in the Smart Switch PC software"...
I downloaded Smart Switch and installed in Windows, but the drivers were not able to install correctly, and failed on the component referring to the ID or something... while Modem driver was installed correctly and the phone appeared in Device Manager. Smart Switch didn't recognize my phone and said "unsupported device".
Now I cannot get the phone stay constantly ON, and the screen shuts down and loads in an endless loop, to the "Error occured" screen... When trying to boot to the ODIN Download page, it loads, I press UP for Continue, and then it again shuts down and loads to "Error Occured".
I tried to charge over night but it didn't help. It does the same thing when the phone is connected to the charger...
However it seems that by IMEI it is sill under warranty. I'm not sure if I voided it :/
Here's what the Download mode page says:
ODIN MODE
PRODUCT NAME: SM-A800F
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
FAP LOCK: ON
Secure Download: Enabled
KNOX WARRANTY VOID: 0
AP_SWREV: 1
Would appreciate any help, this phone is almost new but now it's dead :/
Your warranty is not voided. Your Knox E-Fuse still intact.
Also this is for S8 not A8 forums.
Paradoxxx said:
Your warranty is not voided. Your Knox E-Fuse still intact.
Also this is for S8 not A8 forums.
Click to expand...
Click to collapse
Thanks,
I just couldn't find any A8 forum, and thought there would be more people here who can help.
Would appreciate any help on this... thanks in advance
wurlitzer99 said:
Thanks,
I just couldn't find any A8 forum, and thought there would be more people here who can help.
Would appreciate any help on this... thanks in advance
Click to expand...
Click to collapse
No worries, your phone is not dead.
Try to find a firmware that correspond to the one you got :
http://updato.com/firmware-archive-select-model?exact=1&q=SM-A800F
and use ODIN : http://dl.sammobile.com/Odin3-v3.12.7.zip
You should be good to go.
EDIT : Also for that error occurred thing, try to be faster than it by starting odin flash before it appears.
Thanks,
The problem is that neither the error nor the Odin page would stay on for more than a few seconds. Once they appear, the screen would go dark after 5-10 seconds and then the "error" page would load again (after being darks for another 10 seconds or so). So I can never have ODIN or Smart Switch connecting to the device (the drivers won't connect in Windows)... making it impossible to upload any firmware.
wurlitzer99 said:
Thanks,
The problem is that neither the error nor the Odin page would stay on for more than a few seconds. Once they appear, the screen would go dark after 5-10 seconds and then the "error" page would load again (after being darks for another 10 seconds or so). So I can never have ODIN or Smart Switch connecting to the device (the drivers won't connect in Windows)... making it impossible to upload any firmware.
Click to expand...
Click to collapse
Could you take a picture of that error ? I've never heard/seen such thing
Hi, thanks for the help !
The error is this:
http://statics1.grupoandroid.com/up...1850.jpg.d2bb2a8b77e4fba5fc6467f3d1547886.jpg
I *think* I have some direction... here's what I did/found:
- I installed Smart Switch on my Mac, and chose "Reinstall Device Driver" from the menu. Then restarted the MAC
- I loaded Smart Switch, and Chose "Emergency Software Recovery and Initialization". Then chose the "Device Initialization" tab
- Added the model number "SM-A800F" and the device's serial number (which are physically written on my device).
Smart Switch determined the firmware version to be used for initialization, as:
PDA:QC3 / PHONEG3 / CSCH4(XXV)
- Smart Switch asked to:
1. Power the device down
2. Load recovery mode by pushing Power+Vol Down+Home, then connect the device to the MAC and choose "Continue" to start the initialization...
The problem/s:
My device won't turn on at all, if I do not connect it to either the charger or the MAC (which acts as a supply source?) - which makes me think the battery is fully drained ? i.e when not connected at all, it won't power on.
But when connected to either the charger or MAC, it would bootloop endlessly. i.e it will load the "error" page mentioned above, shut down itself, reload again, shut down and so on.
(I have to mention, that when I first noticed the bootloop, I reset everything to factory settings, cleared cache etc, and it still bootlooped on the Samsung logo).
If when it shuts down during the loop, I push Power+Vol Down+Home, it would boot to ODIN recovery page, where I can push UP for the Download page, but it will still reboot and will again load into the "error" page, which will again reboot endlessly. If I take the charger off the device, it powers off and won't load with any combination of button push.
I also cannot just make it shut down when the charger is connected, using any of the possible button combinations...
I wonder:
- Is there there's a problem which prevents the battery from being charged at all ?
What's strange is that the original problem which made me get into this whole issue, was that is was endlessly booting to the "samsung" logo - but when I booted to System Recovery or Download/ODIN modes, it stopped rebooting endlessly and stayed on... it was also showing the charging indication when powered off... the battery was charging well ever since.
- Why would it bootloop when connected to the charger ? is it possible that the bootloader went bad during my attept to install firmware using ODIN ? I know it always went through the boot.img and recovery.img successfully and only got stuck at about 50% when installing system.img...
I think the current bootloop problem began only once the battery ran out of power. But why wouldn't it charge at all now ??? It's supposed to still charge in this state, isn't it ?
wurlitzer99 said:
Hi, thanks for the help !
The error is this:
http://statics1.grupoandroid.com/up...1850.jpg.d2bb2a8b77e4fba5fc6467f3d1547886.jpg
I *think* I have some direction... here's what I did/found:
- I installed Smart Switch on my Mac, and chose "Reinstall Device Driver" from the menu. Then restarted the MAC
- I loaded Smart Switch, and Chose "Emergency Software Recovery and Initialization". Then chose the "Device Initialization" tab
- Added the model number "SM-A800F" and the device's serial number (which are physically written on my device).
Smart Switch determined the firmware version to be used for initialization, as:
PDA:QC3 / PHONEG3 / CSCH4(XXV)
- Smart Switch asked to:
1. Power the device down
2. Load recovery mode by pushing Power+Vol Down+Home, then connect the device to the MAC and choose "Continue" to start the initialization...
The problem/s:
My device won't turn on at all, if I do not connect it to either the charger or the MAC (which acts as a supply source?) - which makes me think the battery is fully drained ? i.e when not connected at all, it won't power on.
But when connected to either the charger or MAC, it would bootloop endlessly. i.e it will load the "error" page mentioned above, shut down itself, reload again, shut down and so on.
(I have to mention, that when I first noticed the bootloop, I reset everything to factory settings, cleared cache etc, and it still bootlooped on the Samsung logo).
If when it shuts down during the loop, I push Power+Vol Down+Home, it would boot to ODIN recovery page, where I can push UP for the Download page, but it will still reboot and will again load into the "error" page, which will again reboot endlessly. If I take the charger off the device, it powers off and won't load with any combination of button push.
I also cannot just make it shut down when the charger is connected, using any of the possible button combinations...
I wonder:
- Is there there's a problem which prevents the battery from being charged at all ?
What's strange is that the original problem which made me get into this whole issue, was that is was endlessly booting to the "samsung" logo - but when I booted to System Recovery or Download/ODIN modes, it stopped rebooting endlessly and stayed on... it was also showing the charging indication when powered off... the battery was charging well ever since.
- Why would it bootloop when connected to the charger ? is it possible that the bootloader went bad during my attept to install firmware using ODIN ? I know it always went through the boot.img and recovery.img successfully and only got stuck at about 50% when installing system.img...
I think the current bootloop problem began only once the battery ran out of power. But why wouldn't it charge at all now ??? It's supposed to still charge in this state, isn't it ?
Click to expand...
Click to collapse
Hmmm, the thing is, the battery charging process is actually held on some kind of "mini-boot" OS on Samsung I believe, where the phone boots into a certain state, with that said mini-os to display the battery charging info and this kind of things.
My guess is that you *might* have, or more likely your phone did corrupt the flash at some point for x or y reason.
What I'd do is :
Let the phone on a charger a whole night doing its bootlooping thing. And see from there if the battery would charge.
I'd try another computer with Odin just to be sure something is not triggering the reboot process at some point.
And if all the above fails, you still have the warranty, so beside time, you would not be losing any money..
I'm going to write a long post. But I believe it will help a lot of people having a similar problem.
Long story short - problem solved! but it took much of my nerves (and time).
I'll start with the "warranty". The so-called Samsung "warranty" which basically worths nothing!
Calling Samsung international service center, they "informed" me that I must contact Samsung Vietnam, where I bought the device, although I am not there anymore... Needless to say the local dealer in my country refused to take care of this situation, saying Samsung's warranty is regional based, rather than international... which means, only Samsung in the original country where the device was sold in, are responsible for the warranty (and therefore repair!). I had a chat with a Samsung Vietnam representative, who just kept saying "I'm sorry", and refused to let me sent the device out to them for repair! asking me to "bring it to them", although I noted him a few times that I bought it as a tourist and I am not in Vietnam anymore.... Thank you Samsung !! From now on every traveler in the world will know they basically have NO WARRANTY if they buy any Samsung device in a "foreign" country while traveling abroad!
Now for the solution:
I started by letting the device staying connected to the charger overnight, which didn't help. With the OS now installed, I realize that the battery was NOT CHARGED ! it was completely drained, although connected to a charger for long hours... So, know from now on that if your boot data is corrupted, it may cause the device NOT TO CHARGE THE BATTERY at all. Luckily, my desktop PC could use the device while connected to it although the battery was empty, until the problem was sorted out. I did get a crash on my MAC tough (Log said it was USB related), while using Smart Switch, so one option is that it could not supply enough power to the device to keep it keep working at all, or working correctly... So my suggestion is to use a desktop Windows PC in this case, which can potentially provide more power to a device with 0% battery power.
After scratching my head, and considering removing the front panel for replacing the battery (a very risky procedure) I decided to keep on investigating....
I followed a youtube video who suggests that you should install Smart Switch on a PC, choose "reinstall driver" from the menu, restart the PC, then use Emergency Recovery and Initialization, enter the phone model number in the search box (as appearing on the back of the device) , and once it recognizes the model, also to enter its serial number. Here's the video:
https://www.youtube.com/watch?v=1yXQUFrEWg4
This basically brings up a popup message saying Smart Switch detects a compatible firmware for this device, and is about to download and install it. It then asks the user to do the Power+Vol Up+Home push combination trick + pushing UP once the page is loaded in order to "Continue" and bring up the ODIN Download screen, which worked for me if did that as soon as the device shuts down (in the middle of the bootloop). As I couldn't make it load at all with no charger connected, I had it connected to the charger, and once I saw the Smart Switch message asking to do the push combination, I quickly connected it to the computer using another cable which was already connected to the PC USB port on its other end.
Somehow, I could at last make Smart Switch finally start downloading the firmware from the web, and the device again disconnected (bootlooped), but luckily Smart Switch didn't care about it disconnecting, and kept on downloading the firmware. At about 85% of the progress bar state, I could find the downloaded firmware on the temp folders, which are described in this thread:
http://forum.gsmhosting.com/vbb/f777/samsung-firmware-download-belongs-his-serial-number-2038404/
I had to make sure it wasn't still downloading, and watched the "last modified" state of the file to make sure they are not being downloaded anymore. CAUTION: although the AP was not downloading anymore, I know it was probably not good as ODIN couldn't verify it when I tested it. USE ONLY SMART SWITCH !
I quickly copied the folder to which the app extracted the BL and AP files it downloaded, and finally had an officialy bootloader (BL) image, which I could use in ODIN in order to reupload a correct, "official" bootloader to the device....
I hoped the device won't bootloop in the middle, but luckily ODIN was fast enough to send the image successfully, with a "PASSED" status, and the device booted with a nice "Samsung" logo directly to a System Recovery page!
What I exactly did, was loading ODIN, then loading ONLY the BL file into the BL field in ODIN, having it verifying it, and once verified I connected the device, and as soon as ODIN recognized it, pushed START. It managed to upload the image into the device in a few seconds! It seems then, that the bootloop was not caused by a bad battery, but as a result of a corrupt upload of an AP image through ODIN - or because I possibly was using an incorrect version when I tried to upload an AP files to the device on my first attempt to flash it.
Note that I did search for the correct, compatible AP file, by country and model (on Sammobile) but it didn't' work (stuck at 50% in ODIN) ! so I really suggest everyone TO ONLY USE SMART SWITCH if they want to be sure that the correct firmware is being used, and avoid similar situations...
I then deleted the temp files from the PC (the actual ones which were in the temp folder), reinstalled the drivers from inside Smart Switch (just in case), booted the device to Download mode (WHICH DIDN'T BOOTLOOP this time), let Windows installing the drivers (checked in Device Manager), then restarted the PC, and ran Smart Switch again. I repeated the procedure of loading Emergency and Initialization, entering the model and serial number, having it fully downloading the firmware (again) from the web, and installing the firmware into the device. This time it completed the process, and I finally had the device installing and booting into a fresh version 6.0.1 of Android!
Hope it helps!
The phone went into bootloop randomly, it loops at the cyanogen intro and sometimes after the android is optimizing message. I can go into recovery(cyanogen), it has no option to connect to a pc or anything similar. It shows option to enter bootloader, install update from storage etc. I want to recover the images, videos from the device and don't care if i'm unable to use the device after recovering it. Couldn't install twrp as the device doesn't show up in fastboot devices, i'm guessing this is due to usb debugging and such other options not turned on. But i can't do these now as the device is stuck in a bootloop. Is it possible to recover the data or all i can do is flash rom using qfil and lose my data??
kakarotsaiyan said:
The phone went into bootloop randomly, it loops at the cyanogen intro and sometimes after the android is optimizing message. I can go into recovery(cyanogen), it has no option to connect to a pc or anything similar. It shows option to enter bootloader, install update from storage etc. I want to recover the images, videos from the device and don't care if i'm unable to use the device after recovering it. Couldn't install twrp as the device doesn't show up in fastboot devices, i'm guessing this is due to usb debugging and such other options not turned on. But i can't do these now as the device is stuck in a bootloop. Is it possible to recover the data or all i can do is flash rom using qfil and lose my data??
Click to expand...
Click to collapse
Hello, seems your bootloader isn't unlocked and you have the stock recovery, no custom recovery like twrp. So your device cannot be recognized by adb when you have it not enabled.
Try to shut it off by pressing the power button for some time and try to charge it full, then switch on. Also clearing cache in stock recovery can help.
Good evening! I hope you can help me.
I flashed LineageOS 14.1, but I wanted to go back to EMUI. I made all the wipes and tried to flash different stock firmwares through a forced update (volume buttons + power button), but it never worked. At that point, I read about a guy in this forum who suggested to create a flashable zip with Huawei Update Extractor: I followed the suggestion and tried to flash it with TWRP. No error was given, but when I tried to restart, TWRP told me I had no OS installed. I thought it was strange, so I tried to restart anyway. That's when I got in rescue mode. I can't get into the recovery and I can't use fastboot. What rescue mode shows me is:
RESCUE MODE
Attention!
Please update system again
Update User Guide:
*link*
*android avatar*
Error!
Func NO: 10 (boot image)
Error NO: 2 (load failed!)
Pressing the three buttons, I'm able to force an update. The problem is I can't find a firmware that doesn't get rejected. With Lollipop firmwares, it starts to install, but it fails at 12%. With Marshmallow ones, the installation process doesn't even start.
What can I do to make it work again? I'm very sad because this phone was gifted to me a couple of days ago and I already messed it up. I don't even know how to turn it off.
What can I do to get in fastboot mode? At that point, what should I do to flash the stock firmware? Or maybe do I need to find the first stock firmware ever installed into this phone to make the forced update work?
Please, I need help. Thank you in advance!
P.S. The phone's model is ALE-L21. I live in Italy, so I assume it's a European version.
Did you managed to fix this?
Jhon_Locke said:
Did you managed to fix this?
Click to expand...
Click to collapse
Not yet, but I'm working on it. I found out that the device is recognized by my PC if I follow these steps:
1. Connect the phone to the PC and wait for it to go in rescue mode;
2. Wait until the notification LED stops to blink;
3. Disconnect the USB cable;
4. Press volume - and power button;
5. Reconnect the cable.
At that point, the screen turns black and the phone is recognized as "㌲㔴㜶㤸". I installed the drivers and now it's recognized as "HUAWEI USB COM 1.0". I should be able to reflash the partitions and make my phone work again, but I'm still trying to understand how to do it correctly.
Any help is appreciated!
ErikChimello said:
Not yet, but I'm working on it. I found out that the device is recognized by my PC if I follow these steps:
1. Connect the phone to the PC and wait for it to go in rescue mode;
2. Wait until the notification LED stops to blink;
3. Disconnect the USB cable;
4. Press volume - and power button;
5. Reconnect the cable.
At that point, the screen turns black and the phone is recognized as "㌲㔴㜶㤸". I installed the drivers and now it's recognized as "HUAWEI USB COM 1.0". I should be able to reflash the partitions and make my phone work again, but I'm still trying to understand how to do it correctly.
Any help is appreciated!
Click to expand...
Click to collapse
fastboot detects your device when you plug it into your computer?
I mean, if you run "fastboot devices" it shows your phone?
I've had this same problem but with an P8 Lite 2017, after flashing some ROM that supposedly was the stock one and trying to flash recovery I ended up with my phone bootlooping into rescue mode, I was able to "bypass" this thing rebooting my phone like crazy, seriously like after 20 reboot it finally booted into the damn ROM and I never touched the phone again. Sometimes when the phone ran out of battery and tried to power it on the phone booted into rescue mode and again after some reboots it booted to Android but now I want to install a custom ROM or at the very least root this damn phone so that's why I'm asking you if you have solved this, if you do then probably if I follow the same steps I would be able to fix that screen, hopefully.
If you are able to flash something start with flashing all recoveries your update.app has, maybe that's the problem (at least in my phone it is).
Jhon_Locke said:
fastboot detects your device when you plug it into your computer?
I mean, if you run "fastboot devices" it shows your phone?
I've had this same problem but with an P8 Lite 2017, after flashing some ROM that supposedly was the stock one and trying to flash recovery I ended up with my phone bootlooping into rescue mode, I was able to "bypass" this thing rebooting my phone like crazy, seriously like after 20 reboot it finally booted into the damn ROM and I never touched the phone again. Sometimes when the phone ran out of battery and tried to power it on the phone booted into rescue mode and again after some reboots it booted to Android but now I want to install a custom ROM or at the very least root this damn phone so that's why I'm asking you if you have solved this, if you do then probably if I follow the same steps I would be able to fix that screen, hopefully.
If you are able to flash something start with flashing all recoveries your update.app has, maybe that's the problem (at least in my phone it is).
Click to expand...
Click to collapse
No, it doesn't show anything if I write that command...
I guess mine won't ever boot into the rom because it seems like there's no system installed. I made some researches and found out there are some softwares that let you reflash the partitions IF the phone is recognized as "HUAWEI USB COM 1.0". I'm still trying to figure out how to do it correctly though. I feel like if I do something wrong, then my phone won't probably turn on again.
In your case, you should be able to flash a custom rom without any issue. You just have to be very careful and inform you as much as you can: I don't want your phone to end up like mine?. Anyway, it seems pretty hard to go back to the stock rom, so think about it before you flash a custom rom. Also, make a Nandroid Backup is very important.
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