Database Info

Recovery for Marshmallow?

Hello all! I recently updated my Spring Note5 to Marshmallow! I quickly installed the Aurora Kernel to root it and got xposed installed via FlashFire. I was just curious as to if there was a Custom Recovery for marshmallow yet? I tried the latest TWRP and got stuck in a bootloop (soft brick). I was able to recover it luckily. Is there a working custom recovery yet? Thank you!

Here is the TWRP link for the Note 5 running marshmallow https://www.androidfilehost.com/?fid=24459283995314665

dmbstyle said:
Here is the TWRP link for the Note 5 running marshmallow https://www.androidfilehost.com/?fid=24459283995314665
Click to expand...
Click to collapse
Thank you! This is confirmed to be working?! Should i flash it with flashfire? Since i cant use odin.

DemoNKiTTy69 said:
Thank you! This is confirmed to be working?! Should i flash it with flashfire? Since i cant use odin.
Click to expand...
Click to collapse
Twrp is working but I got stuck in a bootloader trying to flash the twrp update with flashfire Odin is best way I had to use Odin to recover out of the bootloop

The file that I posted you don't need to use Odin or flashfire just install the Zip file then you can boot the cell into TWRP

dmbstyle said:
The file that I posted you don't need to use Odin or flashfire just install the Zip file then you can boot the cell into TWRP
Click to expand...
Click to collapse
How do I install the zip? Through stock recovery?

G920T : "dm-verity verification failed..." Help.

Hello, I currently have a G920T that had been working alright for quite some time. The problem is that yesterday while using it normally, it suddenly froze. Thought it was the app, but saw it was the phone itself. Thus, I decide to turn it on again. When I do that, the phone does not continue after the logo and has the LED light white, while blinking on an off. When I manage to enter the Android Recovery menu it gives me the error shown in the title. The phone's rooted and was unlocked, so I could use it with AT&T.
I attempted doing a full reset, upgraded it to Nougat, and I am still stuck. Any help's appreciated in advanced.

Would like to say, when I installed the official Nougat Upgrade for my phone, upon starting, it began installing some things and then preceded to start Deleting. Afterwards, it just froze again. Did I do something wrong?

To get past this issue you have to Root with SuperSU, this will patch the Kernel to disable DM-Verity and will allow you to boot normally.
If you don't want to get rooted then reflash stock firmware via odin. never do OTA updates as i have always say the come "Dirty"
EDIT: Sorry didn't read you were rooted, just re-root again with SuperSU (To get your Kernel patched again) for DM-Verity

Starnel said:
To get past this issue you have to Root with SuperSU, this will patch the Kernel to disable DM-Verity and will allow you to boot normally.
If you don't want to get rooted then reflash stock firmware via odin. never do OTA updates as i have always say the come "Dirty"
EDIT: Sorry didn't read you were rooted, just re-root again with SuperSU (To get your Kernel patched again) for DM-Verity
Click to expand...
Click to collapse
So I use (what I previously used) cf-autoroot again? I ask this, since it seems their website have the recovery for marshmallow version and not for nougat (if I am not able to downgrade to 6).

Junito72 said:
So I use (what I previously used) cf-autoroot again? I ask this, since it seems their website have the recovery for marshmallow version and not for nougat (if I am not able to downgrade to 6).
Click to expand...
Click to collapse
Root with TWRP and superSU zip, i don't recommend CF-AutoRoot
Before flashing the Zip do the following on a Terminal in TWRP
Mount o- bind /dev/urandom /dev/random

Junito72 said:
So I use (what I previously used) cf-autoroot again? I ask this, since it seems their website have the recovery for marshmallow version and not for nougat (if I am not able to downgrade to 6).
Click to expand...
Click to collapse
You can use CF-AutoRoot for 6.0.1 and 7.0.

forumber2 said:
You can use CF-AutoRoot for 6.0.1 and 7.0.
Click to expand...
Click to collapse
When I use CF-Autoroot and attempt to boot it into recovery I get the following message, "recovery is not seandroid enforcing".
So I'd take I try installing a custom ROM first before attempting to start it in recovery?

