Database Users

Can someone please create a thourough start to finish guide on converting, rooting

Can someone please create a thourough start to finish guide on converting, rooting, recovery, and rom installations?
listen im no noob but im no mater either ive been rooting since the original TMO G1 and it has gotten very complex on top of that ive missed alot since i got my note 4 retail (out of the game) anyways someeone please compile a step by step list of what to do and where to find the neccasary files. and in what order.
please and thank you

For BL unlocking follow this
For rooting
If staying on stock:
Boot into download mode (VOL-DOWN + HOME + POWER) and flash twrp-3.0.2-0-trltevzw via ODIN (MAKE SURE YOU UNCHECK AUTO-REBOOT!!!).
Battery pull phone and then boot straight into recovery (VOL-UP + HOME + POWER) to finish the recovery install process or else it will install the default android recovery.
Then flash the Emotion-TW-5.1.1-nightly-r21-RC1-SM-N910P kernal via recovery.
Then flash the BETA-SuperSU-v2.71-20160331103524 via recovery.
Reboot.
If going to a different rom, you should just be able to flash the rom via recovery and get right in. But results may very, check the forums.

refusedchaos said:
For BL unlocking follow this
For rooting
If staying on stock:
Boot into download mode (VOL-DOWN + HOME + POWER) and flash twrp-3.0.2-0-trltevzw via ODIN (MAKE SURE YOU UNCHECK AUTO-REBOOT!!!).
Battery pull phone and then boot straight into recovery (VOL-UP + HOME + POWER) to finish the recovery install process or else it will install the default android recovery.
Then flash the Emotion-TW-5.1.1-nightly-r21-RC1-SM-N910P kernal via recovery.
Then flash the BETA-SuperSU-v2.71-20160331103524 via recovery.
Reboot.
If going to a different rom, you should just be able to flash the rom via recovery and get right in. But results may very, check the forums.
Click to expand...
Click to collapse
thank you very much i was a little frustratrated because it seems like the info is very fragmented

Can someone please tell me where I have gone wrong.
I have gotten temproot via kingroot installed and was able to get the unlocker to run and I can see that the device is now a developer device. I am trying to get root to work but not having any luck.
I follwed the instructions at http://forum.xda-developers.com/note-4-verizon/general/guide-noobs-guide-to-perm-root-twrp-t3360883 and had problems in step 8 when trying to run super-sume. I ran it successfully for stage 1 but then it hung when trying to run stage 2. However, I was able to move on to step 9 and install TWRP and the emotion kernel. I have done a full reset and tried a 2nd time but still no luck in getting permament root access.
Root checker shows no root access and superSU is installed but shows no su binary installed.
If I run SuperSUME-Pro then it shows the device is wrte=protected
It seems I can run kingroot again to gain temp root access but not perm root access.
Any ideas on how to proceed from here?

mlcampbe said:
Can someone please tell me where I have gone wrong.
I have gotten temproot via kingroot installed and was able to get the unlocker to run and I can see that the device is now a developer device. I am trying to get root to work but not having any luck.
I follwed the instructions at http://forum.xda-developers.com/note-4-verizon/general/guide-noobs-guide-to-perm-root-twrp-t3360883 and had problems in step 8 when trying to run super-sume. I ran it successfully for stage 1 but then it hung when trying to run stage 2. However, I was able to move on to step 9 and install TWRP and the emotion kernel. I have done a full reset and tried a 2nd time but still no luck in getting permament root access.
Root checker shows no root access and superSU is installed but shows no su binary installed.
If I run SuperSUME-Pro then it shows the device is wrte=protected
It seems I can run kingroot again to gain temp root access but not perm root access.
Any ideas on how to proceed from here?
Click to expand...
Click to collapse
Install SuperSU from TWRP. Does that work?

If you Developer mode and twrp but no root, then what you need to do is install emotional kernel from twrp and reboot device then boot back into twrp and install SuperSU zip and reboot device you should be fine.

After re-checking my recovery I do not believe that I have TWRP installed after all. I was booting into android recovery and it hit me I was not seeing what I expected to see. I need to work on getting TWRP installed. I do indeed have the custom kernel and developer mode enabled!!

