Database Users

(Q) does not boot into CWM after install with heimdall

I just bought a brandnew i9505 today here in Germany
I tried to install CWM on the S4
sudo heimdall flash --recovery recovery-clockwork-6.0.3.3-jfltexx.img --no-reboot
This device may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading RECOVERY
100%
RECOVERY upload successful
Ending session...
Releasing device interface...
Re-attaching kernel driver...
===========
The blue transfer bar appears and than i tried to restart the phone into CWM but it always loads into stock firmware
I tried it several times and i tried several times to immediately booting into CWM after flashing CWM with heimdall
any suggestions?

MasterBrush said:
I just bought a brandnew i9505 today here in Germany
I tried to install CWM on the S4
sudo heimdall flash --recovery recovery-clockwork-6.0.3.3-jfltexx.img --no-reboot
This device may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading RECOVERY
100%
RECOVERY upload successful
Ending session...
Releasing device interface...
Re-attaching kernel driver...
===========
The blue transfer bar appears and than i tried to restart the phone into CWM but it always loads into stock firmware
I tried it several times and i tried several times to immediately booting into CWM after flashing CWM with heimdall
any suggestions?
Click to expand...
Click to collapse
Hi,
Do you havee the option in heimdall to NOT reboot?
Go into the ROM,then , power off and try to get into CWM.
When you power on,hold power +volume up button
When you see the blue writing,press and let go volume down button only.
Also , try a different CWM.

problem solved
When you see the Samsung logo, keep holding down Volume Up and Center Home buttons but let go of the Power button.
I did not know this...

