Related
Presently: T-Mobile-Polska ROM (4.4.2 KitKat, Build ID: KOT49H) flashed 24-03-2015y.
Well customized, rooted, well tuned up with Xpose instaler modules etc., frozen bloatware
For several months it is proposed to update for a reason: Security Fix!
Is it worth updating at all? As such a "security fixes" used to mean user couldn't customize or tune OS, you could hardly detect any other difference!
However, what is the latest or simply the best ROM for the 64bit device?
(And where to download from?)
No matter stock or custom, just it needs fully work and has some nice "state of the art" builtin functionality
The other facilities will be acquired through the means above mentioned: root, Xpose, 3Ctools and some neat tools available on the market.
Possibly half of the stock system apps are just bloatware, so 3Ctools will help to cleanup them
You might try to ask the tech support what is in this update for example the MMS fix surely feels like must have (well known by now mms bug allowing to execute a code send by mms) but if that something you could manage to dodge on your own then just ignore it.
About the ROM with some nice looks n feels well we don't have any TBH we don't have any so called "daily driver" at all but I can suggest installing a custom launcher some of the more liked ones were on sale not so long ago you just have to track the app sales
I don't suggest any cause I don't know the forum rules regard the advertising.
Edit: There's Cyanogenmod 12 but it's bugged, not something u want to use daily.
ioy said:
Presently: T-Mobile-Polska ROM (4.4.2 KitKat, Build ID: KOT49H) flashed 24-03-2015y.
Well customized, rooted, well tuned up with Xpose instaler modules etc., frozen bloatware
For several months it is proposed to update for a reason: Security Fix!
Is it worth updating at all? As such a "security fixes" used to mean user couldn't customize or tune OS, you could hardly detect any other difference!
However, what is the latest or simply the best ROM for the 64bit device?
(And where to download from?)
No matter stock or custom, just it needs fully work and has some nice "state of the art" builtin functionality
The other facilities will be acquired through the means above mentioned: root, Xpose, 3Ctools and some neat tools available on the market.
Possibly half of the stock system apps are just bloatware, so 3Ctools will help to cleanup them
Click to expand...
Click to collapse
There's only 1 rom available for the 64 bit and that's the one patrik made the cm12 and it has a good amount of bugs so it's not suggested as a daily driver yet. Nothing else but that and stock.
Hello everyone. Those days I feel some to root my phone (ALE-L21 6.0 Dual SIM) to install custom ROMs like LineageOS with Android Nougat and use apps like WPS WPA Tester but other some I feel not because I'm still in warranty time (it ends after 1 year + the warranty isn't in my country) and I never rooted any device or even used Android (my lase phone was Nokia 110) so today I wanna to know why root is useful and why not and what can I use it for and what's the root dangerous? I need all informations about root. :laugh:
Edit: Is all custom ROMs has bugs? Like Radio FM doesn't work, screen recorder doesn't work or even has a bug?
AmirGTX said:
I need all informations about root. :laugh:
Edit: Is all custom ROMs has bugs?
Click to expand...
Click to collapse
Root was a good thing on earlier versions of Android. Now I don't think it's a necessity.
Custom ROM's seems a good idea, but if you don't have official version from the developers I myself don't recommend it.
You can try deoxed, modified or trimmed versions of stock ROM, to get more features.
If you have a branded phone I recommend to unbrand it to obtain ROM updates easily.
I recommend to keep stock for now because we get security patches from time to time.
I think main reasons for rooting and unlocking bootloader.
1. Devices with small memory you can install apps in to SD-card.
2. If you realy hate ads you can use Adblocking.
3. Install custom ROM or kernel to get better battery life/performance (with some devices these are only stuff that isn't perfectly stable but sill stable enoughfor daily use).
4. Uninstall unessesary system apps.
5. More customizing possibilities like change screen dpi(dots per inch --> smaller value gives smaller icons and text so you can fit more stuff in screen at the same time).
6. There is more things to do but this was of the top of my head.
IMO root yes, of course, many reasons pick the ones you like most: uninstall bloatware, tweak kernel parameters, activate hidden options, xposed, greenify...
keikari said:
I think main reasons for rooting and unlocking bootloader.
1. Devices with small memory you can install apps in to SD-card.
2. If you realy hate ads you can use Adblocking.
3. Install custom ROM or kernel to get better battery life/performance (with some devices these are only stuff that isn't perfectly stable but sill stable enoughfor daily use).
4. Uninstall unessesary system apps.
5. More customizing possibilities like change screen dpi(dots per inch --> smaller value gives smaller icons and text so you can fit more stuff in screen at the same time).
6. There is more things to do but this was of the top of my head.
Click to expand...
Click to collapse
1. I use my device currently and needn't more space.
2. I already have Adguard, it's enough for me.
3. Yes, I've bored from the stock Android theme and want to change it.
4. I needn't to remove system apps because I don't even use them.
5. IDK what's this obviously. :laugh:
6. What else?
fosco_ said:
IMO root yes, of course, many reasons pick the ones you like most: uninstall bloatware, tweak kernel parameters, activate hidden options, xposed, greenify...
Click to expand...
Click to collapse
What's IMO? What's bloatware? What's tweak kernel? What's all this? :silly:
AmirGTX said:
1. I use my device currently and needn't more space.
2. I already have Adguard, it's enough for me.
3. Yes, I've bored from the stock Android theme and want to change it.
4. I needn't to remove system apps because I don't even use them.
5. IDK what's this obviously. :laugh:
6. What else?
Click to expand...
Click to collapse
Well I forgot to tell most important reason, because you can : D
Nowdays that's prety much all the stuf that matters for regular user.
Maybe bagroundplayback for youtube if it isn't already possible with regular app.
And it's kind of a plus that you can back backup your full system in TWRP, thought main reson for backups is that you are testing something unstable or new stuff which you can only do with unlocked bootloader.
PS. Your logic in 4 is kind of weird XDD
And dpi is kind of like resolution of screen but still very different but you can think of it as a weird resolution setting
Azzureux said:
Root was a good thing on earlier versions of Android. Now I don't think it's a necessity.
Custom ROM's seems a good idea, but if you don't have official version from the developers I myself don't recommend it.
You can try deoxed, modified or trimmed versions of stock ROM, to get more features.
If you have a branded phone I recommend to unbrand it to obtain ROM updates easily.
I recommend to keep stock for now because we get security patches from time to time.
Click to expand...
Click to collapse
Can you explain more? I didn't got it :cyclops:
AmirGTX said:
What's IMO? What's bloatware? What's tweak kernel? What's all this? :silly:
Click to expand...
Click to collapse
Are you kidding?
IMO = In My Opinion
bloatware = preinstalled apps you don't want but can't remove
tweak kernel = change kernel parameters such as min/max speed, governor, i/o scheduler, gpu speed and so
AmirGTX said:
Can you explain more? I didn't got it :cyclops:
Click to expand...
Click to collapse
I'll try to be brief.
First I rooted my Samsung Galaxy S plus, android version was 2.3.6. Was a good thing? Yes, I had good devs who not only made Rom's up to Lollipop (I use now KitKat on it) but also repartitioned the space available through Twrp giving me more space for apps.
My next one was Galaxy S3 mini, android version was 4.1. I rooted it. Was a good thing? Yes and No.
Yes was good because I could use apps for backup, to remove bloatware, and posible to try custom ROMs.
No... Because I didn't had good developers, every custom ROMs had issues. That made me feel cautious and only installed stock ROM's that gave me more personalization and stable use of the phone (that doesn't mean I don't have problems with it, but it's mostly caused by apps who are not 100% compatible with KK ROM's).
Now let's talk about P8 Lite.
1. Can I squeeze more time of use from battery? Yes, we got the option <Ultra battery>.
2. Can I disable bloatware? I can't remove apps but I can disable them (MM has an option for it).
3. Can I backup apps and data? Yes. We got an option for it.
4. Can I get security updates for my ROM? Yes, for now we get security updates from Huawei.
5. Can I customize my ROM? To a point... Yes, you can customize the interface through themes, and the theme itself using other apps.
6. Can I get Nougat (version 7 of Android).
No, and you can start blaming Google for the requirements asked for it.
Yes, if you buy the 2017 version of the phone.
Sorry I was not brief. :good:
fosco_ said:
Are you kidding?
IMO = In My Opinion
bloatware = preinstalled apps you don't want but can't remove
tweak kernel = change kernel parameters such as min/max speed, governor, i/o scheduler, gpu speed and so
Click to expand...
Click to collapse
Oh alright +1, why I need root else? (I'm just collecting info b4 rooting my device)
Azzureux said:
I'll try to be brief.
First I rooted my Samsung Galaxy S plus, android version was 2.3.6. Was a good thing? Yes, I had good devs who not only made Rom's up to Lollipop (I use now KitKat on it) but also repartitioned the space available through Twrp giving me more space for apps.
My next one was Galaxy S3 mini, android version was 4.1. I rooted it. Was a good thing? Yes and No.
Yes was good because I could use apps for backup, to remove bloatware, and posible to try custom ROMs.
No... Because I didn't had good developers, every custom ROMs had issues. That made me feel cautious and only installed stock ROM's that gave me more personalization and stable use of the phone (that doesn't mean I don't have problems with it, but it's mostly caused by apps who are not 100% compatible with KK ROM's).
Now let's talk about P8 Lite.
1. Can I squeeze more time of use from battery? Yes, we got the option <Ultra battery>.
2. Can I disable bloatware? I can't remove apps but I can disable them (MM has an option for it).
3. Can I backup apps and data? Yes. We got an option for it.
4. Can I get security updates for my ROM? Yes, for now we get security updates from Huawei.
5. Can I customize my ROM? To a point... Yes, you can customize the interface through themes, and the theme itself using other apps.
6. Can I get Nougat (version 7 of Android).
No, and you can start blaming Google for the requirements asked for it.
Yes, if you buy the 2017 version of the phone.
Sorry I was not brief. :good:
Click to expand...
Click to collapse
Awesome, that's why I want to root it but I'm still waiting until LineageOS be available and stable without bugs for me. I bought my phone last year and updated it to MM 6.0 at 7 month of last year, now I have UPDATE.APP (got it from here) it has no bugs and too stable for me. So I saw tutorials here for rooting my device but it were too much big and I need to use my computer. NP if I used my computer but can't I root it using apps suck as KingRoot and then install the ROM? Also I want to know all thing about bootloader and unlocking it and all thing in this operation. I want to know to be deep for such as problems. Thanks for info
AmirGTX said:
Also I want to know all thing about bootloader and unlocking it and all thing in this operation.
Click to expand...
Click to collapse
Few years ago, when we could not imagine that phones can get ROM updates, no one bothered about bootloaders. But after few years they were shocked to see old clients use same depleted phones with new ROM's.
If you look back, when Google started to release Android 3 and up, we can see that the manufactures didn't try to much to improve "the smartphones", the selling ideology was the same as before, manufactures imagined just few improvements for the new models.
But then iPhone appeared, Samsung Galaxy smartphone line appeared and rules changed. Everyone tried to sell smarter phones on the market, Apple had a closed system so everyone looked at Google and android delivered.
So after the "Wild West" period, manufactures wanted more control over their devices, don't forget that devices had hardware in many configurations, so to prevent bricked phones, to try to stop clients from destroying their devices and after ask for guaranty, bootloaders were invented. It's a compromising way for users to obtain root access and avoid warranty claims.
Now, we see that Google stepped a bit, with Android 7, by limiting the compatibility asking for minimum hardware from manufactures. It's a way to make clients buy new devices. Same thing we saw at Microsoft when it released Vista and up. It's a good way for manufactures to stop companies like CM to make unwanted ROM's updates. At the beggining CM ROM's where 100% bug free, but now we can't say the same. Manufactures don't release drivers for hardware so developers to implement new versions of Android on old devices.
For me the only viable option for ROM updates is stock modifications that try to remove restrictions in the software available thru all the world.
But why is Huawei giving a legal way to unlock the bootloader? It's a very easy way to see who still got guaranty and who is out of guaranty. And also it's a way to keep clients close by getting ROM updates faster, it's basically a removal of the middle man (manufactures can't live without firms that do installment sales) a way to increase the overall sales.
Imagine a person who needs a smartphone but can't afford it. Carriers can give devices for less, manufactures get the full price, and carriers get the whole price with interest over a limited period. And now manufactures have a problem, they need to keep clients of carriers happy, and need to push updates on the devices. Carriers see this as a loss of control, but can't make the manufacturer to keep the system closed. So for legal requirements bootloaders were invented.
You can ask for root, but manufactures and Google is giving secure control over the devices, that basically do same thing as apps that required root.
My final advice: if you don't plan to learn about android ROM development, if you don't plan to be a developer, then don't root. Wait until you get a new device, maybe with the new iteration of ROM. If you see something you like, then you can start learning and start developing.
:silly: can't believe i wrote so much. Happy reading and good luck.
Azzureux said:
Few years ago, when we could not imagine that phones can get ROM updates, no one bothered about bootloaders. But after few years they were shocked to see old clients use same depleted phones with new ROM's.
If you look back, when Google started to release Android 3 and up, we can see that the manufactures didn't try to much to improve "the smartphones", the selling ideology was the same as before, manufactures imagined just few improvements for the new models.
But then iPhone appeared, Samsung Galaxy smartphone line appeared and rules changed. Everyone tried to sell smarter phones on the market, Apple had a closed system so everyone looked at Google and android delivered.
So after the "Wild West" period, manufactures wanted more control over their devices, don't forget that devices had hardware in many configurations, so to prevent bricked phones, to try to stop clients from destroying their devices and after ask for guaranty, bootloaders were invented. It's a compromising way for users to obtain root access and avoid warranty claims.
Now, we see that Google stepped a bit, with Android 7, by limiting the compatibility asking for minimum hardware from manufactures. It's a way to make clients buy new devices. Same thing we saw at Microsoft when it released Vista and up. It's a good way for manufactures to stop companies like CM to make unwanted ROM's updates. At the beggining CM ROM's where 100% bug free, but now we can't say the same. Manufactures don't release drivers for hardware so developers to implement new versions of Android on old devices.
For me the only viable option for ROM updates is stock modifications that try to remove restrictions in the software available thru all the world.
But why is Huawei giving a legal way to unlock the bootloader? It's a very easy way to see who still got guaranty and who is out of guaranty. And also it's a way to keep clients close by getting ROM updates faster, it's basically a removal of the middle man (manufactures can't live without firms that do installment sales) a way to increase the overall sales.
Imagine a person who needs a smartphone but can't afford it. Carriers can give devices for less, manufactures get the full price, and carriers get the whole price with interest over a limited period. And now manufactures have a problem, they need to keep clients of carriers happy, and need to push updates on the devices. Carriers see this as a loss of control, but can't make the manufacturer to keep the system closed. So for legal requirements bootloaders were invented.
You can ask for root, but manufactures and Google is giving secure control over the devices, that basically do same thing as apps that required root.
My final advice: if you don't plan to learn about android ROM development, if you don't plan to be a developer, then don't root. Wait until you get a new device, maybe with the new iteration of ROM. If you see something you like, then you can start learning and start developing.
:silly: can't believe i wrote so much. Happy reading and good luck.
Click to expand...
Click to collapse
Extremely awesome and thanks a lot. I want to start to learn about root but IDK from where can I start! There are no way to root any Android emulator and learn from it or executing on main device would be more stable?
IMO, root device it's a personal choice, the important question is:
There's something that you want to do and you can't because you need root?
To install custom rom you don't need root, you have to unlock bootloader, install a custom recovery (TWRP) and finally you can flash you custom rom (generally already rooted!)
ItalianWolf said:
IMO, root device it's a personal choice, the important question is:
There's something that you want to do and you can't because you need root?
To install custom rom you don't need root, you have to unlock bootloader, install a custom recovery (TWRP) and finally you can flash you custom rom (generally already rooted!)
Click to expand...
Click to collapse
Ciao amico mio ? (some Italian from school ?) can you give me a tutorial for this? I need to try. Also why there are a lot of stuffs to root ALE-L21? What if I used apps such as KingRoot?
Ciao!
Kingroot, if it's working again, isn't a good root solution; i've tried (we were with lollipop) but messed up a lot of things so i had to re-flash stock firmware.
https://forum.xda-developers.com/p8lite/general/mega-thread-root-unbricking-updating-t3400994
Yes for :
Tweak kernel, install AdAway and remove preinstalled apps.
personally for me is a must, i just do much things with root, anyways you could say i'm an advanced user of android so i need root, if you are good with your phone as it is, or a newer user of android, you don't need to root
panchovix said:
personally for me is a must, i just do much things with root, anyways you could say i'm an advanced user of android so i need root, if you are good with your phone as it is, or a newer user of android, you don't need to root
Click to expand...
Click to collapse
I don't like normal things, I need to be special that's why I think to root my device. I'm neither pro nor newer. So I need to know if I rooted my device what will I do else custom ROMs and block ads and remove system apps?
Ok, so I have been working on this for a couple of days and I wanted to update everyone on my progress. Since rooting my SM-P205, I have been working on porting TWRP to this device. I have hit a couple of roadblocks, so I am making my way through them as I encounter them. This thread will be used to update on progress as it occurs.
UNLESS YOU ARE BEING CONSTRUCTIVE AND TRYING TO ASSIST IN DEVELOPMENT, DON'T SPAM THIS THREAD. As I make developments, I will post them. No, I don't need testers, I have my own device.
Current Status: Everything builds, and it boots, but the screen just flashes repeatedly. Doing some digging to see if I can find the issue.
What have I done?
Well, I have made a device tree and posted kernel sources. The kernel sources are not 100% current, but I doubt Samsung has changed much in the kernel in a single release. Anywho, I have also tried to install the TWRP for the SM-T515, since they are literally the same device, except this one has an 8" screen and an S-Pen, but no dice; Odin just gets stuck on the file analysis. So, in the meantime, I have posted links to the repositories for what work I have done up to this point, but I am far from finished. If building from the full Omni sources fails, I guess I'll have to try Lineage (much to my dismay).
Side note, if you look at my repository and think to yourself, "gee this looks awfully similar to the repo for the SM-T515", well that's not a coincidence. As I stated earlier, they're basically the same device: same chipset, same RAM, heck even the same resolution.
Device Repository: https://github.com/eagerestwolf/android_device_samsung_wisdom/
Kernel Repository: https://github.com/eagerestwolf/andtoid_kernel_samsung_wisdom/
Status update (12/26/2019 0034 EST)
The recovery image has built successfully using the full OmniROM source. I am currently building the boot image and testing will begin shortly...maybe.
Status update (12/26/2019 0041 EST)
The boot image has built successfully, going to make the ODIN package and flash it now.
Status update (12/26/2019 0046 EST)
Does not boot...error validating footer...I think I know why, I'm pretty sure the board id is wrong in the config...gotta fix that...somehow.
Developer Information for the futurez
This device...like so many others these days is using Android Verified Boot. More importantly, it uses the Treble configuration with A/B verity under the guise of "data integrity" (we all know that Google and Samsung would love for everyone to stop rooting and installing custom ROMs).
So how does that affect me?
Well, first off. You CANNOT touch the boot partition...at all. If you do...boom Download Mode for you. Secondly, when rooting (even with TWRP) NOTHING can be installed to /system. If you do...boom Download Mode for you too. Currently, I am working to create a TWRP package with dm-verity disabled, BUT that will only allow flashing unverified images...it does NOT bypass the restrictions of Android Verified Boot...sadly. Also, the flashing process is VERY different. You have to flash two system images, so ROM installs will take twice as long...be aware.
To build TWRP for this device, you cannot use the minimal manifest. Not sure why, but it will fail on the Toybox compilation (Toybox is Google's codename for Android's implementation of SELinux). So what you need to do is sync the FULL omnirom sources (could probably also use AOSP or Lineage, I just used Omni):
Code:
repo init -u git://github.com/omnirom/android.git -b android-9.0
DON'T SYNC YET!. You need to modify some manifests first. In .repo/local_manifests/twrp.xml, add the following:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="TeamWin"
fetch="https://github.com/TeamWin"
review="https://gerrit.twrp.me" />
<!-- TWRP lives in TeamWin android-9.0 (not AOSP!) -->
<remove-project name="platform/bootable/recovery"/>
<project path="bootable/recovery" name="android_bootable_recovery" remote="TeamWin" revision="android-9.0"/>
<!-- Include external Magisk repo for repack binaries -->
<project path="external/magisk-prebuilt" name="external_magisk-prebuilt" remote="TeamWin" revision="master" />
<!-- Include TeamWin android_system_update_engine to build a good update_engine_sideload -->
<remove-project name="android_system_update_engine" />
<project path="system/update_engine" name="android_system_update_engine" remote="TeamWin" revision="android-9.0" />
</manifest>
You might as well add your device sources at this point as well. Then sync and build.
Good info, thanks. I know on the pixel 3 any system mod has to be done through magisk. No twrp available at all.
Sent from my Pixel 3 XL using Tapatalk
lafester said:
Good info, thanks. I know on the pixel 3 any system mod has to be done through magisk. No twrp available at all.
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
Yeah, it's a pain. On this particular device, even mods installed via Magisk cause a bootloop.
Can something similar like this work on the SM-T290 model??
secretwolf98 said:
Can something similar like this work on the SM-T290 model??
Click to expand...
Click to collapse
No, sadly not. The SM-P205 (and SM-P200 [<-- the WiFi model]) is the international model, so it has the Exynos chipset. The SM-T290 and SM-T295 are US models, so they use the Qualcomm chipet. Due to the legal troubles Samsung and Qualcomm have had in the past, Samsung cannot directly sell Exynos device models in US retail locations (they can, however, still sell them online). Additionally, due to the very open nature of the Exynos chipset, I doubt the US carriers would even stock them.
EDIT:
Actually, I misread the question...sorry. So long as you can unlock the bootloader (which on most QC US models you cannot, but I may be wrong on this one), then a similar process would work yes, but you need to scope out the information for your device. The closest match, I would guess, is probably the Galaxy S10e, so I would use that as a starting point.
EagerestWolf said:
No, sadly not. The SM-P205 (and SM-P200 [<-- the WiFi model]) is the international model, so it has the Exynos chipset. The SM-T290 and SM-T295 are US models, so they use the Qualcomm chipet. Due to the legal troubles Samsung and Qualcomm have had in the past, Samsung cannot directly sell Exynos device models in US retail locations (they can, however, still sell them online). Additionally, due to the very open nature of the Exynos chipset, I doubt the US carriers would even stock them.
EDIT:
Actually, I misread the question...sorry. So long as you can unlock the bootloader (which on most QC US models you cannot, but I may be wrong on this one), then a similar process would work yes, but you need to scope out the information for your device. The closest match, I would guess, is probably the Galaxy S10e, so I would use that as a starting point.
Click to expand...
Click to collapse
Ok, thank you for that information. You said the US can't sell exynos chips, Walmart in the US currently has the SM-T510 model with exynos?? That was in the store, I saw it my self.
secretwolf98 said:
Ok, thank you for that information. You said the US can't sell exynos chips, Walmart in the US currently has the SM-T510 model with exynos?? That was in the store, I saw it my self.
Click to expand...
Click to collapse
That may have changed then. Samsung may now be paying Qualcomm for a license. There was a patent infringement lawsuit involving those two a couple of years ago, so idk. I do know that the SM-T290 is a Qualcomm device though.
Any updates for the project? I've been waiting to get a proper twrp and root this device. I hope anyone gets to make it soon.
Been wanting to see updates for this too. Any progress?
is the project dead?
Thread closed.
Hello dear community,
I have a 9th generation Fire 7 with OS 7.3.1.7 from a good friend.
The device is to be bricked.
Professionally I am an IT system electronics technician and as a hobby I am a tecnican-freak, but this is where I reach my limits.
I have already opened the device and tried the hardware method, but I also get an error message in the terminal. So that I cannot unlock the device or the bootloader.
With MTK-SU this is no longer possible with the OS as I have already read and tested.
My question is, is it still possible to crack the device with this build (date 12/20/20)?
Or am I doing something wrong?
Linux installation
mustang
magisk
everything followed as described in these instructions https://forum.xda-developers.com/t/fire-7-2019-mustang-unbrick-downgrade-unlock-root.3944365/
A reasonable instruction video would be desirable if something like that exists
I'm from Germany so sorry if the English is a bit broken
But I hope there is some way to help me
Many Thanks
Edit:
regularly at Check GPT it breaks off see on pic 2
sudoers said:
Hello dear community,
I have a 9th generation Fire 7 with OS 7.3.1.7 from a good friend.
The device is to be bricked.
Professionally I am an IT system electronics technician and as a hobby I am a tecnican-freak, but this is where I reach my limits.
I have already opened the device and tried the hardware method, but I also get an error message in the terminal. So that I cannot unlock the device or the bootloader.
With MTK-SU this is no longer possible with the OS as I have already read and tested.
My question is, is it still possible to crack the device with this build (date 12/20/20)?
Or am I doing something wrong?
Linux installation
mustang
magisk
everything followed as described in these instructions https://forum.xda-developers.com/t/fire-7-2019-mustang-unbrick-downgrade-unlock-root.3944365/
A reasonable instruction video would be desirable if something like that exists
I'm from Germany so sorry if the English is a bit broken
But I hope there is some way to help me
Many Thanks
Edit:
regularly at Check GPT it breaks off see on pic 2
Click to expand...
Click to collapse
What device is listed as a lsusb? If you can access the bootrom (MediaTek Phone 6227) you have hope
If you are willing to experiment I have a couple ideas I've been contemplating as I have a device I want to root also.
Basically two methods mirroring the original, a hardware method (involves probing SPI/UART) or software method leveraging finding a exploit in userspace. (linux or arm based)
WARNING: DO NOT PROCEED IF YOU WANT TO KEEP YOUR DEVICE
I HAVE NOT TESTED ANYTHING PERSONALLY!
I'm just spitballing from a perspective of a advanced Electronics engineer and Linux backround. (none in pentesting or ANDROID environments) Which is what we need.
The Mediatek vulnerability was a once in 5 years exploit and it seems unlikely to find another exploit that wide open.
For the hardware method you'd need a USB - > TTL/UART/SPI adaptor you could try to crack root but if there isn't even a login console then you are out of luck with that aspect.
Proposed software methods:
This might be made to work if compiled for arm32-bit
GitHub - liamg/traitor: :arrow_up: :fire: Automatic Linux privesc via exploitation of low-hanging fruit e.g. gtfobins, pwnkit, dirty pipe, +w docker.sock
:arrow_up: :skull_and_crossbones: :fire: Automatic Linux privesc via exploitation of low-hanging fruit e.g. gtfobins, pwnkit, dirty pipe, +w docker.sock - GitHub - liamg/traitor: :arrow_up: :fire: ...
github.com
If we can get a stock fireOS image we could run
GitHub - cruise-automation/fwanalyzer: a tool to analyze filesystem images for security
a tool to analyze filesystem images for security. Contribute to cruise-automation/fwanalyzer development by creating an account on GitHub.
github.com
or
GitHub - fkie-cad/FACT_core: Firmware Analysis and Comparison Tool
Firmware Analysis and Comparison Tool. Contribute to fkie-cad/FACT_core development by creating an account on GitHub.
github.com
Also found some shell scripts that don't need compilation.
GitHub - carlospolop/PEASS-ng: PEASS - Privilege Escalation Awesome Scripts SUITE (with colors)
PEASS - Privilege Escalation Awesome Scripts SUITE (with colors) - GitHub - carlospolop/PEASS-ng: PEASS - Privilege Escalation Awesome Scripts SUITE (with colors)
github.com
GitHub - pentestmonkey/unix-privesc-check: Automatically exported from code.google.com/p/unix-privesc-check
Automatically exported from code.google.com/p/unix-privesc-check - GitHub - pentestmonkey/unix-privesc-check: Automatically exported from code.google.com/p/unix-privesc-check
github.com
There's also Ghidra if you are a pro binary analyzer which might be the best bet but also the hardest.
-ANDROlD- said:
If you are willing to experiment I have a couple ideas I've been contemplating as I have a device I want to root also.
Click to expand...
Click to collapse
sudoers said:
My question is, is it still possible to crack the device with this build (date 12/20/20)?
Click to expand...
Click to collapse
Got a interesting idea i'm working on, todo with fbtool and unbrick on this particular type of Fire 7, requires compiling lineage, possibly a bit of reverse engineering - currently thinking about it still:
Fire 7 2020 mustang Brainstorming
Trying to brainstorm ideas for unbrick (firstly) of the new Fire 7 2020 Gen 9 models that feature 6.3.1.5 and were released post Feb 2020. Already have a method to downgrade this and many other devices (HD8 Onyx and HD 10 post patch Feb 2020)...
forum.xda-developers.com
The problem is that they secretly revised the hardware for that model .
After the first production run made in 2019 , without the public knowing
They started to lock down the whole tablet.
its not only software locked , its hardware locked on the chip .
Most people didn't realize they did this after the initial 2019 production run .
Any chance I get I advise people not to purchase a newer amazon tablet . especially
The gen 9 .
You can't go wrong with the tablet 7 , gen 7 .
every variant for that Amazon model is flashable . even the ones that need to be opened up
to do the hardware short .
It doesn't look good for the gen 9 model ,
Its locked down harder then Pam Anderson growing up in the 80s .
I've successfully downgraded from FireOS 7 using the hardware method. Latest magisk canary etc
CFKod said:
I've successfully downgraded from FireOS 7 using the hardware method. Latest magisk canary etc
Click to expand...
Click to collapse
That sounds good .
just curious , what year is that 9gen .
That could be more documentation on exactly what year model 7 , gen 9 could
be modded . maybe you found something different that could work after the
2019 batches that were shipped. Idk . I just know what I seen until know ,
but absolutely there could always be exceptions.
Chris.
Sure let
fleisch80 said:
That sounds good .
just curious , what year is that 9gen .
That could be more documentation on exactly what year model 7 , gen 9 could
be modded . maybe you found something different that could work after the
2019 batches that were shipped. Idk . I just know what I seen until know ,
but absolutely there could always be exceptions.
Chris.
Click to expand...
Click to collapse
Does that help? Registered 26th October 2019
CFKod said:
Sure let
View attachment 5854183
Does that help? Registered 26th October 2019
Click to expand...
Click to collapse
mtksu software method will never work on fire os7
However, you can use the hardware method, which installs twrp and allows for downgrade back to 6
LineageOS 18.1 UNOFFICIAL for 2015 Samsung Galaxy Tab S2 SM-T715 ONLY​Model: SM-T715 (LTE) - gts28ltexx - 8" screen, Exynos 5433 SoC, LTE
This is the ONLY model that the ROM will work on.
There is NO ROM for the T710, T810 or T815 in this thread. Questions about T710, T810 or T815 will be completely IGNORED.
For T710 please use the equivalent ROM at its separate XDA forum thread.
For T810 please use the equivalent ROM at its separate XDA forum thread.
You MUST READ posts 1-3 (about 10 minute read) before deciding to install this ROM. If you think this is an unreasonable request, then stop reading now and find another ROM. Thank you.
DISCLAIMER
I am not responsible for lost data, identity theft, lost money, security vulnerabilities, bricked devices or any other hardware or software malfunctions that comes as a result of flashing this ROM.
All involved in bringing this build to you are working voluntarily on it in very limited spare time, and their other life commitments have much higher priority. Don't expect a prompt, or even any, response to questions and bug reports.
Before attempting to install this ROM
1. Ask yourself: would bricking your device be a disaster for you? If yes, don't try this ROM! It can't be guaranteed stable and reliable enough to depend on for daily use.
2. BACKUP YOUR DATA AND EXISTING ROM. Be prepared for a complete restore if anything goes wrong.
3. RESEARCH adb, fastboot, Odin/heimdall, and TWRP and how to use them, if not already familiar with these.
What works
bluetooth
wifi
GPS
brightness
audio through loudspeaker
audio through headphone jack
audio over bluetooth
SELinux enforcing
DRM level 3 (SD definition)
deep sleep
RIL - mobile data and telephony/SMS/Cell Broadcast - some limitations for telephony audio options apply, see below
vibration and haptic feedback
hardware buttons and lighting
What doesn't work
fingerprint. As retiredtab wrote in post 1891 at
https://forum.xda-developers.com/t/...t810-t815-t815y.3879302/page-95#post-85533725
the team will not spend anymore time looking at fingerprint. If you need fingerprint to work, stay with stock Samsung ROM.
DRM level 1 (no HD definition). There's more detail in post 1891 above. I will not be trying to achieve level 1 for HD definition. If you need HD definition for your streaming media, stay with stock Samsung ROM.
If you charge the device while it's powered off and then want to power it on, you MUST wait at least 30 seconds AFTER disconnecting the charger cable before pressing the power button otherwise you might run into strange boot problems such as the touch screen not working. While recent builds solved the touchscreen issue, you still might see excessive battery drain until you perform another reboot.
For telephony audio, currently only the loudspeaker option is working. If you try to use/switch to bluetooth audio during a phone call, the audio stack will go wild and afterwards loudspeaker will stop working too until you perform a reboot.
Please note that for an incoming call, it might take a couple of seconds until both sides can hear each other.
I have invested a lot of time trying to troubleshoot the audio routing, and this is for sure a device-specific issue most likely due to the the old Samsung binaries so chances are almost zero to get that fixed.
Possibly other features that I haven't tested or do not use.
Source Code
See FAQ 1 for links in post #2.
Thanks
LineageOS team for the upstream source code.
@retiredtab, @ananjaser1211, @lpedia, @Yogi555 and @CuckooPenguin for spending nearing 1 month fixing the 2 most biggest bugs in 17.1 that plagued users for nearly 10 months: the wifi instability and random reboots. These are discussed in detail at
https://forum.xda-developers.com/t/...rs-running-any-version-of-android-10.4308193/
https://forum.xda-developers.com/t/...rs-running-any-version-of-android-10.4308203/
A special shout out to retiredtab for providing the T710 ROM and code here which is the base for this ROM. Also this ROM would not have been possible with all the help and mentoring he provided during the past 6 months of development. Also many thanks to lpedia and bluess57 for their outstanding hints and tips.
All past contributors of the exynos5433 code, especially ananjaser1211 for his major contributions and @ripee for working on prior gts2 builds until end of 2021.
@rINanDO for his lmkd spam fix in 18.1.
Alpha testers: simon-edwards for the many hours testing and helping troubleshooting RIL, SELinux policies and various gapps options; Don K and Sir Thopas for addional RIL model testing.
@bluess57 for his excellent code donations for the gts2 LTE models.
retiredtab and lpedia for providing the blueprint for this forum entry and the FAQ in post #2 and constantly improving it. This work is just a little contribution standing on strong shoulders of previous contributions.
Frequently Asked Questions. You MUST READ this before posting any questions. Thank you.
QuestionAnswerQ1. Can I build this ROM for myself? Where are the source and kernel source files?A1. Yes, you can. The source files are listed below.
Kernel
https://github.com/metterschlg/android_kernel_samsung_universal5433
Device Tree
https://github.com/metterschlg/android_device_samsung_gts2-common-selinux
https://github.com/metterschlg/android_device_samsung_gts28ltexx
Vendor
https://github.com/metterschlg/proprietary_vendor_samsung
In addition, there is a repo diff file for device-specific tweaks needed to work and a roomservice.xml (local manifest file) file so you can build this rom yourself. The other patch required for tcp/ip is at https://github.com/DerpFest-11/pack...mmit/22fd53a977eeaf4e36be7bf6358ecf2c2737fa5e
Build manifest can be found at
https://github.com/metterschlg/local_manifests/blob/lineage-18.1/gts28ltexx.xml
Build environment setup is docmented (as code) at
https://github.com/metterschlg/los-devel-scriptsQ2. Is this ROM suitable as a daily driver?A2. It might be, depending on your requirements. You would need to try it yourself, with your preferred apps, to see if suits your purposes. I've been using it myself since mid April 2022 with no major issues.Q3. What do I do if my app xyz doesn't work?A3. I can't help diagnose problems with random apps I know nothing about. If the app is critically important to you and it doesn't work on this ROM, go back to a ROM where it did work.Q4. Why is this ROM laggy and/or buggy?A4. The device will be noticeably slower if you're using any Gapps package. Consider going gapps-free. A lot of apps will work without Google's services, or there exist alternatives that will. Check out F-Droid, Aurora Store, NewPipe, etc.Q5. What TWRP should I use?A5. I use official TWRP 3.6.1_9. Get it from
https://twrp.me/samsung/samsunggalaxytabs280ltexx2015.htmlQ6. Why should I use this ROM?A6. You don't have to! If you don't like it, go back to your old ROM.Q7. Will you offer monthly updates with security patches?A7. I plan to do so. I will try to update the ROM with the monthly security patches after LineageOS has released them, free time permitting. Each monthly build will be quickly tested to make sure the ROM still works, before it's made available (which might in some cases delay the release).Q8. I'm a newbie. Can you provide step by step instructions?A8. We simply don't have the time to do this, but there are lots of tutorials, videos, etc online showing how to flash custom ROMs and how to deal with common problems. Newbie questions are also accepted in the XDA General Questions and Answers forum. Having said that, @pflyaz has kindly make a guide in post #37.Q9. Can I report a bug with respect to the ROM?A9. Yes, but you need to supply the following information. If you don't, I won't look at it.
Provide an adb logcat of the problem, and if possible describe how to reproduce it. Note that I can't help if it involves downloading any app I don't already use that requires payment or creating a userid/password.
To get a logcat, open a terminal window on your PC, connect your device to it via USB, and do this:
Bash:
# clear the logcat first
adb logcat -c
# start logcat trace
adb logcat > problem.txt
# reproduce problem
# wait until problem has occurred,
# then stop trace by hitting ctrl-c then zip the problem.txt file
# before uploading it.
Q10. How long will you build 18.1 for this device?A10. For now, 18.1 will be built for all of 2022. After that, we will make a decision depending on a number of factors.Q11. Do I need to erase everything and format my data before installing this ROM for the first time?A11. Under most circumstances, yes.
If you're coming from stock Samsung Android, or an earlier version of LineageOS, or a different custom ROM, you MUST 'clean flash': boot to TWRP recovery, wipe system, data, dalvik/art cache, and cache partitions, then Format Data, then install this ROM.
If you don't do this you're likely to run into problems, such as getting stuck at the boot animation for more than 5 minutes.Q12. What Gapps should I use?A12. Your choice! There are several well-known Gapps packages, such as NikGapps, BiTGapps, OpenGapps, and MindTheGapps. OpenGapps is being removed as per this post. Do your own research as to what is the most reliable gapps option for you.
I recommend installing the SMALLEST version of any of these, preferably with just the minimum Google services needed to access the Play Store and run apps that depend on Google services.
You could also consider Google alternatives, such as Aurora Store, which mirrors the Google Play Store apps but doesn't need any Google services itself. Many Play Store apps do not actually depend on Google services.
If you are going to install any Gapps package, follow the installation instructions given for that particular package.Q13. I'm having problems with Gapps. Can you tell me why it's not working?A13. I can't answer any questions about Gapps, because I don't use them. Ask your questions on the XDA thread for the Gapps package you're using.Q14. Why isn't my post answered?A14. There are several possible reasons: the question is answered in the FAQ (in which case it will be ignored completely); or it involves apps or operating systems that I don't use; or it's about Gapps, which I don't use; or I simply have not had time to answer any questions.Q15. What speed up/optimization tips do you suggest?A15. These steps can make a big difference to performance:
Turn off animations. Go to Settings > System > Developer options, scroll down to the Drawing section, and set Window, Transition and Animator scale all to "Animation off".
Don't install Gapps unless you depend on something that only Google is providing. Use Aurora Store to get your preferred Play Store apps - they will all be available on Aurora Store. You can choose to access this anonymously or use a Google account.
Don't run more than two apps at the same time. You can probably listen to music in the background and use a web browser at the same time.
Use a web browser with built-in adblock and privacy features, such as Brave.
Use NewPipe to watch your streaming content. It has built in adblock so you don't have to watch forced ads.
Look for apps that are open source, ad-free and lightweight.
Q16. Does this ROM support Magisk so I can root my device?A16. Magisk works with this ROM and I'm using it, but that could change with any revision and changes by Google. However I can't help with any related issues. Direct any questions about Magisk to the XDA Magisk forum.Q17. Will this ROM ever become official?A17. Never. Official maintainers have onerous responsibilities, and I know my device trees, code organization and git commits will NOT meet LineageOS standards. I'm not able or willing to take on the responsibilities and commit the extra time to supporting an official build.Q18. What is the difference between this ROM and others?A18. This ROM tries to be pure LineageOS with little or no modification. Other ROMs may come with a different UI, different bundled apps, etc.Q19. Will there be any major 18.1 code modifications in the future?A19. I don't anticipate any major modifications. There may be some slight tweaking to the SEpolicy, small bug fixes and minor code cleanup, but all the hard work - getting the ROM up and running, and fixing all the major bugs - has been done. This doesn't mean the code is perfect or well organized, but I won't be making any major changes.Q20. Why did you fork the trees?A20. I wanted my own private branch where I could make changes that would only affect my own personal builds.Q21. Can you build a variant of this device? For example, a S-pen version?A21. I cannot and will not try to build for a variant device if I don't physically have that device. I have to be able to boot and test it myself, and there's no guarantee that I can get those variant features working. So I will NEVER build T710, T810 and T815.Q22. Does this ROM have any wifi connection issues?A22. This ROM's wifi has been stable on the specified device ever since lpedia and retiredtab determined the root cause of the wifi problems back in July 2021 and re-installed the original S2 network 'blobs' with LOS 17.1.Q23. Is this ROM secure so I can do financial transactions?A23. Although Android monthly security patches do improve general security, this ROM's outdated kernel and old proprietary vendor blobs/drivers will NEVER get updates of any kind, and could have significant security holes.
In addition, although the ROM is SElinux enforcing, there's a good chance that the rules written (about 800+ lines of code) have some errors.
If the device is rooted, this would further weaken the security.
With this information, it's up to you to make an informed decision about whether you trust this ROM to be secure enough for your financial transactions.Q24. Okay, I understand the consequences and willing to take the risks outlined, now where can I find the BETA ROM?A24. Downloads are at
https://sourceforge.net/projects/los4sgt/files/los18.1/
Please note that there are two builds for every date. Start with the enforcing build, if you hit issues, flash the permissive boot image to determine if your issue is related to SELinux. If you have Magisk installed, you first need to patch the permissive boot image with the Magisk app before flashing.
If your initial enforcing build install does not have working RIL, you might need to fix SELinux labeling of your EFS partition. To do so, use ADB in root mode. Please note that ADB root needs to be enabled in the developer options of your device. Then use the following commands from a PC connected via ADB:
Bash:
adb root
adb shell
# Check if SELinux relabeling is required, do not modify anything
restorecon -R -v -n /efs
# If you see some "Relabeling..." output, run the real relabeling
restorecon -R -v /efs
Release notes
June 18, 2023 Release
June 2023 LineageOS & Android security fixes. >5500 files changed.
May 14, 2023 Release
May 2023 LineageOS & Android security fixes. >5600 files changed
April 23, 2023 Release
April 2023 LineageOS & Android security fixes. >4600 files changed.
March 26, 2023 Release
March 2023 LineageOS & Android security fixes. >27000 files changed.
February 18, 2023 Release
February 2023 LineageOS & Android security fixes. >21000 files changed.
January 22, 2023 Release
January 2023 LineageOS & Android security fixes. >4200 files changed.
December 17, 2022 Release
December 2022 LineageOS & Android security fixes. >3800 files changed.
November 13, 2022 Release.
November 2022 LineageOS & Android security fixes. >4000 files changed.
Kernel improvements by Ananjaser
Starting with these builds I will only publish the SELinux enforcing ROM. If you encounter issues that might be SELinux-related, please first flash the boot_permissive-<date>.img as boot image and re-try to help me identify if the issue is SELinux-related.
October 22, 2022 Release.
Initial public release. First 18.1 T715 ROM with working RIL, also first 18.1 T715 ROM with SELinux in Enforcing mode. T710/T715 common code based on retiredtab's work for T710 so all his latest changes apply as well.
Reserved #3
Reserved #4
Reserved #5
Congratulations on this release @metterschling and @retiredtab , great to see!
@metterschling If you don't mind a couple of comments about your scripts, you need not have created a patch for my script. You could have just forked mine and pushed your changes to it. No need to complicate things for novice builders. Secondly, I'm sure your gts28lte tree can be a source of inspiration for the other 3 variants so as to build a complete set. Thirdly, you may be able to let gts28wifi users flash your builds if you add gts28wifi as a TARGET_DEVICE, to make it easier to cover more users in the meantime. Fourthly, you clone so many repos when it could be cleaner to fork then substitute your forks in the roomservice. This could avoid potential repo syncing errors.
ripee said:
@metterschling If you don't mind a couple of comments about your scripts, you need not have created a patch for my script. You could have just forked mine and pushed your changes to it. No need to complicate things for novice builders. Secondly, I'm sure your gts28lte tree can be a source of inspiration for the other 3 variants so as to build a complete set. Thirdly, you may be able to let gts28wifi users flash your builds if you add gts28wifi as a TARGET_DEVICE, to make it easier to cover more users in the meantime. Fourthly, you clone so many repos when it could be cleaner to fork then substitute your forks in the roomservice. This could avoid potential repo syncing errors.
Click to expand...
Click to collapse
Thank you @ripee. Just to be sure: all you above comments are related to my build environment setup script here, correct?
I agree with regards to the patch, this is how I started and just wanted to document my steps as code. During my next free cycle, I'll be looking at reworking this.
Regarding 2) as mentioned in the opening post my work is already the result of synergies between code trees for the other devices, mainly based on retiredtab's trees, and we keep the common set wherever possible.
So there is no need for 3) as gts28wifi users can directly use the equivalent one linked on the top of post #1.
For 4) I'm open for suggestions which clones you are referring to. As an example, I don't want to fork the entire LineageOS tree just to apply the small NetworkStack patch.
metterschling said:
Thank you @ripee. Just to be sure: all you above comments are related to my build environment setup script here, correct?
I agree with regards to the patch, this is how I started and just wanted to document my steps as code. During my next free cycle, I'll be looking at reworking this.
Regarding 2) as mentioned in the opening post my work is already the result of synergies between code trees for the other devices, mainly based on retiredtab's trees, and we keep the common set wherever possible.
So there is no need for 3) as gts28wifi users can directly use the equivalent one linked on the top of post #1.
For 4) I'm open for suggestions which clones you are referring to. As an example, I don't want to fork the entire LineageOS tree just to apply the small NetworkStack patch.
Click to expand...
Click to collapse
@ripee I've pushed a new version of the build environment setup script, following your guidance. Please let me know if there are more areas of improvement, very much appreciated!
November build lineage-18.1-20221113-UNOFFICIAL-gts28ltexx.zip uploaded. Please see FAQ #24 for the download link.
November 13, 2022 release notes:
November 2022 LineageOS & Android security fixes. >4000 files changed.
Kernel improvements by Ananjaser
Starting with these builds I will only publish the SELinux enforcing ROM. If you encounter issues that might be SELinux-related, please first flash the boot_permissive-<date>.img as boot image and re-try to help me identify if the issue is SELinux-related.
Enjoy!
metterschling said:
Thank you @ripee. Just to be sure: all you above comments are related to my build environment setup script here, correct?
I agree with regards to the patch, this is how I started and just wanted to document my steps as code. During my next free cycle, I'll be looking at reworking this.
Regarding 2) as mentioned in the opening post my work is already the result of synergies between code trees for the other devices, mainly based on retiredtab's trees, and we keep the common set wherever possible.
So there is no need for 3) as gts28wifi users can directly use the equivalent one linked on the top of post #1.
For 4) I'm open for suggestions which clones you are referring to. As an example, I don't want to fork the entire LineageOS tree just to apply the small NetworkStack patch.
Click to expand...
Click to collapse
If gts28wifi users get an error that their device is not gts28ltexx, then yes it would be necessary to add it as a target device in the tree. Lineage uses the networkstack repo from google, which you can tell cuz they track the aosp remote, so in this case we have nothing to fork and substitute. Only a patch of google's own repo would be convenient.
Just to clarify, since there has been discussion about the WiFi version (t713), can this ROM be safely flashed on one?
Also I believe I have a t715Y... Would this t715 ROM work on it?
(I have three Tab S2 units -- two t713 models and a t715Y.)
Thanks
KeepingItCuttingEdge said:
Just to clarify, since there has been discussion about the WiFi version (t713), can this ROM be safely flashed on one?
Also I believe I have a t715Y... Would this t715 ROM work on it?
Click to expand...
Click to collapse
The T713 and T715 have completely different chipsets. T713 is msm8976 and T715 is exynos5433.
If your T715Y is known as "gts28ltexx" OR "gts28lte" as described in post #1, then you can flash this rom on it. You can download an utility called devcheck by flar2 to verify. Your device name will be shown in the system tab under device.
https://play.google.com/store/apps/details?id=flar2.devcheck
metterschling's code checks for gts28lte,gts28ltexx using this below
https://github.com/metterschlg/andr...s28ltexx/blob/lineage-18.1/BoardConfig.mk#L17
KeepingItCuttingEdge said:
Also I believe I have a t715Y... Would this t715 ROM work on it?
Click to expand...
Click to collapse
Most likely, ROMs for the T715 work on the T715Y according to some XDA posts. Like this one. I don't own a T715Y, so can't test myself.
December build lineage-18.1-20221217-UNOFFICIAL-gts28ltexx.zip uploaded. Please see FAQ #24 for the download link.
December 17, 2022 release notes:
December 2022 LineageOS & Android security fixes. >3800 files changed.
If you are coming from a previous version of these builds, you can dirty flash, otherwise please perform a factory reset and format data before installing this ROM.
Enjoy
Hi friends, after loading from TWRP twrp-3.7.0_9-0-gts28ltexx.img.tar on my SM T710, my tab gets stuck on booting with lineageos graphics. I made the backup with TWRP if I upload the files can I repair the tab as before?
mikelosat said:
Hi friends, after loading from TWRP twrp-3.7.0_9-0-gts28ltexx.img.tar on my SM T710, my tab gets stuck on booting with lineageos graphics. I made the backup with TWRP if I upload the files can I repair the tab as before?
Click to expand...
Click to collapse
If I understand correctly, you picked the gts28ltexx version which is for the SM-T715. If your device is the SM-T710 (gts28wifi) I'd strongly recommend to use the ROM and matching TWRP linked in this thread.
If your device is SM-T715, please see FAQ #5 in post #2 of this thread. I use the downlevel TWRP because newer ones did not work for me.
I use a SAMSUNG SM-T715 device just as described:
Model: SM-T715 (LTE) - gts28ltexx - 8" screen, Exynos 5433 SoC, LTE.
To be able to install the ROM I used "TWRP twrp-3.7.0_9-0-gts28ltexx.img.tar"
After several attempts I could neither restore the BACKUP nor start the operating system. I had to do a complete WIPE and at that point lineageos advanced, now I'm having problems, I don't have the gapps I downloaded version 11 for ARM but despite having enough space it gives me an error "70" not enough space. I have no google services and no PLAYSTORE, I am in a critical situation, how can I install the google PlayStore? I can't even add gmail account from settings, it's a disaster.
metterschling said:
If I understand correctly, you picked the gts28ltexx version which is for the SM-T715. If your device is the SM-T710 (gts28wifi) I'd strongly recommend to use the ROM and matching TWRP linked in this thread.
If your device is SM-T715, please see FAQ #5 in post #2 of this thread. I use the downlevel TWRP because newer ones did not work for me.
Click to expand...
Click to collapse
Finally I come to the conclusion, after fully formatting my SAMSUNG SM T715 the ROM started up, the problem was the wrong recovery, using the version indicated in the guide above everything started up correctly.
Unfortunately this ROM is full of bugs and its use is useless, below I will list all the problems it causes during use:
1. 4g calls don't work, during the call you can't hear anything either incoming or outgoing.
2. Bluetooth only works with music while in call it remains mute.
3. the only way to call is to keep the speakerphone open otherwise the call will be silent.
4. Whatsapp is impossible to use and only allows you to use it in beta.
5. Smart Switch as for whatsapp does not work with custom ROMs
6. Does not sync contacts even though sync has started.
It's really a shame after all these hours to find that you've only wasted so much time.
Maybe I've done something wrong, I don't rule it out, maybe someone will be able to give me some advice.