refusedchaos said:
For BL unlocking follow this
For rooting
If staying on stock:
Boot into download mode (VOL-DOWN + HOME + POWER) and flash twrp-3.0.2-0-trltevzw via ODIN (MAKE SURE YOU UNCHECK AUTO-REBOOT!!!).
Battery pull phone and then boot straight into recovery (VOL-UP + HOME + POWER) to finish the recovery install process or else it will install the default android recovery.
Then flash the Emotion-TW-5.1.1-nightly-r21-RC1-SM-N910P kernal via recovery.
Then flash the BETA-SuperSU-v2.71-20160331103524 via recovery.
Reboot.
If going to a different rom, you should just be able to flash the rom via recovery and get right in. But results may very, check the forums.
Click to expand...
Click to collapse
So what you posted above is all that you need to do for root? You definitely have a much more concise explanation than the main thread. The other instructions made me feel like I was back on my old Droid 2 working from the giant tutorial threads over on rootzwiki, hah.
I'm also guessing that as you mentioned elsewhere that if we wish to run a custom ROM we'll have to reflash the stock kernel before doing so?

Does it matter whether or not its 4.4.4 or 5.1.1
refusedchaos said:
For BL unlocking follow this
For rooting
If staying on stock:
Boot into download mode (VOL-DOWN + HOME + POWER) and flash twrp-3.0.2-0-trltevzw via ODIN (MAKE SURE YOU UNCHECK AUTO-REBOOT!!!).
Battery pull phone and then boot straight into recovery (VOL-UP + HOME + POWER) to finish the recovery install process or else it will install the default android recovery.
Then flash the Emotion-TW-5.1.1-nightly-r21-RC1-SM-N910P kernal via recovery.
Then flash the BETA-SuperSU-v2.71-20160331103524 via recovery.
Reboot.
If going to a different rom, you should just be able to flash the rom via recovery and get right in. But results may very, check the forums.
Click to expand...
Click to collapse
Does it matter whether or not its 4.4.4 or 5.1.1

ttall8ball said:
Does it matter whether or not its 4.4.4 or 5.1.1
Click to expand...
Click to collapse
If you're wanting to unlock the bootloader, root and install TWRP then no it doesn't matter. Now if you want to install a custom ROM that is 5.1.1 then you WILL have to be on that firmware if you are currently on 4.4.4
If anyone helps, plz give thanks?
N910V ? BL / KYUBI ROM

MissionImprobable said:
So what you posted above is all that you need to do for root? You definitely have a much more concise explanation than the main thread. The other instructions made me feel like I was back on my old Droid 2 working from the giant tutorial threads over on rootzwiki, hah.
I'm also guessing that as you mentioned elsewhere that if we wish to run a custom ROM we'll have to reflash the stock kernel before doing so?
Click to expand...
Click to collapse
The instructions for rooting suggest installing the Emotion kernel first.
Many of the ROMs available to flash will suggest which kernel to use. You can go directly to that kernel.

I need a little info, my note I just got is already rooted. So I didn't have the joy to do it. A co worker just picked up a refurbished and it has 5.0.1 ., is the 2bog5 able to be rooted?

bingo6104 said:
I need a little info, my note I just got is already rooted. So I didn't have the joy to do it. A co worker just picked up a refurbished and it has 5.0.1 ., is the 2bog5 able to be rooted?
Click to expand...
Click to collapse
Yes it can. But I am pretty sure that you must unlock the bootloader first unless you already have a DevEd.
If anyone helps, plz give thanks?
N910V ? BL / KYUBI ROM

stajam said:
Yes it can. But I am pretty sure that you must unlock the bootloader first unless you already have a DevEd.
If anyone helps, plz give thanks?
N910V ? BL / KYUBI ROM
Click to expand...
Click to collapse
Thanks, I thought that from what I have been reading. To many guides, need to be complied into 2 guides and sticky on the forum for rusty people like me lol
Sent from my SM-N920V using Tapatalk

No problem bruh.
If anyone helps, plz give thanks?
N910V ? BL / KYUBI ROM

ttall8ball said:
Does it matter whether or not its 4.4.4 or 5.1.1
Click to expand...
Click to collapse
Thanks, I got it done
---------- Post added at 08:52 AM ---------- Previous post was at 08:49 AM ----------
stajam said:
If you're wanting to unlock the bootloader, root and install TWRP then no it doesn't matter. Now if you want to install a custom ROM that is 5.1.1 then you WILL have to be on that firmware if you are currently on 4.4.4
If anyone helps, plz give thanks?
N910V ? BL / KYUBI ROM
Click to expand...
Click to collapse
Thanks stajam, I got it done last night.

