Database Users

WARNING messages created byROM kitchen log files

I have been playing around in the kitchen the past days and managed to cook several 'version' of ROMs. Each always produced the same error message, as below:
echo Warning: OS type not detected, you may need to set tounicode variable manuallywrite xip block starting at 81740000, with 7 fileswrite xip block starting at 81b00000, with 122 files!!! your rom is not known to me: md5: 1cd007bbffa268b12b7968cabb7cc75fthis bootloader seems to be V5.22 2003-05-15 17:46:55no operator rom found80000000 - 80040000 -- bootloader 0 files 1 modules80040000 - 8015d5cc 9 XIPKERNEL 5 files 5 modules80180000 - 80375bdc 8 KERNEL 10 files 14 modules80380000 - 8064306c 7 OS 20 files 36 modules80670000 - 80be66a8 6 SHELL 107 files 88 modules80c00000 - 8102ce98 5 BROWSING 11 files 36 modules81050000 - 813ef114 4 COREAPPS 95 files 44 modules81400000 - 815d2238 3 EXAPPS 34 files 7 modules815f0000 - 8171bc7c 2 PHONE 56 files 19 modules81740000 - 8177ffec 10 XDA_DEVELOPERS1 7 files 0 modules81780000 - 81781c34 -- xip chain 11 xip entries817c0000 - 81ae4338 1 MISC 109 files 42 modules81b00000 - 81e1904c 11 XDA_DEVELOPERS2 122 files 0 modules81ec0000 - 81ee5800 -- bitmap : ffffffff .. ffffffff../rom.exe: found a preamble of 31232 bytes adding: English/NK.nbf (deflated 47%)
-------------------------------------------
Does it mean anything? Is this normal?
I have used one of the newly created ROM and installed it in my XDA. The installation went smooth. But now after 12 hours usage my XDA run unusually sluggish...i.e. when I tapped a menu, the response took a good 3 secs or even much longer on some menus...
I just did a hard reset and everything seemed to be fine (for now), but now I am concerned if this thing will happen again.
Has anyone experienced this before? Could any one please be so kind as to give me a short explantion?
BTW, this website is the coolest thing I have ever experienced in my 17 years of internet browsing. Simply the best!!

I have experienced similar warning msgs on the logs. I think they are pretty normal, but the ROMs work fine.
Abt the slow response - I had similar problems with my device initially. After lots of research, I found that the problem was the stk.lnk file in the startup folder. Once I removed this, all was fine.
The ROM kitchen does this for you now.
Also select "fix multiple reset bug .. " as well.
hope this helps

Ignore this warning. It just means the 4.x ROMs aren't in the database of known ROMs yet. Lazyness on our part...

sps: appreciate your kind reply and advises. Did all that ...actually ..
another small problem I just found when i turned on the unit, the xda started a soft reset automatically (i.e. i did not press the soft reset button at all). On another occasion, the unit went off as soon as the back light went off. (my battery was fully charged).
sorry if i asked too many small questions like this, but i wanted to know if anyone else experienced these and that if it is some bugs from WM2003 or something else. I don't mind with all these teething problems, as i always like to try new things. But I need some advises/ comments.
xda-developers : thank you for your prompt n effective explanation..
cheers..

Proximity Sensor Problem

Hi all,
Like many of us, I managed to kill a digitizer on my HTC Aria. Replaced the blasted thing, and now I find my proximity sensor is really sensitive. It's locked in proximity mode (Z-devicetest shows distance 0) in normal conditions.
If I pull off the digitizer, so the prox sensor has a clear path in front of it, it goes out of proximity state and Z-devicetest shows the distance as 1 (and the display works properly during calls, speakerphone works, etc) ...
If I slowly move the tip of my finger towards the prox. sensor, digitizer still removed, Z-devicetest shows it flip from 1 to 0 (out of prox to in prox) as my finger gets within ~2 inches.
So it seems the prox. sensor is working but is too sensitive.
Is this the normal failure mode of a CM3602 prox sensor (read: i dropped it, and not only broke the digizer, but took out the prox sensor too!) .. or, is there some sort of calibration i need to do?
Anyone have a USA source of the CM3602? My usual suppliers digikey and mouser don't carry this component..
*curses self* shoulda listened to my friend who warned me this phone is real easy to bust

