Related
Phone specs:
Samsung Galaxy S3 Verizon SCH-i535
It was already running KitKat 4.4.2 before I rooted
This is my first time rooting and flashing ROMs to my Samsung Galaxy s3 and I have bricked it. I'm pretty sure it can be salvaged but have yet to find anything that works.
I have written the long version for those who need it, but the short version is that I screwed up and can no longer boot into recovery mode or normal mode, I'm not even sure if Download mode is working, and my device isn't recognized by Kies or Odin on my PC so I cannot yet do a recovery from there.
As of now my phone only boots into Odin Mode and gives the following info:
ODIN MODE
PRODUCT NAME: SCH-I535
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: OFFICIAL
QUALCOM SECUREBOOT: ENABLE
BOOTLOADER AP SWREV: 2
and displays the yellow triangle error and says: Firmware upgrade encountered an issue. Please use Software repair Assistant & try again.
I tried to use Samsung Kies which has an emergency firmware tool but my device will not connect and become recognized by the program.
This is pretty much where I'm stuck.
Keep reading if you need additional info.
Steps leading up to problem:
I was able to Root the device succesfully
I then downloaded the latest CM11 package (cm-11-20140217-NIGHTLY-d2vzw.zip) and Gapps
I also downloaded the TWRP recovery img (openrecovery-twrp-2.7.1.0-d2vzw.img)
Once I had these downloaded I got the app [ROOT] Rashr - Flash Tool
I opened the app and tried to do a backup but I'm pretty sure it failed, or at least it said it failed. I couldn't find out how to check, but was not worried since I have already backed up my important files to the verizon cloud.
On the app I went to recover using other file and found the TWRP recovery img I downloaded.
From here I booted into recovery manually, but it did not bring up the TEAMWIN screen for TWRP like I've seen in other video tutorials so I rebooted into normal mode went to the Rashr app again and followed the prompt to do a Recovery boot using the TWRP img.
THIS IS WHERE THE PROBLEMS BEGAN:
It began to lead into recovery mode but it gave a message that said something along the lines that I have tried installing a custom OS and to take my phone to the nearest verizon store.
I turned it off and tried to boot back normally but got the same error.
I tried to boot into Download mode and was successful! So I thought yaay!
Read a tutorial to reload a stock version of android here: http://forum.xda-developers.com/showthread.php?t=2586319
I followed all the steps but when i got to 7. which said You should see your phone under ID:COM (you should also see it has been added in message) I was not seeing my phone there. I figured it may be OK since I was able to install the drivers so that meant the USB was working so I went ahead and ran Odin to recover Jelly Bean 4.3 onto the device.
My thoughts and guesses as to what the problem is:
I think that it may be because I was already running 4.4.2 and/ or didn't have the proper bootloader when I tried to do the TWRP recovery.
Am I on the right track? Thanks for any help!
Please ask. In correct forum this is int'l s3 (i9300) forum
Let me start off by saying I have already scoured this forum and other sources for a solution to this problem. I should add that I am somewhat bound by the confines of my experience, also.
Like many others here, my Samsung S4 mini GT-I9195 is stuck in a boot loop, unable to get into recovery mode. It can get to download mode, but is not recognized by my PC.
Things I've done so far:
1. tried to boot in recovery mode - doesn't work, says "Recovery starting..." then restarts into boot loop
2. checked battery - not it
3. dissasembled phone and checked power button - works fine
4. tried Samsung Kies - "Device is not responding. To resolve the issue, reboot the device." - no can do (note that I only just installed Samsung Kies on my PC for the first time after the boot loop started)
5. flashed firmware using Odin - PASS! - still in bootloop w/no recovery mode
6. flashed firmware again using Odin w/Auto-Reboot unchecked - PASS! - then attempted to reboot into recovery - no go, still in bootloop w/no recovery mode
The firmware I successfully flashed was Poland/T-Mobile version 4.4.2 downloaded from sammobile.
The one thing I have NOT tried is to repartition the pit file. Would this possibly make any difference? If it's worth a try, can I do this using the tar.md5 package above, or do I need a separate .pit file and if so, how do I know I have the right one???
After doing a little reading, I downloaded CSB_signed_SERRANOLTE_ONEPIT_OPEN_130523.pit, which was included in a 'repair firmware' .zip file that also included separate bootloader, code, csc and modem files. I actually did try flashing those files (except for the pit file) and that failed (of course) with error "Device 2, Binary 1", so I flashed the firmware above again and it passed again.
What else?
- Phone is not rooted
- I have no idea if USB debugging is turned on or not
- I was doing nothing with the phone when it first died. I figured the battery might have somehow rapidly drained to zero even though it should have been around 70%. I had last touched the phone about an hour earlier, to shut off my alarm. I tried plugging in to wall charger but phone would not turn on even after an hour or more of charging. I really don't remember exactly how or when the bootloop started.
ODIN MODE
PRODUCT NAME: GT-I9195
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
CSB-CONFIG-LSB:0x30
BOOTLOADER AP SWREV: 2
WRITE PROTECTION: Enable
Anyone out there feel like helping out a noob today?
i have same problem
Actually , only one diferrent
KNOX WARRANTY VOID: 0x1
exactly same ,but i tried with pit 2 pit files and 2 diferent roms , and no result. Pleace help us!!!
I'm just going to leave this here in case anyone of you encounters this problem after modifying files in the system or after flashing custom ROMs. Do note that this fix does not remove the error, but instead bypasses it (for those without EFS backup) and enables the system to boot up normally (installs SuperSU as well). Also, as this requires the use of Odin, devices running MacOS or OSX are not supported.
An alternative (and easier) method has been discovered (refer to post #4 for more details)
Prerequisites:
1) TWRP recovery (https://drive.google.com/open?id=0B6QXDUz9wzc9YWcyZklybmZLc0k)
2) dm-verity bypass (https://drive.google.com/open?id=0B6QXDUz9wzc9Wk1ra0hKYVJtT1k)
3) Odin (https://drive.google.com/open?id=0B6QXDUz9wzc9c3BxYzdBNXhvbnc)
Steps (please follow the steps accordingly in order):
1) Place your phone in D/L mode
- Ensure device is fully turned off by pressing the volume down and power button
- Hold the volume down, home, and power button until a blue warning screen appears
- Press once on the volume up button
- Connect your device to your computer
2) Flash TWRP onto your device
- Open Odin and click on the "AP" tab, and then directing to the location of the TWRP recovery (TWRP_3.0.2.tar)
- Click on the "Options" tab and untick the option "Auto Reboot" [DO NOT TICK ANYTHING ELSE]
- Click on "Start" until Odin says "PASS!"
3) Reboot device into TWRP and flash the bypass zip
- Hold the volume down and power down button until the screen turns off
- Then, hold the volume up, home, and power button until "Set Warranty Bit : recovery" appears at the top of the screen
- Click on "Advanced", followed by "ADB Sideload" and ensure that "Wipe Dalvik Cache" and "Wipe Cache" is ticked, then swipe the bar at the bottom to start sideload
- Using the command prompt, type "adb sideload dm-verity bypass.zip" and wait till it completes
- Click on "Reboot System" after it completes, and your system should be able to boot
Possible errors which you may have encountered:
1) Odin does not detect my device
-- [You will need to install the device driver]
> Download the driver at https://drive.google.com/open?id=0B6QXDUz9wzc9LU9FclQ5WjNWRFk and install it.
2) My device does not boot into recovery after flashing via Odin
-- [System was trying to boot instead of recovery and had ignored the custom recovery after that]
> Go back to step 1) and repeat again
What is ADB and where can I get it?
> The installer is available for download at https://drive.google.com/open?id=0B0MKgCbUM0itNVB1elljU2NPR0k
> Run the installer and type "Y" for every prompt
> Open the command prompt (On your keyboard, press the windows key followed by the "R" key, then type "cmd" in the window and press enter
> Type "cd C:\adb" and you may continue with the steps (do note that C: is the mounted letter of your root drive which may be different from yours)
"* cannot read 'dm-verity bypass.zip *" appears after I entered the command
-- [ADB cannot read the file as the file cannot be found]
> Copy the dm-verity bypass.zip into your ADB folder, or after typing "adb sideload ", drag the dm-verity bypass.zip into your command prompt window and then pressing enter.
Do notify me immediately if there are any errors. Thank you and good luck!
Thanks to @KingWilliams for the dm-verity bypass zip which was present in one of your ROMs.
Q&A
Will OTA updates still work?
> No, the phone will detect that files has been modified and thus OTA updates are stopped. Updates will have to be carried out manually.
NIce Info Thanks, btw is it work on Marshmallow or Lollipop j500f ?
NIce Info Thanks, btw is it work on Marshmallow or Lollipop j500f
Click to expand...
Click to collapse
Should work on both versions but would you mind trying out a simpler and better method instead? It works fine on my device but I am unsure if it works on other models/variants. This method keeps the system status official and even enables OTA updates.
The guide below encompasses the updated method. Do note that as the guide is still being tested and is not an official method, I am assuming that all necessary drivers are installed correctly on your computer and that you have the knowledge and experience to work through the steps as these prerequisites are not included in this guide.
1) Download SamFirm (https://forum.xda-developers.com/attachment.php?attachmentid=3803841&d=1467715462), extract and then run the application.
2) After checking the "Auto" and "Binary Nature" box, type in your model (in your case, SM-J500F) and your region (refer to http://samsung-updates.com/device/?id=SM-J500F if you need help identifying your region) before clicking on "Check Update".
2.1) The application should now be able to detect a firmware saying (for example)
Code:
SamFirm v0.3.6.0
Checking firmware for SM-J500F/TGY/J500FZHU1API2/J500FZZH1API2/J500FZHU1API2/J500FZHU1API2
Model: SM-J500F
Version: J500FZHU1API2/J500FZZH1API2/J500FZHU1API2/J500FZHU1API2
OS: Lollipop(Android 5.1.1)
Filename: SM-J500F_1_20161018133014_hz4nve666g_fac.zip.enc4
Size: 1060126192 bytes
LogicValue: 0us57tdgetwzs2jy
3) Before clicking on "Download", ensure that the option "Decrypt automatically" is checked. The "Check CRC32" option is optional.
4) Once the application is done downloading and decrypting the firmware image, extract it.
5) Using Odin, flash BL, AP, CP, CSC and once it reboots and the error pops up, boot the phone back to the Download Mode.
6) Using Odin, flash AP only (untick BL, CP and CSC checkboxes).
The phone should now boot up normally into the system. Do report the results here for further analysis. Thank you!
Thanks mate, i'll try it :highfive:
Rizzed said:
Should work on both versions but would you mind trying out a simpler and better method instead? It works fine on my device but I am unsure if it works on other models/variants. This method keeps the system status official and even enables OTA updates.
The guide below encompasses the updated method. Do note that as the guide is still being tested and is not an official method, I am assuming that all necessary drivers are installed correctly on your computer and that you have the knowledge and experience to work through the steps as these prerequisites are not included in this guide.
1) Download SamFirm (https://forum.xda-developers.com/attachment.php?attachmentid=3803841&d=1467715462), extract and then run the application.
2) After checking the "Auto" and "Binary Nature" box, type in your model (in your case, SM-J500F) and your region (refer to http://samsung-updates.com/device/?id=SM-J500F if you need help identifying your region) before clicking on "Check Update".
2.1) The application should now be able to detect a firmware saying (for example)
Code:
SamFirm v0.3.6.0
Checking firmware for SM-J500F/TGY/J500FZHU1API2/J500FZZH1API2/J500FZHU1API2/J500FZHU1API2
Model: SM-J500F
Version: J500FZHU1API2/J500FZZH1API2/J500FZHU1API2/J500FZHU1API2
OS: Lollipop(Android 5.1.1)
Filename: SM-J500F_1_20161018133014_hz4nve666g_fac.zip.enc4
Size: 1060126192 bytes
LogicValue: 0us57tdgetwzs2jy
3) Before clicking on "Download", ensure that the option "Decrypt automatically" is checked. The "Check CRC32" option is optional.
4) Once the application is done downloading and decrypting the firmware image, extract it.
5) Using Odin, flash BL, AP, CP, CSC and once it reboots and the error pops up, boot the phone back to the Download Mode.
6) Using Odin, flash AP only (untick BL, CP and CSC checkboxes).
The phone should now boot up normally into the system. Do report the results here for further analysis. Thank you!
Click to expand...
Click to collapse
excuse me, i've tried this method but when i boot the phone to the recovery mode, an error message still show (Device does nit have DRK (Device Root Key), contact to SW PL please flash ENG binary then install DRK), any suggestion ?
dv6661 said:
excuse me, i've tried this method but when i boot the phone to the recovery mode, an error message still show (Device does nit have DRK (Device Root Key), contact to SW PL please flash ENG binary then install DRK), any suggestion ?
Click to expand...
Click to collapse
Sorry about that and for wasting your time. In my original thread, I stated that this method does not eradicate the problem completely but simply bypasses it. The guide that I had requested you to try had two differences - sets the system status to official and enables OTA updates. Now that I think of it, this method is only useful for devices that does not have a workable TWRP/CWM recovery yet, or to give people a peace of mind that their system is official and unmodified. Since entering the recovery mode resurfaces this problem , this method is more or less useless as OTA updates are installed in recovery mode. All updates would need to be done manually via Odin/Smart Switch.
You got to admit this method is simpler and easier though! Could I ask does this method work? Did your phone boot up normally? Thank you.
Rizzed said:
Sorry about that and for wasting your time. In my original thread, I stated that this method does not eradicate the problem completely but simply bypasses it. The guide that I had requested you to try had two differences - sets the system status to official and enables OTA updates. Now that I think of it, this method is only useful for devices that does not have a workable TWRP/CWM recovery yet, or to give people a peace of mind that their system is official and unmodified. Since entering the recovery mode resurfaces this problem , this method is more or less useless as OTA updates are installed in recovery mode. All updates would need to be done manually via Odin/Smart Switch.
You got to admit this method is simpler and easier though! Could I ask does this method work? Did your phone boot up normally? Thank you.
Click to expand...
Click to collapse
yes my phone just boot up normally, the only problem is when i entering recovery mode there's a message "dm-verity need to check verification failed drk first"
i fixed it by mount /system and it worked on j500f .
s10gopal said:
i fixed it by mount /system and it worked on j500f .
Click to expand...
Click to collapse
Are you sure about that? This error only appears when the /efs partition is corrupted.
100%
https://source.android.com/security/verifiedboot/
s10gopal said:
100%
https://source.android.com/security/verifiedboot/
Click to expand...
Click to collapse
Will test it out later on my device.
I have a question. Can I take a DRK backup from one phone and repair another? I have a working Galaxy S6 64gb, and a Galaxy S6128GB that has DRK issue.
Can't Flash TWRP, FRP lock :/
Hi, I have the dm-verification failed problem, but I can't flash twrp because of the FRP lock. Any solution? thanks
_ale33_ said:
Hi, I have the dm-verification failed problem, but I can't flash twrp because of the FRP lock. Any solution? thanks
Click to expand...
Click to collapse
Got to developer settings and tap oem lock on and it should fix your problem.
Hello.
My phone is a Samsung Note 5. 64gb, SM-N9208 ( Taiwan ).
Many many thanks for this post! I have trawled the net for weeks and weeks to find a solution for this ridiculous dm-verity, DRK missing fiasco. I have managed to fix it thanks to your instructions. I understand that this is a work around, don't mind that one bit! But should anyone have a solution to get rid of the problem permanently, you will be an even bigger hero. Let me know if anyone does. Best Regards. Ian.
JaanZZ said:
Got to developer settings and tap oem lock on and it should fix your problem.
Click to expand...
Click to collapse
there's a problem, a mobile go backup sent the device in bootloop, can't boot, only stock recovery or download mode available and i need to backup sensible data.
witty2309 said:
Hello.
My phone is a Samsung Note 5. 64gb, SM-N9208 ( Taiwan ).
Many many thanks for this post! I have trawled the net for weeks and weeks to find a solution for this ridiculous dm-verity, DRK missing fiasco. I have managed to fix it thanks to your instructions. I understand that this is a work around, don't mind that one bit! But should anyone have a solution to get rid of the problem permanently, you will be an even bigger hero. Let me know if anyone does. Best Regards. Ian.
Click to expand...
Click to collapse
Glad that I could help. I suppose you used the TWRP method to recover your device?
_ale33_ said:
there's a problem, a mobile go backup sent the device in bootloop, can't boot, only stock recovery or download mode available and i need to backup sensible data.
Click to expand...
Click to collapse
Perhaps the system files are corrupted. Try flashing the AP file (not HOME file) in Odin and you should be good to go.
Jamessr79 said:
I have a question. Can I take a DRK backup from one phone and repair another? I have a working Galaxy S6 64gb, and a Galaxy S6128GB that has DRK issue.
Click to expand...
Click to collapse
Really sorry for the late reply but in case you have not found an answer yet, no it's not possible (even if it is possible it would be considered illegal - duplicate IMEI).
Hi,
I can't use my tablet anymore tried Odin to re-install the origin firmware "SM-T825Y_1_20180122165040_zf84f94qoe_fac.zip" (new android 8 stock ROM) but it fails, Odin shows the transfer has PASSED but I still get this message in the screen:-
"Security Error: This device has been flashed with unathorised software & is locked.
Call your mobile operator for additional support. "
I wasn't planning flashing a custom ROM the only thing I did is put OEM Lock on, not sure why I did that.
When I put in Download Mode it shows this in the screen:-
ODIN MODE [High Speed]
PRODUCT NAME: SM-T825Y
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
FAP LOCK: ON
OEM LOCK: ON
DID: 03EA1E00AE16
WARRANTY VOID: 0x1 (Ox20C)
QUALCOM SECUREBOOT: ENABLE
AP SWREV: B3 (1, 1, 1, 1, 1) K2 S2
SECURE DOWNLOAD: ENABLE
CCIC: S2 MM005 HW: 4
BOOT: 6 MAIN: DS
Regards,
Sal.
1. It's FRP not FAP ya perv.
2. Reflash firmware with odin, do not go into download mode afterwards before 3.
3. The rest watch this video carefully, and next time you want to leave your device stock, leave it stock, if you want to install a custom rom or twrp, do not have auto reboot ticked.
4. here is link ---> https://www.youtube.com/watch?v=o0T-CR-KpfM
I did reflash with odin but I still get this message "Security Error: This device has been flashed with unathorised software & is locked.
Call your mobile operator for additional support. " There is another small message on top , "Custom binary blocked by FRP. (boot.img)"
Odin tells me its PASSED but the Tablet still says its locked FRP and OEM locked .
In download mode I am getting same info.
I just went to the Samsung Shop and they fixed it for free, they said they just put a new firmware not sure how they did it but I tried it myself with latest firmware but I couldn't get rid of the lock, I am missing something? like software? or just not enough info about about getting rid of locks?
I had the same issue after i installed a Xposed module. Had to reflash Pie Bootloader and Rom via odin. Now it boots, but i can't flash twrp anymore... It always fails.
I have an Android device supplied by my government for students and secured by Samsung Knox. However & unfortunately, I forgot the security pattern of the device and I want to hard reset it to access it again. But Knox prevents factory reset by all the ways :/
I have tried entering the pattern in a wrong way 20+ times but it still refuses to achieve a factory reset. I have also tried booting into Android recovery but the factory reset option says MDM disallows factory reset.
Also Google's Find My Device can't even detect the device so I can't reset it using Google's Find My Device. And developer options are disabled by Knox too so I can't do it using adb
I know that I have made it complex but its the truth and I was wondering if someone knows any way or PC tool to hard reset without USB debugging, or a PC tool that can enable USB debugging.
I don't want to flash ROMs because they will erase Knox which I shouldn't erase :/
Any help would be appreciated.
hard reset of a device with secure knox
I have exactly the same problem.
Can you share the solution if you found one?
Thanks.
MatrixMario012 said:
I have an Android device supplied by my government for students and secured by Samsung Knox. However & unfortunately, I forgot the security pattern of the device and I want to hard reset it to access it again. But Knox prevents factory reset by all the ways :/
I have tried entering the pattern in a wrong way 20+ times but it still refuses to achieve a factory reset. I have also tried booting into Android recovery but the factory reset option says MDM disallows factory reset.
Also Google's Find My Device can't even detect the device so I can't reset it using Google's Find My Device. And developer options are disabled by Knox too so I can't do it using adb
I know that I have made it complex but its the truth and I was wondering if someone knows any way or PC tool to hard reset without USB debugging, or a PC tool that can enable USB debugging.
I don't want to flash ROMs because they will erase Knox which I shouldn't erase :/
Any help would be appreciated.
Click to expand...
Click to collapse
See if you can enter recovery mode
prashantp01 said:
See if you can enter recovery mode
Click to expand...
Click to collapse
I can enter "safe mode" but even there the tablet ask me for the password I haven't got in order to switch off the flight mode that prevents any attempt to locate the smartphone from the Samsung remote service.
Secured Knox prevents hard reset.
No password + flight mode on => Do I throw an almost new device to the bin?
There should be a way, I cannot imagine there is not way around this.
Watch this video: https://www.youtube.com/watch?v=6t5gMP4b7CY&feature=emb_rel_end
Odin mode is disabled by administrator
I don't know how could it be possible
so when pressing power button, volume down and home all together (samsung galaxy tab A sm-t585)
the device is ignoring me completely and boot normally into android
I need to flash another official firmware.
pleeeeeeease , can anyone give me a working method to flash that firmware.
Thanx in advance
you are forced to go to a samsung outlet to apply for a warranty
Anyone find a solution to this?
Update for posterity. I did find a way around this. You essentially have to re-flash your device - which isn't difficult, but it will result in losing all data on the device.
1. Enter download mode by holding vol+, vol- & power keys while plugging in your phone via USB to your computer (windows machines only). This must be done from a powered off status.
2. Download Odin
3. Download OEM firmware for your device (Samfirm or Firja tools can help with this)
4. Download Samsung USB drivers
5. With all of these tools and with your firmware obtained, go into download mode and flash your device.
6. Once complete, the device will format itself (you will lose all data) and boot into initial configuration mode where you can set up you device as if it were new.
wxo said:
Update for posterity. I did find a way around this. You essentially have to re-flash your device - which isn't difficult, but it will result in losing all data on the device.
1. Enter download mode by holding vol+, vol- & power keys while plugging in your phone via USB to your computer (windows machines only). This must be done from a powered off status.
2. Download Odin
3. Download OEM firmware for your device (Samfirm or Firja tools can help with this)
4. Download Samsung USB drivers
5. With all of these tools and with your firmware obtained, go into download mode and flash your device.
6. Once complete, the device will format itself (you will lose all data) and boot into initial configuration mode where you can set up you device as if it were new.
Click to expand...
Click to collapse
Did you success flash fw ?
after finish flashing , any authentication required ?
jobzsparrow said:
Did you success flash fw ?
after finish flashing , any authentication required ?
Click to expand...
Click to collapse
Nope. Phone works as if it were new out of the box.
wxo said:
Update for posterity. I did find a way around this. You essentially have to re-flash your device - which isn't difficult, but it will result in losing all data on the device.
1. Enter download mode by holding vol+, vol- & power keys while plugging in your phone via USB to your computer (windows machines only). This must be done from a powered off status.
2. Download Odin
3. Download OEM firmware for your device (Samfirm or Firja tools can help with this)
4. Download Samsung USB drivers
5. With all of these tools and with your firmware obtained, go into download mode and flash your device.
6. Once complete, the device will format itself (you will lose all data) and boot into initial configuration mode where you can set up you device as if it were new.
Click to expand...
Click to collapse
This procedure didn't work for me.
In order to factory reset, before flashing the stock firmware/ROM, I had to flash the TWRP and wipe everything.
Followed this procedure for my galaxy tab:
[RECOVERY] TWRP 2.8.3.0 for Galaxy Tab 4 8 inch
Support is discontinued. Between the 6 different variants that I made this recovery for, it has been downloaded less than 500 times total over a 2 month period. That tells me that this device is simply not popular enough for continued support...
forum.xda-developers.com
It worked fine. Once wiped through recovery TWRP, I flashed the stock ROM and everything was fine and factory reset.
Unfortunately before starting I tried an auto root procedure but Knox recognized and locked everything (so the counter now is 0x1).
ahmedgeddo said:
Odin mode is disabled by administrator
I don't know how could it be possible
so when pressing power button, volume down and home all together (samsung galaxy tab A sm-t585)
the device is ignoring me completely and boot normally into android
I need to flash another official firmware.
pleeeeeeease , can anyone give me a working method to flash that firmware.
Thanx in advance
Click to expand...
Click to collapse
You can get to Odin mode with knox. Message me back and I’ll explain. You basically trick the device. Does it have removable battery?
I’ve done it on dozens of Xcover pro devices.
Simple Simon
Whiteninja73 said:
אתה יכול להגיע למצב אודין עם נוקס. שלח לי הודעה ואני אסביר. אתה בעצם מרמה את המכשיר. האם יש לו סוללה נשלפת?
עשיתי את זה על עשרות מכשירי Xcover pro.
סיימון פשוט
Click to expand...
Click to collapse
Hey friend
You say you can get into Odin mode with active knox?
I tried dozens of options without success, I would be happy if you explain to me what your solution is (my device without a removable battery ...)
klhd said:
This procedure didn't work for me.
In order to factory reset, before flashing the stock firmware/ROM, I had to flash the TWRP and wipe everything.
Followed this procedure for my galaxy tab:
[RECOVERY] TWRP 2.8.3.0 for Galaxy Tab 4 8 inch
Support is discontinued. Between the 6 different variants that I made this recovery for, it has been downloaded less than 500 times total over a 2 month period. That tells me that this device is simply not popular enough for continued support...
forum.xda-developers.com
It worked fine. Once wiped through recovery TWRP, I flashed the stock ROM and everything was fine and factory reset.
Unfortunately before starting I tried an auto root procedure but Knox recognized and locked everything (so the counter now is 0x1).
Click to expand...
Click to collapse
The first recommendation did not work for me, too. After the tab reboots, it says its installing the updates but up to 32% only, then it erases, then it goes back to the same problem.
Tried your quoted solution. However, upon installing twrp, it says it cant install because of frp lock. How do i go about it? Please help....
Deleted member 1890170 said:
Watch this video:
Click to expand...
Click to collapse
sm-g525f , tried to flash andriod and succeded but knox persists,
there is no TWRP file for this fone.
so I Tried this, followed closely to extract but CM file not exist.
COMBINATION_FAC_FAR0_G525FXXU1AUB1
lots of other bin files in there to try, any suggestions?
sm-g525f , tried to flash andriod and succeded but knox persists,
there is no TWRP file for this fone.
so I Tried this, followed closely to extract but CM file not exist.
COMBINATION_FAC_FAR0_G525FXXU1AUB1
lots of other bin files in there to try, any suggestions?
wxo said:
Update for posterity. I did find a way around this. You essentially have to re-flash your device - which isn't difficult, but it will result in losing all data on the device.
1. Enter download mode by holding vol+, vol- & power keys while plugging in your phone via USB to your computer (windows machines only). This must be done from a powered off status.
2. Download Odin
3. Download OEM firmware for your device (Samfirm or Firja tools can help with this)
4. Download Samsung USB drivers
5. With all of these tools and with your firmware obtained, go into download mode and flash your device.
6. Once complete, the device will format itself (you will lose all data) and boot into initial configuration mode where you can set up you device as if it were new.
Click to expand...
Click to collapse
SM-G525F. yup, can flash android BUT knox persists.
seems TWRP file needed but none exists.
Tried the video above in post 5 but there is no CM file.
Any Ideas?
Whiteninja73 said:
You can get to Odin mode with knox. Message me back and I’ll explain. You basically trick the device. Does it have removable battery?
I’ve done it on dozens of Xcover pro devices.
Simple Simon
Click to expand...
Click to collapse
Have you seen this thread? Bunch of people trying to access the xcover pros they paid for after working for walmart:
Cant get Walmart Samsung Galaxy XCover Pro into download mode
So I worked for Walmart for a while. They gave me this free phone. See below. https://www.cbsnews.com/news/walmart-free-smartphones-employee-schedules/ The phone was locked out by Walmart for inactivity. (See image for details) I fixed that...
forum.xda-developers.com
Whiteninja73 said:
You can get to Odin mode with knox. Message me back and I’ll explain. You basically trick the device. Does it have removable battery?
I’ve done it on dozens of Xcover pro devices.
Simple Simon
Click to expand...
Click to collapse
I have 2 X cover pro devices that are knox locked. Could you explain how you manage to trick the device and get to Odin mode?