ttall8ball said:
Thanks, I got it done
---------- Post added at 08:52 AM ---------- Previous post was at 08:49 AM ----------
Thanks stajam, I got it done last night.
Click to expand...
Click to collapse
Good to hear glad you got it going. ?
If anyone helps, plz give thanks?
N910V ? BL / KYUBI ROM

refusedchaos said:
For BL unlocking follow this
For rooting
If staying on stock:
Boot into download mode (VOL-DOWN + HOME + POWER) and flash twrp-3.0.2-0-trltevzw via ODIN (MAKE SURE YOU UNCHECK AUTO-REBOOT!!!).
Battery pull phone and then boot straight into recovery (VOL-UP + HOME + POWER) to finish the recovery install process or else it will install the default android recovery.
Then flash the Emotion-TW-5.1.1-nightly-r21-RC1-SM-N910P kernal via recovery.
Then flash the BETA-SuperSU-v2.71-20160331103524 via recovery.
Reboot.
If going to a different rom, you should just be able to flash the rom via recovery and get right in. But results may very, check the forums.
Click to expand...
Click to collapse
can u get a new link to the twrp to flash..I just want root is all...I've download several twrp with same numbers but no luck flashing
thanks so much
Sent from my SM-N910V using XDA-Developers mobile app

Help to Root A9 pro (SM-A910F)

I'm looking for a way to root "A910F" via google, but no results.
I tried "how to root for A9100" but without success.
Please help me.

Not so far
sanglxagdm said:
I'm looking for a way to root "A910F" via google, but no results.
I tried "how to root for A9100" but without success.
Please help me.
Click to expand...
Click to collapse
Hey there, I have a Google alert set for anything posted about this phone but so far nothing has come up on how to root it. Just two sites on how to update its version of android. (Sorry, I'm not allowed to post links as I'm a brand new user to xda, but likely these sites are not of use to you)
I'm still waiting for a way to buy it! And I've been waiting a long time. May I ask how you purchased it? Any help you could give I would really appreciate!

rapidrem11 said:
Hey there, I have a Google alert set for anything posted about this phone but so far nothing has come up on how to root it. Just two sites on how to update its version of android. (Sorry, I'm not allowed to post links as I'm a brand new user to xda, but likely these sites are not of use to you)
I'm still waiting for a way to buy it! And I've been waiting a long time. May I ask how you purchased it? Any help you could give I would really appreciate!
Click to expand...
Click to collapse
in italy here : http://brenovia.it/samsung/samsung-a9100-galaxy-a9-pro-dual-32gb-211.html

TWRP 3.0.2-1
sanglxagdm said:
I'm looking for a way to root "A910F" via google, but no results.
I tried "how to root for A9100" but without success.
Please help me.
Click to expand...
Click to collapse
TWRP 3.0.2-1. for the Samsung Galaxy A9 pro SM-A910F - Qualcomm MSM8976
Needs someone to test and report what works what doesn't giving plenty of detail and if possible the recovery log. It may boot, it may not.
Stock Recovery is posted below if TWRP doesn't boot.
NOTE:
FLASHING CUSTOM STUFF VOIDS YOUR WARRANTY. THIS WILL TRIP THE KNOX FLAG.
Install:
Boot to download mode.
Flash with Odin using the AP slot.
Uncheck Auto-reboot.
Reboot to recovery immediately after flashing using POWER + HOME + VOL DOWN, as soon as the screen goes blank change to VOL UP whilst still holding the other buttons.
TWRP should now boot.
NOTE: ON SOME ANDROID 5.1.1 and 6.01 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
Install with ODIN:
twrp_3.0.2-1_sm-a910f_25716
Stock recovery:
A910FXXU1APFC_stock_recovery
TO ROOT
Flash the file below in twrp.
https://download.chainfire.eu/964/Su...0519174328.zip
.

Installed fine on my A9100! No more Chinese when I enter TWRP!!!! Thank u!

steberg said:
Installed fine on my A9100! No more Chinese when I enter TWRP!!!! Thank u!
Click to expand...
Click to collapse
Can you post the recovery.log as a file or on pastebin?
Sent from my SM-T280 using XDA-Developers mobile app

@ashyx
Attached the recovery file.

steberg said:
@ashyx
Attached the recovery file.
Click to expand...
Click to collapse
OK, twrp cannot mount data or storage at the moment because your device has encryption enabled and TWRP does not support Samsung encryption at the moment.
To mount data and storage data needs to formatted to remove encryption and a custom boot.img used to disable forced encryption.
Sent from my SM-T280 using XDA-Developers mobile app

