http://www.noverca.it/shop-aggiorna-htc-magic-con-sense#googtrans/it/en
The problem is that we don't know if this is for 32B or 32A... But if you push "Scarica Sense" a .zip that contains a .exe is downloaded... And it flash Sense.
Here is the Google-translation:
Update HTC MAGIC
Download SENSE
SENSEtm installing on your terminal you can manage and customize your HTC Magic as anyone in the world. SENSEtm is an easy interface that lets you make your single terminal at your fingertips, highlighting programs, widgets or features you need and giving you the ability to create an end-measure.
The update is dedicated solely to mobile Noverca's HTC MAGIC, it is not so compatible with terminals acquired from other sources!
Download the application Htc Sense stepmother clicking on the button and install it on your computer2
The phone must be connected to the PC through the USB cable. The PC should recognize the terminal showing the connection icon in the window at the bottom right of the screen.
The battery level must be at least 30% (minimum 3 green blocks on the battery icon).
It 'must have installed on your computer HTC Sync. It 'can be found in MicroSD HTC Sync on the bottom of the terminal or download from the link http://www.htc.com/www/support.aspx
Once all the points mentioned above were followed installation of the application can proceed SENSEtm
The update takes about 10 minutes, DO NOT interrupt the update process, disconnect the phone from a PC, or push any button before the process is concluded.
Warning! Updating the phone will lose all data stored on the phone, therefore, before proceeding, you should make a copy of all relevant information such as names in the phonebook, list of installed programs, events or meetings on the calendar saved , mail accounts etc..
Note 1: The application that allows you to upgrade your HTC MAGIC is supported on the following operating systems: Windows XP Home Edition Service Pack 2, Windows XP Professional Edition Service Pack 2, Windows XP Media Center Edition Service Pack 2, Microsoft Windows Vista Ultimate Edition, Microsoft Windows Vista Enterprise, Windows Vista Business Edition, Microsoft Windows Vista Home Premium Edition, Microsoft Windows Vista Home Basic Edition.
Note 2: If after installing HTC Sync, during the upgrade of the terminal software is required to install new drivers, download the file Android_driver.zip decompress the file on your Desktop and select the drivers folder when request by the computer.
Click to expand...
Click to collapse
I think it's a 32A rom, I'm downloading and test now.
I checked. This is a 32A rom, (hboot support 7200A CPU)
Pity we(G1) can't get a update like that...
Extracted and converted
I extracted the .zip and posted here:
http://www.4shared.com/file/249235242/5f919810/HTC_Sense_Noverca.html
I converted to 32B using relentless roaster here:
http://www.4shared.com/file/249236905/bb7988b8/Roasted-HTC_Sense_Noverca.html
guessing by the size you will need danger spl if on G1, might work on normal MT3G. Anybody willing to try?
Using the extracted files you should be able to convert to english, I just don't know how at the moment.
If anyone got that all english I would have a go.
But I wonder if ot would un-root the phone?
what boot.img file did you use to convert this to a 32b ,downloading
i will post back .
hope it works , i have relentless too,but don't know how to convert 32a to 32b
blinker1683 said:
what boot.img file did you use to convert this to a 32b ,downloading
i will post back .
hope it works , i have relentless too,but don't know how to convert 32a to 32b
Click to expand...
Click to collapse
Any luck dude?
#
# customize.prop for Rogers
#
# Set to PAP
ro.ril.enable.a53=1
ro.ril.ecc.HTC-ISR=100
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=CUPCAKE
ro.build.display.id=CUPCAKE.eng.u70000.20091208.215718
ro.build.version.incremental=98222
ro.build.version.sdk=3
ro.build.version.release=1.5
ro.build.date=Tue Dec 8 21:58:52 CST 2009
ro.build.date.utc=1260280732
ro.build.type=user
ro.build.user=u70000
ro.build.host=Android-X03
ro.build.tags=release-keys
ro.product.model=HTC Magic
ro.product.brand=htc_europe
ro.product.name=htc_magic
ro.product.device=sapphire
ro.product.board=sapphire
ro.product.manufacturer=HTC
ro.product.locale.language=
ro.product.locale.region=
ro.board.platform=msm7k
#
ro.build.product is obsolete; use
ro.product.device
ro.build.product=sapphire
# Do not try to parse
ro.build.description or .fingerprint
ro.build.description=3.05.401.3 CL#98222 release-keys
ro.build.changelist=98222
ro.product.ua=
ro.build.fingerprint=htc_europe/htc_magic/sapphire/sapphire:1.5/CUPCAKE/98222:user/release-keys
keyguard.no_require_sim=1
# end build properties
#
# system.prop for device
#
rild.libpath=/system/lib/libhtc_ril.so
ro.ril.hep = 1
wifi.interface = tiwlan0
ro.ril.htcmaskw1.bitmask = 4294967295
ro.ril.htcmaskw1 = 14449
ro.ril.hsupa.category = 5
# Time between scans in seconds. Keep it high to minimize battery drain.
# This only affects the case in which there are remembered access points,
# but none are in range.
wifi.supplicant_scan_interval = 45
# density in DPI of the LCD of this board. This is used to scale the UI
# appropriately. If this property is not defined, the default value is 160 dpi.
ro.sf.lcd_density = 160
ro.com.google.locationfeatures=1
# For SD storage insert notification sound
persist.service.mount.playsnd = 0
# For auto backlight default value
settings.display.autobacklight=0
# For brightness default value
settings.display.brightness=132
# For the default value of agps
ro.ril.def.agps.mode = 2
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.com.google.locationfeatures=1
ro.com.google.networklocation=1
ro.config.ringtone=Innovation.mp3
ro.config.notification_sound=Color.mp3
ro.config.alarm_sound=Light.mp3
ro.config.cal_notification=Vector.mp3
ro.config.msg_notification=Ascend.mp3
ro.setupwizard.mode=DISABLED
persist.service.mount.playsnd=0
ro.com.google.clientidbase=android-htc
ro.config.sync=yes
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
so what is this in detail ?
Android 1.5 with Sense ?
Does the Roastet_Rom work with 32B? Did anyone try ?
cheers
bullys
blinker1683 said:
what boot.img file did you use to convert this to a 32b ,downloading
i will post back .
hope it works , i have relentless too,but don't know how to convert 32a to 32b
Click to expand...
Click to collapse
I didn't select a particular boot.img, I only used the button that said compatibility.
I guess the system.img could be unyaffed, but as for further details on modifying the language, I'm not sure.
I tried flashing... got a error saying E,unableto find update script. I'm guessing that. We need a suitable boot.img to make it right conversion. If anybody can get the boot.img and the update script I can then convert it right. ITS TIME TO SEARCH!!!
Its 32A so dont flash to 32B.
Related
I'm so busy with work (and the Team EOS kernel for the Xoom) that I haven't had a chance to write this yet, but it should now be fairly straightforward after unlocking to write a recovery (script) that pulls in the old recovery and boot images to SD-Card, then extract those, turn off "ro.secure" and be able to get root once I fastboot that back in.
Maybe this weekend.
kcrudup said:
I'm so busy with work (and the Team EOS kernel for the Xoom) that I haven't had a chance to write this yet, but it should now be fairly straightforward after unlocking to write a recovery (script) that pulls in the old recovery and boot images to SD-Card, then extract those, turn off "ro.secure" and be able to get root once I fastboot that back in.
Maybe this weekend.
Click to expand...
Click to collapse
I'd give it a shot but my recovery is gone.
KitsunePaws said:
I'd give it a shot but my recovery is gone.
Click to expand...
Click to collapse
... then I should do this sooner than later, so you can get it back!
I plan on saving off all three major images (boot/recovery/system) and I guess posting 'em somewhere- that way, until I/we/somebody mods up CWM (et al.) for us, we can always unbrick via "fastboot".
I was quite surprised the modems are in a dd-able/fastboot-able partition. I should probably save that off once I get root, too.
kcrudup said:
... then I should do this sooner than later, so you can get it back!
I plan on saving off all three major images (boot/recovery/system) and I guess posting 'em somewhere- that way, until I/we/somebody mods up CWM (et al.) for us, we can always unbrick via "fastboot".
I was quite surprised the modems are in a dd-able/fastboot-able partition. I should probably save that off once I get root, too.
Click to expand...
Click to collapse
I would have to hug you.
Signature verification is turned on in recovery. So much for this method, and I don't want to blow my recovery yet until I get an image to replace it with. I guess I'll look for an exploit somewhere, so I can grab the images while it's running.
So WTF, Moto? There's no point in being unlocked if the recovery is still locked!
kcrudup said:
Signature verification is turned on in recovery. So much for this method, and I don't want to blow my recovery yet until I get an image to replace it with. I guess I'll look for an exploit somewhere, so I can grab the images while it's running.
So WTF, Moto? There's no point in being unlocked if the recovery is still locked!
Click to expand...
Click to collapse
Gotta love on the unlock page
"To return to Original Software, you will need to reflash a Motorola signed software image to your device, or send it in to our service center to get reflashed. MOTOROLA reserves the right to charge for any assistance required by users during this process. At this time, we are not posting a recovery image for the Photon Q 4G LTE."
"Moto" said:
"At this time, we are not posting a recovery image for the Photon Q 4G LTE."
Click to expand...
Click to collapse
Well, at least the good part is once they do post one, then I should be able to dissect that for the images I need. As long as I have the contents of /dev/block/mmcblk0p32 I'll be able to fastboot the stock recovery back in (even though I'm not sure why I should care about it, if it's got asserts turned on ).
... but I still say that being unlocked w/o the benefit of images is kinda useless. If this is really the Droid 4 (with a Sprint overlay and an LTE radio), I wonder if there's a root exploit that'll at least let me dd over the block devices to the external SD-Card.
me said:
If this is really the Droid 4
Click to expand...
Click to collapse
Nope. That's an OMAP. The search continues!
wait.. what? you do realize signature checking has been here since froyo right? unlocked bootloader doesn't equal unlocked recovery.
just chatted with bigrushdog when i get them ill pass the images to you.
Honestly, been so used to unlocked / unlockable devices, not to mention the stuff at work, thai I'd assumed one followed the other.
Thanks for looking out for the images. How do you know BRD?
kcrudup said:
Honestly, been so used to unlocked / unlockable devices, not to mention the stuff at work, thai I'd assumed one followed the other.
Thanks for looking out for the images. How do you know BRD?
Click to expand...
Click to collapse
toroplus
hopefully some point later today once we get a person who has this phone to join the irc so we can grab stock kernel from there i can grab stock recovery and system and make cwm
then you guys can port team eos rom to the photon q ;P
What method are you going to use to get (to) the kernel? Anything I can do (that doesn't risk bricking)?
oh there is never a chance of bricking, my associate is gunna root someone via remote connection, ideally ssh since teamviewer sucks. but it seems only few people actually care about rooting, so its slow goings
shabbypenguin said:
oh there is never a chance of bricking, my associate is gunna root someone via remote connection, ideally ssh since teamviewer sucks. but it seems only few people actually care about rooting, so its slow goings
Click to expand...
Click to collapse
If your pal is going to be around tonight I'll get SSH running when I get home.
Actually, http://www.raspberrypi.org/phpBB3/viewtopic.php?f=41&t=6130 I'll just toss fastboot and adb on my pi and call it a day.
KitsunePaws said:
If your pal is going to be around tonight I'll get SSH running when I get home.
Actually, http://www.raspberrypi.org/phpBB3/viewtopic.php?f=41&t=6130 I'll just toss fastboot and adb on my pi and call it a day.
Click to expand...
Click to collapse
hes actually busy today but hell be around tomorrow, rangerbry stopped in and he is locked so id rather use his so we can get stock images of the boot partitions and compare them to the unlocked ones.. see if we cnat do anything about that pesky splash screen :/
shabbypenguin said:
hes actually busy today but hell be around tomorrow, rangerbry stopped in and he is locked so id rather use his so we can get stock images of the boot partitions and compare them to the unlocked ones.. see if we cnat do anything about that pesky splash screen :/
Click to expand...
Click to collapse
Good deal, finally another taker
shabbypenguin said:
... my associate is gunna root someone via remote connection, ideally ssh
Click to expand...
Click to collapse
Wait- what?!
How does this work- I mean, it sounds like something I can do now and get things started. Do we have a working exploit for the MSM8664?
Details, man- DETAILS!
kcrudup said:
Wait- what?!
How does this work- I mean, it sounds like something I can do now and get things started. Do we have a working exploit for the MSM8664?
Details, man- DETAILS!
Click to expand...
Click to collapse
the exploit isnt going public
Can you post the /system/build.prop (and /system/default.prop if it exists)? Or show me a screen in Phone -> About phone (everything in there)?
default.prop:
Code:
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.sys.usb.config=mtp
system.prop:
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=7.7.1Q-6_SPR-89_ASA-36
ro.build.display.id=7.7.1Q-6_SPR-89_ASA-36
ro.build.version.incremental=42
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.4
ro.build.date=Fri Aug 3 23:32:39 CDT 2012
ro.build.date.utc=1344054759
ro.build.type=user
ro.build.user=hudsoncm
ro.build.host=il93lnxdroid85
ro.build.tags=release-keys
ro.product.model=XT897
ro.product.brand=motorola
ro.product.name=XT897_us_spr
ro.product.device=asanti_c
ro.product.board=MSM8960
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=motorola
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=msm8960
# ro.build.product is obsolete; use ro.product.device
ro.build.product=XT897_us_spr
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=asanti_c-user 4.0.4 7.7.1Q-6_SPR-89_ASA-36 42 release-keys
ro.build.fingerprint=motorola/XT897_us_spr/asanti_c:4.0.4/7.7.1Q-6_SPR-89_ASA-36/42:user/release-keys
ro.build.characteristics=default
# end build properties
#
# system.prop for surf
#
rild.libpath=/system/lib/libril-qc-qmi-1.so
rild.libargs=-d /dev/smd0
persist.rild.nitz_plmn=
persist.rild.nitz_long_ons_0=
persist.rild.nitz_long_ons_1=
persist.rild.nitz_long_ons_2=
persist.rild.nitz_long_ons_3=
persist.rild.nitz_short_ons_0=
persist.rild.nitz_short_ons_1=
persist.rild.nitz_short_ons_2=
persist.rild.nitz_short_ons_3=
ril.subscription.types=NV,RUIM
DEVICE_PROVISIONED=1
debug.sf.hw=1
debug.egl.hw=1
debug.composition.type=dyn
ro.sf.compbypass.enable=1
ro.sf.lcd_density=240
dev.pm.dyn_samplingrate=1
#
# system props for the cne module
#
persist.cne.UseCne=none
persist.cne.UseSwim=false
persist.cne.bat.range.low.med=30
persist.cne.bat.range.med.high=60
persist.cne.loc.policy.op=/system/etc/OperatorPolicy.xml
persist.cne.loc.policy.user=/system/etc/UserPolicy.xml
persist.cne.bwbased.rat.sel=false
persist.cne.snsr.based.rat.mgt=false
persist.cne.bat.based.rat.mgt=false
persist.cne.rat.acq.time.out=30000
persist.cne.rat.acq.retry.tout=0
persist.cne.nsrm.mode=false
ro.hdmi.enable=true
lpa.decode=false
lpa.use-stagefright=true
#system props for the MM modules
media.stagefright.enable-player=true
media.stagefright.enable-http=true
media.stagefright.enable-aac=true
media.stagefright.enable-qcp=true
media.stagefright.enable-fma2dp=true
media.stagefright.enable-scan=true
#
# system props for the data modules
#
ro.use_data_netmgrd=true
#system props for time-services
persist.timed.enable=false
# System props for audio
persist.audio.fluence.mode=endfire
persist.audio.vr.enable=false
persist.audio.handset.mic=digital
ro.config.vc_call_vol_steps=7
ro.audio.default.ring.volume=4
ro.audio.default.notif.volume=5
#
# system prop for opengles version
#
# 131072 is decimal for 0x20000 to report version 2
ro.opengles.version=131072
#
# system prop for Bluetooth Dialup Networking
#
ro.qualcomm.bluetooth.dun=false
# system prop for Bluetooth FTP profile
ro.qualcomm.bluetooth.ftp=true
#
# system property for Bluetooth Handsfree Profile Wide Band Speech
#
ro.qualcomm.bluetooth.hfp.wbs=true
#
#system prop for Bluetooth hci transport
ro.qualcomm.bt.hci_transport=smd
#
# system prop for requesting Master role in incoming Bluetooth connection.
#
ro.bluetooth.request.master=true
#
# system prop for Bluetooth Auto connect for remote initated connections
#
ro.bluetooth.remote.autoconnect=true
# system property for Bluetooth discoverability time out in seconds
# 0: Always discoverable
#debug.bt.discoverable_time=0
#system prop for switching gps driver to qmi
persist.gps.qmienabled=true
# system property for thermald
persist.thermal.monitor=true
#
# System prop for sending transmit power request to RIL during WiFi hotspot on/off
#
ro.ril.transmitpower=true
#For TCMD bringup
persist.tcmd.log.limit=0
#
#Simulate sdcard on /data/media
#
persist.fuse_sdcard=true
#
# System prop for Sprint device management
#
persist.sprint.dm.status=1:1:1:1:1:1:1:1:1:1
#
# System prop for Sprint device management GPS
#
persist.sprint.dm.gps.status=0
# BEGIN Motorola, fsk050, IKASANTISPRINT-207 - slate suport
slate.keyevent=false
slate.penevent=false
# END IKASANTISPRINT-207
# our HTML browser (not WAP browser ) does not need to specify UAProf URL
ro.mot.hw.uaprof=http://device.sprintpcs.com/Motorola/XT897-Chameleon/latest
#
# System prop for default network(NETWORK_MODE_LTE_CDMA_EVDO) and LTE enable
#
ro.telephony.default_network=8
telephony.lteOnCdmaDevice=1
# BEGIN Motorola, kgh864, IKASANTISPRINT-218 Hidden menu life data
persist.sys.wifi.rx=0
persist.sys.wifi.tx=0
persist.sys.mob.rx=0
persist.sys.mob.tx=0
persist.radio.lifecalls=0
persist.radio.lifetimer=0
# END IKASANTISPRINT-218
# BEGIN Motorola, rcjk78, 03/19/2012, IKASANTISPRINT-187
ro.cdma.home.operator.numeric = 310120
ro.cdma.home.operator.alpha = Sprint
# END IKASANTISPRINT-187
# BEGIN Motorola, emb046, 04/24/2012, IKHSS7-27158
persist.data_netmgrd_mtu = 1472
# END IKHSS7-27158
# Enable Sleep mode option when power button is pressed
ro.mot.deep.sleep.supported=true
# BEGIN MOTOROLA, eww012, 04/24/2012, IKASANTISPRINT-819: TTY is not working on SPR-31
ro.mot.fid.30544.tty=true
# END MOTOROLA, IKASANTISPRINT-819
# BEGIN IKHSS7-32053 Sprint GPS settings
persist.mot.gps.locktype=4
persist.mot.gps.assisted=false
# END IKHSS7-32053
# Enable HAC mode
ro.mot.hw.HAC=1
#Setting default Ringtone/Notifications
ro.config.ringtone=Pegasus.ogg
ro.config.notification_sound=Bellatrix.ogg
#IKHSS7-8095 VZW-IOT requirement for Ex-DisplayRecord
persist.radio.0x9e_not_callname=1
# BEGIN Motorola, a21739, 04/05/2012, IKASANTISPRINT-160
ro.sprint.lte.ipv6.supported=false
# END IKASANTISPRINT-160
# BEGIN Motorola, rjones1, 4/10/2012, IKHSS7-22881
# NFC Card Emulation Config
# bitfield:
# 15141312 11109 8 7 6 5 4 3 2 1 0
# u u u u u u u u u u p d u u s e
# where:
# u = unused bit
# p = ce on when device is powered off? 0 = no, 1 = yes
# d = ce on when display locked or off? 0 = no, 1 = yes
# s = uicc based secure element
# e = embedded/smx based secure element
#
# 1: embedded, ce off when display or device off
persist.mot.nfc.ce=1
# END IKHSS7-22881
#Proximity sensor debounce time
mot.proximity.delay=450
# disable touch below 60 pixels
mot.proximity.distance=60
# BEGIN Motorola, a22812, 05/29/2012, IKHSS7-35343
ro.camera.sound.forced=1
# END IKHSS7-35343
#MOTO, nfjb73, 06/04/2012, IKHSS7-34220
#Set the preferred cdma subscription to 0-RUIM, 1-NV
ro.cdma.subscription=1
# BEGIN motorola, a186010, 06/12/2012, IKHSS7-38099
ro.cdma.nbpcd=1
#END IKHSS7-38099
# BEGIN Motorola, a21269, 06/12/2012, IKHSS7-38085
persist.radio.add_power_save=1
# END IKHSS7-38085
# In order to hide the market name from the public during user trials,
# set the ro.property.model.exif in system.prop to a non-descriptive string, such as MODEL A.
# This string will be populated in the "model" EXIF field of camera captured image JPEG files.
# When the product team is ready for the market name to be available to the public (e.g., in a TA build),
# then the ro.property.model.exif in system.prop MUST be changed to match the PRODUCT_MODEL string.
ro.product.model.exif=XT897
#
# ADDITIONAL_BUILD_PROPERTIES
#
drm.service.enabled=true
ro.config.ringtone=Bio_Research.ogg
ro.config.alarm_alert=Cesium.ogg
ro.config.notification_sound=Bio.ogg
ro.com.google.clientidbase=android-motorola
ro.com.google.clientidbase.ms=android-sprint-us
ro.com.google.clientidbase.am=android-sprint-us
ro.com.google.clientidbase.gmm=android-sprint-us
ro.com.google.clientidbase.yt=android-sprint-us
keyguard.no_require_sim=true
ro.com.android.dataroaming=true
ro.com.android.dateformat=MM-dd-yyyy
ro.vendor.extension_library=/system/lib/libqc-opt.so
ro.com.google.gmsversion=4.0_r3
persist.radio.apm_sim_not_pwdn=1
persist.radio.call_type=1
persist.sys.qc.sub.rstrtlvl=3
persist.sys.qc.sub.rdump.max=20
ro.qualcomm.cabl=0
ro.bug2go.uid.type=TELEPHONY_DEVICE_ID
ro.usb.mtp_usbnet=0x2e32
ro.usb.mtp_usbnet_adb=0x2e33
ro.usb.cdrom=0x2e20
ro.usb.ms=0x2e21
ro.usb.ms_adb=0x2e22
ro.usb.ptp=0x2e30
ro.usb.ptp_adb=0x2e31
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=128m
ro.setupwizard.mode=DISABLED
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.mot.dpmext=true
ro.com.google.clientid=android-motorola
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.build.version.full=Blur_Version.77.6.36.XT897.Sprint.en.US
ro.mot.hidden_keyboards=evfwd
ro.mot.build.version.sdk_int=7
ro.mot.product.modelno=XT897
Hi,
i have a big problem with my first porting (an Aosp rom from zopo zp999 on my Meizu MX4). Stuck in bootanimation, only one times come the "Installing Applications". Any suggestions? libs modify? :crying:
Naphtha said:
Hi,
i have a big problem with my first porting (an Aosp rom from zopo zp999 on my Meizu MX4). Stuck in bootanimation, only one times come the "Installing Applications". Any suggestions? libs modify? :crying:
Click to expand...
Click to collapse
Hello,
As a senior member, you probably know that logcat is your friend. Since you may not have found how to simplify adb access for 4.4 builds, temporarily add this to your device tree (in the <your chipset name>.mk):
Code:
# Since Android 4.2.2, USB debugging requires authentication, something that is not possible during boot.
# To disable this, set the following property in default.prop (inside initrd):
# ro.adb.secure=0
# To get root access this is a must:
# ro.secure=0
# will allow you to run adbd as root via the adb root command:
#ro.debuggable=1
#service.adb.root=1
ADDITIONAL_DEFAULT_PROPERTIES += \
ro.secure=0 \
ro.adb.secure=0 \
ro.debuggable=1 \
service.adb.root=1 \
persist.service.adb.enable=1 \
persist.service.debuggable=1
Build that, flash, and then take a logcat while booting. You should be able to see what;s going on (even if you need another set of eyes...even then this thread is good for that).
Hope this helps, and good luck!
Thanks so much!
Inviato dal mio MX4 utilizzando Tapatalk
Hi,
I couldn't find a thread already on this with a quick search so I was wondering if anyone knows what bloatware apps, User or System, would be safe to uninstall with a rooted phone?
By safe I mean either:
Has no impact on any other functions and if you don't want the features that the app provides you can uninstall it/freeze it/disable it
Can be uninstalled/disabled/frozen with no major impact on device functionality but with some exceptions that if a user is ok with these exceptions not to work then it is otherwise safe to uninstall/freeze/disable (for example say uninstalling a certain system app breaks NFC but you don't care about NFC anyway)
I basically would like to see if this helps with speeding up the phone as, although there is 3GB of RAM, when clearing all recent apps, 2GB is still used up by, I can only assume, system apps and the OS and perhaps some of these are RAM hoggers that I don't need/want anyway.
Thanks for any help/advice
I personally go by what apps can be found in the app drawer
(Aside the obvious e.g settings app)
Sent from my D6503 using XDA-Developers mobile app
apks of MM .185 on Z5 Compact
I've been doing a lot of debloating some weeks ago, mainly to try to decrease idle battery drain on my Z5 Compact (without much success...)
So I may share my understanding and sorting of system apks by topic and importance.
These are from MM .185 on Z5 Compact (hope all Z5 models have the same apps).
I'm going to post the content of some input file to a script I execute in TWRP, which moves the apk listed in the non-commented lines (lines not starting with a #) in /system/__REMOVED/.
The current state of removed (lines starting with /) vs kept (lines starting with #) is what I consider safe and sane for now. But lots of # app can be removed without any side effects (see comments). It boots and works ok if you remove all the apks listed, except the ones in the latest 2 sections.
(Full content, sorry if it hurts, but it will allow people to find this post if they search XDA for one of the listed apk - like I had been doing for days).
Most have obvious names, so we get what they do. Some others are less obvious, and I give in the comment line before them what i found out (or just guess) they do.
# Started with elements from from XPower 1.0
# http://forum.xda-developers.com/z5-compact/development/rom-xpower-v1-0-aroma-debloat-custom-t3371100
# Also see for a full detailed list of Lollipop apps
# https://docs.google.com/spreadsheets/d/1geFByRKDTOOZSIBOixO2boG1_78NUjqzkB6iozzJ4-k/htmlview#
# 20160520 : tested a few days with some extreme debloat, but no effect on battery usage
# So, we go easier, and we let some app that otherwise would cause warnings in logcat
#########################################
### The obvious bloat
# Other than /system/app/priv-app :
/system/recovery-from-boot.p
# Lots of bloat in etc/product
/system/etc/product
# Not much in these dirs, and these looks like low-level stuff (nativeaudiolatency, servicemenu...), better keep them :
# /system/vendor/overlay
# /system/vendor/app
# Google apps
/system/app/Chrome
/system/app/Drive
/system/app/Gmail2
/system/app/Photos
/system/app/Hangouts
/system/app/Music2
/system/app/Videos
/system/app/YouTube
/system/app/Maps
/system/app/talkback
/system/priv-app/Velvet
# We keep google TTS, we get logcat warnings if no tts available
# /system/app/GoogleTTS
# Sony themes/wallpapers
/system/app/BasicDreams
/system/app/Galaxy4
/system/app/HoloSpiralWallpaper
/system/app/LiveWallpapers
/system/app/LiveWallpapersPicker
/system/app/NoiseField
/system/app/PhaseBeam
/system/app/photoslideshow-release
/system/app/PhotoTable
/system/app/experienceflow2livewallpaper-release
/system/vendor/overlay/overlay-semcexperienceflow2-300-release.apk
# Themes stuff (work without, but we may need to keep it to get black lockscreen wallpaper)
# No, Album should be enough to allow us to pick wallpapers
/system/app/skin-core-release
/system/app/skin-picker-release
/system/app/theme-manager-release
# We keep themes 000 (rainbow) and 006 007 008 (grey, black & white)
# No, we keep only 007 black, just in case
/system/app/Theme000-sw360dp-xhdpi-release
/system/app/Theme001-sw360dp-xhdpi-release
/system/app/Theme002-sw360dp-xhdpi-release
/system/app/Theme003-sw360dp-xhdpi-release
/system/app/Theme004-sw360dp-xhdpi-release
/system/app/Theme005-sw360dp-xhdpi-release
/system/app/Theme006-sw360dp-xhdpi-release
# /system/app/Theme007-sw360dp-xhdpi-release
/system/app/Theme008-sw360dp-xhdpi-release
# Sony updates/accounts/services
/system/app/com.sonyericsson.xhs
/system/app/com.sonymobile.xperialounge.services
/system/app/Lifelog-googlePreloadLive-release-2.9.P.3.8-5377032
/system/priv-app/GetMore-stub-release
/system/priv-app/somc-get-to-know-it-release
/system/priv-app/MyXperia
/system/priv-app/RecommendationEngineExtension-release
/system/priv-app/UpdateCenter-release
# Sonyentrance = Whats new
/system/priv-app/sonyentrance2-release
/system/app/SyncHub-release
/system/app/SemcWarrantyTime
/system/app/sneiaccountmanager-live
/system/app/support
/system/app/DemoAppChecker
/system/priv-app/retaildemo
# Sony & parners apps
/system/app/PhotoWidget-release
/system/app/WikipediaPlugin
/system/app/YouTubeKaraokePlugin
/system/app/YouTubePlugin
/system/app/WorldClockWidget-release
/system/app/WeatherWidget-release
/system/app/facebook-appmanager-xhdpi
/system/priv-app/facebook-installer
/system/priv-app/com.mobisystems.fileman
# We keep clock widgets
# /system/app/ClockWidgets-release
#########################################
### The less obvious bloat
# For Xperia companion (?) that we don't use anymore (we use Flashtool)
/system/priv-app/usb-mtp-backup-transport
/system/priv-app/usb-mtp-factoryreset-wrapper
/system/priv-app/usb-mtp-fotaupdate-wrapper
/system/priv-app/usb-mtp-update-wrapper
/system/priv-app/usb-mtp-vendor-extension-service
# Sony apps/features we don't really care about
/system/app/TouchBlock
/system/app/gmail-reader-service
/system/app/GoogleLyricsPlugin
/system/app/HTMLViewer
/system/app/TopContactsWidget-release
/system/app/weather-release
/system/app/XperiaTransferMobile-release
/system/app/cover-widget
/system/priv-app/CoverApp
/system/priv-app/ActiveClipper
# We only keep SmallAppManagerService : avoid warnings in logcat (but yet no small app)
# /system/priv-app/SmallAppManagerService-release
/system/priv-app/SmallApp-Calculator-release
/system/priv-app/SmallAppsFramework-release
/system/priv-app/SmallAppsLauncher-release
/system/priv-app/SmallApp-Timer-release
/system/priv-app/SmallAppWidget-release
# We keep Sony Tasks, Agenda has some dependancies on it (otherwise logcat warnings)
# /system/app/Tasks
# We will reinstall updated Album from Store
/system/priv-app/album-albumLive-release
# To edit pictures in case we need to
# /system/priv-app/SemcPhotoEditor
# Other apps we don't care about
/system/priv-app/SomcPhotoAnalyzer
/system/app/SomcMovieCreatorRmm-release
/system/priv-app/SomcMovieCreator-release
/system/priv-app/SemcVideo
/system/priv-app/SemcMusic
/system/priv-app/SomcPodcast
/system/priv-app/SemcEmail
# Sony Video store
/system/priv-app/SnpVUStore
# Music Metadata
/system/app/SemcMetadataCleanup
# Camera gadget addons
/system/priv-app/ArtFilterCamera-xhdpi-release
/system/app/ar-effect
/system/priv-app/SemcCamera3D-xhdpi-release
/system/priv-app/StylePortrait
/system/app/StyleBlue-release
/system/app/StyleBubble-release
/system/app/StyleDaily-release
/system/app/StylePaint-release
/system/app/StyleRed-release
/system/app/StyleStar-release
/system/app/StyleSunshine-release
/system/app/StyleSuntan-release
/system/priv-app/DualCamera-xhdpi-release
/system/priv-app/FaceFusionCamera-xhdpi-release
/system/priv-app/OnlineRemoteCamera-xhdpi-release
/system/priv-app/SoundPhotoCamera-xhdpi-release
/system/priv-app/CameraWearableBridgeHandheldServer
# Tv & wireless sharing
/system/app/dlna-somc-xhdpi-release
/system/priv-app/SemcTvOut
/system/priv-app/SomcMirrorLinkManualSwitch
/system/priv-app/SomcMirrorLinkServer
/system/priv-app/SomcMirrorLinkSystem
/system/priv-app/SomcPlayAnywhere
# We let everything "wifi display", not really clear what is sony/qualcomm/atfWD
# and what makes Chromecast or Miracast in settings...
# (ATFWD may mean AT command forward, which would be completely something else)
# Could be added to build.prop : persist.radio.atfwd.start=false
# /system/priv-app/SomcWifiDisplay
# Qualcomm Wifi display
# /system/app/WfdService
# Gamepad, smartwatch, heartbeat & co
/system/app/AntHalService
/system/priv-app/livewaremanager
/system/app/DualShockManager
/system/app/RemoteControlService
# Asian keyboards
/system/app/ExternalKeyboardJP
/system/app/SomcPOBox
/system/priv-app/textinput-chn-xhdpi
# Intelligent stuff
/system/app/Iengine
/system/app/IntelligentBacklight
/system/app/IntelligentObserver
/system/priv-app/IntelligentGesture
/system/app/FaceLock
# OverTheAir stuff
/system/app/OmaDownload
/system/app/OmaV1AgentDownloadServices
/system/app/fota-service
/system/priv-app/OMAClientProvisioning-release
# This app deletes some becknmark apps and block access to android forums (launched in
# some very specific context ?!)
/system/app/pip
# Sony background services, crash & usage reporting
/system/app/AnonymousData
/system/app/CrashMonitor
/system/app/CrashMonitorSystem
/system/app/IddAgent
/system/app/RcaHandler
/system/app/phone-usage
/system/app/device-monitor
/system/app/GoogleAnalyticsProxy
# Setting "Storage/Move stuff to Sd Card" will Force-Close without this
# but it checks disk usage every 10 minutes ! :
/system/priv-app/SemcStorageChecker
# Xperia configurator/Enterprise/Cloud backup...
/system/app/DeviceConfigTool
# Exchange & Enterprise stuff
/system/app/Exchange3Google
/system/priv-app/Exchange2
/system/app/SomcEnterpriseInstallationService
/system/priv-app/EnterpriseService
/system/app/OneTimePassLockScreenApp
/system/priv-app/RemoteUnlockService
# DRM stuff : we keep them, may be needed for Sony own drm stuff
# /system/app/DrmDialogs
# /system/app/SecureClockService
# /system/priv-app/DtcpCtrl-release
# /system/app/KerberosService
# Works fine without all that :
# These creates some bookmarks sqlite dbs
# /system/app/BookmarkProvider
# /system/app/PartnerBookmarksProvider
# /system/priv-app/BackupRestoreConfirmation
# /system/priv-app/EmergencySms
# Backup on SD card
# /system/priv-app/SharedStorageBackup
# We keep this one to avoir warnings in logcat
# /system/app/PrintSpooler
# These two do not prevent the SIM card and phone from working :
# "Sim service" app : if kept, our carrier icon is recreated in Home launcher at each boot
/system/app/Stk
/system/app/SmartcardService
# /system/app/TetherEntitlementCheck
# May help start SIM card pin earlier (?)
# /system/app/StartupFlagV2
# Rich content services ? We can keep them, may be used by SMS/MMS
# /system/app/rcs-startup
# /system/priv-app/RcsVideoShare
# /system/priv-app/rcs-core
# /system/priv-app/rcs-settings
# Low level GSM/network stuff
# Works without these, but do not change battery usage, so let's keep them
# /system/priv-app/CNEService
# /system/priv-app/QtiTetherService
# /system/priv-app/fast-dormancy-wakeup
# /system/priv-app/qcrilmsgtunnel
###############################################
# 20150517 : boots and works OK without the following ones,
# but some features are obviously lost
# Bluetooth & NFC
# /system/app/Bluetooth
# /system/app/NfcNci
# /system/app/BluetoothMidiService
# /system/app/AptxNotifier
# Camera
# /system/app/CameraAddonPermission-release
# /system/app/CameraCommonPermission-release
# /system/app/CameraExtensionPermission-release
# /system/priv-app/CameraCommon
# /system/priv-app/SemcCameraUI-generic-xhdpi-release
# /system/priv-app/SuperVideoCamera-xhdpi-release
# Wifi (CaptivePortal = free wifi access points with intermediate web page ?)
# /system/app/CaptivePortalLogin
# /system/app/HotspotAdvancedSetting
# /system/priv-app/SomcWifiService
# Used to raise power when acting as a hotspot, and decrease it when power is low :
# /system/app/TransmitPower
# Fingerprint (works ok without this Sony one), but :
# java.lang.Exception: The FPC extension service could not be loaded
# /system/priv-app/SomcFingerprint
# /system/app/FingerprintServiceExtension
# Fingerprint "FIDO" stuff, fingerprint unlock works without these two apk
# /system/app/FingerprintASM
# Other FIDO stuff (not in CM13)
# /system/app/FidoClient
# /system/priv-app/FidoCryptoService
# Other Sony stuff we can remove
# /system/app/HeadphoneSelection
# /system/app/UnsupportedHeadsetNotifier
# /system/app/SemcAutoPowerOff
# /system/app/SemcPowerSaveModule
# Cnap = Calling Name Provider
# /system/app/SemcCnapProvider
# Restart if SIM inserted/removed popup
# /system/app/SemcSimDetection
# /system/app/TouchFilterPackageSwitchService
# This one installs packages (?)
# /system/app/package-courier-release
# Sound
# /system/app/SoundEnhancement
# /system/priv-app/MusicFX
# /system/priv-app/SoundRecorder
# Sony images enhancement
# Let's keep it to validate drmrestore
# /system/app/ImageEnhancer
# /system/app/ImageProcessorPermission-release
# Standard stuff (also in CM13)
# /system/app/PacProcessor
# /system/app/Radio3
# /system/app/WAPPushManager
# WapPush is Sony only
# /system/priv-app/WapPush
# /system/app/white-balance
# /system/priv-app/ApnUpdater-release
# /system/priv-app/CallLogBackup
# /system/priv-app/CredentialManagerService
# /system/priv-app/CustomizationSelector-xhdpi-release
# /system/priv-app/CustomizedSettings-release
# Low level security (IMEI, SIM, S1 cert...) :
# /system/priv-app/DeviceSecurityService
# /system/priv-app/ExtendedBootLockService
# /system/priv-app/ScreenRecording
# /system/priv-app/SimlockUnlockApp
# /system/priv-app/SmartSearch
# /system/priv-app/TopContactsProvider
# /system/priv-app/VpnDialogs
# Lots of location services in this Qualcomm app
# /system/priv-app/com.qualcomm.location
# USB stuff, mainly for japanese carrier ? (not many translations in ressources)
# /system/priv-app/enhancedusbux
###############################################
# Google core stuff
# Apps included in Open Gapps PICO :
# ConfigUpdater
# GoogleBackupTransport
# GoogleContactsSyncAdapter
# GoogleFeedback
# GoogleLoginService
# GoogleOneTimeInitializer
# GooglePartnerSetup
# GoogleServicesFramework
# Phonesky
# PrebuiltGmsCore
# SetupWizard
# Stock Google stuff, that we can remove if we want to install Gapps pico instead
# /system/app/GoogleCalendarSyncAdapter
# /system/app/GoogleContactsSyncAdapter
# /system/priv-app/ConfigUpdater
# /system/priv-app/GoogleBackupTransport
# /system/priv-app/GoogleFeedback
# /system/priv-app/GoogleLoginService
# /system/priv-app/GoogleOneTimeInitializer
# /system/priv-app/GooglePackageInstaller
# /system/priv-app/GooglePartnerSetup
# /system/priv-app/GoogleServicesFramework
# /system/priv-app/Phonesky
# /system/priv-app/GmsCore
# /system/priv-app/SetupWizard
# We can remove some of them, but some others of them are needed : otherwise, bootloop.
###############################################
# 20150517 : apk we still keep (probably all essentials)
# /system/app/CertInstaller
# /system/app/ClockWidgets-release
# /system/app/CoreSettings
# /system/app/DocumentsUI
# /system/app/DownloadProviderUi
# /system/app/ExactCalculator
# /system/app/ExternalKeyboardsInternational
# /system/app/KeyChain
# /system/app/LockscreenSettings-release
# /system/app/SemcSettings
# /system/app/ServiceMenu
# /system/app/TimeService
# /system/app/UserDictionaryProvider
# /system/app/WebViewGoogle
# /system/app/app-textInputLive-release
# /system/app/bootinfo
# /system/app/duidgenerator
# /system/app/home-release
# /system/app/telresources
# /system/app/wallpaperpicker-release
# /system/app/xperia-keyboard-dictionaries
# /system/priv-app/CalendarProvider
# /system/priv-app/CarrierConfig
# /system/priv-app/Conversations
# /system/priv-app/DefaultContainerService
# /system/priv-app/DownloadProvider
# /system/priv-app/ExternalStorageProvider
# /system/priv-app/FusedLocation
# /system/priv-app/InCallUI
# /system/priv-app/InputDevices
# /system/priv-app/LocalContacts
# /system/priv-app/ManagedProvisioning
# /system/priv-app/MediaProvider
# /system/priv-app/MmsService
# /system/priv-app/Phonebook
# /system/priv-app/ProxyHandler
# /system/priv-app/SEMCSetupWizard
# /system/priv-app/SemcCalendar
# /system/priv-app/SemcClock
# /system/priv-app/SemcContactsProvider
# /system/priv-app/SemcTelephonyProvider
# /system/priv-app/Settings
# /system/priv-app/SettingsProvider
# /system/priv-app/Shell
# SimCotacts = services with "sdn" in names
# /system/priv-app/SimContacts
# /system/priv-app/StatementService
# /system/priv-app/SystemUI
# /system/priv-app/Tag
# /system/priv-app/TeleService
# /system/priv-app/Telecom
# /system/priv-app/WallpaperCropper
# /system/priv-app/sound-picker-release
# The end.
Thank you very much for the extensive guide and tests! Great job and good help for anyone interested in Sony's bloat
I personally focused myself on the running processes and services, searched for information about them and decompiled the strange ones, and then just hid the useless apks.
For anyone interested: freezing/disabling system apps will not prevent them from being launched and run, you need to uninstall them or hide them (which makes them unavailable to the Android system without deleting them, ready to be restored)
LolaPalocz said:
I've been doing a lot of debloating some weeks ago, mainly to try to decrease idle battery drain on my Z5 Compact (without much success...)
So I may share my understanding and sorting of system apks by topic and importance.
Click to expand...
Click to collapse
Did you encounter any problem with com.qualcomm.qti.tetherservice?
Sometimes, on reboot, i get cyclic crashing of this app, and Logcat shows that the problem lays on some uninstalled system apps (like crashmonitor or enterprise service) :
Bad call: specified package com.appname under uid 1000 but it is really -1
and then com.qualcomm.qti.tetherservice crashes because of:
SecurityException: com.appname was not granted this permission: android.permission.WRITE_SETTINGS
com.appname could be enterprise service or crashmonitor or other system apps uninstalled. They strangely seem to make qti tether app crash. Restoring one of them just makes the error trigger with another system app.
ninestarkoko said:
Did you encounter any problem with com.qualcomm.qti.tetherservice?.
Click to expand...
Click to collapse
No, it was may be among the packages I removed early, with the other Entreprise stuff.
I dont do any tethering, and I didnt encouter what you did, sorry.
Have you tried removing it ? Tethering may still work with the pure android stuff (like fingerprint still worked when I removed 2 or may be the 3 apk with fingerprint in their names).
I also checked in my archive of numerous logcats, and did not find any occurence of the string "com.appname" ...
LolaPalocz said:
I'm going to post the content of some input file to a script I execute in TWRP, which moves the apk listed in the non-commented lines (lines not starting with a #) in /system/__REMOVED/.
The current state of removed (lines starting with /) vs kept (lines starting with #) is what I consider safe and sane for now. But lots of # app can be removed without any side effects (see comments). It boots and works ok if you remove all the apks listed, except the ones in the latest 2 sections.
Click to expand...
Click to collapse
As some people requested it, here are the script and the files list.
Probably best to use it just after flashtool and fastboot flash boot+twrp, before first boot, but can be run anytime, even multiple times if you want to debloat progressively by uncommenting some lines.
In TWRP : Advanced > Terminal, then cd /externalsd/, and execute :
sh debloat.sh debloat.sane dry to see what the script would do
sh debloat.sh debloat.sane to actually move the apks into /system/__Removed/.
Forgot to say in my first post that it also removes the whole content of /oem/deletable-app/ and /oem/priv-app/ .
LolaPalocz said:
I also checked in my archive of numerous logcats, and did not find any occurence of the string "com.appname" ...
Click to expand...
Click to collapse
com.appname was a generic name for one of the system apps removed... however i'll try to remove Qti tether and see. thanks
LolaPalocz said:
As some people requested it, here are the script and the files list.
Probably best to use it just after flashtool and fastboot flash boot+twrp, before first boot, but can be run anytime, even multiple times if you want to debloat progressively by uncommenting some lines.
In TWRP : Advanced > Terminal, then cd /externalsd/, and execute :
sh debloat.sh debloat.sane dry to see what the script would do
sh debloat.sh debloat.sane to actually move the apks into /system/__Removed/.
Forgot to say in my first post that it also removes the whole content of /oem/deletable-app/ and /oem/priv-app/ .
Click to expand...
Click to collapse
Thanks for the scripts.
If I want to restore an apk I just move the apk back to its original place and reboot?
For some reason cant get it to work. Open Terminal but unable to cd to /externalsd/.
If not too much trouble could I ask you to upload it as a flashable script.zip?
Norup58 said:
Thanks for the scripts.
If I want to restore an apk I just move the apk back to its original place and reboot?
For some reason cant get it to work. Open Terminal but unable to cd to /externalsd/.
If not too much trouble could I ask you to upload it as a flashable script.zip?
Click to expand...
Click to collapse
Sorry, I dont know how to make flashable zips. And as TWRP is so nice and provides a shell (you can get it with 'adb shell' too, which is more confortable than the tiny keyboard and screen), you get more flexibility.
And it's ' cd /external_sd/ ' (with a _), where you'll find your external SD card.
And yes, to restore, you just move it back from /system/__Removed/ to its original place, and reboot.
You first have to mount /system (with twrp menu) read-write.
Also, an apk is actually in its own directory (with other stuff, libs, odex...), so we (the script, and you when you restore) are moving directories. So, if you vant to restore, you move the directory back.
Good luck.
LolaPalocz said:
Sorry, I dont know how to make flashable zips. And as TWRP is so nice and provides a shell (you can get it with 'adb shell' too, which is more confortable than the tiny keyboard and screen), you get more flexibility.
And it's ' cd /external_sd/ ' (with a _), where you'll find your external SD card.
And yes, to restore, you just move it back from /system/__Removed/ to its original place, and reboot.
You first have to mount /system (with twrp menu) read-write.
Also, an apk is actually in its own directory (with other stuff, libs, odex...), so we (the script, and you when you restore) are moving directories. So, if you vant to restore, you move the directory back.
Good luck.
Click to expand...
Click to collapse
Thanks again, got it to work....sort of....
In my case it was 'cd /sdcard/' and running the script via Minimal ADB gives a better overview :good:
Only 'issue' was the apks werent removed. Oh, they were 'backup' ok as your script said/does but had to manually deleted then afterwards. So guess to get best result one should run the script straight after 'SuperSU' has been flashed/installed (before any apks starts updating)- like you mentioned earlier
system/app/AnonymousData
system/app/ar-effect
system/app/BasicDreams
system/app/Chrome
system/app/com.sonyericsson.xhs
system/app/com.sonymobile.xperialounge.services
system/app/cover-widget
system/app/CrashMonitor
system/app/CrashMonitorSystem
system/app/DemoAppChecker
system/app/Drive
system/app/DualShockManager
system/app/ExactCalculator
system/app/experienceflow2livewallpaper-release
system/app/Exchange3Google
system/app/facebook-appmanager-xhdpi
system/app/Galaxy4
system/app/GetMoreClient-release
system/app/Gmail2
system/app/gmail-reader-service
system/app/GoogleLyricsPlugin
system/app/GoogleTTS
system/app/Hangouts
system/app/HTMLViewer
system/app/IddAgent
system/app/HoloSpiralWallpaper
system/app/Lifelog-googlePreloadLive-release-2.9.P.3.8-5377032
system/app/LiveWallpapers
system/app/LiveWallpapersPicker
system/app/Maps
system/app/Music2
system/app/NoiseField
system/app/PhaseBeam
system/app/phone-usage
system/app/Photos
system/app/photoslideshow-release
system/app/PhotoTable
system/app/PhotoWidget-release
system/app/RcaHandler
system/app/SemcWarrantyTime
system/app/sneiaccountmanager-live
system/app/support
system/app/SomcPOBox
system/app/StyleBlue-release
system/app/StyleBubble-release
system/app/StyleDaily-release
system/app/StylePaint-release
system/app/StyleRed-release
system/app/StyleStar-release
system/app/StyleSunshine-release
system/app/StyleSuntan-release
system/app/talkback
system/app/TopContactsWidget-release
system/app/TouchBlock
system/app/Videos
system/app/weather-release
system/app/WeatherWidget-release
system/app/WikipediaPlugin
system/app/WorldClockWidget-release
system/app/XperiaTransferMobile-release
system/app/YouTube
system/app/YouTubeKaraokePlugin
system/app/YouTubePlugin
system/etc/product
system/priv-app/ActiveClipper
system/priv-app/album-albumLive-release
system/priv-app/ArtFilterCamera-xhdpi-release
system/priv-app/com.mobisystems.fileman
system/priv-app/CoverApp
system/priv-app/DualCamera-xhdpi-release
system/priv-app/facebook-installer
system/priv-app/FaceFusionCamera-xhdpi-release
system/priv-app/GetMore-release
system/priv-app/livewaremanager
system/priv-app/MyXperia
system/priv-app/OnlineRemoteCamera-xhdpi-release
system/priv-app/RecommendationEngineExtension-release
system/priv-app/retaildemo
system/priv-app/SemcCamera3D-xhdpi-release
system/priv-app/SmallApp-Calculator-release
system/priv-app/SmallAppManagerService-release
system/priv-app/SmallAppsFramework-release
system/priv-app/SmallAppsLauncher-release
system/priv-app/SmallApp-Timer-release
system/priv-app/SmallAppWidget-release
system/priv-app/SnpVUStore
system/priv-app/somc-get-to-know-it-release
system/priv-app/SomcPhotoAnalyzer
system/priv-app/sonyentrance2-release
system/priv-app/SoundPhotoCamera-xhdpi-release
system/priv-app/StylePortrait
system/priv-app/textinput-chn-xhdpi
system/priv-app/UpdateCenter-release
system/priv-app/usb-mtp-backup-transport
system/priv-app/usb-mtp-factoryreset-wrapper
system/priv-app/usb-mtp-fotaupdate-wrapper
system/priv-app/usb-mtp-update-wrapper
system/priv-app/usb-mtp-vendor-extension-service
system/priv-app/Velvet
LolaPalocz said:
As some people requested it, here are the script and the files list.
Probably best to use it just after flashtool and fastboot flash boot+twrp, before first boot, but can be run anytime, even multiple times if you want to debloat progressively by uncommenting some lines.
In TWRP : Advanced > Terminal, then cd /externalsd/, and execute :
sh debloat.sh debloat.sane dry to see what the script would do
sh debloat.sh debloat.sane to actually move the apks into /system/__Removed/.
Forgot to say in my first post that it also removes the whole content of /oem/deletable-app/ and /oem/priv-app/ .
Click to expand...
Click to collapse
Greetings,
the script works perfect!
Is it possible to make a script for the new firmware .224 ?
Thanks in advance.
greg.chalk said:
Is it possible to make a script for the new firmware .224 ?
Click to expand...
Click to collapse
Here it is (changes from .185 to .224 described at the beginning of the list file).
LolaPalocz said:
Here it is (changes from .185 to .224 described at the beginning of the list file).
Click to expand...
Click to collapse
That works nice on Z3+/Z4 with 224 FW
LolaPalocz said:
Here it is (changes from .185 to .224 described at the beginning of the list file).
Click to expand...
Click to collapse
Thank you very much for your effort
LolaPalocz said:
Here it is (changes from .185 to .224 described at the beginning of the list file).
Click to expand...
Click to collapse
After testing the script, everything works perfectly.
Just one last question: is it possible to disable or delete with the script "suggested apps"?
Also, maybe it's a good idea to make a new specific thread for this script so even more people be able to find it.
greg.chalk said:
Just one last question: is it possible to disable or delete with the script "suggested apps"?
Click to expand...
Click to collapse
If you mean the list of recent opened apps on the side of the drawer, it's part of the launcher (/system/app/home-release), and you don't want to remove the launcher : ) , so no.
(It would need hacking this package - there are other threads about modded sony home to install and replace this one - dunno if there is one with this removed).
greg.chalk said:
Also, maybe it's a good idea to make a new specific thread for this script so even more people be able to find it.
Click to expand...
Click to collapse
Well, I like it here : ) The real added value is the list of packages, sorted by importance and categories, with comments. So people can go edit it by hands and decide for themselves what they need. The script is just a side effect : )
Is it possible to make a script for the new firmware .253?
toncheee said:
Is it possible to make a script for the new firmware .253?
Click to expand...
Click to collapse
I wont have the time to check .253 soon.
But the script and the file list for .224 will most probably work with .253.
There was a few changes between .185 (Android 6.0) and .224 (Android 6.0.1), but as .253 is still Android 6.0.1, Sony may not have changed many .apk filenames, possibly none.
You may execute the script with the option "dry" to see what would be removed. If you see any line starting with "?" instead of "dry", the apk was not found and Sony may have renamed (or just removed) it. Please tell us.
Hi,
I have a device with stock rom. Rooted and I can use SU with ADB.
I edited build.prop and added ro.debuggable=1 at the top. *remount rw, edit then remount ro*. However getprop ro.debuggable returns 0.
All the guides I found were about getting root but I have it already.
I don't have custom recovery as my aboot is locked.
Any ideas how to add ro.debuggable to my phone with root without pulling the boot image and repack it?
It's one of those that you cannot edit once it's set.
CXZa said:
It's one of those that you cannot edit once it's set.
Click to expand...
Click to collapse
So you mean that there is no option for me to debug any app?
prof.abkarino said:
Hi,
I have a device with stock rom. Rooted and I can use SU with ADB.
I edited build.prop and added ro.debuggable=1 at the top. *remount rw, edit then remount ro*. However getprop ro.debuggable returns 0.
All the guides I found were about getting root but I have it already.
I don't have custom recovery as my aboot is locked.
Any ideas how to add ro.debuggable to my phone with root without pulling the boot image and repack it?
Click to expand...
Click to collapse
ro.debuggable is in the boot.img/recovery.img in file default.prop try changing it there
Sent from my Z958 using Tapatalk
rick.wardenburg said:
ro.debuggable is in the boot.img/recovery.img in file default.prop try changing it there
Sent from my Z958 using Tapatalk
Click to expand...
Click to collapse
Like he said. The earliest setting is the one you have to modify.
prof.abkarino said:
Hi,
I have a device with stock rom. Rooted and I can use SU with ADB.
I edited build.prop and added ro.debuggable=1 at the top. *remount rw, edit then remount ro*. However getprop ro.debuggable returns 0.
All the guides I found were about getting root but I have it already.
I don't have custom recovery as my aboot is locked.
Any ideas how to add ro.debuggable to my phone with root without pulling the boot image and repack it?
Click to expand...
Click to collapse
What device do you have?
Sent from my Z958 using Tapatalk
rick.wardenburg said:
ro.debuggable is in the boot.img/recovery.img in file default.prop try changing it there
Click to expand...
Click to collapse
Just in case you didn't notice, my bootloader is locked so I can't use fastboot. I want a way to control it.
rick.wardenburg said:
What device do you have?
Click to expand...
Click to collapse
LG L90
@prof.abkarino
can you post your build.prop
also, just making sure your not entering the command "set ro.debuggable=1" the correct way is "setprop ro.debuggable=1"
also im not sure which variant of LG90 you have but i came across this thread in a search,
https://forum.xda-developers.com/lg-l90/general/guide-unlock-bootloader-flash-custom-t2839690
rick.wardenburg said:
@prof.abkarino
can you post your build.prop
also, just making sure your not entering the command "set ro.debuggable=1" the correct way is "setprop ro.debuggable=1"
also im not sure which variant of LG90 you have but i came across this thread in a search,
https://forum.xda-developers.com/lg-l90/general/guide-unlock-bootloader-flash-custom-t2839690
Click to expand...
Click to collapse
ro.debuggable is read only so "setprop ro.debuggable=1" doesn't work. I attached a screenshot.
I have LG L90 D410 V20b. V10* is for kitkat.
For build.prop file, I set it on the first line and I am sure it has no duplicate or override.
Code:
[email protected]:/ # cat /system/build.prop
ro.debuggable=1
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=LRX22G.**************
ro.build.display.id=LRX22G.************
ro.build.version.incremental=1604115251e54
ro.build.version.sdk=21
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=5.0.2
ro.build.date=Wed Feb 10 11:59:44 IST 2016
ro.build.date.utc=1455085784
ro.build.type=user
ro.build.user=jenkins
ro.build.host=SI-RD10-BX-45
ro.build.tags=release-keys
ro.product.model=LG-D410
ro.product.brand=lge
ro.product.name=w7ds_global_com
ro.product.device=w7ds
ro.product.board=MSM8226
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.cpu.abilist=armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=
ro.product.manufacturer=LGE
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=msm8226
# ro.build.product is obsolete; use ro.product.device
ro.build.product=w7ds
.......
I am very sorry if this is a dumb question, I have been having sex with this phone for a few days and I have no idea what I am doing. and my wife is going to kill me if I don't get her phone and data up and running soon :crying: so I was trying to recover some files that got acidentally removed from the device and I decided to root it. I thought, it's not going to be a big deal... and so I didn't backup. (facepalm)
So I used instruction on gadgethacks dot com (can't post a link because I am new here), however I ignored the part where they say you need to validate that your phone is compatible. (again, facepalm)
I flashed AP = CF-Auto-Root-herolte-heroltexx-smg930f.tar.md5 using Odin3-v3.10.6.exe and now when the phone restarts I get "Verification failed Unable to restart your device. The integrity verification has failed. You need to reset your device to factory default settings. This will erase your data."
Then I discovered that in download mode it says that my phone is SW-G930W8
Then I found this file and I tried to flash it.
CF-Auto-Root-heroltebmc-heroltebmc-smg930w8.tar.md5
same error message.
Then I flashed twrp-3.2.3-0-herolte.img.tar
I can get into the twrp recovery, but still can't boot the system. then I used adb in twrp mode but can't see any of my wife's files in internal memory, I am guessing because they are on an encrypted partition or something like that. but I can access /system/ and so I found a file called build.prop where it says that my Android version is G930W8VLS3BRC2
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=NRD90M
ro.build.display.id=NRD90M.G930W8VLS3BRC2
ro.build.version.incremental=G930W8VLS3BRC2
ro.build.version.sdk=24
ro.build.version.preview_sdk=0
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=7.0
ro.build.version.security_patch=2018-03-01
ro.build.version.base_os=samsung/heroltebmc/heroltebmc:7.0/NRD90M/G930W8VLU3BRB2:user/release-keys
ro.build.version.security_index=1
ro.build.date=Thu Mar 8 14:44:49 KST 2018
ro.build.date.utc=1520487889
ro.build.type=user
ro.build.user=dpi
ro.build.host=SWHE9410
ro.build.tags=release-keys
ro.build.flavor=heroltebmc-user
ro.product.model=SM-G930W8
ro.product.brand=samsung
ro.product.name=heroltebmc
ro.product.device=heroltebmc
ro.product.board=universal8890
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=arm64-v8a
ro.product.cpu.abilist=arm64-v8a,armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=arm64-v8a
ro.product.manufacturer=samsung
ro.product.locale=en-CA
ro.wifi.channels=
ro.board.platform=exynos5
so I found this amazing site called firmware.mobi where I was able to get a recovery from that specific version of android... and still the same error message comes up.
So I was following the instructions of the root manual so I have developer mode turned on and "OEM unlock" enabled if that helps at all.
Please help me Any advice is very much appreciated.
Question 1: Is it possible to save the data in the internal memory of the phone? i.e. either boot the system or fetch and decrypt the partition? How?
Question 2: If not, then how do I at least get the phone to work again? Just do what it says and wipe it? Or flash some complete stock ROM?
So nobody knows? Or is my question so dumb that no one wants to bother to answer?