[RECOVERY][OFFICIAL] TWRP 3.5.0_9-0 [T710][T715][T715Y][T810][T815][T815Y]

[gantagavin]

sorry, but can it works for the AT&T variant, T817A? Will the T815 version compatible for it?

And will it be okay if i flash the AT&T version through Odin?

thanks before

 

[NeWONEx]

MTP doesn't work on T815 Installed driver multiple times, it work when boot to system but not in TWRP . tried every single option to get it works but no luck . maybe there is something you missed to implant .

 

[ripee]

MTP doesn't work on T815 Installed driver multiple times, it work when boot to system but not in TWRP . tried every single option to get it works but no luck . maybe there is something you missed to implant .

ashyx's 3.1.0-1 also suffered from this, and I compared his code to mine, as well as jcadduono's code, so it must be something else.

 

[NeWONEx]

ashyx's 3.1.0-1 also suffered from this, and I compared his code to mine, as well as jcadduono's code, so it must be something else.

Is there anyway to fix it ?

Thanks for the effort

Sent from my SM-T815 using Tapatalk

 

[ripee]

Is there anyway to fix it ?

Thanks for the effort

Sent from my SM-T815 using Tapatalk

What did I just write?

 

[NeWONEx]

What did I just write?

ashyx's 3.1.0-1 also suffered from this, and I compared his code to mine, as well as jcadduono's code, so it must be something else.

This is what you just write !

Did you mention if it is fixable or not ? As well as you need to mention it in bug list.

Sent from my SM-T815 using Tapatalk

 

[ripee]

ashyx's 3.1.0-1 also suffered from this, and I compared his code to mine, as well as jcadduono's code, so it must be something else.

This is what you just write !

Did you mention if it is fixable or not ? As well as you need to mention it in bug list.

Unless I can determine the cause, I won't know if it's fixable for our tablets, or if it's a bug on twrp's end.

Edit: In comparing gts210vewifi's twrp device tree, I'm pretty sure adb and mtp are determined in the kernel. One possible solution would be to build twrp using bonuzzz's oreo kernel, as that is the only version of his I've been able to compile. I'll look into it.

 

[bonuzzz]

@ripee not working mtp is not twrp or kernel issue. just config and init scripts.
take a look in my git more deep. maybe you'll find something interesting and don't forget t710 is my primary dev tablet.
ps: i don't want to publish any unofficial twrp because you have already official ones. And my builds will be only ones because of shared sources. But I dont want to make work for you and fix your bugs, because I continue to think you are very hurry to make official twrp and if you decided to be maintainer you have to publish quality product, because looking at your product we as users evaluate all product (twrp) at all.

 

[ubergeek77]

@ripee not working mtp is not twrp or kernel issue. just config and init scripts.
take a look in my git more deep. maybe you'll find something interesting and don't forget t710 is my primary dev tablet.
ps: i don't want to publish any unofficial twrp because you have already official ones. And my builds will be only ones because of shared sources. But I dont want to make work for you and fix your bugs, because I continue to think you are very hurry to make official twrp and if you decided to be maintainer you have to publish quality product, because looking at your product we as users evaluate all product (twrp) at all.

I just want to add my two cents and say that ADB doesn't work in recovery either. Hopefully whatever fix is needed for MTP will also cover ADB.

 

[ripee]

@ripee not working mtp is not twrp or kernel issue. just config and init scripts.
take a look in my git more deep. maybe you'll find something interesting and don't forget t710 is my primary dev tablet.
ps: i don't want to publish any unofficial twrp because you have already official ones. And my builds will be only ones because of shared sources. But I dont want to make work for you and fix your bugs, because I continue to think you are very hurry to make official twrp and if you decided to be maintainer you have to publish quality product, because looking at your product we as users evaluate all product (twrp) at all.

It's not that I was in a hurry to release 3.2.1, it's that I got tired if waiting for others to do so.

I think I know how to fix MTP, but I'll look into it tonight because I work today.

 

[bonuzzz]

@ripee for adb find my twrp sources for note4. It has adb working there.

 

[ripee]

@ripee for adb find my twrp sources for note4. It has adb working there.

I will tonight, thanks.

 

[ripee]

@ripee for adb find my twrp sources for note4. It has adb working there.

Your twrp sources for note4 are nowhere to be found.

 

[ripee]