ashyx said:
TWRP 3.0.2-1. for the Samsung Galaxy A9 pro SM-A910F - Qualcomm MSM8976
Needs someone to test and report what works what doesn't giving plenty of detail and if possible the recovery log. It may boot, it may not.
Stock Recovery is posted below if TWRP doesn't boot.
NOTE:
FLASHING CUSTOM STUFF VOIDS YOUR WARRANTY. THIS WILL TRIP THE KNOX FLAG.
Install:
Boot to download mode.
Flash with Odin using the AP slot.
Uncheck Auto-reboot.
Reboot to recovery immediately after flashing using POWER + HOME + VOL DOWN, as soon as the screen goes blank change to VOL UP whilst still holding the other buttons.
TWRP should now boot.
NOTE: ON SOME ANDROID 5.1.1 and 6.01 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
Install with ODIN:
twrp_3.0.2-1_sm-a910f_25716
Stock recovery:
A910FXXU1APFC_stock_recovery
TO ROOT
Flash the file below in twrp.
https://download.chainfire.eu/964/Su...0519174328.zip
.
Click to expand...
Click to collapse
Hello I can be use this Files on SM A910F/DS Series??? Please reply me my phone is Dual Sim
hello please reply me can i use this file on A910/DS

ashyx said:
OK, twrp cannot mount data or storage at the moment because your device has encryption enabled and TWRP does not support Samsung encryption at the moment.
To mount data and storage data needs to formatted to remove encryption and a custom boot.img used to disable forced encryption.
Click to expand...
Click to collapse
I did format data and in TWRP I was then able to save recovery.log on internal storage. But after reboot it's back to encryption... I don't know how to make custom boot.img.
Thanks for your effort!

steberg said:
I did format data and in TWRP I was then able to save recovery.log on internal storage. But after reboot it's back to encryption... I don't know how to make custom boot.img.
Thanks for your effort!
Click to expand...
Click to collapse
I will provide the custom boot.img to disable encryption.

Ah that is awesome!!!

steberg said:
Ah that is awesome!!!
Click to expand...
Click to collapse
Flash with ODIN or extract the boot.img and flash with TWRP.
Boot to TWRP format DATA(not wipe). Please note this will delete all user data.
Reboot to TWRP, should now be able to mount data and make backups.
Boot to OS, forced encryption should be disabled.
A910FXXU1APFC_no_encryptable_boot
.

ashyx said:
Flash with ODIN or extract the boot.img and flash with TWRP.
Boot to TWRP format DATA(not wipe). Please note this will delete all user data.
Reboot to TWRP, should now be able to mount data and make backups.
Boot to OS, forced encryption should be disabled.
A910FXXU1APFC_no_encryptable_boot
.
Click to expand...
Click to collapse
Would this boot image work with the latest firmware for the A9100? Would you mind posting one if it won't? Could you also provide paypal info I'd like to contribute for your efforts.

trafficontrolr said:
Would this boot image work with the latest firmware for the A9100? Would you mind posting one if it won't? Could you also provide paypal info I'd like to contribute for your efforts.
Click to expand...
Click to collapse
It may do, but if it doesn't post up your boot.img.
If you go to the xda website the donate button should be on the left. Or use the link below. Thanks for your support. [emoji106]
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU

ashyx said:
Flash with ODIN or extract the boot.img and flash with TWRP.
Boot to TWRP format DATA(not wipe). Please note this will delete all user data.
Reboot to TWRP, should now be able to mount data and make backups.
Boot to OS, forced encryption should be disabled.
A910FXXU1APFC_no_encryptable_boot
.
Click to expand...
Click to collapse
Yes It works fine now, even after reboot there is full access! I can now mount Data partition in twrp!
I get my paycheck tomorrow, so beer is incoming!
But there are some issues now in OS, most probably because the boot.img is for A910F and I'm on A9100... The navigation keys does not light up and is not working, also it will not turn on wifi even though I flip the switch. But finally some developer is taking the time for A9!

steberg said:
Yes It works fine now, even after reboot there is full access! I can now mount Data partition in twrp!
I get my paycheck tomorrow, so beer is incoming!
But there are some issues now in OS, most probably because the boot.img is for A910F and I'm on A9100... The navigation keys does not light up and is not working, also it will not turn on wifi even though I flip the switch. But finally some developer is taking the time for A9!
Click to expand...
Click to collapse
Those issues are almost certainly because of the kernel. Post your boot.img from the stock firmware.
Sent from my SM-T280 using XDA-Developers mobile app

