edit try this first if you just want wifi: http://forum.xda-developers.com/showthread.php?t=2151142
I love Sense and Viper ROM. What I don't love is HTC's definition of “unlocked” - so changing my WIFI and Radio firmware is a pain.
I hacked Viper's boot.img to use /etc/firmware rather than the WIFI(x2) + Radio partitions. I can now change my firmware using adb or an install tool => just put/update the files into /etc/firmware. As CM10 ROMs (my 2nd love) use /etc/firmware, you can now use their firmware installers.
This worked for me on my phone - but it is a hack - maybe it will work for others, mabye not. I would not try this if you aren't experienced, as it's totally untested and unverified. If this is a viable solution you'll see refinement and success reports over time.
This might help you get your wifi working with the Viper ROM - if you cannot flash your write protected WIFI partitions
This will make it really easy to change Radios
prerequisites
- Working Viper Install
- Recovery Image working (I used TWRP, but for sure their are others)
- Fastboot working
- adb working
- Ability to diagnose and fix a boot loop
- Guts as this is untried, untested and unverified...
1. Make a backup and copy it off your phone.
I use TWRP and then adb to 'pull' it.
2. Load WIFI firmware and Radio firmware into /etc/firmware - these are most often (*) transparent to Sense ROMS
You need to load the Radio, Wifi (q6) and Wifi (wcnss) firmwares into /etc/firmware. You will have an awsome boot loop later on if you leave something out.
I copied the files with adb, but you can also install zip files:
Radio: The awsome Tecardo's CM10 Radio Collection, use the CM10-Radio-InstallerV1.5.zip - from here.
WIFI (q6 and wcnss): I hacked an installer to use /etc/firmware rather than the partitions see attached file . I shamlessly copied from Zarboz WIFI firmware installer. These are the firmware files that fixed the WIFI authentication problem for me.
Boot into TWRP then install:
Ville.WIFI.Firmware_etcfirmware.RC1.zip
CM10-Radio-InstallerV1.5.zip -> choose the radio you want (
3. Sanity check - Boot Viper and make sure it's still working.
The firmware you just added is most often (*) ignored. You should verify the additional files are in /etc/firmware - adb shell.
Code:
[COLOR="RoyalBlue"][SIZE="2"]bash-4.2$ adb shell
[email protected]/# cd /etc/firmware
[email protected]/etc/firmware#
[email protected]/etc/firmware# ls -al | grep q6
-rw-r--r-- root root 276 2013-02-17 11:15 q6.b00
-rw-r--r-- root root 6580 2013-02-17 11:15 q6.b01
-rw-r--r-- root root 3428272 2013-02-17 11:15 q6.b03
-rw-r--r-- root root 2032526 2013-02-17 11:15 q6.b04
-rw-r--r-- root root 766032 2013-02-17 11:15 q6.b05
-rw-r--r-- root root 13248 2013-02-17 11:15 q6.b06
-rw-r--r-- root root 6856 2013-02-17 11:15 q6.mdt
[email protected]/etc/firmware# ls -al | grep wcnss
-rw-r--r-- root root 212 2013-02-17 11:15 wcnss.b00
-rw-r--r-- root root 6540 2013-02-17 11:15 wcnss.b01
-rw-r--r-- root root 8360 2013-02-17 11:15 wcnss.b02
-rw-r--r-- root root 1787316 2013-02-17 11:15 wcnss.b04
-rw-r--r-- root root 6752 2013-02-17 11:15 wcnss.mdt
[email protected]/etc/firmware#
[email protected]/etc/firmware# ls -al | grep modem
-rw-r--r-- root root 308 2008-08-01 22:00 modem.b00
-rw-r--r-- root root 6600 2008-08-01 22:00 modem.b01
-rw-r--r-- root root 22530448 2008-08-01 22:00 modem.b02
-rw-r--r-- root root 5120129 2008-08-01 22:00 modem.b03
-rw-r--r-- root root 1345816 2008-08-01 22:00 modem.b04
-rw-r--r-- root root 71376 2008-08-01 22:00 modem.b06
-rw-r--r-- root root 717044 2008-08-01 22:00 modem.b07
-rw-r--r-- root root 6908 2008-08-01 22:00 modem.mdt
-rw-r--r-- root root 1044 2008-08-01 22:00 modem_fw.b00
-rw-r--r-- root root 7060 2008-08-01 22:00 modem_fw.b01
-rw-r--r-- root root 2676 2008-08-01 22:00 modem_fw.b02
-rw-r--r-- root root 958928 2008-08-01 22:00 modem_fw.b03
-rw-r--r-- root root 579884 2008-08-01 22:00 modem_fw.b04
-rw-r--r-- root root 239892 2008-08-01 22:00 modem_fw.b05
-rw-r--r-- root root 94208 2008-08-01 22:00 modem_fw.b06
-rw-r--r-- root root 13568 2008-08-01 22:00 modem_fw.b07
-rw-r--r-- root root 11212 2008-08-01 22:00 modem_fw.b08
-rw-r--r-- root root 9596 2008-08-01 22:00 modem_fw.b09
-rw-r--r-- root root 68295 2008-08-01 22:00 modem_fw.b10
-rw-r--r-- root root 118028 2008-08-01 22:00 modem_fw.b13
-rw-r--r-- root root 158676 2008-08-01 22:00 modem_fw.b14
-rw-r--r-- root root 3604 2008-08-01 22:00 modem_fw.b21
-rw-r--r-- root root 28628 2008-08-01 22:00 modem_fw.b22
-rw-r--r-- root root 19424 2008-08-01 22:00 modem_fw.b23
-rw-r--r-- root root 74384 2008-08-01 22:00 modem_fw.b25
-rw-r--r-- root root 50108 2008-08-01 22:00 modem_fw.b26
-rw-r--r-- root root 84588 2008-08-01 22:00 modem_fw.b29
-rw-r--r-- root root 8104 2008-08-01 22:00 modem_fw.mdt
[email protected]/etc/firmware# [/SIZE][/COLOR]
4. Test boot the hacked boot.img
Do a one off download of the hacked boot.img into your phone. It will not over-write the boot.img on the phone, just download it into memory and execute it just this once See attached file
boot into the bootloader for fastboot session:
fastboot boot hackedviperforfirmwarelinks_boot.img
5. Test and post results - either way
Total number of users to try this, that aren't me: 0 be scared
6. Install the hacked boot.img
If your happy and want to keep using the hack. Flash the hacked boot.img.
boot into the bootloader for fastboot session:
fastboot flash boot hackedviperforfirmwarelinks_boot.img
7. To uninstall - remember to do this when you upgrade Viper or restore a ROM
Extract boot.img from ViperOneS_2.0.0.zip - on your linux/windows rig
fastboot flash boot boot.img
(*) note:
The firmware loading mechanisms on Sense ROMs are complicated, RC scripts will search and then link to any salient firmware they might find. Things will depend on what/where and even the case of the filenames!
Caution:
I absolutely 100% guarantee you a boot loop either now or in the future. If you forget to flash the Viper supplied boot.img when you upgrade you'll have a great little recovery excercise! Same goes if you restore a backup. I forgot every time. There probably is some locale specific firmware that I don't know about. If your phone depends on it and it isn't in /etc/firmware then it will boot loop.
Technical Details
I updated the init.target.rc to: see copyright, license banner attached
not mount the firmware partitions: /firmware_radio, /firmware_q6, /firmware_wcnss
softlink above to /etc/firmware
Credit's:
On my screen the entire time was AKToronto's partition list + cat2115
I'd never put a zip file together, so what I've done probably sucks. I shamlessly copied Zarboz's extracted firmware and anything good from his install script, refer.
Nice I will try this later when I switch back to viper rom
Sent from my HTC One S using xda app-developers app
AW: [HACK] ViperOneS2.0.0 boot.img to use /etc/firmware rather than partitions - fix
Nice thanks just what Tecardo and I discussed all the time.
I like your sense of humour in your post. Cheers for making this!
(Although it's quite useless now since we have S-OFF but I'm sure you enjoyed making it!)
sent from viper 2.1
Greeting every1
This is gor Galaxy Core 2 phones ( SM-G355HN )
Been messing about the logo on my GC2. As mentioned it's in the param.lfs (for flashing with Odin) or /dev/block/mmcblk0p13.
You can do it with emulator,root explorer , adb or any other way ...
With the adb :
Code:
C:\ADB>cmd /k cd "C:\ADB\adt-bundle-windows-x86_64-20140702\sdk\platform-tools"
C:\ADB\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>adb shell
[email protected]:/ $ su
su
[email protected]:/ # cat /dev/block/mmcblk0p13>/mnt/extSdCard/param
cat /dev/block/mmcblk0p13>/mnt/extSdCard/param
[email protected]:/ # cd /mnt/extSdCard
cd /mnt/extSdCard
[email protected]:/mnt/extSdCard # ls
ls
Android
Apk's
DCIM
LOST.DIR
bluetooth
device.nng
iGO
iGO primo 9.6.29.404739 - 30 jun 2014
param
[email protected]:/mnt/extSdCard # tar
tar
BusyBox v1.22.1-Stericson (2014-01-25 17:27:18 CET) multi-call binary.
Usage: tar -[cxtZzJjahmvO] [-X FILE] [-T FILE] [-f TARFILE] [-C DIR] [FILE]...
Create, extract, or list files from a tar file
Operation:
c Create
x Extract
t List
f Name of TARFILE ('-' for stdin/out)
C Change to DIR before operation
v Verbose
Z (De)compress using compress
z (De)compress using gzip
J (De)compress using xz
j (De)compress using bzip2
a (De)compress using lzma
O Extract to stdout
h Follow symlinks
m Don't restore mtime
exclude File to exclude
X File with names to exclude
T File with names to include
1|[email protected]:/mnt/extSdCard # tar -t -f param
tar -t -f param
adv-env.img
ani_upload_1_kernel_panic.jpg
ani_upload_2_cp_crash.jpg
ani_upload_3_forced_upload.jpg
ani_upload_4_hardware_reset.jpg
ani_upload_4_smpl.jpg
ani_upload_4_unknown_reset.jpg
ani_upload_4_watchdog_reset.jpg
ani_upload_4_wtsr.jpg
ani_upload_4_wtsr_smpl.jpg
ani_upload_5_user_fault.jpg
ani_upload_6_hsic_disconnected.jpg
download.jpg
download_error.jpg
logo.jpg
lpm.jpg
sud_0.jpg
sud_1.jpg
sud_2.jpg
sud_3.jpg
sud_4.jpg
sud_5.jpg
sud_6.jpg
sud_7.jpg
sud_8.jpg
sud_9.jpg
warning.jpg
[email protected]:/mnt/extSdCard #
After changing logo, messing with photos,sizes of the file and other stuff and when i copy new image and replace the original after booting I get default logo.
The tar files in this case doesn't follow the user and file permissions ?
Have check the image and block after changing logo and image, the image/logo is accepted and installed into, but guess there is some checking or something else while booting. The installed image isn't accepted during boot,guess It's missplaced with the original ("from where ?") or am I missing some other possible way the image is/can be stored ina any other image/partition.
Has any1 tried this with our phone ?
The files for flash the param partition and self flashing archive is included as attachement.
The boot logo (logo.jpg) is the file download.jpg.
The animation "Samsung" is in the /system/media inside bootsamsung.qmg
You can check it via bootanimation in /system/bin, use it via adb or u will have to take the battery out to stop the animation or get to the home screen.
good....some developing for this phone.
I read that the HTC desire 700 have the same SOC as the core2...they have cwm and Twrp...if I dont read bad...maybe we can use some files for the core2.
I play a little with my gilrdfriend core2...and Im trying to make custom recovery...but no luck. I cant play to much cuz of I broke the phone...my GF will kill me.
Boot animation, boot sound ...
Ok, here is the deal for my GC2 Samsung SM-G355HN :
If u have a original firmware (mine is G355HNXXU0ANH3) the boot animation and boot sound are not stored in kernel,ramdisk any other zip (bootanimation ...)
Samsung has made their own qmf's for animation. You can check your bootanimation preferably throught adb with 'bootanimation' in /system/bin/.
If u start the program in phone U'll have to take the battery out to get your phone usable, the animation is top moded aplication.
...In adb mode press just cancel '<Ctrl>+C' or exit/quit adb shell.
Ok, the bootanimation source (qmf's) are in system/media
Code:
C:\ADB\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>adb shell
[email protected]:/ $ cd system/media
cd system/media
[email protected]:/system/media $ ls -l boot*
ls -l boot*
-rw-r--r-- root root 307252 2014-08-27 14:56 bootanimation.zip
-rw-r--r-- root root 2597636 2008-08-01 14:00 bootsamsung.qmg
-rw-r--r-- root root 1213332 2008-08-01 14:00 bootsamsungloop.qmg
-rw-r--r-- root root 49319 2014-08-27 14:56 bootsound.mp3
[email protected]:/system/media $
bootanimation.zip as told doesn't do nothing, some chinese leftover stuff here.
'Bootsamsung.qmg' is the boot file while booting after the end the 'bootsamsungloop.qmg' file is loading/showing until the anroid system is fully loaded and activated.
Check the shutdown.qmg ...
Ok, it took me a little bit to find that the sound is not the usual visible bootsound.mp3.
The animation is only for graphical animation, the boot sound is located in system/media/audio/ui (user interface).
Code:
[email protected]:/system/media/audio/ui $ ls -l
ls -l
-rw-r--r-- root root 7577 2014-08-27 14:56 Alert_on_call.ogg
-rw-r--r-- root root 5146 2014-08-27 14:56 Auto_focus.ogg
-rw-r--r-- root root 571497 2014-08-27 14:56 Birdsong_by_the_Lake.ogg
-rw-r--r-- root root 8059 2014-08-27 14:56 Call_Connect.ogg
-rw-r--r-- root root 6566 2014-08-27 14:56 Cam_Start.ogg
-rw-r--r-- root root 7567 2014-08-27 14:56 Cam_Stop.ogg
-rw-r--r-- root root 6262 2014-08-27 14:56 Camera_Timer.ogg
-rw-r--r-- root root 26266 2014-08-27 14:56 Camera_Timer_2sec.ogg
-rw-r--r-- root root 6210 2014-08-27 14:56 Camera_click_short.ogg
-rw-r--r-- root root 3726 2014-08-27 14:56 Camera_empty.ogg
-rw-r--r-- root root 14351 2014-08-27 14:56 Charger_Connection.ogg
-rw-r--r-- root root 6773 2014-08-27 14:56 Dialer_new.ogg
-rw-r--r-- root root 18648 2014-08-27 14:56 Dock.ogg
-rw-r--r-- root root 786319 2014-08-27 14:56 Fairy_Fountain.ogg
-rw-r--r-- root root 637833 2014-08-27 14:56 Gentle_Spring_Rain.ogg
-rw-r--r-- root root 4713 2014-08-27 14:56 Highlight.ogg
-rw-r--r-- root root 4705 2014-08-27 14:56 HoverPointer.ogg
-rw-r--r-- root root 10937 2014-08-27 14:56 Lock.ogg
-rw-r--r-- root root 6907 2014-08-27 14:56 Lock_none_effect.ogg
-rw-r--r-- root root 8559 2014-08-27 14:56 Lock_tension.ogg
-rw-r--r-- root root 14323 2014-08-27 14:56 LowBattery.ogg
-rw-r--r-- root root 470154 2014-08-27 14:56 Media_preview_Over_the_horizon.ogg
-rw-r--r-- root root 6687 2014-08-27 14:56 New_chat.ogg
-rw-r--r-- root root 97411 2008-08-01 14:00 PowerOn.ogg
-rw-r--r-- root root 11242 2014-08-27 14:56 S_Beam_end.ogg
-rw-r--r-- root root 12070 2014-08-27 14:56 S_Beam_error.ogg
-rw-r--r-- root root 13673 2014-08-27 14:56 S_Beam_start.ogg
-rw-r--r-- root root 9922 2014-08-27 14:56 S_HW_Touch.ogg
-rw-r--r-- root root 4766 2014-08-27 14:56 S_SIP_Backspace.ogg
-rw-r--r-- root root 6830 2014-08-27 14:56 Sent_chat.ogg
-rw-r--r-- root root 558556 2014-08-27 14:56 Serenity.ogg
-rw-r--r-- root root 9520 2014-08-27 14:56 Shutter.ogg
-rw-r--r-- root root 6210 2014-08-27 14:56 Shutter_multiple.ogg
-rw-r--r-- root root 7294 2014-08-27 14:56 SideSync_Connected.ogg
-rw-r--r-- root root 838441 2014-08-27 14:56 Sparkling_Mist.ogg
-rw-r--r-- root root 15785 2014-08-27 14:56 TW_Battery_caution.ogg
-rw-r--r-- root root 8350 2014-08-27 14:56 TW_Call_Disconnect.ogg
-rw-r--r-- root root 4789 2014-08-27 14:56 TW_SIP.ogg
-rw-r--r-- root root 7868 2014-08-27 14:56 TW_Silent_mode_off.ogg
-rw-r--r-- root root 9926 2014-08-27 14:56 TW_Touch.ogg
-rw-r--r-- root root 5515 2014-08-27 14:56 TW_Volume_control.ogg
-rw-r--r-- root root 16795 2014-08-27 14:56 Tap_tension.ogg
-rw-r--r-- root root 5176 2014-08-27 14:56 TextSelection.ogg
-rw-r--r-- root root 816576 2014-08-27 14:56 The_Secret_Forest.ogg
-rw-r--r-- root root 18669 2014-08-27 14:56 Undock.ogg
-rw-r--r-- root root 10939 2014-08-27 14:56 Unlock.ogg
-rw-r--r-- root root 7287 2014-08-27 14:56 Unlock_none_effect.ogg
-rw-r--r-- root root 15468 2014-08-27 14:56 Unlock_tension.ogg
-rw-r--r-- root root 12860 2014-08-27 14:56 Voice_processing.ogg
-rw-r--r-- root root 8038 2014-08-27 14:56 Voice_start.ogg
-rw-r--r-- root root 10141 2014-08-27 14:56 Voice_stop.ogg
-rw-r--r-- root root 10235 2014-08-27 14:56 Zero_Clickr_Ready.ogg
-rw-r--r-- root root 9520 2014-08-27 14:56 camera_click.ogg
-rw-r--r-- root root 13878 2014-08-27 14:56 lens_flare_lock.ogg
-rw-r--r-- root root 4407 2014-08-27 14:56 lens_flare_unlock_silence.ogg
[email protected]:/system/media/audio/ui $
Here and in the /audio/ dir you can insert other music for alarms,notification,ringtones and ui interfaces like :Auto_focus,Undock,Unlock,Camera sounds ...
We are interested in PowerOn.ogg - our boot song
It's the ogg format. Save your favourite boot - Power On sound as PowerOn.ogg in /system/media/audio/ui.
You can do it manually or throught ADB,Terminal emulator :
Here is for the ADB :
First make your /system/ is rw (readwrite) :
Code:
[email protected]:/ $ su
su
[email protected]:/ # mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
[email protected]:/ #
Copy your files to SD root (bootsamsung.qmg,bootsamsungloop.qmg,PowerOn.ogg) or anywhere in the phone, local ADB folder on comp...
overwite *.qmg files in /system/media/ and PowerOn.ogg in /system/media/audio/ui/
Code:
[email protected]:/system/media # cd /storage/extSdCard
cd /storage/extSdCard
[email protected]:/storage/extSdCard # cp bootsamsung.qmg /system/media/bootsamsung.qmg
system/media/bootsamsung.qmg
[email protected]:/storage/extSdCard # cp bootsamsungloop.qmg /system/media/bootsamsungloop.qmg
g /system/media/bootsamsungloop.qmg
[email protected]:/storage/extSdCard # cp PowerOn.ogg /system/media/audio/ui/PowerOn.ogg
m/media/audio/ui/PowerOn.ogg
[email protected]:/storage/extSdCard #
remount back to ro (readonly) and run bootanimation throught adb to check graphic Power ON sequence only:
Code:
[email protected]:/storage/extSdCard # mount -o remount,ro -t ext4 /dev/block/mmcblk0p1 /system
[email protected]:/ # bootanimation
bootanimation
^C
C:\ADB\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>
You can also change the permission of the files before ro remount :
chmod 644 is the primary for those 3 files ( -rw-r--r-- [email protected] ) but not needed if su (#) enabled
Power Off phone and enjoy ... U can change other stuff PowerOff, shutdown ...
Have also provided mine bootanim, loop and sound as update zip recovery package included.
... for now I'm working on to change the boot logo before boot animation.Help or any other infos are mostly wanted.
And about the *.qmg files, check and search the xda, there are lot about it ...
The animations I used are original files from other Samsung devices, PoverOn wav found and converted from the internet.
The update script :
Code:
ui_print("********************************");
ui_print("* StratOS boot animation,sound *");
ui_print("********************************");
ui_print("");
ui_print("For SM-G355H*");
run_program("/xbin/busybox", "mount", "/system");
run_program("/xbin/busybox", "mount", "-o", "rw,remount", "/system", "/system");
ui_print("Deleting files");
delete("/system/media/audio/ui/PowerOn.ogg");
delete("/system/media/bootsamsung.qmg");
delete("/system/media/bootsamsungloop.qmg");
ui_print("Extracting files");
package_extract_dir("system", "/system");
ui_print("");
ui_print("Finished");
run_program("/xbin/sleep", "5");
unmount("/system");
Sent from my SM-G355HN using XDA Free mobile app
StratOS_HTC said:
Ok, here is the deal for my GC2 Samsung SM-G355HN :
If u have a original firmware (mine is G355HNXXU0ANH3) the boot animation and boot sound are not stored in kernel,ramdisk any other zip (bootanimation ...)
Samsung has made their own qmf's for animation. You can check your bootanimation preferably throught adb with 'bootanimation' in /system/bin/.
If u start the program in phone U'll have to take the battery out to get your phone usable, the animation is top moded aplication.
...In adb mode press just cancel '<Ctrl>+C' or exit/quit adb shell.
Ok, the bootanimation source (qmf's) are in system/media
Code:
C:\ADB\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>adb shell
[email protected]:/ $ cd system/media
cd system/media
[email protected]:/system/media $ ls -l boot*
ls -l boot*
-rw-r--r-- root root 307252 2014-08-27 14:56 bootanimation.zip
-rw-r--r-- root root 2597636 2008-08-01 14:00 bootsamsung.qmg
-rw-r--r-- root root 1213332 2008-08-01 14:00 bootsamsungloop.qmg
-rw-r--r-- root root 49319 2014-08-27 14:56 bootsound.mp3
[email protected]:/system/media $
bootanimation.zip as told doesn't do nothing, some chinese leftover stuff here.
'Bootsamsung.qmg' is the boot file while booting after the end the 'bootsamsungloop.qmg' file is loading/showing until the anroid system is fully loaded and activated.
Check the shutdown.qmg ...
Ok, it took me a little bit to find that the sound is not the usual visible bootsound.mp3.
The animation is only for graphical animation, the boot sound is located in system/media/audio/ui (user interface).
Code:
[email protected]:/system/media/audio/ui $ ls -l
ls -l
-rw-r--r-- root root 7577 2014-08-27 14:56 Alert_on_call.ogg
-rw-r--r-- root root 5146 2014-08-27 14:56 Auto_focus.ogg
-rw-r--r-- root root 571497 2014-08-27 14:56 Birdsong_by_the_Lake.ogg
-rw-r--r-- root root 8059 2014-08-27 14:56 Call_Connect.ogg
-rw-r--r-- root root 6566 2014-08-27 14:56 Cam_Start.ogg
-rw-r--r-- root root 7567 2014-08-27 14:56 Cam_Stop.ogg
-rw-r--r-- root root 6262 2014-08-27 14:56 Camera_Timer.ogg
-rw-r--r-- root root 26266 2014-08-27 14:56 Camera_Timer_2sec.ogg
-rw-r--r-- root root 6210 2014-08-27 14:56 Camera_click_short.ogg
-rw-r--r-- root root 3726 2014-08-27 14:56 Camera_empty.ogg
-rw-r--r-- root root 14351 2014-08-27 14:56 Charger_Connection.ogg
-rw-r--r-- root root 6773 2014-08-27 14:56 Dialer_new.ogg
-rw-r--r-- root root 18648 2014-08-27 14:56 Dock.ogg
-rw-r--r-- root root 786319 2014-08-27 14:56 Fairy_Fountain.ogg
-rw-r--r-- root root 637833 2014-08-27 14:56 Gentle_Spring_Rain.ogg
-rw-r--r-- root root 4713 2014-08-27 14:56 Highlight.ogg
-rw-r--r-- root root 4705 2014-08-27 14:56 HoverPointer.ogg
-rw-r--r-- root root 10937 2014-08-27 14:56 Lock.ogg
-rw-r--r-- root root 6907 2014-08-27 14:56 Lock_none_effect.ogg
-rw-r--r-- root root 8559 2014-08-27 14:56 Lock_tension.ogg
-rw-r--r-- root root 14323 2014-08-27 14:56 LowBattery.ogg
-rw-r--r-- root root 470154 2014-08-27 14:56 Media_preview_Over_the_horizon.ogg
-rw-r--r-- root root 6687 2014-08-27 14:56 New_chat.ogg
-rw-r--r-- root root 97411 2008-08-01 14:00 PowerOn.ogg
-rw-r--r-- root root 11242 2014-08-27 14:56 S_Beam_end.ogg
-rw-r--r-- root root 12070 2014-08-27 14:56 S_Beam_error.ogg
-rw-r--r-- root root 13673 2014-08-27 14:56 S_Beam_start.ogg
-rw-r--r-- root root 9922 2014-08-27 14:56 S_HW_Touch.ogg
-rw-r--r-- root root 4766 2014-08-27 14:56 S_SIP_Backspace.ogg
-rw-r--r-- root root 6830 2014-08-27 14:56 Sent_chat.ogg
-rw-r--r-- root root 558556 2014-08-27 14:56 Serenity.ogg
-rw-r--r-- root root 9520 2014-08-27 14:56 Shutter.ogg
-rw-r--r-- root root 6210 2014-08-27 14:56 Shutter_multiple.ogg
-rw-r--r-- root root 7294 2014-08-27 14:56 SideSync_Connected.ogg
-rw-r--r-- root root 838441 2014-08-27 14:56 Sparkling_Mist.ogg
-rw-r--r-- root root 15785 2014-08-27 14:56 TW_Battery_caution.ogg
-rw-r--r-- root root 8350 2014-08-27 14:56 TW_Call_Disconnect.ogg
-rw-r--r-- root root 4789 2014-08-27 14:56 TW_SIP.ogg
-rw-r--r-- root root 7868 2014-08-27 14:56 TW_Silent_mode_off.ogg
-rw-r--r-- root root 9926 2014-08-27 14:56 TW_Touch.ogg
-rw-r--r-- root root 5515 2014-08-27 14:56 TW_Volume_control.ogg
-rw-r--r-- root root 16795 2014-08-27 14:56 Tap_tension.ogg
-rw-r--r-- root root 5176 2014-08-27 14:56 TextSelection.ogg
-rw-r--r-- root root 816576 2014-08-27 14:56 The_Secret_Forest.ogg
-rw-r--r-- root root 18669 2014-08-27 14:56 Undock.ogg
-rw-r--r-- root root 10939 2014-08-27 14:56 Unlock.ogg
-rw-r--r-- root root 7287 2014-08-27 14:56 Unlock_none_effect.ogg
-rw-r--r-- root root 15468 2014-08-27 14:56 Unlock_tension.ogg
-rw-r--r-- root root 12860 2014-08-27 14:56 Voice_processing.ogg
-rw-r--r-- root root 8038 2014-08-27 14:56 Voice_start.ogg
-rw-r--r-- root root 10141 2014-08-27 14:56 Voice_stop.ogg
-rw-r--r-- root root 10235 2014-08-27 14:56 Zero_Clickr_Ready.ogg
-rw-r--r-- root root 9520 2014-08-27 14:56 camera_click.ogg
-rw-r--r-- root root 13878 2014-08-27 14:56 lens_flare_lock.ogg
-rw-r--r-- root root 4407 2014-08-27 14:56 lens_flare_unlock_silence.ogg
[email protected]:/system/media/audio/ui $
Here and in the /audio/ dir you can insert other music for alarms,notification,ringtones and ui interfaces like :Auto_focus,Undock,Unlock,Camera sounds ...
We are interested in PowerOn.ogg - our boot song
It's the ogg format. Save your favourite boot - Power On sound as PowerOn.ogg in /system/media/audio/ui.
You can do it manually or throught ADB,Terminal emulator :
Here is for the ADB :
First make your /system/ is rw (readwrite) :
Code:
[email protected]:/ $ su
su
[email protected]:/ # mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
[email protected]:/ #
Copy your files to SD root (bootsamsung.qmg,bootsamsungloop.qmg,PowerOn.ogg) or anywhere in the phone, local ADB folder on comp...
overwite *.qmg files in /system/media/ and PowerOn.ogg in /system/media/audio/ui/
Code:
[email protected]:/system/media # cd /storage/extSdCard
cd /storage/extSdCard
[email protected]:/storage/extSdCard # cp bootsamsung.qmg /system/media/bootsamsung.qmg
ystem/media/bootsamsung.qmg
[email protected]:/storage/extSdCard # cp bootsamsungloop.qmg /system/media/bootsamsungloop.qmg
g /system/media/bootsamsungloop.qmg
[email protected]:/storage/extSdCard # cp PowerOn.ogg /system/media/audio/ui/PowerOn.ogg
m/media/audio/ui/PowerOn.ogg
[email protected]:/storage/extSdCard #
remount back to ro (readonly) and run bootanimation throught adb to check graphic Power ON sequence only:
Code:
[email protected]:/storage/extSdCard # mount -o remount,ro -t ext4 /dev/block/mmcblk0p1 /system
[email protected]:/ # bootanimation
bootanimation
^C
C:\ADB\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>
You can also change the permission of the files before ro remount :
chmod 644 is the primary for those 3 files ( -rw-r--r-- [email protected] ) but not needed if su (#) enabled
Power Off phone and enjoy ... U can change other stuff PowerOff, shutdown ...
Have also provided mine bootanim, loop and sound as update zip recovery package included.
... for now I'm working on to change the boot logo before boot animation.Help or any other infos are mostly wanted.
And about the *.qmg files, check and search the xda, there are lot about it ...
The animations I used are original files from other Samsung devices, PoverOn wav found and converted from the internet.
The update script :
Code:
ui_print("********************************");
ui_print("* StratOS boot animation,sound *");
ui_print("********************************");
ui_print("");
ui_print("For SM-G355H*");
run_program("/xbin/busybox", "mount", "/system");
run_program("/xbin/busybox", "mount", "-o", "rw,remount", "/system", "/system");
ui_print("Deleting files");
delete("/system/media/audio/ui/PowerOn.ogg");
delete("/system/media/bootsamsung.qmg");
delete("/system/media/bootsamsungloop.qmg");
ui_print("Extracting files");
package_extract_dir("system", "/system");
ui_print("");
ui_print("Finished");
run_program("/xbin/sleep", "5");
unmount("/system");
Sent from my SM-G355HN using XDA Free mobile app
Click to expand...
Click to collapse
Why you use adb? its easy to use a root file manager like ESfilemanager....and just copy and give permissions. Im doing it like that and no problems.......just an idea.
p/s: I send you a PM....I make a zip to deodex the rom...so we can use the TW mods in xda (all the mods are for Deodex roms). I cant test it, but maybe its a good start point to mod the phone.
Thanks for your hardwork! :good:
Cocolopes said:
Why you use adb? its easy to use a root file manager like ESfilemanager....and just copy and give permissions. Im doing it like that and no problems.......just an idea.
p/s: I send you a PM....I make a zip to deodex the rom...so we can use the TW mods in xda (all the mods are for Deodex roms). I cant test it, but maybe its a good start point to mod the phone.
Thanks for your hardwork! :good:
Click to expand...
Click to collapse
Yes it would be great.
Some folders are not visible on different carriers,manufacturers, because they have to be manualy mounted into partition of folder, just like /system/media/, but you can manualy mount it for rw if you know where to link to/mount to.
It's good to post some code to enforce other users to see what's begind ...
Have checked the PM, will try something tomorrow ...
StratOS_HTC said:
Yes it would be great.
Some folders are not visible on different carriers,manufacturers, because they have to be manualy mounted into partition of folder, just like /system/media/, but you can manualy mount it for rw if you know where to link to/mount to.
It's good to post some code to enforce other users to see what's begind ...
Have checked the PM, will try something tomorrow ...
Click to expand...
Click to collapse
well...I just did it...and everything works great. (I have to manualy delete de odex files cuz stock recovery dont use the script to do it in the zip)
now I will try some mods for other samsung phones...
Cocolopes said:
well...I just did it...and everything works great. (I have to manualy delete de odex files cuz stock recovery dont use the script to do it in the zip)
now I will try some mods for other samsung phones...
Click to expand...
Click to collapse
Well after quick view there is I guess an error in update binnary in zip :
Code:
ui_print("------------------------------------------");
ui_print(" Installing Deodexed Apps and Framework ");
ui_print("------------------------------------------");
ui_print(" Deleting odex-files ");
run_program("/sbin/busybox", "mount", "/data");
run_program("/sbin/busybox", "mount", "/system");
package_extract_file("del_odex.sh", "/data/local/tmp/del_odex.sh");
set_perm(0, 0, 0777, "/data/local[COLOR="Red"][B]//[/B][/COLOR]tmp/del_odex.sh");
run_program("/data/local[COLOR="Red"][B]//[/B][/COLOR]tmp/del_odex.sh");
You should manually edit it
the *.sh is :
Code:
#!/sbin/sh
rm -rf /system/app/*.odex
rm -rf /system/framework/*.odex
rm -rf /system/priv-app/*.odex
exit 0
Think in sh U have to set the fs /system/ to rw again before deleting
Yes, thing are doing ok. I could upload the SIO version of latest rom, it contains some usefull apps ... if u want to.
So the update will have to clear those *.odex
StratOS_HTC said:
Well after quick view there is I guess an error in update binnary in zip :
Code:
ui_print("------------------------------------------");
ui_print(" Installing Deodexed Apps and Framework ");
ui_print("------------------------------------------");
ui_print(" Deleting odex-files ");
run_program("/sbin/busybox", "mount", "/data");
run_program("/sbin/busybox", "mount", "/system");
package_extract_file("del_odex.sh", "/data/local/tmp/del_odex.sh");
set_perm(0, 0, 0777, "/data/local[COLOR="Red"][B]//[/B][/COLOR]tmp/del_odex.sh");
run_program("/data/local[COLOR="Red"][B]//[/B][/COLOR]tmp/del_odex.sh");
You should manually edit it
the *.sh is :
Code:
#!/sbin/sh
rm -rf /system/app/*.odex
rm -rf /system/framework/*.odex
rm -rf /system/priv-app/*.odex
exit 0
Think in sh U have to set the fs /system/ to rw again before deleting
Yes, thing are doing ok. I could upload the SIO version of latest rom, it contains some usefull apps ... if u want to.
So the update will have to clear those *.odex
Click to expand...
Click to collapse
Great...I just replace some system apps like systemIU, secSetting, SecSettingProvider and other to get some new options...like 7 effects in lock screen.... so options dont work...and I need to fix it...but Its something....
boot logo ?? where
Trying to get something for boot logo,as mentioned before param have the logo,but this thing doesn't work or it has to be changed.It has to be somewhere in low level of boot sequence.
Messing with decompilation of kernel and bootloader,spl to check for the image.
Boot logo
StratOS_HTC said:
Trying to get something for boot logo,as mentioned before param have the logo,but this thing doesn't work or it has to be changed.It has to be somewhere in low level of boot sequence.
Messing with decompilation of kernel and bootloader,spl to check for the image.
Click to expand...
Click to collapse
As mentioned before, have made a sorted tar ball but it won't work. The file is accepted in block ( dev/block/mmcblk0p13 ), but as told before the logo must be extracted from somwhere else before. The question is from where and why ?
On other Samsung devices it is in the param (dev/block/mmcblk0p13). If any1 wants to check it with odin and create your own tar & md5 checksum feel free to visit : http://www.rwilco12.com/forum/showthread.php?tid=92 but I guess it will be the same .
Buying a beer if some1 get this right or find out where the hell is it ...
mmcblk0p13 - Samsung leftover ?
Update : The param.lfs / PARAM/ mmcblk0p13 is leftover.
Original files ( Even download logo ... ) is/are stored somewhere else.
Have deleted / changed mmvblk0p13 to 0 b file, at boot it shows logo, so the logo must be somwhere in low level.
sboot.bin / SPRDCP.img / SPRDDSP.img / nvitem.bin / hidden.img ???
Help appriciated
Samsung osrc comments delivery notification
[SAMSUNG OSRC COMMENTS DELIVERY NOTIFICATION]
classification : Mobile Phone
model name : SM-G355HN_EUR
Dear Customer,
Thank you for your interest in our product.
There are some proprietary which we developed by ourselves in kernel.
When you make custom ROM, it will be different from our offical ROM because of not opening our proprietary.
Our offical ROM is optimized for our device, so we don't recommand and guarantee to execute custom ROM.
So, we can't officially give you information how to execute or download your custom ROM.
However you can easily find it through internet because there are lot's of information regarding what you want.
It would be appreciated if you can understand our situation.
Please accept our apology for not being able to handle your request up to your satisfaction.
Thank you. Sincerely yours,
Select URL below to evaluate satisfaction for our reply.
http://opensource.samsung.com/satisfaction/mail_satisfaction.do?mailId=???????
----- Original Message -----
Sender : StratOS_HTC#####
Date : 2015-03-21 19:28:42 (GMT+09:00)
Greetings.
I have created the custom rom based on stock release and modified by my needs, even changed kernel,ramdisk and recovery sucessfully.
I have a problem : Cannot find resource to edit boot logo.
The param partition/ param.lfs files are just leftovers. Just want to know where can I find resources to edit boot logo ( not boot animation ).
I'm asking this because I really don't want to get messed with bootloader and other low level boot sources.
I'm just asking for reveal of the resources to edit / how to recompile the boot logo for Samsung G355HN Galaxy Core 2 model.
Waiting for your reply.
Thx in advance.
Regards
Click to expand...
Click to collapse
Samsung Open Source Release Center
http://opensource.samsung.com
need original bootlogo for core 2
StratOS_HTC said:
Greeting every1
This is gor Galaxy Core 2 phones ( SM-G355HN )
Been messing about the logo on my GC2. As mentioned it's in the param.lfs (for flashing with Odin) or /dev/block/mmcblk0p13.
You can do it with emulator,root explorer , adb or any other way ...
With the adb :
Code:
C:\ADB>cmd /k cd "C:\ADB\adt-bundle-windows-x86_64-20140702\sdk\platform-tools"
C:\ADB\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>adb shell
[email protected]:/ $ su
su
[email protected]:/ # cat /dev/block/mmcblk0p13>/mnt/extSdCard/param
cat /dev/block/mmcblk0p13>/mnt/extSdCard/param
[email protected]:/ # cd /mnt/extSdCard
cd /mnt/extSdCard
[email protected]:/mnt/extSdCard # ls
ls
Android
Apk's
DCIM
LOST.DIR
bluetooth
device.nng
iGO
iGO primo 9.6.29.404739 - 30 jun 2014
param
[email protected]:/mnt/extSdCard # tar
tar
BusyBox v1.22.1-Stericson (2014-01-25 17:27:18 CET) multi-call binary.
Usage: tar -[cxtZzJjahmvO] [-X FILE] [-T FILE] [-f TARFILE] [-C DIR] [FILE]...
Create, extract, or list files from a tar file
Operation:
c Create
x Extract
t List
f Name of TARFILE ('-' for stdin/out)
C Change to DIR before operation
v Verbose
Z (De)compress using compress
z (De)compress using gzip
J (De)compress using xz
j (De)compress using bzip2
a (De)compress using lzma
O Extract to stdout
h Follow symlinks
m Don't restore mtime
exclude File to exclude
X File with names to exclude
T File with names to include
1|[email protected]:/mnt/extSdCard # tar -t -f param
tar -t -f param
adv-env.img
ani_upload_1_kernel_panic.jpg
ani_upload_2_cp_crash.jpg
ani_upload_3_forced_upload.jpg
ani_upload_4_hardware_reset.jpg
ani_upload_4_smpl.jpg
ani_upload_4_unknown_reset.jpg
ani_upload_4_watchdog_reset.jpg
ani_upload_4_wtsr.jpg
ani_upload_4_wtsr_smpl.jpg
ani_upload_5_user_fault.jpg
ani_upload_6_hsic_disconnected.jpg
download.jpg
download_error.jpg
logo.jpg
lpm.jpg
sud_0.jpg
sud_1.jpg
sud_2.jpg
sud_3.jpg
sud_4.jpg
sud_5.jpg
sud_6.jpg
sud_7.jpg
sud_8.jpg
sud_9.jpg
warning.jpg
[email protected]:/mnt/extSdCard #
After changing logo, messing with photos,sizes of the file and other stuff and when i copy new image and replace the original after booting I get default logo.
The tar files in this case doesn't follow the user and file permissions ?
Have check the image and block after changing logo and image, the image/logo is accepted and installed into, but guess there is some checking or something else while booting. The installed image isn't accepted during boot,guess It's missplaced with the original ("from where ?") or am I missing some other possible way the image is/can be stored ina any other image/partition.
Has any1 tried this with our phone ?
The files for flash the param partition and self flashing archive is included as attachement.
The boot logo (logo.jpg) is the file download.jpg.
The animation "Samsung" is in the /system/media inside bootsamsung.qmg
You can check it via bootanimation in /system/bin, use it via adb or u will have to take the battery out to stop the animation or get to the home screen.
Click to expand...
Click to collapse
The process seems.quite complicated n i didnt understand..
Will you plz upload the original stock boot logo and procedure to flast it
StratOS_HTC said:
As mentioned before, have made a sorted tar ball but it won't work. The file is accepted in block ( dev/block/mmcblk0p13 ), but as told before the logo must be extracted from somwhere else before. The question is from where and why ?
On other Samsung devices it is in the param (dev/block/mmcblk0p13). If any1 wants to check it with odin and create your own tar & md5 checksum feel free to visit : http://www.rwilco12.com/forum/showthread.php?tid=92 but I guess it will be the same .
Buying a beer if some1 get this right or find out where the hell is it ...
Click to expand...
Click to collapse
Try for boot animation:
framework-res/assets/sounds/bootanim0.raw and bootanim1.raw
about samsung splash boot img:
http://forum.xda-developers.com/galaxy-s2/themes-apps/logo-img-param-lfs-t1315401
Y300-0100 said:
Try for boot animation:
framework-res/assets/sounds/bootanim0.raw and bootanim1.raw
Click to expand...
Click to collapse
Boot animation/boot sounds for our device has allready been changed along time ago in this post by me :
http://forum.xda-developers.com/showpost.php?p=56610974&postcount=3
Y300-0100 said:
about samsung splash boot img:
http://forum.xda-developers.com/galaxy-s2/themes-apps/logo-img-param-lfs-t1315401
Click to expand...
Click to collapse
The splash / lfs is just another leftower. The splash is located in kernel itself. The beer for boot logo for our devices is still in my fridge
http://forum.xda-developers.com/showpost.php?p=59556505&postcount=11
jasbinkarki said:
The process seems.quite complicated n i didnt understand..
Will you plz upload the original stock boot logo and procedure to flast it
Click to expand...
Click to collapse
The "process" is simple, it's not a process. The boot logo is hidden/integrated in lower level kernel
I cannot get source or resource to handle it. So for now still no knowable option how to do it.
Boot anims,boot sounds are simple to change, see previous post in this thread.
BEER :fingers-crossed:
Hey can anyone here will create a custom boot animation in qmg format..
i want windows xp boot animation in qmg format.. i
In the ADB shell as root I get the following results
Code:
/data # ls -la dalvik-cache/
ls -la dalvik-cache
ls: dalvik-cache/[email protected]@[email protected]: No such file or directory
ls: dalvik-cache/[email protected]@[email protected]: No such file or directory
ls: dalvik-cache/[email protected]@[email protected]: No such file or directory
ls: dalvik-cache/[email protected]@[email protected]: No such file or directory
ls: dalvik-cache/[email protected]@[email protected]: No such file or directory
ls: dalvik-cache/[email protected]@[email protected]: No such file or directory
ls: dalvik-cache/[email protected]@[email protected]: No such file or directory
ls: dalvik-cache/[email protected]@[email protected]: No such file or directory
ls: dalvik-cache/[email protected]@[email protected]: No such file or directory
ls: dalvik-cache/[email protected]@[email protected]: No such file or directory
ls: dalvik-cache/[email protected]@[email protected]: No such file or directory
drwxrwx--x 4 root root 57344 Mar 14 12:36 .
drwxrwx--x 41 system system 4096 Mar 15 07:45 ..
drwx--x--x 2 root root 53248 Mar 15 07:45 arm
drwx--x--x 2 system system 20480 Mar 14 20:56 profiles
/data # ls -la property/
ls -la property
ls: property/persist.atvc.allow_res_core: No such file or directory
ls: property/persist.atvc.allow_all_core: No such file or directory
ls: property/persist.radio.adb_log_on: No such file or directory
drwx------ 2 root root 4096 Mar 15 08:25 .
drwxrwx--x 41 system system 4096 Mar 15 07:45 ..
-rw------- 1 root root 1 Jan 2 2009 persist.atvc.adb
-rw------- 1 root root 1 Mar 15 07:45 persist.atvc.allow_res_panic
....
This doesn't seem right. Since /data is an F2FS partition I can't fsck it.
Any ideas on how to get rid of those errors?
What I've tried:
listing (ls), removing, stat'ing, fsck.f2fs'ing, nothing works from the shell.
Is there possibly a better forum to ask this question? I have plenty *nix experience, but am stumped on how to solve this. Normally filechecking tools are necessary but a good one for F2FS doesn't seem available (on Android).
Which ROM are you running on your phone? I'm not sure if that makes a difference since GPE uses ext4 and stock uses f2fs.
I've only run stock KK and L.
In the end I could only solve it by completely wiping the /data partition with dd and reformatting with mkfs.f2fs.
Done from adb shell in recovery.
I dunno how I ended up in this situation but it's solved now.
Running the Brzilian XT1032 ROM now, will reinstall sometime when the EU image is available.
Sent from my XT1032 using XDA Free mobile app
Quark^2 said:
I've only run stock KK and L.
In the end I could only solve it by completely wiping the /data partition with dd and reformatting with mkfs.f2fs.
Done from adb shell in recovery.
I dunno how I ended up in this situation but it's solved now.
Running the Brzilian XT1032 ROM now, will reinstall sometime when the EU image is available.
Sent from my XT1032 using XDA Free mobile app
Click to expand...
Click to collapse
Could you give a link to the file and a list of commands you used?
I'm probably stuck in the same situation as you were.
EvolutionX_4.6_ginkgo-10.0-20200819-0341-OFFICIAL
(same problems with crDroid; stock ROM (Pie) works fine)
Redmi Note 8
Clean install: Format & wipe
After adopting SD and migrating data I'm having some problems. Tested with 2x 128GB cards and 1x 64GB cards, same problems every time. Also tried fresh re-installs with format & wipe, same problems.
When copying files to "/sdcard" (aka "/mnt/runtime/full/emulated", aka "/storage/emulated/0/") I keep getting corrupted directories; directories that I can't write to, I can't delete, I can't move/rename, I can't change permissions, I can't change owner/group. Every time this happens, "df" shows more space being used, but files can't be found.
Problem happens when copying files to adopted storage via "adb push", tar, zip, cpio, and MTP.
I've also tried extracting from a zip file using a GUI app, and also deleting borked directories with a GUI app: No joy.
This is a major problem. This is making it impossible to load up the SD card with the files I need.
Just trying to "adb push" a TitaniumBackup directory to the new phone, and it gets to about 70-80% and then dies with this error:
Code:
adb: error: failed to copy 'TitaniumBackup/com.android.theme.font.xxxx-xxxxxx.apk.gz' to '/sdcard/test/com.android.theme.font.xxxx-xxxxxx.apk.gz': remote couldn't create file: Invalid argument
It keeps dying at slightly different points, but every time it dies it corrupts the directory that I'm copying into; I can't delete it, I can't move/rename it, I can't add anything to it, etc. "df" shows that space is being consumed, but there's no files. The sdcard just keeps getting corrupted, every time.
Code:
rm -rfv test*
rm: test: Directory not empty
rm: test2: Directory not empty
rm: test3: Directory not empty
Code:
find test*
test
test2
test3
Code:
mv test xxx
mv: bad 'test': No such file or directory
Code:
stat test
File: test
Size: 516096 Blocks: 864 IO Blocks: 512 directory
Device: 1fh/31d Inode: 11108 Links: 2
Access: (0771/drwxrwx--x) Uid: ( 0/ root) Gid: ( 1015/sdcard_rw)
Access: 2020-09-03 20:45:01.248588627 +1200
Modify: 2020-09-03 20:50:58.918624257 +1200
Change: 2020-09-03 20:50:58.918624257 +1200
This does nothing:
Code:
find . -inum 11108 -delete
Any ideas?
Linux localhost 4.14.193-QuicksilveR™ #1 SMP PREEMPT Wed Aug 19 05:58:46 CEST 2020 aarch64
Screenshots, error messages while trying to use a GUI tool to extract a zip file.
This is the only type of log entry that I'm seeing consistently when there's a failure (via "adb push"), but I'm also seeing a lot of them when there's no failure:
Code:
[ 09-04 12:27:30.567 891: 891 W//system/bin/adbd ]
type=1400 audit(0.0:26467): avc: denied { search } for comm=73796E6320737663203139 name="oem" dev="mmcblk0p86" ino=45 scontext=u:r:adbd:s0 tcontext=u:object_r:oemfs:s0 tclass=dir permissive=0
And after some testing, it's really trashing the file-system.
Code:
$ du -hcs .
487M .
487M total
df -h .
Filesystem Size Used Avail Use% Mounted on
/mnt/expand/b780ec4a-2dac-4b9e-bf9e-a044afdcad6b/media 118G 61G 57G 52% /storage/emulated
Just me? Any ideas? This is a new phone, and it's really not usable until I get this sorted out.
Code:
pwd
/sdcard
find . \! -type d
<no output>
du -hcs .
4.7M .
4.7M total
df -h .
Filesystem Size Used Avail Use% Mounted on
/mnt/expand/b7cc023f-4716-4010-8078-6a44f560a496/media 118G 82G 36G 70% /storage/emulated
rm -rfv *
rm: test1: Directory not empty
rm: TitaniumBackup: Directory not empty
rm: TitaniumBackup: Directory not empty
rm: TitaniumBackup: Directory not empty
rm: TitaniumBackup: Directory not empty
rm: TitaniumBackup: Directory not empty
rm: TitaniumBackup: Directory not empty
rm: TitaniumBackup: Directory not empty
rm: TitaniumBackup: Directory not empty
rm: TitaniumBackup: Directory not empty
rm: test2: Directory not empty
rm: test3: Directory not empty
rm: test4: Directory not empty
rm: test5: Directory not empty
rm: test6: Directory not empty
rm: test7: Directory not empty
rm: TitaniumBackup: Directory not empty
rm: TitaniumBackup: Directory not empty
find . -exec ls -lhd {} +
drwxrwx--x 20 root sdcard_rw 3.4K 2020-09-04 13:31 .
drwxrwx--x 2 root sdcard_rw 24K 2020-09-04 10:12 ./test1
drwxrwx--x 3 root sdcard_rw 3.4K 2020-09-04 11:34 ./test10
drwxrwx--x 2 root sdcard_rw 500K 2020-09-04 11:40 ./test10/TitaniumBackup
drwxrwx--x 3 root sdcard_rw 3.4K 2020-09-04 11:45 ./test11
drwxrwx--x 2 root sdcard_rw 500K 2020-09-04 11:51 ./test11/TitaniumBackup
drwxrwx--x 3 root sdcard_rw 3.4K 2020-09-04 11:57 ./test12
drwxrwx--x 2 root sdcard_rw 504K 2020-09-04 12:02 ./test12/TitaniumBackup
drwxrwx--x 3 root sdcard_rw 3.4K 2020-09-04 12:09 ./test13
drwxrwx--x 2 root sdcard_rw 504K 2020-09-04 12:15 ./test13/TitaniumBackup
drwxrwx--x 3 root sdcard_rw 3.4K 2020-09-04 12:19 ./test14
drwxrwx--x 2 root sdcard_rw 500K 2020-09-04 12:25 ./test14/TitaniumBackup
drwxrwx--x 3 root sdcard_rw 3.4K 2020-09-04 12:30 ./test15
drwxrwx--x 2 root sdcard_rw 500K 2020-09-04 12:36 ./test15/TitaniumBackup
drwxrwx--x 3 root sdcard_rw 3.4K 2020-09-04 12:40 ./test16
drwxrwx--x 2 root sdcard_rw 500K 2020-09-04 12:47 ./test16/TitaniumBackup
drwxrwx--x 3 root sdcard_rw 3.4K 2020-09-04 13:01 ./test17
drwxrwx--x 2 root sdcard_rw 420K 2020-09-04 13:04 ./test17/TitaniumBackup
drwxrwx--x 3 root sdcard_rw 3.4K 2020-09-04 13:18 ./test19
drwxrwx--x 2 root sdcard_rw 500K 2020-09-04 13:22 ./test19/TitaniumBackup
drwxrwx--x 2 root sdcard_rw 56K 2020-09-04 10:21 ./test2
drwxrwx--x 2 root sdcard_rw 56K 2020-09-04 10:26 ./test3
drwxrwx--x 2 root sdcard_rw 20K 2020-09-04 10:57 ./test4
drwxrwx--x 2 root sdcard_rw 20K 2020-09-04 10:57 ./test5
drwxrwx--x 2 root sdcard_rw 92K 2020-09-04 11:07 ./test6
drwxrwx--x 3 root sdcard_rw 116K 2020-09-04 11:12 ./test7
drwxrwx--x 3 root sdcard_rw 3.4K 2020-09-04 11:20 ./test8
drwxrwx--x 2 root sdcard_rw 500K 2020-09-04 11:26 ./test8/TitaniumBackup
drwxrwx--x 3 root sdcard_rw 3.4K 2020-09-04 11:27 ./test9
drwxrwx--x 2 root sdcard_rw 500K 2020-09-04 11:33 ./test9/TitaniumBackup
Code:
logcat '*:V'
I'm watching the logs in one window, while I get failures in another window. I'm not seeing anything in the logs that corresponds to the failures.
And the sd-card has passed "badblocks" with zero errors.
Nevermind… The problem is being reproduced with stock firmware.
After following these instructions to Enable Adoptable Storage On Mi Phone, I can very consistently reproduce the problem with a stock ROM.
Seems like a hardware fault.
Update: Just got a brand new Redmi Note 8. Out of the box, everything is stock. Same problem with Adata 128GB cards.
I'm trying to get these cards to puke in another machine, but they're testing perfectly.
In the phone, I'm testing with a Lexar 64GB card, and I can't find any problems with it.
Is it possible that these particular Adata cards (brand new!) just aren't compatible with this phone? Is anyone else using 128GB Adata cards with this phone?
I guess I'll have to get a different brand 128GB (or maybe 256GB?) card and do more testing.
And… I got the same error while un-taring 8GB of podcasts. This is with the 64GB Lexar card.
Now what???