Thanks for the help! I tried that a few times and still got the bootloop. Even after getting into recovery and wiping the data and cache there a few times as well. i ended up using a coupon code for Android Reiboot, which I think is basically a script that runs the Odin, lol, but it was only $13 so I did it. Ran it several times on and was still getting the boot loop and finally one of them took and it booted to the stock welcome screen. As soon as it came up I submitted the trade at Amazon. Thanks again for the help, not sure what finally took or if it was the multiple partition/cache wipes, but I definitely appreciate you pointing in the right directions to get it resolved!Sorry you're having this trouble. It took me ages to sort things out also.
I've just realised that I've glossed over the fact that you want to trade your device in, so are looking to re-create a plain vanilla stock installation.
This means you probably don't want to retain TWRP on the device.
If it were me, I'd be doing this - indeed I've done this before:
After successfully flashing these, the tablet rebooted into the stock ROM without further ado.
- obtain the *exactly* correct stock ROM (got mine at samfw.com), paying attention to the bit (BINARY/U/SW REV.) number (mine is 5 - you can see this in the Odin Mode screen on your tablet)
- using Odin3
- Options tab – ticked:
- auto reboot
- Nand Erase
- F. Reset Time
- Files to flash:
- CSC (not home_csc – I wanted to wipe everything)
Hope that helps.
I did a system wipe and then tried loading only the Lineage 19.1 zip with no Gapps but still get the factory data reset reboot right away.I had an older version of 19.1 installed on my SM-T580 and someone else was using for about 4 months but they were done with it so I thought I would wipe it and install the latest version. Put the following on the portable SD card:
Booted into TWRP 3.6.2_9-0 and wiped system , internal storage, and data. Then installed the Lineage zip and the NikGapps zip in succession. Rebooted into system and got to that bluish screen with "Hi there" but then it immediately restarted saying "Factory data reset":
View attachment 5773183
So, did the same procedure and same result. Then did it with OpenGapps instead of Nik but same result.
Any ideas? Thanks.
I upgraded TWRP to 3.7.0_9-0 from https://dl.twrp.me/gtaxlwifi/ but still getting that error. Also tried a previous version of the ROM lineage-19.1-20221020-UNOFFICIAL-gtaxlwifi.zip. Tried wiping everything: system, internal storage, data, cache, Dalvik cache. Still same problem. Gonna take a break from this to clear my head.
As I am also never sure what the difference between wiping and formatting is (and which one includes the other): Have you tried also the format option? Similar errors during clean flash as you see are often related to file system errors.I upgraded TWRP to 3.7.0_9-0 from https://dl.twrp.me/gtaxlwifi/ but still getting that error. Also tried a previous version of the ROM lineage-19.1-20221020-UNOFFICIAL-gtaxlwifi.zip. Tried wiping everything: system, internal storage, data, cache, Dalvik cache. Still same problem. Gonna take a break from this to clear my head.
Here is a good explanation: https://forum.xda-developers.com/t/wipe-data-and-format-data-in-twrp.4095531/
Building on this, I continued today and found something else which is odd (third bullet):Different from my post last night (see below), I tried the same today with NikGApps (dirty flash on P580 with encrypted storage and with GApps from 20221020 to 20221127) on a second device and running into issues:
Anyone an idea? Just a glimpse, bad luck, something with the latest build, the NikGapps or could it be that the storage is broken? Probably asking for too much but maybe someone has by chance an idea - before I wipe completely and give it a clean try.
- As done on other devices, dirty flashing only the LOS 20221127 build. Running into boot loop (LOS start-up screen after PIN for decryption for 1-2 min and then reboot).
- Tried flashing LOS 20221127 build together with NikGapps-core-arm64-12.1-20220908-signed. Results in starting to system but Play Store not able to connect.
- Wiping system before flashing LOS 20221127 build together with NikGapps-core-arm64-12.1-20220908-signed. Results in starting to system but Play Store still not able to connect.
- I double-checked the checksum (LOS build on SD card) but that one is correct as well.
- Wiping system before flashing LOS 20221020 build together with NikGapps-core-arm64-12.1-20220908-signed as during initial installation. Results in a message that the encrypted data are corrupt.
- Wiping system before flashing again LOS 20221127 build together with NikGapps-core-arm64-12.1-20220908-signed. Results in starting to system (no complaint on decrypting data) but Play Store still not able to connect.
LATER ADDITION: Issue with Play Store being offline resolved - but not clear why it happened in the first place. Issue was that the Play Store had network data access deactivated. I recall also that the device was in flight mode when starting to system in 2. of above list. And I know for sure it wasn't before starting the dirty flash. So, something is still quite odd about all of this - a. o. the boot loop mentioned in 1.
first of yall youre using the wrong twrp img use the one given under the guide based on the model you have... again read the guide before doing mistakes like thatI cannot power off the tablet , continuous running , I left the battery going to zero after I put the power cable doing the same thing .
It's starts after I load the Odin3_v3.10.7 / twrp-3.0.2-0-gtaxlwifi.img
I do not have access to operator system, It's stuck to black screen.
This is not true. You can disable the "application bar" at the bottom. Also it is possible bring back the classic navigation bar or alternative to use the gestures navigation. Tried all of these. All are working fine.
Depends on what you need - I can't compare as I never used the Samsung apps. But you can test OneNote and alike (I use Quill for privacy reasons) before upgrading from Stock and decide based on that for writing. PDF is no issue for sure.
... just read carefully the very first post of the developer. He explained it and it works (and was already asked here several times).