Database Develop

Output from the mount command.

I need the output from the mount command. This can be done via adb, SSHDroid, or Android Terminal Emulator.

Code:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/system /system ext3 ro,noatime,nodiratime,barrier=1,data=ordered 0 0
/dev/block/userdata /data ext3 rw,nosuid,nodev,noatime,nodiratime,errors=continue,barrier=1,data=ordered 0 0
/dev/block/cache /cache ext3 rw,nosuid,nodev,noatime,nodiratime,errors=continue,barrier=1,data=ordered 0 0
tmpfs /data/tmp tmpfs rw,relatime,size=2048k 0 0
/dev/block/pds /pds ext3 rw,nosuid,nodev,noatime,nodiratime,errors=continue,barrier=1,data=ordered 0 0
/dev/block/preinstall /preinstall ext3 rw,nosuid,nodev,noatime,nodiratime,barrier=1,data=ordered 0 0
/dev/block/vold/179:1 /mnt/sdcard-ext vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/mnt/sdcard-ext /mnt/sdcard-ext ecryptfs rw,dirsync,nosuid,nodev,noexec,relatime,ecryptfs_sig=0ee41f55517175f3,ecryptfs_cipher=aes,ecryptfs_key_bytes=32,ecryptfs_passthrough,no_new_encrypted 0 0
/dev/block/vold/179:57 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:57 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/mnt/sdcard /mnt/sdcard ecryptfs rw,dirsync,nosuid,nodev,noexec,relatime,ecryptfs_sig=0ee41f55517175f3,ecryptfs_cipher=aes,ecryptfs_key_bytes=32,ecryptfs_passthrough,no_new_encrypted 0 0
There you go, hope it helps

Awesome, there are some good hints toward root in there.
Can you give the output commands below?
ls -a -l /data
ls -a -l /data/tmp
ls -a -l /dev/pts

For ls -a -l /data, it gives 'opendir failed, Permission denied'. ls -a -l /data/tmp gives the following:
Code:
-rw-rw-rw- app_45 app_45 45 2011-08-07 02:11 .scannerfile.txt
-rw-r--r-- mot_tcmd mot_tcmd 3 2011-08-06 13:20 ap_tcmd.pid
srwxrwxrwx vpn vpn 2011-08-06 13:20 vpnc_app_to_dmn
--w--w---- vpn vpn 0 2011-08-06 13:20 vpnc_dmn_lock
-rw------- root root 138 2011-08-06 13:20 smc_ps.log
ls -a -l /dev/pts gives the following:
Code:
crw------- shell shell 136, 0 2011-08-07 14:32 0

Please give me the output.
ls -a -l -R /dev
ps
id
Please give me a copy.
/proc/kallsyms

