Database Info

[Development]Kernel

Hei there.
The idea of this thread is to develop a better kernel for the I9001 in the community. I have compiled my own one for using it in the cwm recovery mod. I've only changed the following so far:
Patched pm2.c file in the samsung kernel sources, see here for the patch:
https://github.com/PabloPL/android_...mmit/46e96915a7e0459dc6b3aec04aa47329371fff44
through menuconfig I've changed the default cpu governor from performance to ondemand.
What we should implement first is init.d support.
I've uploaded my boot.img file for further use here:
http://www.mediafire.com/?6p91s5knka0e0py
It also contains the CWM Recovery

This is great idea bro. Its great to have you here.
Thanks again!!!
Sent from my GT-I9001 using Tapatalk

I would love to see a overclock able kernel! Great idea!
Joost
Sent from my GT-I9001 using XDA App

overclocking module
Hi guys,
coolbho3000 posted source of an overclocking module for HTC Vision. As far I know, it can be used with the SetCPU App together.
http://forum.xda-developers.com/showthread.php?t=813681
Since S+ has a similar Qualcomm chip, it should work as well.
I compiled the overclocking module with the S+ Kernel and packed it into the zImage. The device doesn't boot. Maybe it would be better to follow what coolbho3000 says and adapt the settings
ädu
PS: it needs definitively some adaptions.

Shouldn't we create our own github/bitbucket repositories for kernel and CWM? I'm trying to get my feet wet in generic Android kernel development now, it would be cool to have repository to sync with.

YardE said:
Shouldn't we create our own github/bitbucket repositories for kernel and CWM? I'm trying to get my feet wet in generic Android kernel development now, it would be cool to have repository to sync with.
Click to expand...
Click to collapse
yep of course. I've already opened an account on github. But right now I ain't got time to read the instructions on how to upload repos because I'm busy with applying some changes to FeaMod Recovery and testing them.
I would be happy if a lot of kernel developers would join us!
Edit: The sources for FeaMod recovery 1.1 are on github:
https://github.com/manveru0/FeaMod-Recovery--based-on-CWM-Recovery-
Samsung kernel sources with patched pm2.c:
https://github.com/manveru0/kernel_I9001_samsung

Later I'll try to add "run-parts /system/etc/init.d/" to init.rc, but I'm highly confused from examining ramdisk, because I couldn't find any bash-scripts interpreter (possibly embedded into init executable?) and don't have enough time to continue examining init.rc now. I think, we can add busybox to system image and call it from there. Also, please, modify these lines in default.prop in your future builds:
Code:
ro.secure=0
ro.debuggable=1
As far as I understood, these allow us to use "adb root".
Also, thanks for your awesome work!

YardE said:
Later I'll try to add "run-parts /system/etc/init.d/" to init.rc, but I'm highly confused from examining ramdisk, because I couldn't find any bash-scripts interpreter (possibly embedded into init executable?) and don't have enough time to continue examining init.rc now. I think, we can add busybox to system image and call it from there. Also, please, modify these lines in default.prop in your future builds:
Code:
ro.secure=0
ro.debuggable=1
As far as I understood, these allow us to use "adb root".
Also, thanks for your awesome work!
Click to expand...
Click to collapse
sounds good. I haven't seen a script interpreter either and I'm not quite sure if there is one included in the init. I think it's better we include busybox. Take a look at this thread by the way:
http://forum.xda-developers.com/showthread.php?t=1152740
I'll try to do that testwise.
Here's the adress for my uploaded boot.img-ramdisk without the samsung pictures (we can easily add them again when building a new boot.img):
https://github.com/manveru0/bootimage_ramdisk_I9001
I've already included the changes in default.prop
EDIT: some useful links
http://www.kandroid.org/online-pdk/guide/bring_up.html
http://www.androidenea.com/2009/08/init-process-and-initrc.html

After some init.rd learning I've inserted a service here which should get the job's done, but I have no idea how to test it. Anyway, here is the diff from the normal one:
Code:
[[email protected] boot]$ diff -u3 init.rc ../boot_mod/init.rc
--- init.rc 2011-11-05 22:35:33.194680288 +0400
+++ ../boot_mod/init.rc 2011-11-05 22:24:40.000000000 +0400
@@ -566,7 +566,7 @@
# ihryu 2010.07.19
setprop ro.rfkilldisabled 0
- class_start default
+ #class_start default
# +++++++++++++++++++++++++++++++++++++++++++
# for silent reset
@@ -714,6 +714,10 @@
onrestart restart netd
onrestart restart sensor-daemon
+service initd /system/bin/logwrapper /system/xbin/busybox run-parts /system/etc/init.d
+ oneshot
+
service media /system/bin/mediaserver
user media
group system audio camera graphics inet net_bt net_bt_admin net_raw radio qcom_oncrpc
[[email protected] boot]$
Have also commented "class_start default" which runs twice for some reason. To have this working in theory, you should have busybox installed in /system/xbin with run-parts support. For me, it boots at least ^_^
P.S. It also works if I call command line from adb. Also, adb root works after changing default.prop, good.
P.P.S. You can also remove "charging.rle" from repo, as it is image, too, but why not just keep all the files in repo? git is loyal to binary files as long as you don't try to create a patch. ~_^ Also, you can use .gitignore to exclude some files from git's view at all.