There is a guy in the accessories board that is selling parts of his aria. I'd link ya but I don't know how from this app.
Sent from my Liberty using XDA App

Right on.
I didn't want to butcher this poor little POS more so I figured out how to turn the bloody sensor off in software.
append
gsm.proximity.enable=false
to /system/build.prop
or just uncomment the line if you have an editor.. but you can just cat >> build.prop in the shell and type in the line. No editor needed.
Must do this via adb shell with phone in clockwork, otherwise nand is lokt. boo. dev eng hardware doesn't have that problem... stupid consumer devices!

So do you just start Android sdk and then type the following.
append (enter)
gsm.proximity.enable=false (enter)
or is there more to it. I really need to get this disabled.

I tried to do it with ASTRO but it doesnt save my changes.

/system/build.prop is a standard text file.
Remember that stuff in /system is protected, I find the best way to deal with the /system partition is through clockworkmod recovery.
a. Disconnect USB, reboot into clockworkmod recovery
b. Mount the /system partition from the partitions menu
c. Connect USB to a system with adb
d. adb pull /system/build.prop
e. Edit file with your favorite text editor to append gsm.proximity.enable=false
f. adb push build.prop /system/build.prop
g. unmount /system from clockworkmod recovery partition menu
h. reboot phone, receive bacon
If you don't have clockworkmod recovery, just use unrevoked to install it

Oh, i should also say CM6 (and maybe all of Froyo images?) do not honor this setting.

Thank you I will try this when I get home..
I may have an issue because if I open build.prop with root explorer it says...
# try to disable proximity sensor in call by default
# gsm.proximity.enable=false
This is located almost at the bottom of the page does this mean I am sol. It is the liberated Rom and I haven't done anything to it.
Sent from my HTC Liberty using XDA App

Just remove the # ...
# gsm.proximity.enable=false
..to
gsm.proximity.enable=false

thank you so much..... you may be oh wait you are the FN man.
ok so if froyo images dont honor this does that mean when we get froyo I shouldn't upgrade.
anyway thank you so much now I can use my phone again, I didn't realize how much my Pure was dated till I had to use it for a few days.

Glad that helped
I didn't find a property in Froyo that disabled the proximity sensor. Maybe there is one, maybe there is not. I went another method..
Code:
# hexdump -C /system/lib/hw/sensors.liberty.so | grep -C3 dev/cm
00001b10 54 5f 54 46 4c 41 47 20 65 72 72 6f 72 20 28 25 |T_TFLAG error (%|
00001b20 73 29 00 45 43 53 5f 49 4f 43 54 4c 5f 41 50 50 |s).ECS_IOCTL_APP|
00001b30 5f 53 45 54 5f 4d 56 46 4c 41 47 20 65 72 72 6f |_SET_MVFLAG erro|
00001b40 72 20 28 25 73 29 00 2f 64 65 76 2f 63 6d 66 75 |r (%s)./dev/cmfu|
00001b50 6b 74 00 43 41 50 45 4c 4c 41 5f 43 4d 33 36 30 |kt.CAPELLA_CM360|
00001b60 32 5f 49 4f 43 54 4c 5f 45 4e 41 42 4c 45 20 65 |2_IOCTL_ENABLE e|
00001b70 72 72 6f 72 20 28 25 73 29 00 2f 64 65 76 2f 6c |rror (%s)./dev/l|
Offset 1b48 in /system/lib/hw/sensors.liberty.so defines the device name of the proximity sensor, normally /dev/cm3602.
Hexedit the file to change the name of the device to something that doesn't exist, and you will no longer use the proximity sensor.
Nasty and totally the wrong way to do this, but it worked for me. I suppose I could have dug through source code to check for a flag to disable the sensor, but that takes more time and is far less hacking fun than hex editing a system library If I didn't want to live dangerously I'd stick with the stock ROM lol.

