The Problem:
Galaxy S2 (9100G only) + Usb JIG and no reset of the counter...
The Solution:
Downgrade bootloader and the use JIG to reset the counter
Procedure (credits to: Street79)
1- reboot into download mode
2- start odin
3- connect your phone
4- extract the .zip-file
5- load the .tar-file as PDA
6- uncheck 'Auto Reboot'
7- check 'Phone Bootloader Update'
8- start flashing
9- wait for the message '<OSM> All threads completed. (succeed 1 / failed 0)' disconnect your phone
10- remove battery
11- connect the USB JIG
12- insert battery
13- wait for the massage 'ERASING DOWNLOAD INFORMATION SUCCEEDED.'
14- remove USB JIG
15- hold power-button until your phone reboots
Click to expand...
Click to collapse
Tested by me and Street79
2- Is it dangerous? Flashing wrong bootloader seems to be...
Click to expand...
Click to collapse
Yes, Flashing a new bootloader is very risky. If you flash a wrong one, or something goes wrong during flashing, say goodbye to your phone. If you're on ICS you can try triangle away to reset flash counter (i only tried on GT-I9100 make sure that you can run on GT-I9100G)
What procedure u followed?
Sent from my GT-I9100G using XDA App
AFAIK, bootloader is not ROM based and can be flashed. I did it on my SGS2 seeing JIG would not reset my counter. Flashed while on GB 2.3.6 custom ROM and IT WORKS as my JIG is reseting the counter just fine afterwards, I personally can't tell if it works for ICS builds but people on web reported it did (google is your friend). However, as with all flashing procedures, it is a bit risky... Find chainsfire's ROM thread and download old bootloader, read around and use CWM... well, GL.
So to resume briefly on your questions:
1- Have any one done this procedure?
2- Is it dangerous? Flashing wrong bootloader seems to be...
3- Where are these old bootloaders?
Click to expand...
Click to collapse
1. Yes
2. There is no wrong bootloader - just old and "new" ones.
3. Chainfire's ROM thread
Example of succesful testimony, see here: http://androidforums.com/galaxy-s2-international-all-things-root/518798-siyah-ics-kernel-v3-x-2.html
or use Triangle away apk by chainfire.
Hope it helps.
well
I think people are making this confuse with 9100 information on a 9100G thread.
Hi,
here you have a bootloader for GT-I9100G which is working with the USB JIG. I have tested it on my own GT-I9100G!
Howto Flash with Odin:
reboot into download mode
start odin
connect your phone
extract the .zip-file
load the .tar-file as PDA
uncheck 'Auto Reboot'
check 'Phone Bootloader Update'
start flashing
wait for the message '<OSM> All threads completed. (succeed 1 / failed 0)'
disconnect your phone
remove battery
connect the USB JIG
insert battery
wait for the massage 'ERASING DOWNLOAD INFORMATION SUCCEEDED.'
remove USB JIG
hold power-button until your phone reboots
must flash boatloader 1st then use jig to reset? lol thats why my jig wont work..
zbuh said:
well
I think people are making this confuse with 9100 information on a 9100G thread.
Click to expand...
Click to collapse
You're absolutely right. I confused i9100 and G versions as I was in a hurry to provide any info available. My bad.
Still, it is the same principle and method to be used on both
Cheers for posters and links!
Street79 said:
Hi,
here you have a bootloader for GT-I9100G which is working with the USB JIG. I have tested it on my own GT-I9100G!
Howto Flash with Odin:
reboot into download mode
start odin
connect your phone
load the file as PDA
uncheck 'Auto Reboot'
check 'Phone Bootloader Update'
start flashing
wait for the message '<OSM> All threads completed. (succeed 1 / failed 0)'
disconnect your phone
remove battery
connect the USB JIG
insert battery
wait for the massage 'ERASING DOWNLOAD INFORMATION SUCCEEDED.'
remove USB JIG
hold power-button until your phone reboots
Click to expand...
Click to collapse
I follow the procedure, but Odin hangs...
maybe a corrupted file?
zbuh said:
I follow the procedure, but Odin hangs...
maybe a corrupted file?
Click to expand...
Click to collapse
You're right, sorry for that! I don't know what was going wrong when I uploaded the file...
I have replaced the attached file. It's now a .zip-file, so you have to extract it first and than flash the .tar-file!
This time I have checked the file and it's working! (I have downloaded the .zip-file, extracted the .tar-file and flashed it to my phone to be sure it's really working!)
Once again: Sorry for that!
Street79 said:
You're right, sorry for that! I don't know what was going wrong when I uploaded the file...
I have replaced the attached file. It's now a .zip-file, so you have to extract it first and than flash the .tar-file!
This time I have checked the file and it's working! (I have downloaded the .zip-file, extracted the .tar-file and flashed it to my phone to be sure it's really working!)
Once again: Sorry for that!
Click to expand...
Click to collapse
Thanks, I'll try again later on...
Hello,
I recently got a used Galaxy S3 I9300. I wanted to install temasek's UNOFFICIAL CM12.1. I already installed CWM on my old Galaxy S2.
Now I got a ridiculous problem; I cannot get CWM or TWRP installed via Odin. This is what I did, in every detail:
a) Turn on USB Debugging (not even sure if necessary)
b) Started in DOWNLOAD-MODE by Voldown+Home+Power
b1) Funnily, it already confirms that I tried to install "Custom Binary Download" 4 times but otherwise is unimpressed. Current binary is still "Samsung Official".
b2) I connect via USB and start ODIN 3.10.7 in Admin mode.
b3) It recognizes the telephone, I have "Auto Reboot" and "F. Reset Time" selected, nothing else. Then I select the .tar I want (i tried "twrp-2.8.6.1-i9300.tar" and "CWM_6.0.4.7_Touch_GT-I9300.tar"), AP box is checked.
b4) I press start, Odin says that everything is fine and signals "Pass".
c) Now, when I start into recovery mode by Volup+Home+Power I still land in the default recovery. This is really annoying.
What am I doing wrong?
Thanks a lot in advance
Greetings
untrue
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).
Request to Thread Mods
May I have this thread moved to the guides section for this device? Thanks!
UPDATE UPDATE UPDATE
I have made a flashable stock recovery! Select AP in Odin and load this file!
INTRODUCTION
This guide is similar to the previous root instructions posted earlier for this device, only this guide does not require debloating or blocking packages.
DISCLAIMER
This method is provided as is, without any form of insurance or responsibility if your phone grows legs and hops off a balcony. Proceed at your own risk!
PREPARATION
You will need the following:
- Samsung Galaxy On5 (SM-S550TL)
- 50% or more battery
- Kingroot version 5.0.5 (Linked at bottom)
- Permissive Boot.tar (Find it here )
- Stock ROM (Find it Here )
- Odin (Latest Version)
- Patience and a cup of coffee
PART ONE: ODIN A
You do not necessarily have to follow this first step, unless you have already been toying around with your On5. Completely power off your device. Now press and hold the [VOL DOWN] [HOME] and [POWER] keys until the warning screen for Odin mode appears. Press [VOL UP] to enter Odin Mode.
With Odin installed and running, confirm that your device has been added. Now load the file named ALL_TFN_S550TLUDU1APG1_S550TLTFN1APG1_CL8482018_QB10267860_REV00_user_low_ship.tar.md5.
Press start and wait for the PASS Signal. WARNING! YOU WILL LOSE ALL PERSONAL DATA AND FILES ON THIS DEVICE!
PART TWO: PHONE PREP
When the phone has booted, proceed through the setup while looking for Google or KNOX popups. Decline any security prompts from Google and at the end of the setup, do not install My KNOX.
Go to your settings from the launcher and select the 'About Phone' option. Look for the field labeled 'Build Number' and tap it until it says 'You are now a developer!'
Go back and you will find the development settings. Enable USB Debugging and Unlock OEM settings.
Now go to Lockscreen and Security and allow unknown sources. Power off your device and go back into Odin mode.
PART THREE: ODIN B
From the Odin window click AP and load the file boot.tar and click start. your device will flash and reboot. Your SE Linux is now set to permissive.
PART FOUR: FINALE
Now install the kingroot 5.0.5 app (kr505.apk) and run it. When the root process starts, do not touch your device unless it freezes, in which case you will pull your battery and retry. If you have adb, and would like to help me make this better, run logcat on the device while it roots. RUN LOGCAT BEFORE YOU BEGIN THE ROOT PROCESS! With luck you should be rooted. No debloating required. If Kingroot asks to disable KNOX, tell it yes.
Very informational we need guides like this more often
Error 404 for boot.tar link
Dre009 said:
Error 404 for boot.tar link
Click to expand...
Click to collapse
I have fixed the link. Google is starting to bug me. I put it on MEGA this time. Enjoy!
HitByAZinger said:
Request to Thread Mods
May I have this thread moved to the guides section for this device? Thanks!
UPDATE UPDATE UPDATE
I have made a flashable stock recovery! Select AP in Odin and load this file!
INTRODUCTION
This guide is similar to the previous root instructions posted earlier for this device, only this guide does not require debloating or blocking packages.
DISCLAIMER
This method is provided as is, without any form of insurance or responsibility if your phone grows legs and hops off a balcony. Proceed at your own risk!
PREPARATION
You will need the following:
- Samsung Galaxy On5 (SM-S550TL)
- 50% or more battery
- Kingroot version 5.0.5 (Linked at bottom)
- Permissive Boot.tar (Find it here )
- Stock ROM (Find it Here )
- Odin (Latest Version)
- Patience and a cup of coffee
PART ONE: ODIN A
You do not necessarily have to follow this first step, unless you have already been toying around with your On5. Completely power off your device. Now press and hold the [VOL DOWN] [HOME] and [POWER] keys until the warning screen for Odin mode appears. Press [VOL UP] to enter Odin Mode.
With Odin installed and running, confirm that your device has been added. Now load the file named ALL_TFN_S550TLUDU1APG1_S550TLTFN1APG1_CL8482018_QB10267860_REV00_user_low_ship.tar.md5.
Press start and wait for the PASS Signal. WARNING! YOU WILL LOSE ALL PERSONAL DATA AND FILES ON THIS DEVICE!
PART TWO: PHONE PREP
When the phone has booted, proceed through the setup while looking for Google or KNOX popups. Decline any security prompts from Google and at the end of the setup, do not install My KNOX.
Go to your settings from the launcher and select the 'About Phone' option. Look for the field labeled 'Build Number' and tap it until it says 'You are now a developer!'
Go back and you will find the development settings. Enable USB Debugging and Unlock OEM settings.
Now go to Lockscreen and Security and allow unknown sources. Power off your device and go back into Odin mode.
PART THREE: ODIN B
From the Odin window click AP and load the file boot.tar and click start. your device will flash and reboot. Your SE Linux is now set to permissive.
PART FOUR: FINALE
Now install the kingroot 5.0.5 app (kr505.apk) and run it. When the root process starts, do not touch your device unless it freezes, in which case you will pull your battery and retry. If you have adb, and would like to help me make this better, run logcat on the device while it roots. RUN LOGCAT BEFORE YOU BEGIN THE ROOT PROCESS! With luck you should be rooted. No debloating required. If Kingroot asks to disable KNOX, tell it yes.
Click to expand...
Click to collapse
The AQC4 firmware can be rooted too, if you want to add that to your post.
https://forum.xda-developers.com/showpost.php?p=74524073&postcount=102
Files are in the above linked post.
mcopeland1003` said:
The AQC4 firmware can be rooted too, if you want to add that to your post.
https://forum.xda-developers.com/showpost.php?p=74524073&postcount=102
Files are in the above linked post.
Click to expand...
Click to collapse
I can't figure out how to root the SM-G550T1 on AQC4. SELinux is permissive, but KingRoot just refuses to work. Did I trip KNOX for nothing?
Freezed at 17%. anyone has any luck?
Hello all,
First of all, I'm posting this here just cause I can't find a thread describing this situation.
***I'M NOT the owner/creator of any file here and is not that easy to find it.
***I'M NOT responsible for any casualities that leads to a bricket phone or else.
***Make sure that you have a backup of all your data that you want to keep.
***On the download link you can find all the files mentioned below.
I advice that if you try to push the recovery.img from others releases, may result a boot loop.
READ ALL THIS THREAD BEFORE START TO DO.
HOW TO SOLVE THE LOOP:
- Run or Install SamFirm software;
- Write the model number and set the region. (You will need to google a little to find out what's the name of yours, mine is ZTO -> Brazil).
- You can fill all the boxes or can check "Auto" to skip it. ("auto" always worked to me).
- And than, click on "Check Update".
***Your mobile don't need to be plugged to do the research.
- If the software find a firmware, UNcheck the option "Check CRC32".
- Download and Decrypt throught the software.
On the download link you can find the release that worked to me, but first, try to find from your region.
BEFORE MAKING MODIFICATIONS, IS NECESSARY TO GO TO (IF IT POSSIBLE):
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK AND USB DEBUGGING FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
- Using any version of Odin v3.09 or higher, connect the device on Download mode and select the firmware on "AP" slot, uncheck the Auto Reboot in Options and hit the start.
- When the flashing finishes, Odin will show a message in green "PASS", remove the battery and unplug the USB cable.
- Reinsert the battery and restart the phone normally.
- Try to use it for how about 20 minutes, letting the update finishes all background tasks. The phone will be very slow but don't worry.
- Restart again when the updates finishes and wait for more 20 minutes with the phone unlocked.
You should pay attention to the battery level after every system reboot.
- Now you are able to flash the recovery.tar.
To install TWRP:
Boot to DOWNLOAD mode.
Flash with ODIN in the AP slot.
Uncheck Auto reboot.
Load the "recovery.tar" into the AP slot and hit start.
When the flashing finishes, Odin will show a message in green "PASS", remove the battery and unplug the USB cable.
Reinsert the battery and press Vol UP + Home + Power Button till the TeamWin Appears.
DON'T do nothing, just restart again after that.
Reboot again in the Recovery mode and install the SuperSU.zip. MUST TO BE 2.82v or higher, if not, you will need to start over.
*** Don't wipe any cache after install the SuperSU.
:highfive: :highfive: :highfive:
Link on the first comment. If you have any link problem, contact me pls.
It's done!
Link to DOWNLOAD!!
https://1drv.ms/f/s!Anl6fvUz6w2rj7BdPneLlaqHctIBPA