Found excellent reference on init.rd:
http://www.kandroid.org/online-pdk/guide/bring_up.html
Fixed previous post (removed "disabled"), so it should really work now. Going to test it, but not really sure if my test are correct (I'll try to write something to sdcard, but is it mounted r/w at the moment of script running?)
Test failed, thinking of some other, more accurate tests now.
Tried to create file in /cache, and it worked! Here is boot.img with working init.rd and adb root. Flash it via dd (dd if=boot.img of=/dev/block/mmcblk0p8). You should have busybox installed into /system/xbin for this to work.

YardE said:
Found excellent reference on init.rd:
http://www.kandroid.org/online-pdk/guide/bring_up.html
Fixed previous post (removed "disabled"), so it should really work now. Going to test it, but not really sure if my test are correct (I'll try to write something to sdcard, but is it mounted r/w at the moment of script running?)
Test failed, thinking of some other, more accurate tests now.
Click to expand...
Click to collapse
thx for your commit, I'm testing it as well with the adrenaline shot. If init.d support works you should see the changed values.
I do have a working busybox in /system/xbin with run-parts support, so that shouldn't be the issue as my tests didn't work so far.
Okay, gonna delete disable as well.
concerning the images i wasn't so sure about law problems since they include original samsung stuff.
update:
success You did it! Init support works. Though I have to retest it since I've also added user root to the init.rc. Honestly I'm not quite sure if that entry is needed

"user root" is not needed since user is root by default, already tested without it (edited my posts above).

YardE said:
"user root" is not needed since user is root by default, already tested without it (edited my posts above).
Click to expand...
Click to collapse
okay then, i will change the init.rc file and commit it to github. I will name you in the comment to the change. Which name should I use? Is that okay for you?

Oh, you can use either "abbradar" or "YardE", I don't mind. ^_^ Thank you for credits and again for your work. Gonna experiment a bit with CWM now since init.d is working.

YardE said:
Oh, you can use either "abbradar" or "YardE", I don't mind. ^_^ Thank you for credits and again for your work. Gonna experiment a bit with CWM now since init.d is working.
Click to expand...
Click to collapse
I have to thank you for your work as well, mate It's cool working as a team since we are better, faster and should see more bugs than working alone
Edit:
Hmm, we should include busybox in the boot ramdisk, since not every user has busybox installed.
P.S: funny thing is, I've installed adrenaline shotv13 but only part of it works. For example the sdcard tweak works, the sysctl tweaks don't.
P.P.S: i've installed bash on my device, it's much more easier with it to navigate in the adb shell

manveru0 said:
Hmm, we should include busybox in the boot ramdisk, since not every user has busybox installed.
Click to expand...
Click to collapse
What is the max size limit in our device for ramdisk? Also, should we really do so? It will be hard to update in comparison and maybe will be stripped due to size limit, and users basically'll have two versions of busybox - our embedded into boot.img and their own - in /system. (I'm looking on CM and other init.d implementations as an example) But on the other hand, it is really nearly critical level app (although sh is not in boot.img, for example)
P.S: funny thing is, I've installed adrenaline shotv13 but only part of it works. For example the sdcard tweak works, the sysctl tweaks don
Click to expand...
Click to collapse
They also trying to write some values into non-existent /sys nodes, looks like they are meant for other kernel scheduler, like BFQ (should we also try it?)
---------- Post added at 01:25 AM ---------- Previous post was at 01:25 AM ----------
P.P.S: i've installed bash on my device, it's much more easier with it to navigate in the adb shell
Click to expand...
Click to collapse
Good advice, thank you ^_^.

YardE said:
What is the max size limit in our device for ramdisk? Also, should we really do so? It will be hard to update in comparison and maybe will be stripped due to size limit, and users basically'll have two versions of busybox - our embedded into boot.img and their own - in /system. (I'm looking on CM and other init.d implementations as an example) But on the other hand, it is really nearly critical level app (although sh is not in boot.img, for example)
They also trying to write some values into non-existent /sys nodes, looks like they are meant for other kernel scheduler, like BFQ (should we also try it?)
---------- Post added at 01:25 AM ---------- Previous post was at 01:25 AM ----------
Good advice, thank you ^_^.
Click to expand...
Click to collapse
the maximum size of both recovery and boot.img is 7864320 Bytes. Riversource once found that out. It's also in the BoardConfig.mk So we would have enough space for including busybox. But you're right, it would only lead to 2 busyboxes on the device which is not the best idea.
CM uses the BFQ scheduler as far as I know so yeah, we should give it a try

AFAIK, BFS patch nearly fully removes original kernel schedulers, so some work of comparing with original Linux kernel will be needed to do. Although, it may not be true for Android kernel sources or my experience may be wrong, so we should just try it as is before continuing.
Sent from my GT-I9001 using XDA App

YardE said:
AFAIK, BFS patch nearly fully removes original kernel schedulers, so some work of comparing with original Linux kernel will be needed to do. Although, it may not be true for Android kernel sources or my experience may be wrong, so we should just try it as is before continuing.
Sent from my GT-I9001 using XDA App
Click to expand...
Click to collapse
yep, I've looked at the changes the patches make and they remove alot of the CFQ related functions. Fortunately the makefile is patched as well so no work here.
I've have downloaded the patches for kernel 2.6.35 here:
http://algo.ing.unimo.it/people/paolo/disk_sched/sources.php
I applied them to my sources, compiled em and flashed my FeaMod pack with the new kernel and your changes to the boot ramdisk.
So far everything is working on my device I'm gonna upload the patches to github.
Edit: Had to change the .config as well since bfq is not the default I/O scheduler. It is now, I've also activated the hierarchical scheduler support.

Concerning ramdisk git repo: maybe we should move all the code into some folder, for example, "ramdisk", and move README out from there to avoid it being placed into final image? Also, we should point which files are missing from ramdisk in README.

[STOPPED][ROM ICS 15 Jul] slim rom for Desire [based on Sandvold .15 & K900 build 40]