Thanks again I will check back when group comes out if I can't figure it out. I am going to stick with the liberated Rom till we get the official Rom and it gets liberated.
Sent from my HTC Liberty using XDA App

Not a bad idea if you're happy with 2.1 and Sense

Yeah I really like the sense UI so I will stay with 2.1 until a 2.2 with sense is available.
Sent from my HTC Liberty using XDA App

Thanks for this info. Just changed CM3602 to XM3602 and it stopped.

I just upgraded to the new attn1 2.2 Rom with sense and I used the same fix you gave me for the 2.1 Rom and it worked so I guess that fix will work on all sence roms.
Sent from my HTC Liberty using XDA App

I just used hexeditor on my phone ( fr 2.2) and went to the location you noted 00001b48 but nothing there. I went on looking and found it on a few lines starting at 00002090. but which value do I change to get it to disable. If you could look at this for me it would help alot.

nrvate said:
/system/build.prop is a standard text file.
Remember that stuff in /system is protected, I find the best way to deal with the /system partition is through clockworkmod recovery.
a. Disconnect USB, reboot into clockworkmod recovery
b. Mount the /system partition from the partitions menu
c. Connect USB to a system with adb
d. adb pull /system/build.prop
e. Edit file with your favorite text editor to append gsm.proximity.enable=false
f. adb push build.prop /system/build.prop
g. unmount /system from clockworkmod recovery partition menu
h. reboot phone, receive bacon
If you don't have clockworkmod recovery, just use unrevoked to install it
Click to expand...
Click to collapse
I am trying to use these steps to disable the sensor, but I am having issues pulling build.prop.
In the command prompt, I enter in:
adb pull /system/build.prop c:\
And receive:
264 Kb/s (4695 bytes in .012s)
The issue I am having is that I cannot find where adb stores the file on my computer. It's not in the c:\ directory. It's not in platform-tools folder. I did a search, and nothing came up
Any suggests would be really appreciated.
Thanks!

I'm confused - why are you guys disabling the proximity sensor???
Is it because you improperly installed a new screen?
Might as well use duct tape to hold the new screen on and then JB Weld the back case. Seriously guys, do things right and take the screen back off and install it the right way.

kaschenberg,
I dropped my phone, shattering the screen; resulting in a lot of fractures in the glass where the sensor is located. The phone and screen works when I add pressure to the upper right corner, leaving me to believe the sensor is being interrupted by the fractures. I am hopeful, as a temporary fix, that if I can disable the sensor, the phone will work more optimally until I replace the screen.
- Thoughts?

Trying to get files from ftp server

Hello all
i'm trying to make a button that connects to an ftp server and download a bunch of files
i have everything figured out , but i'm wondering how to execute it , should i use asynctask ?
i want to also update progress and such ...
the files will be around 60MB so i don't know how long it will take , a few minutes i guess depends on the connection .
is there a more suitable answer than asynctask ?
thanks to all helpers !

I think asynctask would be a nice solution, progress updating is included as well (publishProgress(int progress) and then by overriding onProgressUpdate(...) you can access ui elements)
---------------------------------
Phone : Nexus 4
OS :
- KitKat 4.4.4 stock
- Xposed: 58(app_process); 54(bridge)
- SU: SuperSU
- no custom recovery
---------------------------------
4d 61 73 72 65 70 75 73 20 66 74 77
Gesendet von Tapatalk

TA Backup for G814x only

If someone interested, just try this small tool:
Run from cmdline (according to sample image), connect device in flash mode, and wait a bit.
*binary* comes from device directly, *config* is in infile format if you want to know what is inside.
No virus / other foreign legionary inside :
https://www.virustotal.com/#/file/8...f13e2099bc9b5a1ddb487ad41cb3948144d/detection
Works on G814x, may work on other devices, but not before (and including) Z5 Premium.

How to fix DRM on XZP:
Step one: Collect Underpants.
Step two: Backup TA.
Step three: Profit.
But seriously, good luck to all testing this. Please report back!

No matter how unstable or chancy this may be (haven't tested, don't wanna risk it haha) it''s progress in this right direction and to the idiots that gave up in the bounty thread, having patience can pay off

