New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GalaxyS9+ don't start after using of global component blocking in App Manager. Pls help! #363
Comments
<
@starting TWRP 3.2.3-0-32aef7a2 on Sat Apr 10 2021
(pid 3444)
TW_NO_REBOOT_BOOTLOADER := true
RECOVERY_SDCARD_ON_DATA := true
I:Lun file '/sys/class/android_usb/android0/f_mass_storage/lun0/file' does not exist, USB storage mode disabled
TW_HAS_DOWNLOAD_MODE := true
TW_INCLUDE_CRYPTO := true
I:TW_BRIGHTNESS_PATH := /sys/class/backlight/panel/brightness
I:Found brightness file at '/sys/class/backlight/panel/brightness'
I:TWFunc::Set_Brightness: Setting brightness control to 12800
I:LANG: en
Starting the UI...
Skipping adf graphics -- not present in build tree
cannot find/open a drm device: No such file or directory
fb0 reports (possibly inaccurate):
vi.bits_per_pixel = 32
vi.red.offset = 16 .length = 8
vi.green.offset = 8 .length = 8
vi.blue.offset = 0 .length = 8
setting GGL_PIXEL_FORMAT_BGRA_8888
double buffered
framebuffer: 3 (1440 x 2960)
Using fbdev graphics.
I:TWFunc::Set_Brightness: Setting brightness control to 12800
I:Loading package: splash (/twres/splash.xml)
I:Load XML directly
I:PageManager::LoadFileToBuffer loading filename: '/twres/splash.xml' directly
I:Checking resolution...
I:Scaling theme width 1.333333x and height 1.541667x, offsets x: 0 y: 0 w: 0 h: 0
I:Loading resources...
I:Loading variables...
I:Loading mouse cursor...
I:Loading pages...
I:Loading page splash
I:Switching packages (splash)
=> Linking mtab
=> Processing /etc/recovery.fstab
I:Reading /etc/recovery.fstab
I:Processing '/system'
I:Processing '/system_image'
I:Processing '/data'
I:Processing '/cache'
I:Processing '/preload'
I:Created '/preload' folder.
I:Processing '/boot'
I:Processing '/recovery'
I:Processing '/modem'
I:Processing '/efs'
I:Created '/efs' folder.
I:Processing '/misc'
I:Processing '/vendor'
I:Created '/vendor' folder.
I:Processing '/vendor_image'
I:Processing '/odm'
I:Created '/odm' folder.
I:Processing '/external_sd'
I:Created '/external_sd' folder.
I:Processing '/usb-otg'
I:Created '/usb-otg' folder.
I:Done processing fstab files
I:Setting up '/data' as data/media emulated storage.
I:mount -o bind '/data/media' '/sdcard' process ended with RC=0
I:mount -o bind '/data/media/0' '/sdcard' process ended with RC=0
I:Setting up '/data' as data/media emulated storage.
I:mount -o bind '/data/media' '/sdcard' process ended with RC=0
I:mount -o bind '/data/media/0' '/sdcard' process ended with RC=0
I:Backup folder set to '/data/media/0/TWRP/BACKUPS/2134b3361c057ece'
I:Settings storage is '/data/media/0'
I:Decrypt adopted storage starting
I:PageManager::LoadFileToBuffer loading filename: '/data/system/storage.xml' directly
I:successfully loaded storage.xml
Updating partition details...
I:Data backup size is 8801MB, free: 4572MB.
I:cmd: /sbin/exfat-fuse -o big_writes,max_read=131072,max_write=131072 /dev/block/mmcblk0p1 /external_sd
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
...done
I:Unmounting main partitions...
Partition Logs: /system_image | /dev/block/sda18 | Size: 4400MB /data | /dev/block/sda25 | Size: 53382MB Used: 8801MB Free: 4572MB Backup Size: 8801MB /cache | /dev/block/sda21 | Size: 581MB Used: 1MB Free: 579MB Backup Size: 1MB /preload | /dev/block/sda22 | Size: 5MB Used: 0MB Free: 5MB Backup Size: 0MB /boot | /dev/block/sda10 | Size: 55MB /recovery | /dev/block/sda11 | Size: 64MB /modem | /dev/block/sda12 | Size: 50MB /efs | /dev/block/sda3 | Size: 15MB Used: 3MB Free: 12MB Backup Size: 3MB /misc | /dev/block/sda15 | Size: 1MB /vendor | /dev/block/sda19 | Size: 617MB Used: 558MB Free: 58MB Backup Size: 558MB /vendor_image | /dev/block/sda19 | Size: 650MB /odm | /dev/block/sda20 | Size: 625MB Used: 597MB Free: 28MB Backup Size: 597MB /external_sd | /dev/block/mmcblk0p1 | Size: 122110MB Used: 54753MB Free: 67357MB Backup Size: 54753MB /usb-otg | | Size: 0MB Used: 0MB Free: 0MB Backup Size: 0MB I:Loading package: TWRP (/data/media/0/TWRP/theme/ui.zip) I:Copying file /cache/recovery/log to /cache/recovery/last_log |
Any solution for to fix this problem? |
You could've informed us right after it had stopped working. Anyway, components blocked by AM are stored in two places:
Note: None of these files are accessible from ADB without root, but you can do this in the recovery if they support it. If the recovery doesn't offer a terminal or a file manager, use something like the Aroma FM. |
OKe. Thank you Muntashir. |
"You could've informed us right after it had stopped working." Yes. You are 100% right. But I didn't. I tried to stay calm and started looking for a solution myself. For reliability, before all the manipulations, I made a backup copy of all my no longer starting system in recovery TWRP. (So I can to put all old files back in dirty system with new ROM files and I understand that this is not a good solution cause new files will be deleted in this situation. May be I will do first Restore of my all broken system. I will find this map and this blocked files. I will delete it and will try to restart? If it will not working I will flash with a new ROM 2.6 and I will see if it help... ?) Unfortunately, I upgraded the phone with a newer bootloader and newer firmware ROM. Roll back to the previous bootloader is not possible. I found out about this later, when I wanted to return to the old firmware version 2.3 instead of the new 2.6. Now I looked at both folders and there is nothing inside them. Apparently with a dirty flashing of newer ROM, the new firmware rubbed all AM files in this maps. This map if I use windows map is empty: "Note: None of these files are accessible from ADB without root, but you can do this in the recovery if they support it." Yes. As you said they are not accessible. From Windows map too. I have Terminal in TWRP recovery but I don't know which command to give him for to see/ to reach this map. If I write |
I have in TWRP Recovery this Advanced options: |
I try to restart now for to do after this new log file on my microSD card. <
Starting TWRP 3.2.3-0-32aef7a2 on Sun Apr 11 08:12:37 2021
(pid 3442)
TW_NO_REBOOT_BOOTLOADER := true
RECOVERY_SDCARD_ON_DATA := true
I:Lun file '/sys/class/android_usb/android0/f_mass_storage/lun0/file' does not exist, USB storage mode disabled
TW_HAS_DOWNLOAD_MODE := true
TW_INCLUDE_CRYPTO := true
I:TW_BRIGHTNESS_PATH := /sys/class/backlight/panel/brightness
I:Found brightness file at '/sys/class/backlight/panel/brightness'
I:TWFunc::Set_Brightness: Setting brightness control to 12800
I:LANG: en
Starting the UI...
Skipping adf graphics -- not present in build tree
cannot find/open a drm device: No such file or directory
fb0 reports (possibly inaccurate):
vi.bits_per_pixel = 32
vi.red.offset = 16 .length = 8
vi.green.offset = 8 .length = 8
vi.blue.offset = 0 .length = 8
setting GGL_PIXEL_FORMAT_BGRA_8888
double buffered
framebuffer: 3 (1440 x 2960)
Using fbdev graphics.
I:TWFunc::Set_Brightness: Setting brightness control to 12800
I:Loading package: splash (/twres/splash.xml)
I:Load XML directly
I:PageManager::LoadFileToBuffer loading filename: '/twres/splash.xml' directly
I:Checking resolution...
I:Scaling theme width 1.333333x and height 1.541667x, offsets x: 0 y: 0 w: 0 h: 0
I:Loading resources...
I:Loading variables...
I:Loading mouse cursor...
I:Loading pages...
I:Loading page splash
I:Switching packages (splash)
=> Linking mtab
=> Processing /etc/recovery.fstab
I:Reading /etc/recovery.fstab
I:Processing '/system'
I:Processing '/system_image'
I:Processing '/data'
I:Processing '/cache'
I:Processing '/preload'
I:Created '/preload' folder.
I:Processing '/boot'
I:Processing '/recovery'
I:Processing '/modem'
I:Processing '/efs'
I:Created '/efs' folder.
I:Processing '/misc'
I:Processing '/vendor'
I:Created '/vendor' folder.
I:Processing '/vendor_image'
I:Processing '/odm'
I:Created '/odm' folder.
I:Processing '/external_sd'
I:Created '/external_sd' folder.
I:Processing '/usb-otg'
I:Created '/usb-otg' folder.
I:Done processing fstab files
I:Setting up '/data' as data/media emulated storage.
I:mount -o bind '/data/media' '/sdcard' process ended with RC=0
I:mount -o bind '/data/media/0' '/sdcard' process ended with RC=0
I:Setting up '/data' as data/media emulated storage.
I:mount -o bind '/data/media' '/sdcard' process ended with RC=0
I:mount -o bind '/data/media/0' '/sdcard' process ended with RC=0
I:Backup folder set to '/data/media/0/TWRP/BACKUPS/1234b5678c901ece'
I:Settings storage is '/data/media/0'
I:Decrypt adopted storage starting
I:PageManager::LoadFileToBuffer loading filename: '/data/system/storage.xml' directly
I:successfully loaded storage.xml
Updating partition details...
I:Data backup size is 8802MB, free: 4571MB.
I:cmd: /sbin/exfat-fuse -o big_writes,max_read=131072,max_write=131072 /dev/block/mmcblk0p1 /external_sd
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
...done
I:Unmounting main partitions...
Partition Logs: /system_image | /dev/block/sda18 | Size: 4400MB /data | /dev/block/sda25 | Size: 53382MB Used: 8802MB Free: 4571MB Backup Size: 8802MB /cache | /dev/block/sda21 | Size: 581MB Used: 1MB Free: 579MB Backup Size: 1MB /preload | /dev/block/sda22 | Size: 5MB Used: 0MB Free: 5MB Backup Size: 0MB /boot | /dev/block/sda10 | Size: 55MB /recovery | /dev/block/sda11 | Size: 64MB /modem | /dev/block/sda12 | Size: 50MB /efs | /dev/block/sda3 | Size: 15MB Used: 3MB Free: 12MB Backup Size: 3MB /misc | /dev/block/sda15 | Size: 1MB /vendor | /dev/block/sda19 | Size: 617MB Used: 558MB Free: 58MB Backup Size: 558MB /vendor_image | /dev/block/sda19 | Size: 650MB /odm | /dev/block/sda20 | Size: 625MB Used: 597MB Free: 28MB Backup Size: 597MB /external_sd | /dev/block/mmcblk0p1 | Size: 122110MB Used: 54754MB Free: 67356MB Backup Size: 54754MB /usb-otg | | Size: 0MB Used: 0MB Free: 0MB Backup Size: 0MB I:Loading package: TWRP (/data/media/0/TWRP/theme/ui.zip) I:Copying file /cache/recovery/log to /cache/recovery/last_log
|
"Anyway, components blocked by AM are stored in two places: From file Manager in Recovery I find a lot of files inside /data/system/ifw: And a lot of other files. "/data/system/users/0/package-restrictions.xml: Delete all the XML tags called disabled-components, i.e." In this map: /data/system/users/0/ I see inside 2 files called: Inside both there is nothing. If I push it I see in the file manager 6 buttons: Copy, Move, chmod755, chmod, Delete, Rename file. |
In this map just find this AM file with log of my last "activity": ) PC\USB -device MTP\Internal Storage\Android\data\io.github.muntashirakon.AppManager\files\cache |
I deleted all entries in the folder: Was sure more than 150 .xml files inside. I try to restart in System but without succes. May be I need to change as you said /data/system/users/0/package-restrictions.xml: Delete all the XML tags called disabled-components but I see no any entries inside. Should I push chmod755 button for to see this inside? I don't know what to do for to see this entries for to correct it as you said above. In this map: /data/system/users/0/ I see inside 2 files called: Inside both there is nothing. If I push it I see in the file manager 6 buttons: Copy, Move, chmod755, chmod, Delete, Rename file. |
Oh! It's oke. |
All restrictions between and inside package-restrictions.xml deleted! And NOW EVERYTHING WORKS properly! Oh Muntashir! YOU ARE GREAT and YOUR AppMan ALSO VERY STRONG!!! : ))) Thank YOU many times for your help and very great application! Many thanks!!! A question again. I think to delete this samsung ROM and all google, facebook, twitter etc apps and services by installing Arrow ROM. Сan you please advise any other operating system (ROM?) that can be flashed into a smartphone? Anything deeply cleansed of all this filth? That was a good new experiance! |
Congratulations! Not many people have the patience to do what you've done (and blame others for their mistake).
I would suggest you start with Lineage OS. You can also try LeOS if it's available and stable for your device. My favourite was Magma Moonshine which is, unfortunately, not active right now. Most other ROMs have different issues such as Gapps, SELinux permissive, signature spoofing support etc. I've never tried Arrow OS but last time I checked its website contains ads from Google. You can also try crDroid but make sure to check whether SELinux is enforcing (otherwise you won't have any security whatsoever). |
HI Muntashir. Thank you again. Avow own mistake, there is nothing wrong with that. I will check AЯЯow ROM with and without GApps. It's not normal that they has 6oo6l6 ads on his site. Go6gl6 try to buy everything and everybody with big experience like yours. May be Arrow OS is also already infected like his site and owners. I'm very glad that your don't sell you self to nobody, to him inclusief. A few time ago I thought to try PinePhone64 (link) but I seen that he don't work as he must. Better to say totally don't work. About Librum5 I know not enough and his price (around +/-800$) is also not so affordable. I thought to downgrade to Samsung galaxy Note 4 or galaxy S5 with possiblity to pull out battery. Can you also advise some internet site or group for to know more about how to protect devices and internet safety (started with changing of home router/modem till how to block 4G/5G gsm module inside our SamsuG66l6Appel SpyPhones? |
Librem and Pine Phones are worse than Android phones in terms of security. The root cause of the insecurities in Android (or any other operating systems) is, unfortunately, the Linux kernel itself. A large kernel such as Linux can have a lot of vulnerabilities. The best way to solve this issue is to use the micro kernels. Micro kernels, as the name suggests, is very small in size and therefore, when cleverly implemented, they can only have a small set of vulnerabilities. Google, with Fuschia OS, is trying to use a micro kernel, as a result. There are many sources and communities available such as https://prism-break.org, https://privacytools.io (the latter does not always provide good info), https://madaidans-insecurities.github.io, https://infosec-handbook.eu (the latter two are very good resources). If you're looking for a telegram/Matrix group, you can also try @spitetech, @techloregroup (https://techlore.tech), etc. |
"The best way to solve this issue is to use the micro kernels." Do you know some firewall that can control maximum inside android phones from useal ports activity till kernel of even gsm block activity? And what do you think about Element (Riot) messenger? Which one is a good alternatief for SpytsApp (WhatsApp)? |
Is it possible to find with AM filter all apps with for ex. gps tracking-, microfon-, camera-, run in background and read_clipboard activity and to deactivate this activity for always? Some apps don't late to do this? HOw to switch OFF this operation of some App? Also a question. Is it possible to move Scanner button in AM to the left without too much swipe to the right for to reach him? |
Is this activity of Element messenger serves for ex. for to communicate with google and facebook? I see if I block this activities the app is still alive and work without it still good. Element says: <
We believe people should be able to talk, via the internet, with the same level of privacy as a face-to-face conversation in their own home. We believe people should be able to communicate on their own terms; securely and in control of their data. Now used by over 20 million individuals, companies and governments to protect their communication.>** But actually work together with 6oo6k6 and facebook. |
|
OKe. Tnx for info. I'm not really satissfied with connection inside this messenger. I have a question about AM. |
Use Element from F-Droid, not Google Play.
Could you share a screenshot or something? |
After install of PAssword Saver (good manager but unfortunally as you see with 66ogle trackers) and first blocking of all trackers by 1 click action I seen this windows: I flashed LingeosOS 11 (lineage-18.1-20210321-UNOFFICIAL-star2lte.zip) After 1 secound on this page (Providers) AM stopt with a fault message "the application crashed again. About App. Close App " I think this is cause this AM build was made for Android 10 and not Android 11. After stop of some not critical system apps and reestart of this OS, it's run just the bootloop and than ly device goes to Recovery. No problem. I just checked what is this, this LineageOS and ArrowOs. Now I need to re flash it again or looking for an old ROM based on Android 10. What do you think? May be it is better go back to Android 10 till you made some update of AM for Android 11? 3 questions again.
Thank you Muntashir! |
v2.5.20 added experimental support for Android 11. So, crashes were very much expected. Most of the crashes are fixed in the pre-releases and many more fixes will be shipped with v2.6.0, the next release. I don't have Android 11 on my device, so I can't test the issues myself.
Don't use unofficial LOS ROMS, they don't represent Lineage OS team and are usually full of bugs.
Yes, even flagship phones (except the Pixel ones) are having issues with A11. It's better to use Android 10 for now (you'll get regular patches anyway).
Root has its own issues. Currently Magisk is the best way to handle root because it runs in its own SELinux context which is better than any other rooting software.
I don't know which terminals work or do not work on Android 11. You can try Android Terminal or Termux (both available on F-Droid).
Try Bitwarden (online) or KeePassDX (offline/online using git repo), both available on F-Droid (the former is via their own repo). |
Thank you very much for your answers! The last avalable build of AM on f-droid is 2.5.17 (+/-6 month old). I use him and he crash when I go to the page "Providers". I see that A11 is not stable. Can crash without real strong reason after restart. So it's really, so to speak, unripe fruit. I use unofficial LineageOS cause unfortunally there is no an official ROM for my device (just this around 20 are supported officially) I think to try your last AM pre-build AM, may be it will work without crashes. Which browser can you advise? Thank you very much for your attantion, help and advice! |
Then you should try other official ROMs. Unofficial LOS are always unstable (that's why they're unofficial!).
Pre-releases should work fine in most part.
I would suggest Bromite. It has fingerprint mitigation features that no other Android browsers have. Privacy Browser still uses Android webview, so you've to change the webview to actually have any privacy. The author promised a built-in engine long ago and I haven't seen any progress on that.
To you too, especially in this global pandemic situation. |
I try to connect my S.G. S9+ to PC (Win x64) via USB he don't wonna connect to PC. I see just icons of mmy device but there is nothing inside. If I switch On the USB debugging under Developer option it don't wonna connect totaly. |
Could you please describe the correct procedure for reinstalling the AM? First, I need to undo all the changes made by the AM of the previous version, or can I install direct a new one over the old one without changing the settings in the old one? |
Oh, I see. First desinstall and that again full install. Can you change in List option point: Trackers to Trackers inside (T.i.) and to add this undertitle near the name of App.? If I good understand, not all trackers are bad. But how to know which one is safe and which one is bad? |
I see an option SEND SELECTED (missing) Signatures. I find 246. But there is no button Select all. Can you add it pls? |
There's a reason for this. See https://muntashirakon.github.io/AppManager/guide/scanner-page.html#missing-signatures Most of your questions already have answers in the docs. I suggest you should take a look at the docs first. |
May be it will be good to add an option: Find all missing (unknow yet) signatures by 1 click option, in Advance option. And that late it send to you. |
YEs. Tnx. I will read it first deeper. |
No, I don't need all the signatures. I only need the relevant ones. |
HI Muntashir! Before all thank you very much for your fantastic app! IT"s very usefull!
Hi friends!
I have Samsung Galaxy S9+ 64Gb Exinos. Alexis ROM 2.6, last boatloader flashed with Odin:
BL_G965FXXUFFUC6_CL21315605_QB39020729_REV01_user_low_ship.tar
CP_G965FXXUFFUC6_CP18513641_CL21315605_QB39020729_REV01_user_low_ship.tar
PC runnig with Windows x64.
Today I made a big fault when I try to use App Manager's option without to read instruction and danger warning about this function.
I'am not idiot, but I done this like an idiot cause on this moment I was very angry for all this f**king Google, Facebook and Samsung trackers and other spy options inside phone.
So, I gone to this folder: global component blocking, than searched and found all the components of Facebook and block it and than swiched on search even between the system components everything with name Samsung and pressed like an donkey the button to block all this components.
The list was very very very long.
Oh my God! Why I made it!????
So.
Ofcause after this stupid manipulations, all icons and the main screen stopped to responding on my screen.
No any answer for to press action. Just the up menu worked at this moment.
An error message occurred about stopping the OneUI application on the main page.
After restart of my device I seen just the first blocked main screen with clock and 2 buttons for camera and to call. But no reaction for anything more.
Further nothing worked.
Then I had an idea to upgrade the my old firmware from AlexisROM 2.3 to AlexisROM 2.6 with the replacement of the botloader.
I flashed it using Durty flash with succes and I had a hope that it will help me to reactivate all blocked components (facebook and samsung) and to start my device for to do backup of all my passwords and notes.
Yes, I know that that I had to do it in advance, before but the memory of my micro SD card was full. So i thought to do it later and... you see I made an mistake before to actually to do this backup in TWRP.
Yes. I'am booby!!! Why? Why I pushed it!? Oh my God!
Than I try to do an restore of just system map from TWRP from my old buckup without my last passwords and last notes.
But without any succes. I seen just the boot loop. I understand that with a new ROM 2.6 everything changed but than I gone to do everything like before, like on the moment of ROM 2.3 (cause I made an broken ROM copie with Alexis ROM 2.3 with blocked Samsung components). So no I have flashed Alexis ROM 2.6 and my device start (1-2 minutes) with samsung logo and that can't start with a first wallpaper screen.
So, no I have the follow situation:
My device try to run with a new durty flashed system with the latest boatloder from Alexis but after 2 attempts to start it, he goes automatically to restart and goes to TWRP mode.
So I can't start as before.
I need to take all my passwords from passwords app and all my notes from Samsung Note app. but I can't!
I can to connect my devce via ADB via TCP but I don't know what to do after this last command:
"Finally, run the following command to enable ADB over TCP:"
"./adb tcpip 5555"
I see an answer message in Window PowerShell:
PC C:\adb\platform-tools> ./adb devices
List of devices attached
1234b5678c901ece recovery
What can I do for to de block all blocked samsung components?
Do you know something like SafeMode ROM for to dirty flash into divices like in my situation?
Please help me somebody!
Developer options is enabled.
ADB via TCP works. Is it may be possible to uncheck all blocked in App Manager fk**ing samsung components via TCP commands?
Divice can start but can't go to the first screen with asking of password for to unlock him.
I can seen internal storage of disc with all maps but map Note is empty and Password app like all other apps I can't see from my window. Pls see the picture in attach.
The text was updated successfully, but these errors were encountered: