Database Develop

[Q] Integrate Updates in Galaxy S DBT 2.2.1 FW...

Hi there!
This might be a real dumb question, so feel free to call me an Arthur Dent worthy kneebiter and point me to the right forum thread.
I just updated my Galaxy S DBT version to 2.2.1 after it is finally available officially via Kies in Germany.
Of course the SamsungApps, Market and GoogleMaps as well as Layar were already out of date, so i wanted to integrate them into the ROM after rooting with SuperOneClick with TitaniumBackup. Unfortunately that failed and after checking with adb shell it looks like there is simply not enough space on the system partition.
So i am wondering now: Did i do something wrong and do i have some huge left over piece of junk in the system partition, or is the 2.2.1 rom really a bit tight?
In the end i moved Layar and that HRS-Hotel application to /data/app to get it in.
So when i now grep for all files in /system touched "today" i get this now:
-rw-r--r-- root root 2262043 2011-03-09 23:03 SamsungApps.apk
-rw-r--r-- root root 6143559 2011-03-09 23:13 Maps.apk
-rw-r--r-- root root 24576 2011-03-09 22:17 UNAService.apk
-rw-r--r-- root root 1820247 2011-03-09 22:30 Vending.apk
And that's the root i guess (skipped posting the symlinks):
-rwxr-xr-x root shell 1062992 2011-03-09 22:20 busybox
-rw-rw-rw- root shell 196521 2010-10-16 22:04 Superuser.apk
-rwsr-xr-x root shell 26264 2010-10-16 22:04 su
With Layar-samsung.apk and HRS-Hotel.apk removed that gives me:
/system: 282432K total, 282076K used, 356K available (block size 4096)
Does that look ok for you or should i better do a desaster recovery and try again?
Bests,
Tobias

I'm not quite sure why it fails, but flashing back to a previous FULL stock rom with repartition should solve any issues you have. I can also recommend to root it through hardcore's speedmod. http://forum.xda-developers.com/showthread.php?t=822756
This will allow you to format all the partitions to EXT4. I'm not assuming anything, you might already know all of this.
Which PIT-file did you use?
Personally I haven't seen any reason to update through Kies rather than Odin, the desired effect will be the same am I right?

Well i just did a standard update via Kies 2 from Froyo 2.2 DBT to Froyo 2.2.1 DBT. I guess this does not repartition the filesystem.
Before i delve into the mysteries of Odin and spend my weekend fiddling, i wanna know: Is something screwed or is this the system partition really packed full on 2.2.1 ?
So if somebody who did a stock updata and has it rooted with OneClickRoot could do an
adb shell
df
with the Android platform tools
And give me the line for /dev/block/stl9 or /system, then i would know if it is worth the effort to restart from scratch.
I get:
/system: 282432K total, 280816K used, 1616K available (block size 4096)
With Samsung Apps, Task Manager, Google Maps, UNA database and Android Market update integrated into Rom:
-rw-r--r-- root root 2262043 2011-03-09 23:03 SamsungApps.apk
-rw-r--r-- root root 713998 2011-03-10 17:32 JobManager.apk
-rw-r--r-- root root 6143559 2011-03-09 23:13 Maps.apk
-rw-r--r-- root root 86053 2011-03-10 13:35 UNAService.apk
-rw-r--r-- root root 1820247 2011-03-09 22:30 Vending.apk
Plus rooting:
-rwxr-xr-x root shell 1062992 2011-03-09 22:20 busybox
-rw-rw-rw- root shell 196521 2010-10-16 22:04 Superuser.apk
-rwsr-xr-x root shell 26264 2010-10-16 22:04 su
And with:
Layar-samsung.apk, HRS-Hotel.apk and MiniDiary.apk/.odex removed
I do not really need any of the three removed aplications, so if i have not messed up anything else, i'd rather leave it as is and do my Odin experiments when the XEU Gingerbread comes out
Thanks,
Tobias
P.S.: Thanks for moving to Q&A, i overlooked that yesterday night.

Reboot loop after upgrading from CM 10.0 stable to CM 10.1 nightly

Hi
I was running CM 10 stable and on friday I installed CM 10.1 nightly 20130111. I installed after factorty reset, cache and dalvik cache wipe. After rebooting I saw a message that android is upgrading along with "optimising" 96 apps. After finishing optimisation it went to home screen and instantly message "Unfortunatley, the process com.android.phone has stopped" popped up. when I hit ok, it popped up again and again and then phone rebooted.
Now it is stuck in reboot loop.
Please help.
Thanks

transact said:
Hi
I was running CM 10 stable and on friday I installed CM 10.1 nightly 20130111. I installed after factorty reset, cache and dalvik cache wipe. After rebooting I saw a message that android is upgrading along with "optimising" 96 apps. After finishing optimisation it went to home screen and instantly message "Unfortunatley, the process com.android.phone has stopped" popped up. when I hit ok, it popped up again and again and then phone rebooted.
Now it is stuck in reboot loop.
Please help.
Thanks
Click to expand...
Click to collapse
Have you tried wiping data again from recovery and then boot?