@ripee not working mtp is not twrp or kernel issue. just config and init scripts.
take a look in my git more deep. maybe you'll find something interesting and don't forget t710 is my primary dev tablet.
ps: i don't want to publish any unofficial twrp because you have already official ones. And my builds will be only ones because of shared sources. But I dont want to make work for you and fix your bugs, because I continue to think you are very hurry to make official twrp and if you decided to be maintainer you have to publish quality product, because looking at your product we as users evaluate all product (twrp) at all.

I was expecting a bit more maturity from someone who knows more about this than me than a passive-aggressive comment. Here's a very crazy idea: how about you either help me with MTP or take over yourself? This isn't about who does what, it's about making the best builds available to the community.

 

[bonuzzz]

I was expecting a bit more maturity from someone who knows more about this than me than a passive-aggressive comment. Here's a very crazy idea: how about you either help me with MTP or take over yourself? This isn't about who does what, it's about making the best builds available to the community.

That's funny. Just interesting, how many official recoveries have you already made?
I told you where you can find fixes. but I will not do your work for you. If you can't, so leave it as it. That's all.
Nobody forced you to be official maintainer. It was only your decision.
I'm really scared to use official twrp for any devices after that.

ps: I didn't, don't and will not pretend to be maintainer on lineage, twrp or elsewhere.

 

[ripee]

That's funny. Just interesting, how many official recoveries have you already made?
I told you where you can find fixes. but I will not do your work for you. If you can't, so leave it as it. That's all.
Nobody forced you to be official maintainer. It was only your decision.
I'm really scared to use official twrp for any devices after that.

ps: I didn't, don't and will not pretend to be maintainer on lineage, twrp or elsewhere.

I can't find your fixes because you deleted your trelte repo.

If you're not a maintainer, then what would you call your work on android?

Anyway, I just managed to fix MTP on T810. The others will follow in a few minutes and I'll update the OP then.

 

[bonuzzz]

@ripee I mean maintainer of official repos.
forget about adb.

 

[ripee]

@ripee I mean maintainer of official repos.
forget about adb.

Thanks for the tip of taking a look at your treltexx twrp device tree. You did delete it from your GitHub, but user fuzhengqu had forked it before you had, so I was able to see your work in the recovery/root folder.

I managed to fix both MTP and ADB in my TWRP builds, thanks to your previous work. I am very grateful for your contribution.

 

[hurray]

Hello @ripee: Thank you for updating the TWRP.
I just made a new test-backup with the current TWRP from you and like my last test in december 2017 I get the error message:

  ==> set selinux context: u:object_r:system_file:s0
E:recv error on uevent

during the backup. Just to inform you that there is still a bug in TWRP which prevents the complete usage (I cant trust a backup which throws errors even at the backup stage).
I am now back on "twrp_3.1.0-1_sm-t810_13317" and everything is good again => Backup and Restore are working correctly

I read a little bit around and found out that there are other TWRP users which have exact the same problem without a solution for now ( I read only the last 5 pages of the thread and there are multiple replies to this error):
https://forum.xda-developers.com/s7-edge/development/recovery-official-twrp-hero2lte-3-0-0-0-t3334084/page220

So I think that there is a bug in TWRP which is not bound to an explicit phone/tablet.

Btw: I am running now your "lineage-14.1-20180427-UNOFFICIAL-gts210wifi.zip" with success.

 

[ripee]

Hello @ripee: Thank you for updating the TWRP.
I just made a new test-backup with the current TWRP from you and like my last test in december 2017 I get the error message:

  ==> set selinux context: u:object_r:system_file:s0
E:recv error on uevent

during the backup. Just to inform you that there is still a bug in TWRP which prevents the complete usage (I cant trust a backup which throws errors even at the backup stage).
I am now back on "twrp_3.1.0-1_sm-t810_13317" and everything is good again => Backup and Restore are working correctly

I read a little bit around and found out that there are other TWRP users which have exact the same problem without a solution for now ( I read only the last 5 pages of the thread and there are multiple replies to this error):
https://forum.xda-developers.com/s7-edge/development/recovery-official-twrp-hero2lte-3-0-0-0-t3334084/page220

So I think that there is a bug in TWRP which is not bound to an explicit phone/tablet.

Btw: I am running now your "lineage-14.1-20180427-UNOFFICIAL-gts210wifi.zip" with success.

That error message is entirely innocent. I have no idea what's causing it, but my backups restore and boot normally. Sorry that you jumped to the conclusion that this was a showstopper for you. I can assure you that it isn't. Because this is a minor annoyance, I hadn't bothered looking into it so far, but I will.