Related
Hello everyone, I just got bought a used Nexus 6P for the purpose of installing Kali Nethunter on it. I kept looking for some guide or steps to walk me through doing this but I couldn't find anything other than the official announcement that Nethunter is now supported on the Nexus 6p and it does mention how to install, but I couldn't follow them especially that I'm a noob when it comes to custom ROM installation and android stuff, here's the official announcement link in case you wanna take a look.
All I did was install TWRP application from play store and downloaded Nethunter and Magisk. I looked for some guide or tutorial to reboot into TWRP but all I found was that I have to root the device first, but as far as I now Magisk is a root for the device if I'm not mistaken, and I think I can't flash two root images at the same time. and I have a question do I need to use a USB drive to flash the Nethunter and Magisk images? cause I don't have a USB Type-C drive on hand rn,
Thanks in advance.
@Person_0
Only to have said it:
Magisk allows you to root Android, if not already rooted yet, its not a root itself.
jwoegerbauer said:
@Person_0
Only to have said it:
Magisk allows you to root Android, if not already rooted yet, its not a root itself.
Click to expand...
Click to collapse
So do you think I should root the device first to enable TWRP recovery then flash Nethunter and Magisk? and if so can I flash them without a USB by just putting the images on the device?
Person_0 said:
So do you think I should root the device first to enable TWRP recovery then flash Nethunter and Magisk? and if so can I flash them without a USB by just putting the images on the device?
Click to expand...
Click to collapse
To install Kali Nethunter neither Magisk must be installed nor a custom ROM is absolutely required, but it's required that Android is rooted ( SuperSU does this job ) and BusyBox is installed.
Also to be noted: 20 GB disk space available is required, too, if all features get installed. And, it would be of advantage if USB-Debugging got enabled.
That's all from my side. Happy installing.
jwoegerbauer said:
To install Kali Nethunter neither Magisk must be installed nor a custom ROM is absolutely required, but it's required that Android is rooted ( SuperSU does this job ) and BusyBox is installed.
Also to be noted: 20 GB disk space available is required, too, if all features get installed. And, it would be of advantage if USB-Debugging got enabled.
That's all from my side. Happy installing.
Click to expand...
Click to collapse
Thanks a lot for your reply I'm rooting the device rn, then I'll install BusyBox and I'll deal with the rest, thanks again :laugh:.
Hello,
I just managed to generate TWRP recovery for S912 Android 9 version, you can install the official TWRP app to flash with in the ROM.
But after reboot the ROM goes back to stock recovery, so for now i am installing everytime i need to use recovery, unless i am able to find a permanent solution.
Link to TWRP
Suggestions welcome if you have for keeping the recovery persistent.
Regards
I was able to keep it persistent but if I go to install all I get for folder names is a mess. Using Superceleron's generic SC normal pie rom. Appeared to install magisk but magisk manager didn't see it and I lost superuser access so I had to reflash rom. I hope you or others can pick up on TWRP for this. Unfortunately I don't have the knowledge so can only test. Liking the Superceleron rom on my T95Z(2/16) much better than poison or stock (so far... still testing...). Glad to see these old devices getting some new love. Hopefully it will continue.
rickpub said:
I was able to keep it persistent but if I go to install all I get for folder names is a mess. Using Superceleron's generic SC normal pie rom. Appeared to install magisk but magisk manager didn't see it and I lost superuser access so I had to reflash rom. I hope you or others can pick up on TWRP for this. Unfortunately I don't have the knowledge so can only test. Liking the Superceleron rom on my T95Z(2/16) much better than poison or stock (so far... still testing...). Glad to see these old devices getting some new love. Hopefully it will continue.
Click to expand...
Click to collapse
Jumbled charcters is because the ROM is encrypted and this recoveery is not able to decrypt it.
Bumping this, going to test this on Aidans rom
Update: could not confirm if it works it looks like the reset button is not mapped on Aidans rom. The weird thing is it works if I use the USB burn tool but not when I do a regular boot.
Doctorbeefy said:
Update: could not confirm if it works it looks like the reset button is not mapped on Aidans rom. The weird thing is it works if I use the USB burn tool but not when I do a regular boot.
Click to expand...
Click to collapse
Do you mean we can flash using amlogic usb burning tool, I am now struggling to install this ROM on khadas 64 android 9 ROM by Highway star
Hi @eagledipesh!
I managed to install your TWRP successfully on Aidan's ROM, thank you very much!
First I unpacked the Aidan' ROM with the Customizatio Tool, then I replaced the original recovery with your TWRP. I repackaged the ROM and flashed it with the AMLogic USB Burning Tool.
With TWRP and I did a full backup and I was also able to restore without errors. However, after restoring and booting the system, it gets stuck on AndroidTV splash screen.
Maybe I need to port the correct TWRP, because when unpacking your recovery with AIK, I saw in one of the files that the model is gxm_q201_2g, but my Android Box is gxm_q200_3g.
1. What base TWRP did you use to create your TWRP?
2. I tried porting TWRP myself from Aidan's ROM recovery, I can even get into recovery, but the letters are all scrambled. Can you help me make my own port?
ulissesemuman said:
Hi @eagledipesh!
I managed to install your TWRP successfully on Aidan's ROM, thank you very much!
First I unpacked the Aidan' ROM with the Customizatio Tool, then I replaced the original recovery with your TWRP. I repackaged the ROM and flashed it with the AMLogic USB Burning Tool.
With TWRP and I did a full backup and I was also able to restore without errors. However, after restoring and booting the system, it gets stuck on AndroidTV splash screen.
Maybe I need to port the correct TWRP, because when unpacking your recovery with AIK, I saw in one of the files that the model is gxm_q201_2g, but my Android Box is gxm_q200_3g.
1. What base TWRP did you use to create your TWRP?
2. I tried porting TWRP myself from Aidan's ROM recovery, I can even get into recovery, but the letters are all scrambled. Can you help me make my own port?
Click to expand...
Click to collapse
I used one of the twrp port guides, twrp was stock one, with stock recovery extracted from initial Android 9 builds by Highway star'
You can use the official twrp as base and then recovery from any of rom for your device
eagledipesh said:
I used one of the twrp port guides, twrp was stock one, with stock recovery extracted from initial Android 9 builds by Highway star'
You can use the official twrp as base and then recovery from any of rom for your device
Click to expand...
Click to collapse
Are you talking about the Wiko Highway Star? Any special reason for using this ROM as a base? How do I know which version of TWRP to use?
i create a twrp for my amlogic T972 but can't boot into it, don't know where to start fix bug
Can you help me build a twrp for this? Or can you teach me do that? Thank you @eagledipesh
Is there now a working TWRP for the Yoka KB2 Pro 3gb on Android 9.0? I would prefer to have an img file, but if there is really no other way, I would also take the zip version.
Thank you and best regards
I have been developing Ubuntu Touch for the Tab A 10.1 2019
This ROM has been tested on both SM-T510 (WiFi version) and SM-T515 (WiFi + LTE)
Any developers reading this and has the device with them and are interested in the project may contact me :
@midhunvnadh on Telegram
Not Working :-
Bluetooth
Audio
Anbox (Android Emulator)
MTP
I am trying to fix these.
Download Files
Download the Halium arm32 GSI file : from Here
(Optional) Download SamsungUSBTethering zip : from here
Ubports Patched Kernel : from here
Get all the above files copied to your External SD Card
Installation
WARNING : I am NOT responsible for any damage caused to your device
If you are following this post, please takeup full responsibility of your device.
Noobs at flashing ROM's can click here: https://telegra.ph/Installing-Ubuntu-Touch-T510T515-08-22
Thanks to @ahamshubham for making this
1.0 Flash STOCK Android 9.0 Pie on your device and install TWRP.
(Because not tested on STOCK Android 10.0)
1.5 Boot into TWRP and Wipe all except external SD. REBOOT to recovery.
2.0 On TWRP : Flash the Lineage 16.0 build. DON'T REBOOT.
3.0 On TWRP : Goto Install -> Install Image -> (Flash halium-boot.img) DON'T REBOOT.
4.0 On TWRP : Goto Install -> (Flash ubports_GSI_installer_V1-arm32.zip).
5.0 (Optional) : Goto Install -> (Flash samsung-usb-tethering.zip)
5.1 Reboot.
(Incase : unable to boot ? , boot into TWRP -> reboot -> system)
samsung-usb-tethering.zip is used to get an SSH console from device to PC. Credits to @erfanoabdi
Please report all the errors you encounter here.
Sources
Kernel : https://github.com/midhunvnadh/android_kernel_samsung_gta3xlwifi
Device Tree : https://github.com/midhunvnadh/device_samsung_gta3xlwifi
GSI arm32 : https://github.com/midhunvnadh/android_device_halium_ubport
The Device tree is a dummy tree with kernel sources linked. Which serves a purpose of compiling halium-boot.img. For more info contact me.
Donations are always appreciated : Just click here
Reserved
Reserved
Pick me! Pick me!
I will gladly take that on. Just got down installing lineage ,17.1 with Kali Linux.. I will see what I can't get done tonight.
mikehunt723 said:
I will gladly take that on. Just got down installing lineage ,17.1 with Kali Linux.. I will see what I can't get done tonight.
Click to expand...
Click to collapse
Hello, you gave me a first reply... !!!
This is my real thread post on ROM's.
I didn't understand what you meant by "Pick me" and "I will gladly take that on. "
Are you looking forward to make contribution to this project ?
Bruh this is amazing work, keep it going!
This looks like an interesting project, none of the download links work for me
nubianprince said:
This looks like an interesting project, none of the download links work for me
Click to expand...
Click to collapse
It is a direct link. It works for me ?
Can you support Galaxy Tab A6?
Mohamed677 said:
Can you support Galaxy Tab A6?
Click to expand...
Click to collapse
I can try if you can give me a device.
Mohamed677 said:
Can you support Galaxy Tab A6?
Click to expand...
Click to collapse
The sm-t580? I tryed like a month ago, and i got the boot.img file to compile for halium7, but not the system image, and los14 is broken so it cant work anyway, and, when i tryed to compile using halium9, i had missing libs.
I also tryed postmarketOS, and it did not boot
(Well, if it did, and i think it did because it didnt reboot into download mode automatically), and screen and usb wasnt working
MIDHUN.V.NADH said:
1.0 Flash STOCK Android 9.0 Pie on your device and install TWRP.
Click to expand...
Click to collapse
Wow. This is exciting news. Really have been longing for a non-android based OS for a long time. Thanks a ton. Will surely donate when I get a job(currently unemployed due to covid):good:
What do you mean by installing stock? You are going to installing LOS 16.0 so can that not be the starting point? Do I have to go back and install stock using Odin and do the whole process again?
aveemashfaq said:
Wow. This is exciting news. Really have been longing for a non-android based OS for a long time. Thanks a ton. Will surely donate when I get a job(currently unemployed due to covid):good:
What do you mean by installing stock? You are going to installing LOS 16.0 so can that not be the starting point? Do I have to go back and install stock using Odin and do the whole process again?
Click to expand...
Click to collapse
Yes, you have to do all those steps.
Why I am asking everyone to install Stock 9.0 is because :
1. On Samsung Exynos Devices developers have an hard time developing Ubuntu Touch.
2. There are changes in partition structure going on from upgrade to Stock 9.0 to 10.0
3. The kernel source of stock Android 9.0 is VERY different from 10.0
4. I wasn't able to get logs from Stock 10.0 due to the partition changes mentioned on (2)
5. Halium 9.0 (Build Engine for Touch) highly recommends Android 9.0/Lineage 16.0 as a base to install upon.
6. Moreover I haven't tested if it boots on stock 10.0 because of (2), (3), (5) and I am currently fixing the bugs.
Please try to out on AOSP 10.0 and let me know if it work
Hello! I installed it on my Galaxy Tab A 2019 T510, however, a strange problem happens. Suddenly the screen goes dark and I can't do anything, even pressing the power button. A little while later the screen goes black, forcing me to use the Volume - / Power keys to restart. Anyone else going through this? I have another question: the installation file (ubports gsi) says arm32. Is the architecture of this tablet arm34 or arm64?
Geek_Ceará said:
Hello! I installed it on my Galaxy Tab A 2019 T510, however, a strange problem happens. Suddenly the screen goes dark and I can't do anything, even pressing the power button. A little while later the screen goes black, forcing me to use the Volume - / Power keys to restart. Anyone else going through this? I have another question: the installation file (ubports gsi) says arm32. Is the architecture of this tablet arm34 or arm64?
Click to expand...
Click to collapse
Hi !, Were you able to boot into the OS ?
I haven't faced that issue can you elaborate ?
The Tablet has an arm64 kernel but the vendor and system are both arm32.
I had to make the arm32 GSI for ubuntu touch to run on this tablet.
The GSI will also work for devices with the arm32 vendor and system.
Geek_Ceará said:
Hello! I installed it on my Galaxy Tab A 2019 T510, however, a strange problem happens. Suddenly the screen goes dark and I can't do anything, even pressing the power button. A little while later the screen goes black, forcing me to use the Volume - / Power keys to restart. Anyone else going through this? I have another question: the installation file (ubports gsi) says arm32. Is the architecture of this tablet arm34 or arm64?
Click to expand...
Click to collapse
Hi ! Thank you for your reply.
Were you able to boot into the OS ?
I haven't faced that issue. Can you elaborate ?
The Tablet has an arm64 kernel but the vendor and system are both arm32 eventhough some devices with the same SoC has full arm64.
I am trying to port arm64 vendor into the device but I think arm32 will be better because the device only has 2GB RAM (Atleast on my device)
I had to make the arm32 GSI for ubuntu touch to run on this tablet.
The GSI will also work for devices with the arm32 vendor and system.
Worked!!
I was looking forward to run Ubuntu Touch on my Samsung Galaxy Tab A (SM-T515NZKDINU). I contacted MIDHUN.V.NADH, he helped me through the process and we got Ubuntu Touch running on my device. I would like to thank him for his help and his post. I, however, felt that I could not follow the instructions in the post very easily. Maybe, this is because I am doing something like this for the first time. So, I compiled a list of instructions to follow. I will send him this list of instructions and post them here too. I feel they will be helpful for people looking to run Ubuntu Touch on the same device.
MIDHUN.V.NADH said:
Hi !, Were you able to boot into the OS ?
I haven't faced that issue can you elaborate ?
The Tablet has an arm64 kernel but the vendor and system are both arm32.
I had to make the arm32 GSI for ubuntu touch to run on this tablet.
The GSI will also work for devices with the arm32 vendor and system.
Click to expand...
Click to collapse
Yes. I managed to initialize, however, this problem happens to me. I uninstalled Ubuntu and returned to android. Someday, when I have something stable, I test it again.
And about the processor architecture, I understand your explanation. Thank you!
Just adding instructions on how I did it on my device
My device details:
Device Model Number: SM-T515 (NZKDINU)
Linux Kernel Version: 4.4.111-17420370
Instructions for SM-T515:
1) Download these files using the links given in the post I am commenting on:
a) Halium arm32 GSI file
b) Ubports Patched Kernel
c) (Optional) SamsungUSBTethering zip
2) Copy all the above files to your External SD Card and insert this SD card in the device (tablet)
3) Flash STOCK Android 9.0 Pie on your device (tablet) and install TWRP:
a) For installing TWRP, use the following post: https://forum.xda-developers.com/ga...very-twrp-3-3-1-2019-galaxy-tab-10-1-t3934805. The instructions for installing TWRP as given in this post are:
i) Unlock bootloader (See the end of my comment)
ii) Hold Vol Up & Vol Down buttons during restart to enter Download mode
iii) Install TWRP to AP with Odin
iv) Hold Power & Vol Up buttons during restart to enter TWRP recovery
v) On TWRP: Swipe to allow modifications
vi) On TWRP: Wipe -> Advanced Wipe -> Select all except SD card
vii) On TWRP: Reboot -> Recovery
4) On TWRP: Go to Install -> Install Image -> (Flash halium-boot.img. Partition to flash image is BOOT). DON'T REBOOT. PRESS BACK.
5) On TWRP: Go to Install -> (Flash ubports_GSI_installer_V1-arm32.zip. Don't check any check boxes)
6) (Optional) On TWRP: Goto Install -> (Flash samsung-usb-tethering.zip)
7) Reboot
8) Ubuntu Touch will open. The password is: phablet
Unlocking Bootloader (Check this post: https://www.getdroidtips.com/oem-unlocking/):
1) Enable Developer Mode in Device Settings
2) Enable OEM Unlocking Option in Developer options after connecting to WiFi and setting the year in the phone to the year 2019
3) Get into Device Unlock Mode: Press (Volume Up Key + Volume Down Key + Insert USB Cable in the phone) while restarting the phone
4) Unlock bootloader. (Very Important!!) DON'T LET THE DEVICE BOOT INTO THE ANDROID OS AFTER UNLOCKING DEVICE BOOTLOADER
MIDHUN.V.NADH said:
Yes, you have to do all those steps.
Why I am asking everyone to install Stock 9.0 is because :
1. On Samsung Exynos Devices developers have an hard time developing Ubuntu Touch.
2. There are changes in partition structure going on from upgrade to Stock 9.0 to 10.0
3. The kernel source of stock Android 9.0 is VERY different from 10.0
4. I wasn't able to get logs from Stock 10.0 due to the partition changes mentioned on (2)
5. Halium 9.0 (Build Engine for Touch) highly recommends Android 9.0/Lineage 16.0 as a base to install upon.
6. Moreover I haven't tested if it boots on stock 10.0 because of (2), (3), (5) and I am currently fixing the bugs.
Please try to out on AOSP 10.0 and let me know if it work
Click to expand...
Click to collapse
Hi, I just tried it out on my device. I had stock 9.0 over which I had flashed Lineage OS 17.1(based on Android 10). Over that, I flashed LOS 16, halium-boot, ubports-gsi and usb tethering. Worked for me.
I have to say, I have a pinephone and it seems that ubports on Samsung tab is faster than on pinephone.
antoine62 said:
The sm-t580? I tryed like a month ago, and i got the boot.img file to compile for halium7, but not the system image, and los15 is broken so it cant work anyway, and, when i tryed to compile using halium9, i had missing libs.
I also tryed postmarketOS, and it did not boot
(Well, if it did, and i think it did because it didnt reboot into download mode automatically), and screen and usb wasnt working
Click to expand...
Click to collapse
Did you ever get this to work/ any tips for trying because I really want this to work (I am trying at the moment).
** UNOFFICIAL A-TEAM RELEASE**
*******Testing ONLY*******
**testing has only been done on GN2200 July patch device but should atleast boot into twrp on other sec patch on GN2200 devices***
***Let us know if not***
*****HEED THE WARNING OF IMPENDING APOCALYPSE, DOOM, BOOTLOOPS , BRIMSTONE AND FIRE, AND ALSO TWRP ******
***NOBODY IS RESPONSIBLE FOR WHAT YOU DO WITH THIS EXCEPT YOU***
***DO NOT BUILD AND FLASH THIS UNLESS YOU KNOW EXACTLY WHAT YOUR DOING***
****DONT DO ANYTHING I SAY, I CANT BE HELD RESPONSIBLE FOR WHAT I SAY OR DO*****
**THIS IS AN ** UNOFICIAL RELEASE ** SO DONT GO CRYING TO ANYONE THAT YOU MADE YOURSELF AN EXPENSIVE PAPERWEIGHT IF YOU USE ANYTHING IN THIS POST***
********* THE RESPNSIBILITY LIES SOLELY UPON YOU***
***FLASHING IN CURRENT STATE DOES NOT BOOT INTO SYSTEM****
****READ EVERYTHING BEFORE YOU DO ANYTHING******
******ONLY POSTING THIS FOR DEV PURPOSES*******
******Huge THANKS to PizzaG for this!!!******
***Thanks to Eduardo as well for his contributions, he may still be working on his own release***
Am posting this with a copy/paste i posted in telegram group..
We need people with the knowledge/skills and experience to help get this TWRP finished AND/OR work out the bugs.
GitHub - PizzaG/recovery_device_oneplus_OP515AL1
Contribute to PizzaG/recovery_device_oneplus_OP515AL1 development by creating an account on GitHub.
github.com
*this is not ready for release but the source is here for anyone who can build upon it*
touch is not working
you cant fastboot boot on this device so DO NOT flash this to your device without a backup of your stock/current boot image
issues we are having is no touch, can't mount /data, and so far cant boot into system with the recovery installed so if you want to use it youll need to flash this to boot, use it for whatever and then flash stock boot back, if your magisk patched youll need to flash the backup of that patched boot image you made before flashing this in order to get back into your system....... i have sort of found a slight work around for having to keep flashing the boot partitions until someone can get this to boot by placing my current boot image on an sdcard along with the twrp, flash the twrp to the active boot partition, boot into twrp, install image and install your backed up boot image to the current slot, then go back to advanced and install twrp to ramdisk and select and install the twrp image to the ramdisk, if your magisk patched you need to flash magisk zip right now, you can adb shell into twrp to pull a copy of this boot image if you want and i have flashed my "twrp-ramdisk installed boot image" on the Slot that my system is on and stock/backup boot image to inactive slot because its the only way to boot back to system for now without reflashing the stock(backed up) boot image back to the slot. and reboot into bootloader, change active and reboot and your back into your system.... when you need twrp you can set active to the other slot, it will bootloop once into bootloader and choose recovery to get back to twrp... when done reboot to bootloader and set active back to the other slot and reboot into system.............otg mouse works, adb works, mtp works, some work has been done on the touch but thats still not working yet, everything seems to be mounting except data............. big shout out to PizzaG for this
***this is a very round-about way to get a currently buggy twrp on the device but if you have a usb-c adapter and mouse you can navigate twrp....***
PizzaG doesnt have the device and has spent more time than anyone could possibly ask someone to spend on this for free... I dont have the skills required yet to really work on this. I have tested as much as possible and here it is for those who can build and work on it. i dont recommend releasing in its current form because im sure alot of people will be complaining and bricking their devices. if you can build it im sure you can work on it and should have the skills to atleast recover and have the sense to make backups first.......
Thanks again to everyone who has already donated the valuable time working on this for us and to everyone who will follow and build upon this!
You can find the telegram group for our device here:
You can find the A-Team in telegram
Also FYI in case you missed the post about our kernel source, it can be found here:
GitHub - OnePlusOSS/android_kernel_msm-5.4_oneplus_sm6375 at oneplus/sm6375_r_12.0.1_oneplus_nord_n20_5g
Contribute to OnePlusOSS/android_kernel_msm-5.4_oneplus_sm6375 development by creating an account on GitHub.
github.com
If anyone with experience building twrp and especially for OnePlus devices needs a tester or any files from the device hit me up on telegram @PsYk0n4uT2 and I will do my best to provide whatever you need and test builds along with providing logs.
heres a compiled boot image from the above tree as of 10/02/2022.
**remeber it DOES NOT boot to system, this is twrp only, not installed into recovery ramdisk yet. so BACKUP YOUR STOCK(current) boot image FIRST**** you will have to flash your stock(current) boot image back to boot back into your system. you can sort of get around this by above mentioned method BUT here it is for the GN2200 anyways. working on my July patched device and my May patched device so it should work for other GN2200 sec patches too...
***BACKUP BACKUP BACKUP*****
also cant change active slot from twrp, must reboot to bootloader to change active slot
Heres TWRP installed to ramdisk on a july patched boot image. does not boot to system but since it doesnt you should still be able to use this on any patch for testing purposes.....
You can backup your boot image and flash your current boot image to inactive slot and flash this to active slot by selecting recovery from bootloader after it loops once.... use twrp then go back to bootloader and change active and reboot to get back into your system.
**BACKUP YOUR CURRENT BOOT IMAGE****
***DOES NOT BOOT TO SYSTEM**
***YOU WILL NEED YOUR CURRENT BOOT IMAGE TO BOOT YOUR SYSTEM< YOU SHOULD ALREADY HAVE A BACKUP OF YOUR STOCK IMAGE IN THE CASE THAT YOU ARE MAGISK PATCHED ALREADY< KEEP A COPY OF BOTH IN CASE YOU DECIDE TO WIPE DATA< YOU WILL NOT BOOT BACK INTO YOUR SYSTEM WITH A MAGISK PATCHED BOOT IMAGE IF YOU WIPE DATA*******
if someone can get their system to boot after installing the TWRP from post 4 or their own build after personal edits please post here how you were able to achieve the install and maintain booting into system..
currently twrp indicates that path to /mnt could not be found and cant mount /data .. i think if someone could fix this maybe some progress could be made
ScarletWizard said:
I wonder if TWRP will work for devices with a serial number defeicy
Click to expand...
Click to collapse
halfway working on mine, just isnt finished yet, we need someone who knows alot more about this than i do. another dev is working on twrp but needs a device. the serial wont affect anything else other than the oneplus care app and getting the unlock token..... other than that u have full functionality.... the one posted above needs ALOT of work to finish. no touch yet but it could work for SOME things....
I know C/C++ at a decent level, however; I don't have much experience with low level stuff (especially dealing with bootloaders and other specific proprietary android kernel stuff). If there is anything that needs testing, I am down for it since this is just a secondary phone for me and I won't be too upset if it explodes.
I'm going to attempt this
[ SOLUTION ] [ MTK ] to Fix Touch not Working on TWRP / Philz Due to Kernel Disabled Touch.
In this tutorial, i'm going to show how i managed to patch kernel to enable touch in recovery TWRP / Philz. WARNING : This worked fo...
factopea.blogspot.com
It's written for mtk device but might have similar enough instructions to port for qcom kernel,
But I believe this is what is needed to get the TWRP touch going
Is the trwp.fstab using the right version? Both have different
Code:
/dev/block/bootdevice/by-name/userdata /data f2fs noatime,nosuid,nodev,discard,inlinecrypt,reserve_root=32768,resgid=1065,fsync_mode=nobarrier latemount,wait,resize,check,formattable,fileencryption=aes-256-xts:aes-256-cts:v2+inlinecrypt_optimized+wrappedkey_v0,keydirectory=/metadata/vold/metadata_encryption,metadata_encryption=aes-256-xts:wrappedkey_v0,quota,reservedsize=128M,checkpoint=fs
Try this instead in twrp.fstab
Code:
/data f2fs /dev/block/bootdevice/by-name/userdata flags=fileencryption=ice:aes-256-cts;wrappedkey;keydirectory=/metadata/vold/metadata_encryption
Techted89 said:
Is the trwp.fstab using the right version? Both have different
Code:
/dev/block/bootdevice/by-name/userdata /data f2fs noatime,nosuid,nodev,discard,inlinecrypt,reserve_root=32768,resgid=1065,fsync_mode=nobarrier latemount,wait,resize,check,formattable,fileencryption=aes-256-xts:aes-256-cts:v2+inlinecrypt_optimized+wrappedkey_v0,keydirectory=/metadata/vold/metadata_encryption,metadata_encryption=aes-256-xts:wrappedkey_v0,quota,reservedsize=128M,checkpoint=fs
Try this instead in twrp.fstab
Code:
/data f2fs /dev/block/bootdevice/by-name/userdata flags=fileencryption=ice:aes-256-cts;wrappedkey;keydirectory=/metadata/vold/metadata_encryption
Click to expand...
Click to collapse
i just unpacked the twrp image with AIK and made the suggested edits and repacked, reflashed, same...... another person is working on twrp and has gotten much of the fstab corrected in their build but their keeping their source closed til they get it ready for release and is still very far from being finished with it and doesnt have much time to work on it right now so we are just kinda stuck waiting on someone that knows what their doing to help get this going. the other person has touch working on theirs so i know its possible i just dont know how long it will be before we see a beta even
Techted89 said:
Is the trwp.fstab using the right version? Both have different
Code:
/dev/block/bootdevice/by-name/userdata /data f2fs noatime,nosuid,nodev,discard,inlinecrypt,reserve_root=32768,resgid=1065,fsync_mode=nobarrier latemount,wait,resize,check,formattable,fileencryption=aes-256-xts:aes-256-cts:v2+inlinecrypt_optimized+wrappedkey_v0,keydirectory=/metadata/vold/metadata_encryption,metadata_encryption=aes-256-xts:wrappedkey_v0,quota,reservedsize=128M,checkpoint=fs
Try this instead in twrp.fstab
Code:
/data f2fs /dev/block/bootdevice/by-name/userdata flags=fileencryption=ice:aes-256-cts;wrappedkey;keydirectory=/metadata/vold/metadata_encryption
Click to expand...
Click to collapse
also i see a recovery.fstab instead of twrp.fstab in /system/etc. is this what your referring to?
You need both from what iv read ,. TWRP.flags is a module that rewrites the stab at a certain point which may be the reason it's not compiling but I will post. Recovery.fstab is supposed to be a copy paste from the boot.img and gives the general mount partitions locations,. TWRP.fstab is mounted using the same partitions but different format/flag structure to be available to TWRP .
Techted89 said:
You need both from what iv read ,. TWRP.flags is a module that rewrites the stab at a certain point which may be the reason it's not compiling but I will post. Recovery.fstab is supposed to be a copy paste from the boot.img and gives the general mount partitions locations,. TWRP.fstab is mounted using the same partitions but different format/flag structure to be available to TWRP .
Click to expand...
Click to collapse
Interesting article above. Were you able to get that to work? I know it says MTK but seems like mechanism should be the same, or atleast I would assume anyways that the function would be very similar in the case of a flag. Was told you needed to use original kernel but then I couldn't get that to boot period. I'm out of my area of knowledge at this point but always willing to learn.
Also I tried messing around a little with the f stab and TWRP flags I was told that TWRP flags is pretty much the same as the twrp.fstab... also this build needs to have something added to the drivers I do believe that this is somehow related to USB touch it is a goodix gt9886 touch panel using the Samsung 9886 drivers. Maybe the init's need some help here as well.
I have the programming knowwledge that TWRP would require, but have not as of yet created one as my devices were typically readily complete before-hand. Once my device is back up, and running I am going to boot into Ubuntu and give it a go.
I need some excuse to have learned assembly x86, c, c++, Java, Python, and rust and have been eyeing learning scripting so it could be a fun side project assuming it is still incomplete as of the moment?
Is it normal for manufacturers to use components from other's in their builds? The kernel posted seemed to indicate at least a couple Samsung files included.
Well C is a guarantee possibly some C++ as well and definitely some sh scripting if you know rust and know how to attach it to C well enough that could add more possibilities I would imagine. The recovery is from my understanding in the boot image Android Image Kitchen would help you see it unmodified if that is the case.
I found a unofficial TWRP that flashes to the boot partition, and works pretty damn well, id have to say! I am not an experienced developer, I just like to flash around on my phone in my spare time.. Anyways here y'all go:
I am down while I got partitions backed up to the cloud.
Please has anyone been able to port TWRP recovery for an a/b partitioned device, I mean devices that contains the recovery ramdisk in the boot.img and doesn't have a separate recovery partition.
Thanks in advance.
Kelexine said:
Please has anyone been able to port TWRP recovery for an a/b partitioned device, I mean devices that contains the recovery ramdisk in the boot.img and doesn't have a separate recovery partition.
Thanks in advance.
Click to expand...
Click to collapse
What do you mean by "port"?
TWRP is supported on multiple A/B devices such as the Google Pixel. However, TWRP does not support the compression necessary to replace the stock recovery in the boot image, so TWRP may only be used "live", where the TWRP image is booted via command, instead of being flashed to /boot.
V0latyle said:
What do you mean by "port"?
TWRP is supported on multiple A/B devices such as the Google Pixel. However, TWRP does not support the compression necessary to replace the stock recovery in the boot image, so TWRP may only be used "live", where the TWRP image is booted via command, instead of being flashed to /boot.
Click to expand...
Click to collapse
By porting I mean changing some files, like copying the kernel and other device specific files to a prebuilt TWRP boot image for a related device.
For example I was able to do that for my android 8 based device and it worked flawlessly, but my problem is that I don't know how to do that for a/b partitioned devices cause my device is not officially supported and i can't seem to find any unofficial version for my device, plus my phone's kernel source and device are not published on GitHub or anywhere.
But some devices specially some Mediatek and Unisoc based devices don't support live boot and so it's necessary two flash it to the boot partition.
Finally built twrp for this device after so many attempts, here is the file for those that owns this device too.
NOTE: This file is for KG5j variant not KG5k or any other variant
Kelexine said:
Finally built twrp for this device after so many attempts, here is the file for those that owns this device too.
Click to expand...
Click to collapse
hello how is the twrp for tecno spark 8c it works fine for me but when I restart the phone it enters a bootloop to the recovery
Jermaine22martinez said:
hello how is the twrp for tecno spark 8c it works fine for me but when I restart the phone it enters a bootloop to the recovery
Click to expand...
Click to collapse
I don't understand, please explain your issues so I can know how to help
Follow this guide https://forum.xda-developers.com/t/...hat-does-not-have-recovery-partition.4572311/
Jermaine22martinez said:
hello how is the twrp for tecno spark 8c it works fine for me but when I restart the phone it enters a bootloop to the recovery
Click to expand...
Click to collapse
You can use the updated version with crypto support and automatic data partition decryption.
Download from https://github.com/dextterblog/Twrp-builder/releases
Jermaine22martinez said:
hello how is the twrp for tecno spark 8c it works fine for me but when I restart the phone it enters a bootloop to the recovery
Click to expand...
Click to collapse
After flashing run fastboot reboot, it will reboot directly to TWRP recovery enter your lock screen password to unecrypt data, then click on advanced install recovery ramdisk and select the twrp.img you downloaded or click on advanced then install current TWRP and let the recovery do the rest.
Check it out on hovatek forum
Kelexine said:
Here is a copy of you can't download from GitHub.
Click to expand...
Click to collapse
Make A TWRP Tree For Your Device & Build.md
GitHub Gist: instantly share code, notes, and snippets.
gist.github.com
This Guide will help you!
FiniteCode said:
Make A TWRP Tree For Your Device & Build.md
GitHub Gist: instantly share code, notes, and snippets.
gist.github.com
This Guide will help you!
Click to expand...
Click to collapse
Thanks but I already compiled for my device
Kelexine said:
Thanks but I already compiled for my device
Click to expand...
Click to collapse
Great! No Problem...
(*Sigh* Why Am I So Late At Everything?)
FiniteCode said:
Great! No Problem...
(*Sigh* Why Am I So Late At Everything?)
Click to expand...
Click to collapse
Just keep trying your best
New release: TWRP recovery for TECNO SPARK 8C
Link to files are here for latest build look here and for direct download click here