ishangoyal said:
Have you tried wiping data again from recovery and then boot?
Click to expand...
Click to collapse
Yeah, multiple times.
I tried to flash stock firmware back but I think system is read only now.
When I flashed stockfirmware from samfirmware also with odin and pit file, I was able to go to stock recovery but phone never booted to stock firmware. Then I flashed semaphore . this time I could see semaphore logo and then cyanogenmod animation. Seeing cyanogen animation was a surprise as it should have been wiped when i flashed stockfirmare.
I went to recovery mode again did factory reset, cache wipe, dalvik cache. Then mounted usb and copied latest nightly of 10.1 and gapps to customroms folder on my sdcard.
After copying I rebooted into recovery mode again and selected install from zip on sdcard but to my surprise the new files I copied were not there but the files I deleted were still there.
It seems like phone didn't allow me to alter content of sdcard. To test I mounted the usb storage again and created some dummy files like default.txt, default.ini and default.zip in root of sdcard and deleted some files from my backup files of fuellog folder. After unmounting and going through files on phone I discovered that new files are not there and old files are still present.
Another thing is that I have factory reset multiple times, wiped cache partition and cleared dalvik cache as well but every time I mount usb from recovery I have .android_secure folder filled with my previous apps from CM 10.0, which I think shouldn't be there after factory reset.
So I guess it is something to do with permissions. I have done 'fix permissions' multiple times but that also didn't helped.
One more thing I noticed is that after I flash CM10.1 from old file still in my sdcard, on first boot I get com.phone.android error but then on second boot I saw option to complete action using apex, nova or trebuchet laucnher behing the com.android.phone error. I think I shouldn't see that message as it is suppose to be new install with factory reset.
after I click ok on the error message, the phone reboots again but this time it stuck on cyanogen animation. it never goes past animation on 3rd boot.
I have really no idea what is happening.
Is there a way to reset everything through adb? or reset file permissions? I could access my device using adb but had no idea what I could do or not do.
File system view when phone is booting and stuck at cyanogen animation
Code:
drwxr-xr-x root root 2013-01-15 10:29 acct
-rw-r--r-- root root 614 2013-01-15 10:29 boot.txt
drwxrwx--x system cache 2013-01-15 10:29 cache
-rwxr-x--- root root 264080 2013-01-15 10:29 charger
dr-x------ root root 2013-01-15 10:29 config
lrwxrwxrwx root root 2013-01-15 10:29 d -> /sys/kernel/debug
drwxrwx--x system system 2013-01-11 17:08 data
drwxrwx--x system system 2013-01-15 10:29 datadata
-rw-r--r-- root root 163 2013-01-15 10:29 default.prop
drwxr-xr-x root root 2013-01-15 10:29 dev
drwxr-xr-x radio radio 2013-01-14 21:30 efs
lrwxrwxrwx root root 2013-01-15 10:29 emmc -> /storage/sdcard1
lrwxrwxrwx root root 2013-01-15 10:29 etc -> /system/etc
-rw-r----- root root 568 2013-01-15 10:29 fstab.aries
-rwxr-x--- root root 109484 2013-01-15 10:29 init
-rwxr-x--- root root 555 2013-01-15 10:29 init.aries.gps.rc
-rwxr-x--- root root 5375 2013-01-15 10:29 init.aries.rc
-rwxr-x--- root root 3899 2013-01-15 10:29 init.aries.usb.rc
-rwxr-x--- root root 1238 2013-01-15 10:29 init.cm.rc
-rwxr-x--- root root 2487 2013-01-15 10:29 init.goldfish.rc
-rwxr-x--- root root 18768 2013-01-15 10:29 init.rc
-rwxr-x--- root root 1795 2013-01-15 10:29 init.trace.rc
-rwxr-x--- root root 3915 2013-01-15 10:29 init.usb.rc
-rw-r--r-- root root 340 2013-01-15 10:29 lpm.rc
drwxr-xr-x root root 2013-01-14 22:02 lvm
drwxrwxr-x root system 2013-01-15 10:29 mnt
dr-xr-xr-x root root 1970-01-01 10:00 proc
drwxr-xr-x root root 2013-01-14 21:28 radio
drwxr-xr-x root root 2013-01-15 10:29 res
drwxr-x--- root root 2013-01-15 10:29 sbin
lrwxrwxrwx root root 2013-01-15 10:29 sdcard -> /storage/sdcard0
d---r-x--- root sdcard_r 2013-01-15 10:29 storage
drwxr-xr-x root root 2013-01-15 10:29 sys
drwxr-xr-x root root 2013-01-11 17:01 system
-rw-r--r-- root root 1489 2013-01-15 10:29 ueventd.aries.rc
-rw-r--r-- root root 272 2013-01-15 10:29 ueventd.goldfish.rc
-rw-r--r-- root root 5220 2013-01-15 10:29 ueventd.rc
lrwxrwxrwx root root 2013-01-15 10:29 vendor -> /system/vendor
file system view when in recovery
Code:
drwxr-xr-x 18 root root 0 Jan 15 00:12 .
drwxr-xr-x 18 root root 0 Jan 15 00:12 ..
drwxr-xr-x 3 root root 0 Jan 15 00:12 acct
-rw-r--r-- 1 root root 586 Jan 15 00:12 boot.txt
drwxrwx--x 1 system cache 4096 Jan 14 23:29 cache
-rwxr-x--- 1 root root 264080 Jan 15 00:12 charger
dr-x------ 2 root root 0 Jan 15 00:12 config
lrwxrwxrwx 1 root root 17 Jan 15 00:12 d -> /sys/kernel/debug
drwxrwx--x 12 system system 0 Jan 15 00:12 data
-rw-r--r-- 1 root root 2887 Jan 15 00:12 default.prop
drwxr-xr-x 13 root root 3040 Jan 15 00:12 dev
drwxr-xr-x 2 root root 0 Jan 15 00:12 efs
d--------- 2 system system 0 Jan 15 00:12 emmc
drwxr-xr-x 2 root root 0 Jan 15 00:12 etc
-rw-r----- 1 root root 568 Jan 15 00:12 fstab.aries
-rwxr-x--- 1 root root 109484 Jan 15 00:12 init
-rwxr-x--- 1 root root 10349 Jan 15 00:12 init.rc
-rw-r--r-- 1 root root 340 Jan 15 00:12 lpm.rc
drwxr-xr-x 4 root root 0 Jan 14 11:02 lvm
dr-xr-xr-x 73 root root 0 Jan 1 1970 proc
drwxr-xr-x 3 root root 0 Jan 15 00:12 res
drwxr-x--- 2 root root 0 Jan 15 00:12 sbin
d--------- 2 system system 0 Jan 15 00:12 sdcard
drwxr-xr-x 12 root root 0 Jan 15 00:12 sys
drwxr-xr-x 3 root root 0 Jan 15 00:12 system
drwxr-xr-x 2 root root 0 Jan 15 00:12 tmp
-rw-r--r-- 1 root root 1489 Jan 15 00:12 ueventd.aries.rc
-rw-r--r-- 1 root root 272 Jan 15 00:12 ueventd.goldfish.rc
-rw-r--r-- 1 root root 5220 Jan 15 00:12 ueventd.rc
-rw-r--r-- 1 root root 3899 Jan 15 00:12 usb.rc
lrwxrwxrwx 1 root root 14 Jan 15 00:12 vendor -> /system/vendor
I hope they give some kind of clue.
please help.
thanks