Here are the outputs from the last request edgan.....
ls -a -l -R /dev - Too big to paste, attaching output in a txt file
ps -
Code:
[email protected]_solana:/$ ps
USER PID PPID VSIZE RSS WCHAN PC NAME
root 1 0 440 292 ffffffff 00000000 S /init
root 2 0 0 0 ffffffff 00000000 S kthreadd
root 3 2 0 0 ffffffff 00000000 S ksoftirqd/0
root 4 2 0 0 ffffffff 00000000 S migration/0
root 7 2 0 0 ffffffff 00000000 S events/0
root 9 2 0 0 ffffffff 00000000 S khelper
root 10 2 0 0 ffffffff 00000000 S async/mgr
root 11 2 0 0 ffffffff 00000000 S pm
root 12 2 0 0 ffffffff 00000000 S suspend
root 13 2 0 0 ffffffff 00000000 S irq/142-omap_em
root 14 2 0 0 ffffffff 00000000 S irq/143-omap_em
root 15 2 0 0 ffffffff 00000000 S sync_supers
root 16 2 0 0 ffffffff 00000000 S bdi-default
root 17 2 0 0 ffffffff 00000000 S kblockd/0
root 19 2 0 0 ffffffff 00000000 S omap2_mcspi
root 20 2 0 0 ffffffff 00000000 S cpcap_irq
root 21 2 0 0 ffffffff 00000000 S khubd
root 22 2 0 0 ffffffff 00000000 S kmmcd
root 23 2 0 0 ffffffff 00000000 S spi_tty_wq
root 24 2 0 0 ffffffff 00000000 S mboxd
root 25 2 0 0 ffffffff 00000000 S khungtaskd
root 26 2 0 0 ffffffff 00000000 S kswapd0
root 27 2 0 0 ffffffff 00000000 S aio/0
root 29 2 0 0 ffffffff 00000000 S ecryptfs-kthrea
root 30 2 0 0 ffffffff 00000000 S crypto/0
root 46 2 0 0 ffffffff 00000000 S kxtf9_wq
root 47 2 0 0 ffffffff 00000000 S mdm_ctrl_wq
root 54 2 0 0 ffffffff 00000000 S file-storage
root 55 2 0 0 ffffffff 00000000 S qtouch_obp_ts_w
root 56 2 0 0 ffffffff 00000000 S als_wq
root 57 2 0 0 ffffffff 00000000 S media_cache_mgm
root 58 2 0 0 ffffffff 00000000 S w1_bus_master1
root 59 2 0 0 ffffffff 00000000 S kstriped
root 60 2 0 0 ffffffff 00000000 S kondemand/0
root 62 2 0 0 ffffffff 00000000 S khotplug/0
root 64 2 0 0 ffffffff 00000000 S kmothotplug/0
root 66 2 0 0 ffffffff 00000000 S usbhid_resumer
root 67 2 0 0 ffffffff 00000000 S binder
root 68 2 0 0 ffffffff 00000000 S ipc_rec_queue/0
root 70 2 0 0 ffffffff 00000000 S l2cap
root 71 2 0 0 ffffffff 00000000 S krfcommd
root 72 2 0 0 ffffffff 00000000 S dsi_upd
root 73 2 0 0 ffffffff 00000000 S dsi2_upd
root 74 2 0 0 ffffffff 00000000 S HDMIWORK
root 75 2 0 0 ffffffff 00000000 S mmcqd
root 76 2 0 0 ffffffff 00000000 S mapphone_esd
root 77 2 0 0 ffffffff 00000000 S mapphone_panel
root 78 2 0 0 ffffffff 00000000 S mmcqd
root 79 2 0 0 ffffffff 00000000 S pvr_timer/0
root 81 2 0 0 ffffffff 00000000 S cpcap_accy
root 82 2 0 0 ffffffff 00000000 S OMAPVOUT
root 83 2 0 0 ffffffff 00000000 S OMAPVOUT
root 84 2 0 0 ffffffff 00000000 S OMAPVOUT
root 85 2 0 0 ffffffff 00000000 S s3d_workqueue
root 86 2 0 0 ffffffff 00000000 S irq/131-ABE
root 87 1 316 172 ffffffff 00000000 S /sbin/ueventd
root 88 2 0 0 ffffffff 00000000 S kjournald
root 98 2 0 0 ffffffff 00000000 S kjournald
root 108 2 0 0 ffffffff 00000000 S kjournald
root 111 2 0 0 ffffffff 00000000 S flush-179:32
root 121 2 0 0 ffffffff 00000000 S kjournald
root 131 2 0 0 ffffffff 00000000 S kjournald
mot_tpapi 162 1 884 356 ffffffff 00000000 S /system/bin/tf_daemon
shell 164 1 3448 172 ffffffff 00000000 S /sbin/adbd
system 165 1 864 192 ffffffff 00000000 S /system/bin/servicemanager
root 167 1 3920 412 ffffffff 00000000 S /system/bin/vold
vpn 170 1 908 204 ffffffff 00000000 S /system/bin/tund
root 171 1 4300 424 ffffffff 00000000 S /system/bin/netd
root 172 1 728 176 ffffffff 00000000 S /system/bin/debuggerd
radio 173 1 18296 884 ffffffff 00000000 S /system/bin/rild
root 175 1 880 280 ffffffff 00000000 S /system/bin/usbd
mot_accy 176 1 1348 360 ffffffff 00000000 S /system/bin/battd
bluetooth 177 1 908 256 ffffffff 00000000 S /system/bin/uim-sysfs
media 178 1 23452 396 ffffffff 00000000 S /system/bin/syslink_daemon.out
root 180 1 87888 14392 ffffffff 00000000 S zygote
media 181 1 45708 3380 ffffffff 00000000 S /system/bin/mediaserver
bluetooth 182 1 1332 324 ffffffff 00000000 S /system/bin/dbus-daemon
root 183 1 904 280 ffffffff 00000000 S /system/bin/installd
keystore 184 1 1800 188 ffffffff 00000000 S /system/bin/keystore
mot_whisper 185 1 2336 320 ffffffff 00000000 S /system/bin/whisperd
mot_tcmd 186 1 9312 756 ffffffff 00000000 S /system/bin/tcmd
compass 187 1 1136 244 ffffffff 00000000 S /system/bin/akmd2
radio 190 1 1104 248 ffffffff 00000000 S /system/bin/ftmipcd
root 191 1 888 212 ffffffff 00000000 S /system/bin/mdm_panicd
mot_tpapi 193 1 1204 324 ffffffff 00000000 S /system/bin/secclkd
vpn 194 1 6192 1928 ffffffff 00000000 S /system/bin/vpnclientpm
root 195 2 0 0 ffffffff 00000000 S hci0
root 201 2 0 0 ffffffff 00000000 S pvr_workqueue
root 205 2 0 0 ffffffff 00000000 S ipu_resources
root 210 2 0 0 ffffffff 00000000 S ipu_clean_up
system 250 180 231884 76144 ffffffff 00000000 S system_server
root 259 2 0 0 ffffffff 00000000 S pvr_display_syn
system 342 180 115492 28124 ffffffff 00000000 S com.android.systemui
app_9 361 180 117872 24660 ffffffff 00000000 S com.swype.android.inputmethod
radio 367 180 137080 30588 ffffffff 00000000 S com.android.phone
app_14 368 180 200828 25892 ffffffff 00000000 S com.motorola.blur.service.main
app_55 373 180 119124 28588 ffffffff 00000000 S com.motorola.blur.service.blur
app_2 379 180 98644 14184 ffffffff 00000000 S com.motorola.Dlna
system 380 180 115128 20116 ffffffff 00000000 S com.motorola.process.system
app_37 386 180 97272 14060 ffffffff 00000000 S com.motorola.batterymanager
app_8 402 180 112416 16240 ffffffff 00000000 S com.nuance.android.vsuite.vsuiteapp
app_64 437 180 97288 15092 ffffffff 00000000 S com.motorola.PerformanceManager
app_14 442 180 123912 23700 ffffffff 00000000 S com.motorola.contacts
system 444 180 97216 14684 ffffffff 00000000 S com.motorola.android.portal
app_4 450 180 102692 19420 ffffffff 00000000 S com.motorola.usb
app_32 532 180 102916 15680 ffffffff 00000000 S android.tts
app_150 563 180 123856 34124 ffffffff 00000000 S android.process.acore
app_25 644 180 98008 15776 ffffffff 00000000 S com.fusionone.android.sync.service
app_128 1030 180 117460 26164 ffffffff 00000000 S com.aws.android.elite
app_127 1096 180 119908 23664 ffffffff 00000000 S com.anddoes.fancywidgets
app_31 1128 180 129224 19356 ffffffff 00000000 S com.motorola.blur.home.newsstatusweather
app_103 8853 180 98604 15388 ffffffff 00000000 S com.android.bluetooth
system 9923 180 97448 17420 ffffffff 00000000 S com.motorola.android.datamanager
app_99 10549 180 97116 15996 ffffffff 00000000 S com.motorola.globalunplug
app_31 10556 180 97112 15328 ffffffff 00000000 S com.motorola.android.buacontactadapter
app_18 12210 180 128204 23476 ffffffff 00000000 S com.google.process.gapps
app_31 12252 180 100948 17072 ffffffff 00000000 S com.motorola.blur.home
app_145 12401 180 102888 15928 ffffffff 00000000 S com.google.android.apps.genie.geniewidget
app_41 12471 180 113980 18880 ffffffff 00000000 S com.google.android.apps.maps:NetworkLocationService
app_130 12774 180 129940 25720 ffffffff 00000000 S com.handcent.nextsms
app_75 12816 180 97308 15608 ffffffff 00000000 S com.motorola.bluetooth
app_88 13116 180 99660 16556 ffffffff 00000000 S com.vzw.hss.myverizon
app_31 13136 180 112364 17716 ffffffff 00000000 S com.motorola.blur.home.other
app_118 14151 180 106644 17940 ffffffff 00000000 S com.motorola.blurgallery
app_72 14281 180 98360 16392 ffffffff 00000000 S com.motorola.dock.service
app_44 14767 180 109784 18884 ffffffff 00000000 S com.motorola.im.service
app_31 14819 180 134244 23164 ffffffff 00000000 S com.motorola.blur.friendfeed
app_133 14926 180 134508 36676 ffffffff 00000000 S com.quoord.tapatalkxda.activity
app_45 15406 180 102560 19924 ffffffff 00000000 S android.process.media
app_115 15415 180 101884 17408 ffffffff 00000000 S com.google.android.gm
app_153 15423 180 105204 19068 ffffffff 00000000 S com.amazon.venezia
radio 15464 173 2100 512 ffffffff 00000000 S /system/bin/pppd-ril
app_135 15467 180 99520 16056 ffffffff 00000000 S com.smartandroidapps.equalizer
app_74 15524 180 101240 15872 ffffffff 00000000 S com.motorola.process.system
app_123 15689 180 101988 22768 ffffffff 00000000 S com.facebook.katana
app_118 15757 180 105536 19724 ffffffff 00000000 S com.motorola.gallerywidget
app_31 15778 180 101820 17412 ffffffff 00000000 S com.motorola.im.widget
app_31 15785 180 105648 18844 ffffffff 00000000 S com.motorola.blur.home.message
app_31 15794 180 101496 17368 ffffffff 00000000 S com.motorola.bookmarkswidget
app_146 15836 180 97760 18656 ffffffff 00000000 S fr.depoortere.android.CircleBatteryWidget
system 15907 180 98812 17228 ffffffff 00000000 S com.android.settings
app_83 15918 180 100060 19432 ffffffff 00000000 S com.slacker.radio
app_116 15926 180 100940 20736 ffffffff 00000000 S com.vcast.mediamanager
app_117 15935 180 117744 26748 ffffffff 00000000 S com.android.vending
app_16 15960 180 101856 18972 ffffffff 00000000 S com.google.android.googlequicksearchbox
shell 15997 164 792 372 c0091c38 afd0c43c S /system/bin/sh
shell 16066 15997 948 340 00000000 afd0b4ec R ps
app_104 30297 180 104568 14880 ffffffff 00000000 S com.cequint.cityid
[email protected]_solana:/$
id -
Code:
[email protected]_solana:/$ id
uid=2000(shell) gid=2000(shell) groups=1003(graphics),1004(input),1007(log),1009(mount),1011(adb),1015(sdcard_rw),3001(net_bt_admin),3002(net_bt),3003(inet)
/proc/kallsyms - attached.