Its working. If you don't want to try, don't do that. This is not violence, this only an option To make a drm fix, this could be a step forward.
It's NOT write anything to the device, so safe to try. I have only one G8142, tested, read working fine. On weekend, I'll work on full/partial restore.
Anyway, its not for personal profit, I just want to speed up a complete lossless root solution

Just tested, files have been created, and phone is working without any problem.
Hope someone could get DRM fix soon or at least a point to start with this tool.
Thanks a lot for the effort

Mine just hangs on Checking S1 devices
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Edit: Sorry Didn't read the part that need to connect FLASH MODE It backed up stuff.

does it work with sony xz1 or should wait for next update

karrouma said:
does it work with sony xz1 or should wait for next update
Click to expand...
Click to collapse
You can test is. It cannot write anything, at most cannot read anything.
BTW, this is NOT A RAW TA BACKUP, it backup what the phone give us. But I hope it contains any DRM related stuff
I hope someone will try it out who can understand what it read out, and can give us some feedback.
Anyway, unlocked my one, I love new green shots, but now I can attack from another way too. Looks like dd raw backup
a bit bigger, even its not fully filled

Very good work. It's because people like you that things get done.

HELLO !!! @Macs1209 PERFECT WORK BRO !!!
MY PHONE IS G8141 with windows 7 x64
E:\SONY\XPERIA XZ PREMIUM>dmsSonyTABackup.exe
Checking S1 devices
S1 interface found: \\?\USB#VID_0FCE&PID_B00B#5&1dd2df13&0&2#{a5dcbf10-6530-11d2
-901f-00c04fb951ed}
TA1 binary read ok, size: 139096, saved to E:\SONY\XPERIA XZ PREMIUM\MY IMEI_TA_1.binary.tab
- TA binary parsed, saved to E:\SONY\XPERIA XZ PREMIUM\MY IMEI_TA_1.confi
g.tab
TA2 binary read ok, size: 179230, saved to E:\SONY\XPERIA XZ PREMIUM\MY IMEI_TA_2.binary.tab
- TA binary parsed, saved to E:\SONY\XPERIA XZ PREMIUM\MY IMEI_TA_2.confi
g.tab
THANK YOU VERY VERY SO MUCH GOOD WORK
ps it 's possible change in TA.img or add restore ?
please help bro @munjeni

LukeyWolf said:
No matter how unstable or chancy this may be (haven't tested, don't wanna risk it haha) it''s progress in this right direction and to the idiots that gave up in the bounty thread, having patience can pay off
Click to expand...
Click to collapse
There's a quote in Urdu "sabar ka phal meetha hota he" means that the fruit of patience is always sweet.
kudos to this guy. since S8 Snapdragon 835 version is now rooted. i hope we can get Root and Drm keys together sooner on our XZP

Saadkhalid786 said:
There's a quote in Urdu "sabar ka phal meetha hota he" means that the fruit of patience is always sweet.
kudos to this guy. since S8 Snapdragon 835 version is now rooted. i hope we can get Root and Drm keys together sooner on our XZP
Click to expand...
Click to collapse
Yep, a grest step in the correct direction, also I have to wait anyway haha as I only got my XZP 1 month ago with EE locked haha

I can help reconstruct real TA.img!
Edit:
This tool doesn't backup drm key, I didn't see unit 66667. Without shake authentification I'm believing you can't backup secured units including that drm key unit. I'm still believing that drm key or unlock key is outside trim area, I even didn't see unit 0x8b2 from unlocked device trim area. https://github.com/munjeni/newflasher , can you show your's?
@the_laser , how that is possible that his tool reads some units like:
Code:
[67320]
size=2
data=9A 02
text=
[67321]
size=2
data=FA 01
text=
[67322]
size=2
data=3A 01
text=:
[67323]
size=2
data=1A 01
text=

This works on XZ1 Compact.
It produced 4 files:
[IMEI]_TA_1.binary.tab (146036 bytes)
[IMEI]_TA_1.config.tab (Text display of above)
[IMEI]_TA_2.binary.tab (183728 bytes)
[IMEI]_TA_2.config.tab (Text display of above)
EDIT: For reference, the XZ1c's TA partition is 2MB, so this tool is pulling < 1/4th of that partition.
I don't see 66667 or 8B2 either.