transact said:
Yeah, multiple times.
I hope they give some kind of clue.
please help.
thanks
Click to expand...
Click to collapse
That's a really weird and detailed explanation .. however I am unable to explain the behaviour of your phone.. what I can suggest is formating the sd card too (if you have backup of data that is) and format /system too manually along with wiping data, cache and dalvik cache.. after that flash CM10.1 nightly twice.. don't flash gapps atm.. after that reboot recovery.. wipe data, cache again (not /system this time) and flash nightly again.. fix permissions and then reboot..
I know repetition like this doesn't make much sense but nor does your problem..
Hope this will help.

if you are comeing from cm10.0 ant flashing cm10.1 it is recommend to wipe /system befor flashing

Boot loop, problems with recovery

Hello,
I recently unlocked my bootloader and went to install a custom rom with Clockwork Recovery. It got stuck on the HTC boot screen (using an M7), and it would not move. I hard booted the device, and it corrupted my data.
Now, when going into CWM, the device reboots. I have tried reflashing CWM to no avail, so I then tried flashing TWRP. TWRP cannot mount any partition other than system. Problematically, I cannot get adb to recognize my device when in recovery (on multiple computers) but can get fastboot to detect it.
I cannot get a new image onto my phone via usb to fix it, and I cannot use the following guide (edit, cannot post links yet) to fix my corrupted data as a result. Also, I cannot get the device to show up as mountable storage in windows (I have yet to try Linux) to transfer files to it.
What are my options here?

Update:
I was able to update my "unknown" driver to the HTC diver in windows, and now can see my phone with adb devices.
So, I tried the data corruption fix by loading mkfs.ext4 to it and running :
/tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^extra_isize -m 0 /dev/block/mmcblk0p37
this completed, but now I still cant mount /data/ for some reason.
this is what I get:
ls -l
drwxr-xr-x 2 root root 0 May 10 20:12 cache
drwxr-xr-x 2 root root 0 Jan 1 1970 data
-rw-r--r-- 1 root root 6586 Jan 1 1970 default.prop
drwxr-xr-x 12 root root 3440 May 10 20:12 dev
drwxr-xr-x 2 root root 0 May 10 20:12 etc
-rwxr-x--- 1 root root 105268 Jan 1 1970 init
-rwxr-x--- 1 root root 1670 Jan 1 1970 init.rc
drwxr-xr-x 3 root root 0 Jan 1 1970 license
dr-xr-xr-x 157 root root 0 Jan 1 1970 proc
drwxr-xr-x 5 root root 0 Jan 1 1970 res
drwx------ 2 root root 0 Aug 15 2013 root
drwxr-x--- 2 root root 0 Jan 1 1970 sbin
drwxr-xr-x 2 root root 0 May 10 20:12 sdcard
drwxr-xr-x 2 root root 0 Jan 1 1970 supersu
dr-xr-xr-x 24 root root 0 May 10 20:12 sys
drwxr-xr-x 3 root root 0 Jan 1 1970 system
drwxrwxr-x 2 root shell 0 May 10 20:17 tmp
-rw-r--r-- 1 root root 272 Jan 1 1970 ueventd.goldfish.rc
-rw-r--r-- 1 root root 5075 Jan 1 1970 ueventd.rc
drwxrwxrwx 2 root root 0 May 10 20:12 usb-otg
~ # ←[6nmount data
mount data
mount: mounting /data on ext4 failed: No such file or directory
~ # ←[6nmount /data
mount /data
mount: mounting /data on ext4 failed: No such file or directory
~ # ←[6nexit
exit
Now what?

Hey Wulf,
Sorry I'm still at work but this happened to me once as well. You wiped the OS completely from the phone and somehow corrupted the recovery.
I resolved it by relocking the bootloader and flashing a stock RUU. After it booted stock I unlocked the bootloader again reflashed the custom rom.

wulfsburg said:
What are my options here?
Click to expand...
Click to collapse
my bad, useless contribution / preaching.

nkk71 said:
re-EDIT: you start by reading (a little or a lot)... by reading you will learn... by learning you will acquire knowledge... and by knowledge you will be hopefully to get a lot farther than where you are now.
Click to expand...
Click to collapse
By posting useless crap like this you become a douche bag, when you become a douche bag people disregard your opinion, when people disregard your opinion you become useless to a forum community, when you become useless to a forum community you get eaten by a bear. Don't get eaten by a bear, stop posting useless crap

nicowagner said:
By posting useless crap like this you become a douche bag, when you become a douche bag people disregard your opinion, when people disregard your opinion you become useless to a forum community, when you become useless to a forum community you get eaten by a bear. Don't get eaten by a bear, stop posting useless crap
Click to expand...
Click to collapse
Have removed my post.
Thanks for pointing it out.

No CSC folder in stock MM?

In other ROMs I've edited an XML file in /system/csc to make some changes to the keyboard -- specifically, to display alternate symbols when you press-hold a key. I flashed stock MM tonight and noticed that this folder no longer exists.
I checked the Maximum OvrDriVE MM ROM and it does have this folder with the appropriate file. So what happened to the CSC stuff in stock?

SteveRiley said:
In other ROMs I've edited an XML file in /system/csc to make some changes to the keyboard -- specifically, to display alternate symbols when you press-hold a key. I flashed stock MM tonight and noticed that this folder no longer exists.
I checked the Maximum OvrDriVE MM ROM and it does have this folder with the appropriate file. So what happened to the CSC stuff in stock?
Click to expand...
Click to collapse
which stock firmware you are using?