Here's output from busybox ps there's a bit more info about some processes.
On a side note dosu won't work for us, it looks for /lib/ld-linux.so.3 which is why it receives not found when running. Must be there in the Atrix

If you need any other confirmations I would like to help
Sent from my DROID3 using XDA App

Just noticed this in data/tmp
-r-xr-Srwx 1 1000 1000 14 Aug 8 17:01 webtop_overlay
It contains:
1,0,0,0,0,0,0
Its odd because there is no webtop. I thought it was created on reset, but the last was 20 min after.

eww245 said:
Just noticed this in data/tmp
-r-xr-Srwx 1 1000 1000 14 Aug 8 17:01 webtop_overlay
It contains:
1,0,0,0,0,0,0
Its odd because there is no webtop. I thought it was created on reset, but the last was 20 min after.
Click to expand...
Click to collapse
This is from MIUICamera I found it somewhere here on xda, it only writes the first time it esecutes after a reboot and the permissions are different every time . HOW DOES IT HAVE SYSTEM ACCESS?
I'm going to see if I can find the source.

I've seen that too, and plugged it into the atrix dock (using extension cables) and it DOES work...surprisingly.

What works? Does it just mirror or are you actually running webtop?

It's actually webtop, that pseudo-gnome interface.

LOL.. how well does it run on the 512MB? The webtop devices were supposed to have 1GB for the added webtop functionality.

Is the pulse audio race exploit possible then?
Sent from my DROID3 using XDA App

Runs and usable are DIFFERENT things entirely. If webtop lags as bad as it does on 1GB, just imagine. :/
AFAIK, the D3 only has ALSA mods loaded, not positive about pulse. Something to look into though. Going through DMESG, I didn't see any references.

eww245 said:
Just noticed this in data/tmp
-r-xr-Srwx 1 1000 1000 14 Aug 8 17:01 webtop_overlay
It contains:
1,0,0,0,0,0,0
Its odd because there is no webtop. I thought it was created on reset, but the last was 20 min after.
Click to expand...
Click to collapse
I just rebooted, it's not there.
Though I did see it before.

