- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago (Last edited 2 weeks ago by SamsungRei ) in
TabletsWhy would you build anti-rollback into this bootloader? You knew this tablet couldn't handle android 11. I understand pushing updates to a newer version, taking a chance that the device can't handle it. But on a device where people more than likely can't afford to have their device killed/phased out/apple-ized. Why would you anti-roll back? There are devs pleading to support this device. Yet you killed it. Don't recommend me to the samsung dev chat. They only do what they are told. The brand is at fault.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago in
Tablets- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
a week ago in
TabletsThis is not an Android problem. This is a Samsung problem. They pushed an update to the bootloader that locks it, even from previous factory images. Greed.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Wednesday in
Tablets- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago in
TabletsGo to Settings > About tablet > Software information and check the latter part of the 'Build number' number. What does it say?
Where/how did you get the stock firmware package for your Tab A?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
a week ago in
TabletsIt's the latest unfortunately. It's locked. I have seen a few promising posts in the last few days though. With a patched vbmeta it may be possible to run a gsi. Will play around with it this weekend.