{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Team Win Recovery Project (TWRP) is an open-source software custom recovery image for Android-based devices. It provides a touchscreen-enabled interface that allows users to install third-party firmware and back up the current system, functions often unsupported by stock recovery images. It is, therefore, often installed when rooting Android devices, although it isn't dependent on a device being rooted to be installed.
NOTE : THIS IS A WORK IN PROGRESS PROJECT, PROCEED AT YOUR OWN RISK.
Click to expand...
Click to collapse
Features:
Decryption working
Removed TWRP App
Adjusted clock position
Custom dark theme
Installation
Download recovery.img and twrp-installer-fajita-3.2.3-*.zip
Copy twrp-installer-fajita-3.2.3-*.zip to internal storage
Reboot to fastboot
From fastboot: fastboot boot recovery.img
From recovery: install twrp-installer-fajita-3.2.3-*.zip
Or: adb sideload twrp-installer-fajita-3.2.3-*.zip
If you are on custom recovery, simply install twrp-installer-fajita-3.2.3-*.zip (you don't have to download recovery.img)
Flash Magisk after installing recovery
Download
Builds: androidfilehost
Source code:
https://github.com/HelllGuest/twrp-fajita
Credits:
@eng.stk
@xls654
@squid2
@micky387
@mauronofrio
@Dees_Troy
Known issues
Restoring backup (Not tested)
Changelog
01-Dec-2018:
Initial build.
Confused...there 2 twrp's now?
We have a working unofficial TWRP for the 6T.
https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482
Wow, really? This guy posts to help and this is what he gets? While we do have a working twrp, the other thread is filled with people with issues, and random twrps being posted, so maybe his works better. Thank you sir for your work
Is It possible a recovery that support multirom?
Sent from my [device_name] using XDA-Developers Legacy app
suzook said:
Confused...there 2 twrp's now?
Click to expand...
Click to collapse
biohaz55 said:
We have a working unofficial TWRP for the 6T.
https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482
Click to expand...
Click to collapse
First time seeing multiple twrp for a single device ?
If you're confused, then try both.
We dont need this.
Please, all projects are good, thanks @AnoopKumar
What are the benefit(s) of this particular recovery compared to the one(s) in the other thread? From a first glance they look basically the same.
sssarg said:
What are the benefit(s) of this particular recovery compared to the one(s) in the other thread? From a first glance they look basically the same.
Click to expand...
Click to collapse
Please take a look at the source. Maybe same, my method is different.
SpectraFun said:
We dont need this.
Click to expand...
Click to collapse
Who are you representing? Who is "we". Who put you in that position? If you personally don't need this why are you here?
sssarg said:
What's the benefit of this particular recovery compared to the one(s) in the other thread?
Click to expand...
Click to collapse
@AnoopKumar
This question is precisely why we don't normally have different TWRP threads. TWRP is arguably the MOST important part of helping users easily modify their device once they've unlocked their bootloader. Instead of having two threads with unknown differences, for the sake of the members, it would be better to create a slack or telegram group where all TWRP devs can combine their work into one tree UNTIL we have an officially maintained version. After that you can have all the versions you want because there will be a stable branch to point members to if they have a problem.
I absolutely love development and I am not in any way discouraging you from continuing your work on TWRP. However, I do ask you to consider that there will be extra work on all our parts to help new members because we have to ask what recovery they use and know if there are bugs for two different unofficial versions.
AnoopKumar said:
Please take a look at the source. Maybe same, my method is different.
Click to expand...
Click to collapse
New members aren't going to know how to check the source which is why devs normally put changelogs in the post to prevent this. They are going to see your TWRP picture at the top and think this is basically an official team release of TWRP.
AlkaliV2 said:
@AnoopKumar
This question is precisely why we don't normally have different TWRP threads. TWRP is arguably the MOST important part of helping users easily modify their device once they've unlocked their bootloader. Instead of having two threads with unknown differences, for the sake of the members, it would be better to create a slack or telegram group where all TWRP devs can combine their work into one tree UNTIL we have an officially maintained version. After that you can have all the versions you want because there will be a stable branch to point members to if they have a problem.
I absolutely love development and I am not in any way discouraging you from continuing your work on TWRP. However, I do ask you to consider that there will be extra work on all our parts to help new members because we have to ask what recovery they use and know if there are bugs for two different unofficial versions.
Click to expand...
Click to collapse
I clearly mentioned features and known issues.
This is really disappointing, you guys can't understand what changes i made. You guys thinking i simply cloned the repo and simply compiled. I was trying to improve it. First change i made was hex editing the prebuilt adbd so that i can exclude /system_root/system/bin/crash_dump64 because it is a duplicate file. I changed the default theme, adjusted clock position from another guys commit and some minor changes. I compiled many times for checking each and every changes. It took my time and energy. My apologies.
I hope soon some of recoveries will have OTA support for stock rom. Redwolf or orangefox have this function, but this recoveries are for miui. This is my feature request for future if general functions will be working good. Regards
From: ONEPLUS A6013
Using: Tapatalk 6.3.2 BWS
Daviteusz said:
I hope soon some of recoveries will have OTA support for stock rom. Redwolf or orangefox have this function, but this recoveries are for miui. This is my feature request for future if general functions will be working good. Regards
From: ONEPLUS A6013
Using: Tapatalk 6.3.2 BWS
Click to expand...
Click to collapse
I will look into it.
AnoopKumar said:
This is really disappointing, you guys can't understand what changes i made. You guys thinking i simply cloned the repo and simply compiled. I was trying to improve it. First change i made was hex editing the prebuilt adbd so that i can exclude /system_root/system/bin/crash_dump64 because it is a duplicate file. I changed the default theme, adjusted clock position from another guys commit and some minor changes. I compiled many times for checking each and every changes. It took my time and energy. My apologies.
Click to expand...
Click to collapse
Hold on now EVERYONE... I believe we should not take this to such a personal level. Anoop you KNOW that provide whatever differences you made, improvements and whatnot that people will be interested in what you work on, otherwise you would not necessitate it's publicity. So I'm asking as just a simple Non-dev Android enthusiast, if you will please not stoop to the level of where ignorant retorts are coming from. I know it seems unappreciative, sometimes it is, but mostly I think it comes from lack of understanding of the possible benefits of the work you provided. So being yourself, from a level of a particular skill, I believe you know what to overlook and how to directly cut to the primary topic of people's inquiries to dispel further squabbling. If people still refuse to understand, those are things to overlook and let another XDA member cope with. No reason to exhaust yourself with repetitive pessimism. Just remember most is because people don't genuinely understand what you understand.
Oh Furthermore Thank you Sir
Exactly what Causical just said ^
Thank you for all your work.
AnoopKumar I appreciate all that you are doing
AnoopKumar said:
This is really disappointing, you guys can't understand what changes i made. You guys thinking i simply cloned the repo and simply compiled. I was trying to improve it. First change i made was hex editing the prebuilt adbd so that i can exclude /system_root/system/bin/crash_dump64 because it is a duplicate file. I changed the default theme, adjusted clock position from another guys commit and some minor changes. I compiled many times for checking each and every changes. It took my time and energy. My apologies.
Click to expand...
Click to collapse
Precisely. Which is why I asked my previous question regarding the differences of this recovery compared to the ones we've seen up until now.
Many, or most, of us don't do android development, and deciphering the source code and commits to pick out how a recovery is different from another when they seem to come from the same places (yours is forked from the initial decrypt success, which makes people think it's that one with a few changes) is very difficult.
Out of the changes you mentioned in that quote, I could figure out you had changed the clock position, and had another theme available, because you had stated that already in your OP. The rest? No idea.
As @AlkaliV2 said, in this early stage it's likely going to cause more confusion than not with several unofficial TWRP recoveries with independent development, instead of the devs cooperating to come up with a single and stable unofficial recovery until a time we have a good maintained baseline.
I doubt anyone wants you to stop development, but people are obviously confused with a second thread popping up.
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Who's back? We're back.
CarbonROM is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled roms, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best rom we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
Please feel free to look, build, and use our code at CarbonROM's GitHub... and at CarbonROM Gerrit.
Disclaimer:
While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device, family, pets, or perception of reality. We ask that you do your part to know your device and know how to recover from problems before you flash! If you have questions, ask your fellow users or ask us in #teamcarbon on freenode IRC.
Support:
We spend an astonishing amount of time developing this software. We can't spend much time on XDA as a result, so if you need support, please try the following:
1) Search. Search, search, search. Yes, you. I don't care how unique or important your question is, it's very likely someone has adressed it already. Especially if you're even close to new at this.
2) Read our FAQ, which can be found on our website. Carbon FAQ
3) Ask a question in your device forum. Someone will no doubt try to help you. Warning: this help may come in the form of telling you it's a dumb question that has been asked before. See step 1 - such are the perils of asking questions when you haven't done the research yourself. Android is about helping yourself.
4) Ask a question on our IRC channel. Connect to #teamcarbon on irc.freenode.net or click here. You'll find several other Carbon fans and usually one or more devs as well. Please be polite.
Downloads:
Get CarbonROM
GitHub
Gerrit
Kernel source
Remember, every penny you send to us goes right back into the rom. It's used for hardware, server costs, etc - all the things that help us make Carbon better with every release. Your support means the world to us! If you've enjoyed Carbon, please consider a donation toward this goal. Thank you, and we hope you continue to enjoy Carbon!
XDA:DevDB Information
CarbonROM, ROM for the Google Pixel
Contributors
Myself5, CarbonROM
Source Code: https://github.com/CarbonROM
ROM OS Version: 7.x Nougat
Based On: AOSP
Version Information
Status: Nightly
Created 2017-01-01
Last Updated 2018-03-17
Very nice! Ask and you shall receive, right?
quangtran1 said:
Very nice! Ask and you shall receive, right?
Click to expand...
Click to collapse
Official builds are currently compiling and will be uploaded once done. The unofficial build with Gapps will be linked to in a post when I find some time.
Myself5 said:
Official builds are currently compiling and will be uploaded once done. The unofficial build with Gapps will be linked to in a post when I find some time.
Click to expand...
Click to collapse
Thank you! Happy '17! I've always liked Carbon ROM.
Looks amazing! I was never crazy about the AOSP look but I've gotten more used to it since the pixel is so close to being stock. Time to root and install TWRP finally. Love all the customization options especially the menu bar at the bottom.
Just curious what the Gapps issues are exactly because I've seen some other people mention them but didn't really go into detail.
Thanks!
aholeinthewor1d said:
Looks amazing! I was never crazy about the AOSP look but I've gotten more used to it since the pixel is so close to being stock. Time to root and install TWRP finally. Love all the customization options especially the menu bar at the bottom.
Just curious what the Gapps issues are exactly because I've seen some other people mention them but didn't really go into detail.
Thanks!
Click to expand...
Click to collapse
gApps have always been problematic with every additional security layer added. With different slots, but shared data, I can envision it's getting more complicated.
Downloading.... It's like Christmas all over again. Thanks @Myself5!
quangtran1 said:
Downloading.... It's like Christmas all over again. Thanks @Myself5!
Click to expand...
Click to collapse
What's up with the Gapps thing. Do we flash after or are they built in.
@Myself5, may I have 2 questions:
1) Which gApps should I download for the Pixel sailfish? I tried all combinations of ARM and ARM64, but they all failed to install due to "gApps size too large, try smaller gApps".
2) The ROM seems to get installed to the inactive slot on its own. If I set slot A to be active, Carbon is installed to B. Then I turned around and made B active on a different Pixel, it installed to A, and booted into A.
Thanks!
This is rather nice to see. Thanks for your hard work.
aholeinthewor1d said:
Looks amazing! I was never crazy about the AOSP look but I've gotten more used to it since the pixel is so close to being stock. Time to root and install TWRP finally. Love all the customization options especially the menu bar at the bottom.
Just curious what the Gapps issues are exactly because I've seen some other people mention them but didn't really go into detail.
Thanks!
Click to expand...
Click to collapse
They don't go into detail for a reason. The cause is, as far as I am informed, more or less unknown.
TWRP is suspected to be the cause at the moment, but I don't know much more either ATM. I'd, by guessing assume that it might be a mix of TWRP and the GApps installers that struggle with the AB system, but I don't know for sure.
I do know, that when installing a build with builtin GApps (we can't officially provide builds like this) its working, which is why I'll upload some unofficial builds with builtin Gapps until the issues are solved.
quangtran1 said:
@Myself5, may I have 2 questions:
1) Which gApps should I download for the Pixel sailfish? I tried all combinations of ARM and ARM64, but they all failed to install due to "gApps size too large, try smaller gApps".
2) The ROM seems to get installed to the inactive slot on its own. If I set slot A to be active, Carbon is installed to B. Then I turned around and made B active on a different Pixel, it installed to A, and booted into A.
Thanks!
Click to expand...
Click to collapse
1) None ATM, even when hacking the Installer they seem to dissapear on boot. (See above for more Info).
2) The ROM installs to both slots, and then boots to one that wasnt selected previously, for whatever reason (might be TWRP related or Installer related (the pixel installer zips are really goofy) or even bootloader related, I can't tell for sure).
A Featurelist will be coming soon, please bear with us on that. We hard a very hard time even hitting our release deadline which was supposed to be the 31th of December 2016 but jenkins started to be very picky so all time to prepare threads on XDA and changelogs and stuff went down for jenkins. This thread for example is based on one of my old unofficial Note 10.1 threads, with very small changes. We will rework those later this week too. There was just no time at 4AM this morning to do so
Regards
Myself5 said:
They don't go into detail for a reason. The cause is, as far as I am informed, more or less unknown.
TWRP is suspected to be the cause at the moment, but I don't know much more either ATM. I'd, by guessing assume that it might be a mix of TWRP and the GApps installers that struggle with the AB system, but I don't know for sure.
I do know, that when installing a build with builtin GApps (we can't officially provide builds like this) its working, which is why I'll upload some unofficial builds with builtin Gapps until the issues are solved.
1) None ATM, even when hacking the Installer they seem to dissapear on boot. (See above for more Info).
2) The ROM installs to both slots, and then boots to one that wasnt selected previously, for whatever reason (might be TWRP related or Installer related (the pixel installer zips are really goofy) or even bootloader related, I can't tell for sure).
A Featurelist will be coming soon, please bear with us on that. We hard a very hard time even hitting our release deadline which was supposed to be the 31th of December 2016 but jenkins started to be very picky so all time to prepare threads on XDA and changelogs and stuff went down for jenkins. This thread for example is based on one of my old unofficial Note 10.1 threads, with very small changes. We will rework those later this week too. There was just no time at 4AM this morning to do so
Regards
Click to expand...
Click to collapse
Thank you!
Carbon....No way
So we install it and then it boots the opposite slot? Is that what I'm understanding?
wow I thought carbon was dead. used to be my fav rom, thanks.
instructions on how to install?
Simer03 said:
Carbon....No way
So we install it and then it boots the opposite slot? Is that what I'm understanding?
Click to expand...
Click to collapse
It's installed in both slots. And yes, it boots into the slot that was not previously active. At this time, as the dev responded above, there's no GApps yet.
---------- Post added at 09:44 AM ---------- Previous post was at 09:42 AM ----------
fix-this! said:
wow I thought carbon was dead. used to be my fav rom, thanks.
instructions on how to install?
Click to expand...
Click to collapse
You install it like you'd install any ROM in a recovery such as twrp. Then install gApps. There's no gApps available yet.
So it installs to both slots does that mean it uses double storage space
dantexaiver said:
So it installs to both slots does that mean it uses double storage space
Click to expand...
Click to collapse
It's the same setup you have now being stock. There are 2 of a few different folders including /system which is where the software is stored. No difference
It's good to see Carbon around!!!!
In anticipation of this becoming available for Marlin soon, I have a couple questions.
1) Does this have Slim Recents? I didn't see it listed on the features page.
2) I notice on the features webpage that it has light/dark theme options. Is it the one that can be set to automatically change? If so, does it have auto day/night Substratum support or does it only use the built in theme?
---------- Post added at 04:54 PM ---------- Previous post was at 04:51 PM ----------
Myself5 said:
Pixel related info: Due to yet to be fixed issues, manually flashing GApps on the Pixel builds is not working on all ROMs. The GApps will be gone after booting. I'll might release an unofficial build with GApps included soon.
Click to expand...
Click to collapse
Yep, that's how DU and AOSiP are doing it for the moment.
Built-in. I didn't think it was possible to flash gapps at all, let alone have them install and then go away after reboot.
CZ Eddie said:
It's good to see Carbon around!!!!
In anticipation of this becoming available for Marlin soon, I have a couple questions.
1) Does this have Slim Recents? I didn't see it listed on the features page.
2) I notice on the features webpage that it has light/dark theme options. Is it the one that can be set to automatically change? If so, does it have auto day/night Substratum support or does it only use the built in theme?
---------- Post added at 04:54 PM ---------- Previous post was at 04:51 PM ----------
1) No.
2) The feature page is outdated, but will be updated later this day.
The ROM is having full substratum support, you only need to root and install substratum.
Yep, that's how DU and AOSiP are doing it for the moment.
Built-in. I didn't think it was possible to flash gapps at all, let alone have them install and then go away after reboot.
Click to expand...
Click to collapse
Will provide a build in the next days.
Flashing GApps "worked" after some dirty hacks to the installer Well... "working" as far as "it was there and then dissapeared after the boot" can be defined
Are there "legal" reasons Gapps can't be built in or something? Just curious because I've always wondered how it's OK to release some builds with them built in
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
Do not ask for ETA's.
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 this ROM before flashing it!
YOU are choosing to make these modifications,
and if you point the finger at me for messing up your device, I will laugh at you.
INSTRUCTIONS
- BOOT to twrp and wipe both slots. If you are on A then after wiping it change to B and wipe and vice-versa. Make also a format data, otherwise you will take a bootloop.
- REBOOT TO bootloader and again BOOT TO twrp and then flash this latest rom https://drive.google.com/open?id=1jJ6STCqLjmBhcc7FIksxfnlJRC5guY25
- again reboot to bootloader and boot to twrp and flash magisk and gapps
- Enjoy CypherOS!
What's working :
Boots
RIL (Calls, SMS, Data)
Fingerprint
IR Blaster
Wi-Fi
Camera
Bluetooth (after fixing files)
Video Playback
Audio
Sensors
Flash
LED
GPS
Volte
Known issues:
You tell me
YOU CAN ALWAYS CONTACT ME ON TELEGRAM.. :- @fosseperme
LINK TELEGRAM GROUP: t.me/fossepermeroms
XDA:DevDB Information
[ROM][UNOFFICIAL][8.1.0] CypherOS [2018-04-30], ROM for Xiaomi Mi A1 aka TISSOT
Contributors
fosseperme
Source Code: https://github.com/CypherOS/platform_manifest
Kernel Source: https://github.com/GamingDevilsCC/android_kernel_xiaomi_msm8953
Credits :-
@fosseperme @all aoscp team
Fake rom and fake dev
MrDante95 said:
Fake rom
Click to expand...
Click to collapse
Why you said this ROM is "fake"?
Ayrton990 said:
Why you said this ROM is "fake"?
Click to expand...
Click to collapse
This developer has carved himself a bad renown of brick lord ..
Ayrton990 said:
Why you said this ROM is "fake"?
Click to expand...
Click to collapse
he sells it for his when it is not like that, as with all the other roms made by him (in fact all his posts here on xda have been closed)
MrDante95 said:
Fake rom and fake dev
Click to expand...
Click to collapse
His recent ROMs do not bootloop, therefore the ROM is working and not fake.
laugeek57 said:
This developer has carved himself a bad renown of brick lord ..
Click to expand...
Click to collapse
Are you living few months back. This developer started to make legit ROMs after releasing of xenon hd 8.1.0 . . .
Custom rom 243 said:
Are you living few months back. This developer started to make legit ROMs after releasing of xenon hd 8.1.0 . . .
Click to expand...
Click to collapse
And I still wouldn't use his ROMs.
He is threatining other developers, talking **** and overall acting like a child.
People who use and trust his ROMs must have completly lost their minds and he should just be banned for the greater good.
GamingDevilsCC said:
His recent ROMs do not bootloop, therefore the ROM is working and not fake.
Click to expand...
Click to collapse
You and him last time are same guys I remember someone said that... Just two different ids. No offense but I just remembered
methuselah said:
You and him last time are same guys I remember someone said that... Just two different ids. No offense but I just remembered
Click to expand...
Click to collapse
You may have quoted the wrong guy.
The guy you quoted is the creator of mint kernel
Buckethand said:
You may have quoted the wrong guy.
The guy you quoted is the creator of mint kernel
Click to expand...
Click to collapse
Yeah I am talkikt about that guy only
methuselah said:
You and him last time are same guys I remember someone said that... Just two different ids. No offense but I just remembered
Click to expand...
Click to collapse
I'm just in contact with him and multiple other maintainers for our device. We like to maintain ROMs as a hobby, and I don't like it when users don't like the developer from a few errors and mistake they've done when they're first exposed to a new device, so I stand up for them.
We were all new to something at first and would make mistakes. Putting the developer down from a few mistakes he made at the start will not make him a better dev, and everyone should encourage the dev and/or help them for when they get something fix, instead of discouraging them for that.
GamingDevilsCC said:
I'm just in contact with him and multiple other maintainers for our device. We like to maintain ROMs as a hobby, and I don't like it when users don't like the developer from a few errors and mistake they've done when they're first exposed to a new device, so I stand up for them.
We were all new to something at first and would make mistakes. Putting the developer down from a few mistakes he made at the start will not make him a better dev, and everyone should encourage the dev and/or help them for when they get something fix, instead of discouraging them for that.
Click to expand...
Click to collapse
As of now is not mistakes is kang (I don't really know if it pranav showed evidences) but that up to you devs to resolve those issues.
Us users must use whatever rom/kernel etc we like and if i dont like a certain dev for some reason simple not use it.
If kang is really true mods should take actions
Just my two cents and this will be the first and last time i will ever talk about this "drama" around this user
GamingDevilsCC said:
I'm just in contact with him and multiple other maintainers for our device. We like to maintain ROMs as a hobby, and I don't like it when users don't like the developer from a few errors and mistake they've done when they're first exposed to a new device, so I stand up for them.
We were all new to something at first and would make mistakes. Putting the developer down from a few mistakes he made at the start will not make him a better dev, and everyone should encourage the dev and/or help them for when they get something fix, instead of discouraging them for that.
Click to expand...
Click to collapse
see I tell you something. Those who sync sources are just do nothing for the original are not developers for me. The real developers are those to me who write code. Who fixes those RIL related issues. Those who just synching and just posting random builds are nothing just not doing anything. Its someones else work right. So i have no idea what as per you is developer idk about it. .. And this very user uses to post builds even without asking the original developers and then threaten them lawers. lol, I mean seriously.
GamingDevilsCC said:
I'm just in contact with him and multiple other maintainers for our device. We like to maintain ROMs as a hobby, and I don't like it when users don't like the developer from a few errors and mistake they've done when they're first exposed to a new device, so I stand up for them.
We were all new to something at first and would make mistakes. Putting the developer down from a few mistakes he made at the start will not make him a better dev, and everyone should encourage the dev and/or help them for when they get something fix, instead of discouraging them for that.
Click to expand...
Click to collapse
Bro he don't know how to give proper credits in XDA and just compiling ROMs and create a thread name it as official and first he must learn and then use the XDA share it to others
simply spamming forum will lead to ban only from XDA Hope u understand and I will always help others but at least use Google for some info and get reference if still he doesn't know about it, that's it we can't help
[ROM][10.0][DEVICE] Pixel Experience [AOSP][2020/09/30]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What is this?
Pixel Experience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation)
Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device
Based on Android 10.0
Whats working?
Wifi
RIL
Mobile data
GPS
Camera (non-stock need to be installed)
Flashlight
Camcorder
Bluetooth
FMRadio
Fingerprint reader
NFC
Lights
Sound / vibration
Known issues
Need to install a google camera app
Do NOT FLASH GAPPS, they are already included.
Download from Pixel Experience website
Donate
Liked my work? Give me a beer
Translation
Help with project translation
Stay tuned
Our Telegram channel
Our blog
• Android OS version: 10.0.0_r31
• Security patch level: September 2020
• Build author/Device Maintainer: giminji
• Device Source code: https://github.com/PixelExperience-Devices
• Source code: https://github.com/PixelExperience
• Kernel is from https://github.com/AOSiP-Devices/kernel_oneplus_sdm845
• ROM Developer: jhenrique09
Here is a build I did last week. I am using Pixel Experience I built two weeks ago. Not sure what to put here, but you can try if you like!
September 2020 security patch should be in here. That's the only reason I do ROMs, is for the security updates.
{Mod edit}
Now, let's see what I did wrong on the posting style!
I cannot wait for October security!
I did add in daydream support.
Now, let's see what I did wrong on the posting style!
Onedrive link: https://1drv.ms/u/s!AimL8kQOGqb5hbMjQ8DwozBF61xksA?e=UDBR2l Just until I can get onto android file host.
Install directions: https://wiki.pixelexperience.org/devices/fajita/install/
Summary of install:
1) Install adb and fastboot drivers
a) enable usb debugging
c) adb reboot bootloader
d) fastboot devices
Just to check you can see the fastboot
e) fastboot oem unlock <------ erases all your data! proceed past this point at your own peril!
2) adb reboot bootloader
3) fastboot boot recovery recovery.img (from twrp I use)
4) for me, now it was just install zip from either adb sideload or adb push
5) reboot phone and installed.
The link before all of this has more details.
Giminji said:
Here is a build I did last week. I am using Pixel Experience I build two weeks ago. Not sure what to put here, but you can try if you like!
September 2020 security patch should be in here. That's the only reason I do ROMs, is for the security updates.
{Mod edit}
Now, let's see what I did wrong on the posting style!
Click to expand...
Click to collapse
Aha, taking our first steps into compiling and releasing.. Exciting stuff! And a grand learning experience. Let's start by making the download link... Well, downloadable. You've currently shared a link to an unshared file in your drive. You need to create a share link first. Always test your download links in por.. Eh, incognito mode before releasing. And look into other hosting options that provide more stability such as AFH.
Next on the priority list is adding a link to the kernel source. This is very important for us not to get into any legal trouble as we must comply with GPLv2 in that respect.
Take a look at the other ROM threads to get more familiar with the desired structure. Mostly the bottom parts are important. Like giving credit to those that made your release possible and version information.
Also, you may want to explain what this is (see other PE threads), how people must flash it and notify of any known issues/limitations, if any. Add a disclaimer perhaps, you just never know.
We'll get there together because we're an awesome community like that
Timmmmaaahh said:
Aha, taking our first steps into compiling and releasing.. Exciting stuff! And a grand learning experience. Let's start by making the download link... Well, downloadable. You've currently shared a link to an unshared file in your drive. You need to create a share link first. Always test your download links in por.. Eh, incognito mode before releasing. And look into other hosting options that provide more stability such as AFH.
Next on the priority list is adding a link to the kernel source. This is very important for us not to get into any legal trouble as we must comply with GPLv2 in that respect.
Take a look at the other ROM threads to get more familiar with the desired structure. Mostly the bottom parts are important. Like giving credit to those that made your release possible and version information.
Also, you may want to explain what this is (see other PE threads), how people must flash it and notify of any known issues/limitations, if any. Add a disclaimer perhaps, you just never know.
We'll get there together because we're an awesome community like that
Click to expand...
Click to collapse
Well, that WAS a fail on my part. Try this out please! I usually use onedrive, wanted to use google this time around.
{Mod edit}
Giminji said:
Here is a build I did last week. I am using Pixel Experience I build two weeks ago. Not sure what to put here, but you can try if you like!
September 2020 security patch should be in here. That's the only reason I do ROMs, is for the security updates.
{Mod edit}
Now, let's see what I did wrong on the posting style!
Click to expand...
Click to collapse
You been using this rom? I'm so excited to try this out, I really miss PE on my 6T
Sent from my OnePlus6T using XDA Labs
champagne66601 said:
You been using this rom? I'm so excited to try this out, I really miss PE on my 6T
Sent from my OnePlus6T using XDA Labs
Click to expand...
Click to collapse
Well, I've been using the non-plus. Got my trees swapped, I also added in daydream support. I will be flashing the October security one when I find it's been promulgated.
Giminji said:
Well, I've been using the non-plus. Got my trees swapped, I also added in daydream support. I will be flashing the October security one when I find it's been promulgated.
Click to expand...
Click to collapse
I was using the last official build but I just flashed your build and everything it's working flawlessly, thank you! You did an amazing work
Sent from my OnePlus6T using XDA Labs
Thanks OP for bringing PE to fajita. Keep it up!
I can't seem to download. Appears its been removed from One Drive cloud?
HUGE thanks op for PE for the 6t!! :good
Edit added: Downloading now from the Google Drive link below the op.
Giminji said:
I have build fajita Pixel Experience unofficial, I want to make post, is there a way to do so in the roms section, but have it only for my eyes for right now? So that I can edit, view and then post when ready? I am planning to run the Pixel Experience on my device (with Daydream support) and also make the Pixel Experience ten-plus.
Also, is it okay just to gdrive the downloads?
Thanks!
Click to expand...
Click to collapse
Giminji said:
...
Click to expand...
Click to collapse
@Giminji THREAD CLOSED! Placeholder threads (i.e. those without a workable download link) are not accepted. Your currently linked folder on Onedrive is empty. The link has been removed.
Please advise the moderators team (best via the report function) to re-open your thread when ready to provide a functionable download link.
Why is Pixel Experience always the ROM to cause forum problems? lol
Causical said:
Why is Pixel Experience always the ROM to cause forum problems? lol
Click to expand...
Click to collapse
I've seen PE rom on a few past devices I've owned and it really does seem like something happens. The dev either disappears or something else. lol.
Hoping our Pixel Experience guy will stay around and just keep everything cool with the mod(s). ??
I used this build from the ops second post with the Drive link the other day and it was solid. I always return to Corvus nowadays. PE is a beast though! I've had PE+ on my other device for 6+ months. It always makes me wish I had a Pixel again which will eventually happen once I slowly gather enough funds for one thanks to covid-19. ?
fixed link!
flash713 said:
I've seen PE rom on a few past devices I've owned and it really does seem like something happens. The dev either disappears or something else. lol.
Hoping our Pixel Experience guy will stay around and just keep everything cool with the mod(s).
I used this build from the ops second post with the Drive link the other day and it was solid. I always return to Corvus nowadays. PE is a beast though! I've had PE+ on my other device for 6+ months. It always makes me wish I had a Pixel again which will eventually happen once I slowly gather enough funds for one thanks to covid-19. ?
Click to expand...
Click to collapse
It has been unlocked the thread again, try this link: https://1drv.ms/u/s!AimL8kQOGqb5hbMjQ8DwozBF61xksA?e=UDBR2l
I will post an android file host one once they approve me to do so. Long story short, my gdrive link was giving out too much info. I didn't like that, I shut down and used windows explorer letting it sync files, it did not sync, someone pointed it out to a mod, got put on hold and now thread is back!
Giminji said:
It has been unlocked the thread again, try this link: https://1drv.ms/u/s!AimL8kQOGqb5hbMjQ8DwozBF61xksA?e=UDBR2l
I will post an android file host one once they approve me to do so. Long story short, my gdrive link was giving out too much info. I didn't like that, I shut down and used windows explorer letting it sync files, it did not sync, someone pointed it out to a mod, got put on hold and now thread is back!
Click to expand...
Click to collapse
You were always good in my book bro. Thank you for sharing your work!! :good:
Same reason I don't leave Drive links. You're smart.
Hi? Can you fix SafetyNET? I like this rom, but safetynet...
SevralT said:
Hi? Can you fix SafetyNET? I like this rom, but safetynet...
Click to expand...
Click to collapse
You can fix that with the MagiskHide module
Sent from my OnePlus6T using XDA Labs
Will you become an official developer for 6T ??
Is there any instructions to install this rom?
Does any telegram group?
DimaYarosh1289 said:
Is there any instructions to install this rom?
Click to expand...
Click to collapse
Sadly, I am not very well versed yet. Best I can do.
1) Unlock bootloader
2) boot into fastboot
3) do the "fastboot boot RECOVERIMAGENAME.img
-- I usually do twrp
4) install it.
Maybe someone can help me flesh that out some, this is my first rom I made.
SevralT said:
Will you become an official developer for 6T ??
Click to expand...
Click to collapse
I am trying, but the rules to become developer for 6t on the PE website is confusing. In a few weeks when I make October 2020 with security up to date, I may look again and see if I can fulfull requirements.
Nothing to see here
ROM source here: https://github.com/Bootleggers-BrokenLab
And chat here: https://t.me/keepthebootleg
Remember this is not an official build so builds won't be here ^ and unofficial support, chatting, etc, are not allowed here so please respect the rules.
*Bootleg 8t Chat coming soon..
This one too
Current Build: v14
v14.zip
drive.google.com
Previous build here: https://drive.google.com/file/d/1-I3z_pLzLEZPhBmJb_FZesLUcycY_5Ud/view?usp=drivesdk
Tnx for your amazing work bro
damn! bootleggers is a coming!
and comes with neutrino power!
thankssss
What about MTP not working ??
Some people saying that in some chats do you know anything about that??
This is the best news ever.
dpryor88 said:
This is the best news ever.
Click to expand...
Click to collapse
MTP working for you?? Thanks in advance
alex moymoy said:
What about MTP not working ??
Some people saying that in some chats do you know anything about that??
Click to expand...
Click to collapse
Enable in development options if you have issues, Works fine for me. I have no issues. But I always enable via development options
alex moymoy said:
MTP working for you?? Thanks in advance
Click to expand...
Click to collapse
Well I certainly don't work for IT. It works for me on the weekends, part time. I don't pay it well, but it doesn't know any better.
FullOfHell said:
Spoiler
Hello, you all may remember me from my ROMs for pixel 5, pixel 4, 8t, 7t, 6t, Shamu, and J7..
I left 8t development a few months ago to have some fun with a pixel 5, and a month ago, dusted the ol' kebab off and jumped back in. I keep most of my ROMs on the silent side of things and don't use xda but for official releases. Hopefully, This unofficial build will become official. I think you all will love it as much as I do. It comes with my own branch of neutrino kernel, as does all my ROMs, it's entirely based on neutrino, but I add klapse, hbm, vibration tuning, etc, and some other kernel options that I don't care to add device tree side. This is a beta build so it has a couple weird small bugs, and no they do not affect anything.
Bugs-
1. At first boot, soon as you see the setup wizard, it will show you a toast, phone is rebooting, it reboots then setup continues not to happen again. This affects nothing. Not sure why, but don't really care either, as it all works ferociously fine after.
2. Occasionally, up at the left most corner, where the status bar clock is, a slice of the hour part of the clock is sliced off, it doesn't exist all the time, just sometimes. It is perfect in quick settings view and typically corrects itself only to randomly get sliced. I probably have a duplicate overlay for the dimensions related to that spacing. Will fix next chance I get.
That's it for any issues.
Features-
All the current bootleggers features for "Rimbon". Perfect fingerprint, face unlock, endless theming options, larger quick setting icons for easier tapping, proton aosp blur, proton aosp optimizations, Verizon support, dual sim support, enable/disable fingerprint vibration, Dolby, raise to wake, app lock, the list goes on. More features will be coming once I add them, prob fod animations and edge notification pulse.
Things I don't care to add-
fod screen off, safety net spoofing, sm8250-DeviceSettings(we really don't need them at all)I added and they're redundant, and call recording, oh yeah gaming is for PCs and consoles I don't add it to phones. If you want these things. Bootleggers is not for you.
All my builds are fastboot update zips and include gapps. I'm a Google guy and need all their stuff and yes I don't care they can have mine too. Haha.
Flashing- no matter what you are on currently, for best performance flash oos stable first, then format data via recovery, reboot bootloader and the command is fastboot update bootleg_kebab_v7.zip *note, you must open terminal in the folder where the zip is to give this command, other wise fastboot update HereIsLocationToTheZip.zip. after it does it's thing and flashes it boots and then at first boot shows the setup wiz and reboots as declared in "bugs" section.. Root if you would like to use kernel features, this requires the same old process we have used for 3 android versions, I hope you know how, lol. If you have troubles, re read this entire post.
Thanks- to my testers, my friends, the entire kangarooster squad, and the couple android geniuses who shared their wisdom teaching me the ropes the last 4 years of source building.
@xstefen @dpryor88 @omariscal1019 @Neo @wrongway213 @semdoc @hondajohn88 @varund7726 @abalam @ZVNexus @return.of.octobot @aer0zer0 and countless others who I will add once I figure out their xda name.
Trees:
jacks84 - Overview
jacks84 has 98 repositories available. Follow their code on GitHub.
github.com
Click to expand...
Click to collapse
alex moymoy said:
MTP working for you?? Thanks in advance
Click to expand...
Click to collapse
Just connect your phone with pc, go to dev menu and hit this. Choose what you want
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hey, I tried to flash your ROM using the method you recommended, But it only spat out,
error: failed to load 'bootleg_kebab_v7.zip': Not enough space
Click to expand...
Click to collapse
Is there something I am doing wrong? Many apologies, I haven't flashed a ROM like this, This will be my first time.
Huskied said:
Hey, I tried to flash your ROM using the method you recommended, But it only spat out,
Is there something I am doing wrong? Many apologies, I haven't flashed a ROM like this, This will be my first time.
Click to expand...
Click to collapse
have you adb sideloading a rom before?
Huskied said:
Hey, I tried to flash your ROM using the method you recommended, But it only spat out,
Is there something I am doing wrong? Many apologies, I haven't flashed a ROM like this, This will be my first time.
Click to expand...
Click to collapse
Update sdk
Huskied said:
Hey, I tried to flash your ROM using the method you recommended, But it only spat out,
Is there something I am doing wrong? Many apologies, I haven't flashed a ROM like this, This will be my first time.
Click to expand...
Click to collapse
Prob need to msm first, sounds like your partitions are funky, or as abalam said, update platform tools
Just kidding
bootleg_kebab_v7.zip
drive.google.com
Huskied said:
Hey, I tried to flash your ROM using the method you recommended, But it only spat out,
Is there something I am doing wrong? Many apologies, I haven't flashed a ROM like this, This will be my first time.
Click to expand...
Click to collapse
You need a platform tools update
best rom i ever used on my 8t
smooth af, snappy af, fod fast af
thanks dev
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Team Win Recovery Project Official
For SM-T210(R)/SM-T211 (lt02)
USE AT YOUR OWN RISK!
Please make sure to this thread if you like the port!
ISSUES
Temperature is not available because the kernel does not support it.
Google apps install does not work (Fixed in latest nightly release!)
DOWNLOADS
All nightly releases are on our build repository. DOWNLOAD
All standard releases are on the TWRP website. DOWNLOAD
LINKS
Source Code
Discord Server
CREDITS
@Jespert
@TriDiscord
@gr8nole
@ketut.kumajaya
@paziusss
@ruben15prd
Reserved -
Thanks for maintaining TWRP for this almost 9 year old tablet! It's about time it gets official support. Works perfectly on my SM-T2105.
Just as a heads up, any installers that check for the correct device before installing using the "assert(getprop("ro.product.device")" line in the install script may give an error since you have the product showing as "lt02" (as opposed to lt02wifi, lt023g, etc.) for this recovery. Won't likely be an issue unless someone gets a device-specific version of a source built rom working (Lineage, Omni, etc.). Most customized versions of stock-based roms won't have that line in the install script.
gr8nole said:
Just as a heads up, any installers that check for the correct device before installing using the "assert(getprop("ro.product.device")" line in the install script may give an error since you have the product showing as "lt02" (as opposed to lt02wifi, lt023g, etc.) for this recovery. Won't likely be an issue unless someone gets a device-specific version of a source built rom working (Lineage, Omni, etc.). Most customized versions of stock-based roms won't have that line in the install script.
Click to expand...
Click to collapse
We'll probably never get a custom ROM except for modified stock ones anyways lol.
throwaway019299292 said:
We'll probably never get a custom ROM except for modified stock ones anyways lol.
Click to expand...
Click to collapse
CM11 exist, there are plans to fix bugs.
throwaway019299292 said:
We'll probably never get a custom ROM except for modified stock ones anyways lol.
Click to expand...
Click to collapse
uhh, cyanogenmod 11 recieved its last update for this tablet 7 years ago, so it's been around for a damn long time
gr8nole said:
Just as a heads up, any installers that check for the correct device before installing using the "assert(getprop("ro.product.device")" line in the install script may give an error since you have the product showing as "lt02" (as opposed to lt02wifi, lt023g, etc.) for this recovery. Won't likely be an issue unless someone gets a device-specific version of a source built rom working (Lineage, Omni, etc.). Most customized versions of stock-based roms won't have that line in the install script.
Click to expand...
Click to collapse
ROMs should support the `TARGET_OTA_ASSERT_DEVICE` flag if they're building for multiple devices. Will remove the `lt02` from that, though. Let me know if you have any other codenames for the Tab 3 7.0
TriDiscord said:
ROMs should support the `TARGET_OTA_ASSERT_DEVICE` flag if they're building for multiple devices. Will remove the `lt02` from that, though. Let me know if you have any other codenames for the Tab 3 7.0
Click to expand...
Click to collapse
SM-T2105 shows up as lt02kidswifi in the device field and lt02kidswifiue in the product field on the Device Info HW app.
throwaway019299292 said:
SM-T2105 shows up as lt02kidswifi in the device field and lt02kidswifiue in the product field on the Device Info HW app.
Click to expand...
Click to collapse
This is the line as the final result:
TARGET_OTA_ASSERT_DEVICE := lt02wifi,lt02wifijpn,lt02wifizc,lt02wifizs,lt02wifiue,lt02kidswifi,lt02kidswifiub,lt02kidswifiue,lt02kidswifiww,lt02kidswifixw,lt02kidswifizc,lt02kidswifizh
Will merge when other changes are completed. Thanks!
This has inspired me to TRY to create a custom rom for the T210R.
I'm trying diligently to make one based on CM 14.1.
Anyone have any ideas, I'm more than happy to collaborate.
Thanks for the recovery!
CaptainBenSisko said:
This has inspired me to TRY to create a custom rom for the T210R.
I'm trying diligently to make one based on CM 14.1.
Anyone have any ideas, I'm more than happy to collaborate.
Thanks for the recovery!
Click to expand...
Click to collapse
After a month... I don't know what I've gotten myself into. This is a royal pain to try to build a rom for.
CaptainBenSisko said:
After a month... I don't know what I've gotten myself into. This is a royal pain to try to build a rom for.
Click to expand...
Click to collapse
Hehe, I understand. It takes so much time.
CaptainBenSisko said:
After a month... I don't know what I've gotten myself into. This is a royal pain to try to build a rom for.
Click to expand...
Click to collapse
Any GitHub sources? We can maybe try to help?
TriDiscord said:
Any GitHub sources? We can maybe try to help?
Click to expand...
Click to collapse
These are what I was working with, all credit to the OP's. (Especially gr8nole, he seems to have his hand in all things T210R)
GitHub - lt02-dev/android_device_samsung_lt02wifi: Device Tree for Galaxy Tab 3 7.0 Wifi (lt02wifi)
Device Tree for Galaxy Tab 3 7.0 Wifi (lt02wifi). Contribute to lt02-dev/android_device_samsung_lt02wifi development by creating an account on GitHub.
github.com
GitHub - gr8nole/android_vendor_samsung_lt02wifi: Proprietary files for lt02wifi
Proprietary files for lt02wifi. Contribute to gr8nole/android_vendor_samsung_lt02wifi development by creating an account on GitHub.
github.com
sm-t210r / android_kernel_samsung_lt02 · GitLab
GitLab.com
gitlab.com
Don't fall down the rabbit hole, but if you wanna give it a go, I'm more than happy to collab.
CaptainBenSisko said:
These are what I was working with, all credit to the OP's. (Especially gr8nole, he seems to have his hand in all things T210R)
GitHub - lt02-dev/android_device_samsung_lt02wifi: Device Tree for Galaxy Tab 3 7.0 Wifi (lt02wifi)
Device Tree for Galaxy Tab 3 7.0 Wifi (lt02wifi). Contribute to lt02-dev/android_device_samsung_lt02wifi development by creating an account on GitHub.
github.com
GitHub - gr8nole/android_vendor_samsung_lt02wifi: Proprietary files for lt02wifi
Proprietary files for lt02wifi. Contribute to gr8nole/android_vendor_samsung_lt02wifi development by creating an account on GitHub.
github.com
sm-t210r / android_kernel_samsung_lt02 · GitLab
GitLab.com
gitlab.com
Don't fall down the rabbit hole, but if you wanna give it a go, I'm more than happy to collab.
Click to expand...
Click to collapse
Those are very buggy sources for CyanogenMod 11. I doubt that 14.1 will work on this.
@CaptainBenSisko, @TriDiscord, I tried building 14.1 for T210R this month using
https://github.com/SamsungGalaxyTab3
but ran into the exact same problem and error messages that the previous person @sscsps was getting in this thread
https://forum.xda-developers.com/t/abandoned-not-working-lineageos-14-1-for-t211.3621818/
There's no boot animation and my last_kmsg shows the same problem.
retiredtab said:
@CaptainBenSisko, @TriDiscord, I tried building 14.1 for T210R this month using
https://github.com/SamsungGalaxyTab3
but ran into the exact same problem and error messages that the previous person @sscsps was getting in this thread
https://forum.xda-developers.com/t/abandoned-not-working-lineageos-14-1-for-t211.3621818/
There's no boot animation and my last_kmsg shows the same problem.
Click to expand...
Click to collapse
I'm just curious, has anyone tried MM yet?
I think I found a guy who got lollipop to work on the t210r but it was canceled
HackerMan195 said:
I think I found a guy who got lollipop to work on the t210r but it was canceled
Click to expand...
Click to collapse
Ooh! Could you share a link?