Jewremy said:
I just rebooted, it's not there.
Though I did see it before.
Click to expand...
Click to collapse
Plug in HDMI and it comes back.

Well MIUI does not give out their source there's actually a thread dedicated to the legality of it. The apk is signed with Android SignAPK from what I can see that's what Google uses. So either they hacked the signature or it is an open signature? I don't know how the apk signing works.
What does anyone think is this worth looking into.Is this a possible exploit? It's kind of odd that a 3rd party app can have system access.
pplude you gotta start poking around in there theirs probably something worthwhile especially since it's not a full webtop.
edgan sorry about hijacking this thread, it's for a good cause
This is where I got the apk forum.xda-developers.com/showpost.php?p=15307536&postcount=167 it's the fixed2, and it's a pretty good camera app.
[edit] So maybe it's not this app. The graphics drivers maybe, if hdmi also produces it.

[Q] - High io activity ?

Hi all,
I am trying to track down the slowness problem on my sgs.
I think that the problem is the io system.
Can someone tell me his thoughts about this iostat output ?
Code:
CPU: 13.1% usr 2.7% sys 0.0% nic 0.0% idle 82.4% io 0.0% irq 1.5% sirq
Load average: 3.46 2.08 1.50 2/542 4702
PID PPID USER STAT VSZ %VSZ CPU %CPU COMMAND
2353 90 10115 S 176m 48.2 0 11.5 {d.process.acore} android.process.
690 90 system S 277m 75.7 0 1.7 system_server
62 2 root DW 0 0.0 0 1.5 [mmcqd]
5 2 root RW 0 0.0 0 1.0 [events/0]
809 90 system S 160m 43.8 0 0.3 {ndroid.systemui} com.android.syst
2148 2141 root R 2260 0.6 0 0.3 /system/xbin/busybox /sbin/top
15 2 root SW 0 0.0 0 0.3 [kondemand/0]
822 90 radio S 172m 46.9 0 0.1 {m.android.phone} com.android.phon
2561 90 10093 S 138m 37.8 0 0.1 org.dayup.gtask
100 1 compass S 2880 0.7 0 0.1 /system/bin/orientationd
861 90 10044 S 226m 61.8 0 0.0 {e.process.gapps} com.google.proce
31608 1 10175 S 186m 50.8 0 0.0 {udsandsheepfree} com.hg.cloudsand
2681 90 10061 S 174m 47.6 0 0.0 {ogle.android.gm} com.google.andro
2711 90 10054 S 169m 46.0 0 0.0 {LocationService} com.google.andro
2626 90 10054 S 166m 45.5 0 0.0 {droid.apps.maps} com.google.andro
2318 90 10104 S 151m 41.3 0 0.0 {droid.apps.plus} com.google.andro
1668 90 10084 S 151m 41.1 0 0.0 {nputmethod.axt9} com.sec.android.
2733 90 10054 S 150m 41.1 0 0.0 {onFriendService} com.google.andro
2726 90 10054 S 144m 39.4 0 0.0 {s:FriendService} com.google.a

mods please close thread

closed

How to compile TWRP recovery?
I followed the guide here http://rootzwiki.com/topic/23903-how-to-compile-twrp-from-source/
To summarize...
1. Install Linux
2. Set up CM10 build environment - this is sssssooooo easy and there are loads of guides available with just a simple google search.
3. Repo sync
4. Build standard cm10 from source
5. Delete the contents of the ~/android/system/bootable/recovery and replace with https://github.com/TeamWin/Team-Win-Recovery-Project/ - i just clicked on the download zip button on the top left and unzipped into the folder but am sure there is a proper way of doing this... zip clone???
6. gedit ~/android/system/device/samsung/galaxys2-common/recovery.rc and add: export LD_LIBRARY_PATH .:/sbin
7. gedit ~/android/system/device/samsung/n7000/BoardConfig.mk and add the following to the bottom of the file
#twrp
DEVICE_RESOLUTION := 800x1280
8. cd ~/android/system
9. make -j3 bootimage (if you have a quad core processor make -j5 bootimage)
10. you can find your boot.img at ~/android/system/out/target/product/n7000
11. Copy to SDCARD and flash with mobile odin
12. Done!!!!!

good work. appreciate the effort you have put in.
looking into it now.

Finally here, good work. Will try it as i'm already using TWRP in my N7.
Enviat des d'es meu Nexus 7 amb so Tapatalk2

im using TWRP to flash rom for N8013 and work great.Thanks

nice to see u
subscribed.

You Should pm entropy
Sent from my GT-N7000 using Tapatalk 2

I have sent him a PM
Sent from my GT-N7000 using XDA Premium HD app

