Database Users

[Q] TWRP Not Installing

Hey. I have a Canadian Note 4.
I enabled USB Debugging
I chose PDA -> openrecovery-twrp-2.8.1.0-trltecan.img.tar
Auto Reboot/F Reset are the only options enabled
When I flash, it says passed. The software update function on the note doesnt work anymore obviously, but I also cant get into TWRP. When I go to recovery, it says Installing System update and shows regular recovery?
Anyone know why?

Uncheck the reset option and try again.

Hi, did you solve it somehow? Same problem here - tried different versions of ODIN, no luck. Thanks.

Hello
I'm facing the same problem.. Did you find a solution?

Seriously, not anyone that know what is going on? I'm having the same problem after trying to root my Note 4 (910F)
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1100)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/005> Removed!!

- Use ODIN and add in the .tar file into PDA.
- Un-tick Auto Reboot
- Check F.Reset Time (should be the only thing ticked)
- Click start
- The phone will sit on the download mode screen after it has completed
- Unplug the USB cable and pull the battery
- Re-insert the battery and boot straight into recovery (Vol Up+Home+Power)
TWRP should now boot and it will replace the stock recovery as part of it (if you allow it to).

FamousSAS31 said:
- Use ODIN and add in the .tar file into PDA.
- Un-tick Auto Reboot
- Check F.Reset Time (should be the only thing ticked)
- Click start
- The phone will sit on the download mode screen after it has completed
- Unplug the USB cable and pull the battery
- Re-insert the battery and boot straight into recovery (Vol Up+Home+Power)
TWRP should now boot and it will replace the stock recovery as part of it (if you allow it to).
Click to expand...
Click to collapse
Can you elaborate on "if you allow it to"? I've found that if un-tick Auto Reboot and pull the battery as you describe, I can then boot into TWRP but only once.. The next time I run my OS, it just replaces TWRP anyway.