pvsgh said:
which stock firmware you are using?
Click to expand...
Click to collapse
The one DeeXii posted a couple weeks ago: N910TUVS2EPG2_N910TTMB2EPG2_TMB
http://forum.xda-developers.com/note-4-tmobile/development/stock-n910t-n910tuvu2epe3-6-0-1-t3407018

SteveRiley said:
The one DeeXii posted a couple weeks ago: N910TUVS2EPG2_N910TTMB2EPG2_TMB
http://forum.xda-developers.com/note-4-tmobile/development/stock-n910t-n910tuvu2epe3-6-0-1-t3407018
Click to expand...
Click to collapse
Those are the stock ODIN flashable files. Once you flash it via ODIN you will see CSC folder on your phone under /system directory.

pvsgh said:
Those are the stock ODIN flashable files. Once you flash it via ODIN you will see CSC folder on your phone under /system directory.
Click to expand...
Click to collapse
No CSC folder here.
Code:
[email protected]:/ # [B]ls -al /system[/B]
drwxr-xr-x root root 2016-08-11 23:53 app
drwxr-xr-x root shell 2008-12-31 07:00 bin
-rw-r--r-- root root 8080 2008-12-31 07:00 build.prop
drwxr-xr-x root root 2008-12-31 07:00 cameradata
drwxr-xr-x root root 2016-07-07 07:17 container
drwxr-xr-x root root 2016-08-12 01:00 etc
drwxr-xr-x root root 2008-12-31 07:00 fonts
drwxr-xr-x root root 2016-07-07 07:17 framework
-rw-r--r-- root root 10800 2008-12-31 07:00 kern_sec_info
drwxr-xr-x root root 2016-08-11 23:36 lib
drwx------ root root 1969-12-31 16:00 lost+found
drwxr-xr-x root root 2008-12-31 07:00 media
drwxr-xr-x root root 2016-07-07 07:16 preloadedmdm
drwxr-xr-x root root 2016-08-11 23:52 priv-app
-rw-r--r-- root root 4876860 2008-12-31 07:00 recovery-from-boot.bak
drwxr-xr-x root root 2008-12-31 07:00 saiv
-rw-r--r-- root root 417 2016-07-07 07:36 tima_measurement_info
drwxr-xr-x root root 2008-12-31 07:00 tts
drwxr-xr-x root root 2008-12-31 07:00 usr
drwxr-xr-x root shell 2008-12-31 07:00 vendor
drwxr-xr-x root root 2008-12-31 07:00 voicebargeindata
drwxr-xr-x root root 2008-12-31 07:00 wakeupdata
drwxr-xr-x root shell 2008-12-31 07:00 xbin
And a little bit of searching on /system and /data doesn't reveal anything much:
Code:
[email protected]:/ # [B]find /system -iname '*csc*'[/B]
/system/fonts/CarroisGothicSC-Regular.ttf
/system/lib/libcontrolcsc.so
/system/lib/libsccore_csc.so
/system/priv-app/CSC
/system/priv-app/CSC/CSC.apk
/system/priv-app/CSC/oat/arm/CSC.odex.xz
[email protected]:/ # f[B]ind /data -iname '*csc*'[/B]
/data/data/com.samsung.sec.android.application.csc
/data/data/com.google.android.gms/files/AppDataSearch/main/cur/ds.cscoring
/data/system/cscversion.txt
/data/dalvik-cache/profiles/com.samsung.sec.android.application.csc
/data/dalvik-cache/arm/[email protected]@[email protected]@classes.dex
And this zero-byte file seems odd:
Code:
[email protected]:/ # [B]ls -al /data/system/cscversion.txt[/B]
-rw------- system system 0 2016-08-12 20:03 cscversion.txt
I've flashed the build a couple times now, same results. My procedure:
1. Ensure SuperSU zip is on external SD card
2. Boot TWRP recovery (currently 3.0.2 installed)
3. Wipe every partition except external SD
4. Boot the phone into download mode
5. Odin (3.0.9) the ROM to the phone
6. Odin TWRP back to the phone
7. Boot TWRP recovery
8. Flash SuperSU zip
9. Reboot and let settle for 15 minutes

SteveRiley said:
No CSC folder here.
Code:
[email protected]:/ # [B]ls -al /system[/B]
drwxr-xr-x root root 2016-08-11 23:53 app
drwxr-xr-x root shell 2008-12-31 07:00 bin
-rw-r--r-- root root 8080 2008-12-31 07:00 build.prop
drwxr-xr-x root root 2008-12-31 07:00 cameradata
drwxr-xr-x root root 2016-07-07 07:17 container
drwxr-xr-x root root 2016-08-12 01:00 etc
drwxr-xr-x root root 2008-12-31 07:00 fonts
drwxr-xr-x root root 2016-07-07 07:17 framework
-rw-r--r-- root root 10800 2008-12-31 07:00 kern_sec_info
drwxr-xr-x root root 2016-08-11 23:36 lib
drwx------ root root 1969-12-31 16:00 lost+found
drwxr-xr-x root root 2008-12-31 07:00 media
drwxr-xr-x root root 2016-07-07 07:16 preloadedmdm
drwxr-xr-x root root 2016-08-11 23:52 priv-app
-rw-r--r-- root root 4876860 2008-12-31 07:00 recovery-from-boot.bak
drwxr-xr-x root root 2008-12-31 07:00 saiv
-rw-r--r-- root root 417 2016-07-07 07:36 tima_measurement_info
drwxr-xr-x root root 2008-12-31 07:00 tts
drwxr-xr-x root root 2008-12-31 07:00 usr
drwxr-xr-x root shell 2008-12-31 07:00 vendor
drwxr-xr-x root root 2008-12-31 07:00 voicebargeindata
drwxr-xr-x root root 2008-12-31 07:00 wakeupdata
drwxr-xr-x root shell 2008-12-31 07:00 xbin
And a little bit of searching on /system and /data doesn't reveal anything much:
Code:
[email protected]:/ # [B]find /system -iname '*csc*'[/B]
/system/fonts/CarroisGothicSC-Regular.ttf
/system/lib/libcontrolcsc.so
/system/lib/libsccore_csc.so
/system/priv-app/CSC
/system/priv-app/CSC/CSC.apk
/system/priv-app/CSC/oat/arm/CSC.odex.xz
[email protected]:/ # f[B]ind /data -iname '*csc*'[/B]
/data/data/com.samsung.sec.android.application.csc
/data/data/com.google.android.gms/files/AppDataSearch/main/cur/ds.cscoring
/data/system/cscversion.txt
/data/dalvik-cache/profiles/com.samsung.sec.android.application.csc
/data/dalvik-cache/arm/[email protected]@[email protected]@classes.dex
And this zero-byte file seems odd:
Code:
[email protected]:/ # [B]ls -al /data/system/cscversion.txt[/B]
-rw------- system system 0 2016-08-12 20:03 cscversion.txt
I've flashed the build a couple times now, same results. My procedure:
1. Ensure SuperSU zip is on external SD card
2. Boot TWRP recovery (currently 3.0.2 installed)
3. Wipe every partition except external SD
4. Boot the phone into download mode
5. Odin (3.0.9) the ROM to the phone
6. Odin TWRP back to the phone
7. Boot TWRP recovery
8. Flash SuperSU zip
9. Reboot and let settle for 15 minutes
Click to expand...
Click to collapse
Don't know if it would make any difference but you should be using Odin 3.11.1 with this latest EPG2 firmware. CSC related files reside in cache.img.ext4 , so it is possible that that particular file is not being flashed in your case.