[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

note4: SM-N910F Flashing gone wrong

Hey
So I have a note4: SM-N910F from a french Carrier, I was on the ANJ4 firmware, my phone is unlocked. I decided to flash it to make it work on my US GearVR following the advice of some redditors who after my many concerns have assured me it was low risk. I downloaded the ANK4 from another carrier and tried to flash it with Odin.
It failed and gave me the following error
"Volume size is too big 81920 < 512000
ODIN : Invalid Ext4 image"
The guy who's help I was following told me to clear cache and even gave me an explanation on how to do it. So I figured I'd just revert to my original firmware, which I have by flashing it back
EXCEPT! and here is the problem. Now my phone says 'Firmware upgrade encountered an issue. Please select recovery in Kies & try again.' - and I can't connect it to the computer! connecting doesn't work. It does DETECT IT when I plug it in, but then goes 'starting connection' till it says it didn't work. I tried other USB ports, I tried to reboot, I tried to reinstall USB drivers through Kies. I'm starting to be at a loss.
so I can't do anything in my phone and I can't connect it to a computer.
halp
(also I would love to avoid the obvious don't trust the internet people rhetoric, I'm past that and I knew the risks )
There is a reddit thread here: red dit.com/r/GearVR/comments/2poelk/to_flash_or_not_to_flash_that_is_the_question_to/cmyl01d
I put a spacebar between the 2 D of reddit because I can't put links in as a new user
EDIT IN THE PROCESS OF FIXING IT SUCCESSFULLY - can't find delete thread button

Better tell us how you solved then.
Sent from my SM-N910F using XDA Free mobile app

odin failed
Sur.
I am interested by the solution because i have the same issue while flashing carrier firmwares (orange ...) in odin (volume size too big 122000<512000)
invalid ext4 image.
It is ok for flashing country firmwares (xef, dbt ...).
Thank's for answering.

I was also having the same problem.
Here is how you solve it.
1. Download the stock firmware ending with .tar.md5.
2. rename it so it ends with .tar
3. Extract it using winrar to get recovery.img file
4. Download this tool (http://forum.xda-developers.com/showthread.php?t=2446269)
5. extract it also, and move the recovery.img file from step 3 and put it in the newly extract folder from step 4.
6. Click the ImgToTar.MD5.bat file and sit back.
7. You will now see a new file in there named "recovery.tar.md5"
8. flash this file with odin and your done!

Done above and flashed just the file recovery .tar. md5
All I get now is the Samsung logo... left the phone hanging like this for 30 minutes thinking it would boot up to beginning of phone..
Am I missing something?
Any help would be appreciated
Regards Braggster

Stuck in bootloop ; what to do??

Hi everyone!
I've got a problem : a friend's phone is stuck in bootloop. He so gave it to me to try something to get it back to life.
So, I do have access to recovery and download mode.
I first tried to factory reset it in recovery mode, but it didn't help...
I then went in download mode, and flashed the right firmware (for me) with Odin. All went well, Odin said ("PASS" ; "RES OK!!" " all threads completed. (succeed 1/failed 0)")
BUT, when I try to reboot, I'm still stuck in bootloop...
If someone could help me, I would really appreciate! Thanks!!

Have you flashed the right firmware for the device?

P€πtex4869 said:
Have you flashed the right firmware for the device?
Click to expand...
Click to collapse
Hi, Thanks for the reply !
Yes, I'm sure about the FW, I live in France, and the right fw is the "XEF" one. I even tried other european multilanguages FW, but it doesn't work, still in bootloop...
I've got some errors about "corrupted data", if that can help. ("E:failed to mount /data (Invalid argument")
Thanks again...

néonaloj said:
Hi, Thanks for the reply !
Yes, I'm sure about the FW, I live in France, and the right fw is the "XEF" one. I even tried other european multilanguages FW, but it doesn't work, still in bootloop...
I've got some errors about "corrupted data", if that can help. ("E:failed to mount /data (Invalid argument")
Thanks again...
Click to expand...
Click to collapse
Well then. I dont know much about that. Normally everything comes out fine after flashing through odin. Never faced an issue. May be someone else could help you

P€πtex4869 said:
Well then. I dont know much about that. Normally everything comes out fine after flashing through odin. Never faced an issue. May be someone else could help you
Click to expand...
Click to collapse
Thanks again foryour reply!
The flash through Odin "seems" to go well, no error, the flashing process is ok..
BUT, after that, on the phone is written :
"Finding update package..
.
Opening update package..
.
-- Appling Muti-CSC --
Formating /cache...
E: failed to mount /data
(Invalid argument)
E: copy_log_files_to_data
:: can't mount /dataReb
ooting... "
If that could help?! Thanks everybody!!

néonaloj said:
Thanks again foryour reply!
The flash through Odin "seems" to go well, no error, the flashing process is ok..
BUT, after that, on the phone is written :
"Finding update package..
.
Opening update package..
.
-- Appling Muti-CSC --
Formating /cache...
E: failed to mount /data
(Invalid argument)
E: copy_log_files_to_data
:: can't mount /dataReb
ooting... "
If that could help?! Thanks everybody!!
Click to expand...
Click to collapse
Try the method told in the first reply here. That is flash with pit and bootloader.
https://forum.xda-developers.com/showthread.php?t=2371548

P€πtex4869 said:
Try the method told in the first reply here. That is flash with pit and bootloader.
https://forum.xda-developers.com/showthread.php?t=2371548
Click to expand...
Click to collapse
Thank you again for trying helping me!!
But, the download link of the thread you talked about is working, but when I try to download it, it says "404 not found"... That with a ton of pop-ups!
So, I'm still at the same stage..
The thing I don't understand, is that the flash goes well, says "PASS" or "RESET", but this only with Odin v3.07. And the phone is still in bootloop on the Samsung logo..
Any other Odin version I try, is stopping the flashing process at :
"<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished successfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1203)..
<ID:0/004> File analysis.. "
...and there it stops ... I can wait for hours, nothing happens.
Thanks for everybody help, would appreciate!

Try odin without battery

noob&noob said:
Try odin without battery
Click to expand...
Click to collapse
I did it too... But thanks anyway!

Try .pit file in odin folder, it will stuck at setup...
Reset odin, unplug cable, select firmware files
Reboot phone in download mode -> continue, plug cable, flash
If it stuck or fail try again
I face same problem, i try reboot download mode again and again about 20 times, and finally it work
If u can go to recovery try wipe all

noob&noob said:
Try .pit file in odin folder, it will stuck at setup...
Reset odin, unplug cable, select firmware files
Reboot phone in download mode -> continue, plug cable, flash
If it stuck or fail try again
I face same problem, i try reboot download mode again and again about 20 times, and finally it work
If u can go to recovery try wipe all
Click to expand...
Click to collapse
Hi, thanks for your help!!
So I did what you say, flashed .pit in Odin without issue, Odin saying "RESET".
Then I Reset odin, unplug cable, select firmware, plug cable again, and flash. Nothing better happened, Odin saying "PASS", but still stuck in bootloop...
As you said, I tried many many times, without result.
At the moment, Odin is even not recognising the phone in download mode!! (differents versions of Odin, on both Win7 and Wn10)...
PS I can acces recovery, and wiped all "hundreds" of times..
Always stuck in bootloop, even if odin said the flash was all right many times, even after flashing .pit, alone, or with firmware. And now, as I said, even Odin don't recognize the phone in download mode..... Strangly, it (Odin) DOES recognize the phone in recovery mode!! But flashing then is impossible.
Any other ideas guys?? Thank you very much!

Now try install other rom via cwm, maybe it will boot

noob&noob said:
Now try install other rom via cwm, maybe it will boot
Click to expand...
Click to collapse
So what I did too : I tried to install CWM (two different versions), but they didn't stuck when I try to reboot (even immediatly) into recovery...
I tried to install roms via CWM when just installed, without succes.
Then I finally got a working custom recovery that is TWRP 3.0.3-0, and this time it eventually stays! I was so happy... But...
I've tried many roms available, CM9.2-20161020-UNOFFICIAL-totoro.zip, it ended up with ERROR 7 written in red.
I tried too "[ROM]GT-S5360]SL V2.1]New Update.zip without error, but when I want to reboot, it saysd "NO OS Installed, bla bla"... The same happens with the rom VROMV1-NOTE7.zip etc etc...
Conclusion : I now have a working TWRP, but no rom is working.... Always stuck at "Samsung Galaxy Y Young GT-S5360"!
I begin to desesperate.... Thanks for your help anyway!!

With twrp working, go to advanced -> file manager and see what inside your / on your phone
Upload screenshot if you can

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.