Database Users

Looking for a group of Ubuntu Touch devs to join

Hi,
I have some free time and would like to join a group of Ubuntu Touch devs. Is this a good place to ask or should I re-post on Canonical?

You can attempt to re-post on Canonical's forums, but the Ubuntu Touch Google+ Community is pretty active with both developers that work on Ubuntu Touch and consumers. I know I've seen Canonical's Michael Hall post in there as well as a couple others at some points.

https://ubports.com
This might be the place for you. They are asking for devs.
Good luck. I hope you start with the shamu (Nexus 6)

kidhudi said:
https://ubports.com
This might be the place for you. They are asking for devs.
Good luck. I hope you start with the shamu (Nexus 6)
Click to expand...
Click to collapse
I have a Nexus 5 and I want to dual boot Ubuntu with Android. There are 2 instructions on ubports.com but the one using MultiROM(to dual boot) has no link! I followed other guides with MultiROM but Ubuntu won't boot. Android's still working fine, though.

Matrixians 14 said:
I have a Nexus 5 and I want to dual boot Ubuntu with Android. There are 2 instructions on ubports.com but the one using MultiROM(to dual boot) has no link! I followed other guides with MultiROM but Ubuntu won't boot. Android's still working fine, though.
Click to expand...
Click to collapse
You will likely need to look into the official Ubuntu Dualboot solution and adapt that for the hammerhead. Ubports ROMs are intended to be installed via the ubuntu-device-flash commands only and are likely not supported under MultiROM easily.
That said, if you have an UBports system image installed via MultiROM, and it appears via multirom, you can always check /proc/last_kmsg after a failed Ubuntu Boot (while in multirom's boot manager) to see where the boot went bad, you could also open the ROM under MultiROM's recovery and hit Patch init and see if that helps.
Other than that, I'm afraid the only supported installation method for the community ports are the instructions listed on the page. You may also have some luck looking for KDE Plasma Mobile tutorials (which use a standard Ubuntu Touch image for their basic installation, not sure if they do the same thing as ubuntu-device-flash though).
One last thought, have you tried MultiROM manager? It may have images for your system (I recommend going no further than rc-proposed, devel does not run many apps from the Store and is based off Xenial, sp there's some library incompatibilities with apps installed from the Ubuntu Store. Devel branches are also not guaranteed to boot, however rc-proposed and stable should at least boot for you unless their builds are fundamentally broken, in which case, you should bring it up with the maintainer)

Thanks, but now Ubuntu Touch worked. I installed the dual boot app and added the channels for hammerhead. But now Everytime I boot into Ubuntu it removes my custom recovery. Instead of booting into the recovery, it boots into Ubuntu Touch, and it only happens if I reboot into Ubuntu Touch, so I basically have to reinstall recovery after using Ubuntu, which is very inconvenient.

Matrixians 14 said:
Thanks, but now Ubuntu Touch worked. I installed the dual boot app and added the channels for hammerhead. But now Everytime I boot into Ubuntu it removes my custom recovery. Instead of booting into the recovery, it boots into Ubuntu Touch, and it only happens if I reboot into Ubuntu Touch, so I basically have to reinstall recovery after using Ubuntu, which is very inconvenient.
Click to expand...
Click to collapse
I replied on the G+ page too, but figured I'd post here as well so others may benefit if I'm right here. -SNIP-
Edit: I just realized how the dualboot utility works.. It is likely the application overwriting your recovery image. If you want to keep MultiROM, I'm afraid you'll need to reinstall Ubuntu with MultiROM manager as the dualboot utility writes Ubuntu's boot.img to the recovery partition to boot Ubuntu.

Yeah, thanks, but it only works with the dual boot utility. I have my issues with MultiROM if you've read the first post on G+. But now I restored my system to a previous state when there was no dual boot utility so I don't want Ubuntu Touch anymore. Linux Deploy would do the trick, but now even IT has problems installing trusty. After the installation, I reconfigured it from the Linux Deploy menu and when I start it, it failed to start the VNC server and I don't know why. Is it the architecture of Trusty that i chose?

I did see your post, my apologies that MultiROM isn't booting for you, I ran into this weird issue myself on the Flo, normally it can be solved from trying other revision numbers in either the stable or rc-proposed channel. Sadly, through the Dualboot installer, there's no way around this (bar writing an /etc/init.d script for Android that automatically flashes the TWRP image when Android boots back up)
It may very well be the architecture of trusty. I would recommend trying vivid, saucy, wily or xenial. (any of the more recent versions, trusty is rather old at this point and you would've been getting Vivid [15.04] via Ubuntu Touch)
That said, you'll get much more performance using XServer XSDL from the Play Store and setting Linux Deploy to use it (X Server -> Use XServer XSDL), it also allows you to use any X application remotely or locally (on a remote machine you'd do export DISPLAY=[Tablet IP]:0)
As for Ubuntu Touch, if you go back through and attempt MultiROM again, start with the latest revision (I recommend staying far away from devel and devel-proposed unless you are purposely wanting to develop applications for Xenial, most applications targeting Vivid here don't work.) and then if the latest fails to boot, try the next one down the line. Another issue here could be a kernel that doesn't properly support KEXEC, have you tried MultiROM with a different KEXEC compatible kernel? I honestly can only recommend two different configurations, the singluar installation (Ubuntu being the only OS, gives you the most storage space) or MultiROM :\ I don't have much experience with the Dualboot app.

Stock ROMs Factory v6.1 , v8.3 , v8.4 , v8.5 , v8.7, V9.0, V9.2-patch : v21

CAUTION TO NOT LOOSE TWRP
I read two posts that say v21, now again on V8.5, put the stock recovery back instead of twrp. This is probably a side effect of a fresh stock /system and wipe of /data.
As a preventive step, when done flashing and wiping reboot to recovery FIRST, before booting the system It will allow recovery to handle removing the recovery-from-boot.p that flashes stock recovery.
I just patched the modified V7.4.2 up to the newly released 8.3 now 8.4. 8.5, 8.7,9.0 -V9.2 Patch
New update has been made from V17 to V21 of the non prime version of R1-HD, Non prime is behind on security patch (2017-05-05)
Copied ROM from phone and made twrp install ROM from it.
* No preloader change (official updates change the preloader to block your ability to use sp flash tools for rom flashing)
* No lk.bin change __ this part is what allows you to choose boot options(boot menu when power and volume pressed together)
* No "FOTA" app Fota has now been left in to make it easier to get next update, if that ever happens.
* No opera browser
* No adds (removed in the modified 7.4.2)
* Custom boot logo (only done on v8.3, there was no interest in this so abandoned)
--Newer versions of rom left stock, Leaving mods up to user.
** while it is not necessary to do a wipe with this ROM, I still recommend it.
**Thanks:
** @vampirefo needed his patched v7.4.2 in order to apply this new 8.3 patch and again for 8.4
** @ColtonDRG OR @jasonmerc I do not remember which one made it: For the image used in the custom logo
and the modified zip is here .
Roms are rootable with SuperSU, flashed in twrp after install. Must be done in systemless mode. In order to patch system veridy in boot.img
Logo update did not work on original rom changing link to updated version
BLU rolled v8.3 back to v7.4.2 because of app compatability issues. V8.4 is there fixed release. Both 8.3 and 8.4 are modified prime roms with ads stripped
V21 is the non prime update.
Unmodified V6.1
==>NON-ROOTED-logo-not-replaced-modified-V8.3
==>Fixed Logo modified NON_ROOTED V8.3
==>>modified V8.4
==>>modified V8.5
==>>Full with Ads V8.7
==>>Full with Ads V9.0
==>>Patch For V9.2 must be flashed on top of fresh V9.0
****Run debloat ==>script to remove ads if you need/ want to, or remove from zip before flashing ****
alt. manual example: before reboot, while still in twrp. Select mount and put checkmark next to system. Then run these two commands in adb terminal
Code:
adb shell rm /system/priv-app/com.amazon.*/com.amazon.*.apk
adb shell rm /system/app/Adups*/*.apk
==>>Modified V21
** stand alone logo installs

I flashed this but I didn't get the custom boot logo.

mendelgordon said:
I flashed this but I didn't get the custom boot logo.
Click to expand...
Click to collapse
I had that happen to my second phone too.
I don't have an explanation yet.
I even made a separate update.zip , that one didn't make the logo change either. I did eventually change it with sp flash tool.
I tried with both recoveries.
and multiple /dev location formats. and for whatever reason my one phone did not accept the logo change from recovery.
And the other test phone it worked.

mendelgordon said:
I flashed this but I didn't get the custom boot logo.
Click to expand...
Click to collapse
Neither did I but it all seems to be working fine

Been using this for about a day now, likewise no custom boot logo, but that's fine. Otherwise, it's been running super well. A lot better than the previous mostly stock version did for me with the bloatware APKs removed after the install. A lot of the general idiosyncrasies of the previous version of the stock rom seem to have gone away for me. It seemed to have weird storage management issues, errors moving to SD, broken symlinks that prevent apps from moving or being reinstalled, and a lot of other little non-storage issues, but so far, none off that here.
Long story short, good work! I hope we eventually see proper 7.x roms through some of the efforts going on, but in the meanwhile, your work here has made life a little bit better on 6.

It seems that I was able to get the logo.bin to update when I applied the original update patch, but not when I used the same line in the rom install.
It is no big deal that it did not work, I was just trying to make it look different at boot time.
edit:
I think i found the problem with the logo not updating.
i used the update-binary from the official patch update. (the one that allowed the logo to change the first time)
and it changes . so since the ROM seems to install the way it is , only the logo didn't flash I put it in a separate update.zip if anyone is interested in it.
EDIT 2:
clarification.
It was not so much the binary allowing the logo to change but the format of the partition location I had been using that needed that binary.
Further test had shown me that I could have used the binary I was using but just change the partition naming line
Code:
package_extract_file("logo.bin", "/dev/block/mmcblk0p9")
the above code works with the same update-binary as rom install
But I was using
Code:
package_extract_file("logo.bin", "/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/logo")
Taken straight from the official patch, and thats why it needed the update-binary also.
I dont know what is different in the binary other than , major size difference.
The powered by me logo was just a test file to see changes in the logo.
**logo-update is same as composite but with alt updater-binary
**composite-logo screenshot is in op
**stock logo will return to original BLU logo

mrmazak said:
It seems that I was able to get the logo.bin to update when I applied the original update patch, but not when I used the same line in the rom install.
It is no big deal that it did not work, I was just trying to make it look different at boot time.
edit:
I think i found the problem with the logo not updating.
i used the update-binary from the official patch update. (the one that allowed the logo to change the first time)
and it changes . so since the ROM seems to install the way it is , only the logo didn't flash I put it in a separate update.zip if anyone is interested in it.
EDIT 2:
clarification.
It was not so much the binary allowing the logo to change but the format of the partition location I had been using that needed that binary.
Further test had shown me that I could have used the binary I was using but just change the partition naming line
Code:
package_extract_file("logo.bin", "/dev/block/mmcblk0p9")
the above code works with the same update-binary as rom install
But I was using
Code:
package_extract_file("logo.bin", "/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/logo")
Taken straight from the official patch, and thats why it needed the update-binary also.
I dont know what is different in the binary other than , major size difference.
The powered by me logo was just a test file to see changes in the logo.
Click to expand...
Click to collapse
Hahaha the scribbled "ME" is hilarious. Your work is awesome, I don't think anyone using this rom will have an issue with the boot image but thanks for being so helpful and explaining.
P. S. Do you have any plans with the Nougat update?

Serenitybs said:
Hahaha the scribbled "ME" is hilarious. Your work is awesome, I don't think anyone using this rom will have an issue with the boot image but thanks for being so helpful and explaining.
P. S. Do you have any plans with the Nougat update?
Click to expand...
Click to collapse
Nougat is going to take a full build from scratch. We don't have 100% identical hardware with any other nougat device to my knowledge. We might have the same MTK chipset, but there are several other differences. All we really need is an official device overlay and the vendor files released by BLU themselves. We can then apply those to the latest Lineage or AOSP (I prefer AOSP myself) and build. Then the only problem we'll run into is anything that has changed in 7.x that isn't compatible with our kernel we use in 6.0. It'd be a slight chance our current kernel would work without some patches on 7.x We can't even get our official sources for anything else, so I'm almost certain we'll not find any patches to for the kernel to work properly with Nougat, at least not from BLU or any similar devices. None The less Nougat has been well thought of, and we have been trying to debug issues with a broken Port. But a broken port from a different device is just that - Broken. We need a team of knowledgeable devs to build Nougat + Kernel from scratch and then we'll have it working. I can't do it alone with the old computer I have, the R1HD would be long forgot of by the time I got Android Compiled haha.
Mr. Mazak I flashed your rom it went smooth, I was hoping the newest update was for 6.0.1. But I didn't lose any functionality, hopefully on my Cricket Service this update has patched some things to the radio device that will retain connection more steadily. I experienced a lot of coming and going with the 7.4.2 rom. None The Less you did a good job with this update Mr. My suggestion is find the same MTK chipset with a fully working 7.x rom and just port the /System but keep all our libs and inits from this release just for a test starter. And don't replace the camera app thats in AOSP 7.x. )

linuxsociety said:
Nougat is going to take a full build from scratch. We don't have 100% identical hardware with any other nougat device to my knowledge. We might have the same MTK chipset, but there are several other differences. All we really need is an official device overlay and the vendor files released by BLU themselves. We can then apply those to the latest Lineage or AOSP (I prefer AOSP myself) and build. Then the only problem we'll run into is anything that has changed in 7.x that isn't compatible with our kernel we use in 6.0. It'd be a slight chance our current kernel would work without some patches on 7.x We can't even get our official sources for anything else, so I'm almost certain we'll not find any patches to for the kernel to work properly with Nougat, at least not from BLU or any similar devices. None The less Nougat has been well thought of, and we have been trying to debug issues with a broken Port. But a broken port from a different device is just that - Broken. We need a team of knowledgeable devs to build Nougat + Kernel from scratch and then we'll have it working. I can't do it alone with the old computer I have, the R1HD would be long forgot of by the time I got Android Compiled haha.
Mr. Mazak I flashed your rom it went smooth, I was hoping the newest update was for 6.0.1. But I didn't lose any functionality, hopefully on my Cricket Service this update has patched some things to the radio device that will retain connection more steadily. I experienced a lot of coming and going with the 7.4.2 rom. None The Less you did a good job with this update Mr. My suggestion is find the same MTK chipset with a fully working 7.x rom and just port the /System but keep all our libs and inits from this release just for a test starter. And don't replace the camera app thats in AOSP 7.x. )
Click to expand...
Click to collapse
Somebody already tried this out

linuxsociety said:
Nougat is going to take a full build from scratch. We don't have 100% identical hardware with any other nougat device to my knowledge. We might have the same MTK chipset, but there are several other differences. All we really need is an official device overlay and the vendor files released by BLU themselves. We can then apply those to the latest Lineage or AOSP (I prefer AOSP myself) and build. Then the only problem we'll run into is anything that has changed in 7.x that isn't compatible with our kernel we use in 6.0. It'd be a slight chance our current kernel would work without some patches on 7.x We can't even get our official sources for anything else, so I'm almost certain we'll not find any patches to for the kernel to work properly with Nougat, at least not from BLU or any similar devices. None The less Nougat has been well thought of, and we have been trying to debug issues with a broken Port. But a broken port from a different device is just that - Broken. We need a team of knowledgeable devs to build Nougat + Kernel from scratch and then we'll have it working. I can't do it alone with the old computer I have, the R1HD would be long forgot of by the time I got Android Compiled haha.
Mr. Mazak I flashed your rom it went smooth, I was hoping the newest update was for 6.0.1. But I didn't lose any functionality, hopefully on my Cricket Service this update has patched some things to the radio device that will retain connection more steadily. I experienced a lot of coming and going with the 7.4.2 rom. None The Less you did a good job with this update Mr. My suggestion is find the same MTK chipset with a fully working 7.x rom and just port the /System but keep all our libs and inits from this release just for a test starter. And don't replace the camera app thats in AOSP 7.x. )
Click to expand...
Click to collapse
It was just wishful thinking. I have no idea how all of this is done. All I know is @mrmazak has helped me to fall in love with my phone again with this V8.3. The 7.4.2 did seem a bit buggy for my phone but this update works beautifully and I didn't even root it. If this remains true I will be happy with this phone for awhile even on 6.0

Really confused right now.
I was browsing through the settings menus. And found in the Settings-security- menu a toggle labeled "quick boot" ( not to be confused with "fastboot") . I enabled it then rebooted to see if it booted quicker. Didn't seem to make much if any difference. So I went back to turn it back off. And it wasn't there. I checked in my other phone , it wasn't there on that one either.
Did any body see this menu item, and if so where is is it?
Edit 1:
Few more power off , power on cycles to compare times. With other phone and defiantly seems to have turned on some faster boot option.
This phone goes from off to on in 5-6 seconds other phone takes about 20.
Edit 2:
OK , I panicked for a minute.
Couldn't find the setting and thought that it was another way to block sp flash tool by preventing you from ever being fully powered off.
But the setting was in accessibility not security.

Mrmazak, first of all, thanks for the ROM, installed it yesterday. But I have a problem with SELinuxModeChanger app. First, I'm getting a security warning when installing it, then - when running it. And another message, with this app running - "can't obtain root", although SuperSU shows its status with green #, like every other app it gives root privileges to. On my other Prime phone, running 6.1 out of the box stock ROM, FM radio works just fine with SELinuxModeChanger app behaving flawlessly (no security warnings whatsoever). Any ideas?

detroitredwings said:
Mrmazak, first of all, thanks for the ROM, installed it yesterday. But I have a problem with SELinuxModeChanger app. First, I'm getting a security warning when installing it, then - when running it. And another message, with this app running - "can't obtain root", although SuperSU shows its status with green #, like every other app it gives root privileges to. On my other Prime phone, running 6.1 out of the box stock ROM, FM radio works just fine with SELinuxModeChanger app behaving flawlessly (no security warnings whatsoever). Any ideas?
Click to expand...
Click to collapse
The mode changer app is technically a security issue. I did have that warning a few times when using mode changer app from the XDA thread of the developer, then when I used the app downloaded from f-droid it worked with systemless root and didn't give the security warning.

The app downloaded from f-droid worked for me as well, many thanks!

Big thanks for getting this out, updated from previous debloated, rooted version to this modified 8.3 stock rom, rooted with SU v2.79 SR3, all is good - only App that won't show up nor install, even tried the ones off APK Mirror site - is my Dunkin Donuts App, LOL. Play Store now said it's not compatible and the APK started to install then failed - any ideas or suggestions on what to do ??
Otherwise, it's all good - I will survive without DD App, just run that from another device when I need my caffeine fix.

Letitride said:
Big thanks for getting this out, updated from previous debloated, rooted version to this modified 8.3 stock rom, rooted with SU v2.79 SR3, all is good - only App that won't show up nor install, even tried the ones off APK Mirror site - is my Dunkin Donuts App, LOL. Play Store now said it's not compatible and the APK started to install then failed - any ideas or suggestions on what to do ??
Otherwise, it's all good - I will survive without DD App, just run that from another device when I need my caffeine fix.
Click to expand...
Click to collapse
I also had an app that previously work, say is not compatible now.
Maybe has to do with apps that have links to pay accounts. And that has something to do with trustzone. (Tee1 & tee2)
Those sections I left out of the update. I will add it back in and test. Update when I do. It is also possible this problem is why Blu rolled back there update.
**EDIT**
well that didn't go well at all.
I flashed the new trustzone.bin files from the official update. Now phone no longer turns on and no longer connects to flash tool
**EDIT 2**
After much persistence and many failed attempts to get phone recognized in pc again. Finnaly got to a point that phone was cycling between "preloader" driver and "usb serial device", and with careful timing was able to start sp flash tool at just right time and the flashing back to original trustzone files seems to have recovered phone.
for the record i am not sure what steps made it work. But I was shifting back and forth between leaving phone sit on charge, then on charge with rubber band wrapped around power button, then not plugged in , and not plugged in with rubber band on power button.

Okay... persistence is key in customization, i guess! I am getting somewhere here!
mrmazak said:
The first link is needed to get phone unlocked so you can install twrp.
Click to expand...
Click to collapse
Finally got thru the steps in order (1-2-3-4) then Step (5) and sub-step 1. I can also boot to TWRP.
Now this brings me to this thread, 8.3 Stock ROM. The thread assumes one knows how to install it and I suspect this could be as easy as uploading it to a folder in the phone then booting to TWRP and INSTALLING the ZIP file? Could someone clarify the steps to install this 8.3 ROM?
Thanks!

OldSkewler said:
Okay... persistence is key in customization, i guess! I am getting somewhere here!
Finally got thru the steps in order (1-2-3-4) then Step (5) and sub-step 1. I can also boot to TWRP.
Now this brings me to this thread, 8.3 Stock ROM. The thread assumes one knows how to install it and I suspect this could be as easy as uploading it to a folder in the phone then booting to TWRP and INSTALLING the ZIP file? Could someone clarify the steps to install this 8.3 ROM?
Thanks!
Click to expand...
Click to collapse
Yes. You are correct
Either put the zip file on external sd card , put card into phone boot into recovery mode and install , or put file directly onto phone .
Many ways to do that.
Easiest is to copy to phone while phone is connected to PC.
Cam also download file from internet with your phone.
Bottom line is get zip file to the phone boot to recovery and install

Anyone else having wifi issues after upgrading? While watching videos it seems the internet cuts out. The phone says it's still connected but I have to turn wifi off and back on for anything to work. Could be my router also but it didn't seem to be doing this until I installed 8.3

mrmazak said:
Yes. You are correct
Either put the zip file on external sd card , put card into phone boot into recovery mode and install , or put file directly onto phone .
Easiest is to copy to phone while phone is connected to PC.
Bottom line is get zip file to the phone boot to recovery and install
Click to expand...
Click to collapse
Right on man! I am officially running 8.3 ROM with April 5th 2017 Security Patch Level! Geez.. it was not easy but I got this working!
MrMazak, I followed all your instructions on both links, so could you tell me what exactly I have on my phone? Is it rooted? Bootloader Unlocked? The phone seems to be working fine but I don't know what level of access I have. Honestly I don't even know exactly what the differences between all these terms are.
Also, do I have or not SU? One of the steps under the .bat I believe install it. How do I access it?
Thanks again!
---------- Post added at 10:19 PM ---------- Previous post was at 10:18 PM ----------
Weasel0 said:
Anyone else having wifi issues after upgrading? While watching videos it seems the internet cuts out. The phone says it's still connected but I have to turn wifi off and back on for anything to work. Could be my router also but it didn't seem to be doing this until I installed 8.3
Click to expand...
Click to collapse
My install is pretty fresh, couple of hours, but as far as I can tell all is working fine with Wifi, As a matter of fact this is a new device only connected with Wifi and no SIM Card.... internet works fine.

[RECOVERY][TWRP][Unofficial] Galaxy Tab Active 2 - TWRP 3.2.3-0 [Exynos]

Disclaimer
**** All flashing is done at your own risk! ****
**** While this recovery should not break your device, don't come back here blaming anyone if it does! ****
This is a TWRP 3.2.3 build based on Android 7.1.2 source kernel for the Galaxy Tab Active 2 (codename: gtactive2lte) - Exynos. The "tar" file should be installed using Odin (tested on Odin 3.12.3).
Special Notes:
1. DON'T FORGET TO ENABLE "OEM UNLOCK" (located in Developers options, if its not there, you may have to wait for a few days to access that option, some users claim that its within 10 days before this option appears).
2. KNOX will be tripped once you flashed custom binaries to your phone.
3. Samsung Firmware OTA (aka System Updates) will no longer work once you flashed custom binaries.
(You can flash custom ROMs if you want to keep the OS up-to-date.)
4. It is HIGHLY UNRECOMMENDED to purchase any access to any kind of private forums, ROMs or Kernels.(DO NOT GET FOOLED.)
Installation process:
1. Flash Stock ROM.
2. Flash recovery using Odin (AP = recovery.tar).
3. Load recovery immediately after flashing.
4. Format data (Will erase /data partition).
5. Reboot to recovery.
6. ADB push SuperSU to internal storage / insert SD-Card with SuperSU.zip.
7. Flash SuperSU using TWRP install option.
8. Reboot to system (May bootloop several times. Wait untill system loads).
Bugs:
1. ADB sometimes doesn't work in MTP mode. Need to manually change to PTP in order to get adb usage.
2. Bad label in ADB shell + bad characters appearing while writing through AD. Works well out of recovery and on recovery's terminal.
Sources:
Device tree - Device tree
Kernel - Kernel
TWRP sources - platform_manifest_twrp_omni
SuperSU - SuperSU-2.82-SR5
Recovery download:
Recovery
Version Information
Status: Stable
Current Stable Version: 1.0
Stable Release Date: 08/19/2018 (DD/MM/YYYY)
Contributors:
Many thanks to TWRP's developers for the support on building this recovery.
Special thanks to CaptainThrowback, Bigbiff and Dees_Troy on TWRP-freenode and Ashyx on xda-developers.
Please post any bugs you encounter. I will try to fix any issues that come up.

Thanks for the work and sharing. I'm excited to try. Having root would be great, but I'd also like to be able to make voice calls ( using bluetooth as the built-in speaker & microphone aren't adequate ). Do you think this is possible. What changes, if any, are required to have work with T397 Tab Active 2 ( US variant ) ? I'm sure that it's mobile frequencies are different than what the euro-spec'd T395, but otherwise I think identical.
Slomo

slomo2 said:
Thanks for the work and sharing. I'm excited to try. Having root would be great, but I'd also like to be able to make voice calls ( using bluetooth as the built-in speaker & microphone aren't adequate ). Do you think this is possible. What changes, if any, are required to have work with T397 Tab Active 2 ( US variant ) ? I'm sure that it's mobile frequencies are different than what the euro-spec'd T395, but otherwise I think identical.
Slomo
Click to expand...
Click to collapse
Well, Samsung has a nice repo of their source kernels for every phone Samsung sources
I guess we just have to validate some data taken from boot.img from the stock rom and then build the same with the appropriate source kernel.

Shedaim said:
Well, Samsung has a nice repo of their source kernels for every phone Samsung sources
I guess we just have to validate some data taken from boot.img from the stock rom and then build the same with the appropriate source kernel.
Click to expand...
Click to collapse
Had no idea the source was available for these devices, thanks for sharing. T397 source is in the repository. Let me know if there is something that I can do to assist. I've not compiled these sources although I've compiled other things. Possible to use this tablet as a phone with this ROM as stock T397 ( even after installing several different dialers does not dial ) ?

slomo2 said:
Had no idea the source was available for these devices, thanks for sharing. T397 source is in the repository. Let me know if there is something that I can do to assist. I've not compiled these sources although I've compiled other things. Possible to use this tablet as a phone with this ROM as stock T397 ( even after installing several different dialers does not dial ) ?
Click to expand...
Click to collapse
I can't check the dialer thing, as I don't even have cellular network on my Tablet.
I'll try to build the recovery for the T397 later today, but you will have to check it I guess, as I have no access to that one.

Shedaim said:
I can't check the dialer thing, as I don't even have cellular network on my Tablet.
I'll try to build the recovery for the T397 later today, but you will have to check it I guess, as I have no access to that one.
Click to expand...
Click to collapse
This will be great, let me know if I can help, perhaps document.

slomo2 said:
This will be great, let me know if I can help, perhaps document.
Click to expand...
Click to collapse
Ok, so this is a first try, so I believe it's not going to work, but who knows? we may get lucky.
Recovery for SM-T397 - Android 7.1.2
If it doesn't get installed or leads to a bootloop, I'm gonna need you to pull the boot.img from your device, or send me a link of the stock ROM if it's available.
Please follow the intsallation process described on the README file on the github repository

Shedaim said:
Ok, so this is a first try, so I believe it's not going to work, but who knows? we may get lucky.
Recovery for SM-T397 - Android 7.1.2
If it doesn't get installed or leads to a bootloop, I'm gonna need you to pull the boot.img from your device, or send me a link of the stock ROM if it's available.
Please follow the intsallation process described on the README file on the github repository
Click to expand...
Click to collapse
Thank you! Successfully installed. I found this video helpful for this generation of Samsung device and learning how to navigate recovery and download modes. I disabled auto-reboot in ODIN per your instructions, but it wasn't clear to me how to power-off after download so as to be able to go into recovery without booting so after adequate time I just pulled the battery. I'll spend the evening playing with things and report back, but so far everything seems to be working
---------- Post added at 11:27 PM ---------- Previous post was at 11:15 PM ----------
slomo2 said:
Thank you! Successfully installed. I found this video helpful for this generation of Samsung device and learning how to navigate recovery and download modes. I disabled auto-reboot in ODIN per your instructions, but it wasn't clear to me how to power-off after download so as to be able to go into recovery without booting so after adequate time I just pulled the battery. I'll spend the evening playing with things and report back, but so far everything seems to be working
Click to expand...
Click to collapse
One thing I notice, 7.1.1 is what was/is installed on my tablet now. Not sure what version of Android available on Samsung Opensource or how to check it, but I suspect it is the same since nothing has been pushed OTA.

7.1.1 is what The T397U should have already been on before you started. Mine is and I have not installed this recovery as of yet. Just wanted to let you know it's where it should be.

slomo2 said:
Thank you! Successfully installed. I found this video helpful for this generation of Samsung device and learning how to navigate recovery and download modes. I disabled auto-reboot in ODIN per your instructions, but it wasn't clear to me how to power-off after download so as to be able to go into recovery without booting so after adequate time I just pulled the battery. I'll spend the evening playing with things and report back, but so far everything seems to be working
---------- Post added at 11:27 PM ---------- Previous post was at 11:15 PM ----------
One thing I notice, 7.1.1 is what was/is installed on my tablet now. Not sure what version of Android available on Samsung Opensource or how to check it, but I suspect it is the same since nothing has been pushed OTA.
Click to expand...
Click to collapse
Awesome. I really had my doubts being it the first build and all. I guess, there aren't really any major differences.
If it's possible, can you go through the TWRP checklist here
Some of the tests aren't really necessary, but it's a good checklist to go by anyway.
That way, I can officially add it to the OP.

Shedaim said:
Awesome. I really had my doubts being it the first build and all. I guess, there aren't really any major differences.
If it's possible, can you go through the TWRP checklist here
Some of the tests aren't really necessary, but it's a good checklist to go by anyway.
That way, I can officially add it to the OP.
Click to expand...
Click to collapse
Sorry for delay. I've done the following tests all with the expected results. The only thing I noticed compared to previous installations of TWRP that I've performed ( some years ago ) is that the load time of recovery seems long at 1:15. Also a message about "RECOVERY NOT SEANDROID ENFORCING" which I suspect is normal. Tablet has been working without incident. Thanks again.
Blocking checks
- Correct screen/recovery size
- Working Touch, screen
- Backup to internal/microSD
- Restore from internal/microSD
- reboot to system
-ADB ( yes, if this means being able to access from ADB while in recovery )
Medium checks
- Screen goes off (and on )
- F2FS/EXT4 Support, exFAT/NTFS where supported
- all important partitions listed in mount/backup lists
===> define important ? - depends on the device, i guess
= Assume we can still boot a recovery (aboot/lk is still there for fastboot), can restore everything left ?
- backup/restore to/from external (USB-OTG) storage
- Correct date
Minor checks
- MTP export
- reboot to bootloader
- reboot to recovery
- poweroff
- battery level
- USB mass storage export
- set brightness
- vibrate

Security Policy Updates should not be applied to this system ?
Since this is stock Samsung OS that is rooted I'm guessing this system is still SELinux "enforcing" so does this mean that I can/should say yes to Security Enhancements automatic updates from Samsung ? Any explanation or link on this matter appreciated.

Hey @Shedaim, thanks a lot for this recovery, would it be possible to release an update for oreo?

maddada said:
Hey @Shedaim, thanks a lot for this recovery, would it be possible to release an update for oreo?
Click to expand...
Click to collapse
Hey, sorry for the very late answer.
I'm currently not working on Android and I've never tried on OREO, so my politically correct answer would be: "Right now there is no plan to work the same magic on OREO, but whoever wants, can try to use the device tree I created with a new official OREO kernel (didn't know they have one already)".
Anyway, keep checking the forum from time to time, I may have found the time to work on it
Links to the device tree and other tools used are in the main page of this thread.
Thank you,
Shedaim

I Pay 100$ for making my Galaxy Tab Active 2 booting when its charging
Hey guys,
i hope somebody can help me.
Im trying since 2 Weeks to make my Galaxy Tab Active 2 booting when its charging.
I try all the ways i found (fastboot, LPM change and Autoboot App) and nothing was successful.
So i hope to find with this way somebody who would help me to get the feature.
I need it because i installed the Active 2 on my Harley Davidson as my navigation.
And the problem is that i make a Novalauncher thats looking like the original Harley Davidson one and starts without a code.
So when i put the Tablet in the Mask i dont get a method to press to power button and when i make a method (hole trough the mask or something) then everybody can start up my tablet and use it.
So if somebody can help me with that i will pay them 100$ for helping!
you can contact me at [email protected].
thanks alot

Excuse me for a moment, but i have a Galaxy Tab Active 2 WIFI (sm-t390) and im looking for a custom recovery for it. All i can find for this model is the SM-T395 variant of TWRP,root, etc. Absolutelly nothing for the SM-T390? Does any one have any ideas???? Thank you in advance either way.

sCOTTN916 said:
Excuse me for a moment, but i have a Galaxy Tab Active 2 WIFI (sm-t390) and im looking for a custom recovery for it. All i can find for this model is the SM-T395 variant of TWRP,root, etc. Absolutelly nothing for the SM-T390? Does any one have any ideas???? Thank you in advance either way.
Click to expand...
Click to collapse
I used the methods and recovery here for my tablet which is a T397U...works flawlessly. The same should work for the wifi T390 you have aswell.

Flash process
I am new to the rooting process. This will be my first time. What is the actual flash process? How do I flash the rom on my tablet?

All the links are dead can anyone please post this recovery

i can Flash this twrp-3.2.3-0-gtactive2lte-7.1.2.tar, Odin says pass, but there is no TWRP. it boots into System. when i stop and boot to recovery, there is stll custom recovery from T395XXU5CSH2.
Any hints?

Help updating S4 sm-t530nu

Hi. I have a Samsung Galaxy Tab 4 sm-t530nu and it is running on a really old Android version so I am unable to use some of the apps I would like to use. I have searched the internet and I am really finding it difficult to find an easy explanation on how to update it to the latest android version ( currently sit's at 5.0.2 and wont auto update any further ). I have seen some YouTube videos but most of the links they refer to are old and the video quality is quite poor. Can anyone direct me to somewhere that can easily explain what I need to do. Really sorry but I am not very knowledgeable when it comes to android things. Please help and much appreciated.

sandstorm_uk said:
Can anyone direct me to somewhere that can easily explain what I need to do.
Click to expand...
Click to collapse
You are at the right place. Before you can install a new version of Android, you need to install twrp, a replacement for the stock recovery program on your tablet. For most people this is the hardest part of the whole process. If and when you install twrp, installing a new OS is a piece of cake. Please watch this Youtube video:
Samsung Galaxy Tab 4 10.1 T530 How to install Twrp Recovery Tutorial
After watching the video and you still want to proceed, here are the links for where and what to download to install twrp:
Samsung Android USB Driver | Samsung Developers
You need the driver only if you are developing on Windows and want to connect a Samsung Android device to your development environment over USB.
developer.samsung.com
Downloads for : Samsung Galaxy Tab 4 10.1 | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
download twrp-3.6.0_9-0-matisse.tar (Odin likes tar)
Odin download latest version 2021 / 2022 / 2023 - Odin 3.14.4
Samsung Odin tool is a third-party utility that is designed to resolve software-related issues in Android mobile phones. Especially in Samsung handsets. It wasn’t developed for the public at first. However, with time, the software tool becomes available to the public as well. If you own a car, a...
odin3download.com
After you install twrp and are comfortable using the program, reply back and we'll guide you thru the remainder of the process to update Android.

Hi. Thank you so much for the response. So I have TWRP installed now and I am happy to continue. Very much appreciated. Great forum BTW.
Thanks

sandstorm_uk said:
I have TWRP installed now and I am happy to continue.
Click to expand...
Click to collapse
Download the latest LineageOS 18.1 (Android 11) for YOUR tablet here:
lineage-18.1-20220312-UNOFFICIAL-matissewifi.zip | by matteo0026 for Galaxy Tab 4 10.1
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Go here for the Google Apps:
The Open GApps Project
OpenGApps.org offers information and pre-built packages of The Open GApps Project. The Open GApps Project is an open-source effort to script the automatic generation of up-to-date Google Apps packages. All Android versions and platforms supported.
opengapps.org
Very important: Select ARM, Android 11, nano
The website will prepare the ZIP for download
This top and first message will guide you thru the install process:
[ROM][UNOFFICIAL][matisse][millet] LineageOS 18.1
LineageOS is a free, community built, aftermarket firmware distribution of Android 11, which is designed to increase performance and reliability over stock Android for your device. LineageOS is based on the Android Open Source Project with extra...
forum.xda-developers.com
Make sure your tablet is fully charged before flashing. Drag off to your desktop computer any files you want to save, pictures, DCIM, sound. Disable screen timeout in TWRP settings, screen. Installing the new ROM will go by fast. The Google Apps take time to install. Just sit and watch. When the tablet reboots again just sit and watch, lots of things happening under the hood. There may appear a Google app error. Ignore it. It only happens once.

Excellent thanks. I have one query. When Install the above , can I do it without a SD Card ?. Can I drag the files direct to the Tablet ?
Thanks again ,massive help.

Hi. All sorted and go it all installed. Thank you so much for the help and this is a great forum. Appreciate that it was a professional and easy to understand response and no trolling , which is rife these days. Thanks for the effort and time and really really glad I came across this forum. @SteinbeckFan ; thank you so much.

Congrats sandstorm I don't know what I am doing wrong but I have flashed 11 a few times and when I get to set up I get stuck at "can't find sim" so I go back to 5.02 and try again with the same result. Any suggestions for where I am going wrong or step by step to try again?

Just completed again - got it working - picked the correct Gappa - all done

SteinbeckFan said:
You are at the right place. Before you can install a new version of Android, you need to install twrp, a replacement for the stock recovery program on your tablet. For most people this is the hardest part of the whole process. If and when you install twrp, installing a new OS is a piece of cake. Please watch this Youtube video:
...
Click to expand...
Click to collapse
Thanks so much for the links and making it clear! I was able to do it super easily.
Note) I did have to chose an older TWRP version in order to be able to download it from Android File Host.
EDIT: One thing I needed to do extra was flash Magisk to get root (don't bother trying any of the samfirm, frija, samloader, etc (region code XAR) or CF-AutoRoot, SuperSU). To do so, grab the magisk.apk from the GitHub releases, then rename the extension to .zip, then flash it through TWRP. Make sure to also flash this after: "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" here: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389 and rename it to "Disable_ForceEncrypt_10.20.2019.zip"
[SOLVED] Phone gets stuck in bootloop if I try to install Magisk ZIP!
From the forum I followed these step to install magisk: - Patched my boot.img of my current rom using Magisk Manager and flashed via fastboot - After rebooting from fastboot it got stuck in recovery so had to wipe all data and it booted finally...
forum.xda-developers.com
EDIT 2: ...I'm still stuck in bootloop where it tells me to it's "formatting data"... Highly recommend making a backup in TWRP before trying to install Magisk/root.

Question Is there even ONE working custom recovery?

I bought this phone in large part due to the EDL flashing tool which OnePlus decided to lock down and start charging money for. So I'm pretty bummed to see a landscape without much activity or support from various well known projects like TWRP and Lineage. Is there any recovery out there on par with TWRP that works right now whose GitHub repo hasn't been deleted?

Custom recvoerys like TWRP dont play a big role anymore. At least i did not need one on my last 3 devices. OnePlus 8 Pro, Nothing Phone 1, Pixel 7 Pro. All have custom roms and everything is fine.
The only thing i am missing is NandroidBackup but without sdcard sot Nandroid is not really useful anyway.
Short answer: No we have no custom recovery but we dont need one.

Ia there anything working with this Nothing phone

Nandroid backup saved me so many times...
I would like so much TWRP

xtcislove said:
Short answer: No we have no custom recovery but we dont need one.
Click to expand...
Click to collapse
For me, that's not true.
I have a couple of cases that the TWRP can solve.
- delete some apps in the super partition.
- use scripts from @osm0sis to deactivate force encryption and make super partition writable again
- nandroid backup
- delete magisk modules if they make problems or bootloops
- and much more that I have forgotten

I'm not an expert, but I loved to flash ROM (before my NP!)
Now I'm with 1.5.3 with a big fear to brick my NP1 to jump on a Custom ROM
Every Custom ROM has a particular instruction to flash it, XDA is no more the basic area where the threat are updated, now is Telegram where are all the info
But these "info" are not simple and explained step by step...
TWRP would have been a safe port for me (us? @dreas74 )

... I have no such scripts.

osm0sis said:
... I have no such scripts.
Click to expand...
Click to collapse
I may have mistaken the author.
In any case, the works are inspired by you.
example:
[Deprecated] Universal DM-Verity, ForceEncrypt, Disk Quota Disabler [11/2/2020]
Hi all! For the past couple of months, I've been looking into making a more universal solution to disable dm-verity and forceencrypt. Needing to take different zips, modify them for different devices, and then cross your fingers when you switch...
forum.xda-developers.com

xtcislove said:
Custom recvoerys like TWRP dont play a big role anymore. At least i did not need one on my last 3 devices. OnePlus 8 Pro, Nothing Phone 1, Pixel 7 Pro. All have custom roms and everything is fine.
The only thing i am missing is NandroidBackup but without sdcard sot Nandroid is not really useful anyway.
Short answer: No we have no custom recovery but we dont need one.
Click to expand...
Click to collapse
I think the problem for the most users is they can't handle adb and fastboot and that's why they want a recovery. I haven't used any recovery since OnePlus 8 series and i never missed it.

P6P said:
I think the problem for the most users is they can't handle adb and fastboot and that's why they want a recovery. I haven't used any recovery since OnePlus 8 series and i never missed it.
Click to expand...
Click to collapse
Then put us in the entire light of the platform tools gods.
How can I disable encryption of the data partition and how can I delete youtube parts in the system partition with ADB or fastboot?

P6P said:
I think the problem for the most users is they can't handle adb and fastboot and that's why they want a recovery. I haven't used any recovery since OnePlus 8 series and i never missed it.
Click to expand...
Click to collapse
I use ADB and fastboot all the time, but it would be nice to regain the ability to do things without being tethered to a laptop.

Heard somewhere (Telegram group) that TWRP is coming soon.

solomon.rajan said:
Heard somewhere (Telegram group) that TWRP is coming soon.
Click to expand...
Click to collapse
How can I join this group?

solomon.rajan said:
Heard somewhere (Telegram group) that TWRP is coming soon.
Click to expand...
Click to collapse
I've been reading this almost since the release of NP1.
[Unofficial] [12.1] OrangeFox Recovery (spacewar) (Experimental)
OrangeFox Recovery ℹ️ Information Status: Experimental Version: 12.1 Release Date: 2022-08-23 Source Code: View Source on GitHub! ⬇️Download: Latest Version Download 📲 Installation on Nothing Phone 1: - Download the latest OrangeFox build from...
forum.xda-developers.com