timstanley1985 said:
Team Win Recovery Project 2.3 for Galaxy Note (CM10 only)
If you do not know what TWRP is, click here first...... now you know what TWRP is (and how very cool it is!!!) we can continue.
Foreword:
I have looked at those with devices with TWRP with envy for the entire time i have owned a Galaxy Note and have been waiting patiently for an experienced Dev to compile a version for the N7000. After a year of ownership this has not happened so i have decided to go ahead and do it myself!!
Why have you called this a proof on concept?
For a few reasons:
1. I am not an experienced Dev... i have built CM6, 7 and 10 from source and done all the usual tweaks to my android devices but that is where my experience ends. This in itself is no big deal in its self but leads me to point 2...
2. This recovery may have MMC_CAP_ERASE / Brick Bug! I do not know how to check if it is present or not! Until an experienced Dev confirms MMC_CAP_ERASE has been fully suppressed you should assume this recovery is dangerous. As soon as an experienced Dev confirms the recovery is safe i will update this post. If it is confirmed it is not safe i will remove all links
3. I unfortunately to do not have time to maintain this recovery. As Samsung recoveries are included in the boot.img (kernel) it will mean the recovery will need recompiling every time a change is merged to the kernel in CM10. As development is still very active on the N7000 kernel i cannot make the commitment to recompile this that often
4. I am not a kernel Dev therefore i can only compile stock kernel with TWRP recovery. We all love (me included) a custom kernel with all the normal tweaks, OC etc. etc. I will never be able to achieve this so want to use this as the seed for somebody else to take and use to build there own custom kernel with TWRP recovery
5. It needs more extensive testing.... I have been playing with it for an hour this morning and everything seems to work fine but needs more testing.
I have included how to compile TWRP in post two... did i hear someone say enough talking, i want to try this out!!!
How to install
I have attached the boot.img at the bottom of this post.
1. Download
2. Copy to SDCARD
3. Flash with Mobile Odin
4. Enjoy!!
Please remember: This recovery may contain MMC_CAP_ERASE / Brick Bug! I do not known how to check! It is built from CM10 sources and there are TWRP ports for other devices so should be safe but i cannopt be positive! Use at your own risk!
Experienced Dev's: Any feedback on whether this recovery is safe would be VERY gratefully received!
As soon as any confirmation of this recovery being unsafe i will remove link immediately!
Click to expand...
Click to collapse
Based on item #4 (this is using a stock kernel repacked with a new recovery) - it will not be safe for flashing things.
For wipes and backups, it depends on exactly how you built it. Run strings on the binary...
Code:
strings recovery |grep MMC
If you see
Code:
warning: %s: Wipe via secure discard suppressed due to bug in EMMC firmware
The recovery binary is safe to do wipes/backups with, but as said above, if you used a stock kernel, it will be dangerous to flash ZIPs.
Also, of course, as this is a galaxys2-family device, the moment you flash anything containing a new kernel, TWRP will be gone.

Sorry, I should have been clearer. When I say stock kernel I mean stock CM10 kernel. This recovery is built by deleting the /bootable/recovery/ folder and replacing it with TWRP recovery. The rest of the build is standard CM10.
Sent from my GT-N7000 using XDA Premium HD app

Some usage feedback: I found it quite hard navigating through a folder filled with many sub-folders and files to select what I want to flash...quite jerky UI and a lot different from the experience I get on my TWRP-recoveried tablet.
But great initial release dev - really, well done!

And is this Heimdall flashable or do you strictly recommend Odin only? I have never used Odin since it is blackbox and everyone I knew has been recommending Heimdall. I know the former is designed to best-case mimic the latter, but just want to cover all my bases.

Heimdall will work
Sent from my GT-N7000 using XDA Premium HD app

timstanley1985 said:
Heimdall will work
Sent from my GT-N7000 using XDA Premium HD app
Click to expand...
Click to collapse
Alright will give it a go. Thanks for the quick reply.

alharaka said:
Alright will give it a go. Thanks for the quick reply.
Click to expand...
Click to collapse
Yeah, so maybe I did not understand entirely but when I flashed I got a success with Heimdall 1.3.1 CLI on OS X (10.6.8).
Code:
my-bacbook-pro:~ root# heimdall flash --recovery /Users/myusername/Downloads/boot.img --verbose
Heimdall v1.3.1, Copyright (c) 2010-2011, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Manufacturer: "SAMSUNG"
Product: "Gadget Serial"
length: 18
device class: 2
S/N: 0
VID:PID: 04E8:685D
bcdDevice: 021B
iMan:iProd:iSer: 1:2:0
nb confs: 1
interface[0].altsetting[0]: num endpoints = 1
Class.SubClass.Protocol: 02.02.01
endpoint[0].address: 83
max packet size: 0010
polling interval: 09
interface[1].altsetting[0]: num endpoints = 2
Class.SubClass.Protocol: 0A.00.00
endpoint[0].address: 81
max packet size: 0200
polling interval: 00
endpoint[1].address: 02
max packet size: 0200
polling interval: 00
Claiming interface...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...
Beginning session...
Session begun with device of type: 131072
Downloading device's PIT file...
PIT file download sucessful
Uploading RECOVERY
0%File Part #0... Response: 0 0 0 0 0 0 0 0
2%
File Part #1... Response: 0 0 0 0 1 0 0 0
5%
File Part #2... Response: 0 0 0 0 2 0 0 0
7%
File Part #3... Response: 0 0 0 0 3 0 0 0
10%
File Part #4... Response: 0 0 0 0 4 0 0 0
12%
File Part #5... Response: 0 0 0 0 5 0 0 0
15%
File Part #6... Response: 0 0 0 0 6 0 0 0
18%
File Part #7... Response: 0 0 0 0 7 0 0 0
20%
File Part #8... Response: 0 0 0 0 8 0 0 0
23%
File Part #9... Response: 0 0 0 0 9 0 0 0
25%
File Part #10... Response: 0 0 0 0 A 0 0 0
28%
File Part #11... Response: 0 0 0 0 B 0 0 0
31%
File Part #12... Response: 0 0 0 0 C 0 0 0
33%
File Part #13... Response: 0 0 0 0 D 0 0 0
36%
File Part #14... Response: 0 0 0 0 E 0 0 0
38%
File Part #15... Response: 0 0 0 0 F 0 0 0
41%
File Part #16... Response: 0 0 0 0 10 0 0 0
44%
File Part #17... Response: 0 0 0 0 11 0 0 0
46%
File Part #18... Response: 0 0 0 0 12 0 0 0
49%
File Part #19... Response: 0 0 0 0 13 0 0 0
51%
File Part #20... Response: 0 0 0 0 14 0 0 0
54%
File Part #21... Response: 0 0 0 0 15 0 0 0
57%
File Part #22... Response: 0 0 0 0 16 0 0 0
59%
File Part #23... Response: 0 0 0 0 17 0 0 0
62%
File Part #24... Response: 0 0 0 0 18 0 0 0
64%
File Part #25... Response: 0 0 0 0 19 0 0 0
67%
File Part #26... Response: 0 0 0 0 1A 0 0 0
70%
File Part #27... Response: 0 0 0 0 1B 0 0 0
72%
File Part #28... Response: 0 0 0 0 1C 0 0 0
75%
File Part #29... Response: 0 0 0 0 1D 0 0 0
77%
File Part #30... Response: 0 0 0 0 1E 0 0 0
80%
File Part #31... Response: 0 0 0 0 1F 0 0 0
83%
File Part #32... Response: 0 0 0 0 20 0 0 0
85%
File Part #33... Response: 0 0 0 0 21 0 0 0
88%
File Part #34... Response: 0 0 0 0 22 0 0 0
90%
File Part #35... Response: 0 0 0 0 23 0 0 0
93%
File Part #36... Response: 0 0 0 0 24 0 0 0
96%
File Part #37... Response: 0 0 0 0 25 0 0 0
98%
File Part #38... Response: 0 0 0 0 26 0 0 0
100%
RECOVERY upload successful
Ending session...
Rebooting device...
But I rebooted and was back in ClockwordModRecovery 6.1.2. Did I misunderstand the directions? Sorry, my first time using Heimdall to write to my device; last few times I just detect'n'dump-ed to avoid destroying my phone because it was unnecessary.