XeroVolume said:
Can you elaborate on "if you allow it to"? I've found that if un-tick Auto Reboot and pull the battery as you describe, I can then boot into TWRP but only once.. The next time I run my OS, it just replaces TWRP anyway.
Click to expand...
Click to collapse
If you have it ticked, I've found the OS will automatically overwrite the recovery again back to stock (or fail and you'll get limited recovery functionality). When leaving it unticked and pulling the battery, I found that as soon as I went back into recovery after flashing TWRP it would load TWRP and install over the stock recovery. From then on it would boot into TWRP everytime without issue.
Not sure why after you've booted into TWRP it's not installing over the top of stock recovery (it's meant to). What version of Android you using? I've done this on 5.1.1 and 6.0.1 and TWRP 2.8.7 and 2.8.6, using a Note 4.

FamousSAS31 said:
If you have it ticked, I've found the OS will automatically overwrite the recovery again back to stock (or fail and you'll get limited recovery functionality). When leaving it unticked and pulling the battery, I found that as soon as I went back into recovery after flashing TWRP it would load TWRP and install over the stock recovery. From then on it would boot into TWRP everytime without issue.
Not sure why after you've booted into TWRP it's not installing over the top of stock recovery (it's meant to). What version of Android you using? I've done this on 5.1.1 and 6.0.1 and TWRP 2.8.7 and 2.8.6, using a Note 4.
Click to expand...
Click to collapse
That's correct, the stock OS will automatically overwrite any recovery that is not stock if the OS is allowed to load, even after Odin shows passed. In this particular case, TWRP was flashed successfully, but the stock OS simply re-flashed the stock recovery as soon as it loads. As you described, one must un-tick Auto Reboot in the options of Odin, which will leave your phone sitting on the download mode screen, then pull the battery, (or if you leave Auto Reboot ticked you can quickly pull the battery immediately after the phone reboots) reinstall the battery and immediately boot into recovery. TWRP will then load, and in my case I was running TWRP 3.0.2-0, which upon first time use prompts the user with the following:
"TWRP has detected an unmodified partition. TWRP can leave your partition unmodified to make it easier for you to take official updates. TWRP will be unable to prevent the stock ROM from replacing from replacing TWRP and will not offer to root your device. Installing zips or performing adb operations may still modify the system partition."
To answer my own question and hopefully anyone else reading this, that query will show only on newer versions of TWRP (sorry, I don't know exactly when it started) but if you see it, know this: it only shows if the system partition is currently untouched. What you want to do the first time you see it is to leave the partition unmodified and immediately use TWRP to perform a nandroid backup. Then reboot TWRP. Now you can allow TWRP to modify the system partition, and if an official OTA comes out that you want to install, you can restore the backup and take the OTA update.
The following is from the TWRP official changelog:
System read only option:
Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.​
I hope that answers any questions.

Better to first root the device and then install recovery via flashify app .
Reporting via N910G

download usb/fastboot. Enable usb debugging, open a cmd prompt with adb. Type "adb reboot fastboot" as the screen turns off hold vol up + power + home

I'm having the exact same problem. Cant find any solutions. Someone Pls help.
Before this my A9pro had twrp then i rooted it and upon restarting it showed 'custom binar locked by arp". Then i flashed stock firmware and the system did an auto update and the version changed.
Now after flashing twrp via odin in the 1st attempt to boot into twrp it shows the twrp page then says system updating and boots into stock recovery. From the 2nd attempt it just says system updating and boots into stock recovery but the boot page shows unlocked icon and says CUSTOM.
pls help

[HELP] SM-G900F stuck in a recovery bootloop

Hi,
I'm from Singapore and I believe I have the international s5 (SM-G900F), at least that's what it says in download mode. My phone was running CM13 nightly and till last night it was working fine. Last night when I charged it, I woke up this morning and my battery was incredibly overheated. I changed my battery and tried booting, but now it gets stuck in a bootloop. I flashed stock 5.0 lollipop from sammobile via odin, but it still is stuck. I can boot perfectly into download mode with the android logo. Here are the details:
PRODUCT NAME: SM-G900F
CURRENT BINARY: Custom
System Status: Custom
Reactivation Lock (KK): OFF
KNOX WARRANTY LOCK: 0x1 (04)
QUALCOMM SECUREBOOT: ENABLE(CSB)
RP SWERV: S1, T1, R1, A1, P1
SECURE DOWNLOAD: ENABLE
UDC START
I would really appreciate any help. Thanks!

Boot into recovery and factory reset, then try booting again
Sounds like the DATA partition got corrupted, or something installed to it did, flashing with ODIN doesn't wipe anything, so you'll still be bootlooped unless you wipe DATA / Factory Reset

When you go from cyanogenmod back to stock samsung firmware, a wipe data / factory reset is required in recovery or else the phone will be stuck in a boot loop or not boot up.

Hi, the problem is I cant access the recovery any more. Every time I hold power, volume up and the home button, it says recovery booting, warranty bit:kernel, kernel is not se android enforcing (the usual) but doesn't actually enter recovery.

imbtrthanu said:
Hi, the problem is I cant access the recovery any more. Every time I hold power, volume up and the home button, it says recovery booting, warranty bit:kernel, kernel is not se android enforcing (the usual) but doesn't actually enter recovery.
Click to expand...
Click to collapse
Flash TWRP 3.0.0.0 with ODIN and wipe from there, then flash stock again
https://dl.twrp.me/klte/twrp-3.0.0-0-klte-klte.img.tar.html

Hi I tried flashing twrp but that didn't work. It doesnt enter recovery, it still just restarts.

Is there any other way I can do a wipe? Through adb or something? Or should I select a specific option in Odin (3.09) ? Like bootloader update, etc or something?

imbtrthanu said:
Hi I tried flashing twrp but that didn't work. It doesnt enter recovery, it still just restarts.
Click to expand...
Click to collapse
Uncheck "Auto Reboot" in ODIN, flash TWRP again, when it completes, disconnect USB and pull the battery to power off the phone
Replace the battery, and boot immediately into recovery with Vol Up & Home & Power

Hi that's not working as well. Should I reflash stock and then flash twrp in the way you suggested?

Try, but something seems wrong because you should be able to flash TWRP with ODIN
Have you got the drivers installed and does ODIN give you a COM port at the top when the phone is in download mode?
You are putting the phone in download mode to flash TWRP right?
Vol Down & Home & Power

Yes I'm using Odin 3.09. I'm flashing via the AP slot. I only have F Reset time checked. My S5 is definitely in downloading mode. Looks similar to this:
http://cdn.androidblog.gs/wp-content/uploads/2014/12/Samsung-Galaxy-S5-Stuck-In-Download-Mode.png
Also, I think the drivers may be the issue here. Could you advise me on how to check and how to fix it? Thanks so much! Also, yes, the COM port lights up

imbtrthanu said:
Yes I'm using Odin 3.09. I'm flashing via the AP slot. I only have F Reset time checked. My S5 is definitely in downloading mode. Looks similar to this:
http://cdn.androidblog.gs/wp-content/uploads/2014/12/Samsung-Galaxy-S5-Stuck-In-Download-Mode.png
Also, I think the drivers may be the issue here. Could you advise me on how to check and how to fix it? Thanks so much! Also, yes, the COM port lights up
Click to expand...
Click to collapse
If the COM port lights up, the drivers are installed and working
Try ODIN 3.10.7, that's the latest version
Code:
https://mega.nz/#!vcIGmBTQ!Yr00OrGvUslQouU9E-zPf4SmpyVwL7mwIjeSG-0EAZg

Hi, that also didn't work. Any other advice?

Use a different PC / USB lead, everything you have tried should have worked fine on a G900F

Hi, I tried using a different PC and USB cable. Still nothing. Could it be because I flashed a different PIT file previously? There was a thread where someone suggested flashing a pit file, so

imbtrthanu said:
Hi, I tried using a different PC and USB cable. Still nothing. Could it be because I flashed a different PIT file previously? There was a thread where someone suggested flashing a pit file, so
Click to expand...
Click to collapse
Didn't you flash the G900F PIT?
Flash this in the PIT section of ODIN along with the stock ROM
http://forum.xda-developers.com/attachment.php?attachmentid=2721101&d=1399024091
Extract to .pit first

Hi, I tried flashing the stock rom with the PIT you gave me but it gave me the following response:
<ID:0/005> FAIL! (Size)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any ideas what I should do now? Also, which stock rom should I be flashing? KK or Lollipop?

I don't know what you've done to your phone, and from your main post, it is definitely a G900F if that is what it says in download mode
Which PIT did you flash the first time? And did it flash successfully?
Any stock ROM should work, but might as well go for Lollipop, I know 100% this one works
Code:
https://mega.nz/#!fVhhzRBC!A79uC8Fgg1mGCZOaujQCzBxcUUN9z_ctVVkigD8ffVM
The only thing I can think of for now is to tell KIES3 to perform a firmware recovery
Code:
http://www.samsung.com/uk/support/usefulsoftware/KIES/
If you already have KIES installed, remove it and try ODIN again, people have reported it interferes with ODIN
If not, install KIES3, go to the firmware recovery setting and see if it can fix your phone
Other than that, it looks like it's going to need someone with knowledge of manual partitioning via adb shell or something, if the phone can enter a mode the PC can use that with
EDIT - You are using a native PC running Windows 7 or later right? Not a mac running Windows? Macs don't install the drivers properly and fail

Yup I'm running Windows 10. I'll try KIES and see if that works!

Which PIT did you originally flash? And did it actually flash?

S7 Edge G935F // Faulty ODIN flash // Stuck in Bootloader [SOLVED]

Hi Guys,
today I wanted to flash the latest Stock ROM for my device via ODIN. I've done this many times before and (thought) I knew what I was doing. It is my third Phone frome the same carrier and none of them were branded/ locked devices before. Unfortunatly I wasn't aware that this particular device was locked.
After downloading the international firmware I tried to install it and ODIN got stuck while writing the system.img. After that my phone did not boot up (of course). After that I downloaded and tried to isntall the firmware of the carrier, but I had the exact same issue. When I turn my device on I get to an error screen which tells me to execute an "emergency recovery" via the Samsung smart switch software. But it too gets stuck on some point and only gets me to an error screen.
FRP hinders me to install a custom recovery and the stock one does not allow any isntallations via ADB or SD card.
My qustion is: Does anyone know how I can install a rom from here?
I know that I had to have made some changes prior to the flashing, but as I said I was not aware and an Idiot for not double checking.
Since it is not bricked yet I suppose there must be an answer but I can't find anything.
Thanks in advance
Edit:
After only installing the stock bootloader, I am autmaticly entering it when I boot my devive. On the bottom of the screen is an error message: "dm-verity verification failed...
E:failed to mount /system (invalid argument)"

Fix
For anyone in the same situation: I fixed it.
In the end all you have to do is flash the firmware with the fitting PIT file. If you firmware consists of multiple files and there is a "HOME"-file, flash it with this one first on the AP slot in ODIN. After that the same again just use the AP file this time.
My phone is up and running again now.

fabivons said:
hi guys,
today i wanted to flash the latest stock rom for my device via odin. I've done this many times before and (thought) i knew what i was doing. It is my third phone frome the same carrier and none of them were branded/ locked devices before. Unfortunatly i wasn't aware that this particular device was locked.
After downloading the international firmware i tried to install it and odin got stuck while writing the system.img. After that my phone did not boot up (of course). After that i downloaded and tried to isntall the firmware of the carrier, but i had the exact same issue. When i turn my device on i get to an error screen which tells me to execute an "emergency recovery" via the samsung smart switch software. But it too gets stuck on some point and only gets me to an error screen.
Frp hinders me to install a custom recovery and the stock one does not allow any isntallations via adb or sd card.
My qustion is: Does anyone know how i can install a rom from here?
I know that i had to have made some changes prior to the flashing, but as i said i was not aware and an idiot for not double checking.
Since it is not bricked yet i suppose there must be an answer but i can't find anything.
Thanks in advance
edit:
After only installing the stock bootloader, i am autmaticly entering it when i boot my devive. On the bottom of the screen is an error message: "dm-verity verification failed...
E:failed to mount /system (invalid argument)"
Click to expand...
Click to collapse
have u solved your problem ? This problem i am facing on the s7edge nougat ? Plz help ?

Hey,
look at the second post I made in this thread. There is described how I got my S7 up and running again. I'm not sure if it is a valid solution since it felt like trial and error to me, but I'm writing this text from my S7 so it might be worth a try!
Good luck!

Fabivons said:
Hey,
look at the second post I made in this thread. There is described how I got my S7 up and running again. I'm not sure if it is a valid solution since it felt like trial and error to me, but I'm writing this text from my S7 so it might me worth a try!
Good luck!
Click to expand...
Click to collapse
y i have done that and the device boots up but some applications force close and when i insert the memory card , the phone gets restarted everytime

Fabivons said:
For anyone in the same situation: I fixed it.
In the end all you have to do is flash the firmware with the fitting PIT file. If you firmware consists of multiple files and there is a "HOME"-file, flash it with this one first on the AP slot in ODIN. After that the same again just use the AP file this time.
My phone is up and running again now.
Click to expand...
Click to collapse
Tell us in detail now.

SjDU said:
Tell us in detail now.
Click to expand...
Click to collapse
"please"
I described everything I did in the posts before.
As soon as you can enter the system again all you need to do is deactivate the locks I was talking about in my first post and perform a full wipe.
After that you can install any ROM you want via ODIN just like you are used to.
If that doesn't work for you, I don't have any answers either.
But again:
Prep work:
1. Download most recent ODIN
2. Download the correct firmware for your carrier (from www.sammobile.com)
3. Download the correct PIT file for your device
4. Put your device in download mode
Process:
1. Extract your firmware if it is a zip
2. Start up ODIN
3. Connect your device and check if it's detected by ODIN
3. Put the PIT file in ODIN
4. Put the "HOME" file of your firmware in the PDA slot of ODIN
5. Press start
6. When finished unplug your device and restart phone and ODIN
7. Reconnect your phone and check if it's detected by ODIN
8. Put all the other files of your firmware + the PIT in the correct slot in ODIN
9. Press start
After that my device booted up but still was, as you described too, a little buggy. So I deactivated FRP, activated USB debugging in the dev options, installed TWRP, performed a full wipe and installed another firmware of my choosing via ODIN (without a PIT file this time).
I am running 7.0 on my device now and it works flawlessly.

Fabivons said:
"please"
I described everything I did in the posts before.
As soon as you can enter the system again all you need to do is deactivate the locks I was talking about in my first post and perform a full wipe.
After that you can install any ROM you want via ODIN just like you are used to.
If that doesn't work for you, I don't have any answers either.
But again:
Prep work:
1. Download most recent ODIN
2. Download the correct firmware for your carrier (from www.sammobile.com)
3. Download the correct PIT file for your device
4. Put your device in download mode
Process:
1. Extract your firmware if it is a zip
2. Start up ODIN
3. Connect your device and check if it's detected by ODIN
3. Put the PIT file in ODIN
4. Put the "HOME" file of your firmware in the PDA slot of ODIN
5. Press start
6. When finished unplug your device and restart phone and ODIN
7. Reconnect your phone and check if it's detected by ODIN
8. Put all the other files of your firmware + the PIT in the correct slot in ODIN
9. Press start
After that my device booted up but still was, as you described too, a little buggy. So I deactivated FRP, activated USB debugging in the dev options, installed TWRP, performed a full wipe and installed another firmware of my choosing via ODIN (without a PIT file this time).
I am running 7.0 on my device now and it works flawlessly.
Click to expand...
Click to collapse
the time when u were fixing your device , you were on marshmallow or nougat ? beacuse i am on nougat and whenever i flash twrp , it stucks there and not booting into it even i have ticked the oem unlock and usb debugging in developer mode ?

suhaibahmad said:
the time when u were fixing your device , you were on marshmallow or nougat ? beacuse i am on nougat and whenever i flash twrp , it stucks there and not booting into it even i have ticked the oem unlock and usb debugging in developer mode ?
Click to expand...
Click to collapse
Does the TWRP flash complete? Can you boot up the OS after you flashed TWRP? (And did you download the correct version of TWRP for your device?)
As a last resort, you could try and flash marshmallow on your device and see if it works there.

Fabivons said:
Does the TWRP flash complete? Can you boot up the OS after you flashed TWRP? (And did you download the correct version of TWRP for your device?)
As a last resort, you could try and flash marshmallow on your device and see if it works there.
Click to expand...
Click to collapse
if i flash marshmallow it doesnt even boot up and in the odin mode showing binary and everything as custom , if i flash nougat and then flash twrp and try to manually boot into twrp it stucks on the s7edge screen which comes before recovery , and if i boot the mobile normally without the button combination then it stucks on the second logo SAMSUNG . if i flash again the stock recovery then boots normally

suhaibahmad said:
if i flash marshmallow it doesnt even boot up and in the odin mode showing binary and everything as custom , if i flash nougat and then flash twrp and try to manually boot into twrp it stucks on the s7edge screen which comes before recovery , and if i boot the mobile normally without the button combination then it stucks on the second logo SAMSUNG . if i flash again the stock recovery then boots normally
Click to expand...
Click to collapse
Have you tried to perform a regular factory reset via the OS on nougat? Sometimes that does the job, too.
But as I said. I can only give you my best guess here - my phone worked after my procedure, so I didn't investigate further.
And don't forget: Google is your friend.

Fabivons said:
Have you tried to perform a regular factory reset via the OS on nougat? Sometimes that does the job, too.
But as I said. I can only give you my best guess here - my phone worked after my procedure, so I didn't investigate further.
And don't forget: Google is your friend.
Click to expand...
Click to collapse
thats your kindness , yes i have performed the factory reset several times from recovery , but when i trying to reset it from settings , it goes after restart to recovery with dm-verity error , then i wipe and factory reset from there

Fabivons said:
For anyone in the same situation: I fixed it.
In the end all you have to do is flash the firmware with the fitting PIT file. If you firmware consists of multiple files and there is a "HOME"-file, flash it with this one first on the AP slot in ODIN. After that the same again just use the AP file this time.
My phone is up and running again now.
Click to expand...
Click to collapse
Fabivons said:
"please"
I described everything I did in the posts before.
As soon as you can enter the system again all you need to do is deactivate the locks I was talking about in my first post and perform a full wipe.
After that you can install any ROM you want via ODIN just like you are used to.
If that doesn't work for you, I don't have any answers either.
But again:
Prep work:
1. Download most recent ODIN
2. Download the correct firmware for your carrier (from www.sammobile.com)
3. Download the correct PIT file for your device
4. Put your device in download mode
Process:
1. Extract your firmware if it is a zip
2. Start up ODIN
3. Connect your device and check if it's detected by ODIN
3. Put the PIT file in ODIN
4. Put the "HOME" file of your firmware in the PDA slot of ODIN
5. Press start
6. When finished unplug your device and restart phone and ODIN
7. Reconnect your phone and check if it's detected by ODIN
8. Put all the other files of your firmware + the PIT in the correct slot in ODIN
9. Press start
After that my device booted up but still was, as you described too, a little buggy. So I deactivated FRP, activated USB debugging in the dev options, installed TWRP, performed a full wipe and installed another firmware of my choosing via ODIN (without a PIT file this time).
I am running 7.0 on my device now and it works flawlessly.
Click to expand...
Click to collapse
Well I had the same issue but Odin method didn't work for me on Nougat. And also FRP lock was On. every time I flashed the files it give me FRP on error. so I had to use Smartswitch. Even though I used original csc and ap files with latest Odin. BTW I have SM-G935FD model

SjDU said:
Well I had the same issue but Odin method didn't work for me on Nougat. And also FRP lock was On. every time I flashed the files it give me FRP on error. so I had to use Smartswitch. Even though I used original csc and ap files with latest Odin. BTW I have SM-G935FD model
Click to expand...
Click to collapse
Well FRP has to be turned off (the button in the menu is called "OEM unlock, the button has to be set to on which deactivates FRP). You don't mention using a PIT file - did you use one?

Help ! Custom binary blocked by CC Mode.

Hi All,
I got this error when I had installed Secure Hub (my phone previously was rooted) and tried to connect to my crop secure lan , after decline I get
(alert something about administrator.. I clicked allow)
just ignored that, but after one phone restart I got bricked and
(Custom binary blocked by CC Mode.)
message appear.. when I trying to turn on my phone ... (I have installed TWRP Recovery and it still working maybe there is a command that I can run on terminal and disable CC mode ?

I fixed it.
This is the solution:
1.- TWRP INSTALLED
2.- Download your rom
3.- Extract boot.img and recovery.img from AP file from your rom using winrar.
4.- Copy boot.img and recovery.img to your phone.
5.- Flash FIRST boot.img then flash recovery.img using twrp.
Now try to boot to download mode and you will see that "Download is blocked by cc mode" is not anymore, flash your rom with odin.
Thats all!

Agreed with Fabreitor .. works fine as he instructed..

Hello There!
My device is not turning to Download mode as well.... But I don't have installed the TWRP.
Is there a way to install TWRP, without download mode or stating the System on U.I part?

J530Y: help downgrade from oreo to any stock rom

Dear fellows kindly help my problem here.
days ago due to "intune" app by microsoft office 365, my j530y need to unroot, and somehow the intune app reads my stock rom as custom rom.
so i download and flash this "SM-J530Y - J530YDXU3BRH6 XID" from Ymobile site.
everything working just fine (in my opinion), until i tried to flash twrp and try to root. NOTHING WORKED, i tried several twrp tar and cf autoroot also fail.
the notifications are :
1. "Only official released binaries are allowed to be flashed(RECOVERY)"
ID:0/010> Odin engine v(ID:3.1301)..
<ID:0/010> File analysis..
<ID:0/010> Total Binary size: 22 M
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> NAND Write Start!!
<ID:0/010> SingleDownload.
<ID:0/010> recovery.img
<ID:0/010> RQT_CLOSE !!
<ID:0/010>
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Code:
Click to expand...
Click to collapse
2. i tried to downgrade to marshmllow/nougat and this error appear: "SW REV. CHECK FAIL (BOOTLOADER) DEVICE:3 BINARY:2"
3. last resource was just trying to flash custom rom (breeze+) which packed in zip file. the problem is when i want to flash it in the stock recovery, the process failure "can't mount /sdcard"
so please guys help me, i already browse several threads and days for downgrading this, but nothing cant pass this error message "SW REV. CHECK FAIL (BOOTLOADER) DEVICE:3 BINARY:2
please help,
im not a rich guy, but i will share a bit of my money to anybody give me the proper solution
Thank you in advance:crying:
hacker812c said:
[RMM] RMM State Fix Oreo 8.1 OEM Unlock Fix Dez 2018
This for users with RMM State or OEM Unlock Fix
And for users install custom ROM after Oreo 8.xx
[IMPORTANT]
With this tutorial you can reactivate de OEM unlock Option
TO install twrp or Downgrade to 7.0 nougat
Or install Custom ROM Oreo
[FILES]
#Samsung drivers
#Latest Stock firmware 8.x from Sammobile
#Odin any release after 3.x
#Miracle box 2.85
[NOTE:]
Back up your IMPORTANT files in your phone.
[STEPS]
1. install samsung drivers
2. Disable antivirus and Charge your Battery J7
3. Extract miracle all zip files
4. Run miracle box loader (run as admin)
5. Set your time to 2 years past.
6. Then close miracle box.
7. Open miracle box loader again (you will see miracle box is working now)
8. Connect the phone.
(Always check the phone. if there something pops up, tick "always allow" then "allow") i start Miracle Box_Cracked 2.58 and select Try to 3 options
9. Click "Connect" button on the top left side on miracle box
10. Click "Samsung tab" on the miracle box
11. Click Scan on the top right corner
12. Set the mode selection into : Download then hit "Go" button you will notice that your phone is on download mode and its blank. Just let it be on that state its on the process right now.
13. Click on "Reset Reactivation/EE Locks
14. Hit " Start button" and now its on the process.
15. Reboot the phone in download just hold synchronously press vol - , home button , and power then wait until you get again in the selection and then select "Continue". As you can see there's no more RMM State: prenormal in info. It means you're almost there..
16. Flash Stock 8.1 via Odin.
17. Enter in Stock Recovery and Factory Reset
18. Install TWRP and install Custom ROM
[CHECK ON STOCK]
After reboot Oreo
Steps on Check REMOVING RMM
Setup your phone
You're done.. Check Dev Options and you see "OEM Toggle".
[NOTICE]
After flash Fix is normal
You will see error on the miracle.
That's okay you're almost there to get rid of it.
[LINKS]
Miracle Box:
https://www.techeligible.com/2018/04/03/download-miracle-2-58-with-loader/
https://drive.google.com/file/d/1n_UGxEEmvJFGym0li05GH5tw087_7GjW/view
Hacker812c
The secret of my success is Jesus
Dedicated To Sabrina Mello (2015)​
Click to expand...
Click to collapse
Hi all,
My J530Y oem unlock didnt show, rmm state prenormal, cant do anything to root or do more than stock users do basically.
ive been aimlessly crying for help and waiting if there's any update..ive been searching for this answer from July 2018.
So here's why i can work it out:
1. i read this thread just today, and realized there's some miracle called miracle box
2. i used miracle box to "RESURFACE" the OEM Unlock toggle in developer mode (3 times i fail, realized i have to use the newest stock rom of 8.1, indonesian region you can find it here) using odin until i make the oem unlock re-appear (this stock firmware is just temporary so at the end i replaced it with custom rom Breeze+)
3. im using twrp from here, countless time failure until i realized i should really read the guide to flash the twrp in odin, notice no7 that you have to untick auto reboot. read through and it should work!
4. last problem in twrp was it cant mount data partition, the solution is here, notice the faq part
5. so TWRP done, the next thing i do was installing these files in TWRP from OTG >RMM State Lock fix, and no-verity-opt-encrypt-6.0.zip
6. Last, im installing Breeze+ Also in TWRP and still using OTG. (i prefer using this because its prerooted with magisk, which is nice because i need the Intune Hider4magisk so i still can work freely with rooted device
7. I never "REBOOT SYSYEM" from step 4 to 6, since i tried and just realized need to install the custom rom at no6.
Might this help for my fellow J530Y users whose had the same problem as me.
Thank you all.

em. said:
Dear fellows kindly help my problem here.
days ago due to "intune" app by microsoft office 365, my j530y need to unroot, and somehow the intune app reads my stock rom as custom rom.
so i download and flash this "SM-J530Y - J530YDXU3BRH6 XID" from Ymobile site.
everything working just fine (in my opinion), until i tried to flash twrp and try to root. NOTHING WORKED, i tried several twrp tar and cf autoroot also fail.
the notifications are :
1. "Only official released binaries are allowed to be flashed(RECOVERY)"
2. i tried to downgrade to marshmllow/nougat and this error appear: "SW REV. CHECK FAIL (BOOTLOADER) DEVICE:3 BINARY:2"
3. last resource was just trying to flash custom rom (breeze+) which packed in zip file. the problem is when i want to flash it in the stock recovery, the process failure "can't mount /sdcard"
so please guys help me, i already browse several threads and days for downgrading this, but nothing cant pass this error message "SW REV. CHECK FAIL (BOOTLOADER) DEVICE:3 BINARY:2
please help,
im not a rich guy, but i will share a bit of my money to anybody give me the proper solution
Thank you in advance:crying:
Click to expand...
Click to collapse
You have to wait for a week to flash twrp. Its a part of the Oreo update that the bootloader remains locked for 7 days

garylawwd said:
You have to wait for a week to flash twrp. Its a part of the Oreo update that the bootloader remains locked for 7 days
Click to expand...
Click to collapse
hi,
i kept my phone awake for 3 weeks and no UEM unlock on devlpr option, do u know why ?
i keep searching for some threads that actually got the uem unlock option in just one week, but not mine.
help.......

Same problem here on G570M.
Does anybody know if Oreo bootloader lock with olders Security patch can be bypassed changing date and making manual updates? I'm stucked right here.

em. said:
Dear fellows kindly help my problem here.
days ago due to "intune" app by microsoft office 365, my j530y need to unroot, and somehow the intune app reads my stock rom as custom rom.
so i download and flash this "SM-J530Y - J530YDXU3BRH6 XID" from Ymobile site.
everything working just fine (in my opinion), until i tried to flash twrp and try to root. NOTHING WORKED, i tried several twrp tar and cf autoroot also fail.
the notifications are :
1. "Only official released binaries are allowed to be flashed(RECOVERY)"
2. i tried to downgrade to marshmllow/nougat and this error appear: "SW REV. CHECK FAIL (BOOTLOADER) DEVICE:3 BINARY:2"
3. last resource was just trying to flash custom rom (breeze+) which packed in zip file. the problem is when i want to flash it in the stock recovery, the process failure "can't mount /sdcard"
so please guys help me, i already browse several threads and days for downgrading this, but nothing cant pass this error message "SW REV. CHECK FAIL (BOOTLOADER) DEVICE:3 BINARY:2
please help,
im not a rich guy, but i will share a bit of my money to anybody give me the proper solution
Thank you in advance:crying:
Click to expand...
Click to collapse
same problem on SM-J530G

renguer0 said:
Same problem here on G570M.
Does anybody know if Oreo bootloader lock with olders Security patch can be bypassed changing date and making manual updates? I'm stucked right here.
Click to expand...
Click to collapse
WandresJersey said:
same problem on SM-J530G
Click to expand...
Click to collapse
Have you guys had any solution to this?

em. said:
Have you guys had any solution to this?
Click to expand...
Click to collapse
Just seven days waiting. There is a patch when unlocking bootloader that able to unlock without this trouble.

em. said:
Dear fellows kindly help my problem here.
days ago due to "intune" app by microsoft office 365, my j530y need to unroot, and somehow the intune app reads my stock rom as custom rom.
so i download and flash this "SM-J530Y - J530YDXU3BRH6 XID" from Ymobile site.
everything working just fine (in my opinion), until i tried to flash twrp and try to root. NOTHING WORKED, i tried several twrp tar and cf autoroot also fail.
the notifications are :
1. "Only official released binaries are allowed to be flashed(RECOVERY)"
2. i tried to downgrade to marshmllow/nougat and this error appear: "SW REV. CHECK FAIL (BOOTLOADER) DEVICE:3 BINARY:2"
3. last resource was just trying to flash custom rom (breeze+) which packed in zip file. the problem is when i want to flash it in the stock recovery, the process failure "can't mount /sdcard"
so please guys help me, i already browse several threads and days for downgrading this, but nothing cant pass this error message "SW REV. CHECK FAIL (BOOTLOADER) DEVICE:3 BINARY:2
please help,
im not a rich guy, but i will share a bit of my money to anybody give me the proper solution
Thank you in advance:crying:
Hi all,
My J530Y oem unlock didnt show
Thank you all.
Click to expand...
Click to collapse
Thank for reply
If twrp correctly installed and internal memory not encrypt is possible flash any rom
Two problems
1 sd encrypt
2 OEM unlock and RMM state
I searching solution for You
Hacker friend
---------- Post added at 10:33 AM ---------- Previous post was at 10:22 AM ----------
renguer0 said:
Just seven days waiting. There is a patch when unlocking bootloader that able to unlock without this trouble.
Click to expand...
Click to collapse
So i will not go back to official rom
Samsung stupid software
Hacker

hacker812c said:
Thank for reply
If twrp correctly installed and internal memory not encrypt is possible flash any rom
Two problems
1 sd encrypt
2 OEM unlock and RMM state
I searching solution for You
Hacker friend
---------- Post added at 10:33 AM ---------- Previous post was at 10:22 AM ----------
So i will not go back to official rom
Samsung stupid software
Hacker
Click to expand...
Click to collapse
See last post mine on TWRP thread. I've posted a solution to this.
If you have your phone briked you can upload stock rom from odin. Take care about the version, you can't downgrade.

renguer0 said:
See last post mine on TWRP thread. I've posted a solution to this.
If you have your phone briked you can upload stock rom from odin. Take care about the version, you can't downgrade.
Click to expand...
Click to collapse
Very important this information
Thank You
Report below => text form post @Renquer0 (thanks)
About TWRP => Error on twrp installing any zip rom, magisk or kernel
When ENCRYPTION message is showed when booting DON'T CLICK IN RESET.
You need to enable data partition (guide quoted) and then install Magisk,
RMM State Bypass and no-verity-opt-encrypt-6.0 files in that order.
​

This is the entire quoted post:
renguer0 said:
For everyone that can't mount or format data (this f**k up the entire rooting process) you can follow this:
sharneil said:
While formatting device using TWRP re., device failed and showed me something like "unable to mount /data or system"
This happens because your recovery is unable to read internal storage. You need to do some small steps.
Steps
1) Reboot into TWRP recovery
2) go to " Wipe "
3) then " Advanced Wipe "
4) Choose " data " and tap on " Repair or Change File System "
5) Then tap " Change File System "
You will see text as ext4 infront of ' file system '
6) Change it to "EXT2" by tapping and swiping.
7) Once its done, change it to "EXT4" again.
(if some detail doesn't match after step 5, don't worry... Change file system path to something else then and to default again.)
DONE !
Then go back and try formatting ( or any other work ). It should succeed.
This method worked for me where I was using Redmi Note 4 with custom(Lineage) os and TWRP 3.2.3.0
If this doesn't work, then try once again or I will suggest you to install TWRP recovery again.
Thank you.
Click to expand...
Click to collapse
Maybe the OP can add it to the first post. This allowed to me to install TWRP and Magisk in my J5 Prime.
When ENCRYPTION message is showed when booting DON'T CLICK IN RESET. You need to enable data partition (guide quoted) and then install Magisk, RMM State Bypass and no-verity-opt-encrypt-6.0 files in that order.
Click to expand...
Click to collapse
Hope it helps. In my case I couldn't format data partition in TWRP until I changed filesystem to EXT2 and EXT4.