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...
Related
This app is confirmed to be working on the tattoo,
now you can root your device at one click and you can unroot also,
yesterday I have tested it, its rooted successfully on my tattoo
instruction:
1. Download the attached apk
2. copy the apk file to your phone device
3. use file explorer & Install
4. open the application in the all program list & hit root
thats it!! your phone is rooted successfully
Note: Added universalAndroot1.6.2 beta5
(Supported Devices):
* Google Nexus One (2.2)
* Google G1 (1.6)
* HTC Hero (2.1)
* HTC Magic (1.5) (Select Do not install Superuser)
* HTC Tattoo (1.6)
* Dell Streak (2.1)
* Motorola Milestone (2.1)
* Motorola XT701
* Motorola XT800 (2.1)
* Motorola ME511
* Motorola Charm
* Motorola Droid (2.01/2.1/2.2 with FRG01B)
* Sony Ericsson X10 (1.6)
* Sony Ericsson X10 Mini (1.6)
* Sony Ericsson X10 Mini Pro (1.6)
* Acer Liquid (2.1)
* Acer beTouch E400 (2.1)
* Samsung Galaxy Beam
* Samsung galaxy 5 (gt-i5500)
* Vibo A688 (1.6)
* Lenovo Lephone (1.6)
* LG GT540 (1.6)
* Gigabyte GSmart G1305
(Not supported):
* Google Nexus One (2.2 FRG33)
* Samsung i9000 / i6500U / i7500 / i5700
* Motorola ME600 / ME501 / MB300 / CLIQ XT
* Motorola 2.2 FRG22D
* Archos 5
* HuaWei U8220
* HTC Desire / Legend / Wildfire (/system 無法寫入, 不過可以靠 Soft Root)
* HTC EVO 4G / Aria
* SonyEricsson X10i R2BA020
* myTouch Slide
Iam not the developer
official thread hear
Works on my Tattoo, no problems install Busybox and Titanium backup that requires root
{
"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"
}
other devices
ofcource it works on others devices also (listed below)
ogle Nexus One (2.2)
HTC Hero (2.1)
HTC Magic (1.5)
Dell Streak (2.1)
Motorola Milestone (2.1)
Motorola XT701
Motorola XT800 (2.1)
Motorola ME511
Sony Ericsson X10 (1.6)
Sony Ericsson X10 Mini Pro (1.6)
Acer Liquid (2.1)
Vibo A688 (1.6)
OK Stuck
ravichandrabr said:
ofcource it works on others devices also (listed below)
Vibo A688 (1.6)
Click to expand...
Click to collapse
hi
pls give more details on how to use the same so the user could easily use the same
and wont have to has u too many questions on the same
good work very nice of u to give help full contribution to the forum
haree said:
hi
pls give more details on how to use the same so the user could easily use the same
and wont have to has u too many questions on the same
good work very nice of u to give help full contribution to the forum
Click to expand...
Click to collapse
Download, install, open app and follow on screen instructions. Couldn't be easier!
Sent from my HTC Tattoo using XDA App
i microwaved my tattoo :/(
basinizadussun said:
i microwaved my tattoo :/(
Click to expand...
Click to collapse
why?
alberto88a said:
why?
Click to expand...
Click to collapse
please be brief everybody, otherwise others can't understand easily, specially noobs..
It doesn't work on my HTC tattoo, I followed instructions on screens but my phone is still not root??
any body know why???
phone is not locked to any network, and it's not branded. Official rom.
ngotova7 said:
It doesn't work on my HTC tattoo, I followed instructions on screens but my phone is still not root??
any body know why???
phone is not locked to any network, and it's not branded. Official rom.
Click to expand...
Click to collapse
it has to root your tattoo, so many users rooted,
do factory reset and try ... don't forget to backup
ravichandrabr said:
it has to root your tattoo, so many users rooted,
do factory reset and try ... don't forget to backup
Click to expand...
Click to collapse
Tnx man, it's working
ngotova7 said:
Tnx man, it's working
Click to expand...
Click to collapse
enjoy buddy
Excellent !!!!!!! i've been waiting for this for such a long time
I tryed to factory reset... and nothing it does not root!? (i think)
because look at the log i asked it for generate:
Version: Universal Androot - v1.6.2 beta
Detected OS version:4
Go for root !
User selected: Cupcake
Trying to get mount point:/system/bin
Preparing Exploit ... :1
Preparing busybox binary ... :1
Preparing Su binary ... :1
Preparing Superuser apk ... :1, resid:2130968581
Preparing root toolkit script ... :1
Trying to get mount point:/data
/dev/block/mtdblock5 /data yaffs2 rw,nosuid,nodev 0 0
Trying to get mount point:/system
/dev/block/mtdblock3 /system yaffs2 ro 0 0
insmod ./tattoo_hack_gf922713.ko
insmod ./tattoo_hack_g6561203.ko
mount -o remount,rw /dev/block/mtdblock3 /system
cat su > /system/bin/su
chmod 04755 /system/bin/su
mount -o remount,ro /dev/block/mtdblock3 /system
insmod ./tattoo_hack_gf922713.ko
insmod ./tattoo_hack_g6561203.ko
mount -o remount,rw /dev/block/mtdblock3 /system
rm /system/bin/su
mount -o remount,rw,nosuid,nodev -t yaffs2 /dev/block/mtdblock5 /data
mount -o remount,ro /dev/block/mtdblock3 /system
Preparing to execute exploit, do chmod
Executing exploit..
cmd: /data/data/com.corner23.android.universalandroot/files/getroot /dev/block/mtdblock5 yaffs2
[*] Android local root exploid (C) The Android Exploid Crew
[*] Modified by shakalaca for various devices
[+] Using basedir=/sqlite_stmt_journals, path=/data/data/com.corner23.android.universalandroot/files/getroot
[+] opening NETLINK_KOBJECT_UEVENT socket
[+] sending add message ...
[*] Try to invoke hotplug now, clicking at the wireless
[*] settings, plugin USB key etc.
[*] You succeeded if you find /system/bin/rootshell.
[*] GUI might hang/restart meanwhile so be patient.
Wifi enabled ...
After wifi, do copy files
insmod: init_module './tattoo_hack_g6561203.ko' failed (Exec format error)
mount: Device or resource busy
ls -l /system/etc
-rw-r--r-- root root 486 2009-11-22 14:39 AudioFilter.csv
-rw-r--r-- root root 232 2009-11-22 14:39 gps.conf
-rw-r--r-- root root 447488 2009-11-22 14:39 WP_0419RUS.db
-rw-r--r-- root root 398336 2009-11-22 14:39 WP_0405CSY.db
-rw-r--r-- root root 2037 2009-11-22 14:39 bookmarks.xml
-rw-r--r-- root root 392192 2009-11-22 14:39 WP_0410ITA.db
-rw-r--r-- root root 463872 2009-11-22 14:39 WP_0408GRK.db
-rw-r--r-- root root 394240 2009-11-22 14:39 WP_0C0AESN.db
-rw-r--r-- root root 567 2009-11-22 14:39 pvplayer.cfg
-rw-r--r-- root root 61495 2009-11-22 14:39 AudioPara_VODA-SFR.csv
-rw-r--r-- root root 2596 2009-11-22 14:39 apversion.txt
-rw-r--r-- root root 396288 2009-11-22 14:39 WP_0413NLD.db
drwxr-xr-x root root 2009-11-22 14:39 ppp
-rw-r--r-- root root 25 2009-11-22 14:39 hosts
drwxr-xr-x root root 2009-11-22 14:39 bluez
-rw-r--r-- root root 64861 2009-11-22 14:39 NOTICE.html.gz
-rw-r--r-- root root 85 2009-11-22 14:39 01_qcomm_omx.cfg
-r--r----- radio audio 61497 2009-11-22 14:39 AudioPara4.csv
drwxr-xr-x root root 2009-11-22 14:39 dhcpcd
-rw-r--r-- root root 7276 2009-11-22 14:39 event-log-tags
-rw-r--r-- root root 1471 2009-11-22 14:39 apns-conf.xml
drwxr-xr-x root root 2009-11-22 14:39 wifi
-rw-r--r-- root root 183 2009-11-22 14:39 pvasflocal.cfg
-rw-r--r-- root root 0 2009-11-22 14:39 apcl.txt
drwxr-xr-x root root 2009-11-22 14:39 security
drwxr-xr-x root root 2009-11-22 14:39 iproute2
-rw-r--r-- root root 369 2009-11-22 14:39 vold.conf
drwxr-xr-x root root 2009-11-22 14:39 clockwidget
-rw-r--r-- root root 3616 2009-11-22 14:39 AudioPreProcess.csv
-r-xr-x--- root shell 1176 2009-11-22 14:39 init.goldfish.sh
-rw-r--r-- root root 401408 2009-11-22 14:39 WP_0804CHS.db
-rw-r--r-- root root 391168 2009-11-22 14:39 WP_0407GER.db
-rw-r--r-- root root 29696 2009-11-22 14:39 timezones.db
-rw-r--r-- root root 392192 2009-11-22 14:39 WP_0409WWE.db
-rw-r--r-- root root 0 2009-11-22 14:39 agps_rm
-rw-r--r-- root root 393216 2009-11-22 14:39 WP_040CFRA.db
-rw-r--r-- root root 401408 2009-11-22 14:39 WP_0404CHT.db
-r--r----- bluetooth bluetooth 935 2009-11-22 14:39 dbus.conf
drwxr-xr-x root root 2009-11-22 14:39 permissions
-rw-r--r-- root root 2907 2009-11-22 14:39 voicemail-conf.xml
-rw-r--r-- root root 398336 2009-11-22 14:39 WP_0415PLK.db
drwxr-xr-x root root 2009-11-22 14:39 firmware
-rw-r--r-- root root 391168 2009-11-22 14:39 WP_0414NOR.db
ls -l /sqlite_stmt_journals
ls -l /data/local/tmp
opendir failed, Permission denied
ls -l /system/bin/reboot
-rwsr-sr-x root shell 5600 2009-11-22 14:39 reboot
cat /proc/sys/kernel/osrelease
2.6.29-gf922713
getprop ro.product.model
HTC Tattoo
getprop ro.product.brand
vodafone_pt
getprop ro.product.name
htc_tattoo
getprop ro.product.manufacturer
HTC
getprop ro.build.product
bahamas
Install rootkit: true
Exploit delete success
install attached apk v1.6.1 n select superuser 1.5 1.6 then hit root that's it...
I. think u tried with android version 1.6.2 its still in. the beta version...
Well i eventually ended up using a puzzle ROM. with root and superuser.
So now i have root i hope, but when i go to use root explorer and mount the system as Rw, and create a new file.. it wont works!? it wont say failed.. but it wont add that file..
like there is no space to add that file..
And i really need to change this file:
/system/etc/wifi/wap_supplicant.conf
Thank you, worked a treat!
THX man very easy use!!!
Great work!!!
this app is really good. Thank so much.
Nice work
NICE.... great work... thank you
Hi,
I bought a brand new samsung galaxy s plus GT-I9001 in Poland (locked to Orange network) and I 'm trying to unlock the phone, but I can't because my phone does not contain the nv_data.bin file in the efs folder.
I have rooted the phone using the tutorial posted in
http://forum.xda-developers.com/wiki/Samsung_Galaxy_S_Plus/GT-I9001#Rooting
I got root access and found that in efs folder I got these files
Code:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
$ su
su
# pwd
pwd
/
# ls -l -a
ls -l -a
drwxrwx--x system system 2012-10-09 15:39 efs
dr-x------ root root 2012-10-10 13:27 config
drwxrwx--- system cache 2012-10-10 13:29 cache
drwxrwx--x system system 1980-01-06 01:00 persist
lrwxrwxrwx root root 2012-10-10 13:27 sdcard -> /mnt/sdcard
drwxr-xr-x root root 2012-10-10 13:27 acct
drwxrwxr-x root system 2012-10-10 13:27 mnt
lrwxrwxrwx root root 2012-10-10 13:27 vendor -> /system/vendor
lrwxrwxrwx root root 2012-10-10 13:27 d -> /sys/kernel/debug
lrwxrwxrwx root root 2012-10-10 13:27 etc -> /system/etc
-rw-r--r-- root root 5610 1970-01-01 01:00 ueventd.rc
-rw-r--r-- root root 0 1970-01-01 01:00 ueventd.goldfish.rc
drwxr-xr-x root root 2012-10-10 12:15 system
drwxr-xr-x root root 2012-10-10 13:27 sys
drwxr-x--- root root 1970-01-01 01:00 sbin
-rw-r--r-- root root 339852 1970-01-01 01:00 recovery
dr-xr-xr-x root root 1970-01-01 01:00 proc
-rw-r--r-- root root 2011 1970-01-01 01:00 lpm.rc
drwxr-xr-x root root 1970-01-01 01:00 lib
-rwxr-x--- root root 24620 1970-01-01 01:00 initlogo.rle
-rwxr-x--- root root 30518 1970-01-01 01:00 init.rc
-rwxr-x--- root root 6900 1970-01-01 01:00 init.qcom.sh
-rwxr-x--- root root 8590 1970-01-01 01:00 init.qcom.rc
-rwxr-x--- root root 1677 1970-01-01 01:00 init.goldfish.rc
-rwxr-x--- root root 106780 1970-01-01 01:00 init
-rw-r--r-- root root 118 1970-01-01 01:00 default.prop
drwxrwx--x system system 2012-10-10 13:27 data
-rw-r--r-- root root 38528 1970-01-01 01:00 charging.rle
-rw-r--r-- root root 22268 1970-01-01 01:00 ARIESVE.rle
drwx------ root root 2011-12-19 08:31 root
drwxr-xr-x root root 2012-10-10 13:35 dev
# cd efs
cd efs
# ls -l -a
ls -l -a
-rw-r--r-- system system 9 2012-10-09 15:39 cryptprop_applied_result
-rw-r--r-- root root 5 2012-10-10 10:51 cryptprop_onetimeboot
-rw-r--r-- system system 1 2012-10-09 15:39 cryptprop_essiv
drwx------ root root 1980-01-06 01:01 lost+found
drwxrwxr-x root root 1980-01-06 01:09 .files
-rw-r--r-- root root 3 2012-10-10 10:51 cryptprop_securewipedata
# cd .files
cd .files
# ls -l -a
ls -l -a
drwxrwxr-x media system 1980-01-06 01:01 .ssh01
-rw-rw-rw- radio radio 2 1980-01-06 01:09 keystr
drwxrwxr-x media system 1980-01-06 01:01 .jck12
drwxrwxr-x media system 1980-01-06 01:01 .dj550
as you can see the efs folder contain cryptprop files which are very small.
The phone works normally, it has its IMEI and connects to GSM network and WiFi network as well. (*#06# returns value 352377055840629)
I'm trying to unlock the phone myself but without nv_data.bin I'm getting nowhere...
Could someone please help me?
PS:
I have changed the stock rom (orange) to XEO rom (I9001XXKPU 2.3.6 and I9001XXKI2 2.3.4) but efs folder is the same each time.
I have checked the init.rc file in the root... ht file looks like this:
Line 56:
mkdir /efs 0771 system system
Line 131 - 135:
mount ext4 /dev/block/mmcblk0p27 /efs nosuid nodev barrier=0
insmod /lib/modules/sec_param.ko
Line 160 - 165:
#efs
chown system system /efs
chmod 0771 /efs
mkdir /efs/.files 0775
# Added for testing DIVX DRM
mkdir /efs/.files/.ssh01 0775
mkdir /efs/.files/.jck12 0775
mkdir /efs/.files/.dj550 0775
chown media system /efs/.files/.ssh01
chown media system /efs/.files/.jck12
chown media system /efs/.files/.dj550
chmod 0775 /efs/.files/.ssh01
chmod 0775 /efs/.files/.jck12
chmod 0775 /efs/.files/.dj550
This init.rc does not create the folders WiFi or Bluetooth like in other device (I checked in a galaxy SII)
The init.rc file is attached.
fcornejo said:
I 'm trying to unlock the phone,
Click to expand...
Click to collapse
It might be easier to use an app or tool from My Android Collections to unlock phone
xsenman said:
It might be easier to use an app or tool from My Android Collections to unlock phone
Click to expand...
Click to collapse
Well thanx, but all the aps and methods require the nv_data.bin file...
fcornejo said:
Well thanx, but all the aps and methods require the nv_data.bin file...
Click to expand...
Click to collapse
have a look at /persist folder.
xsenman said:
have a look at /persist folder.
Click to expand...
Click to collapse
There are files:
Code:
#
# cd persist
cd persist
# ls -l -a
ls -l -a
-rw-r--r-- root root 3468 2011-08-29 00:40 WCN1314_qcom_wlan_nv.bi
-rw-r--r-- root root 3 2011-08-29 00:40 efs_info.bin
drwxr-xr-x root root 2011-09-08 10:14 qcom
-rw-r--r-- root root 1656 2011-08-29 00:40 qcom_wlan_nv.bin
-rw-rw-rw- root root 2 2012-10-10 13:27 sd_det.bin
-rw-rw-rw- root root 1 2012-10-10 12:08 usb_sel.bin
drwxrwxr-x root root 1980-01-06 01:00 .files
-rw-rw-rw- root root 1 1980-01-06 01:00 movinand_checksum_pass
-rw-rw-rw- root root 1 1980-01-06 01:00 movinand_checksum_done
How to fix this update problem
Finding update package.....
Opening update package....
Verifying update package....
Installing update....
Verifying current system.....
System/app/PartnerBookmarksProvider.apk" has unexpected contents
Installation aborted
Write host_mode :0 done
Install TWRP
Place original file
Install stock Recovery again
It's a virus!
My hone was infected and PartnerBookmarksProvider.apk was the app that triggered the virus.
Here is the list of apk that got installed as root (my phone isn't even rooted!)
Thelist is sorted by time. you can see when the app (PartnerBookmarksProvider) got installed the viruses started to flood now I don't even know how to remove them. So think twice before installing it.
Any Idea how to solve it?
-rw-r--r-- root root 2674688 19/08/2016 15:36 KingoUser.apk
-rw-r--r-- root root 31 19/08/2016 17:12 OPBKEY_2d4f7e56b3ef4b45f0b89a9b23696e4bab0d
-rw-r--r-- root root 180224 19/08/2016 17:38 system0816.apk
-rw-r--r-- root root 3080528 16/08/2016 2:59 FB_57.apk
-rw-r--r-- root root 1971150 15/08/2016 18:29 lm-jinwf_mp_14_musicplayer0712.apk
-rw-r--r-- root root 20282 15/08/2016 18:49 com.android.display.apk
-rw-r--r-- root root 294310 15/08/2016 18:49 com.android.telephone.views.apk
-rw-r--r-- root root 119 15/08/2016 19:15 Androidevice
-rw-rw-r-- root root 1205501 15/08/2016 23:08 com.system.cap.qs42.iupdater.apk
-rw-r--r-- root root 6017692 14/08/2016 4:46 lm-Booster_tx01.apk
#NOM? root root 31 12/08/2016 7:41 com.sms.server.socialgraphop.db
-rw-r--r-- root root 1398951 12/08/2016 7:44 com.glb.filemanager.apk
-rw-r--r-- root root 2770328 12/08/2016 8:08 com.beny.compass.apk
-rw-r--r-- root root 857425 12/08/2016 8:09 com.tensor3d.s1.apk
#NOM? root root 51 12/08/2016 9:08 OPBKEY_aiwozhh_18e2a07cbb1acb44f8b8b27bb8654fa21ded
-rw-r--r-- root root 773511 12/08/2016 9:08 cm1.apk
#NOM? root root 31 12/08/2016 9:08 com.aiwozhh.server.socialgraphop.db
-rw-r--r-- root root 32545 12/08/2016 9:18 AndroidFileManger.apk
-rw-r--r-- root root 75232 12/08/2016 9:19 GloablBCServiceInfo.apk
-rw-r--r-- root root 1 12/08/2016 9:19 cd89800001
-rw-r--r-- root root 562737 12/08/2016 9:24 lm-Compass0714.apk
-rw-r--r-- root root 314441 12/08/2016 10:14 yijialing1.apk
-rw-r--r-- root root 53647 12/08/2016 10:18 CertificateInstallerProviders.apk
-rw-r--r-- root root 227958 12/08/2016 10:18 InstallerProtect.apk
-rw-r--r-- root root 4647 12/08/2016 10:20 CameraDevicesOptimization.apk
-rw-r--r-- root root 2771641 12/08/2016 10:43 com.glb.news.apk
-rw-r--r-- root root 2767858 12/08/2016 10:44 com.zhaoy.calculator.apk
-rw-r--r-- root root 2767841 12/08/2016 10:44 com.zhaoy.minifilemanager.apk
-rw-r--r-- root root 3695992 12/08/2016 10:45 Browser.apk
-rw-r--r-- root root 1151352 12/08/2016 10:45 Calculator.apk
-rw-r--r-- root root 2108322 12/08/2016 10:45 Calendar.apk
-rw-r--r-- root root 4954507 12/08/2016 10:45 Email.apk
-rw-r--r-- root root 8921088 12/08/2016 10:45 LatinIME.apk
-rw-r--r-- root root 8423276 12/08/2016 10:45 Maps.apk
-rw-r--r-- root root 8374746 12/08/2016 10:45 YouTube.apk
-rw-r--r-- root root 21112 12/08/2016 10:54 1004.apk
-rw-r--r-- root root 578831 12/08/2016 10:57 system0804.apk
-rw-r--r-- root root 67246 12/08/2016 11:07 web3.0_20160713.apk
-rw-r--r-- root root 251727 12/08/2016 11:24 webcps0615.apk
-rw-r--r-- root root 46788 12/08/2016 11:26 68_20160715.apk
-rw-r--r-- root root 801255 12/08/2016 11:26 admobcps.apk
-rw-r--r-- root root 2911374 12/08/2016 11:41 aisha0725.apk
-rw-r--r-- root root 596372 12/08/2016 19:28 lm-13_FileExplorer10803.apk
-rw-r--r-- root root 978541 12/08/2016 20:36 GoogleUp0812.apk
#NOM? root u0_a 74 6063 09/08/2016 11:44 ChromeCustomizations.apk
#NOM? root u0_a 74 18733 09/08/2016 11:44 PartnerBookmarksProvider.apk
-rw-r--r-- root root 15619975 12/10/2015 3:15 movie.mp4
-rw-r--r-- root root 4904345 12/10/2015 3:16 Gmail2.apk
-rw-r--r-- root root 502096 12/10/2015 3:16 GoogleCalendarSyncAdapter.apk
-rw-r--r-- root root 206547 12/10/2015 3:16 GoogleContactsSyncAdapter.apk
-rw-r--r-- root root 282060 12/10/2015 3:16 frozenkeyboard.apk
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.
I just hope some obe still on stock MM that is rooted at least. Guys im fully porting Nougat to H811 without the need of TMO or LG but i need your help. I need to pull some files from root folder that are auto created once you flash the Stock. With those files i can successfully make this port easier porting wifi calling and Volte. Anything else is just flawlessly working great. Please i need you help with this issue if anyone can.
Thanks
Sent from my LG-H811 using Tapatalk
No but I have backup
If that helps
I am running rooted stock 20v.
Sent from my LG-H811 using XDA-Developers Legacy app
Awesome bro.
Can you see if at root you see a folder name cust or carrier?
Thanks bro
Sent from my LG-H811 using Tapatalk
TecknoFreak said:
Awesome bro.
Can you see if at root you see a folder name cust or carrier?
Thanks bro
Sent from my LG-H811 using Tapatalk
Click to expand...
Click to collapse
Cust yes
Carrier yes
They are empty though
deltadiesel said:
Cust yes
Carrier yes
They are empty though
Click to expand...
Click to collapse
Ok thanks bro
I guess i have to figure this out the hard way. Lol
Sent from my LG-H811 using Tapatalk
TecknoFreak said:
Ok thanks bro
I guess i have to figure this out the hard way. Lol
Sent from my LG-H811 using Tapatalk
Click to expand...
Click to collapse
Unless it deletes on first boot or
Because I'm not actually using T-Mobile service on m T-Mobile 811
I'm not sure.... Never go in there
deltadiesel said:
Unless it deletes on first boot or
Because I'm not actually using T-Mobile service on m T-Mobile 811
I'm not sure.... Never go in there
Click to expand...
Click to collapse
No most likely those files got deleted by either a mod or custom rom
Sent from my LG-H811 using Tapatalk
TecknoFreak said:
No most likely those files got deleted by either a mod or custom rom
Sent from my LG-H811 using Tapatalk
Click to expand...
Click to collapse
My backup is not mod or custom
Its stock lg T-Mobile
deltadiesel said:
My backup is not mod or custom
Its stock lg T-Mobile
Click to expand...
Click to collapse
It doesnt matter once they get deleted the back up will not keep them as those files r located out of the system and they are in root which your backup will not safe
Sent from my LG-H811 using Tapatalk
TecknoFreak said:
It doesnt matter once they get deleted the back up will not keep them as those files r located out of the system and they are in root which your backup will not safe
Sent from my LG-H811 using Tapatalk
Click to expand...
Click to collapse
I guess. If your saying is because I rooted before I made backup theyre not there I guess you are right...but I'm not sure
All I know is I backed up EVERYTHING...including system cache firmware image data dalvik etc
deltadiesel said:
I guess. If your saying is because I rooted before I made backup theyre not there I guess you are right...but I'm not sure
All I know is I backed up EVERYTHING...including system cache firmware image data dalvik etc
Click to expand...
Click to collapse
Yeah that wont back up root\
Sent from my LG-H811 using Tapatalk
My Root folder is empty!
Sent from my LG-H811 using XDA-Developers Legacy app
Waiting4MyAndroid said:
My Root folder is empty!
Sent from my LG-H811 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Ok thanks bro. I will figure it out later if is possible and rhe only way to make that happen with tmo is by reverse engineer a lot of crap which i gave up for now.
Sent from my LG-H811 using Tapatalk
I'm running stock 20R and rooted. I have never installed a ROM on my phone. It's been on 20R since I got the phone and I don't see cust or carrier folder in root. My wife also has a H811 with stock 20R so I'll check her phone later to see if she has them.
probaina said:
I'm running stock 20R and rooted. I have never installed a ROM on my phone. It's been on 20R since I got the phone and I don't see cust or carrier folder in root. My wife also has a H811 with stock 20R so I'll check her phone later to see if she has them.
Click to expand...
Click to collapse
Wow this can be it. Maybe my lucky day. Lol
Can you please check of at root path you see a folder name ../cust ?
Sent from my LG-H811 using Tapatalk
I've checked my phone and my wife's h811 and u can't find ./cust in the root path. Could this be somewhere else? Here's a list if everything that's in mine:
[email protected]:/ $ ls -l
drwxr-xr-x root root 2015-01-22 06:37 acct
drwxrwx--- system cache 2017-09-25 21:20 cache
lrwxrwxrwx root root 1969-12-31 14:00 charger -> /sbin/healthd
dr-x------ root root 2015-01-22 06:37 config
lrwxrwxrwx root root 2015-01-22 06:37 d -> /sys/kernel/debug
drwxrwx--x system system 2017-08-22 04:42 data
-rw-r--r-- root root 546 1969-12-31 14:00 default.prop
drwxr-xr-x root root 2017-09-17 14:37 dev
lrwxrwxrwx root root 2015-01-22 06:37 etc -> /system/etc
-rw-r--r-- root root 77988 1969-12-31 14:00 file_contexts
dr-xr-x--- system system 1969-12-31 14:00 firmware
-rw-r----- root root 1891 1969-12-31 14:00 fstab.fota
-rw-r----- root root 1289 1969-12-31 14:00 fstab.p1
-rwxr-x--- root root 1175792 1969-12-31 14:00 init
-rwxr-x--- root root 4291 1969-12-31 14:00 init.alphap.bt_vendor.rc
-rwxr-x--- root root 3108 1969-12-31 14:00 init.class_main.sh
-rwxr-x--- root root 1478 1969-12-31 14:00 init.environ.rc
-rwxr-x--- root root 1711 1969-12-31 14:00 init.lge.audio.rc
-rwxr-x--- root root 631 1969-12-31 14:00 init.lge.early.rc
-rwxr-x--- root root 1055 1969-12-31 14:00 init.lge.fs.rc
-rwxr-x--- root root 8162 1969-12-31 14:00 init.lge.log.rc
-rwxr-x--- root root 3073 1969-12-31 14:00 init.lge.modem_log.rc
-rwxr-x--- root root 4291 1969-12-31 14:00 init.lge.power.rc
-rwxr-x--- root root 9323 1969-12-31 14:00 init.lge.rc
-rwxr-x--- root root 894 1969-12-31 14:00 init.lge.svelte.rc
-rwxr-x--- root root 774 1969-12-31 14:00 init.lge.usb.default.sh
-rwxr-x--- root root 21023 1969-12-31 14:00 init.lge.usb.rc
-rwxr-x--- root root 6535 1969-12-31 14:00 init.lge.usb.sh
-rwxr-x--- root root 4279 1969-12-31 14:00 init.msm8992.crash.sh
-rwxr-x--- root root 2035 1969-12-31 14:00 init.msm8992.sensor.sh
-rwxr-x--- root root 6464 1969-12-31 14:00 init.msm8992_core.rc
-rwxr-x--- root root 5998 1969-12-31 14:00 init.p1.power.rc
-rwxr-x--- root root 277 1969-12-31 14:00 init.p1.rc
-rwxr-x--- root root 8737 1969-12-31 14:00 init.p1_core.rc
-rwxr-x--- root root 2045 1969-12-31 14:00 init.p1_product.rc
-rwxr-x--- root root 7374 1969-12-31 14:00 init.qcom.class_core.sh
-rwxr-x--- root root 12931 1969-12-31 14:00 init.qcom.factory.sh
-rwxr-x--- root root 30016 1969-12-31 14:00 init.qcom.rc
-rwxr-x--- root root 8545 1969-12-31 14:00 init.qcom.sh
-rwxr-x--- root root 27314 1969-12-31 14:00 init.rc
-rwxr-x--- root root 335 1969-12-31 14:00 init.recovery.p1.rc
-rwxr-x--- root root 10264 1969-12-31 14:00 init.target.rc
-rwxr-x--- root root 387 1969-12-31 14:00 init.time_in_state.sh
-rwxr-x--- root root 1921 1969-12-31 14:00 init.trace.rc
-rwxr-x--- root root 3896 1969-12-31 14:00 init.usb.rc
-rwxr-x--- root root 301 1969-12-31 14:00 init.zygote32.rc
-rwxr-x--- root root 531 1969-12-31 14:00 init.zygote64_32.rc
-rw-r--r-- root root 1143 1969-12-31 14:00 lge.fota.rc
-rw-r--r-- root root 4000 1969-12-31 14:00 lge.fota.update.rc
drwxr-xr-x root system 2015-01-22 06:37 mnt
drwxrwxr-x system system 2016-06-13 14:30 mpt
drwxr-xr-x root root 1969-12-31 14:00 oem
drwxrwx--x system system 2015-01-22 06:37 persist
drwxrwx--x system system 2014-12-31 15:08 persist-lg
dr-xr-xr-x root root 1969-12-31 14:00 proc
-rw-r--r-- root root 18270 1969-12-31 14:00 property_contexts
drwxr-xr-x root root 1969-12-31 14:00 res
drwx------ root root 2017-01-10 18:17 root
drwxr-x--- root root 1969-12-31 14:00 sbin
lrwxrwxrwx root root 2015-01-22 06:37 sdcard -> /storage/self/primary
-rw-r--r-- root root 3825 1969-12-31 14:00 seapp_contexts
-rw-r--r-- root root 7 1969-12-31 14:00 selinux_version
-rw-r--r-- root root 506714 1969-12-31 14:00 sepolicy
-rw-r--r-- root root 19205 1969-12-31 14:00 service_contexts
-rw-r--r-- root root 607 1969-12-31 14:00 set_emmc_size.sh
drwxr-xr-x system system 2014-12-31 15:00 sns
drwxr-xr-x root root 2017-09-17 14:38 storage
drwxr-xr-x root root 2014-12-31 19:47 su
dr-xr-xr-x root root 2015-01-22 06:37 sys
drwxr-xr-x root root 2015-01-01 22:43 system
lrwxrwxrwx root root 2015-01-22 06:37 tombstones -> /data/tombstones
-rw-r--r-- root root 12806 1969-12-31 14:00 ueventd.p1.rc
-rw-r--r-- root root 4845 1969-12-31 14:00 ueventd.rc
lrwxrwxrwx root root 2015-01-22 06:37 vendor -> /system/vendor
[email protected]:/ $
It should be there
I aldo need this folder and the files inside if you have it from stock /root/data/ipsec/