It is great that such a serious developer starts to work for a9 pro and there are results immediately. @ashyx is there any way to put somehow anyhow a910f firm into a9100?
thanks

ashyx said:
Those issues are almost certainly because of the kernel. Post your boot.img from the stock firmware.
Sent from my SM-T280 using XDA-Developers mobile app
Click to expand...
Click to collapse
I thought so as well, that is why we cannot crossflash the A910F firmware to A9100. Anyway here is the boot.img from A9100! Thank u once again!
Btw, beer incoming!

No way to use international kernel somehow for a9100?

S7 EDGE SM-G935FD stucked at Samsung logo after rooting !

Hi guys.
First of all sorry if this question is asked before. But i habe tried every method to fix this issue reading other threads.
Today i tried rooting my s7 edge sm-g935fd (indian version) first using cf-autoroot method and then using this method <URL>http://forum.xda-developers.com/galaxy-s7/development/recovery-official-twrp-herolte-t3333770 </URL>.
I followed each and every step properly and also tried two-three times. But after rebooting the phone (first boot) it always gets stucked at Samsung Logo. I have let the phone sit alone for more than 2-3 hours every time but phone is not booting up.
Also tried to flash no-verity-opt-encrypt (as mentioned in 2nd thread point no 11) but its not booting up. Also did format dat when booted recovery for the first time.
Do i have to unroot and flash the stock indian firmware and start the root again? But for that i need to have that SECURE STARTUP THING and for which i have to boot into my phone .
So plz guys tell me how to fix this issue? I dont have that secure start up pin for unrooting.
Things i used:
Odin 3.12.3, 3.10.6
CF-autoroot for hero2lte
Twrp -3.0.2-2
Thanks for your help.

The step you're missing here is your phone is encrypted (i did the same thing)... Flash TWRP and go to Wipe then hit the advanced button. You will have to type "yes" and TWRP will wipe the entire partition and rebuild it without encryption. You can then flash any ROM with TWRP and then flash dm-verity, and not get the secure verify issue.

dude9946 said:
The step you're missing here is your phone is encrypted (i did the same thing)... Flash TWRP and go to Wipe then hit the advanced button. You will have to type "yes" and TWRP will wipe the entire partition and rebuild it without encryption. You can then flash any ROM with TWRP and then flash dm-verity, and not get the secure verify issue.
Click to expand...
Click to collapse
Thanks dude for your reply. But as i mentioned i did FORMAT DATA and clicked typed YES when i booted recovery for the first time after flashing it with odin. Also i did swipe to allow modifications when i was asked in recovery.

In the settings > developers options did you allow or tick OEM unlock?
Sent from my SM-G935F using XDA-Developers mobile app

blu3angel said:
In the settings > developers options did you allow or tick OEM unlock?
Sent from my SM-G935F using XDA-Developers mobile app
Click to expand...
Click to collapse
Thanks for your reply. Yes i ticked both oem unlock and usb debugging.

If you used the proper cf root for your phone it should of worked.
the second method is not for the S7 edge. which is stated very clearly like this
Do not flash on S7 Edge or Qualcomm models!
Click to expand...
Click to collapse
I believe the only way to fix this is to download the Samsung drivers to your computer and use recovery on smart switch device initialization to restore your phone to original. To use device initialization you need to know the model of your phone (which you have) and the serial number which you should be able find from the box the phone came in.
Click to expand...
Click to collapse
Click to expand...
Click to collapse

Cosmic Blue said:
If you used the proper cf root for your phone it should of worked.
the second method is not for the S7 edge. which is stated very clearly like this
Do not flash on S7 Edge or Qualcomm models!
Click to expand...
Click to collapse
I believe the only way to fix this is to download the Samsung drivers to your computer and use recovery on smart switch device initialization to restore your phone to original. To use device initialization you need to know the model of your phone (which you have) and the serial number which you should be able find from the box the phone came in.
Click to expand...
Click to collapse
Oops i actually did not read that it does not work on s7 edge. But in the youtube video by max lee it was mentioned that the method works on s7/s7 edge exynos versions.
Edit: there is a same method for s7 edge also. Here is the link. http://forum.xda-developers.com/s7-edge/development/recovery-official-twrp-hero2lte-3-0-0-0-t3334084
Can you provide me the link for rooting s7 edge with cf-auto root and also step by step procedure to do so.
And also provide me the link for indian firmware for s7 edge. The one memtioned in one thread is corrupt.
Thanking you.
Click to expand...
Click to collapse
Click to expand...
Click to collapse