Thanks for responses. So now I need to focus on 66667 abnd 0x8B2.
BTW, "text=" lines for info only, to see is there any text inside, like imei, any sw part version, or log data.
Another question: is there any way to create a modem interface for this device? In the modem firmware part, there's
lot of AT commands, but without interface, I can't communicate with the baseband. On Samsung qualcomm devices,
I could reach lot of things via modem, same logs what are in the partial TA backup binaries. (also I killed one exynos
g925f by wrote something wrong to RF calibration.... )

pbarrette said:
This works on XZ1 Compact.
It produced 4 files:
[IMEI]_TA_1.binary.tab (146036 bytes)
[IMEI]_TA_1.config.tab (Text display of above)
[IMEI]_TA_2.binary.tab (183728 bytes)
[IMEI]_TA_2.config.tab (Text display of above)
EDIT: For reference, the XZ1c's TA partition is 2MB, so this tool is pulling < 1/4th of that partition.
I don't see 66667 or 8B2 either.
Click to expand...
Click to collapse
The tool didn't find my XZ1c, tough I probably need some special drivers that I missed.

Those files are s1 dump for Sony repair services
That provide device info, last Boot logs, installed firmware versions, baseband info, etc
Small parts of TA nothing important

pbarrette said:
This works on XZ1 Compact.
It produced 4 files:
[IMEI]_TA_1.binary.tab (146036 bytes)
[IMEI]_TA_1.config.tab (Text display of above)
[IMEI]_TA_2.binary.tab (183728 bytes)
[IMEI]_TA_2.config.tab (Text display of above)
EDIT: For reference, the XZ1c's TA partition is 2MB, so this tool is pulling < 1/4th of that partition.
I don't see 66667 or 8B2 either.
Click to expand...
Click to collapse
@Macs1209
it is wirking in xz1 also
i got same 4 files
xzp xzc xz1 same drm and same oreo firmware family like xz and xzs

pbarrette said:
EDIT: For reference, the XZ1c's TA partition is 2MB, so this tool is pulling < 1/4th of that partition.
Click to expand...
Click to collapse
Yes partition is 2mb but that not mean that it have 2mb of the data inside! So thats expected.
---------- Post added at 09:39 AM ---------- Previous post was at 09:38 AM ----------
munjeni said:
https://github.com/munjeni/newflasher , can you show your's?
Click to expand...
Click to collapse
Macs1209 said:
Another question: is there any way to create a modem interface for this device?
Click to expand...
Click to collapse
Yes, but waiting your reaply to my question first.

munjeni said:
Yes partition is 2mb but that not mean that it have 2mb of the data inside! So thats expected.
---------- Post added at 09:39 AM ---------- Previous post was at 09:38 AM ----------
Yes, but waiting your reaply to my question first.
Click to expand...
Click to collapse
Code:
Checking S1 devices
S1 interface found: \\?\USB#VID_0FCE&PID_B00B#6&f44bfc6&0&4#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
Response(BIN): SUCCESS: 104857600
Response(HEX): SUCCESS: 31 30 34 38 35 37 36 30 30
Reading TA 1 / 2226
Response(BIN): FAILED: Unable to read TA unit 2226, error=-22
Response(HEX): FAILED: 55 6E 61 62 6C 65 20 74 6F 20 72 65 61 64 20 54 41 20 75 6E 69 74 20 32 32 32 36 2C 20 65 72 72 6F 72 3D 2D 32 32
Reading TA 2 / 2226
Response(BIN): FAILED: Unable to read TA unit 2226, error=-22
Response(HEX): FAILED: 55 6E 61 62 6C 65 20 74 6F 20 72 65 61 64 20 54 41 20 75 6E 69 74 20 32 32 32 36 2C 20 65 72 72 6F 72 3D 2D 32 32
Reading TA 1 / 66667
Response(BIN): FAILED: Unable to read TA unit 66667, error=-22
Response(HEX): FAILED: 55 6E 61 62 6C 65 20 74 6F 20 72 65 61 64 20 54 41 20 75 6E 69 74 20 36 36 36 36 37 2C 20 65 72 72 6F 72 3D 2D 32 32
Reading TA 2 / 66667
Response(BIN): FAILED: Command not authenticated
Response(HEX): FAILED: 43 6F 6D 6D 61 6E 64 20 6E 6F 74 20 61 75 74 68 65 6E 74 69 63 61 74 65 64
Done
Sadly not. 2/66667 looks like needs some authentication, but after it possible to read
(I already unlocked this device, so error-22 can mean TA ID not exists (anymore) too)