pvsgh said:
Don't know if it would make any difference but you should be using Odin 3.11.1 with this latest EPG2 firmware. CSC related files reside in cache.img.ext4 , so it is possible that that particular file is not being flashed in your case.
Click to expand...
Click to collapse
Hm, you might very well have discovered the cause.
Examining the cache.img.ext4 file on my PC:
Code:
[email protected] ~/junk $ [B]simg2img cache.img.ext4 cache.raw[/B]
[email protected] ~/junk $ [B]sudo mount -t ext4 -o loop cache.raw /mnt[/B]
[email protected] ~/junk $ [B]ls -al /mnt[/B]
total 28
drwxr-xr-x 4 root root 4096 Dec 31 1969 .
drwxr-xr-x 1 root root 122 Dec 24 2015 ..
drwx------ 2 root root 4096 Dec 31 1969 lost+found
drwxrwx--- 2 steve 2001 4096 Jul 7 07:36 recovery
[email protected] ~/junk $ [B]ls -al /mnt/recovery/[/B]
total 82720
drwxrwx--- 2 steve 2001 4096 Jul 7 07:36 .
drwxr-xr-x 4 root root 4096 Dec 31 1969 ..
-rw-r--r-- 1 root root 78 Jul 7 07:36 command
-rw-r--r-- 1 root root 84691365 Jul 7 07:36 sec_csc.zip
[email protected] ~/junk $ [B]unzip -l /mnt/recovery/sec_csc.zip[/B]
Archive: /mnt/recovery/sec_csc.zip
signed by SignApk
Length Date Time Name
--------- ---------- ----- ----
{... many files, including several for system/csc ...}
--------- -------
104784820 113 files
I'm surprised the phone even works!

Hm, experiencing flash write failures. First time was about 15% finished. Second time seems about 95% finished.

Third flash completed. Before rebooting, I flashed TWRP. Then I booted TWRP and installed SuperSU. Booted normally and received the dreaded ddi: mmc_read failed message. Crap. Tried another flashing round, which also completed, and let it boot immediately. The Samsung recovery started (which I have never actually seen before) and ran through an installation cycle of something. After that, the phone booted and once again shows ddi:mmc_read failed. Is this thing kaput now?
----------
EDIT: I power cycled the phone and now it appears to be doing a normal first boot -- I'm staring at the T-Mobile splash and the status light is flickering blue/cyan. Wow!

SteveRiley said:
Third flash completed. Before rebooting, I flashed TWRP. Then I booted TWRP and installed SuperSU. Booted normally and received the dreaded ddi: mmc_read failed message. Crap. Tried another flashing round, which also completed, and let it boot immediately. The Samsung recovery started (which I have never actually seen before) and ran through an installation cycle of something. After that, the phone booted and once again shows ddi:mmc_read failed. Is this thing kaput now?
----------
EDIT: I power cycled the phone and now it appears to be doing a normal first boot -- I'm staring at the T-Mobile splash and the status light is flickering blue/cyan. Wow!
Click to expand...
Click to collapse
Did you use the latest version of ODIN now? Also if the phone looks stuck on T-Mobile logo for longer than 30 mins, then remove the battery from the phone and try to boot again.

pvsgh said:
Did you use the latest version of ODIN now? Also if the phone looks stuck on T-Mobile logo for longer than 30 mins, then remove the battery from the phone and try to boot again.
Click to expand...
Click to collapse
Yep, Odin 3.11.1 worked, but like I wrote before, it took three attempts. Weird.
BTW, not everyone agrees that the version of Odin was the actual problem:
http://forum.xda-developers.com/not...ow-updates-issues-t3415914/page2#post68173468

pvsgh said:
Don't know if it would make any difference but you should be using Odin 3.11.1 with this latest EPG2 firmware. CSC related files reside in cache.img.ext4 , so it is possible that that particular file is not being flashed in your case.
Click to expand...
Click to collapse
Worked like a charm. Now I have wifi calling and secondary characters on my keyboard again!

You'll also notice that Bluetooth tethering is gone. T-Mobile likes to disable that for some reason. I imagine that buried in one of the CSC files is a line you could delete to restore Bluetooth tethering.

Having an issue creating my first Magisk module

