Timeline for Analyzing boot loop Root cause from console-ramoops-0 ( & logcat)
Current License: CC BY-SA 4.0
13 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 20, 2021 at 16:39 | comment | added | alecxs | btw there is app doing the same thing (restore app data and chown uids) | |
| Sep 20, 2021 at 5:55 | comment | added | alecxs | it took me ages to figure out why jellybean backup solution didn't work any longer. selinux was introduced with KitKat (permissive) and the only reason for me to compile gnu tar. if you copy app data with no secontext, restorecon will set (wrong) default values. but there is more, some xattrs are also important and will cause crashes even on permissive. if you follow instructions exactly it should work for you too (at least for WhatsApp) | |
| Sep 20, 2021 at 5:45 | comment | added | user1874594 | dunno could be? I will ..gimme s'time ... pastbin that entire comparison reproduce the error... if it'd help dig up the root | |
| Sep 20, 2021 at 5:42 | comment | added | alecxs | so it's the same tar that behaves differently on arm | |
| Sep 20, 2021 at 5:14 | comment | added | user1874594 |
gnu tar admittedly secontext isnt something that worried me cos my SeLinux is passive....not Good, yes I know. But keeping it like that till I find all the raves and rants in logcat about violations ... that is for future :)... the way I hv things ..I still use a 2nd ext4 to store all my non split apks & all user app data ( save for his TWRP backup sit'n). I wrote code that installs these apks & then finds out their userid gids & then links the data & does all necessary chowns the access rights were already there. Most apps work OOTB. Seldom complaints cos of diff. arch etc
|
|
| Sep 20, 2021 at 4:56 | comment | added | user1874594 |
here's my Linux Pup tar root# tar --version tar (GNU tar) 1.30 Copyright (C) 2017 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html>. This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Written by John Gilmore and Jay Fenlason.
|
|
| Sep 19, 2021 at 17:00 | comment | added | alecxs |
so you say the malformed header is not caused by twrp-tar on creating, and the error output (which is filtered with 2> /dev/null in linked question) does only appear on arm but not on x86? that's strange because I always get it. what is your linux tar version, is it star maybe (because that's what twrp-tar is based on)?
|
|
| Sep 19, 2021 at 11:58 | comment | added | user1874594 |
Well bad might be a 'bad' name after all. It should at least be able to list out the contents vide tf option and that is just where it gives that error as welll . And on Linux it worked just fine no issues. So I guess the bad was reference to its incompatibility with my tar. AFAIK when I made that tar using TWRP I never used the compress option. I grabbed an ARM tar based on the link choosing the smallest package size...should have delved into it being available solo ...
|
|
| Sep 19, 2021 at 1:48 | comment | added | user1874594 |
thanks Alec ..actually busybox tar as well as arm tar both were tried and they both threw up in the middle of the road so as to say. If it was a problem of wrongly using it - they'd not extract partially . Entire f would be rejected w something like 'not a tar archive' --this error was unexpected end of tar. AFA UUIDs are concerned. Yes I did that by a program I wrote that grabbed individual UID & GID after the apks got installed and run chown but that wasnt part of Q I asked. I will nonetheless put in an udpdate line for completeness
|
|
| Aug 4, 2021 at 14:47 | comment | added | user1874594 |
Howdy Mikko SeLinux 1 is kept so state in many Custom ROMs . In my case for stock ROM I keep it at 1 momentarily to see where all did I violate & accordingly change context before toggling but that is at ease . /data/tmp/tar-arm isnt expected as per what the link mentioned - you have to grab it from the smallest available gapp. Still dont follow why 1) that /data restore boot-looped 2) UnEncry'd backup from Encry Partcant be restored simply & causes Tar Fork found that as a bug report in an older TWRP version & this is few hoops ahead
|
|
| Aug 4, 2021 at 13:58 | comment | added | Mikko Rantalainen |
Note that it is not safe to use ROM that doesn't have SELinux enabled as your daily driver. It sounds that the ROM you're trying to use is just broken or if /data/tmp/tar-arm wasn't provided by the ROM, that's the problematic part of your adventure. If you have encrypted data partition, you have to use good enough TWRP version or you cannot actually have a working backup (it's easy to notice - if you have encrypted data partition, TWRP should prompt for password). Note that the backups made with TWRP are not encrypted; see android.stackexchange.com/q/188339/5738 for details.
|
|
| Aug 3, 2021 at 10:01 | vote | accept | user1874594 | ||
| Aug 3, 2021 at 9:10 | history | answered | user1874594 | CC BY-SA 4.0 |