LG G4 v29a magisk + safetynet pass + debloat + adaway - Howto guide

Hey guys.
I am using magisk 15.3 to debloat the v29a system systemlessly.
Systemless Debloat with the magisk module (terminal debloater) means that the system partition isn't touched!
Hence, it don't breaks safetynet (also with the help of Universal safetynet fix beta 5).
Requirements:
BL unlocked
TWRP installed, up and running
Here is a short how to guide:
When you already on v29a and you have modify the system partition (adaway, supersu, TiBu,...) just flash the stock v29a system partition again and don't touch it (no supersu, no adaway,...)!
Here is the link: https://forum.xda-developers.com/g4/development/h815-nougat-stock-t3659860
Flash magisk 15.3 in TWRP and boot up.
Here is the Link: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Go into magisk manager and check safetynet status. In my case cts profile fails. No problem...
Go into twrp and flash the universal safetynet beta 5 fix. DONT USE the stable, use the BETA!
Here is the link: https://forum.xda-developers.com/apps/magisk/xiaomi-safetynet-fix-t3600431
Restart phone and check safetynet status. It should pass booth checks.
Now you are rooted and pass safetynet. You can install and use Netflix, Super Mario Run, banking apps... victory
To get adaway working and not breaking safetynet, open it, go to settings and set the hosts file location to /data/. Press update/install hosts file. Adaway will ask you to create a symlink on system. Do it, this will not break safetynet!
From magisk manager you can install "terminal debloater" and use my list to Debloat the rom without breaking safetynet.
Here is the List:
1 - Google Play Books
2 - DRM Service
3 - Docs
4 - Sheets
5 - Slides
6 - GNSS Air Test
7 - gnsslogcat
8 - LG GNSS 2.1
9 - GnssTest 1.2
10 - Google Text-to-speech Engine
11 - HTML Viewer
12 - Hangouts
13 - Hidden Menu
14 - HiddenSIMUnlockMenu
15 - LG Account
16 - LGAirDrive
17 - LG Backup Launcher
18 - LGDrm
19 - FOTA Update
20 - Audio share
21 - LGSmartcardService
22 - Smart cleaning
23 - LGWernickeManager
24 - LteConfigs
25 - Google Play Newsstand
26 - PacProcessor
27 - Google Play Games
28 - Google+
29 - Print Spooler
30 - Use DLNA feature
31 - SmartShareProvider
32 - Google Play Movies
33 - Wfd Service
34 - atfwd
35 - ELTest
36 - ServiceMenu
37 - TalkBack
38 - BackupRestoreConfirmation
39 - LG Health Agent
40 - Cloud
41 - Battery drain info
42 - GCUV
43 - Game battery saver
44 - IceContacts
45 - InCalAgent
46 - LG AirDrive
47 - Clock
48 - App Updates
49 - LG Mobile Switch
50 - Internet
51 - Calculator
52 - Calendar
53 - Cell Broadcast
54 - Smart Notice
55 - Contacts
56 - LGSmartCover
57 - Software update
58 - Email
59 - Exchange
60 - File Manager
61 - FormManager
62 - Answer me
63 - LGInstallService
64 - LDB
65 - LGMapUI
66 - Messaging
67 - Music
68 - Music
69 - LG P2p Service
70 - LG Bridge Service
71 - LGPartnerBookmarksProvider
72 - LG RCS Services
73 - RcsCall
74 - SharedSketch
75 - SnapPage
76 - Tasks storage
77 - Update Center
78 - Voice Recorder
79 - LG WFDS Services
80 - LIA Informant
81 - LIA S4URecommender
82 - LG Connectivity Service
83 - My Places Engine
84 - My Place
85 - RCSProvider
86 - SmartSetting
87 - Tags
88 - qcrilmsgtunnel
Click to expand...
Click to collapse
Now you are rooted, have adaway, pass safetynet & debloated all the LG s*** out of this rom.
Go to the magisk manager download section and find other great systemless mods
THX goes to:
@twrp team and @steadfasterX for TWRWP
@kessaras for v29a flashable zip
@Deic for universal safetynet fix beta 5
All the others I forgot.
pOpY