I'm trying to create a Magisk module that would replace ALL alarms, notifications and ringtones in the system by my own collection.
I've downloaded the magisk module template, and edited config.sh and module.prop like this:
Code:
MODID=mymediacollection
AUTOMOUNT=true
PROPFILE=false
POSTFSDATA=false
LATESTARTSERVICE=false
print_modname() {
ui_print "==============================="
ui_print " My Media Collection "
ui_print "==============================="
}
REPLACE="
/system/media/audio
"
set_permissions() {
set_perm_recursive $MODPATH 0 0 0755 0644
}
Code:
id=mymediacollection
name=My Media Collection
version=v1.0
versionCode=1
author=Nazgulled
description=A personal collection of alarms, notifications and ringtones.
template=3
Than I've placed my alarms, notifications and ringtones files on a structure like this:
Code:
MyMediaCollection
└───system
└───media
└───audio
├───alarms
├───notifications
└───ringtones
I then installed the module, rebooted my phone and tried to configure new sounds. Alarms were OK, but notifications and ringtones were empty (the list to pick one).
What am I doing wrong?

Could you upload the module zip instead?
Edit: and a Magisk log from when you have the module installed.

Didgeridoohan said:
Could you upload the module zip instead?
Edit: and a Magisk log from when you have the module installed.
Click to expand...
Click to collapse
Where is the log located?

Nazgulled said:
Where is the log located?
Click to expand...
Click to collapse
In the Magisk Manager - Log - Magisk. Save it (upper right corner) and attach it as a file to your post.
---------- Post added at 13:33 ---------- Previous post was at 13:18 ----------
Actually, it could also be interesting to see what's actually in the module after installation. In a terminal emulator, type this and report back:
Code:
su
ls -A -R /magisk/mymediacollection

I don't think you're supposed to use the replace flag...
Sent from my Nexus 6 using Tapatalk

rignfool said:
I don't think you're supposed to use the replace flag...
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Well, if you want to completely clear a folder and only keep the files mounted from the module, that's what you should do...
I'm thinking that it might be that each folder (alarms, notifications, ringtones) need to be added rather than just audio.

Yes, I want to replace everything on those folders, that's why I'm using the REPLACE thing.
I found my issue and I can tell you that replacing the parent folder (instead of each one individually) works just as well. My problem was that I have quite a lot of alarms, notifications and ringtones that make up for a module of around 115Mb and I don't seem to have enough space for this. I found this by removing all sound files but one from each folder and it worked as I expected it.
I'm not sure how will I be able to workaround this besides deleting a few files but the idea was for this module to be a collection of sorts. I'm not sure how to free up space from the "system partition" to be able to install my module because most things shouldn't probably be deleted.

Nazgulled said:
Yes, I want to replace everything on those folders, that's why I'm using the REPLACE thing.
I found my issue and I can tell you that replacing the parent folder (instead of each one individually) works just as well. My problem was that I have quite a lot of alarms, notifications and ringtones that make up for a module of around 115Mb and I don't seem to have enough space for this. I found this by removing all sound files but one from each folder and it worked as I expected it.
I'm not sure how will I be able to workaround this besides deleting a few files but the idea was for this module to be a collection of sorts. I'm not sure how to free up space from the "system partition" to be able to install my module because most things shouldn't probably be deleted.
Click to expand...
Click to collapse
You shouldn't have to free up space on the system partition. The Magisk image is resized accordingly depending on the size of your module and then accommodates that when mounting the files. I just did a test with a 1.5 GB module on my device with 1.1 GB free space in /system. No worries.
Again: It'd be good to see the module in question and also a Magisk log (with verbose logging enabled) with the full, not working, module installed.

@Nazgulled, the problem is that you're actually disabling /system/media/audio. The replace feature is more like a debloater. You use it only when you want to "remove" something from /system. What you did there is like adding things to /system/media/audio and deleting them afterwards. The result is, you guessed it: you just disabled your /system/media/audio folder. To solve the problem, simply remove the line "/system/media/audio" (keep the quotation marks).

VR25 said:
@Nazgulled, the problem is that you're actually disabling /system/media/audio. The replace feature is more like a debloater. You use it only when you want to "remove" something from /system. What you did there is like adding things to /system/media/audio and deleting them afterwards. The result is, you guessed it: you just disabled your /system/media/audio folder. To solve the problem, simply remove the line "/system/media/audio" (keep the quotation marks).
Click to expand...
Click to collapse
Again... No. At least that's not the intended behavior of the replace feature.
This is what @topjohnwu says about putting a .replace file in the folder (which the REPLACE part of config.sh does, you can also do it yourself):
You can think as it wipes the existing folder, and then adds contents to that folder in /system.
Click to expand...
Click to collapse
This is from the wiki thread.
Edit: I haven't actually used that feature of Magisk, so I did some testing. It works just as advertised... Empties out the folder and only keeps the files from the module.

