Related
I've installed Fresh ROM on my Evo Shift 4G. It worked for about a week, then the GPS stopped working (a known bug with this device and Gingerbread). I restarted the device as normal, and when it came back up all my downloaded apps and the Market were gone, and the device was in that strange indeterminate state where I'm both synced to a Gmail account and not at the same time (the Setup app appears in the Apps folder). Signing in doesn't help.
I rebooted into Clockwork Recovery (3.2.0.1), wiped data/factory reset, wiped the cache, wiped dalvik, and installed Fresh ROM again.
Once that was complete and booted, I signed in, attempted to install an app and the phone reset. There's no file manager installed nor terminal app so I can't delete things by bash. I connected over USB and tried to adb shell in, but that caused the phone to reset.
I'm stuck. Clearly something has not been properly wiped prior to installing Fresh ROM.
What do I need to do to get out of this loop?
SoopahMan said:
I've installed Fresh ROM on my Evo Shift 4G. It worked for about a week, then the GPS stopped working (a known bug with this device and Gingerbread). I restarted the device as normal, and when it came back up all my downloaded apps and the Market were gone, and the device was in that strange indeterminate state where I'm both synced to a Gmail account and not at the same time (the Setup app appears in the Apps folder). Signing in doesn't help.
I rebooted into Clockwork Recovery (3.2.0.1), wiped data/factory reset, wiped the cache, wiped dalvik, and installed Fresh ROM again.
Once that was complete and booted, I signed in, attempted to install an app and the phone reset. There's no file manager installed nor terminal app so I can't delete things by bash. I connected over USB and tried to adb shell in, but that caused the phone to reset.
I'm stuck. Clearly something has not been properly wiped prior to installing Fresh ROM.
What do I need to do to get out of this loop?
Click to expand...
Click to collapse
Sounds like you either had a bad Flash, a bad Download, or both. So redownload the Rom you choose, then Clear and Flash your device according to THESE INSTRUCTIONS .
Thanks for the response. I downloaded the ROM again and ran a check - identical to the file I downloaded previously. So, if the ROM is the culprit, then the latest version of Fresh ROM for Evo Shift does not work (4.1.1).
I followed the instructions linked, wiping the cache and dalvik-cache twice (why?), and wiping system etc prior to installing the ROM.
I'm running into the exact same issues as before - I can't install anything from the Market, and the phone resets if I connect it to a computer over USB. When it resets, it resets multiple times and when it comes back up the 4G no longer works.
If I rerun the above instructions, the 4G works again, but I'm stuck back in this loop - can't use the Market or connect it over USB or it will reset, so forth.
Could Fresh ROM 4.1.1 for Evo Shift be bad? I still suspect the real problem is something is not sufficiently wiped or setup prior to install.
In case it might help, here's an ls -al after installing Fresh Rom 4.1.1 on my phone (an HTC Evo Shift 4G after following the above install instructions).
/
drwxr-xr-x 2 root root 0 Jan 17 07:39 boot
drwxr-xr-x 4 root root 1024 Jan 17 07:41 cache
drwxrwx--x 2 root root 0 Jan 1 1970 data
drwxr-xr-x 2 root root 0 Jan 17 07:39 datadata
-rw-r--r-- 1 root root 3462 Jan 1 1970 default.prop
drwxr-xr-x 12 root root 3060 Jan 17 07:39 dev
drwxr-xr-x 2 root root 0 Jan 17 07:39 emmc
drwxr-xr-x 2 root root 0 Jan 17 07:39 etc
-rwxr-x--- 1 root root 94372 Jan 1 1970 init
-rwxr-x--- 1 root root 899 Jan 1 1970 init.rc
dr-xr-xr-x 79 root root 0 Jan 1 1970 proc
drwxr-xr-x 4 root root 0 Jan 1 1970 res
drwx------ 2 root root 0 May 15 2011 root
drwxr-x--- 2 root root 0 Jan 1 1970 sbin
drwxr-xr-x 2 root root 0 Jan 17 07:39 sd-ext
drwxrwxrwx 78 root root 32768 Jan 1 1970 sdcard
drwxr-xr-x 18 root root 0 Jan 17 07:39 sys
drwxr-xr-x 3 root root 0 Jan 1 1970 system
drwxr-xr-x 2 root root 0 Jan 17 07:45 tmp
-rw-r--r-- 1 root root 0 Jan 1 1970 ueventd.goldfish.rc
-rw-r--r-- 1 root root 4027 Jan 1 1970 ueventd.rc
-rw-r--r-- 1 root root 987 Jan 1 1970 ueventd.speedy.rc
/data
(empty)
/system
drwxr-xr-x 2 root root 0 Jan 1 1970 bin
/system/bin
(empty)
/sys
drwxr-xr-x 2 root root 0 Jan 17 07:53 android_camera
drwxr-xr-x 2 root root 0 Jan 17 07:53 android_camera_awb_cal
drwxr-xr-x 2 root root 0 Jan 17 07:53 android_touch
drwxr-xr-x 2 root root 0 Jan 17 07:53 block
drwxr-xr-x 2 root root 0 Jan 17 07:39 board_properties
drwxr-xr-x 9 root root 0 Jan 17 07:53 bus
drwxr-xr-x 2 root root 0 Jan 17 07:53 camera_led_status
drwxr-xr-x 47 root root 0 Jan 17 07:53 class
drwxr-xr-x 4 root root 0 Jan 17 07:53 dev
drwxr-xr-x 10 root root 0 Jan 17 07:39 devices
drwxr-xr-x 2 root root 0 Jan 17 07:53 firmware
drwxr-xr-x 3 root root 0 Jan 17 07:53 fs
drwxr-xr-x 6 root root 0 Jan 17 07:53 kernel
drwxr-xr-x 62 root root 0 Jan 17 07:53 module
drwxr-xr-x 2 root root 0 Jan 17 07:53 power
drwxr-xr-x 2 root root 0 Jan 17 07:53 systemlog
I can post more or other diagnostics if others have something to recommend. Really stuck here.
Is it odd that /sd-ext is at root and not located on the SD card, and a directory not a symlink?
Now that you have 10 posts you should try posting your questions in the thread for flipz's rom.So the dev can help and maybe anyone else that is running this rom. Also have you tried the a2sd remove command adb shell or from terminal emulator? See if that helps.
Sent from my PG06100 using Tapatalk
A bit more to isolate the problem:
If the phone resets (due to attempting an install from the Market or plug in from USB), 4G fails - but if I restart the phone at that point, when it reboots 4G works again. So 4G appears to be fine, it's the resets that are at the core of the issue.
I shutdown, removed the SD card, booted, and attempted to install an app and got the same reset, so it's not the SD card - it's definitely a problem somewhere on internal storage.
What else do I need to clear to clear this up?
Fresh ROM's pages say to look in /data/app and /system/app for a place where an app already exists that would cause a conflict.
Here's /data after booting the ROM and setting up a Gmail account:
lrwxrwxrwx 1 root root 14 Jan 17 07:54 app -> /system/sd/app
lrwxrwxrwx 1 root root 22 Jan 17 07:54 app-private -> /system/sd/app-private
drwx------ 5 system system 1024 Jan 6 1980 backup
drwxrwx--x 2 system system 14336 Jan 17 16:25 dalvik-cache
drwxrwx--x 161 system system 9216 Jan 17 07:57 data
drwxr-x--- 2 root log 1024 Jan 17 07:54 dontpanic
lrwxrwxrwx 1 root root 11 Jan 17 07:54 drm -> /data/local
-rw-r--r-- 1 root root 6134 Jan 6 1980 dta2sd.lg1
-rw-r--r-- 1 root root 6266 Jan 6 1980 dta2sd.lg2
-rw-r--r-- 1 root root 6266 Jan 6 1980 dta2sd.log
drwxrwxrwx 2 root root 1024 Jan 17 07:54 htcfs
drwxr-xr-x 4 root root 1024 Jan 17 07:42 jit
drwxrwx--x 4 shell shell 1024 Jan 17 07:54 local
drwxrwx--- 2 root root 12288 Jan 17 07:41 lost+found
drwxrwx--t 10 system misc 1024 Jan 17 07:55 misc
drwx------ 2 root root 1024 Jan 6 1980 property
drwx------ 3 system system 1024 Jan 17 07:55 secure
drwxrwxr-x 9 system system 1024 Jan 17 17:48 system
drwxrwx--- 3 system system 1024 Jan 17 17:14 wimax
I'd like to know if app and app-private are as expected (they appear to be the result of the ROM install, since they were completely wiped prior to installing it). The app symlink is a strange one. It points to /system/sd/app, which I can't cd to. /system/sd I can cd to, and this is all it contains:
-rw-r--r-- 1 root root 17 Aug 1 2008 placeholder
A file named placeholder. What?
I'm starting to suspect apps2sd. None of the relevant partitioning steps are in those install instructions, and they appear to be specific to the apps2sd of CyanogenMod. Google's appears to support a DOS partition, while CyanogenMod's appears to only support an ext3 partition, which I do not have.
At the same time, removing the SD card didn't change things, so color me confused.
As suggested by FdxRider you should definately post up in the Rom thread. That way you can get help resolving the issue from others running the same Rom.
It was apps2sd.
To resolve this problem, I had to:
Reboot into ClockwordModRecovery
Connect the phone to a computer over USB
In Clockwork, choose Mount Storage and choose the last option, Mount USB.
Dump anything I wanted to keep off of the SD card (most importantly, the FreshRom zip file).
Then, back in Clockwork, Advanced>Partition SD
Choose a size (they recommend 1024M)
This wipes out everything on the SD card, creates a Linux partition for apps2sd to use, marks the rest as a Windows partition.
Wait till it's done, then, still from ClockworkModRecovery:
Wipe cache, dalvik cache, system, data
Factory reset
Now Mount USB again so you can copy the FreshRom zip back onto the Windows partition (the only part that will come up on a Windows machine).
Eject on the Windows machine to ensure the copy completes, Unmount in Clockwork.
Install the ROM again
Let it boot, restart
Setup my Google Account/Gmail user
And one final thing:
As it turns out ES File Explorer is pre-installed on this ROM. That means installing it from the Market will make the phone go crazy regardless of proper setup. But I am now able to install other apps just fine from the Market (at last).
reset loop NO clockwork until factory reset
I installed Fresh 4.1.1 on my shift 4g
I went to install ROM Manager got it downloaded and it reset the phone at install.
I even tried going to the website and installing it that way. Same results.
I can't get clockwork to work, when i hold the volume down and then press power nothing happens until i release the power button then it goes directly to the Fresh install.
PLEASE HELP!!!!
---------- Post added at 05:30 AM ---------- Previous post was at 05:09 AM ----------
I got the problem solved. I used the RRU and it walked me through a recovery, part of it was yanking the battery. DUH!
I bought a new TF 700 and the first time I booted the tablet, asked me to install the firmware update.
I did, but when it booted, tried to update camera firmware whitout success.
Then every time I boot the tablet it tries to update the camera firmware for 3 minutes before I can use it.
I am with the last firmware.
How do I fix it?
gian.salvati said:
Then every time I boot the tablet it tries to update the camera firmware for 3 minutes before I can use it.
I am with the last firmware.
How do I fix it?
Click to expand...
Click to collapse
Once updated, the camera version should be TF700T-0xB03400. Does the camera work properly (take pictures and record video)?
xcal321 said:
Once updated, the camera version should be TF700T-0xB03400. Does the camera work properly (take pictures and record video)?
Click to expand...
Click to collapse
The update dont work every time it runs, both cameras dont work as well. The information is to update the firmware first to use it.
Full factory reset
gian.salvati said:
The update dont work every time it runs, both cameras dont work as well. The information is to update the firmware first to use it.
Click to expand...
Click to collapse
I just did a full factory reset on tablet. But the same problem....
Please anyone..help me!
gian.salvati said:
I just did a full factory reset on tablet. But the same problem....
Please anyone..help me!
Click to expand...
Click to collapse
You could try a complete reinstall using the recovery menu. Make sure you have a backup of all important files. You will also require a MicroSD card formatted as FAT32 (I have not tested anything else). If you do not have one check this thread. I recently bought a Kingston 32GB Micro SDHC class 10 from their mobility kit specifically to so a recovery myself and it works right out of the box (it's formatted as FAT32).
Check your SKU version: Settings->About tablet, Build number: JRO03C.<SKU>_epad_<version>-<date>, where <SKU> is either WW, US, CN or TW
Download the latest firmware from the Asus support site (Version V10.4.4.18),
Extract the .zip file, the result will be another zip file (<SKU>_epad-user-10.4.4.18.zip)
Rename the extracted zip to "EP201_768_SDUPDATE.ZIP" (without the " ") and copy it to your MicroSD card
Make sure it's not called *.zip.zip, when you have hide extension on in windows (default; if you haven't changed it, it is on)
Insert the MicroSD card in your tablet and turn it off (Power OFF)
Then press the following button combination: Power ON + volume down (left side) for about 5-7 secs
You now have 10 seconds to press volume down again, this will start the RCK option (recovery)
At this point the device should start updating your firmware and can take about 10 minutes.
xcal321 said:
You could try a complete reinstall using the recovery menu. Make sure you have a backup of all important files. You will also require a MicroSD card formatted as FAT32 (I have not tested anything else). If you do not have one check this thread. I recently bought a Kingston 32GB Micro SDHC class 10 from their mobility kit specifically to so a recovery myself and it works right out of the box (it's formatted as FAT32).
Check your SKU version: Settings->About tablet, Build number: JRO03C.<SKU>_epad_<version>-<date>, where <SKU> is either WW, US, CN or TW
Download the latest firmware from the Asus support site (Version V10.4.4.18),
Extract the .zip file, the result will be another zip file (<SKU>_epad-user-10.4.4.18.zip)
Rename the extracted zip to "EP201_768_SDUPDATE.ZIP" (without the " ") and copy it to your MicroSD card
Make sure it's not called *.zip.zip, when you have hide extension on in windows (default; if you haven't changed it, it is on)
Insert the MicroSD card in your tablet and turn it off (Power OFF)
Then press the following button combination: Power ON + volume down (left side) for about 5-7 secs
You now have 10 seconds to press volume down again, this will start the RCK option (recovery)
At this point the device should start updating your firmware and can take about 10 minutes.
Click to expand...
Click to collapse
I'll try it now!
THANKS A LOT!
gian.salvati said:
I'll try it now!
THANKS A LOT!
Click to expand...
Click to collapse
NO SUCCESS!
Restored the firmware, but the firmware update continues with error
gian.salvati said:
NO SUCCESS!
Restored the firmware, but the firmware update continues with error
Click to expand...
Click to collapse
I don't know if helps, but the firmware files that are in /etc/firmware are:
[email protected]:/etc/firmware/camera $ ls -al
-rw-r--r-- root root 2064384 2012-10-12 01:09 00-RS_M6Mo.bin
-rw-r--r-- root root 524288 2012-10-12 01:09 02-01-000129.bin
-rw-r--r-- root root 524288 2012-10-12 01:09 02-02-000129.bin
-rw-r--r-- root root 524288 2012-10-12 01:09 03-01-000129.bin
-rw-r--r-- root root 524288 2012-10-12 01:09 03-02-000129.bin
-rw-r--r-- root root 2064384 2012-10-12 01:09 04-RS_M6Mo.bin
-rw-r--r-- root root 524288 2012-10-12 01:09 05-01-000129.bin
-rw-r--r-- root root 524288 2012-10-12 01:09 05-02-000129.bin
-rw-r--r-- root root 1048576 2012-10-12 01:09 07-02-030102.bin
Any idea?
gian.salvati said:
I don't know if helps, but the firmware files that are in /etc/firmware are:
[email protected]:/etc/firmware/camera $ ls -al
-rw-r--r-- root root 2064384 2012-10-12 01:09 00-RS_M6Mo.bin
-rw-r--r-- root root 524288 2012-10-12 01:09 02-01-000129.bin
-rw-r--r-- root root 524288 2012-10-12 01:09 02-02-000129.bin
-rw-r--r-- root root 524288 2012-10-12 01:09 03-01-000129.bin
-rw-r--r-- root root 524288 2012-10-12 01:09 03-02-000129.bin
-rw-r--r-- root root 2064384 2012-10-12 01:09 04-RS_M6Mo.bin
-rw-r--r-- root root 524288 2012-10-12 01:09 05-01-000129.bin
-rw-r--r-- root root 524288 2012-10-12 01:09 05-02-000129.bin
-rw-r--r-- root root 1048576 2012-10-12 01:09 07-02-030102.bin
Click to expand...
Click to collapse
Hmm, mine are much older (WW Build 10.4.4.18, 2012-10-12):
Code:
-rw-r--r-- root root 2064384 2012-09-07 11:33 00-RS_M6Mo.bin
-rw-r--r-- root root 524288 2008-08-01 14:00 02-01-000129.bin
-rw-r--r-- root root 524288 2008-08-01 14:00 02-02-000129.bin
-rw-r--r-- root root 524288 2008-08-01 14:00 03-01-000129.bin
-rw-r--r-- root root 524288 2008-08-01 14:00 03-02-000129.bin
-rw-r--r-- root root 2064384 2008-08-01 14:00 04-RS_M6Mo.bin
-rw-r--r-- root root 524288 2008-08-01 14:00 05-01-000129.bin
-rw-r--r-- root root 524288 2008-08-01 14:00 05-02-000129.bin
-rw-r--r-- root root 1048576 2008-08-01 14:00 07-02-030102.bin
Here's the MD5 hash (md5sum /etc/firmware/camera/*), check to see if they are the same
Code:
a7eaf754f8341df1ebe484dc548d2301 /etc/firmware/camera/00-RS_M6Mo.bin
eb77ce2b95346562df259ca52ec66ad6 /etc/firmware/camera/02-01-000129.bin
3a0a589f73d8a41c305e7b774d18f5bb /etc/firmware/camera/02-02-000129.bin
eb77ce2b95346562df259ca52ec66ad6 /etc/firmware/camera/03-01-000129.bin
3a0a589f73d8a41c305e7b774d18f5bb /etc/firmware/camera/03-02-000129.bin
d560c7892cae1f1bfb519101504ba70e /etc/firmware/camera/04-RS_M6Mo.bin
eb77ce2b95346562df259ca52ec66ad6 /etc/firmware/camera/05-01-000129.bin
3a0a589f73d8a41c305e7b774d18f5bb /etc/firmware/camera/05-02-000129.bin
f6f00d4ee4173ef66e8c1aa7bb8789af /etc/firmware/camera/07-02-030102.bin
I've had a look at the kernel source for flashing the camera firmware (kernel-e7f6ff7/drivers/media/video/tegra/fjm6mo.c). It seems 04-RS_M6Mo.bin is the binary for the TF700T camera, 00-RS_M6Mo.bin is for the TF201 camera. I also compared it to the previous firmware (JB .16; no changes) and to the last ICS firmware (.30). Other than removal of some face detection code, there is no change in the way the camera firmware is updated.
So if the MD5 hash of 04-RS_M6Mo.bin is the same, I'd think something is wrong with the camera and would return the TF700T/exchange it for another one.
xcal321 said:
Hmm, mine are much older (WW Build 10.4.4.18, 2012-10-12):
Code:
-rw-r--r-- root root 2064384 2012-09-07 11:33 00-RS_M6Mo.bin
-rw-r--r-- root root 524288 2008-08-01 14:00 02-01-000129.bin
-rw-r--r-- root root 524288 2008-08-01 14:00 02-02-000129.bin
-rw-r--r-- root root 524288 2008-08-01 14:00 03-01-000129.bin
-rw-r--r-- root root 524288 2008-08-01 14:00 03-02-000129.bin
-rw-r--r-- root root 2064384 2008-08-01 14:00 04-RS_M6Mo.bin
-rw-r--r-- root root 524288 2008-08-01 14:00 05-01-000129.bin
-rw-r--r-- root root 524288 2008-08-01 14:00 05-02-000129.bin
-rw-r--r-- root root 1048576 2008-08-01 14:00 07-02-030102.bin
Here's the MD5 hash (md5sum /etc/firmware/camera/*), check to see if they are the same
Code:
a7eaf754f8341df1ebe484dc548d2301 /etc/firmware/camera/00-RS_M6Mo.bin
eb77ce2b95346562df259ca52ec66ad6 /etc/firmware/camera/02-01-000129.bin
3a0a589f73d8a41c305e7b774d18f5bb /etc/firmware/camera/02-02-000129.bin
eb77ce2b95346562df259ca52ec66ad6 /etc/firmware/camera/03-01-000129.bin
3a0a589f73d8a41c305e7b774d18f5bb /etc/firmware/camera/03-02-000129.bin
d560c7892cae1f1bfb519101504ba70e /etc/firmware/camera/04-RS_M6Mo.bin
eb77ce2b95346562df259ca52ec66ad6 /etc/firmware/camera/05-01-000129.bin
3a0a589f73d8a41c305e7b774d18f5bb /etc/firmware/camera/05-02-000129.bin
f6f00d4ee4173ef66e8c1aa7bb8789af /etc/firmware/camera/07-02-030102.bin
I've had a look at the kernel source for flashing the camera firmware (kernel-e7f6ff7/drivers/media/video/tegra/fjm6mo.c). It seems 04-RS_M6Mo.bin is the binary for the TF700T camera, 00-RS_M6Mo.bin is for the TF201 camera. I also compared it to the previous firmware (JB .16; no changes) and to the last ICS firmware (.30). Other than removal of some face detection code, there is no change in the way the camera firmware is updated.
So if the MD5 hash of 04-RS_M6Mo.bin is the same, I'd think something is wrong with the camera and would return the TF700T/exchange it for another one.
Click to expand...
Click to collapse
SAME MD5 for the file 04-RS_M6Mo.bin.
I think I need to send this tablet back to USA .
gian.salvati said:
SAME MD5 for the file 04-RS_M6Mo.bin.
I think I need to send this tablet back to USA .
Click to expand...
Click to collapse
Based on this http://forum.xda-developers.com/showthread.php?t=1861356 report I found this:
<pre>
[email protected]:/system/etc/firmware/camera $ ls
00-RS_M6Mo.bin
02-01-000129.bin
02-02-000129.bin
03-01-000129.bin
03-02-000129.bin
04-RS_M6Mo.bin
05-01-000129.bin
05-02-000129.bin
07-02-030102.bin
[email protected]:/system/etc/firmware/camera $ isp_fw_update -isp
Current fw version in ISP= TF700T-0xFFFFFF
Front Sensor: no definition. Not TF300 or TF500 series?
New camera isp ROM version = TF201-0x9900
Current camera isp version:TF700T-0xFFFFFF
rom_version: TF201-0x9900 isp_version: TF700T-0xFFFFFF
Different project name
[email protected]:/system/etc/firmware/camera $
</pre>
The error: Different project name
If I move the file 00-RS_M6Mo.bin and try again?
Why this firmware for TF201 is this ROM?
gian.salvati said:
New camera isp ROM version = TF201-0x9900
Current camera isp version:TF700T-0xFFFFFF
rom_version: TF201-0x9900 isp_version: TF700T-0xFFFFFF
Different project name
Click to expand...
Click to collapse
It looks like it "thinks" it's a TF201 instead of a TF700T and therefore not update. Have you tried reinstalling ICS (FW version 9.4.5.30) and see if the camera(s) work(s)?
xcal321 said:
It looks like it "thinks" it's a TF201 instead of a TF700T and therefore not update. Have you tried reinstalling ICS (FW version 9.4.5.30) and see if the camera(s) work(s)?
Click to expand...
Click to collapse
I didn't tried.
How do I do it?
gian.salvati said:
I didn't tried.
How do I do it?
Click to expand...
Click to collapse
The same steps as my previous post, but instead use version 9.4.5.30 as opposed to 10.4.4.18.
xcal321 said:
The same steps as my previous post, but instead use version 9.4.5.30 as opposed to 10.4.4.18.
Click to expand...
Click to collapse
Do I need to wipe data before?
gian.salvati said:
Do I need to wipe data before?
Click to expand...
Click to collapse
No need to wipe yourself, it will be wiped by the recovery.
xcal321 said:
No need to wipe yourself, it will be wiped by the recovery.
Click to expand...
Click to collapse
I captured this logs on debugger
Image attached
i have same problem too
any idea?????????????????
asus is bad
i can not unlock bootloader too.it fails on unlocking
kia1349 said:
i have same problem too
any idea?
Click to expand...
Click to collapse
Did the camera(s) work in ICS?
i dont know
i am on JB now
in JB , camera dosent work
How can I utilize unicode myanmar(burmese)on my android
galaxy y
Android is natively UTF-8 (that is Unicode).
There are two conditions to that.
1) You need a font that has the characters that you require for your language.
2) You might want/need some way to type in those characters.
You could replace your fallback font with another font that contains Myanmarese.
If you have a compatible font on your browser, this should be (kind of) legible.
ပြည်ထောင်စု သမ္မတ မြန်မာနိုင်ငံတော်
Thanks for your kindness,but I still have problem.Here we are I installed south east asia font and I change my font style to it.I don't know whether it is utf-8 or ttf.
After that I saw empty space in the place of myanmar font ,this happen on web page,sms page and memo page.So how can I replace fallback font or any other way available?
UTF-8 and TTF are different concepts.
Give me a link to the font that you are using.
Thanks for yr kindness.
But unfortunately I cannot post the link though I tried cause I m new user of xda so what the alternatively way?
You could always PM me the link.
I have already done the pm of the software link
I haven't looked into what the apk itself does but assets/fonts/hsfsea.ttf is the font "Padauk".
Unzip the .apk
Remount your /system on your device as read/write
Code:
adb pull /system/fonts/DroidSansFallback.ttf
adb push hsfsea.ttf /system/fonts/DroidSansFallback.ttf
adb reboot
Here's a screenshot of my post from above on my Nook:
I am not clear yr post,but I have done unzip the apk, I saw hfsea.ttf. So I copied that to system/font/ and set file permission as droidsansfallback.ttf.And reboot my phone.Nothing changed.So please reply me more detail the procedure.
You do have exactly this (capitalization is important)?
Code:
ls -l /system/fonts
-rw-r--r-- root root 1139424 2013-03-01 12:00 DroidSansFallback.ttf
(-rw-rw-rw- is ok too)
Did you test in a browser?
Yes ofcourse,in the browser also nothing change, but the blank.
I'm unclear here.
You are saying that the stock DroidSansFallback.ttf was there,
that you replaced it with the hsfsea.ttf, and that the sizes agree?
Did you already try to install some other font?
Try clearing the cache.
Try explicitly setting the font to DroidSansFallback.
The procedure I have done is that I added hsfsea.ttf to system/font and I set the file permissin as other ttf.I also tried as u said rw rw rw.I clear cache.I reboot my phone.I also go to recovery and cwm recovery but I saw nothing related to font.Currently I have 4 fonts, unicode/south east asia,zawgyi one ttf,zawgyi one 2008 and system default.What elese thing shall I do for unicode?May I thank you in advance.
I don't know what is going on with your system.
You may be specifying a font that says it has the Unicode range for Myanmar, but doesn't.
Are you telling your apps to use a specific font?
Paste a ls -l /system/fonts please.
Me too I don't know what the problem is?I saw other android user also,they can not see myanmar font by using this application(unicode/south east asia )
Renate NST said:
Paste a ls -l /system/fonts please.
Click to expand...
Click to collapse
It may be that your system is rejecting it as a fallback font because it does not support the Basic Latin Unicode range (A-Z, etc).
You might try overwritng DroidSansFallback.ttf with Zawgyi.
How can I overwrite droidsansfallback.ttf by zawgyi? Any way I always thank you for your kindness.
Well, didn't you already overwrite DroidSansFallback.ttf with hsfsea.ttf?
We may be having miscommunication problems here.
I've been asking you to post a listing of ls -l /system/fonts
Could you do that, please?
Yes,that is
/system/font/
Clockopia.ttf
Droidindia.ttf
Droidsans-bold.ttf
Droidsans.ttf
Droidsansarabic.ttf
Droidsansfallback.ttf
Droidsanshebrew.ttf
Droidsansmono.ttf
Droidsansthai.ttf
Droidserif-bold.ttf
Droidserif-bolditalic.ttf
Droidserif-italic.ttf
Droidserif-regular.ttf
hsfsea.ttf(I have already added)
Samsungamericanregular.ttf
Samsunggeorgianregular.ttf
Code:
ls [b]-l[/b] /system/fonts
That's the small L in there, so that we can actually see something.
Code:
ls -l /system/fonts
-rw-r--r-- root root 4824 2012-06-29 04:58 AndroidClock.ttf
-rw-r--r-- root root 4824 2012-06-29 04:58 AndroidClock_Highlight.ttf
-rw-r--r-- root root 4824 2012-06-29 04:58 AndroidClock_Solid.ttf
-rw-r--r-- root root 6880 2012-06-29 04:58 Clockopia.ttf
-rw-r--r-- root root 366760 2012-06-29 04:58 DroidNaskh-Regular.ttf
lrw-r--r-- root root 2012-06-29 05:01 DroidSans-Bold.ttf -> Roboto-Bold.ttf
lrw-r--r-- root root 2012-06-29 05:01 DroidSans.ttf -> Roboto-Regular.ttf
-rw-r--r-- root root 13856 2012-06-29 04:58 DroidSansArmenian.ttf
-rw-r--r-- root root 227928 2012-06-29 04:58 DroidSansEthiopic-Regular.ttf
-rw-r--r-- root root 5300184 2012-06-29 04:58 DroidSansFallback.ttf
-rw-r--r-- root root 21096 2012-06-29 04:58 DroidSansGeorgian.ttf
-rw-r--r-- root root 30280 2012-06-29 04:58 DroidSansHebrew-Bold.ttf
-rw-r--r-- root root 30024 2012-06-29 04:58 DroidSansHebrew-Regular.ttf
-rw-r--r-- root root 119380 2012-06-29 04:58 DroidSansMono.ttf
-rw-r--r-- root root 35584 2012-06-29 04:58 DroidSansThai.ttf
-rw-r--r-- root root 185228 2012-06-29 04:58 DroidSerif-Bold.ttf
-rw-r--r-- root root 190304 2012-06-29 04:58 DroidSerif-BoldItalic.ttf
-rw-r--r-- root root 177560 2012-06-29 04:58 DroidSerif-Italic.ttf
-rw-r--r-- root root 172916 2012-06-29 04:58 DroidSerif-Regular.ttf
-rw-r--r-- root root 139296 2012-06-29 04:58 Lohit-Bengali.ttf
-rw-r--r-- root root 64232 2012-06-29 04:58 Lohit-Devanagari.ttf
-rw-r--r-- root root 66184 2012-06-29 04:58 Lohit-Tamil.ttf
-rw-r--r-- root root 79620 2012-06-29 04:58 Roboto-Bold.ttf
-rw-r--r-- root root 82880 2012-06-29 04:58 Roboto-BoldItalic.ttf
-rw-r--r-- root root 82580 2012-06-29 04:58 Roboto-Italic.ttf
-rw-r--r-- root root 79396 2012-06-29 04:58 Roboto-Regular.ttf
Why is the capitalization of all your files different?
You realize that this is the fourth time that I have asked you to do a simple directory listing.
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
Update: Fixed by
command !
Guys,
I am currently Running STOCK LRX21O.Rooted using Chainfire's AutoRoot and TWRP -2.8.1.0. I made backup but I am unable to access it using ES file explorer(with root option enabled). Also tried Root explorer but It just doesnt show the Folder itself.
When I boot into TWRP it shows the Backup folder there. So I tried to check it with adb to do a ls and it shows its there. I need to copy that folder to cloud just incase. I dont see permission issues. Plese suggest how to fix this ?
Code:
C:\Users\Zaibrockstar>adb shell ls -l /sdcard/
drwxrwx--- root sdcard_r 1971-01-05 22:48 Alarms
drwxrwx--x root sdcard_r 2014-11-12 21:00 Android
drwxrwx--- root sdcard_r 2014-11-12 23:29 DCIM
drwxrwx--- root sdcard_r 2014-11-13 08:44 Download
drwxrwx--- root sdcard_r 1971-01-05 22:48 Music
drwxrwx--- root sdcard_r 2014-11-12 21:34 Notifications
drwxrwx--- root sdcard_r 2014-11-12 23:26 Pictures
drwxrwx--- root sdcard_r 1971-01-05 22:48 Podcasts
drwxrwx--- root sdcard_r 1971-01-05 22:48 Ringtones
[B][U]lstat '/sdcard//TWRP' failed: Permission denied[/U][/B]
drwxrwx--- root sdcard_r 2014-11-13 09:27 backups
drwxrwx--- root sdcard_r 2014-11-12 21:32 baidu
drwxrwx--- root sdcard_r 2014-11-12 23:13 media
Code:
C:\Users\Zaibrockstar>adb shell ls -R /sdcard/
/sdcard/:
Alarms
Android
DCIM
Download
Music
Notifications
Pictures
Podcasts
Ringtones
[COLOR="Red"]TWRP[/COLOR]
backups
baidu
media
[B][COLOR="Red"]/sdcard//TWRP: Permission denied[/COLOR]
[/B]
Thanks
Zaib
http://forum.xda-developers.com/google-nexus-5/general/sdcard-problems-upgrading-android-t2938749