[STOPPED][ROM ICS 15 Jul] slim rom for Desire [based on Sandvold .15 & K900 build 40]
These are a simple slim version of the original ICS ported rom for htc desire (aka bravo) provided by Sandvold and K900
Of course all credits must go to Sandvold & K900, I'm not a developer, simply I needed a lighter rom and due to many requests I decided to share my (small) work and dedicate to it a thread
They work just as original rom, I haven't changed a single bit, just removed all stuffs that can be downloaded later from google play (aka PhoneSky.apk). This thread is intended for "advanced users" but none can't stop you to make experiments
These rom are intended to work with cm7r2 hboot table & without the need of any ext3-4 partition (this means max 120-130 app)
IMPORTANT: as a2sd script we use as default for both roms 69a2sd script, more info here
CHANGELOG (15 Jul) :
- updated 98mydesireI script (modded minfree memory management)
- updated default Apex Launcher (anyway you can use whatever you prefer)
- updated OS fonts, I choose a ligther & smoother one
- Download here or Mirror here
CHANGELOG (06 Jul) :
- updated 98mydesireI script (reduced boot pause, it will stay only upon a fresh installation)
- updated MultiLing keyboard
- updated Music apk with JB release (moved backup to /system)
- moved LauncherApex from /system to /data (make an apex setting/icon backup before flash, you have to replace widget too)
CHANGELOG (04 Jul) :
- upgraded Sandolvd based ics rom (.15)
Some notes before starting:
before start I strongly suggest, if you are under MS Windows environment, to download the mini-sdk-android-windows.zip (look at 2nd post for details) from repository (aka known as diaduit), unzip the entire folder, without renaming it, where you prefer under your C: drive, this little zip contains some utilities and batch scripts to automate some recurrent actions useful to easily manage your device, such as for example radio flash, hboot flash, script injection, etc...
these slim rom will fit on cm7r2 partition table, if you don't know what is it you can start from alpharev.nl website, or simply download your .img copy from repository
I strongly suggest to use a modern and full functionally recovery, personally I use 4EXT: download from repository and flash trough _flash_recovery.bat batch script (from mini-sdk-android-windows.zip)
always in repository you can find a copy of the slim rom (named as rom-slim-etc...zip)
editing directly rom-slim-desireics-xyz_x.y.zip requires winrar (search in google)
this rom can work without any ext3-4 additional partition, I just move into sd-card ALL the games and not fundamental apps using default android behavior: Settings => Applications => Sd-card (tap correspondent app to move)
as a2sd script we use as default for both roms 69a2sd script, more info here
and now rom modded content:
removed all google applications (*) downloadable from google-play except QuickSearch and Vending (google-play app)
removed all tts lang (except for the service), they can be downloaded later from google-play because I suppose that own language should be enough for most of us
removed almost all sounds except one for alarm, one for ring and six for notifications, anyway you can create your own sounds repository in your sd-card, so you wont loose them never more: make a folder in your sd-card named /media/audio, then create under audio other 3 folders named: alarms, notifications, ringtones , then put your personal sounds under correspondent folders
removed default ics keyboard, the 1st reason because it's heavy and fat, the 2nd because has ton of languages when we really need just one... our own (I included as default MultiLing free keyboard, a light and highly configurable keyboard with downloadable single dictionary)
removed all customization and stock kernel is provided (eventually Tiamat kernel can be flashed separately), of course customization are included with best options/balance about my experience/opinion
default launcher is Apex Launcher
added 98mydesireI script (present under extra folder of mini-sdk-android-windows.zip), you can edit it as you prefer (use for this purpose pspad editor due to its ability to manipulate unix txt files), as default its primary goal is to manage cpu freq between sleep and awake states (245-245 when sleep, 960-1075when awake)
auto-adjust swap tuning (swappiness= 20 if zRam enabled, 0 if not)
installation instructions, starting from the beginning:
make a full backup before start, personally I don't use titanium due to its restoring issues probabilities, I prefer a full backup from recovery, for this purpose 4EXT is just perfect (from repository), it will backup eventually your ext3-4 partition too
download and copy rom-slim-desireics-xyz_x.y.zip file in your sd-card
if you don't have cm7r2 hboot you should upgrade to cm7r2, download the .img file from repository and use _flash_hboot.bat batch script (from mini-sdk-android-windows.zip) to easily flash the new hboot
reboot your device into recovery, pay attention that if you changed hboot table, for example from data+ to cm7r2, you have to force a full wipe (do it from recovery itself)
after rom flash & upon complete boot SetupWizard wont start (I removed it) so as 1st step I suggest you to configure a working wlan, then launch google-play and start registering your existing account...
download & configure all apps you intend to use (hint: search google inc to find all google stuffs such as maps, gmail, youtube, etc...)
post installation guide, another important step:
if you come from an upgrade/reflash remember that installer will format only /system folder, some previous related system app will still be under /data/app such as for example LatinIME.apk, so if you keep MultiLing keyboard (or whatever) remove from /app/data the LatinIME.apk (edit and use _remove batch script)
go under Settings => Evervol Toolbox => Performance => Memory management and activate "kernel samepage merging" (do not activate zRam, our device has enough ram and also because I noticed random FC under heavy usage)
as you know some video from gallery (using internal libs) are rendered badly, install instead MXPlayer (from google-play) and force it to use SW rendering (from MXPlayer settings)
removed almost all sounds except one for alarm, one for ring and six for notifications, anyway you can create your own sounds repository in your sd-card, so you wont loose them never more: make a folder in your sd-card named /media/audio, then create under audio other 3 folders named: alarms, notifications, ringtones , then put your personal sounds under correspondent folders
added 98mydesireI script, you can edit it as you prefer (use for this purpose pspad editor), as default its primary goal is to manage cpu freq between sleep and awake states (245-245 when sleep, 960-1075 when awake)
Other tips (I'll add step by step as I remember):
prevent unnecessary battery drainage by disabling auto-time update... device keeps date/time sync with connected cell tower every minute! (disable from Settings => Date & Time) and install instead ClockSync from google-play (setup auto-update every 3 days)
move ALL games or spare used app from nand to sd-card (Settings => Application => SD-card => tap on move able app)
to speed-up open/close phase disable animation from Settings => Developer options => Scale from 1x to 0,5x (or none)
(*) App list installed as default on /system:
Code:
ApplicationsProvider.apk
BackupRestoreConfirmation.apk
Bluetooth.apk
Browser.apk
Calendar.apk
CalendarProvider.apk
Camera.apk
CertInstaller.apk
Contacts.apk
ContactsProvider.apk
DefaultContainerService.apk
DeskClock.apk
DownloadProvider.apk
DownloadProviderUi.apk
DrmProvider.apk
EVToolbox.apk
EVWidgets.apk
Email.apk
Exchange.apk
Gallery2.apk
GenieWidget.apk
GoogleBackupTransport.apk
GoogleCalendarSyncAdapter.apk
GoogleContactsSyncAdapter.apk
GoogleLoginService.apk
GooglePackageVerifier.apk
GooglePackageVerifierUpdater.apk
GoogleQuickSearchBox.apk
GoogleServicesFramework.apk
GoogleTTS.apk
HTMLViewer.apk
KeyChain.apk
LauncherApex.apk
MarketUpdater.apk
MediaProvider.apk
MediaUploader.apk
Mms.apk
Music.apk
MusicFX.apk
NetworkLocation.apk
PackageInstaller.apk
Phone.apk
PicoTts.apk
Provision.apk
Settings.apk
SettingsProvider.apk
SharedStorageBackup.apk
SoundRecorder.apk
Stk.apk
Superuser.apk
SystemUI.apk
Talk.apk
TelephonyProvider.apk
UserDictionaryProvider.apk
Vending.apk
VoiceCommand.apk
VoiceSearch.apk
WAPPushManager.apk
df output on fresh installation:
Code:
Filesystem Size Used Free
/dev 202M 32K 202M
/mnt/asec 202M 0K 202M
/mnt/obb 202M 0K 202M
/system 145M 141M 3M
/data 287M 1M 285M
/cache 5M 784K 4M
screenshots below plus videos here 1/3 (installing) - 2/3 (average usage test) - 3/3 (game test)

mini-android-sdk-windows dedicated post
As explained few lines above this small zip downloadable from repository contains some batch scripts useful to automatize frequent operations, such as flashing radio, hboot, inject scripts, splash screen, etc...
simply unzip it on your physical hard drive ( C: ) in the folder you prefer, rename adb.ba_ as adb.bat, then move adb.bat under c:\windows folder, this to help you in recalling adb environment* (Start > adb > Run and it will open the folder plus a ready cmd shell)
*tested under Vista and 7, remember also if you intend to use adbWireless to edit IP.bat batch file and change IP (up 3) addresses matching the one of your device (useful for adbWireless)
let's take a tour on its content:
IP.bat => simple IP file configuration, write here your device IP list for connecting trough adbWireless (of course if you use it)
_flash_hboot.bat => this will flash hboot table, simply connect your device (without reboot in anything, just attach it) and provide in the same folder the hboot .img file named hboot.img (remember if you change hboot table to wipe before flash anything else)
_flash_radio.bat => as above but for radio, provide radio.img in the same folder, pay attention that radio flashing is really dangerous because in case of fault you'll probably brick your device, anyway latest radio provided for our device (on XDA or repository) is perfect so you shouldn't need to change it
_flash_recovery.bat => as above but for recovery, personally I use 4EXT (version 2.1.3 is faultless, download a copy from repository)
_flash_splash.bat => this is intended for flashing .bmp as splash screen (different from boot-animation, this is the 1st thing you see upon turn-on), provide splash1.bmp in the same folder ([email protected])
_push_98* => init script for control cpu freq (pay attention different version for different hardware, latest version already included in the slim rom)
_push_build.prop.bat => this will inject your personalized build.prop in your device (provide the file under extra folder)
_push_gps.conf.bat => as above, anyway the modded version is yet included in the slim rom
_push_hosts.bat => as above
_push_to_sdcard.abt => this batch script will copy under sd-card your drag'n dropped file (I use in conjunction with adbWireless)
_remove_stuff.bat => use this batch script with care, edit it to add removing actions
note: all .img file go under current folder, while all "extra" such as hosts, build.prop and init script go under extra folder

98mydesireI script dedicated post
1st part are just personal mods, you can keep, mod or remove, but the core of the script is the 2nd part, where the script itself creates a mini script named mycpu under /etc and will detach it in background (nohup /system/bin/sh /system/etc/mycpu&)
so in few words:
98mydesireI init script will be executed after complete boot (90 sec)
98mydesireI init script will write under /etc another script named mycpu (for managing cpu freq)
98mydesireI init script before exiting will launch mycpu control script
mycpu control script will stay in background looking for device state (sleep or wake) and applying relative properties
the annoying problem having a high cpu freq jump, for example from 245 to 1113 also with interactive/smartass governors, is that when your device wake up or when you don't put your fingers on it becomes a bit sluggish for a while
instead forcing freq matching display on/off states gives better results also if using conservative governor, in fact we don't need a "speedy" device when its screen is turned off... who use it in that state? while instead we want a speedy device when we actively use it, when its screen is turned on
so the most balanced setup is to have a really sleepy device when screen is off (99% of times not actively in use by user) and on the opposite a really speedy device when screen is on (99% of times in use by user)
the script will control also certain pid priority differently between sleep & wake states, during sleep state it will also recovery ram if under a critic level (right now fixed at 59Mb) by flushing caches
anyway is possible to specify min-max freq by editing 98mydesireI init script, look at these lines below they speak themselves :
Code:
echo 'MinFreqWake=960000;'>>/system/etc/mycpu
echo 'MaxFreqWake=1075200;'>>/system/etc/mycpu
echo 'MinFreqSleep=128000;'>>/system/etc/mycpu
echo 'MaxFreqSleep=384000;'>>/system/etc/mycpu
change values upon your needs, here below freq steps:
128000 245000 384000 422400 460800 499200 537600 576000 614400 652800 691200 729600 768000 806400 844800 883200 921600 960000 998400 1036800 1075200 1113600
to check correct behavior connect your device and open a shell (adb shell) then put commands:
cd /sys/devices/system/cpu/cpu0/cpufreq
turn off display (without detach of course)
cat scal*
last two numbers are current min-max frequencies, your freq min-max should be the lowest possible
turn on display and repeat step 3, your freq min-max should jump
if you turn off again your freq min-max should be lowered

downloading.. will report my experience after flashing

ill give this a go

good Idea Suiller ! - a comprehensive project !
I need to do a little home-work before I dip into this project....
Your repository is very familiar.
Ive taken things from there before

rraaka said:
good Idea Suiller ! - a comprehensive project !
I need to do a little home-work before I dip into this project....
Your repository is very familiar.
Ive taken things from there before
Click to expand...
Click to collapse
thank you friend... probably you used the repository during "diamond" era

added 98mydesireI script, you can edit it as you prefer (use for this purpose pspad editor), as default its primary goal is to manage cpu freq between sleep and awake states (245-245 when sleep, 900-1113 when awake)
This is not good idea.

k3lcior said:
added 98mydesireI script, you can edit it as you prefer (use for this purpose pspad editor), as default its primary goal is to manage cpu freq between sleep and awake states (245-245 when sleep, 900-1113 when awake)
This is not good idea.
Click to expand...
Click to collapse
why not? I use this setup from about 2 years... (from froyo/ginger) I prefer a really responsive device when I actively use it (screen on)
anyway it's easy to lower freqs, is enough to edit the script:
Code:
'MinFreqWake=960000;'>>/system/etc/mycpu
'MaxFreqWake=1113600;'>>/system/etc/mycpu
I'll put freq list on 3rd post

uploaded latest tested version at 12.00 (UTC/GMT time) - 14.00 (CET)
ps: no need to wipe again, just take a look of old apk still under /data/app such as LatinIME.apk (if you don't want default ics keyboard of course)

Does int boot also with stock hboot?? Or only with cm7r2??

gastrella said:
Does int boot also with stock hboot?? Or only with cm7r2??
Click to expand...
Click to collapse
sure, but you'll wast a lot of space... /system will take less than 140Mb

In one word: GREAT!!
I'll give it a try ASAP
P.S. already started to address your initiative onto ... Well, you know where!!

trinity1 said:
I'll give it a try ASAP
P.S. already started to address your initiative onto ... Well, you know where!!
Click to expand...
Click to collapse
thank you friend

tested latest slim version, I wiped everything to be sure & to simulate a complete new installation, all worked as expected so I'm going to publish (it will take few minutes), of course always in repository
ps: keep an eye on rom file date & time (on repository) to be sure you get the updated version

Hi..... Can I make a port request.....?
Sent from my HTC Desire using XDA

Miui ics v4 being developed for n1..... I hope its easy.... There is also a detailed porting guide on miui us. I tried many times but failed...:banghead:
Sent from my HTC Desire using XDA

no sorry, I don't have much time
I'll seek only this thread without beginning any new adventure

Yasir Javed Ansari said:
Miui ics v4 being developed for n1..... I hope its easy.... There is also a detailed porting guide on miui us. I tried many times but failed...:banghead:
Sent from my HTC Desire using XDA
Click to expand...
Click to collapse
I will try to port before end of May but I need people to test.
Sent from my HTC One V using XDA

Thanks
shubhamchamaria said:
I will try to port before end of May but I need people to test.
Sent from my HTC One V using XDA
Click to expand...
Click to collapse
Hi, thanks for response..... as i mentioned in your runny thread, i'm back on wmjan rom, but using ur framework files for swipe to clear, (thanks again), but im waiting for miui ics for desire as lenny has abandoned the project.... untill then, ill stay put at wmjan sense.

How to disable screen at startup ?

Hello,
I'm struggling on disabling screen at startup.
I'm trying many many methods, but still with no good results yet:
1. Disabling in kernel source (mt 6572) - I don't have kernel source because NO.1 / mediatek do not provide it for the device.
2. removing services or libraries - on trying to remove services such as surfaceflinger of libGLE , the device can't boot.
3. on writing to sysfs brightness enries - this is the best I got, I do it in init.d :
chmod 7777 /sys/devices/platform/leds-mt65xx/leds/lcd-backlight/brightness
echo 0 > /sys/devices/platform/leds-mt65xx/leds/lcd-backlight/brightness
chmod 0 /sys/devices/platform/leds-mt65xx/leds/lcd-backlight/brightness​But the 3rd method has drawbacks: It seems that init first do the bootanimation (so I disabled it too), and then I see a watch screensaver . then there is dark screen, and pressing buttons don't change it (just what is desired)
BUT - some later time I get battery status screen - How can it be if brightness has privileged 0 (see above) ?
If anyone have ideas or suggestion, I would appreciate it a lot,
Ranchu

Disable RCTD ( Root Checking Tool) on the G7

I don't believe I have seen this on the G7 forums so I figured I would make a quick guide for anyone whom is unfamiliar with the subject. RCTD is LGs Root Checking Tool that is triggered when the bootloader is unlocked as well as when BusyBox is installed, and is known to drastically affect the performance of the device after root. This is primarily seen in the V30 forums, but I assume it affects the performance of the G7 as well. There are tools to remove it as well as a script by John Fawkes, however from what I could tell, neither of them applied to the G7. It's a pretty simple process I recommend using root explorer and Zacaree1's Root Activity Launcher(play store). There are other ways to get to the hidden menu but if you have deleted the stock dialer or have any other issues, this app will always get you there and it has a massive amount of other great uses as well and I believe any root user should have it installed.
Step 1: Open Root Explorer and head to Product/Priv-app/SRTC and delete the app. This won't stop the process from starting however because LG uses an init.d script to run the tool at boot, leading to step 2.
Step 2: Head to System/Etc/Init and find
"lge.system.services.rc" long press on it to open it with text editor (if using Root Explorer) and scroll down until you see #RCT (Root Checking Tool). Under this line you will see a list of 3 or 4 commands. To stop them from running we want to put a # in front of each and save our changes. Example:
#service rctd /sbin/rctd
# class late_start
# user root
# group root
# seclabel u:r:rctd:s0
Now we've stopped the tool from running at start up, but it will still have the last time root was detected stored in the system. First, reboot to be sure that the edit survived a restart, and if it did then head to step 3.
Step 3: Head to Mnt/Vendor/Persist-LG/RTC and delete the file inside the RTC folder. If you delete the entire RTC folder, it will be recreated at reboot so it's pointless. Save and Reboot.
Step 4: Open the Root Activity Launcher app and type "Hidden" in the search box. This will lead you to the hidden menu activity (not operator hidden menu), so click on it to expand the list. Scroll down pretty far until you see "com.lge.hiddenmenu.HiddenMenu." You can click the icon that looks like a paperclip and it will pin the shortcut to your hidden menu to your home screen if you'd like, otherwise just click on the main line to open the Hidden menu, click SVC Mode and find LG RCT. If you did everything correctly, once you click LG RCT it should show Status-disabled. It will stay disabled regardless of a reboot. Other models like the V30 need additional init.d commands to be disabled. The G7 has these same init.d scripts, but for whatever reason we only needed to stop one of them. Done!

Attachments wouldn't load

Ty mate!!!
One question, i can do all these steps with magisk on stock? Would be reverted the changes at reboot?
---------- Post added at 02:04 AM ---------- Previous post was at 01:39 AM ----------
Bro, in the step 3, i cant find any path called "vendor" under the main path "Mnt", only a 0.00bit file called vendor

it did not work, step 4... status enable

manuhuelva said:
Ty mate!!!
One question, i can do all these steps with magisk on stock? Would be reverted the changes at reboot?
---------- Post added at 02:04 AM ---------- Previous post was at 01:39 AM ----------
Bro, in the step 3, i cant find any path called "vendor" under the main path "Mnt", only a 0.00bit file called vendor
Click to expand...
Click to collapse
You should be able to. I'm still stock, ULM20e Pie. What file manager are you using? That's strange that you can't to your vendor file. Is vendor accessible to you in TWRP?

Stvn77 said:
it did not work, step 4... status enable
Click to expand...
Click to collapse
Hmmm....can you check the Persist-lg folder and see if the file inside showed back up?

Yeedatoy said:
Hmmm....can you check the Persist-lg folder and see if the file inside showed back up?
Click to expand...
Click to collapse
following the path u post, i cant find, bc persist-lg is under vendor, and i cant find vendor

Delete

When you open up your file explorer, did you click the mount R/W button?

Yeedatoy said:
When you open up your file explorer, did you click the mount R/W button?
Click to expand...
Click to collapse
See this bro
https://youtu.be/5Tj5iCnkrj0
---------- Post added at 04:24 PM ---------- Previous post was at 04:23 PM ----------
Ive done steps 1 and 2. Could not do 3

what's the point for the lg guys for slowing down the system if you have root?
and, the service is rct and after you have to look for rtc? they mess up the letters for what? something is strange

Yeedatoy said:
Hmmm....can you check the Persist-lg folder and see if the file inside showed back up?
Click to expand...
Click to collapse
yes. it showed back up

I've followed this guide on my v35 and i confirm it's working just fine!
Thanks!

Stvn77 said:
yes. it showed back up
Click to expand...
Click to collapse
Since None of my photos will load, check this post in the v40 threads to make sure your init.d script was edited with correctly.
https://forum.xda-developers.com/lg-v40/help/rctd-affects-devices-t3945207

cloud1250000 said:
I've followed this guide on my v35 and i confirm it's working just fine!
Thanks!
Click to expand...
Click to collapse
Awesome! I was getting a bit concerned for a moment while trying to think of why it hasn't worked for the others yet. Do you have LDB removed as well? I removed it so long ago that I forgot about it until I came across it in the V40 threads. I don't think it could interfere with this process, but I am trying to rule out anything that may be an issue for the others.

manuhuelva said:
See this bro
https://youtu.be/5Tj5iCnkrj0
---------- Post added at 04:24 PM ---------- Previous post was at 04:23 PM ----------
Ive done steps 1 and 2. Could not do 3
Click to expand...
Click to collapse
https://photos.app.goo.gl/zgYxBS7uWJoAkGFm8

Yeedatoy said:
https://photos.app.goo.gl/zgYxBS7uWJoAkGFm8
Click to expand...
Click to collapse
bro, finally fixed, was the custom kernel, was no installed.
I fixed manually the 1.7 kernel !!!!!
Now reach 825mhz on gpu and have spectrum bro!!
if u want i can tell u how.

manuhuelva said:
bro, finally fixed, was the custom kernel, was no installed.
I fixed manually the 1.7 kernel !!!!!
Now reach 825mhz on gpu and have spectrum bro!!
if u want i can tell u how.
Click to expand...
Click to collapse
Tell me how? Please.

How to Fix
slyxo said:
Tell me how? Please.
Click to expand...
Click to collapse
steps:
1-Open ur bootloader
2-root and install magisk
3-flash xD-Kernel 1.7-Stock from drive folder (other stock folder) in TWRP and reboot to system https://drive.google.com/file/d/1MEFt7Ma2DOw8h7d_HjfyLN64Hnqz2bOo/view?usp=sharing credits to @Smart Ru
4a-poweroff
4b-go Qfil and extract ur boot_a or boot_b partition
5-extract Android image kitchen folder and put ur boot.img inside. https://forum.xda-developers.com/attachment.php?attachmentid=5024495&d=1590190159 credits to @osm0sis
6-run unpack script
7-paste the files i provided inside ramdisk folder and replace it https://drive.google.com/file/d/1HTT-0nm-y6tib_T1VQrws0EMreWia_Us/view?usp=sharing
8-go back and run repack script
9-pick the new image file and flash it on boot_a and boot_b by fastboot or qfil
10-dont care about error message at startup of android, it appears anyways with xd-kernel-1.7-stock kernel without modifications on every boot. It appears due to kernel kills dummy lg process from startup (2.0.2-custom doesnot)
11-download spectrum.
12-done.
Ive edited the profiles too for be more accurate to profile name:
-Balanced:
Governor "blu_schedutil" (is a light schedutil with powersaving on sleep mode, perfect for everyday use)
I/O "cfq" (most balanced I/O for everyday use)
Max/min Cpu.freq = 2.8ghz/800mhz (gold) 1.7ghz/300mhz (silver)
Max/min gpu.freq = 710mhz/160mhz (710mhz is stock top speed)
-Performance:
Governor "Performance" (cpu will run at full speed all the time, just pick it only for run benchmarks or for do selective heavy task u need, will consume battery fast)
I/O "deadline" (best for gaming-benchmarks)
Max/min Cpu.freq = 2.8ghz/1.05ghz (gold) 1.7ghz/748mhz (silver)
Max/min gpu.freq = 780mhz/160mhz
-Battery:
Governor "Powersave" (cpu will run at low speed most time, a really battery saving profile, u will have a little ui lag, but it gives u true promised battery saving)
I/O "SioPlus" (best battery saving I/O available in kernel)
Max/min Cpu.freq = 1.68ghz/825mhz (gold) 1.51ghz/300mhz (silver)
Max/min gpu.freq = 160mhz/160mhz
-Gaming:
Governor "Pixutil" (A port of official Pixel 3 Schedutil governor, awesome performance without stay full 2.8ghz all time, perfect for gaming ^^)
I/O "deadline" (best for gaming-benchmarks)
Max/min Cpu.freq = 2.8ghz/1.05ghz (gold) 1.7ghz/300mhz (silver)
Max/min gpu.freq = 825mhz/160mhz (highest gpu freq profile for more fps)

Yeah, I always get " there is an internal problem with your device" message on startup. That's normal. Spectrum never worked on 1.7 for me and neither did Klapse, but 2.0 fixed that for me.

Development AIO ADB TOOL - PUSH/PULL/DEBLOAT/SIDELOAD/BACKUP/RESTORE + MORE V4.5 (19/5/22)

HELLO GUYS AND GALS
FOR THOSE OF YOU NEW TO XDA OR ARE NOT CONFIDENT WITH USING ADB
I HAVE CREATED A TOOL TO AUTOMATE THE PROCESS
(MOSTLY)
{
"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"
}
This tool was designed for the Exynos Samsung Galaxy S22 Ultra, But most features will work for other variants or brands
The S22 Ultra exy specific tools are
oem unlocking
The Debloat can be used on other variants in some instances "if its there" , but of course you cant remove samsung bloat from other brands
-- CURRENTLY FOR WINDOWS ONLY --
-- lINUX AND MAYBE MAC COMING SOON --
it does make things quicker if you....
1, have usb debugging enabled
2, have the latest adb, fastboot and samsung drivers installed
3, are connected to the laptop via usb before you begin
- if not, the tool will guide you through this process -
Samsung mobile drivers
v1.7.50.exe Click "here" to download from GDrive. Click "here" to download from Dropbox.
ADB & Fastboot for Samsung
v1.5.2 exe - Windows - click "here" to download from GDrive. Click "here" to download from Dropbox
FEAUTURES OF THIS TOOL
BACKUP/RESTORE
all
system
user
obb
(see info in help section below)
ROOT CHECKER
check for su access
REBOOT
recovery
bootloader
standard
DEBLOAT
uninstall all or groups keeping or deleting data / cache
disable all or groups
restore in groups
restore all
SIDELOAD
update.zip
PULL
logcat (needs root)
apps
sysdump - display , battery, battery stats
ringtones
notifications
framework- res (will extract it into folders to make modifying theme items easier)
device (s22 series)
PUSH
files to download folder
FLASH
recovery
(IN THE PUSH MENU)
OEM
unlocking
relocking
QS / TILE LAYOUT
rows - 6/7/8
columns - 6/7/8
DISPLAY DEVICE INFO
see screenshots
FIRSTS THINGS FIRST
--- IF YOU PLAN TO REMOVE BLOATWARE PLEASE EXAMINE THE LIST IN POST BELOW ---
1, Create a folder called "adb" on your "c:\" drive and extract the "ADB & Fastboot" files into it, it should look like this
2, Download the tool
DOWNLOAD
\/ \/ \/
\/ \/
\/
LATEST
.BAT = GDRIVE - DROPBOX - MEGA
2, Place it anywhere (id recommend the adb folder) and double click
3, Follow the on screen instructions taking care to press the correct number
IF YOU WOULD LIKE TO TEST FUTURE BUILDS OR CONTRIBUTE TO DEVELOPMENT
PLEASE GET IN TOUCH
THANKS TO
SomeXGhost - for testing
vlubosh - for testing
PLEASE FEEL FREE TO ASK FOR HELP, MAKE REQUESTS AND REPORT BUGS​

HELP
TO ENABLE DEVELOPER OPTIONS
1st - Go into your setting
2nd - Scroll down to "About Phone", open it
3rd - Open "Software Information"
4th - Press "Build Number" several times until you see a pop up window counting down from 3 until developer options are enabled
TO ENABLE USB DEBUGGING
1st - Enable "Developer Options" (see above)
2nd - Open the Developer Options setting, in settings, at the bottom of the page
3rd - Scroll down to the "Debugging" and press the "USB Debugging" button
TO INSTALL SMASUNG DRIVERS
1st - Download the files in OP
2nd - Once downloaded, Run and follow on screen instructions
BACKUP / RESTORE
Android backups are being discontinued and fully replaced by Google Drive backups. Google drive backups cannot be downloaded, and there is a 25 MB per-app limit. You need a network sniffer to log upload traffic to capture these. The warning was there since the SDK of Android 10 “Queen Cake”, however, backups themselves weren’t changed. In Android 12 “Snow Cone”, apps with Snow Cone’s API level with backup flag set to true and a Snow Cone device will back up to (dumb) Google Drive instead.

CHANGELOG
Spoiler: PREVIOUS VERSIONS
V2.0 RE FORMATTED THE WHOLE CODE WITH LOTS OF CHANGES
V2.1 CHANGED PACKING TOOL ADDED MORE OPTIONS TO DE BLOAT, MINOR BUG FIXES
V2.2 ADDED PULL USER OR SYSTEM APPS, ADDED PUSH TO DOWNLOAD FOLDER
V3.0 ADDED PUSH RECOVERY, ADB SIDELOAD, MORE NAVIGATION OPTIONS, BUG FIXES
V3.1 BUG FIX
V3.2 ADDED QS/TILE ADJUSTMENT, OEM UNLOCKING, ROOT CHECKER, MORE OPTIONS WHILE NAVIGATING
V3.3 BUG FIX
V3.4 FIXED ERROR IN DEBLOAT
v3.5 FIXED BUG IN DEBLOAT
V3.6 ADDED SOME MORE OPTIONS AND SOME INFO
V3.7 ADDED CPUINFO, ACTIVITY AND INPUT TO SYSDUMP, ADDED A DISPLAY DEVICE INFO MENU WITH LOTS OF CHOICES
v3.8 CHANGED MENU CHOICES IN DEBLOAT FROM "IF ERRORLEVEL ==" TO "%M%=="
V3.9 FIXED THE MISSING SELECTION FOR FACEBOOK IN DEBLOAT MENU
v4.0 BUG FIX, NEW REPACKING METHOD
V4.1 FIXED TYPO
V4.5 ADDED RESOTRATION OF DEBLOAT FILES
V4.6 BUG FIX
LATEST
.BAT = GDRIVE - DROPBOX - MEGA​
FOR SOME REASON, GOOGLE KEEPS SAYING MY EXE FILES CONTAIN MALWARE, IVE TRIED SEVERAL DIFFERENT PROGRAMS TO REPACK THEM, THE ONLY THING I CAN THINK OF, IS THAT I SET THE TOOL TO OPEN A LINK TO THIS FORUM THREAD TO SEEK HELP AT CERTAIN STAGES, STRANGE BUT, FOR ANYONE CONCERNED ABOUT THE CODE, GOOGLE ISNT FLAGGING THE .BAT TOOL, EVEN THOUGH ITS EXACTLY THE SAME CODE, SO TRY THAT BUT I ASSURE YOU THE EXE IS SAFE

SEE HERE FOR LIST OF BLOATWARE ITEMS IN THE .BAT AND .EXE TOOL
Spoiler: BLOATWARE
Remove Bixby Bloatware Apps
com.samsung.android.bixby.wakeup
com.samsung.android.app.spage
com.samsung.android.app.routines
com.samsung.android.bixby.service
com.samsung.android.visionintelligence
com.samsung.android.bixby.agent
com.samsung.android.bixby.agent.dummy
com.samsung.android.bixbyvision.framework
Bixby Remap
com.samsung.android.bixby.wakeup
com.samsung.android.app.spage
com.samsung.android.app.routines
com.samsung.android.bixby.service
com.samsung.android.bixby.agent
com.samsung.android.bixby.agent.dummy
General System
com.dsi.ant.sample.acquirechannels
com.dsi.ant.service.socket
com.dsi.ant.server
com.dsi.ant.plugins.antplus
com.android.egg
com.sec.android.easyonehand
com.sec.android.widgetapp.samsungapps
com.samsung.android.mateagent
com.sec.android.easyMover.Agent
com.sec.android.daemonapp
com.samsung.android.app.social
Samsung Pass/Pay
com.samsung.android.samsungpassautofill
com.samsung.android.authfw
com.samsung.android.samsungpass
com.samsung.android.spay
com.samsung.android.spayfw
Gimmicky Apps
com.samsung.android.aremoji
flipboard.boxer.app
com.samsung.android.wellbeing
com.samsung.android.da.daagent
com.samsung.android.service.livedrawing
com.sec.android.mimage.avatarstickers
Facebook
com.facebook.system
com.facebook.appmanager
com.facebook.services
Car Mode
com.samsung.android.drivelink.stub
Printing
com.android.bips
com.google.android.printservice.recommendation
com.android.printspooler
Samsung Email
com.samsung.android.email.provider
com.wsomacp
Samsung Game Launcher
com.samsung.android.game.gamehome
com.enhance.gameservice
com.samsung.android.game.gametools
com.samsung.android.game.gos
com.samsung.android.gametuner.thin
Samsung Browser
com.sec.android.app.sbrowser
com.samsung.android.app.sbrowseredge
Gear VR
com.samsung.android.hmt.vrsvc
com.samsung.android.app.vrsetupwizardstub
com.samsung.android.hmt.vrshell
com.google.vr.vrcore
Samsung Kids
com.samsung.android.kidsinstaller
com.samsung.android.app.camera.sticker.facearavatar.preload
Samsung LED Cover
com.samsung.android.app.ledbackcover
com.sec.android.cover.ledcover
Edge
com.samsung.android.service.peoplestripe
General Bloatware
com.dsi.ant.sample.acquirechannels
com.dsi.ant.service.socket
com.dsi.ant.server
com.dsi.ant.plugins.antplus
flipboard.boxer.app
com.cnn.mobile.android.phone.edgepanel
com.sec.android.easyonehand
com.samsung.android.widgetapp.yahooedge.finance
com.android.dreams.phototable
com.samsung.android.widgetapp.yahooedge.sport
com.samsung.android.spdfnote
com.sec.android.daemonapp
com.samsung.android.weather
com.samsung.android.app.reminder
com.hancom.office.editor.hidden
com.samsung.android.keyguardwallpaperupdator
com.samsung.android.app.news
com.android.egg
com.sec.android.widgetapp.samsungapps
Samsung Bloatware
com.samsung.svoice.sync
com.samsung.android.drivelink.stub
com.samsung.android.svoice
com.samsung.android.widgetapp.yahooedge.finance
com.android.dreams.phototable
com.samsung.android.widgetapp.yahooedge.sport
com.samsung.android.spdfnote
com.sec.android.widgetapp.samsungapps
com.samsung.android.email.provider
com.samsung.android.app.ledcoverdream
com.sec.android.cover.ledcover
com.sec.android.app.withtv
com.samsung.android.app.memo
com.sec.spp.push
com.samsung.android.spay
com.samsung.android.voicewakeup
com.samsung.voiceserviceplatform
com.sec.android.sidesync30
com.samsung.android.hmt.vrsvc
com.samsung.android.app.vrsetupwizardstub
com.samsung.android.hmt.vrshell
com.android.exchange
com.samsung.groupcast
com.sec.kidsplat.installer
com.sec.android.widgetapp.diotek.smemo
com.sec.android.provider.snote
com.sec.android.app.translator
com.vlingo.midas
com.sec.readershub
com.sec.android.app.gamehub
com.sec.everglades.update
com.sec.everglades
tv.peel.samsung.app
com.sec.yosemite.phone
com.samsung.android.app.episodes
com.samsung.android.app.storyalbumwidget
com.samsung.android.tripwidget
com.samsung.android.service.travel
com.tripadvisor.tripadvisor
com.android.email
com.sec.android.app.ocr
Google Bloatware
com.google.android.gm
com.google.android.apps.tachyon
com.google.android.music
com.google.android.apps.docs
com.android.chrome
com.google.vr.vrcore
com.google.android.videos
com.google.android.talk
com.google.android.apps.magazines
com.google.android.apps.plus
Microsoft Bloatware
com.skype.raider
com.microsoft.office.excel
com.microsoft.office.word
com.microsoft.office.powerpoint
Samsung Knox
com.knox.vpn.proxyhandler
com.android.stk2
com.android.stk
com.samsung.android.authfw
com.samsung.knox.keychain
com.samsung.SMT
com.samsung.android.knox.attestation
com.samsung.android.bbc.bbcagent
com.samsung.android.allshare.service.fileshare
com.samsung.android.beaconmanager
Samsung Dex
com.samsung.android.knox.containerdesktop
com.sec.android.app.desktoplauncher
com.sec.android.desktopmode.uiservice
com.samsung.desktopsystemui
com.sec.android.app.desktoplauncher
Others
com.google.ar.core
com.google.android.music
com.google.android.apps.docs
com.google.android.videos
com.samsung.android.bbc.bbcagent
com.samsung.knox.securefolder
com.samsung.android.visionintelligence
com.samsung.android.samsungpassautofill
com.samsung.android.samsungpass
com.samsung.android.bbc.bbcagent
com.google.android.feedback
com.samsung.android.livestickers
com.samsung.android.app.watchmanagerstub
com.google.android.youtube
com.samsung.android.honeyboard
com.samsung.android.homemode
com.samsung.android.galaxycontinuity
com.sec.android.widgetapp.webmanual
com.samsung.android.oneconnect
com.samsung.android.voc
com.samsung.android.email.provider
com.microsoft.office.officehubrow
com.sec.android.usermanual
com.sec.android.app.myfiles

BELOW IS A SELECTION OF SCREENSHOTS SHOWING THE TOOL AND ITS FEATURES
Spoiler: SCREENSHOTS

Tried debloating just keeps giving errors... carrier locked Tmobile s22ultra converted to U1

Does this on the 64bit exe when trying to debloat

SomeXGhost said:
Does this on the 64bit exe when trying to debloat
Click to expand...
Click to collapse
ok thanks, i never tried that...... thats why i was asking for testers, il add you into the credits for testing, i found those errors, il re create the exe into a new version

I can retry when I get out of work tonight unfortunately it won't be for another 12 hours also the .exe throws off as a Trojan to windows defender

yeah i just noticed, google have flagged the 32bit version , idk why, there is nothing malicious in it from myself, its exactly the same code as the 64bit version, its just the exe its packed in thats different, but thats the packing tool that makes those differences for architecture, so i dont know why its saying that
the code can be inspected by anyone, by right clicking the .bat file and selecting edit
or transferring the exe to an ext usb rightclicking in the folder and opening cmd/powershell in it, then with the code "ren :\AIO ADB TOOL V1.8 32BIT.bat AIO ADB TOOL V1.8 32BIT.txt" putting your drive letter before the ":\"

UPDATED THE TOOL AND ADDED MORE FEATURES AND INCLUDED SCREENSHOTS

Worked great on my S22 ultra.

bignazpwns said:
Worked great on my S22 ultra.
Click to expand...
Click to collapse
thanks for the feedback can you confirm which version of windows your using for me please

When you say oem unlocking coming soon do you mean to snapdragon as well?

It works nicely on win11!!! Thanks!!!

olivehue512 said:
When you say oem unlocking coming soon do you mean to snapdragon as well?
Click to expand...
Click to collapse
it should be the same, but that would need to be tested by a sd user.....
qwe202080 said:
It works nicely on win11!!! Thanks!!!
Click to expand...
Click to collapse
thanks for your feedback.....

Is it possible for u to add some of the adb mods to this such number of qs tiles and others?

sswagonman said:
Is it possible for u to add some of the adb mods to this such number of qs tiles and others?
Click to expand...
Click to collapse
if you show/link me the ones you want added il do my best to incoorporate it

gav83collins said:
if you show/link me the ones you want added il do my best to incoorporate it
Click to expand...
Click to collapse
Cheers will have a look for them. I believe this is it. U just change the number at the end for how many tiles u want

sswagonman said:
Cheers will have a look for them. I believe this is it. U just change the number at the end for how many tiles u wantView attachment 5604349
Click to expand...
Click to collapse
OK MATE IVE DONE THAT, WANNA BE A TESTER, IL CREDIT YOU IN OP