Here's the full module: https://drive.google.com/file/d/0BxKzMVB35Z6RZ2VldEF0eUxRQWM/view?usp=sharing
Here's the log with debug enabled (feels too small but the option is enabled):
** Magisk post-fs mode running...
** Magisk post-fs-data mode running...
/data/magisk_merge.img found
/data/magisk.img found, attempt to merge
Expanding /data/magisk.img to 160M...
/dev/block/loop0 /data/magisk.img
/dev/block/loop1 /data/magisk_merge.img
Merging: sensemediacollection
Merge complete
* Running post-fs-data.d
* Loading core props
* Preparing modules
Analyzing module: /magisk/sensemediacollection
Replace: /system/media/audio
Analyzing module: /magisk/unifiedhostsadblock
Replace with dummy: /system/bin
New file: /system/bin/hosts
* Stage 1: Mount system and vendor mirrors
* Stage 2: Mount dummy skeletons
* Stage 3: Mount module items
* Stage 4: Execute module scripts
post-fs-data: /magisk/xposed/post-fs-data.sh
Xposed: Mount: /magisk/xposed/system/lib64/libsigchain.so
Xposed: Mount: /magisk/xposed/system/lib64/libart.so
Xposed: Mount: /magisk/xposed/system/lib64/libart-disassembler.so
Xposed: Mount: /magisk/xposed/system/lib/libsigchain.so
Xposed: Mount: /magisk/xposed/system/lib/libart.so
Xposed: Mount: /magisk/xposed/system/lib/libart-compiler.so
Xposed: Mount: /magisk/xposed/system/bin/patchoat
Xposed: Mount: /magisk/xposed/system/bin/oatdump
Xposed: Mount: /magisk/xposed/system/bin/dex2oat
Xposed: Mount: /magisk/xposed/system/bin/app_process64
Xposed: Mount: /magisk/xposed/system/bin/app_process32
* Stage 5: Mount mirrored items back to dummy
** Magisk late_start service mode running...
* Enabling systemless hosts file support
* Enabling BusyBox
* Linking binaries to /sbin
* Starting MagiskSU
* Running service.d
* Starting MagiskHide
MagiskHide: Moving and re-linking /sbin binaries
MagiskHide: Removing dangerous read-only system props
MagiskHide: resetprop by nkk71 & topjohnwu
Initializing...
Modify data structure: 'ro.boot.verifiedbootstate'='green'
Existing property: 'ro.boot.verifiedbootstate'='orange'
Recheck property: 'ro.boot.verifiedbootstate'='green'
Done!
MagiskHide: resetprop by nkk71 & topjohnwu
Initializing...
Modify data structure: 'ro.boot.veritymode'='enforcing'
Existing property: 'ro.boot.veritymode'='logging'
Recheck property: 'ro.boot.veritymode'='enforcing'
Done!
MagiskHide: Killing com.google.android.gms.unstable
MagiskHide: Killing pt.novobanco.nbapp
MagiskHide: Killing esi.mobile.android.oneclick
MagiskHide: Starting MagiskHide daemon
MagiskHide: Update process/package list:
MagiskHide: [com.google.android.gms.unstable]
MagiskHide: [pt.novobanco.nbapp]
MagiskHide: [esi.mobile.android.oneclick]
Zygote(0) ns=mnt:[4026534403] Zygote(1) ns=mnt:[4026534404]
MagiskHide: com.google.android.gms.unstable(PID=8923 ns=mnt:[4026534504])
MagiskHide: Unmounted (/sbin)
MagiskHide: Unmounted (/system/xbin)
MagiskHide: Unmounted (/system/bin)
MagiskHide: Unmounted (/magisk)
MagiskHide: Unmounted (/system/etc/hosts)
MagiskHide: Unmounted (/system/lib/libart-compiler.so)
MagiskHide: Unmounted (/system/lib/libart.so)
MagiskHide: Unmounted (/system/lib/libsigchain.so)
MagiskHide: Unmounted (/system/lib64/libart-disassembler.so)
MagiskHide: Unmounted (/system/lib64/libart.so)
MagiskHide: Unmounted (/system/lib64/libsigchain.so)
MagiskHide: Unmounted (/system/media/audio)
MagiskHide: Unmounted (/dev/magisk/mirror/system/bin/app_process32)
MagiskHide: Unmounted (/dev/magisk/mirror/system/bin/app_process64)
MagiskHide: Unmounted (/dev/magisk/mirror/system/bin/dex2oat)
MagiskHide: Unmounted (/dev/magisk/mirror/system/bin/oatdump)
MagiskHide: Unmounted (/dev/magisk/mirror/system/bin/patchoat)
Click to expand...
Click to collapse
But there's definitely something wrong, look at this:
Code:
[email protected]_pmeuhl:/ $ ls -la -R /magisk/sensemediacollection
/magisk/sensemediacollection:
-rw-r--r-- root root 0 2017-06-08 08:35 auto_mount
-rw-r--r-- root root 0 2017-06-08 08:35 module.prop
drwxr-xr-x root root 2017-06-08 08:35 system
/magisk/sensemediacollection/system:
drwxr-xr-x root root 2017-06-08 08:35 media
/magisk/sensemediacollection/system/media:
drwxr-xr-x root root 2017-06-08 08:35 audio
/magisk/sensemediacollection/system/media/audio:
-rw-r--r-- root root 0 2017-06-08 08:35 .replace
drwxr-xr-x root root 2017-06-08 08:35 alarms
/magisk/sensemediacollection/system/media/audio/alarms:
-rw-r--r-- root root 832054 2017-06-08 08:35 12th_Hour.mp3
-rw-r--r-- root root 499844 2017-06-08 08:35 Abraft.mp3
-rw-r--r-- root root 1151452 2017-06-08 08:35 Amazon.mp3
-rw-r--r-- root root 170477 2017-06-08 08:35 Amber.flac
-rw-r--r-- root root 819867 2017-06-08 08:35 Armature.flac
-rw-r--r-- root root 273738 2017-06-08 08:35 Beige.mp3
-rw-r--r-- root root 599740 2017-06-08 08:35 Bricolage.flac
-rw-r--r-- root root 714040 2017-06-08 08:35 Burnish.flac
-rw-r--r-- root root 1008836 2017-06-08 08:35 Calx.flac
-rw-r--r-- root root 247747 2017-06-08 08:35 Cape_Breeze.mp3
-rw-r--r-- root root 1190740 2017-06-08 08:35 Celedon.mp3
-rw-r--r-- root root 306262 2017-06-08 08:35 Chambered.mp3
-rw-r--r-- root root 985104 2017-06-08 08:35 Chartreuse.mp3
-rw-r--r-- root root 1319472 2017-06-08 08:35 Cinnabar.mp3
-rw-r--r-- root root 162561 2017-06-08 08:35 Citrine.mp3
-rw-r--r-- root root 77220 2017-06-08 08:35 Classic.mp3
-rw-r--r-- root root 475953 2017-06-08 08:35 Contrails.mp3
-rw-r--r-- root root 3308834 2017-06-08 08:35 Crocus.flac
-rw-r--r-- root root 482223 2017-06-08 08:35 Cylindrical.mp3
-rw-r--r-- root root 483554 2017-06-08 08:35 Daisy.flac
-rw-r--r-- root root 815161 2017-06-08 08:35 Dammar.flac
-rw-r--r-- root root 200684 2017-06-08 08:35 Degauss.mp3
-rw-r--r-- root root 1279338 2017-06-08 08:35 Encaustic.flac
-rw-r--r-- root root 98996 2017-06-08 08:35 Feverfew.flac
-rw-r--r-- root root 126616 2017-06-08 08:35 Flame.mp3
-rw-r--r-- root root 192577 2017-06-08 08:35 Four_Stringer.mp3
-rw-r--r-- root root 2632405 2017-06-08 08:35 Foxglove.flac
-rw-r--r-- root root 2078064 2017-06-08 08:35 Geometer.flac
-rw-r--r-- root root 130796 2017-06-08 08:35 Gold.mp3
-rw-r--r-- root root 1085063 2017-06-08 08:35 Goldenrod.flac
-rw-r--r-- root root 1579972 2017-06-08 08:35 Gouache.flac
-rw-r--r-- root root 427470 2017-06-08 08:35 Harp_Arp.mp3
-rw-r--r-- root root 243844 2017-06-08 08:35 Icedream.mp3
-rw-r--r-- root root 1552584 2017-06-08 08:35 Intaglio.flac
-rw-r--r-- root root 229434 2017-06-08 08:35 Jade.mp3
-rw-r--r-- root root 346468 2017-06-08 08:35 Lavender.flac
-rw-r--r-- root root 363274 2017-06-08 08:35 Licorice.flac
-rw-r--r-- root root 130719 2017-06-08 08:35 Light.mp3
-rw-r--r-- root root 4172130 2017-06-08 08:35 Marble_Dust.flac
-rw-r--r-- root root 220594 2017-06-08 08:35 Mastic.flac
-rw-r--r-- root root 371881 2017-06-08 08:35 Meniscus.mp3
-rw-r--r-- root root 211044 2017-06-08 08:35 Metal.mp3
-rw-r--r-- root root 1198620 2017-06-08 08:35 Moka.mp3
-rw-r--r-- root root 364007 2017-06-08 08:35 Muesdays.mp3
-rw-r--r-- root root 3031438 2017-06-08 08:35 Olive.flac
-rw-r--r-- root root 60363 2017-06-08 08:35 Palette.flac
-rw-r--r-- root root 316293 2017-06-08 08:35 Pendulum.mp3
-rw-r--r-- root root 897024 2017-06-08 08:35 Polychrome.flac
-rw-r--r-- root root 0 2017-06-08 08:35 Princess.mp3
-rw-r--r-- root root 0 2017-06-08 08:35 Progressive.mp3
-rw-r--r-- root root 0 2017-06-08 08:35 Rajah.mp3
-rw-r--r-- root root 0 2017-06-08 08:35 Rocksteady.mp3
-rw-r--r-- root root 0 2017-06-08 08:35 Rose.flac
-rw-r--r-- root root 0 2017-06-08 08:35 Scarlet.mp3
-rw-r--r-- root root 0 2017-06-08 08:35 Sea_Green.mp3
-rw-r--r-- root root 0 2017-06-08 08:35 Seven_Alarm.mp3
-rw-r--r-- root root 0 2017-06-08 08:35 Signifier.flac
-rw-r--r-- root root 0 2017-06-08 08:35 Simulacrum.flac
-rw-r--r-- root root 0 2017-06-08 08:35 Snowbell.flac
-rw-r--r-- root root 0 2017-06-08 08:35 Steel.mp3
-rw-r--r-- root root 0 2017-06-08 08:35 Taupe.mp3
-rw-r--r-- root root 0 2017-06-08 08:35 Teleologic.flac
-rw-r--r-- root root 0 2017-06-08 08:35 Thalia.flac
-rw-r--r-- root root 0 2017-06-08 08:35 Tides.mp3
-rw-r--r-- root root 0 2017-06-08 08:35 Topaz.mp3
-rw-r--r-- root root 0 2017-06-08 08:35 Tulip.flac
-rw-r--r-- root root 0 2017-06-08 08:35 Turquoise.mp3
-rw-r--r-- root root 0 2017-06-08 08:35 Twilight.mp3
-rw-r--r-- root root 0 2017-06-08 08:35 Very_High.mp3
-rw-r--r-- root root 0 2017-06-08 08:35 Wintergreen.flac
-rw-r--r-- root root 0 2017-06-08 08:35 Wisteria.flac
For some reason, it seems to stop copying files... module.prop is also 0bytes and on Magisk Manager, the module shows as installed but the info is all wrong:
{
"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"
}
As I said, if I add a single file to each of the 3 folders, all of them are copied, module.prop won't be 0 bytes and everything will work just fine.
Not sure what am I doing wrong.