first get your phone restored using the smart switch method, that will put the correct uncorrupted firmware for your region.
then we willl talk about rooting. As long as you are in a boot loop on an unrooted phone very little can be done,

Cosmic Blue said:
first get your phone restored using the smart switch method, that will put the correct uncorrupted firmware for your region.
then we willl talk about rooting. As long as you are in a boot loop on an unrooted phone very little can be done,
Click to expand...
Click to collapse
Done with restoring can you tell now what i have to do to root?

Done rooting. But not cannot install xposed
I did the rooting by first using cf auto root and then flashing twrp. But when i flashed xposed v86 sdk23 from twrp the phone is again stucked at samsung logo. Cant get over it from last 1 hour. Is there any fix for it?

You need to flash the wanam custom build xposed version not the regular xposed..

jayas.mayank said:
I did the rooting by first using cf auto root and then flashing twrp. But when i flashed xposed v86 sdk23 from twrp the phone is again stucked at samsung logo. Cant get over it from last 1 hour. Is there any fix for it?
Click to expand...
Click to collapse
can you get into twrp, if yes then do a factory restore to remove xposed from your phone.
if you cannot get into twrp you will need to use smart switch again.

How to fix DM-VERITY issue for 7.0 flashed updates

Here is how you fix it.
Step 1. download OnePlus3t toolkit (note: don't attach the phone to PC yet)
step 2. reboot your phone into bootloader (if in twrp hit restart -> bootloader) if not in twrp try turning phone on and as you see the oem unlock screen hit volume up and down and choose fastboot (or bootloader)
step 3. open oneplus3t toolkit
step 4. choose option 8 (flash stock recovery)
step 5. hit enter and when it says waiting 4 devices attach your device to pc
step 6. let it finish
step 7. when recovery comes up, hold power button for 10 seconds or hit exit (if you can choose it) and reboot into system
step 8. if it keeps rebooting into a stock recovery and you cant decrypt... then when your phone first boots and goes into oem-unlock error hit volume up and click restart.
step 9. Reflash TWRP and SuperSU if needed
Step 10. Enjoy!

Did not work for me. Stock recovery, stock nougat, locked bootloader and I still have dm-verity error.

Skwerl23 said:
Here is how you fix it.
Step 1. download OnePlus3t toolkit (note: don't attach the phone to PC yet)
step 2. reboot your phone into bootloader (if in twrp hit restart -> bootloader) if not in twrp try turning phone on and as you see the oem unlock screen hit volume up and down and choose fastboot (or bootloader)
step 3. open oneplus3t toolkit
step 4. choose option 8 (flash stock recovery)
step 5. hit enter and when it says waiting 4 devices attach your device to pc
step 6. let it finish
step 7. when recovery comes up, hold power button for 10 seconds or hit exit (if you can choose it) and reboot into system
step 8. if it keeps rebooting into a stock recovery and you cant decrypt... then when your phone first boots and goes into oem-unlock error hit volume up and click restart.
step 9. enjoy!
Click to expand...
Click to collapse
Can TWRP be installed afterwards or will it come back when TWRP is installed?

Michalko5896 said:
Did not work for me. Stock recovery, stock nougat, locked bootloader and I still have dm-verity error.
Click to expand...
Click to collapse
Try flashing TWRP and back to stock recovery.
If all keeps happening you may need to follow the guide to unbrick the phone.
I'd personally keep flashing different things if data is important. Sorry to hear this happened. Sounds like dm-verity should never have been a thing. So frustrating. Please update us on what you find. You can always erase system and all then reflash image.

Skwerl23 said:
Try flashing TWRP and back to stock recovery.
If all keeps happening you may need to follow the guide to unbrick the phone.
I'd personally keep flashing different things if data is important. Sorry to hear this happened. Sounds like dm-verity should never have been a thing. So frustrating. Please update us on what you find. You can always erase system and all then reflash image.
Click to expand...
Click to collapse
I have tried everything. DM-verity error every fricking time.. Tbh, I really hate oneplus. They are not releasing factory images, with factory images I could fix every issue in 5 minutes.

I feel your frustration. There is this forum
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306

Michalko5896 said:
I have tried everything. DM-verity error every fricking time.. Tbh, I really hate oneplus. They are not releasing factory images, with factory images I could fix every issue in 5 minutes.
Click to expand...
Click to collapse
Go to TWRP>Wipe>Advanced Wipe>Select system>Repair or change file system>Change filesystem>EXT4>Flash your ROM
That fixed it for me

Michalko5896 said:
I have tried everything. DM-verity error every fricking time.. Tbh, I really hate oneplus. They are not releasing factory images, with factory images I could fix every issue in 5 minutes.
Click to expand...
Click to collapse
I used the hard brick fix to go back to 3.5.1? I let the system update to 3.5.4. Go into developer settings and check allow oem unlock. Went into bootloader and oem unlocked. It will erase everything. Downloaded and put the OTA patch(940gb~not full) and supersu 2.79 on the device somewhere and did a local update with the patch through stock recovery. Went into bootloader and flashed TWRP 3.0.2.0(not 3.0.3.0). Do not exit bootloader. In bootloader I fastboot BOOT the 3.0.2.0 TWRP(3.0.3.0 would not boot up and screwed the dm-verity). If it(3.0.2.0) doesn't want to boot then quickly hold the power button in and wait till it starts rebooting and go into recovery menu option). Swipe to allow modifications and flash the supersu 2.79 that was placed on the device somewhere. This worked for me and no dm-verity error with f2fs.
Long process but it worked.

does dm-verity error mean anything? I have it also currently but nougat seems to be running fine...

PaKii94 said:
does dm-verity error mean anything? I have it also currently but nougat seems to be running fine...
Click to expand...
Click to collapse
https://source.android.com/security/verifiedboot/
In a nutshell, extra security on the boot partition to "ensure chain of trust" one of the possible requirements for Android Pay backend.
********EDIT***********
This method didn't work on the newest beta, and the OP3T ToolKit way has never worked for me on any version of OOS.

card13 said:
https://source.android.com/security/verifiedboot/
In a nutshell, extra security on the boot partition to "ensure chain of trust" one of the possible requirements for Android Pay backend.
********EDIT***********
This method didn't work on the newest beta, and the OP3T ToolKit way has never worked for me on any version of OOS.
Click to expand...
Click to collapse
I see thanks. I guess it doesn't matter to me cause I haven't started using android Pay and since I'm rooted currently

What causes the dm-verity issue in the first place?

guys if my device is unlocked will i still get the ota updates?
how about root ? if my device rooted willi still get ota updates?

saberzaid said:
guys if my device is unlocked will i still get the ota updates?
how about root ? if my device rooted willi still get ota updates?
Click to expand...
Click to collapse
Yes to first. No to second, It will try but will fail.
Sent from my ONEPLUS A3000 using Tapatalk

Mine is unlocked and rooted. The update failed. Then it redownloaded the full 1.4gb. That's how I found the URL. Then it flashed fine but brought recovery to stock and wiped root. Had to use the toolkit to get TWRP and root back.
So yes, even rooted gets the update

noahvt said:
Go to TWRP>Wipe>Advanced Wipe>Select system>Repair or change file system>Change filesystem>EXT4>Flash your ROM
That fixed it for me
Click to expand...
Click to collapse
I did a system restore previously and it set system to ext4. Maybe that's why I didn't have issues.
This dm-verity issue could be showing the instability of f2fs. Hmmm

Hello, just reset original rom under 6.0.1 and the problems and then twrp then flash rom custom

jejemc said:
Hello, just reset original rom under 6.0.1 and the problems and then twrp then flash rom custom
Click to expand...
Click to collapse
Hi guy, I followed your instruction, however, it still has the problem.
When I use the stock recovery to flash the beta1 package, it could not be flashed in.

lanbingxuanyi said:
Hi guy, I followed your instruction, however, it still has the problem.
When I use the stock recovery to flash the beta1 package, it could not be flashed in.
Click to expand...
Click to collapse
Hello, I am going under the beta with the message in red dm-verity for the removed I returned under original rom then I handed twrp then rom custom

card13 said:
https://source.android.com/security/verifiedboot/
In a nutshell, extra security on the boot partition to "ensure chain of trust" one of the possible requirements for Android Pay backend.
********EDIT***********
This method didn't work on the newest beta, and the OP3T ToolKit way has never worked for me on any version of OOS.
Click to expand...
Click to collapse
PaKii94 said:
I see thanks. I guess it doesn't matter to me cause I haven't started using android Pay and since I'm rooted currently
Click to expand...
Click to collapse
I'm running 7.0 stable, unlocked bootloader and dm-verity warning. Android Pay still functions with the workaround.

I'm panicking a bit and i'd really need help :(

Hello ! So i'm bit stressed now cause i never had an unpullable battery before on my samsung.
So i just got from my cousin a galaxy s6 edge plus, and i want to root it. so installed odin and flashed twrp-3.1.0-0-zeroflte.img.tar
However now it kept being on the samsung logo. So i had to e press and hold the Volume down and Power/Lock keys on the device for 10–20 seconds to power it off. But it keeps rebooting, and now, it's only a black screen with a blue led. I don't know what to do, i'd really need your help. Thank you I'm so worried gosh.
update 1: i tried to force shut down by pressing the buttons and it used to display the samsung and carrier logo then be stuck on samsung logo, but now it just shows samsung galaxy, turn off and the recent apps et return buttons blinking. Kinda scary. I'm waiting for the battery to discharge, hopefully it will work I need your help

The zerolte is for the S6 EDGE, you want the zenlte
http://twrp.me/devices/samsunggalaxys6edgeplus.html
You should be able to hold vol down, home and power buttons to get into download mode to flash it.
Use the power and volume down button to force reset and when it does quickly press all 3.

Thank you for your time ! i did as you said, i entered twrp recovery mode and performed a wipe, but i'm still in a bootloop ! any ideas ?
EDIT : but i installed the new twrp over the old one might it be conflicting ?

I went back to 3.0.2.0 and don't have a bootloop issue anymore, it may be the latest update giving the issues.

Ehhh going back to the 3.0.2.0 didn't work either. I have the TWRP menu, have wiped, but i'm still in a bootloop. :/ I'm happy cause it's not bricked but i still use my phone...any help appreciated guys :<

So are you using a custom rom?
You can enter twrp to install/wipe etc?

nope i'm on stock rom and yeah i can enter twrp and install and wipe !

Like i just wanted to root my phone with stock rom, how can i achieve it ? :c

sleepyGrin said:
Like i just wanted to root my phone with stock rom, how can i achieve it ? :c
Click to expand...
Click to collapse
cf auto root can root and keep stock rom

oh nice i've just looked it up. How can i go from my current state to cf auto root ? RIght now it's boot loop with twrp, what can i do to go back to stock rom and use my phone again ? thanks

sleepyGrin said:
oh nice i've just looked it up. How can i go from my current state to cf auto root ? RIght now it's boot loop with twrp, what can i do to go back to stock rom and use my phone again ? thanks
Click to expand...
Click to collapse
Well you can download your stock rom for your model, mine is sm-g928r4 not sure what yours is but ya. Then use odin to flash the stock img and then use cf auto root to get root.

i flashed my rom but it failed and now im stuck with samsung smart switch but its not working, i don't know what to do really..

sleepyGrin said:
i flashed my rom but it failed and now im stuck with samsung smart switch but its not working, i don't know what to do really..
Click to expand...
Click to collapse
Just download the latest firmware for your smartphone (SM-G928x (Replace the x with your spessific model number on the back)) and your country from sammobile.com and flash it through odin. This should wipe your data and perform a clean reflash of the stock ROM. After that procedure it will take about 10 minutes to boot and it should be working again

sammobile is pretty slow is SamFirm okay ? And thanks i'l ltry this !

ok so i tried to flash the rom from sam firm for my SM-G928F SFR but it just shows up with a failed... any ideas ?

I had an issue trying to flash stock Rom back, I was trying to flash an older version and it failed, i downloaded the latest for my model and it worked. Are you sure you downloaded the right one?

sleepyGrin said:
oh nice i've just looked it up. How can i go from my current state to cf auto root ? RIght now it's boot loop with twrp, what can i do to go back to stock rom and use my phone again ? thanks
Click to expand...
Click to collapse
I presume you ave the SM-G928F S6 Edge +. Just flashing TWRP will cause boot loop. Please see post and flash via twrp the section 12. This should stop the bootloop. Allways remember never turn of OEM locking if you have a custom recovery.
" If you only want a bootable system partition or readable data in TWRP:
Download dm-verity and force encryption disabler.
Without exiting TWRP, transfer no-verity-opt-encrypt.zip to your device over MTP* and flash it using [Install] in TWRP.
** If your internal storage is encrypted, you will need to use adb sideload instead."
https://forum.xda-developers.com/s6...ecovery-official-twrp-galaxy-s6-edge-t3354492