If I was you just download mobile Odin lite from xda and flash with that. It's very easy that way
Sent from my GT-N7000 using XDA Premium HD app

timstanley1985 said:
If I was you just download mobile Odin lite from xda and flash with that. It's very easy that way
Sent from my GT-N7000 using XDA Premium HD app
Click to expand...
Click to collapse
I'll give that a try. Who knows what the deal is then.

alharaka said:
I'll give that a try. Who knows what the deal is then.
Click to expand...
Click to collapse
Ok, so I configured Mobile ODIN Lite (thanks for the pointer, by the way, amazing app I thought I had to pay for when I saw it a few weeks ago; had no idea I could test a lite version on XDA, sweet). So, installed it and got the N7000 add-on. What partition do I work with: Hidden?

Just click open file, select the boot.img and then scroll down and click flash image.
You click yes to confirm and then it will flash and reboot
Sent from my GT-N7000 using XDA Premium HD app

timstanley1985 said:
Just click open file, select the boot.img and then scroll down and click flash image.
You click yes to confirm and then it will flash and reboot
Sent from my GT-N7000 using XDA Premium HD app
Click to expand...
Click to collapse
Sorry for all the silly questions, and thanks again. I just wanna be sure since the recovery, well, makes mistakes less serious and I rely on it heavily. Once that is broken fixing my phone will get much more technical than I have time for.

[Q] [modem.bin]upgrade to leak rom by heimdall