What does the author of this thread mean by "systemless debloat"?
Isn't just disabling/freezing apps enough?
Also, how can you pass safetyNet? I cannot pass it even with safetyNet Universal fix...

Reserved

So, there is no way to pass Safety net with roms like H-rom g4 or even worse, Los, right?

polfrank said:
So, there is no way to pass Safety net with roms like H-rom g4 or even worse, Los, right?
Click to expand...
Click to collapse
Sorry, i havent installed the roms and just done this on v29a stock.
Have updated the Op with better instructions on how i have done it.
Would be nice if you could try it and report back.
pOpY

polfrank said:
So, there is no way to pass Safety net with roms like H-rom g4 or even worse, Los, right?
Click to expand...
Click to collapse
I was passing Safety net back on the last Official LOS 14.1 using at the time 15.0 Magisk, universal safety fix and magisk hide. I don't remember all the settings, Now I am on CypherOS and still passing with 15.3 and universal. I mod and change my /system all the time and pass.
What is your setup? Maybe with more information I can help.
Edit: also nice post OP. I'll probably be installing Adaway soon, just never bothered. Also for the terminal debloater, what exactly does that do? Just hide the apps? I mainly just use the TWRP terminal and remove apps from /system that way, but I leave some that I am unsure if they are needed or not. Do you know which ones are always required?

Thx, for your kind words.
Adaway is a must have [emoji3]
No ads, yeah.
Regarding the terminal debloater module, it removes the apk and write a placeholder file. The result is the same like you do (remove the apk), BUT you can disable the whole module or enable single apps and system partition isn't touched!
The list above I have written down from several threads and by trial and error.
Until now, no issues...
Wait... One.. Better battery life [emoji56]
pOpY
Gesendet von meinem LG-H815 mit Tapatalk

popy2006 said:
Thx, for your kind words.
Adaway is a must have [emoji3]
No ads, yeah.
Regarding the terminal debloater module, it removes the apk and write a placeholder file. The result is the same like you do (remove the apk), BUT you can disable the whole module or enable single apps and system partition isn't touched!
The list above I have written down from several threads and by trial and error.
Until now, no issues...
Wait... One.. Better battery life [emoji56]
pOpY
Gesendet von meinem LG-H815 mit Tapatalk
Click to expand...
Click to collapse
Thats pretty cool. I may check it out soon. I'm trying to not to use a lot of Magisk modules on such a new rom (CypherOS 5.1) to be sure everything works. But better battery life is my aim right now. Thanks for the explanation.

tambukey said:
Thats pretty cool. I may check it out soon. I'm trying to not to use a lot of Magisk modules on such a new rom (CypherOS 5.1) to be sure everything works. But better battery life is my aim right now. Thanks for the explanation.
Click to expand...
Click to collapse
You are welcome

Final step, OPEN Terminal Emulator and type:
su
debloat
^^the app list to debloat (in OP) are found in both options #1 and #2
One note: Print Spooler is necessary if you plan to print any documents/pictures onto paper from a printer.
Thanks for the guide!!

Guys I can't run Magisk on my LG G4 H815 with Nougat v29a. After removing Supersu and flashing magisk 17.1 with twrp, the phone doesn't boot normally. It reboots recovery when I click reboot system. It always reboot recovery. I don't know why.
Do you have any Idea?

Use magisk 16.0, that's the version I am using. With 17 and 17.1 I also had those issues.
Good luck
pOpY
Gesendet von meinem LG-H815 mit Tapatalk