Junito72 said:
When I use CF-Autoroot and attempt to boot it into recovery I get the following message, "recovery is not seandroid enforcing".
So I'd take I try installing a custom ROM first before attempting to start it in recovery?
Click to expand...
Click to collapse
Oh, that means CF-AutoRoot has not updated to work on 6.0 & 7.0 bootloader for G920T (It is updated and working on 6.0.1 & 7.0 for G920F)
Flash the stock ROM again. After that, flash TWRP and than flash latest SuperSU zip via TWRP.

forumber2 said:
Oh, that means CF-AutoRoot has not updated to work on 6.0 & 7.0 bootloader for G920T (It is updated and working on 6.0.1 & 7.0 for G920F)
Flash the stock ROM again. After that, flash TWRP and than flash latest SuperSU zip via TWRP.
Click to expand...
Click to collapse
I tried doing that, but wouldn't get past the main ROM's screen. I tried a custom ROM then (I think nemesis or such) and lasted longer, but again froze and loops with the white LED light on.
Any suggestions?

Can I flash TWRP backup through ODIN?

I got the "custom binary boot blocked by frp lock" issue so I gotta reflash the stock firmware, which I should have since I did a full TWRP backup so if I convert my twrp backup in to a flashable zip will i be able to flash it through ODIN? (obviously i cant do it through TWRP Recov since I can only access download mode)
I can get the stock firmware from sammobile.com but its going to take like 4h+ to download and I dont have time for that

izou1838 said:
I got the "custom binary boot blocked by frp lock" issue so I gotta reflash the stock firmware, which I should have since I did a full TWRP backup so if I convert my twrp backup in to a flashable zip will i be able to flash it through ODIN? (obviously i cant do it through TWRP Recov since I can only access download mode)
I can get the stock firmware from sammobile.com but its going to take like 4h+ to download and I dont have time for that
Click to expand...
Click to collapse
Had the same issue. Rookie mistake. I accidentally left the developer option OEM unlock disabled and viola! Had to do a reset. Also, if you had any fingerprints while using the Rom you used, You might come into issues when resetting using Odin. You might have to format your internal memory using TWRP. Im not saying its something slcertain. I just had to. The only firmware I had available was a 6.0.1 MM stock Rom and I came into issues when unlocking the phone. Remember, this was a full reinstall in Odin and the screen was locked. When I unlocked the screen it would just reboot. So, lesson learned. Make sure if you go and root your phone again never ever, ever, ever disable that option in developer.
But try it. You can follow the steps from the root guide for nougat in the threads and go up until the step where you install TWRP. Boot into TWRP and see if you can restore the backup. Chances are it might work without having to do the extra steps like reinstalling the stock firmware. If that doesn't work and you run into issues in TWRP you might need to reinstall everything from scratch again.

Thanks! Already figured it out ?

please explain
izou1838 said:
Thanks! Already figured it out
Click to expand...
Click to collapse
my note 5 is at custom binary blocked by frp lock. i think I also turned off the option of oem unlock in developers option by mistake.
I have twrp back up on pc only. please help me how to unbrick the phone now.

Unfortunately the TWRP back is no help ):
However if you have the stock full system image you can just flash that through ODIN and then re-root? easy fix.
Look for the image here in XDA I've seen it

Sir i have note 5 with csc n920pvps3bpk1 shows in phone aftar dialing *#1234# but on the box of this cell phone is printed as n920fvps3bpk1 and n9200 will u plz tell me which csc is correct and i want to upgrade it to 7.0 and its knox waranty has voided.

izou1838 said:
I got the "custom binary boot blocked by frp lock" issue so I gotta reflash the stock firmware, which I should have since I did a full TWRP backup so if I convert my twrp backup in to a flashable zip will i be able to flash it through ODIN? (obviously i cant do it through TWRP Recov since I can only access download mode)
I can get the stock firmware from sammobile.com but its going to take like 4h+ to download and I dont have time for that
Click to expand...
Click to collapse
Hi, I have the same problem with an SM-520F, did you manage to solve it?

