Database Users

TWRP Install over CWM6 for P3113 Galaxy TAB 2 7 inch

I can't seem to find a link for the version of TWRP that will work on model P3113. I have CyanogenMod 10 Rom JB 4.1.1 with Clockwork Mod 6x.
Can I even install TWRP over CWM6 and can I do it in Mobile ODIn Pro? I have that installed.
I also have Goo Manager and cannot figure out why I cannot find or download TWRP from there unless they do not have a version for my Model or that ROM/Kernel?
I am new to the forum so I cannot ask questions yet in the developer sections which is starting to get annoying since I had one or two threads I could have asked this question on.
Thanks

Use goo manager to install twrp.
Sent from my SGH-I727 using Tapatalk 2

scottx . said:
Use goo manager to install twrp.
Sent from my SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
I have tried that method and it cannot find any files to download

androidfr33k said:
I have tried that method and it cannot find any files to download
Click to expand...
Click to collapse
Use mobile Odin if you have the proper files. Why do you want twrp instead of cwm?

scottx . said:
Use mobile Odin if you have the proper files. Why do you want twrp instead of cwm?
Click to expand...
Click to collapse
Just wanted to try it. So this brings me back to my first question. Is there a compatible version for the Samsung galaxy tab 2 7 inch running cyanogenmod10 latest nightly build?
I Google searched and searched within Samsung forum. I found a version 2.2.1 but I think it was for a hero touch

androidfr33k said:
Just wanted to try it. So this brings me back to my first question. Is there a compatible version for the Samsung galaxy tab 2 7 inch running cyanogenmod10 latest nightly build?
I Google searched and searched within Samsung forum. I found a version 2.2.1 but I think it was for a hero touch
Click to expand...
Click to collapse
Recovery has nothing to do with the ROM. Nothing!
I had it saved. I'm a pack rat when it comes to files. Flash it with cwm. http://d-h.st/B1w

scottx . said:
Recovery has nothing to do with the ROM. Nothing!
I had it saved. I'm a pack rat when it comes to files. Flash it with cwm. http://d-h.st/B1w
Click to expand...
Click to collapse
Will this version work on the p3113? The linked file is p3110
Thanks

I just thought about what you said that cwm recovery has nothing to do with ROM but according to the guide I used it said I had to use a cwm version 6 with JB. so that is why I mentioned the ROM version because it was based on JB. So would you not think it does indeed play an important role in choosing a compatible recovery?