@Nazgulled
There is certainly something wrong... Question is what. I did a quick test (I'm at work and using my daily driver, not gonna do anything crazy ) with your module. I changed it to mount to a test folder in /system (and removed the replace line) and all files were installed and mounted without issue.
I did flash the module through TWRP, so you could try that instead of using the Manager. Sometimes it can have hiccups...
If needed I can do more testing when I get my hands on my play and test device, tonight.

Didgeridoohan said:
I did flash the module through TWRP, so you could try that instead of using the Manager. Sometimes it can have hiccups...
Click to expand...
Click to collapse
With the changes you mentioned above or as-is?

Nazgulled said:
With the changes you mentioned above or as-is?
Click to expand...
Click to collapse
For you it's more useful with as-is...
I'm gonna ask again though if you're sure you want to wipe the entire audio folder? You don't have ui audio in there? You don't have to use the replace part in config.sh. You can just as easily just place a .replace file (mind the dot) in the folders together with your audio files.

Didgeridoohan said:
For you it's more useful with as-is...
I'm gonna ask again though if you're sure you want to wipe the entire audio folder? You don't have ui audio in there? You don't have to use the replace part in config.sh. You can just as easily just place a .replace file (mind the dot) in the folders together with your audio files.
Click to expand...
Click to collapse
You're right, I have an "ui" folder and I want that one to remain there. I'll replace the 3 individual folders instead. Completely forgot about that folder, thanks for the heads-up.
I'll make that change and flash the zip in recovery and see how that goes...

Flashing in recovery worked as expected. Not sure what's wrong with Magisk Manager...