How to install Oreo ROM?

Hi! I'm really humbly sorry, I'm new to this stuff, so I have to ask you...
I have a Galaxy S8+ Duos (SM-GD955FD). I bricked it once or twice trying to root it. So I had to flash a sammobile.com ROM...
Now this is done, I have a successfully rooted phone with with the Baseband version G955FXU1AQH3 and the irritating "security notice" (since I was not able to install Magisk, and the NotifyClean app doesn't work either).
I would like to flash the latest Oreo and root it. I also heard good things about the Oreo ROM by alexega.
So: I'm on AQH3 rooted. What can I do?
Thank you for your patience.

If wou want to install stock ROM you must follow this instructions: https://forum.xda-developers.com/galaxy-s8+/how-to/guide-how-to-flash-crap-using-odin-t3748555. Bear in mind that if you install stock due to security issues you can't unlock OEM for 7 days after flashing (you must not reboot your phone for 170 hours).
If wou want to flash a custom rom you must have TWRP installed, move the zip rom to your SD card and just flash it from recovery. Make sure to format data before flashing.

josegon30 said:
If wou want to install stock ROM you must follow this instructions: https://forum.xda-developers.com/galaxy-s8+/how-to/guide-how-to-flash-crap-using-odin-t3748555. Bear in mind that if you install stock due to security issues you can't unlock OEM for 7 days after flashing (you must not reboot your phone for 170 hours).
If wou want to flash a custom rom you must have TWRP installed, move the zip rom to your SD card and just flash it from recovery. Make sure to format data before flashing.
Click to expand...
Click to collapse
Nice, thank you. So I have just flashed the thing with the sammobile.com ROM again (so, no root) and updated to the oroginal firmware Oreo following your link (I worked parallel).
I was just about to root Oreo and was googling for a way... But did I get you right? I should not reboot my phone for 170 hours now?!? So, no rooting until next week?!
Edit: I have developer options enabled and the "OEM unlock" switch is on (it says: "Bootloader is already unlocked.""). So... confusion...

andifla852 said:
Nice, thank you. So I have just flashed the thing with the sammobile.com ROM again (so, no root) and updated to the oroginal firmware Oreo following your link (I worked parallel).
I was just about to root Oreo and was googling for a way... But did I get you right? I should not reboot my phone for 170 hours now?!? So, no rooting until next week?!
Edit: I have developer options enabled and the "OEM unlock" switch is on (it says: "Bootloader is already unlocked.""). So... confusion...
Click to expand...
Click to collapse
Excuse me, are you currently on Nougat 7.0? If so, you obviously have OEM unlock option available. The problem is in the new 8.0 stock rom, wich sets RMM state to pre-normal preventing you to flash TWRP and to get root in OREO. To skip that you can directly flash a custom rom with 8.0.- Otherwise (stock rom) you must wait 7 days with no phone reboot to get ridd of that pre-normal issue and then flash TWRP and flash Magisk.

Just rooted the new Oreo ROM with TWRP. Works just fine, thank you.
So, what are the advantages of the Oreo ROM by alexega compared to XXU1CRAP?

josegon30 said:
Excuse me, are you currently on Nougat 7.0? If so, you obviously have OEM unlock option available. The problem is in the new 8.0 stock rom, wich sets RMM state to pre-normal preventing you to flash TWRP and to get root in OREO. To skip that you can directly flash a custom rom with 8.0.- Otherwise (stock rom) you must wait 7 days with no phone reboot to get ridd of that pre-normal issue and then flash TWRP and flash Magisk.
Click to expand...
Click to collapse
Hi Jose. I am with stock nogat. Not root. Any advice for flash stock oreo firmware?
Allrey know about odin. Im talking about unlock options, etc.
Thks
Juan from Argentina.

juange said:
Hi Jose. I am with stock nogat. Not root. Any advice for flash stock oreo firmware?
Allrey know about odin. Im talking about unlock options, etc.
Thks
Juan from Argentina.
Click to expand...
Click to collapse
Just follow the steps from the link in my previous repply. As it's an original software, it won't trip knox or void your warantee.

hi, does anybody knows how to install the oreo firmware using odin but without changing the csc I already have?

josegon30 said:
Excuse me, are you currently on Nougat 7.0? If so, you obviously have OEM unlock option available. The problem is in the new 8.0 stock rom, wich sets RMM state to pre-normal preventing you to flash TWRP and to get root in OREO. To skip that you can directly flash a custom rom with 8.0.- Otherwise (stock rom) you must wait 7 days with no phone reboot to get ridd of that pre-normal issue and then flash TWRP and flash Magisk.
Click to expand...
Click to collapse
Do you need a custom rom to not have the RMM lock anymore? A stock with BlackMesa's RMM START .zip is not right?

costafabiof said:
Do you need a custom rom to not have the RMM lock anymore? A stock with BlackMesa's RMM START .zip is not right?
Click to expand...
Click to collapse
There's no need to have a custom rom, if you flash the fix in stock RMM lock gets killed everytime.

josegon30 said:
There's no need to have a custom rom, if you flash the fix in stock RMM lock gets killed everytime.
Click to expand...
Click to collapse
Did not work.
I can not find out where I went wrong.

developer11 said:
Android.com.pl **** you
Little cocksucker
Click to expand...
Click to collapse
Translation?

costafabiof said:
Did not work.
I can not find out where I went wrong.
Click to expand...
Click to collapse
First you have to install OREO and wait 7 days without reseting your phone. After 170 hours, you get OEM unlock in developer options and you will be able to flasf TWRP. After flashing TWRP you flash RMM-State_Bypass_Mesa and that´s all.

josegon30 said:
First you have to install OREO and wait 7 days without reseting your phone. After 170 hours, you get OEM unlock in developer options and you will be able to flasf TWRP. After flashing TWRP you flash RMM-State_Bypass_Mesa and that´s all.
Click to expand...
Click to collapse
That did not work out. But thank you for your attention.

Can only install official binaries message when flashing TWRP with Odin3 on A750FN U4

Hi, I'm having a lot of trouble trying to install a custom recovery. I had it working a couple months back but wanted to go with official again for dumb reasons and now i want to go back but it won't let me flash TWRP, i can't find a TWRP specifically for this version either. It's Android 10 with March security patch.
I hope someone can help me.
Thanks.

Please only create one thread per topic. I've removed the duplicate thread you started on this topic.
As far as your issue goes, I don't actually know much about Samsung specifics, but I believe that particular message means you haven't unlocked your bootloader. You'll need to do that before you can flash custom stuff.

Didgeridoohan said:
Please only create one thread per topic. I've removed the duplicate thread you started on this topic.
As far as your issue goes, I don't actually know much about Samsung specifics, but I believe that particular message means you haven't unlocked your bootloader. You'll need to do that before you can flash custom stuff.
Click to expand...
Click to collapse
actually Im also having the same problem even though i have unlocked my bootloader.. I had previously installed twrp and was trying custom os until one os (evolution x) for some bricked my phone and i had to flash the stock firmware and after that when i try to re-flash twrp through odin it is saying officail binary can be flashed.

Parthiv Shaji said:
actually Im also having the same problem even though i have unlocked my bootloader.. I had previously installed twrp and was trying custom os until one os (evolution x) for some bricked my phone and i had to flash the stock firmware and after that when i try to re-flash twrp through odin it is saying officail binary can be flashed.
Click to expand...
Click to collapse
Like I said, I'm not 100% on Samsung shenannigans, but have you checked to verify that you didn't lock the bootloader as a part of flashing the stock firmware?

OEM unlock toggle in Developer's Options

Hi ¡...
1. You have to reinstall via odin the latest version 9 (AP, BL...etc)
2. On reboot do the entire TWPR flashing process for android 9
The current problem is that there is no TWPR for android 10.
Cheers