androidfr33k said:
I just thought about what you said that cwm recovery has nothing to do with ROM but according to the guide I used it said I had to use a cwm version 6 with JB. so that is why I mentioned the ROM version because it was based on JB. So would you not think it does indeed play an important role in choosing a compatible recovery?
Click to expand...
Click to collapse
Developers or tutorial writers list the recovery because thats the one they preffer / use themselves, but most of the time, it doesnt matter which one you use!!
Btw, the reason they say to use CWM6 with Jelly Bean, is because CWM will automatically stop JB from erasing CWM and returning the stock recovery,
but even if you flash with lets say CWM5, you can still remove the script that will undo CWM, but you will have to do it manually (it's an extra step)

scottx . said:
Recovery has nothing to do with the ROM. Nothing!
I had it saved. I'm a pack rat when it comes to files. Flash it with cwm. http://d-h.st/B1w
Click to expand...
Click to collapse
Will this version work on my GT-P3113?
Thanks

Try this one by nycbjr. It's not the official one, but it is known to work with the P3113
http://rootzwiki.com/topic/27140-recoverytouchtwrp211galaxy-tab-2-7-and-10662012/

androidfr33k said:
Will this version work on my GT-P3113?
Thanks
Click to expand...
Click to collapse
Yes. Works fine on any 31xx. I ran it on my 3113 for a while before cwm came out.

[Q] Difference between HLTE and HLTEXX?

My note 3 is from Vodafone Australia. the model number is SM-N9005. I always assumed it was one of the "International" one. Then i tried flashing the official cyanogen mod nightly for "International" which was called HLTEXX when i tried it it said your phone is an HLTE and not and HLTEXX.
What's the difference? Are there 2 kinds of international?

Wait for a dev to reply this properly, and this should be in the Q&A Section I assume,
Remove the device check in updater-binary, as I guess it means (hlte and xxx) the same device. Some have suggested to use TWRP Recovery as well. This is according to my understanding of the issue.

They are both different ways to say the same thing. Some places the n9005 is referred to as hlte and some places it's hltexx. Now as for why the roms don't flash and give that error, i am not sure. Ppl have been reporting that on ALL roms but i haven't had any issues, the roms seem to flash fine for me. But others have to edit the updater script, also some reported that flashing via cwm worked for them without editing the updater script and others said switching to twrp helped them... This is the weirdest android phone I have owned.
Sent from my SM-N9005 using Tapatalk

I also want to know this, and how to detect if the one i have is hlte or hltexx

JazonX said:
Wait for a dev to reply this properly, and this should be in the Q&A Section I assume,
Remove the device check in updater-binary, as I guess it means (hlte and xxx) the same device. Some have suggested to use TWRP Recovery as well. This is according to my understanding of the issue.
Click to expand...
Click to collapse
Can i move the thead myself to the Q and A section?:

hi,
i had the error flashing a rom and i switched from twrp to cwm now it works!
but i still want to know what the difference is!

Hakired said:
i tried flashing the official cyanogen mod nightly for "International" which was called HLTEXX when i tried it it said your phone is an HLTE and not and HLTEXX.
Click to expand...
Click to collapse
i can also not install the nightly hltexx.
bought my device in germany.
no problem with temasek unoffical and probam.

Hakired said:
My note 3 is from Vodafone Australia. the model number is SM-N9005. I always assumed it was one of the "International" one. Then i tried flashing the official cyanogen mod nightly for "International" which was called HLTEXX when i tried it it said your phone is an HLTE and not and HLTEXX.
What's the difference? Are there 2 kinds of international?
Click to expand...
Click to collapse
I also have Aussie Vodafone stock. hltexx is fine for me. See my answer below. I assume it must read product device and not product name. I have used a number of different firmware now and all good. I would assume yours is from the same place.
johanveld said:
I also want to know this, and how to detect if the one i have is hlte or hltexx
Click to expand...
Click to collapse
Check your Build Prop located in System (use root explorer or a similar app) and you will see this;
ro.product.name=hltexx
ro.product.device=hlte
So this is where people are getting confused because it is both depending on what you read.

Hakired said:
My note 3 is from Vodafone Australia. the model number is SM-N9005. I always assumed it was one of the "International" one. Then i tried flashing the official cyanogen mod nightly for "International" which was called HLTEXX when i tried it it said your phone is an HLTE and not and HLTEXX.
What's the difference? Are there 2 kinds of international?
Click to expand...
Click to collapse
hltexx is product name, hlte is device name
hlte refers to many models, including N9002, N9005, N9006, N9008, N9009
while hltexx is N9005
you can use my app Phone INFO to get more information.

i removed the first line from the updater script and successfully flashed cm nightly in twrp.

johanveld said:
hi,
i had the error flashing a rom and i switched from twrp to cwm now it works!
but i still want to know what the difference is!
Click to expand...
Click to collapse
but im already using CWM tho XiaoLu's custom CWM 6.0.4.5 i think

not-i said:
I also have Aussie Vodafone stock. hltexx is fine for me. See my answer below. I assume it must read product device and not product name. I have used a number of different firmware now and all good. I would assume yours is from the same place.
Check your Build Prop located in System (use root explorer or a similar app) and you will see this;
ro.product.name=hltexx
ro.product.device=hlte
So this is where people are getting confused because it is both depending on what you read.
Click to expand...
Click to collapse
have you tried the cyanogen nightly htlexx?
Are you telling me to edit my build prop?
What i was trying to do was dirty flash the Cyanogen Nightly on top of Temasek. I didnt believe a full wipe would help, Do you reckon I should? Just wanted to try out the Cyanogen but im pretty happy with Temasek's

A.N.Droid said:
i removed the first line from the updater script and successfully flashed cm nightly in twrp.
Click to expand...
Click to collapse
im kinda newbie and this seems difficult. No idea what an updated script is. Is that part of the ROM im flashing or within the recovery?

not-i said:
Check your Build Prop located in System (use root explorer or a similar app) and you will see this;
ro.product.name=hltexx
ro.product.device=hlte
So this is where people are getting confused because it is both depending on what you read.
Click to expand...
Click to collapse
My build prop says this.
ro.product.name=hltexx
ro.product.device=hltexx
So afterall it was hltexx but Cyanogen says it's only hlte.. strange. I'm going to try and do full wipe then flash cyanogen.

Hakired said:
So afterall it was hltexx but Cyanogen says it's only hlte.. strange. I'm going to try and do full wipe then flash cyanogen.
Click to expand...
Click to collapse
if it still doesnt work you could do this:
open the cm nightly archive (i use winrar), navigate to \META-INF\com\google\ and extract the file updater-script.
open in a text editor of your choice.
remove the first line and save the edited file. (you dont need to know a thing about programming to realize that this is the device check)
drag and drop the edited file into that folder in the archive and overwrite the old file.
flash. enjoy !

Thanks it worked. Now to see if it's fully functional with my phone.

Hakired said:
Could you send me your updater script file with the deleted line? When i opened it in notepad they were not in lines and it just goes on and on so I deleted some stuff concerning the checks and it looks like this.
|| abort("This package is for \"hltexx\" devices; this is a \"" + getprop("r ...
I get an error status code: 6
but it does not check for the phone model anymore.
Click to expand...
Click to collapse
great that it works for you now !
please do not use the attached file anymore, its outdated !

sermon edgedai
i have install the rom with the updater-script file
now i have a bootloop with the massage
Kernel is not seandroid enforcing
set warranty bit: kernel
pls help mee

NeoGoku123 said:
i have install the rom with the updater-script file
now i have a bootloop with the massage
Kernel is not seandroid enforcing
set warranty bit: kernel
pls help mee
Click to expand...
Click to collapse
Knox bootloader / kernel not compatible
This arrived to me on another device. I tried flash a Rom MJ2 non Knox over a ML1 Knox. The flashing by Odin was good but the Knox bootloader installed not liked it and give me that error at boot, and the phone not started.
I made a Mod Kernel-ML1.tar.md5 to flash by Odin and problem solved. MJ2 worked whit ML1 kernel.

NeoGoku123 said:
i have install the rom with the updater-script file
now i have a bootloop with the massage
Kernel is not seandroid enforcing
set warranty bit: kernel
pls help mee
Click to expand...
Click to collapse
could be that the attached file is outdated. you have to modify it by yourself next time.
can you get into recovery ? if so, wipe and install a rom.
if not, can you get into download mode ? if so, flash stock rom with odin.
if not, pull the battery and try again.

[Q] TWRP recovery for SM-G900L

Hello there,
My new Samsung Galaxy S5 [SM-G900L] just came in.
It wanted to install custom recovery from TWRP so I could make a backup of my Stock Rom and afterwards could install custom Roms, but there doesn't seem to be any support for the G900L.
I'm quite new here, but is it possible someone can help me with this? So that TWRP will aslo provide support to the G900L.
I'm willing to sent al the necessary files. But you'll have to gide me trough it.
Thanks in advance.

Anybody??

Good luck.. i tried looking for anything related to the 900L model but there's barely any support on it.

chaulklet said:
Good luck.. i tried looking for anything related to the 900L model but there's barely any support on it.
Click to expand...
Click to collapse
Thanks, but yeah, that is why I opened this thread. Because I couldn't find anything about my G900L either
And because I'm new I can't post anything in the development section T.T
I hope someone picks this up though.

Yup I fell ya
/Bump for support

SM 900L Support
Another one for 900L support. Got the phone rooted no problem but failed to install CWM or TWRP yesterday so no custom recoveries available . Got a boot loop for my efforts. Hope there is enough love out there for someone to tweak some of the packages for these phones.
Cheers.

Successfully installed TWRP and CyanogeMmod recoveries on my SM-G900L
Sorry for the very long delay. I only got this mobile last month. I am able to install TWRP recovery by using TWRP manager after rooting (Although his device is not supported officially, the recovery image for the international version (SM-G900F) works really fine. I also successfully flash CyanogenMod (both View attachment Snapshot_recovery.tar and View attachment Nigthy_recovery.tar) recovery images using odin.

sunilpaulmathew said:
Sorry for the very long delay. I only got this mobile last month. I am able to install TWRP recovery by using TWRP manager after rooting (Although his device is not supported officially, the recovery image for the international version (SM-G900F) works really fine. I also successfully flash CyanogenMod (both View attachment 3536028 and View attachment 3536027) recovery images using odin.
Click to expand...
Click to collapse
I have tried many times to use TWRP recovery on G900Lmodel but with no success.
I always end up with "COULD NOT DO NORMAL BOOT".
Also I need one help, I was trying to use this Custom ROM "Insanity S7 edge port", I again get the same message " COULD NOT DO NORMAL BOOT".
Someone told me it's the kernel problem and i have to flash stock kernel after flashing ROM zip. But the thing is I don't have the stock kernel.
Please help.

sachin7825 said:
I have tried many times to use TWRP recovery on G900Lmodel but with no success.
I always end up with "COULD NOT DO NORMAL BOOT".
Also I need one help, I was trying to use this Custom ROM "Insanity S7 edge port", I again get the same message " COULD NOT DO NORMAL BOOT".
Someone told me it's the kernel problem and i have to flash stock kernel after flashing ROM zip. But the thing is I don't have the stock kernel.
Please help.
Click to expand...
Click to collapse
TWRP for kltelget (SM-G900L) is available here. You can also use the TWRP for klte (SM-G900F). The details are available in my xda thread (latest version is not tested). You can boot most Phoenix kernel (I hope Insanity too) based ROMs by either flashing the stock ROM boot.img or a custom boot.img sited in my another xda thread located here (check second post).

sunilpaulmathew said:
TWRP for kltelget (SM-G900L) is available here. You can also use the TWRP for klte (SM-G900F). The details are available in my xda thread (latest version is not tested). You can boot most Phoenix kernel (I hope Insanity too) based ROMs by either flashing the stock ROM boot.img or a custom boot.img sited in my another xda thread located here (check second post).
Click to expand...
Click to collapse
Thank you sunil
I tried the recoveries that you are suggesting, both of them, klte and klteskt from the twrp site.
It seems to work on every other device but mine.
Can't figure what I am doing wrong.

sachin7825 said:
Thank you sunil
I tried the recoveries that you are suggesting, both of them, klte and klteskt from the twrp site.
It seems to work on every other device but mine.
Can't figure what I am doing wrong.
Click to expand...
Click to collapse
Not sure abt the latest versions. can you try the one (klte) linked in my xda thread. and hope ur device is rooted properly...

sunilpaulmathew said:
Not sure abt the latest versions. can you try the one (klte) linked in my xda thread. and hope ur device is rooted properly...
Click to expand...
Click to collapse
yes i will try them, I hope they work on latest MM.
And yes the device is rooted properly with latest CFautoroot for G900L, I even checked it with Root Checker basic.
Anyways, I don't have any special liking for TWRP, I wanted it to flash stock boot.img to make the Insanity ROM work.
I am ok with CWM recovery, but I was told it could not flash .img file and I am not equipped to make my own flashable zip form boot.img.
But now I am planning to use your modded boot.img for Phoneix based MM custom ROMs. I hope that will work.
Btw thank you so much...I checked both of your threads...They are awesome....you seem to be lone warrior for these Korean variants. Not much support elsewhere.
Really appreciate your efforts!!!!
Keep up the good work.

sunilpaulmathew said:
TWRP for kltelget (SM-G900L) is available here. You can also use the TWRP for klte (SM-G900F). The details are available in my xda thread (latest version is not tested). You can boot most Phoenix kernel (I hope Insanity too) based ROMs by either flashing the stock ROM boot.img or a custom boot.img sited in my another xda thread located here (check second post).
Click to expand...
Click to collapse
TWRP worked!!!
Finally..
Thank you so much!!!
Also I tried your kernel with Insanity ROM and it works perfect.!!!
Thank you once again.

i9500 can't install recovery (Fixed)

Hi everyone. I was using my phone with stock rom for a while ans I wanted to pass to Miui cuz I heard 4.4.2 will be released soon.
I downloaded TWRP and tried to flash as I did everytime before with Odin. I flashed it and it rebooted, odin showed Pass with no errors, but when I tried to launch the recovery, it is still stock. I don't know what I'm doing wrong. I flashed it like this before and they always worked but this is not working. Is there another way to install this? I don't have root access but it wasn't an issue before. I have the usb drivers installed and debugging on. It was tricky to install drivers on Win 8.1 but it seems like installed correctly as it didn't showed an error.
Waiting for an answer please. I hate this exynos phone but my parents just not allowing me to sell this.

LittleHedgehog said:
Hi everyone. I was using my phone with stock rom for a while ans I wanted to pass to Miui cuz I heard 4.4.2 will be released soon.
I downloaded TWRP and tried to flash as I did everytime before with Odin. I flashed it and it rebooted, odin showed Pass with no errors, but when I tried to launch the recovery, it is still stock. I don't know what I'm doing wrong. I flashed it like this before and they always worked but this is not working. Is there another way to install this? I don't have root access but it wasn't an issue before. I have the usb drivers installed and debugging on. It was tricky to install drivers on Win 8.1 but it seems like installed correctly as it didn't showed an error.
Waiting for an answer please. I hate this exynos phone but my parents just not allowing me to sell this.
Click to expand...
Click to collapse
Maybe try it with CWM? Here is the link for the latest version:
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/i9500/philz_touch_6.48.4-i9500.tar.md5/

Tkkg1994 said:
Maybe try it with CWM? Here is the link for the latest version:
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/i9500/philz_touch_6.48.4-i9500.tar.md5/
Click to expand...
Click to collapse
Thanks, I'm trying it now.

Please give me a feedback if it works or not. And if I help you please hit thanks man

Tkkg1994 said:
Please give me a feedback if it works or not. And if I help you please hit thanks man
Click to expand...
Click to collapse
Nope. It still opens up the stock recovery. Anymore solutions?

You tried to install one in the stock recovery? A zip file of the Recovery?

Tkkg1994 said:
You tried to install one in the stock recovery? A zip file of the Recovery?
Click to expand...
Click to collapse
I tried installing Miui in the stock rom but it didn't work. Perhaps the last updates did something? Cuz I was able to do this with ease. Maybe downgrading to the first stock 4.4.2 will work but it takes a lot of time and I'm sick of this. Thanks anyway, I'll boost your thanks meter by one more for trying to help

LittleHedgehog said:
I tried installing Miui in the stock rom but it didn't work. Perhaps the last updates did something? Cuz I was able to do this with ease. Maybe downgrading to the first stock 4.4.2 will work but it takes a lot of time and I'm sick of this. Thanks anyway, I'll boost your thanks meter by one more for trying to help
Click to expand...
Click to collapse
The rom you are currently on has nothing to do with your inability to flash the recovery. It's a completely different thing.
Uncheck auto-reboot before you flash the recovery. That should probably fix it.

LittleHedgehog said:
I tried installing Miui in the stock rom but it didn't work. Perhaps the last updates did something? Cuz I was able to do this with ease. Maybe downgrading to the first stock 4.4.2 will work but it takes a lot of time and I'm sick of this. Thanks anyway, I'll boost your thanks meter by one more for trying to help
Click to expand...
Click to collapse
Thanks man
You can maybe look for the latest official firmware from samsung and flash it. And after that try again the recovery. Here the Link: http://www.sammobile.com/firmwares/1/

FIXED!
Lennyz1988 said:
The rom you are currently on has nothing to do with your inability to flash the recovery. It's a completely different thing.
Uncheck auto-reboot before you flash the recovery. That should probably fix it.
Click to expand...
Click to collapse
OMG man you're awesome!!! It worked! Thanks so much.

[Q] dm-verity verification failed in recovery

(My phone is still running stock room, rooted, and with twrp)
So I was just about to flash a custom rom on my note since I learned that I can flash some t-mobile rom on my canadian (Bell) variant if I also flash a certain kernel(Only AEL and star[sumtin] I think) .
When I go to my recovery, I see on the bottom of the screen: dm-verity verificatoin failed.
I did a lot of research and didn't found anything, except some vague mention of that when bootloop are occuring.
So I don't know what I should do, if I can still flash anything without any worries, or should I unroot my note and flash the stock unrooted rom?
Can I still continue what I was doing and flash the custom rom and kernel I wanted to flash?
Another small question: I remember before rooting my note I had a software update available. I decided to root it first thinking I could do the update after (stupid I know), but I couldn't no more (I got a message about using a modified version or something like that). Is it important? Should I unroot my note, update the stock software, then root it again? And I guess if I flash another custom rom it's insignificant right?
thanks in advance! If I'm posting that because I really searched and found nothing satisfactory and clear, also bear with me I'm not perfectly bilingual.

It sounds like the custom rom you downloaded got corrupted, or just isn't compatible with your device. Try downloading again, and see if that works.
As for the update, now you are rooted you can no longer get any OTA updates. Most if not all custom roms will be using the latest builds. If you want to flash a completely stock (updated) rom, sammobile.com is where you need to be. But you will have to root the device afterwards.
Sent from my SM-N910F

Ryado said:
(My phone is still running stock room, rooted, and with twrp)
So I was just about to flash a custom rom on my note since I learned that I can flash some t-mobile rom on my canadian (Bell) variant if I also flash a certain kernel(Only AEL and star[sumtin] I think) .
When I go to my recovery, I see on the bottom of the screen: dm-verity verificatoin failed.
I did a lot of research and didn't found anything, except some vague mention of that when bootloop are occuring.
So I don't know what I should do, if I can still flash anything without any worries, or should I unroot my note and flash the stock unrooted rom?
Can I still continue what I was doing and flash the custom rom and kernel I wanted to flash?
Another small question: I remember before rooting my note I had a software update available. I decided to root it first thinking I could do the update after (stupid I know), but I couldn't no more (I got a message about using a modified version or something like that). Is it important? Should I unroot my note, update the stock software, then root it again? And I guess if I flash another custom rom it's insignificant right?
thanks in advance! If I'm posting that because I really searched and found nothing satisfactory and clear, also bear with me I'm not perfectly bilingual.
Click to expand...
Click to collapse
Same problem for me. Was on completely stock rom until today but hated the lack of control so tried a custom rom. I've been a flashaholic for years so thought I'd have no problem but how wrong I was. First I tried TWRP recovery several times but kept getting stock recovery. I then tried Philz CWM but got even more problems including "dm-verity verification failed". I am fairly new to KitKat as I tried it on my note 1 but didn't like it. I am really angry that the stock rom prevents me installing bloatware and restricts access to my Sd card.
Have now managed to root and install clockwork mod and Echo rom and all seems to be working now

4braid said:
Same problem for me. Was on completely stock rom until today but hated the lack of control so tried a custom rom. I've been a flashaholic for years so thought I'd have no problem but how wrong I was. First I tried TWRP recovery several times but kept getting stock recovery. I then tried Philz CWM but got even more problems including "dm-verity verification failed". I am fairly new to KitKat as I tried it on my note 1 but didn't like it. I am really angry that the stock rom prevents me installing bloatware and restricts access to my Sd card.
Have now managed to root and install clockwork mod and Echo rom and all seems to be working now
Click to expand...
Click to collapse
Anybody solved the "dm-verity verification failed"-issue so far?
Does an installation of the stock-firmware solve the problem?

Parinibbana said:
Anybody solved the "dm-verity verification failed"-issue so far?
Does an installation of the stock-firmware solve the problem?
Click to expand...
Click to collapse
Bump!
Would love to know how to fix this one!
Or do i just have to bite the bullet and do a fresh install.

Ed Law said:
Bump!
Would love to know how to fix this one!
Or do i just have to bite the bullet and do a fresh install.
Click to expand...
Click to collapse
That´s what I finally did. Couldn´t resolve it in any other way.
After that I installed TWRP instead of CWM and also used another root-method as before. (see https://www.youtube.com/watch?v=k2oOvf5tOCY) Since then the problem is gone.

Do you think I can just run Odin and install twrp without refreshing to stock rom first?
I dint even know if it's possible to switch to twrp after installing cwm without A fresh start lol
Might give it a go when I have a few hours to re set up the phone haha
Thanks for your help though!

Ed Law said:
Do you think I can just run Odin and install twrp without refreshing to stock rom first?
I dint even know if it's possible to switch to twrp after installing cwm without A fresh start lol
Might give it a go when I have a few hours to re set up the phone haha
Thanks for your help though!
Click to expand...
Click to collapse
I don´t know whether you can flash twrp after installing cwm, but I doubt it would solve your problem anyway.
Well, you could try. In the worst case you can still go back to stock.

Parinibbana said:
I don´t know whether you can flash twrp after installing cwm, but I doubt it would solve your problem anyway.
Well, you could try. In the worst case you can still go back to stock.
Click to expand...
Click to collapse
I can't find a TWRP File for SM-N910G
I dont think they released one

Ed Law said:
I can't find a TWRP File for SM-N910G
I dont think they released one
Click to expand...
Click to collapse
There are two versions for the Note 4, which together cover all variants.
1. TWRP for Samsung Galaxy Note 4 (Exynos) All Variants
2. TWRP for Samsung Galaxy Note 4 (Qualcomm) All Variants
Please have a look here: http://teamw.in/twrp_view_all_devices
PS: If you find this post useful, please feel free to click the THANKS-button.

Parinibbana said:
There are two versions for the Note 4, which together cover all variants.
1. TWRP for Samsung Galaxy Note 4 (Exynos) All Variants
2. TWRP for Samsung Galaxy Note 4 (Qualcomm) All Variants
PS: If you find this post useful, please feel free to click the THANKS-button.
Click to expand...
Click to collapse
Thanks man but unfortunately, even though it says fr all Qualcomm variants, its only for Verizon, Sprint, T-Mobile and Canada or India. I am not sure if they are SM-N910G models which is released in Australia lol
I dont want to accidentally brick the phone
and thanks for the quick responses man!

Ed Law said:
Thanks man but unfortunately, even though it says fr all Qualcomm variants, its only for Verizon, Sprint, T-Mobile and Canada or India. I am not sure if they are SM-N910G models which is released in Australia lol
I dont want to accidentally brick the phone
and thanks for the quick responses man!
Click to expand...
Click to collapse
I see.
Another thing you could do is, ask Rkrishnamurthy from this thread, what he finally flashed on his 910G-model? http://forum.xda-developers.com/search.php?searchid=325832927
He might have flashed the N910F-recovery on his N910G.
Or ask Aamirleo55 from this thread, what he did with his N910G: http://forum.xda-developers.com/not...rp-2-8-1-0-t2923509/post56392220#post56392220
Sorry, that´s all that comes to mind for now.

Yea i was thinking about giving the 910F Recover a go... but its a bit risky hahaha
The link to the first thread doesnt work but i did message aamirleo55.
Thanks for all your help again man. I feel like such a noob right now haha
I reflashed last night to stock. and then re-rooted, and installed CWM. But after i do all the SUPERSU updates and Xposed Framework, my DM Verity Fails again!!!
This really suck, because essentially i wont be able to backup, restore and flash my phone like i use to on the note 3......
I seriously hope 910F TWRP recovery is the answer.
Ed

Ed Law said:
Yea i was thinking about giving the 910F Recover a go... but its a bit risky hahaha
The link to the first thread doesnt work but i did message aamirleo55.
Thanks for all your help again man. I feel like such a noob right now haha
I reflashed last night to stock. and then re-rooted, and installed CWM. But after i do all the SUPERSU updates and Xposed Framework, my DM Verity Fails again!!!
This really suck, because essentially i wont be able to backup, restore and flash my phone like i use to on the note 3......
I seriously hope 910F TWRP recovery is the answer.
Ed
Click to expand...
Click to collapse
Ok
So I decided to download the latest CF Auto root and I found that the TRLTEDT corresponds with the SM-N910G - http://autoroot.chainfire.eu/
TRLTEDT correspondents to the India TWRP recovery - http://teamw.in/project/twrp2/266
SM-N910G also corresponds to India, Singapore, Sri Lanka and obviously Australia (where i am based) - http://forum.xda-developers.com/note-4/general/galaxy-note-4-versions-cpu-t2883741
So in theory i should probably use that one.
What do you think man?
Thanks for your help again.

Ed Law said:
Yea i was thinking about giving the 910F Recover a go... but its a bit risky hahaha
The link to the first thread doesnt work but i did message aamirleo55.
Thanks for all your help again man. I feel like such a noob right now haha
When I reflashed last night to stock. and then re-rooted, and installed CWM. But after i do all the SUPERSU updates and Xposed Framework, my DM Verity Fails again!!!
This really suck, because essentially i wont be able to backup, restore and flash my phone like i use to on the note 3......
I seriously hope 910F TWRP recovery is the answer.
Ed
Click to expand...
Click to collapse
Sorry for the bad link. I tried to find it again, but also couldn´t. If you wanted, you could still send him a private message.
When I had the DM-verity issue, I also reflashed to stock, installed CWM and rooted again, and got the same problem again. Just as you. Only when I used TWRP it worked for me and the DM-verity problem didn´t occur since then.
For backup you could at least make a Titanium-backup, which in the paid version even allows you to create a flashable .zip-file from all your backupped apps & settings. This is a very convenient way of re-installing everything, almost like a nandroid-backup.
Or if you are brave enough you could try flashing TWRP-recovery directly over your current CWM. I don´t know whether that works, but as long as you can get into download-mode, you will always find your way back to stock.
---------- Post added at 10:05 AM ---------- Previous post was at 10:03 AM ----------
Ed Law said:
Ok
So I decided to download the latest CF Auto root and I found that the TRLTEDT corresponds with the SM-N910G - http://autoroot.chainfire.eu/
TRLTEDT correspondents to the India TWRP recovery - http://teamw.in/project/twrp2/266
So in theory i should probably use that one.
What do you think man?
Thanks for your help again.
Click to expand...
Click to collapse
I am pretty sure it will work, but the decision of course needs to be yours.

Legend.
Thanks for all your help and the very quick replies.
I will report back what I do and if it solves any problems.
Hopefully I come back with a win!

Ed Law said:
Legend.
Thanks for all your help and the very quick replies.
I will report back what I do and if it solves any problems.
Hopefully I come back with a win!
Click to expand...
Click to collapse
Good luck, bro.

Parinibbana said:
Good luck, bro.
Click to expand...
Click to collapse
Thanks mate!
All this work and research just so I can flash my kernel with the N4 AEL Kernel haha
like you said though, as long as i can get into download mode, I should be all good.
I actually soft bricked my phone a couple days after i got it by accidentally converting certain system apps to user apps..... (idiot). Fixed the problem by flashing stock firmware and then re rooting. So i have some experience fixing this haha but hopefully i don't have to and report some good news.
Ill get back to this thread within the next 24 hours with results.

Parinibbana said:
Good luck, bro.
Click to expand...
Click to collapse
Mate! It worked.
So for anyone with DM-Verity Verification failed, simply install the appropriate TWRP recovery over it and it will fix your problem.
also SM-N910G is compatible with the TWRP Recovery for Inidia (even though it does not say it is)
So hap this fixed my problems and big thanks to Parinibbana for all the assistance.

Ed Law said:
Mate! It worked.
So for anyone with DM-Verity Verification failed, simply install the appropriate TWRP recovery over it and it will fix your problem.
also SM-N910G is compatible with the TWRP Recovery for Inidia (even though it does not say it is)
So hap this fixed my problems and big thanks to Parinibbana for all the assistance.
Click to expand...
Click to collapse
You are welcome.
Glad to hear it worked.