Related
LGE - P875h - Optimus F5 BR
I need some help with CWM.
I compiled cwm from CyanogenMod JB tree, setting my device tree with the basic info on partitions sizes-places. It is now booting, but I have no LCD on.
Please take a look at my logs from the CWM boot. My post about the porting.
Anyone could point me to what is wrong?
Thankx!
So, someone knows why the recovery boots but show no UI? blank screen, nada!
If I use this recovery to flash a custom rom (is that even possible with ADB commands only? will have to look around) it should work, right?
[RECOVERY] TWRP 2.8.7.x - TeamWin Recovery Project
TeamWin is proud to present TWRP 2.8.7.x for the Samsung S4 Mini Plus (64-Bit ONLY) (I9195I)!
Youtube video: http://www.youtube.com/watch?v=RIvWVS_Rkxo
Full TeamWin credits are on the TWRP page on the TeamWin website: http://teamw.in/project/twrp2
Introduction:
Team Win Recovery Project or twrp2 for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's a fully touch driven user interface , no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Decryption of /data
Easy selection of internal/external storage
See changelog below for new features
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe cache & dalvik, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
Theming:
Information on TWRP 2 Theming - http://teamw.in/project/twrp2themers
Known Issues:
CWM backups are not compatible - please make a fresh backup in TWRP as soon as you have flashed it
Source Code:
GitHub - https://github.com/omnirom/android_bootable_recovery
Gerrit for TWRP Official Device Configs - http://gerrit.twrp.me
Gerrit Instance - http://gerrit.omnirom.org
If you have made your own twrp build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.
Support Status: Current
Maintainer: None
Code Name: serranoveltexx
DOWNLOAD:
All official devices are listed at the top of the page on the Team Win website. Search for the device in the textbox.
http://twrp.me
Serranoveltexx Download
( I am posting this on behalf of TeamWin with permission of Dees_Troy)
Some more information on the new variant.
Click Here For More Information
Is it possible to install and run this recovery without breaking the knox fuse ?
JackyJack said:
Is it possible to install and run this recovery without breaking the knox fuse ?
Click to expand...
Click to collapse
Not sure, both of my devices are tripped already.
I applied this on my i9195i and did got root/su
After a reboot it got bricked and now it keeps rebooting into TWRP recovery after this message:
kernel is not seandroid enforcing
set warranty bit: kernel
Click to expand...
Click to collapse
Edit:
Dunno what went wrong but re-installed stock rom ( I9195IXXU1AOD2 ) and re-applied twrp 2.8.7.1 with Odin. Had to update su binaries from Play Store (SuperSU) before i got root.
Try and reflash twrp recovery via Odin
Probably no cyanogen mod for this., this phone is so unpopular I am afraid a custom rom will never be released. Thanks for the recovery+root though
I also have problems installing the xposed framework after root. Everytime I try to install the framework i get the "kernel is not seandroid enforcing, set warranty bit: kernel" error.
KeesKaas said:
Probably no cyanogen mod for this., this phone is so unpopular I am afraid a custom rom will never be released. Thanks for the recovery+root though
I also have problems installing the xposed framework after root. Everytime I try to install the framework i get the "kernel is not seandroid enforcing, set warranty bit: kernel" error.
Click to expand...
Click to collapse
So does xposed not work yet on the s4 mini plus?
Seconding this, no xposed for the "plus" version?
Its too bad theres no CM for the 919xi with the Quad core, seems you cant even get the old versions with dual core any more, just had mine replaced and got the quad one.. so either have to sell it or im effed
How to know if my phone is 64 bit ?
Is it possible to change ?
I've updated the TWRP recovery, it supports brightness and additional partitions to backup now, as well as a few minor changes and optimizations for our device. Thanks to Dees_Troy for taking the time to integrate my changes into the official version of TWRP.
NxtGenCowboy said:
[RECOVERY] TWRP 2.8.7.x - TeamWin Recovery Project
Click to expand...
Click to collapse
Any chance you could support our device GT-I9195?
This looks promising. How do I install this though on my GT-i9195i?
And is a Cyanogenmod available too?
Hope someone can help me out.
Kind regards,
Dennis
Thanks, works like a charm. I wish there would be more funny things for this phone. It's cheap and quite good actually :highfive:
Tried installing twrp-2.8.7.1-serranoveltexx.img thru the TWRP manager, it said it was unsuccessful. Nothing broke thankfully. I saw 3.0.0.0 in the list too, but couldnt find any info about it anywhere. Now im too scared to try other methods.
Phone is rooted with kingroot.
I need TWRP for (Samsung Galaxy S4 Mini 32bit (serranoveltexx)) because the 64bit doesn't work for me !
look for rom i9195i
hi, sorry for ask!
does anyone know if there is a ROM for this device? i9195i 64bit
inviv said:
hi, sorry for ask!
does anyone know if there is a ROM for this device? i9195i 64bit
Click to expand...
Click to collapse
No and there propably never will be as this device is not as popular and uses different CPU structure so only if a willing dev decides to support the phone there will be a rom
---------- Post added at 02:56 PM ---------- Previous post was at 02:53 PM ----------
Safest way I found for flashing recovery is downloading the twrp.img file from the net and flashing it with flashify . Worked like a charm full root access through kingroot ->SuperSUme . Only thing is I get recovery is not seandroid enforcing warranty bit: recovery which hasn't caused any real problem so far flashing works, backups work, xposed is recommended after adding twrp and using monsterui module to get the lollipop like feel . also flashing the recovery doesn't wipe the download mode for odin so it's safe to go
---------- Post added at 02:58 PM ---------- Previous post was at 02:56 PM ----------
ahmedghazi said:
I need TWRP for (Samsung Galaxy S4 Mini 32bit (serranoveltexx)) because the 64bit doesn't work for me !
Click to expand...
Click to collapse
Search the forums for your model which is serranoltexx and follow instructions there
inviv said:
hi, sorry for ask!
does anyone know if there is a ROM for this device? i9195i 64bit
Click to expand...
Click to collapse
There actually is a ROM.. Check my thread: "[index] s4 mini plus" http://forum.xda-developers.com/showthread.php?t=3283053
Sent from my GT-I9195I using XDA-Developers mobile app
NxtGenCowboy said:
Code Name: serranoveltexx
Click to expand...
Click to collapse
Stupid question from my side:
The code name that I know is serranoltexx. Why is it serranoveltexx for TWRP?
Credits:
@T10NAZ - who supplied the kernel and a lot of guidance/help
Compile Yourself:
Guide to compiling yourself: http://forum.xda-developers.com/zenwatch-2/help/wip-compiling-twrp-wi502q-wren-device-t3341435 *Will continue to update
Steps to Using:
1) fastboot oem unlock (erases your /data partition)
2) fastboot boot twrp-v3.0.0-0.jk-v3.recovery.img
*DON'T FASTBOOT FLASH RECOVERY* - Not tested
Download Recovery:
Compiled recovery.img file: https://joeykrim.com/android/devices/wren/twrp-v3.0.0-0.jk-v3.recovery.img
Known Bugs:
I'll be working on these, but if anybody else wants to - feel free to send a pull request: https://github.com/joeykrim/wren
Fixed (in v3) - thanks @Dees_Troy - 1) Unable to backup recovery partition - isn't visible from backup menu.
Fixed (in v2) - thanks @Dees_Troy - 2) The screen resolution is small.
Updated Android OS from LCA59B to LCB51 and boot and recovery partitions aren't available in TWRP backup menu.
Please post any feedback, comments, or questions. I'll do my best to update and fix bugs, but please feel free to participate!
Hell yea! Development for all Zenwatch 2 owners!
joeykrim said:
Credits:
@T10NAZ - who supplied the kernel and a lot of guidance/help
Compile Yourself:
Guide to compiling yourself: http://forum.xda-developers.com/zenwatch-2/help/wip-compiling-twrp-wi502q-wren-device-t3341435 *Will continue to update
Steps to Using:
1) fastboot oem unlock (erases your /data partition)
2) fastboot boot twrp-v3.0.0-0.jk-v1.recovery.img
*DON'T FASTBOOT FLASH RECOVERY* - Not tested
Download Recovery:
Compiled recovery.img file: https://joeykrim.com/android/devices/wren/twrp-v3.0.0-0.jk-v2.recovery.img
Known Bugs:
I'll be working on these, but if anybody else wants to - feel free to send a pull request: https://github.com/joeykrim/wren
1) Unable to backup recovery partition - isn't visible from backup menu
Fixed - thanks @Dees_Troy - 2) The screen resolution is small. Fixed now and in the v2 .img posted above
Please post any feedback, comments, or questions. I'll do my best to update and fix bugs, but please feel free to participate!
Click to expand...
Click to collapse
Excellent work. By the way, could you help me get the original boot.img? I flashed on a different model and got bootloop.
Can someone please make a TWRP backup and upload it somewhere? ... I tried to change the LCD density and now my whatch just shows a black screen when I try to boot.
But luckily I can still get into TWRP
AFAIK the lcd density is set in /system/build.prop
ro.sf.lcd_density=***number***
perhaps you can pull this from your watch, alter it and then push it back where it belongs...
I tried that, but still no display
luksab said:
Can someone please make a TWRP backup and upload it somewhere? ... I tried to change the LCD density and now my whatch just shows a black screen when I try to boot.
But luckily I can still get into TWRP
Click to expand...
Click to collapse
I am also in need of TWRP backup for WI502Q. I cannot get out of CSC Fastboot. Please help
I have a big problem. My watch is a WI502Q starts with TWRP 3.0.0.0. It can't boot and it hasn't got an OS on. I can'i install the Ota.zip. It is closed wit status 7 error. I need a full backup with TWRP or original (official) Boot.img, recovery.img and system.img. Could you help me, please? Thank you in advance.
Did you ever get these files?
Loop2323 said:
I have a big problem. My watch is a WI502Q starts with TWRP 3.0.0.0. It can't boot and it hasn't got an OS on. I can'i install the Ota.zip. It is closed wit status 7 error. I need a full backup with TWRP or original (official) Boot.img, recovery.img and system.img. Could you help me, please? Thank you in advance.
Click to expand...
Click to collapse
I'm in a similar situation as you and I'm not sure what to do. Were you able to find anything? Can anybody provide me with a TWRP backup?
Joeykirm now do zenwatch 3 plzkthx
momentandroid said:
Joeykirm now do zenwatch 3 plzkthx
Click to expand...
Click to collapse
Can anyone confirm that this has worked for them? The previous posts of several people with soft bricks or boot loops and no confirming comments makes me hesitant to try it... However, I just got mine today so I'm going to go home and try to boot twrp anyways, if I'm able to complete a backup I'll post the nandroid for all you guys
I downloaded and installed (from twrp.me the new version 3.2.0-0 of the TWRP recovery for our Honor 7 and installed it using version 3.1.1-0. Installation OK but the device remains locked on bootlogo. I reinstalled version 3.1.1-0 with fastboot and the phone started without problems. I reinstalled version 3.2.0-0 with fastboot, the installation was successful but the phone remains locked on bootlogo. Has anyone tried?
yes, I did today and the same problem. I'm using 3.1.1.0
i wrote a message to Team TWRP and they removed v3.2.0.0 from the download site.
The TWRP team has released version 3.2.1-0-plank.img for the H7. Same problem as 3.2.0-0 except that this time the phone succeeds in rebooting in normal mode, but can not reboot in recovery (locked on bootlogo)... Back to 3.1.1-0 ... wait & see
p.s: I warned them
I thought the twrp team was a serious team. But do the recovery tests before publishing them?
no they don't test every release....
i assume there is an automatic build structure - as soon there are a new 'core'-version of twrp the changes are pushed to the device specific trees and at night the build will produce a new recovery for all devices....
TWRP 3.2.1-0 removed from the download site.
Hi, TWRP team response: "Thanks for the report. I will disable the job until the device tree is fixed. The files have been removed."
Someone here to fix the tree?
Would be nice to know, if TWRP writes any log file which notes the cause of the loop or if there is any way to enable a log like these.
I assume, that logcat will not work since we are in an early state of the boot-process and the adb interface won't be up at that time.
Have anyone a copy of TWRP 3.2.* ?
I deleted my copies and the only way to get them would be to create a device tree and i'm not sure how...
Dattel01 said:
Someone here to fix the tree?
Would be nice to know, if TWRP writes any log file which notes the cause of the loop or if there is any way to enable a log like these.
I assume, that logcat will not work since we are in an early state of the boot-process and the adb interface won't be up at that time.
Have anyone a copy of TWRP 3.2.* ?
I deleted my copies and the only way to get them would be to create a device tree and i'm not sure how...
Click to expand...
Click to collapse
https://androidfilehost.com/?fid=818070582850504177
thanks for your reply...
in the meantime i switched the device and my old H7 will have its eventide in the hand of my wife
Is you link a working copy or is it still the old version that crashes?
Twrp
Why there is no option for honor 7x in twrp?
** 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.