Would you know why twrp is not booting, is because kernel is enforcing. I'm trying to build a permissive kernel but there are too errors I'm unable to fix, maybe if someone tries my same task we can get it done.
How to add phone call/voice call function with T227?
Can we apply T225 rom?
No, you can't install firmware from T225, it's a different model...
As an option, root the T227 and add the missing files for calls to work, the files can be taken from the T225 firmware ...
TWRP for Samsung Galaxy A7 Lite SM-T220 SM-T225 SM-T227
/* * Your warranty is now void. * * I am not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about features included in...
forum.xda-developers.com
I finally got rid of T227 (T-Mobile - between that my Note 10+5g which but for the grace and help of Sr member Afaneh92, I would have tossed) I learned a lesson from my experiment purchasing phones from carriers. So, I purchased this:
The topic of this thread is the existence, or not, of other possible ROMs for it. This device is supposed to be not only cellular for data, but is supposed to make and receive phone, text, etc.Initially, because T-Mobile actually owed me a refund, I figured I'd keep their SIM, plug it in and no worries even though I knew the SIM was for data only. So, I was not surprised when the phone did not work and when it eventually caused the issue described below.
As a background, once you get the hang of patching etc, Magisk/rooting is a breeze...just get the official firmware and patch the whole AP file - I do it in the device itself.. it takes longer but it is within my ability! I was even able to download the updated firmware last week get root. fact, at the risk of heaping off-topic praise on the developers of Magisk/LSPosed, the result is a device that is easy to adjust with exponentially more stable functionality! It's given my old galaxy note 10+ 5G another year or two of life! No vbmeta or apparent issues.
My last TWRP experience taught me my limits and how complex it is becoming to develop a recovery for Samsung devices. I love TWRP but I am not a developer. I can clean the cache, do reasonably ok image backups overcome whatever barriers I need for my simple issues.
Back on topic, I need a ROM because no matter what LTE SIM I use (all are rated or approved for this device), the same result: after setting up the device from a clean wipe and reset, all is well. SIM is recognized and functional, wifi works and everything is great. I even have my own phone number assigned for calls and messages - specifically. The problem begins if I step one inch beyond using the LTE as just a provider of data in a passive way, to anything "active" i. e., attempting to send a text or, god forbid, making a phone call. Within seconds after either of those activities, the SIM "dissappears" and when attempting anything requiring LTE, the message is always that I need to install a SIM. I have read hundreds of pages and the suggestions are all the same. Once the SIM is no longer recognized, no amount of fiddling with the SIM, replacing it with a different SIM, cleaning the data from the appropriate drivers, will do anything. The Tablet has to be wiped and factory reset again in order to get the it to recognize the SIM again. My reading does not reveal anyone else reporting this kind of pattern - more worryingly, there is never a conclusion one way or another regarding the general complaint of a SIM not being recognized. Samsung INSISTS that an unlocked world tablet like this can become your new phone! The phone application is part of the device's OS!
With no precedent or guidance that I can find, I have been reduced to hoping that a different ROM would somehow enable the device to do what Samsung swears it can do. I am pretty much hoping for a ROM or a miracle!
The topic of this thread is the existence, or not, of other possible ROMs for it. This device is supposed to be not only cellular for data, but is supposed to make and receive phone, text, etc.Initially, because T-Mobile actually owed me a refund, I figured I'd keep their SIM, plug it in and no worries even though I knew the SIM was for data only. So, I was not surprised when the phone did not work and when it eventually caused the issue described below.
As a background, once you get the hang of patching etc, Magisk/rooting is a breeze...just get the official firmware and patch the whole AP file - I do it in the device itself.. it takes longer but it is within my ability! I was even able to download the updated firmware last week get root. fact, at the risk of heaping off-topic praise on the developers of Magisk/LSPosed, the result is a device that is easy to adjust with exponentially more stable functionality! It's given my old galaxy note 10+ 5G another year or two of life! No vbmeta or apparent issues.
My last TWRP experience taught me my limits and how complex it is becoming to develop a recovery for Samsung devices. I love TWRP but I am not a developer. I can clean the cache, do reasonably ok image backups overcome whatever barriers I need for my simple issues.
Back on topic, I need a ROM because no matter what LTE SIM I use (all are rated or approved for this device), the same result: after setting up the device from a clean wipe and reset, all is well. SIM is recognized and functional, wifi works and everything is great. I even have my own phone number assigned for calls and messages - specifically. The problem begins if I step one inch beyond using the LTE as just a provider of data in a passive way, to anything "active" i. e., attempting to send a text or, god forbid, making a phone call. Within seconds after either of those activities, the SIM "dissappears" and when attempting anything requiring LTE, the message is always that I need to install a SIM. I have read hundreds of pages and the suggestions are all the same. Once the SIM is no longer recognized, no amount of fiddling with the SIM, replacing it with a different SIM, cleaning the data from the appropriate drivers, will do anything. The Tablet has to be wiped and factory reset again in order to get the it to recognize the SIM again. My reading does not reveal anyone else reporting this kind of pattern - more worryingly, there is never a conclusion one way or another regarding the general complaint of a SIM not being recognized. Samsung INSISTS that an unlocked world tablet like this can become your new phone! The phone application is part of the device's OS!
With no precedent or guidance that I can find, I have been reduced to hoping that a different ROM would somehow enable the device to do what Samsung swears it can do. I am pretty much hoping for a ROM or a miracle!
I have seen references to GSI, throughout these discussions. I have no idea what it is because I wanted to stay within the bounds I knew and from which I bring the phone from most bad mistakes. Can you tell me the short version of what its purpose is and at my level, can I do it.
The different gsi and custom is kernel
Rom Gsi use generic kernel , rom .zip use kernel build for one device
And some bugs
Building a bespoke kernel just for my device sounds like a detailed undertaking although I suppose it be the best. A generic sounds great as long as there is enough control in the of the device.
I using banana droid gsi , is perfect rom ever
I don't want try custom kernel or other because my volume up is break , can boot into recovery in power off
At this point, I now realize that I probably should have patched only the boot.img instead of the whole AP tar because of the Vbmeta.img issues (empty vbmeta.img or something like that). I am wondering if it's possible to discreetly flash the vbmeta.img from the stock materials without causing the tablet to complely collapse again and even if possible, and then somehow, I mange to flash TWRP, it will get me any closer to being able to access my SIM (which, of course, has gone out again), on a stable basis so I can use the device to text, call etc, as it was supposedly designed to do. Or, do you think this generic GSI kernal (using the patched stock ROM) even if not perfect, will give me stable access to the SIM card to call, text or whatever? I don't need perfection; I just need root access and the LTE function! This is exhausting!
And, if using GSI depends on extensive use of Fastboot (and I am comfortable using Fastboot), the tablet does not seem to have the ability to use the Fastboot commands. I gave a half hearted attempt to patch the stock recovery with this FastbootD, but that was going nowhere, fast!
1.Default no fastboot for Sam devices.
2.You can uses Fastboot mode of TWRP. (must have suitable bootloader driver for accessing.)
3.FastbooD is the best choice , if you asked me. ( for GSIs)
Thanks man. I really would like to get the LTE functional. I already got the seller to refund the purchase price.. Because apparently this thing is a problem. But, I do like the device itself. I have a phone, watch and don't need a huge tablet..
I have a phone already.. In fact Afenah helped me root it 1 year ago.. I don't know if there are any tablets that run on linix
I don't understand why someone use pinephone and install waydroid to play long time game like Pubg , genshin inpact
Last edited:
I use this Tab for e-book and clash of clans , when i play coc , is so hot and battery (gsi) badly than stock
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
2Rooting itself is incredibly easy, just use the Magisk patched AP method after you unlock the bootloader.
As for custom recoveries. I've been working on it for a bit trying to port a working build, but as of this moment the only thing I have is a successful Odin flash with no actual TWRP boot (It just hangs at the "phone is not running Samsung official firmware" indefinitely, not an actual loop). Of course even with the broken recovery flashed, I can still boot to system, so I dunno.
But if anyone wants to give a fresh set of eyes and see if I've missed anything, I've attached a zip of the odin-ready recovery.img and the decompiled twrp build. Just let me know.
TLDR: For anyone just glancing over this, this IS NOT a working TWRP port2
Have you made any headway? I also spent a significant amount of time attempting to port TWRP. I was able to get TWRP to boot but touch did not work. Plugging in a mouse to a usb dongle, I was about to navigate TWRP but I was not able to do much. I had probelms mounting and editing the DATA partition. Im guessing it was an FSTAB config or an android 11 partitioning problem. I'm pretty fresh to this stuff but still made some progress. I gave up a bit ago but maybe I'll mess around with it a bit more.1
Check out these guides out. The steps are mostly similar for recent Samsung tablets,
https://forum.xda-developers.com/t/guide-unlock-the-tab-s7-bootloader.4158841/
https://forum.xda-developers.com/t/how-to-root-galaxy-tab-s7-guide.4155897/page-511
