Hi all,
Can someone tell me what am I doing wrong here ?
[email protected]:~/android-sdk/build$ ls -altr
total 4824
drwxr-xr-x 8 kenny kenny 4096 2010-05-19 02:24 ..
-rw-r--r-- 1 kenny kenny 2621440 2010-05-19 02:41 mtd2.img
-rwxr-xr-x 1 kenny kenny 2310048 2010-05-19 02:54 zImage
drwxr-xr-x 2 kenny kenny 4096 2010-05-19 03:11 .
[email protected]:~/android-sdk/build$ ../tools/unpack-bootimg.pl mtd2.img
kernel written to mtd2.img-kernel.gz
ramdisk written to mtd2.img-ramdisk.cpio.gz
gzip: ../mtd2.img-ramdisk.cpio.gz: decompression OK, trailing garbage ignored
523 blocks
extracted ramdisk contents to directory mtd2.img-ramdisk/
[email protected]:~/android-sdk/build$ mkbootimg --cmdline 'no_console_suspend=1 console=null' --kernel zImage --ramdisk mtd2.img-ramdisk.cpio.gz -o kernel.desire
[email protected]:~/android-sdk/build$ ls -altr
total 9980
drwxr-xr-x 8 kenny kenny 4096 2010-05-19 02:24 ..
-rw-r--r-- 1 kenny kenny 2621440 2010-05-19 02:41 mtd2.img
-rwxr-xr-x 1 kenny kenny 2310048 2010-05-19 02:54 zImage
-rw-r--r-- 1 kenny kenny 342016 2010-05-19 03:11 mtd2.img-ramdisk.cpio.gz
-rw-r--r-- 1 kenny kenny 2277376 2010-05-19 03:11 mtd2.img-kernel.gz
drwxr-xr-x 8 kenny kenny 4096 2010-05-19 03:11 mtd2.img-ramdisk
-rw-r--r-- 1 kenny kenny 2654208 2010-05-19 03:12 kernel.desire
drwxr-xr-x 3 kenny kenny 4096 2010-05-19 03:12 .
[email protected]:~/android-sdk/build$ ../tools/fastboot flash boot kernel.desire
sending 'boot' (2592 KB)... OKAY
writing 'boot'... FAILED (remote: image update error)
[email protected]:~/android-sdk/build$ ../tools/fastboot flash zimage zImage
sending 'zimage' (2255 KB)... OKAY
writing 'zimage'... FAILED (remote: unknown fail)
[email protected]:~/android-sdk/build$ ls -althr kernel.desire
-rw-r--r-- 1 kenny kenny 2.6M 2010-05-19 03:12 kernel.desire
[email protected]:~/android-sdk/build$ ls -althr zImage
-rwxr-xr-x 1 kenny kenny 2.3M 2010-05-19 02:54 zImage
[email protected]:~/android-sdk/build$
Regards,
Kenny N
i think this has something to do with the bad block issue... try using this command to create the boot image
mkbootimg --base 20000000 --cmdline 'no_console_suspend=1 console=null' --kernel zImage --ramdisk ramdisk.gz -o boot.img
Thanks Craig - I will give it a try once I got home. It tooks me ~3 hours to customize and build the HTC Desire's kernel for Nexus One. It would be a waste if I can't actually see it in action
Regards,
Kenny N
tried -- still the same
Regards,
Kenny N
Did you clear cache? No idea how that would make a difference but I wipe cache before each kernel flash.
It failed to do the initial flash. Clearing cache won't help in my case.
Sent from my Nexus One
vnbuddy2002 said:
tried -- still the same
Regards,
Kenny N
Click to expand...
Click to collapse
Hmm... difficult to say... i don't know how to debug fastboot... try it via a recovery zip... and then check out the recovery.log for any errors...
Related
Hi,
I have upgraded my moboot to 3.0.5 and upgraded the Cyanogenmod to CM9. Also, i have decided to install TouchPadBuntu to test it. Followed the instructions with some modifications, and everything went fine, but when i try to boot on it via moboot, it gives the error:
Loading '/boot/uImage.TouchPadBuntu'... OK
Checking uImage... Invalid Magic
BOOT FAILED!
Also, ClockRecovery doesn't works too, it returns some numbers (hex codes) on the boot screen.
Someone can give some light?
I'm dealing with same problem, but with Arch Linux.
I think the problem is in /boot free space...
Can you list your files in /boot and your free space in there?
ls -l /boot
df -h /boot
Hi, i have attached the errors... one is TouchPadBuntu error, and the other is Cyanogenmod error that is appearing sometimes yes, sometimes no...
http://img19.imageshack.us/img19/5138/imagem0000m.jpg
http://img828.imageshack.us/img828/4153/imagem0001.jpg
Also, here is my /boot
Code:
[email protected]:/# ls -l /boot
-rw-r--r-- 1 root root 1430215 Jul 30 2011 System.map-2.6.35-palm-tenderloin
drwxr-xr-x 2 root root 4096 Oct 14 02:59 bin
-rw-r--r-- 1 root root 490764 Jul 30 2011 boot-genesis.tar.gz
-rw-r--r-- 1 root root 119371 Jul 30 2011 boot-images.tar.gz
-rw-r--r-- 1 root root 115392 Jul 30 2011 boot.bin
-rw-r--r-- 1 root root 75277 Jul 30 2011 config-2.6.35-palm-tenderloin
drwxr-xr-x 2 root root 4096 Oct 14 02:59 dev
drwxr-xr-x 3 root root 4096 Oct 14 02:59 etc
-rwxr-xr-x 1 root root 1131 Jul 30 2011 genesis-update.xml
-rwxr-xr-x 1 root root 2224 Jul 30 2011 image-update.xml
drwxr-xr-x 2 root root 4096 Oct 14 02:59 lib
drwx------ 2 root root 16384 Oct 14 02:56 lost+found
-rw-r--r-- 1 root root 11 Oct 14 03:51 moboot.default
-rw-r--r-- 1 luna luna 0 Feb 9 01:57 moboot.next
-rw-rw-rw- 1 root root 30313 Feb 8 00:58 moboot.splash.CyanogenMod.tga
-rw-r--r-- 1 luna 10000 14046 Sep 8 2001 moboot.splash.webOS.tga
-rw-r--r-- 1 root root 4 Feb 8 01:51 moboot.verbose.TouchPadBuntu
drwxr-xr-x 2 root root 4096 Oct 14 02:59 proc
drwxr-xr-x 2 root root 4096 Oct 14 02:59 realroot
drwxr-xr-x 2 root root 4096 Oct 14 02:59 sbin
drwxr-xr-x 2 root root 4096 Oct 14 02:59 sys
lrwxrwxrwx 1 root root 13 Feb 8 01:51 uImage -> uImage.moboot
-rw-r--r-- 1 root root 3333228 Jul 30 2011 uImage-2.6.35-palm-tenderloin
-rw-r--r-- 1 root root 5006686 Feb 8 00:57 uImage.ClockworkMod
-rw-r--r-- 1 root root 4136681 Feb 8 00:58 uImage.CyanogenMod
-rw-r--r-- 1 root root 1106 Feb 8 02:53 uImage.TouchPadBuntu
-rw-r--r-- 1 root root 64508 Feb 8 01:50 uImage.moboot
lrwxrwxrwx 1 root root 29 Oct 14 02:58 uImage.webOS -> uImage-2.6.35-palm-tenderloin
-rw-r--r-- 1 root root 84 Jul 30 2011 updatefs-info
drwxr-xr-x 5 root root 4096 Oct 14 02:59 usr
[email protected]:/# df -h /boot
Filesystem Size Used Available Use% Mounted on
/dev/root 31.0M 22.1M 8.9M 71% /boot
Hi folks,
I have corrected my problem downloading uImage.TouchPadUbuntu again via CURL direclty to /boot. To do this i have to use mount -O rw,remount /boot and execute the curl command here.
After this, i rebooted the touchpad and now have ubuntu on it. But using touchscreen as mouse is sucking a lot, and response of my touch on virtual keyboard too... but fine to test!
I also solved my problem, I think the problem was pretty like yours!
My solution post.
Hi,
I bought a brand new samsung galaxy s plus GT-I9001 in Poland (locked to Orange network) and I 'm trying to unlock the phone, but I can't because my phone does not contain the nv_data.bin file in the efs folder.
I have rooted the phone using the tutorial posted in
http://forum.xda-developers.com/wiki/Samsung_Galaxy_S_Plus/GT-I9001#Rooting
I got root access and found that in efs folder I got these files
Code:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
$ su
su
# pwd
pwd
/
# ls -l -a
ls -l -a
drwxrwx--x system system 2012-10-09 15:39 efs
dr-x------ root root 2012-10-10 13:27 config
drwxrwx--- system cache 2012-10-10 13:29 cache
drwxrwx--x system system 1980-01-06 01:00 persist
lrwxrwxrwx root root 2012-10-10 13:27 sdcard -> /mnt/sdcard
drwxr-xr-x root root 2012-10-10 13:27 acct
drwxrwxr-x root system 2012-10-10 13:27 mnt
lrwxrwxrwx root root 2012-10-10 13:27 vendor -> /system/vendor
lrwxrwxrwx root root 2012-10-10 13:27 d -> /sys/kernel/debug
lrwxrwxrwx root root 2012-10-10 13:27 etc -> /system/etc
-rw-r--r-- root root 5610 1970-01-01 01:00 ueventd.rc
-rw-r--r-- root root 0 1970-01-01 01:00 ueventd.goldfish.rc
drwxr-xr-x root root 2012-10-10 12:15 system
drwxr-xr-x root root 2012-10-10 13:27 sys
drwxr-x--- root root 1970-01-01 01:00 sbin
-rw-r--r-- root root 339852 1970-01-01 01:00 recovery
dr-xr-xr-x root root 1970-01-01 01:00 proc
-rw-r--r-- root root 2011 1970-01-01 01:00 lpm.rc
drwxr-xr-x root root 1970-01-01 01:00 lib
-rwxr-x--- root root 24620 1970-01-01 01:00 initlogo.rle
-rwxr-x--- root root 30518 1970-01-01 01:00 init.rc
-rwxr-x--- root root 6900 1970-01-01 01:00 init.qcom.sh
-rwxr-x--- root root 8590 1970-01-01 01:00 init.qcom.rc
-rwxr-x--- root root 1677 1970-01-01 01:00 init.goldfish.rc
-rwxr-x--- root root 106780 1970-01-01 01:00 init
-rw-r--r-- root root 118 1970-01-01 01:00 default.prop
drwxrwx--x system system 2012-10-10 13:27 data
-rw-r--r-- root root 38528 1970-01-01 01:00 charging.rle
-rw-r--r-- root root 22268 1970-01-01 01:00 ARIESVE.rle
drwx------ root root 2011-12-19 08:31 root
drwxr-xr-x root root 2012-10-10 13:35 dev
# cd efs
cd efs
# ls -l -a
ls -l -a
-rw-r--r-- system system 9 2012-10-09 15:39 cryptprop_applied_result
-rw-r--r-- root root 5 2012-10-10 10:51 cryptprop_onetimeboot
-rw-r--r-- system system 1 2012-10-09 15:39 cryptprop_essiv
drwx------ root root 1980-01-06 01:01 lost+found
drwxrwxr-x root root 1980-01-06 01:09 .files
-rw-r--r-- root root 3 2012-10-10 10:51 cryptprop_securewipedata
# cd .files
cd .files
# ls -l -a
ls -l -a
drwxrwxr-x media system 1980-01-06 01:01 .ssh01
-rw-rw-rw- radio radio 2 1980-01-06 01:09 keystr
drwxrwxr-x media system 1980-01-06 01:01 .jck12
drwxrwxr-x media system 1980-01-06 01:01 .dj550
as you can see the efs folder contain cryptprop files which are very small.
The phone works normally, it has its IMEI and connects to GSM network and WiFi network as well. (*#06# returns value 352377055840629)
I'm trying to unlock the phone myself but without nv_data.bin I'm getting nowhere...
Could someone please help me?
PS:
I have changed the stock rom (orange) to XEO rom (I9001XXKPU 2.3.6 and I9001XXKI2 2.3.4) but efs folder is the same each time.
I have checked the init.rc file in the root... ht file looks like this:
Line 56:
mkdir /efs 0771 system system
Line 131 - 135:
mount ext4 /dev/block/mmcblk0p27 /efs nosuid nodev barrier=0
insmod /lib/modules/sec_param.ko
Line 160 - 165:
#efs
chown system system /efs
chmod 0771 /efs
mkdir /efs/.files 0775
# Added for testing DIVX DRM
mkdir /efs/.files/.ssh01 0775
mkdir /efs/.files/.jck12 0775
mkdir /efs/.files/.dj550 0775
chown media system /efs/.files/.ssh01
chown media system /efs/.files/.jck12
chown media system /efs/.files/.dj550
chmod 0775 /efs/.files/.ssh01
chmod 0775 /efs/.files/.jck12
chmod 0775 /efs/.files/.dj550
This init.rc does not create the folders WiFi or Bluetooth like in other device (I checked in a galaxy SII)
The init.rc file is attached.
fcornejo said:
I 'm trying to unlock the phone,
Click to expand...
Click to collapse
It might be easier to use an app or tool from My Android Collections to unlock phone
xsenman said:
It might be easier to use an app or tool from My Android Collections to unlock phone
Click to expand...
Click to collapse
Well thanx, but all the aps and methods require the nv_data.bin file...
fcornejo said:
Well thanx, but all the aps and methods require the nv_data.bin file...
Click to expand...
Click to collapse
have a look at /persist folder.
xsenman said:
have a look at /persist folder.
Click to expand...
Click to collapse
There are files:
Code:
#
# cd persist
cd persist
# ls -l -a
ls -l -a
-rw-r--r-- root root 3468 2011-08-29 00:40 WCN1314_qcom_wlan_nv.bi
-rw-r--r-- root root 3 2011-08-29 00:40 efs_info.bin
drwxr-xr-x root root 2011-09-08 10:14 qcom
-rw-r--r-- root root 1656 2011-08-29 00:40 qcom_wlan_nv.bin
-rw-rw-rw- root root 2 2012-10-10 13:27 sd_det.bin
-rw-rw-rw- root root 1 2012-10-10 12:08 usb_sel.bin
drwxrwxr-x root root 1980-01-06 01:00 .files
-rw-rw-rw- root root 1 1980-01-06 01:00 movinand_checksum_pass
-rw-rw-rw- root root 1 1980-01-06 01:00 movinand_checksum_done
Amazon published a new update for Kindle Fire HD 7 (link).
I see that updates come with two different versions of boot image:
Code:
$ unzip update-kindle-7.3.0_D025_3013320.bin
$ ls -l
-rw-r--r-- 1 user group 4.0M 2011-09-07 06:52 boot-eng.img
-rw-r--r-- 1 user group 4.0M 2011-09-07 06:52 boot-prod.img
drwxr-xr-x 3 user group 4.0K 2013-03-28 18:25 META-INF
-rw-r--r-- 1 user group 42K 2011-09-07 06:52 MLO-dummy
-rw-r--r-- 1 user group 41K 2011-09-07 06:52 MLO-dvt
-rw-r--r-- 1 user group 41K 2011-09-07 06:52 MLO-evt
-rw-r--r-- 1 user group 41K 2011-09-07 06:52 MLO-pvt
-rw-r--r-- 1 user group 19K 2011-09-07 06:52 new_cert_swap.sed
drwxr-xr-x 3 user group 4.0K 2013-03-28 18:25 recovery
-rw-r--r-- 1 user group 724K 2011-09-07 06:52 sed
drwxr-xr-x 13 user group 4.0K 2013-03-28 18:25 system
-rw-r--r-- 1 user group 220K 2011-09-07 06:52 u-boot-eng.bin
-rw-r--r-- 1 user group 220K 2011-09-07 06:52 u-boot-prod.bin
What is the different between "boot" and "u-boot" images? And between "-eng" and "-prod" images?
boom boom boom
I couldn't tell you what the actual difference (if any) is, but the designations are "eng" for engineering build and "prod" for production build. Generally speaking, an engineering build has a ton more debugging stuff active, to the point that it negatively impacts performance.
In other ROMs I've edited an XML file in /system/csc to make some changes to the keyboard -- specifically, to display alternate symbols when you press-hold a key. I flashed stock MM tonight and noticed that this folder no longer exists.
I checked the Maximum OvrDriVE MM ROM and it does have this folder with the appropriate file. So what happened to the CSC stuff in stock?
SteveRiley said:
In other ROMs I've edited an XML file in /system/csc to make some changes to the keyboard -- specifically, to display alternate symbols when you press-hold a key. I flashed stock MM tonight and noticed that this folder no longer exists.
I checked the Maximum OvrDriVE MM ROM and it does have this folder with the appropriate file. So what happened to the CSC stuff in stock?
Click to expand...
Click to collapse
which stock firmware you are using?
pvsgh said:
which stock firmware you are using?
Click to expand...
Click to collapse
The one DeeXii posted a couple weeks ago: N910TUVS2EPG2_N910TTMB2EPG2_TMB
http://forum.xda-developers.com/note-4-tmobile/development/stock-n910t-n910tuvu2epe3-6-0-1-t3407018
SteveRiley said:
The one DeeXii posted a couple weeks ago: N910TUVS2EPG2_N910TTMB2EPG2_TMB
http://forum.xda-developers.com/note-4-tmobile/development/stock-n910t-n910tuvu2epe3-6-0-1-t3407018
Click to expand...
Click to collapse
Those are the stock ODIN flashable files. Once you flash it via ODIN you will see CSC folder on your phone under /system directory.
pvsgh said:
Those are the stock ODIN flashable files. Once you flash it via ODIN you will see CSC folder on your phone under /system directory.
Click to expand...
Click to collapse
No CSC folder here.
Code:
[email protected]:/ # [B]ls -al /system[/B]
drwxr-xr-x root root 2016-08-11 23:53 app
drwxr-xr-x root shell 2008-12-31 07:00 bin
-rw-r--r-- root root 8080 2008-12-31 07:00 build.prop
drwxr-xr-x root root 2008-12-31 07:00 cameradata
drwxr-xr-x root root 2016-07-07 07:17 container
drwxr-xr-x root root 2016-08-12 01:00 etc
drwxr-xr-x root root 2008-12-31 07:00 fonts
drwxr-xr-x root root 2016-07-07 07:17 framework
-rw-r--r-- root root 10800 2008-12-31 07:00 kern_sec_info
drwxr-xr-x root root 2016-08-11 23:36 lib
drwx------ root root 1969-12-31 16:00 lost+found
drwxr-xr-x root root 2008-12-31 07:00 media
drwxr-xr-x root root 2016-07-07 07:16 preloadedmdm
drwxr-xr-x root root 2016-08-11 23:52 priv-app
-rw-r--r-- root root 4876860 2008-12-31 07:00 recovery-from-boot.bak
drwxr-xr-x root root 2008-12-31 07:00 saiv
-rw-r--r-- root root 417 2016-07-07 07:36 tima_measurement_info
drwxr-xr-x root root 2008-12-31 07:00 tts
drwxr-xr-x root root 2008-12-31 07:00 usr
drwxr-xr-x root shell 2008-12-31 07:00 vendor
drwxr-xr-x root root 2008-12-31 07:00 voicebargeindata
drwxr-xr-x root root 2008-12-31 07:00 wakeupdata
drwxr-xr-x root shell 2008-12-31 07:00 xbin
And a little bit of searching on /system and /data doesn't reveal anything much:
Code:
[email protected]:/ # [B]find /system -iname '*csc*'[/B]
/system/fonts/CarroisGothicSC-Regular.ttf
/system/lib/libcontrolcsc.so
/system/lib/libsccore_csc.so
/system/priv-app/CSC
/system/priv-app/CSC/CSC.apk
/system/priv-app/CSC/oat/arm/CSC.odex.xz
[email protected]:/ # f[B]ind /data -iname '*csc*'[/B]
/data/data/com.samsung.sec.android.application.csc
/data/data/com.google.android.gms/files/AppDataSearch/main/cur/ds.cscoring
/data/system/cscversion.txt
/data/dalvik-cache/profiles/com.samsung.sec.android.application.csc
/data/dalvik-cache/arm/[email protected]@[email protected]@classes.dex
And this zero-byte file seems odd:
Code:
[email protected]:/ # [B]ls -al /data/system/cscversion.txt[/B]
-rw------- system system 0 2016-08-12 20:03 cscversion.txt
I've flashed the build a couple times now, same results. My procedure:
1. Ensure SuperSU zip is on external SD card
2. Boot TWRP recovery (currently 3.0.2 installed)
3. Wipe every partition except external SD
4. Boot the phone into download mode
5. Odin (3.0.9) the ROM to the phone
6. Odin TWRP back to the phone
7. Boot TWRP recovery
8. Flash SuperSU zip
9. Reboot and let settle for 15 minutes
SteveRiley said:
No CSC folder here.
Code:
[email protected]:/ # [B]ls -al /system[/B]
drwxr-xr-x root root 2016-08-11 23:53 app
drwxr-xr-x root shell 2008-12-31 07:00 bin
-rw-r--r-- root root 8080 2008-12-31 07:00 build.prop
drwxr-xr-x root root 2008-12-31 07:00 cameradata
drwxr-xr-x root root 2016-07-07 07:17 container
drwxr-xr-x root root 2016-08-12 01:00 etc
drwxr-xr-x root root 2008-12-31 07:00 fonts
drwxr-xr-x root root 2016-07-07 07:17 framework
-rw-r--r-- root root 10800 2008-12-31 07:00 kern_sec_info
drwxr-xr-x root root 2016-08-11 23:36 lib
drwx------ root root 1969-12-31 16:00 lost+found
drwxr-xr-x root root 2008-12-31 07:00 media
drwxr-xr-x root root 2016-07-07 07:16 preloadedmdm
drwxr-xr-x root root 2016-08-11 23:52 priv-app
-rw-r--r-- root root 4876860 2008-12-31 07:00 recovery-from-boot.bak
drwxr-xr-x root root 2008-12-31 07:00 saiv
-rw-r--r-- root root 417 2016-07-07 07:36 tima_measurement_info
drwxr-xr-x root root 2008-12-31 07:00 tts
drwxr-xr-x root root 2008-12-31 07:00 usr
drwxr-xr-x root shell 2008-12-31 07:00 vendor
drwxr-xr-x root root 2008-12-31 07:00 voicebargeindata
drwxr-xr-x root root 2008-12-31 07:00 wakeupdata
drwxr-xr-x root shell 2008-12-31 07:00 xbin
And a little bit of searching on /system and /data doesn't reveal anything much:
Code:
[email protected]:/ # [B]find /system -iname '*csc*'[/B]
/system/fonts/CarroisGothicSC-Regular.ttf
/system/lib/libcontrolcsc.so
/system/lib/libsccore_csc.so
/system/priv-app/CSC
/system/priv-app/CSC/CSC.apk
/system/priv-app/CSC/oat/arm/CSC.odex.xz
[email protected]:/ # f[B]ind /data -iname '*csc*'[/B]
/data/data/com.samsung.sec.android.application.csc
/data/data/com.google.android.gms/files/AppDataSearch/main/cur/ds.cscoring
/data/system/cscversion.txt
/data/dalvik-cache/profiles/com.samsung.sec.android.application.csc
/data/dalvik-cache/arm/[email protected]@[email protected]@classes.dex
And this zero-byte file seems odd:
Code:
[email protected]:/ # [B]ls -al /data/system/cscversion.txt[/B]
-rw------- system system 0 2016-08-12 20:03 cscversion.txt
I've flashed the build a couple times now, same results. My procedure:
1. Ensure SuperSU zip is on external SD card
2. Boot TWRP recovery (currently 3.0.2 installed)
3. Wipe every partition except external SD
4. Boot the phone into download mode
5. Odin (3.0.9) the ROM to the phone
6. Odin TWRP back to the phone
7. Boot TWRP recovery
8. Flash SuperSU zip
9. Reboot and let settle for 15 minutes
Click to expand...
Click to collapse
Don't know if it would make any difference but you should be using Odin 3.11.1 with this latest EPG2 firmware. CSC related files reside in cache.img.ext4 , so it is possible that that particular file is not being flashed in your case.
pvsgh said:
Don't know if it would make any difference but you should be using Odin 3.11.1 with this latest EPG2 firmware. CSC related files reside in cache.img.ext4 , so it is possible that that particular file is not being flashed in your case.
Click to expand...
Click to collapse
Hm, you might very well have discovered the cause.
Examining the cache.img.ext4 file on my PC:
Code:
[email protected] ~/junk $ [B]simg2img cache.img.ext4 cache.raw[/B]
[email protected] ~/junk $ [B]sudo mount -t ext4 -o loop cache.raw /mnt[/B]
[email protected] ~/junk $ [B]ls -al /mnt[/B]
total 28
drwxr-xr-x 4 root root 4096 Dec 31 1969 .
drwxr-xr-x 1 root root 122 Dec 24 2015 ..
drwx------ 2 root root 4096 Dec 31 1969 lost+found
drwxrwx--- 2 steve 2001 4096 Jul 7 07:36 recovery
[email protected] ~/junk $ [B]ls -al /mnt/recovery/[/B]
total 82720
drwxrwx--- 2 steve 2001 4096 Jul 7 07:36 .
drwxr-xr-x 4 root root 4096 Dec 31 1969 ..
-rw-r--r-- 1 root root 78 Jul 7 07:36 command
-rw-r--r-- 1 root root 84691365 Jul 7 07:36 sec_csc.zip
[email protected] ~/junk $ [B]unzip -l /mnt/recovery/sec_csc.zip[/B]
Archive: /mnt/recovery/sec_csc.zip
signed by SignApk
Length Date Time Name
--------- ---------- ----- ----
{... many files, including several for system/csc ...}
--------- -------
104784820 113 files
I'm surprised the phone even works!
Hm, experiencing flash write failures. First time was about 15% finished. Second time seems about 95% finished.
Third flash completed. Before rebooting, I flashed TWRP. Then I booted TWRP and installed SuperSU. Booted normally and received the dreaded ddi: mmc_read failed message. Crap. Tried another flashing round, which also completed, and let it boot immediately. The Samsung recovery started (which I have never actually seen before) and ran through an installation cycle of something. After that, the phone booted and once again shows ddi:mmc_read failed. Is this thing kaput now?
----------
EDIT: I power cycled the phone and now it appears to be doing a normal first boot -- I'm staring at the T-Mobile splash and the status light is flickering blue/cyan. Wow!
SteveRiley said:
Third flash completed. Before rebooting, I flashed TWRP. Then I booted TWRP and installed SuperSU. Booted normally and received the dreaded ddi: mmc_read failed message. Crap. Tried another flashing round, which also completed, and let it boot immediately. The Samsung recovery started (which I have never actually seen before) and ran through an installation cycle of something. After that, the phone booted and once again shows ddi:mmc_read failed. Is this thing kaput now?
----------
EDIT: I power cycled the phone and now it appears to be doing a normal first boot -- I'm staring at the T-Mobile splash and the status light is flickering blue/cyan. Wow!
Click to expand...
Click to collapse
Did you use the latest version of ODIN now? Also if the phone looks stuck on T-Mobile logo for longer than 30 mins, then remove the battery from the phone and try to boot again.
pvsgh said:
Did you use the latest version of ODIN now? Also if the phone looks stuck on T-Mobile logo for longer than 30 mins, then remove the battery from the phone and try to boot again.
Click to expand...
Click to collapse
Yep, Odin 3.11.1 worked, but like I wrote before, it took three attempts. Weird.
BTW, not everyone agrees that the version of Odin was the actual problem:
http://forum.xda-developers.com/not...ow-updates-issues-t3415914/page2#post68173468
pvsgh said:
Don't know if it would make any difference but you should be using Odin 3.11.1 with this latest EPG2 firmware. CSC related files reside in cache.img.ext4 , so it is possible that that particular file is not being flashed in your case.
Click to expand...
Click to collapse
Worked like a charm. Now I have wifi calling and secondary characters on my keyboard again!
You'll also notice that Bluetooth tethering is gone. T-Mobile likes to disable that for some reason. I imagine that buried in one of the CSC files is a line you could delete to restore Bluetooth tethering.
Is there a way to extract the SpO2 tpk file from the Galaxy Watch 3 ? I have both watches GW3 and Active 2. I am planning to sideload the SpO2 on the Active 2. Thanks.
A
Blood Oxygen is NO Standalone TPK nor WGT...
It is inside the "magic" Samsung Health package:
Code:
com.samsung.shealth_gear
B
This crap is started as Widget... no idea how exactly it is enablde/disabled for France etc...
Maybe by Plugin APK crap...
C
Code:
tizen-manifest.xml
From Version 4.12.1200
Code:
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<manifest xmlns="http://tizen.org/ns/packages" api-version="5.5.0.1" package="com.samsung.shealth_gear" version="[B]4.12.1200[/B]">
<profile name="wearable"/>
<ui-application
At end of manifest....
Code:
</widget-class>
<[COLOR="Red"][B]widget-class classid[/B][/COLOR]="[COLOR="Red"]oxygensaturation[/COLOR]" max-instance="1" update-period="0">
<!-- DREAM_HEALTH_HEADER_BLOOD_OXYGEN -->
<label xml:lang="ar-ae">الأكسجين ÙÙŠ الدم</label>
<label xml:lang="ar-il">الأكسجين ÙÙŠ الدم</label>
<label xml:lang="as-in">তেজৰ অকà§à¦¸à¦¿à¦œà§‡à¦¨</label>
<label xml:lang="az-az">Qanda oksigen həcmi</label>
<label xml:lang="be-by">КіÑларод у крыві</label>
<label xml:lang="bg-bg">КиÑлород в кръвта</label>
<label xml:lang="bn-bd">রকà§à¦¤à§‡ অকà§à¦¸à¦¿à¦œà§‡à¦¨</label>
<label xml:lang="bn-in">রকà§à¦¤à§‡ অকà§à¦¸à¦¿à¦œà§‡à¦¨</label>
<label xml:lang="bo-cn">血氧</label>
<label xml:lang="bs-ba">Kisik u krvi</label>
<label xml:lang="ca-es">Oxigen en sang</label>
<label xml:lang="cs-cz">Hladina kyslÃ*ku v krvi</label>
<label xml:lang="da-dk">Iltmætning i blodet</label>
<label xml:lang="de-at">Blutsauerstoff</label>
<label xml:lang="de-ch">Blutsauerstoff</label>
<label xml:lang="de-de">Blutsauerstoff</label>
<label xml:lang="el-gr">Οξυγόνο αίματος</label>
<label xml:lang="en-au">Blood oxygen</label>
<label xml:lang="en-ca">Blood oxygen</label>
<label xml:lang="en-gb">Blood oxygen</label>
<label xml:lang="en-ie">Blood oxygen</label>
<label xml:lang="en-nz">Blood oxygen</label>
This leads to
D
Search in BTG6 GW3 Firmwares... leads to this inside rootfs.img instead csc.img...
Code:
usr/apps/com.samsung.w-home/bin/[B]w-home[/B]
Code:
oxygensaturation[B]@[/B]com.samsung.shealth.widget
E
I am at the moment only smart enough to call apps via Commands...
https://forum.xda-developers.com/showpost.php?p=83481485&postcount=2007
But no idea how this Widget crap...
Code:
F
No Firmwarefiles for Tizen 5.5 leaked to do stupid tests inside Firmware...
I mean no CTH8 nor CTI4 for SM-R820...
Maybe somebody have faster solution for testing... :angel:
Best Regards
Edit 1.
Nice Video:
https://www.youtube.com/watch?v=qyul_jA8kWI
Here we can see 2 ways of start...
A
By open Shealth TPK on Watch...
B
Widget crap....
Edit 2.
Sitting on WC... ehm I mean during hard work..
Got an idea...
Watch Face maybe could call such kind of Widget...
But first I have checked BTG6 Firmware from GW3 for text string:
Code:
com.samsung.shealth.widget
Found this script... so we are agin in SQLite database world...
Code:
#!/bin/bash
#
# RW Update Script for 3.0 -> 4.0
PATH=/bin:/usr/bin:/sbin:/usr/sbin
source /usr/share/upgrade/rw-update-macro.inc
get_version_info
#db
HOMEDB=/opt/usr/home/owner/apps_rw/com.samsung.w-home/data/.home.db
if [ ! -e $HOMEDB ]; then
HOMEDB=/opt/usr/apps/com.samsung.w-home/data/.home.db
fi
if [ "$OLD_VER" = "unknown" ]; then
echo "upgrade home DB HOME DB:$HOMEDB"
/usr/bin/sqlite3 $HOMEDB "update home set id = 'com.samsung.app-shortcut-widget' where id='com.samsung.app-widget.widget';"
/usr/bin/sqlite3 $HOMEDB "update home set id = '[email protected]' where id = 'com.samsung.shealth.widget.pedometer';"
/usr/bin/sqlite3 $HOMEDB "update home set id = '[email protected]' where id = 'com.samsung.shealth.widget.hrlog';"
/usr/bin/sqlite3 $HOMEDB "update home set id = '[email protected]' where id = 'com.samsung.shealth.widget.exercise';"
/usr/bin/sqlite3 $HOMEDB "update home set id = '[email protected]' where id = 'com.samsung.shealth.widget.heartrate';"
/usr/bin/sqlite3 $HOMEDB "update home set id = '[email protected]' where id = 'com.samsung.shealth.widget.intake';"
/usr/bin/sqlite3 $HOMEDB "update home set id = '[email protected]' where id = 'com.samsung.shealth.widget.together';"
/usr/bin/sqlite3 $HOMEDB "update home set id = '[email protected]' where id = 'com.samsung.shealth.widget.together.leaderboard';"
/usr/bin/sqlite3 $HOMEDB "update home set id = '[email protected]' where id = 'com.samsung.shealth.widget.together.challenge';"
/usr/bin/sqlite3 $HOMEDB "update home set id = '[email protected]' where id = 'com.samsung.shealth.widget.floor';"
/usr/bin/sqlite3 $HOMEDB "update home set id = '[email protected]' where id = 'com.samsung.w-calendar2.widget.next-event';"
/usr/bin/sqlite3 $HOMEDB "update home set id = 'com.samsung.w-contacts2.widget.multiple' where id = 'com.samsung.w-contacts2.widget.single';"
/usr/bin/sqlite3 $HOMEDB "update home set id = 'com.samsung.w-magazine-widget-app' where id = 'org.tizen.magazine-widget';"
/usr/bin/com.samsung.app-widget-upgrade
fi
if [[ "$OLD_VER" = "3.0"* ]]; then
echo "upgrade home DB 3.0* to 4.0 HOME DB:$HOMEDB"
/usr/bin/sqlite3 $HOMEDB "delete from home where id = '[email protected]';"
fi
Will check if i can find Watch Face as template...
Maybe easier here to "spoof"...
Best Regards
Watch Face seems dead end too...
But paths from Shell script leads to this:
Code:
D:\SDB\SDB260>sdb pull /opt/usr/apps/com.samsung.w-home/data/.home.db
pulled .home.db 100% 16KB
1 file(s) pulled. 0 file(s) skipped.
/opt/usr/apps/com.samsung.w-home/data/.home.db 106 KB/s (16384 bytes in 0.150s)
Code:
D:\SDB\SDB260>sdb pull /opt/usr/home/owner/apps_rw/com.samsung.w-home/data/.home.db
pulled .home.db 100% 16KB
1 file(s) pulled. 0 file(s) skipped.
/opt/usr/home/owner/apps_rw/com.samsung.w-home/data/.home.db 123 KB/s (16384 bytes in 0.130s)
1:1 same file from both locations as it seems...
adfree said:
Watch Face seems dead end too...
But paths from Shell script leads to this:
Code:
D:\SDB\SDB260>sdb pull /opt/usr/apps/com.samsung.w-home/data/.home.db
pulled .home.db 100% 16KB
1 file(s) pulled. 0 file(s) skipped.
/opt/usr/apps/com.samsung.w-home/data/.home.db 106 KB/s (16384 bytes in 0.150s)
Code:
D:\SDB\SDB260>sdb pull /opt/usr/home/owner/apps_rw/com.samsung.w-home/data/.home.db
pulled .home.db 100% 16KB
1 file(s) pulled. 0 file(s) skipped.
/opt/usr/home/owner/apps_rw/com.samsung.w-home/data/.home.db 123 KB/s (16384 bytes in 0.130s)
1:1 same file from both locations as it seems...
Click to expand...
Click to collapse
Looks like we are getting somewhere here. Any files you need for me to check from my Active 2 watch. ?
My setup is are as follows
Phone: Huawei Mate 20 Pro
Watch: Samsung Active 2
Active 2 Watch CSC is now KOO changed using Combination FW and Netodin
Originally it was on 4 0 0 .7 , changed to 4 0 0 .6 after Netodin CSC update
Installed bp.tpk and ecg.tpk via sdb.
then via Samsung OTA it became 4 0 0 .8 then another Samsung OTA came
and it is now 5.5.0. 1. Both Ecg and BP are working using Samsung Health Monitor 167
For better investigation... my SM-R760...
Code:
sh-3.2# cd /opt/usr/home/owner/apps_rw/com.samsung.w-home/data/
sh-3.2# ls -a1l
total 124
drwxrwsr-x 3 owner system_share 4096 Oct 1 05:03 .
drwxr-xr-x 5 owner users 4096 Apr 28 10:04 ..
-rw-r--r-- 1 owner system_share 16384 Oct 2 15:51 .apps.db
-rw-r--r-- 1 owner system_share 12824 Oct 1 05:03 .apps.db-journal
-rw-r--r-- 1 owner system_share 16384 Oct 2 15:51 .home.db
-rw-r--r-- 1 owner system_share 12824 Oct 2 15:51 .home.db-journal
drwxr-sr-x 2 owner system_share 4096 Oct 1 05:04 .pref
-rw-r--r-- 1 owner system_share 20480 Oct 2 15:51 .widget_suggestion.db
-rw-r--r-- 1 owner system_share 16928 Oct 1 05:03 .widget_suggestion.db-journal
sh-3.2# cd /opt/usr/apps/com.samsung.w-home/data/
sh-3.2# ls -a1l
total 124
drwxrwsr-x 3 owner system_share 4096 Oct 1 05:03 .
drwxr-xr-x 5 owner users 4096 Apr 28 10:04 ..
-rw-r--r-- 1 owner system_share 16384 Oct 2 15:51 .apps.db
-rw-r--r-- 1 owner system_share 12824 Oct 1 05:03 .apps.db-journal
-rw-r--r-- 1 owner system_share 16384 Oct 2 15:51 .home.db
-rw-r--r-- 1 owner system_share 12824 Oct 2 15:51 .home.db-journal
drwxr-sr-x 2 owner system_share 4096 Oct 1 05:04 .pref
-rw-r--r-- 1 owner system_share 20480 Oct 2 15:51 .widget_suggestion.db
-rw-r--r-- 1 owner system_share 16928 Oct 1 05:03 .widget_suggestion.db-journal
sh-3.2# mkdir testme
sh-3.2# ls -a1l
total 128
drwxrwsr-x 4 owner system_share 4096 Oct 2 15:56 .
drwxr-xr-x 5 owner users 4096 Apr 28 10:04 ..
-rw-r--r-- 1 owner system_share 16384 Oct 2 15:51 .apps.db
-rw-r--r-- 1 owner system_share 12824 Oct 1 05:03 .apps.db-journal
-rw-r--r-- 1 owner system_share 16384 Oct 2 15:51 .home.db
-rw-r--r-- 1 owner system_share 12824 Oct 2 15:51 .home.db-journal
drwxr-sr-x 2 owner system_share 4096 Oct 1 05:04 .pref
-rw-r--r-- 1 owner system_share 20480 Oct 2 15:51 .widget_suggestion.db
-rw-r--r-- 1 owner system_share 16928 Oct 1 05:03 .widget_suggestion.db-journal
drwxrwsrwx 2 root system_share 4096 Oct 2 15:56 testme
sh-3.2# cd /opt/usr/home/owner/apps_rw/com.samsung.w-home/data/
sh-3.2# ls -a1l
total 128
drwxrwsr-x 4 owner system_share 4096 Oct 2 15:56 .
drwxr-xr-x 5 owner users 4096 Apr 28 10:04 ..
-rw-r--r-- 1 owner system_share 16384 Oct 2 15:51 .apps.db
-rw-r--r-- 1 owner system_share 12824 Oct 1 05:03 .apps.db-journal
-rw-r--r-- 1 owner system_share 16384 Oct 2 15:51 .home.db
-rw-r--r-- 1 owner system_share 12824 Oct 2 15:51 .home.db-journal
drwxr-sr-x 2 owner system_share 4096 Oct 1 05:04 .pref
-rw-r--r-- 1 owner system_share 20480 Oct 2 15:51 .widget_suggestion.db
-rw-r--r-- 1 owner system_share 16928 Oct 1 05:03 .widget_suggestion.db-journal
drwxrwsrwx 2 root system_share 4096 Oct 2 15:56 testme
A
Aha, seems only 1 folder...
So I need only 1 time play with file
Code:
.home.db
B
Code:
D:\SDB\SDB260>sdb pull /opt/usr/home/owner/apps_rw/com.samsung.w-home/data/ .\ftd4\widget
pulled .widget_suggestion.db-journal 100% 16KB
pulled .home.db 100% 16KB
pulled .apps.db 100% 16KB
pulled .apps.db-journal 100% 12KB
pulled .home.db-journal 100% 12KB
pulled .widget_suggestion.db 100% 20KB
pulled 55157627a4c4b5a9bdfc405a197f194d84543b01 100% 44 B
pulled f657e4e15e35a0c1fa53c462020df9ebec5c19ce 100% 36 B
pulled 3cbacb5376e2dee294232c956838fc1954985ea5 100% 49 B
pulled ec6b88021747c602dffdafe2e809beb84d820488 100% 43 B
pulled 1e3463dc2080de6e30d6f7ee28b65fcdfa33d0d5 100% 49 B
pulled d6ea693302f3e6a1b8bb827892323e8ed76a4274 100% 42 B
12 file(s) pulled. 0 file(s) skipped.
/opt/usr/home/owner/apps_rw/com.samsung.w-home/data/ 126 KB/s (96087 bytes in 0.740s)
Maybe more clear what is inside db...
C
If I push with SDB then... hmmm... maybe this is why it fails... maybe...
Code:
sh-3.2# cd /opt/usr/home/owner/apps_rw/com.samsung.w-home/data/
sh-3.2# ls -a1l
total 128
drwxrwsr-x 4 owner system_share 4096 Oct 2 16:13 .
drwxr-xr-x 5 owner users 4096 Apr 28 10:04 ..
-rw-r--r-- 1 owner system_share 16384 Oct 2 15:51 .apps.db
-rw-r--r-- 1 owner system_share 12824 Oct 1 05:03 .apps.db-journal
[COLOR="Red"]-rwxr-xrwx[/COLOR] 1 root system_share 16384 Oct 2 02:14 .home.db
-rw-r--r-- 1 owner system_share 12824 Oct 2 15:51 .home.db-journal
drwxr-sr-x 2 owner system_share 4096 Oct 1 05:04 .pref
-rw-r--r-- 1 owner system_share 20480 Oct 2 15:51 .widget_suggestion.db
-rw-r--r-- 1 owner system_share 16928 Oct 1 05:03 .widget_suggestion.db-journal
drwxrwsrwx 2 root system_share 4096 Oct 2 15:56 testme
Pulled files via SDB from my SM-R820...
Not all possible but few... :good: :good:
Compared with BTG6 Firmware rootfs.img from GW3...
Code:
spo2 app is not enabled. [COLOR="Red"][B]skip[/B][/COLOR]
This is inside...
Code:
/usr/apps/com.samsung.w-manager-service/bin/[COLOR="Red"][B]w-manager-service[/B][/COLOR]
Best Regards
I have now rooted Tizen 5.5 for my SM-R820... CTH8...
Need to prepare few things and backup,,,
Then I will "simple" edit:
Code:
home_default_items.xml
in Default Folder of CSC Preconfig crap...
Code:
<?xml version="1.0" encoding="UTF-8"?>
<data>
<favorite>
<packagename>[email protected]</packagename>
<classname>[email protected]</classname>
<screen>0</screen>
<cellX>0</cellX>
<cellY>0</cellY>
</favorite>
<favorite>
<packagename>com.samsung.app-shortcut-widget</packagename>
<classname>com.samsung.app-shortcut-widget</classname>
<screen>1</screen>
<cellX>1</cellX>
<cellY>0</cellY>
</favorite>
<favorite>
<packagename>[email protected]</packagename>
<classname>[email protected]</classname>
<screen>0</screen>
<cellX>1</cellX>
<cellY>0</cellY>
</favorite>
<favorite>
<packagename>[email protected]</packagename>
<classname>[email protected]</classname>
<screen>0</screen>
<cellX>1</cellX>
<cellY>1</cellY>
</favorite>
<favorite>
<packagename>com.samsung.weather-widget</packagename>
<classname>com.samsung.weather-widget</classname>
<screen>1</screen>
<cellX>0</cellX>
<cellY>0</cellY>
</favorite>
<favorite>
<packagename>[email protected]</packagename>
<classname>[email protected]</classname>
<screen>2</screen>
<cellX>0</cellX>
<cellY>0</cellY>
</favorite>
</data>
Maybe I add or I replace...
Code:
[COLOR="Red"][B]oxygensaturation[/B][/COLOR]@com.samsung.shealth.widget
We will see if this is enough...
Best Regards
How did you root 5.5? I haven't been able to find any info on rooting these other than some old rooted firnwares
Code:
sdb root on
sdb shell mount -vo remount,rw /opt/system/csc/
sdb push SW_Configuration.xml /opt/system/csc/mps/CSC/
sdb push home_default_items.xml /opt/system/csc/preconfig/DEF/usr/homescreen/
First attempt...
Changed 1 Byte to prevent CTI4 FOTA...
@betterl8thannvr
Your Model Name is what?
Because I've play with my SM-R820...
Best Regards
@adfree ah, mine fails when I try sdb root on
>sdb root on
* The version of SDB client (2.3.0) is not same with that of SDB server (4.2.12).
It may cause version compatibility problems.
It is recommended to use SDB server with version 2.3.0. *
Permission denied
Any idea how to get around that?
Edit: I have SM-R825U
sdb root can be done once you connect with Tizen Studio right ?
First attempt not bring Blood Oxygen to me...
Second attempt...
Code:
D:\SDB\SDB260>sdb root on
Switched to 'root' account mode
D:\SDB\SDB260>sdb shell mount -vo remount,rw /opt/system/csc/
mount: /dev/mmcblk0p16 mounted on /opt/system/csc.
D:\SDB\SDB260>sdb shell mkdir /opt/system/csc/preconfig/DBT/usr/homescreen/
mkdir: cannot create directory `/opt/system/csc/preconfig/DBT/usr/homescreen/': No such file or directory
D:\SDB\SDB260>sdb shell
sh-3.2# cd /opt/system/csc/preconfig/DBT/
sh-3.2# ls -a1l
total 8
drwxr-xr-x 4 root root 1024 Jun 16 16:10 .
drwxr-xr-x 71 root root 1024 Jun 16 16:10 ..
drwxr-xr-x 2 root root 1024 Jun 16 16:10 feature
drwxr-xr-x 2 root root 1024 Jun 16 16:10 preset
sh-3.2# mkdir usr
sh-3.2# cd usr
sh-3.2# mkdir homescreen
sh-3.2# exit
exit
D:\SDB\SDB260>sdb push home_default_items.xml /opt/system/csc/preconfig/DBT/usr/homescreen/
pushed home_default_items.xml 100% 1KB
1 file(s) pushed. 0 file(s) skipped.
home_default_items.xml 7 KB/s (1387 bytes in 0.180s)
D:\SDB\SDB260>sdb shell
sh-3.2# cd /opt/system/csc/preconfig/DBT/usr/homescreen/
sh-3.2# ls -a1l
total 7
drwxrwxrwx 2 root root 1024 Oct 3 14:03 .
drwxrwxrwx 3 root root 1024 Oct 3 14:03 ..
-rwxr-xrwx 1 root root 1387 Oct 3 07:49 home_default_items.xml
sh-3.2# reboot
Rebooting.
@EQMOD
You need Root aka Super User aka su Binary inside Firmware... this is Linux stuff...
@betterl8thannvr
You are in similar situation like me...
No latest files leaked...
ATF2 is latest leaked Files for netOdin...
So much harder to get Root Access...
I have at the moment limited time to explain nor to make the files for you...
Maybe next days more time...
Best Regards
adfree said:
First attempt not bring Blood Oxygen to me...
Second attempt...
Code:
D:\SDB\SDB260>sdb root on
Switched to 'root' account mode
D:\SDB\SDB260>sdb shell mount -vo remount,rw /opt/system/csc/
mount: /dev/mmcblk0p16 mounted on /opt/system/csc.
D:\SDB\SDB260>sdb shell mkdir /opt/system/csc/preconfig/DBT/usr/homescreen/
mkdir: cannot create directory `/opt/system/csc/preconfig/DBT/usr/homescreen/': No such file or directory
D:\SDB\SDB260>sdb shell
sh-3.2# cd /opt/system/csc/preconfig/DBT/
sh-3.2# ls -a1l
total 8
drwxr-xr-x 4 root root 1024 Jun 16 16:10 .
drwxr-xr-x 71 root root 1024 Jun 16 16:10 ..
drwxr-xr-x 2 root root 1024 Jun 16 16:10 feature
drwxr-xr-x 2 root root 1024 Jun 16 16:10 preset
sh-3.2# mkdir usr
sh-3.2# cd usr
sh-3.2# mkdir homescreen
sh-3.2# exit
exit
D:\SDB\SDB260>sdb push home_default_items.xml /opt/system/csc/preconfig/DBT/usr/homescreen/
pushed home_default_items.xml 100% 1KB
1 file(s) pushed. 0 file(s) skipped.
home_default_items.xml 7 KB/s (1387 bytes in 0.180s)
D:\SDB\SDB260>sdb shell
sh-3.2# cd /opt/system/csc/preconfig/DBT/usr/homescreen/
sh-3.2# ls -a1l
total 7
drwxrwxrwx 2 root root 1024 Oct 3 14:03 .
drwxrwxrwx 3 root root 1024 Oct 3 14:03 ..
-rwxr-xrwx 1 root root 1387 Oct 3 07:49 home_default_items.xml
sh-3.2# reboot
Rebooting.
@EQMOD
You need Root aka Super User aka su Binary inside Firmware... this is Linux stuff...
@betterl8thannvr
You are in similar situation like me...
No latest files leaked...
ATF2 is latest leaked Files for netOdin...
So much harder to get Root Access...
I have at the moment limited time to explain nor to make the files for you...
Maybe next days more time...
Best Regards
Click to expand...
Click to collapse
What happened after reboot ?
thanks @adfree, I think I can figure out how to root on ATF2, but you said you had root on 5.5, so I am quite curious about how to do that without the leaked files.
I will keep poking at it.
Hmm, well, flashing back to ATF2 is being troublesome. It fails every time, so I now have a small, expensive brick.
<ID:0/001> 192.168.49.1
<ID:0/001> Odin engine v(ID:1.0000)..
<ID:0/001> File analysis..
<ID:0/001> SetupConnection..
<ID:0/001> Initialzation..
<ID:0/001> Set PIT file..
<ID:0/001> DO NOT TURN OFF TARGET!!
<ID:0/001> Get PIT for mapping..
<ID:0/001> Get PIT Transmission
<ID:0/001> Firmware update start..
<ID:0/001> SingleDownload.
<ID:0/001> cm.bin
<ID:0/001>
<ID:0/001> XmitData
<ID:0/001> Complete(Write) operation failed.
<ID:0/001> Removed!!
<OSM> All threads completed. (succeed 0 / failed 1)
Code:
XmitData
Is IMHO out of luck transfer Error...
I have fixed this by trying again...
@betterl8thannvr
Your GW2 still have working:
Code:
download wirelss
About ATF2 I can only remember I have uploaded "corrected" CSC, because invalid file inside...
Will check my HDD...
Best Regards
Tiny progress...
A
Seems I found my mistake...
SDB push change Permissions to file...
Code:
D:\SDB\SDB260>sdb push .home.db /opt/usr/apps/com.samsung.w-home/data/
pushed .home.db 100% 16KB
1 file(s) pushed. 0 file(s) skipped.
.home.db 84 KB/s (16384 bytes in 0.190s)
D:\SDB\SDB260>sdb shell
sh-3.2# cd /opt/usr/apps/com.samsung.w-home/data/
sh-3.2# ls -a1l
total 124
drwxrwsr-x 3 owner system_share 4096 Oct 5 00:33 .
drwxr-xr-x 5 owner users 4096 Oct 3 14:10 ..
-rw-r--r-- 1 owner system_share 16384 Oct 3 14:53 .apps.db
-rw-r--r-- 1 owner system_share 12824 Oct 3 14:53 .apps.db-journal
-rwxr-xrwx 1 root system_share 16384 Oct 3 21:27 .home.db
-rw-r--r-- 1 owner system_share 12824 Oct 5 00:04 .home.db-journal
drwxr-sr-x 2 owner system_share 4096 Oct 3 14:15 .pref
-rw-r--r-- 1 owner system_share 20480 Oct 3 14:15 .widget_suggestion.db
-rw-r--r-- 1 owner system_share 16928 Oct 3 14:15 .widget_suggestion.db-journal
sh-3.2# chmod 644 .home.db
sh-3.2# ls -a1l
total 124
drwxrwsr-x 3 owner system_share 4096 Oct 5 00:33 .
drwxr-xr-x 5 owner users 4096 Oct 3 14:10 ..
-rw-r--r-- 1 owner system_share 16384 Oct 3 14:53 .apps.db
-rw-r--r-- 1 owner system_share 12824 Oct 3 14:53 .apps.db-journal
-rw-r--r-- 1 root system_share 16384 Oct 3 21:27 .home.db
-rw-r--r-- 1 owner system_share 12824 Oct 5 00:04 .home.db-journal
drwxr-sr-x 2 owner system_share 4096 Oct 3 14:15 .pref
-rw-r--r-- 1 owner system_share 20480 Oct 3 14:15 .widget_suggestion.db
-rw-r--r-- 1 owner system_share 16928 Oct 3 14:15 .widget_suggestion.db-journal
So I have to correct it...
But this require ROOT...
Tested .home.db from GW3...
Blood Oxygen still blocked...
Hmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmm.
So this means IMHO... I have to replace
Code:
com.samsung.w-home.home-service
https://forum.xda-developers.com/showpost.php?p=83626487&postcount=6
Best Regards
adfree said:
Tiny progress...
A
Seems I found my mistake...
SDB push change Permissions to file...
Code:
D:\SDB\SDB260>sdb push .home.db /opt/usr/apps/com.samsung.w-home/data/
pushed .home.db 100% 16KB
1 file(s) pushed. 0 file(s) skipped.
.home.db 84 KB/s (16384 bytes in 0.190s)
D:\SDB\SDB260>sdb shell
sh-3.2# cd /opt/usr/apps/com.samsung.w-home/data/
sh-3.2# ls -a1l
total 124
drwxrwsr-x 3 owner system_share 4096 Oct 5 00:33 .
drwxr-xr-x 5 owner users 4096 Oct 3 14:10 ..
-rw-r--r-- 1 owner system_share 16384 Oct 3 14:53 .apps.db
-rw-r--r-- 1 owner system_share 12824 Oct 3 14:53 .apps.db-journal
-rwxr-xrwx 1 root system_share 16384 Oct 3 21:27 .home.db
-rw-r--r-- 1 owner system_share 12824 Oct 5 00:04 .home.db-journal
drwxr-sr-x 2 owner system_share 4096 Oct 3 14:15 .pref
-rw-r--r-- 1 owner system_share 20480 Oct 3 14:15 .widget_suggestion.db
-rw-r--r-- 1 owner system_share 16928 Oct 3 14:15 .widget_suggestion.db-journal
sh-3.2# chmod 644 .home.db
sh-3.2# ls -a1l
total 124
drwxrwsr-x 3 owner system_share 4096 Oct 5 00:33 .
drwxr-xr-x 5 owner users 4096 Oct 3 14:10 ..
-rw-r--r-- 1 owner system_share 16384 Oct 3 14:53 .apps.db
-rw-r--r-- 1 owner system_share 12824 Oct 3 14:53 .apps.db-journal
-rw-r--r-- 1 root system_share 16384 Oct 3 21:27 .home.db
-rw-r--r-- 1 owner system_share 12824 Oct 5 00:04 .home.db-journal
drwxr-sr-x 2 owner system_share 4096 Oct 3 14:15 .pref
-rw-r--r-- 1 owner system_share 20480 Oct 3 14:15 .widget_suggestion.db
-rw-r--r-- 1 owner system_share 16928 Oct 3 14:15 .widget_suggestion.db-journal
So I have to correct it...
But this require ROOT...
Tested .home.db from GW3...
Blood Oxygen still blocked...
Hmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmm.
So this means IMHO... I have to replace
Code:
com.samsung.w-home.home-service
https://forum.xda-developers.com/showpost.php?p=83626487&postcount=6
Best Regards
Click to expand...
Click to collapse
Could you upload both binaries here. (GW3, GA2) and home.db Let me check both
@EQMOD
Soon I have rooted CTI4 uploaded for SM-R820...
Your Model Name is exactly what?
In your posts I see only GWA2...
Best Regards
adfree said:
@EQMOD
Soon I have rooted CTI4 uploaded for SM-R820...
Your Model Name is exactly what?
In your posts I see only GWA2...
Best Regards
Click to expand...
Click to collapse
its SM-R820