I am trying to upgrade from GC100ZSALJ6 rom but failed when flashing the modem.bin. I have tried odin and heimdallv1.3.1.
The output of the heimdall is,
Heimdall v1.3.1, Copyright (c) 2010-2011, Benjamin Dobell, Glass Echidna
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
Initialising connection...
Detecting device...
Manufacturer: "SAMSUNG"
Product: "Gadget Serial"
length: 18
device class: 2
S/N: 0
VIDID: 04E8:685D
bcdDevice: 021B
iMan:iProd:iSer: 1:2:0
nb confs: 1
interface[0].altsetting[0]: num endpoints = 1
Class.SubClass.Protocol: 02.02.01
endpoint[0].address: 83
max packet size: 0010
polling interval: 09
interface[1].altsetting[0]: num endpoints = 2
Class.SubClass.Protocol: 0A.00.00
endpoint[0].address: 81
max packet size: 0200
polling interval: 00
endpoint[1].address: 02
max packet size: 0200
polling interval: 00
Claiming interface...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...
Beginning session...
Session begun with device of type: 131072
Downloading device's PIT file...
PIT file download sucessful
Uploading RADIO
0%File Part #0... Response: 0 0 0 0 0 0 0 0
1%
File Part #1... Response: 0 0 0 0 1 0 0 0
2%
File Part #2... Response: 0 0 0 0 2 0 0 0
3%
File Part #3... Response: 0 0 0 0 3 0 0 0
4%
File Part #4... Response: 0 0 0 0 4 0 0 0
5%
File Part #5... Response: 0 0 0 0 5 0 0 0
6%
File Part #6... Response: 0 0 0 0 6 0 0 0
7%
File Part #7... Response: 0 0 0 0 7 0 0 0
8%
File Part #8... Response: 0 0 0 0 8 0 0 0
9%
File Part #9... Response: 0 0 0 0 9 0 0 0
10%
File Part #10... Response: 0 0 0 0 A 0 0 0
11%
File Part #11... Response: 0 0 0 0 B 0 0 0
12%
File Part #12... Response: 0 0 0 0 C 0 0 0
13%
File Part #13... Response: 0 0 0 0 D 0 0 0
14%
File Part #14... Response: 0 0 0 0 E 0 0 0
15%
File Part #15... Response: 0 0 0 0 F 0 0 0
16%
File Part #16... Response: 0 0 0 0 10 0 0 0
17%
File Part #17... Response: 0 0 0 0 11 0 0 0
18%
File Part #18... Response: 0 0 0 0 12 0 0 0
19%
File Part #19... Response: 0 0 0 0 13 0 0 0
20%
File Part #20... Response: 0 0 0 0 14 0 0 0
21%
File Part #21... Response: 0 0 0 0 15 0 0 0
22%
File Part #22... Response: 0 0 0 0 16 0 0 0
23%
File Part #23... Response: 0 0 0 0 17 0 0 0
24%
File Part #24... Response: 0 0 0 0 18 0 0 0
26%
File Part #25... Response: 0 0 0 0 19 0 0 0
27%
File Part #26... Response: 0 0 0 0 1A 0 0 0
28%
File Part #27... Response: 0 0 0 0 1B 0 0 0
29%
File Part #28... Response: 0 0 0 0 1C 0 0 0
30%
File Part #29... Response: 0 0 0 0 1D 0 0 0
31%
File Part #30... Response: 0 0 0 0 1E 0 0 0
32%
File Part #31... Response: 0 0 0 0 1F 0 0 0
33%
File Part #32... Response: 0 0 0 0 20 0 0 0
34%
File Part #33... Response: 0 0 0 0 21 0 0 0
35%
File Part #34... Response: 0 0 0 0 22 0 0 0
36%
File Part #35... Response: 0 0 0 0 23 0 0 0
37%
File Part #36... Response: 0 0 0 0 24 0 0 0
38%
File Part #37... Response: 0 0 0 0 25 0 0 0
39%
File Part #38... Response: 0 0 0 0 26 0 0 0
40%
File Part #39... Response: 0 0 0 0 27 0 0 0
41%
File Part #40... Response: 0 0 0 0 28 0 0 0
42%
File Part #41... Response: 0 0 0 0 29 0 0 0
43%
File Part #42... Response: 0 0 0 0 2A 0 0 0
44%
File Part #43... Response: 0 0 0 0 2B 0 0 0
45%
File Part #44... Response: 0 0 0 0 2C 0 0 0
46%
File Part #45... Response: 0 0 0 0 2D 0 0 0
47%
File Part #46... Response: 0 0 0 0 2E 0 0 0
48%
File Part #47... Response: 0 0 0 0 2F 0 0 0
49%
File Part #48... Response: 0 0 0 0 30 0 0 0
51%
File Part #49... Response: 0 0 0 0 31 0 0 0
52%
File Part #50... Response: 0 0 0 0 32 0 0 0
53%
File Part #51... Response: 0 0 0 0 33 0 0 0
54%
File Part #52... Response: 0 0 0 0 34 0 0 0
55%
File Part #53... Response: 0 0 0 0 35 0 0 0
56%
File Part #54... Response: 0 0 0 0 36 0 0 0
57%
File Part #55... Response: 0 0 0 0 37 0 0 0
58%
File Part #56... Response: 0 0 0 0 38 0 0 0
59%
File Part #57... Response: 0 0 0 0 39 0 0 0
60%
File Part #58... Response: 0 0 0 0 3A 0 0 0
61%
File Part #59... Response: 0 0 0 0 3B 0 0 0
62%
File Part #60... Response: 0 0 0 0 3C 0 0 0
63%
File Part #61... Response: 0 0 0 0 3D 0 0 0
64%
File Part #62... Response: 0 0 0 0 3E 0 0 0
65%
File Part #63... Response: 0 0 0 0 3F 0 0 0
66%
File Part #64... Response: 0 0 0 0 40 0 0 0
67%
File Part #65... Response: 0 0 0 0 41 0 0 0
68%
File Part #66... Response: 0 0 0 0 42 0 0 0
69%
File Part #67... Response: 0 0 0 0 43 0 0 0
70%
File Part #68... Response: 0 0 0 0 44 0 0 0
71%
File Part #69... Response: 0 0 0 0 45 0 0 0
72%
File Part #70... Response: 0 0 0 0 46 0 0 0
73%
File Part #71... Response: 0 0 0 0 47 0 0 0
74%
File Part #72... Response: 0 0 0 0 48 0 0 0
76%
File Part #73... Response: 0 0 0 0 49 0 0 0
77%
File Part #74... Response: 0 0 0 0 4A 0 0 0
78%
File Part #75... Response: 0 0 0 0 4B 0 0 0
79%
File Part #76... Response: 0 0 0 0 4C 0 0 0
80%
File Part #77... Response: 0 0 0 0 4D 0 0 0
81%
File Part #78... Response: 0 0 0 0 4E 0 0 0
82%
File Part #79... Response: 0 0 0 0 4F 0 0 0
83%
File Part #80... Response: 0 0 0 0 50 0 0 0
84%
File Part #81... Response: 0 0 0 0 51 0 0 0
85%
File Part #82... Response: 0 0 0 0 52 0 0 0
86%
File Part #83... Response: 0 0 0 0 53 0 0 0
87%
File Part #84... Response: 0 0 0 0 54 0 0 0
88%
File Part #85... Response: 0 0 0 0 55 0 0 0
89%
File Part #86... Response: 0 0 0 0 56 0 0 0
90%
File Part #87... Response: 0 0 0 0 57 0 0 0
91%
File Part #88... Response: 0 0 0 0 58 0 0 0
92%
File Part #89... Response: 0 0 0 0 59 0 0 0
93%
File Part #90... Response: 0 0 0 0 5A 0 0 0
94%
File Part #91... Response: 0 0 0 0 5B 0 0 0
95%
File Part #92... Response: 0 0 0 0 5C 0 0 0
96%
File Part #93... Response: 0 0 0 0 5D 0 0 0
97%
File Part #94... Response: 0 0 0 0 5E 0 0 0
98%
File Part #95... Response: 0 0 0 0 5F 0 0 0
99%
File Part #96... Response: 0 0 0 0 60 0 0 0
100%
RADIO upload failed!
Ending session...
ERROR: Failed to confirm end of file transfer sequence!
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet.
ERROR: Failed to send end session packet!
Are there anyone has done this type of work successfully?
Is it related to the flash tools hasn't support this device yet?

not sure if it makes a diff.. but have you rooted your device ?

pileiba said:
not sure if it makes a diff.. but have you rooted your device ?
Click to expand...
Click to collapse
Thanks for your reply.
Yes I have rooted the device. But as this procedure is in the download mode, is it related to rooted/non-rooted?
I just want to try another rom.
I have tried another way without modem.bin included and seems all the file could be uploaded to the device now.
But I still not sure about why the modem.bin couldn't been flashed

some other solutions I came across where here.. https://github.com/Benjamin-Dobell/Heimdall/issues/43 i.e. to try different versions of heimdell, try a 32bit operating system as opposed to 64 bit, and reinstall the samsung drivers. There is apparently a Heimdell 1.4 . http://www.glassechidna.com.au/2012/devblogs/heimdall-1-4-release-candidate-1/ . Lastly you could try a different usb cable and a different usb port. I think powered hubs sometimes work better.

Enabling face or iris unlock triggers log spam and high CPU usage

Hi,
I am running stock N960FXXS3CSG1 AP firmware on a freshly factory reset Exynos-based Note 9 device and I observed that when either face or iris is enabled as screen lock type, SystemUI is continuously generating warning logs as long as the screen is on. This can be seen by connecting the phone to a PC and running 'adb logcat' after enabling USB debugging. The warning logs are generated even if the phone is unlocked using the fingerprint sensor, without even showing the lock screen. Restarting the phone does not help.
The lines that are continuously written to the log by the SystemUI process are:
Code:
07-20 11:24:58.157 5439 5439 W View : requestLayout() improperly called by com.android.keyguard.biometric.KeyguardBiometricSmallIconView{c777788 V.E...... ......ID 0,84-1440,217 #7f0a0273 app:id/keyguard_iris_text_preview} during layout: running second layout pass
07-20 11:24:58.157 5439 5439 I [email protected][StatusBar]: requestLayout is already in process
07-20 11:24:58.157 5439 5439 I [email protected][StatusBar]: requestLayoutDuringLayout is already in process
07-20 11:24:58.157 5439 5439 I [email protected][StatusBar]: requestLayoutDuringLayout is already in process
07-20 11:24:58.159 5439 5439 W View : requestLayout() improperly called by com.android.systemui.statusbar.phone.NotificationPanelView{5a9da25 V.E...... ........ 0,0-1440,2960 #7f0a0387 app:id/notification_panel} during second layout pass: posting in next frame
07-20 11:24:58.159 5439 5439 W View : requestLayout() improperly called by com.android.keyguard.biometric.KeyguardBiometricSmallIconView{c777788 V.E...... ........ 0,84-1440,217 #7f0a0273 app:id/keyguard_iris_text_preview} during second layout pass: posting in next frame
This behavior causes high CPU usage and battery drain when either iris or face unlock is enabled.
Here is a snapshot of top running after the phone was unlocked, with face unlock enabled:
Code:
800%cpu 80%user 7%nice 104%sys 608%idle 0%iow 0%irq 0%sirq 0%host
PID USER PR NI VIRT RES SHR S[%CPU] %MEM TIME+ ARGS
5439 u0_a8 20 0 4.9G 380M 300M S 74.3 6.7 8:16.99 com.android.systemui
4388 system 12 -8 3.0G 45M 37M S 31.6 0.7 5:07.57 surfaceflinger
4261 logd 30 10 21M 4.7M 2.7M S 18.3 0.0 4:04.49 logd
4366 system 20 0 166M 5.0M 4.3M S 16.0 0.0 2:03.32 [email protected]
2259 root RT 0 0 0 0 S 11.0 0.0 2:49.27 [decon0]
20277 root 20 0 0 0 0 S 7.0 0.0 0:06.64 [kworker/0:0]
20228 root 0 -20 0 0 0 S 6.6 0.0 0:02.47 [kworker/u17:1]
15695 root 0 -20 0 0 0 S 6.0 0.0 0:19.06 [kworker/u17:4]
4931 system 18 -2 5.4G 429M 318M S 5.6 7.6 32:10.51 system_server
21346 shell 20 0 12M 5.1M 3.9M R 3.6 0.0 0:00.35 top
This is how it looks when face and iris unlock are disabled (phone was restarted so different pids):
Code:
800%cpu 10%user 2%nice 9%sys 778%idle 0%iow 0%irq 0%sirq 0%host
PID USER PR NI VIRT RES SHR S[%CPU] %MEM TIME+ ARGS
4927 system 18 -2 5.2G 502M 400M S 11.0 8.9 5:07.68 system_server
17742 shell 20 0 12M 5.0M 3.8M R 3.3 0.0 0:00.33 top
17650 root 20 0 0 0 0 S 1.6 0.0 0:01.89 [kworker/0:2]
4569 wifi 20 0 19M 5.8M 5.5M S 1.6 0.1 0:08.97 wificond
6128 u0_a15 20 0 3.7G 138M 120M S 1.0 2.4 0:12.86 android.process.acore
6414 system 20 0 3.7G 132M 118M S 0.6 2.3 0:26.58 com.sec.android.sdhms
4532 system 20 0 11M 3.3M 3.2M S 0.6 0.0 0:10.69 argosd
7 root 20 0 0 0 0 S 0.6 0.0 0:09.04 [rcu_preempt]
5406 u0_a8 20 0 4.5G 358M 286M S 0.3 6.3 0:42.20 com.android.systemui
Here is the logcat output for pid/tid 5439 (com.android.systemui), starting from when the power button was pressed, with face unlock enabled:
https://pastebin.com/zX77zHW8
The messages at the end keep repeating until the screen is turned off.
Here is the logcat output with face unlock disabled:
https://pastebin.com/1An2X6TJ
Can anyone else run 'adb shell top' with face or iris unlock enabled and confirm whether this is a firmware issue or it's just something on my end?
Thanks!

Did you manage to figure it out? I'm getting the same exact issue.

artoria5 said:
Did you manage to figure it out? I'm getting the same exact issue.
Click to expand...
Click to collapse
Unfortunately, no. I was hoping to get more input on this. Samsung Community hasn't been much help either.