Database Users

remount failed??

Problem fixed !!! Thansk!
Any ONE can help?
My kindle fire already rooted, every time i want to install the input method by adb remount is fail.
remount failed: operation not permitted!
how can i fix it??

would thing you get the $ prompt if you open the adb shell
enter "su" - the prompt should change to #
then the remount command should succeed

enter "su" - the prompt should change to # in shell mode
then type : # adb remount ?
could you get me a detail command set ?. because kindle fire is my first's android device , BIG THANKS!

this should be the way it works:
adb shell
$ su
su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
#
the bold commands are the ones to enter ...

My file is saved in c:\apps\hk.cedime.inputmethod.apk
and also have a copy in c:\adb\hk.cedime.inputmethod.apk
Show many error ??? Any expert can help?
adb shell
$ su
su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
# install c:\apps\hk.cedime.inputmethod.apk /system/app/
install c:\apps\hk.cedime.inputmethod.apk /system/app/
install: can't stat ' c:appshk.cedime.inputmethod.apk' : No such file or directory
# install hk.cedime.inputmethod.apk /system/app/
install hk.cedime.inputmethod.apk /system/app/
install: can't stat ' hk.cedime.inputmethod.apk' : No such file or directory
#cp hk.cedime.inputmethod.apk /system/app/
cp hk.cedime.inputmethod.apk /system/app/
cp: can't stat ' hk.cedime.inputmethod.apk' : No such file or directory
#cp c:\apps\hk.cedime.inputmethod.apk /system/app/
cp c:\apps\hk.cedime.inputmethod.apk /system/app/
cp: can't stat ' c:appshk.cedime.inputmethod.apk' : No such file or directory

install: can't stat ' c:appshk.cedime.inputmethod.apk' : No such file or directory
Click to expand...
Click to collapse
it don't find the .apk file
i use to put the files to install in the directory where adb.exe resides
and do the command without a path ie: install hk.cedime.inputmethod.apk /system/app/
furthermore i'm not shure if the command works inside the adb shell
would also try (from command prompt):
adb install c:\apps\hk.cedime.inputmethod.apk /system/app/
or if .apk in current directory (where adb resides):
adb install hk.cedime.inputmethod.apk /system/app/

Adb command is my first choice
But the system show the error : can't find '/system/app/' to install

then it seems not to be mounted ...
try to check with:
"adb shell"
"su"
"mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system"
"cd \system"
"ls -l" -> any directory listing here ?
"cd app"
"ls -l" -> any apk's listed ?

OH! my God!
c:\ADB>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
6C18000600000001 device
c:\ADB>adb shell
$ su
su
# mount -o remount, rw -t yaffs2/dev/block/mtdblock3/system
mount -o remount, rw -t yaffs2/dev/block/mtdblock3/system
Usage: mount [-r] [-w] [-o options] [-t type] device directory
#

no problem - if it's not mounted it's hard to remount
would try:
"mount /system" in adb shell
or
"adb shell mount -o remount rw /system" from the command prompt

Sorry, many problem can't fix...............
c:\ADB>adb shell mount -o remount rw/system
Usage: mount [-r] [-w] [-o options] [-t type] device directory
c:\ADB>
c:\ADB>adb shell mount -o remount rw/system
Usage: mount [-r] [-w] [-o options] [-t type] device directory
c:\ADB>adb shell
$ su
su
# mount -o remount, rw -t yaffs2 /dev/block/mtdblock3 /system
mount -o remount, rw -t yaffs2 /dev/block/mtdblock3 /system
Usage: mount [-r] [-w] [-o options] [-t type] device directory
# ls -l
ls -l
dr-x------ root root 2012-03-19 05:51 config
drwxrwx--- system system 2012-03-20 07:00 dropbox
drwxrwx--- system cache 2012-03-19 05:51 cache
lrwxrwxrwx root root 2012-03-19 05:51 sdcard -> /mnt/sdcard
drwxr-xr-x root root 2012-03-19 05:51 acct
drwxrwxr-x root system 2012-03-19 05:51 mnt
lrwxrwxrwx root root 2012-03-19 05:51 vendor -> /system/vendor
lrwxrwxrwx root root 2012-03-19 05:51 d -> /sys/kernel/debug
lrwxrwxrwx root root 2012-03-19 05:51 etc -> /system/etc
-rw-r--r-- root root 4203 1969-12-31 16:00 ueventd.rc
-rw-r--r-- root root 840 1969-12-31 16:00 ueventd.omap4430.rc
-rw-r--r-- root root 0 1969-12-31 16:00 ueventd.goldfish.rc
drwxr-xr-x root root 2012-01-19 04:27 system
drwxr-xr-x root root 2012-03-19 05:51 sys
drwxr-x--- root root 1969-12-31 16:00 sbin
dr-xr-xr-x root root 1969-12-31 16:00 proc
-rwxr-x--- root root 14869 1969-12-31 16:00 init.rc
-rwxr-x--- root root 11357 1969-12-31 16:00 init.omap4430.rc
-rwxr-x--- root root 1677 1969-12-31 16:00 init.goldfish.rc
-rwxr-x--- root root 94200 1969-12-31 16:00 init
-rw-r--r-- root root 118 1969-12-31 16:00 default.prop
drwxrwx--x system system 2012-03-18 06:53 data
drwx------ root root 2012-01-09 22:20 root
drwxr-xr-x root root 2012-03-19 06:01 dev
# cd app
cd app
cd: can't cd to app
#

from your post #5:
adb shell
$ su
su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
Click to expand...
Click to collapse
this has seemed to work - or was there allways a error message following up which you did'nt copy and paste ?
usually "mount /system" is sufficient - "mount -w /system" should work too
# cd app
cd app
cd: can't cd to app
Click to expand...
Click to collapse
if you look to the directory listing you are on the root - there is no directory or mountpoint "app" - it is in the system directory - the command should be:
"cd \system"
"ls -l" -> any directory listing here ?
and then if you are in "system"
"cd app"
"ls -l" -> any apk's listed ?
as in post #8

Expert ! Next step what can i do?
C:\ADB>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
6C18000600000001 device
C:\ADB>adb shell mount -o remount rw /system
mount: Operation not permitted
C:\ADB>adb shell
$ su
su
# mount -o remount, rw -t yaffs2 /dev/block/mtdblock3 /system
mount -o remount, rw -t yaffs2 /dev/block/mtdblock3 /system
Usage: mount [-r] [-w] [-o options] [-t type] device directory
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
# cd \system
cd \system
# ls -l
ls -l
drwxr-xr-x root root 1969-12-31 16:00 lost+found
drwxr-xr-x root root 2012-03-19 05:49 app
drwxr-xr-x root shell 2012-03-17 18:19 bin
-rw-r--r-- root root 2151 2008-08-01 05:00 build.prop
drwxr-xr-x root root 2012-01-19 04:27 etc
drwxr-xr-x root root 2012-01-19 04:27 fonts
drwxr-xr-x root root 2012-01-19 04:27 framework
drwxr-xr-x root root 2012-01-19 04:27 lib
drwxr-xr-x root root 2012-01-19 04:27 media
drwxr-xr-x root root 2012-01-19 04:27 tts
drwxr-xr-x root root 2012-01-19 04:27 usr
drwxr-xr-x root shell 2012-01-19 04:27 vendor
drwxr-xr-x root shell 2012-03-17 20:51 xbin
# cd app
cd app
# ls -l
ls -l
-rw-r--r-- root root 2669573 2008-08-01 05:00 ATVAndroidClient.apk
-rw-r--r-- root root 233689 2008-08-01 05:00 AccountAndSyncSettings.ap
k
-rw-r--r-- root root 3581879 2008-08-01 05:00 AmazonVenezia.apk
-rw-r--r-- root root 29574 2008-08-01 05:00 ApplicationsProvider.apk
-rw-r--r-- root root 3574986 2008-08-01 05:00 AudibleAndroidApplication
-venezia.apk
-rw-r--r-- root root 164188 2008-08-01 05:00 CSApp-unsigned.apk
-rw-r--r-- root root 152004 2008-08-01 05:00 CalendarProvider.apk
-rw-r--r-- root root 116225 2008-08-01 05:00 CertInstaller.apk
-rw-r--r-- root root 4019454 2008-08-01 05:00 Cloud9-release-unsigned.a
pk
-rw-r--r-- root root 57208 2008-08-01 05:00 Cloud9SystemBrowserProvid
er-unsigned.apk
-rw-r--r-- root root 2049942 2008-08-01 05:00 Contacts.apk
-rw-r--r-- root root 145545 2008-08-01 05:00 ContactsProvider.apk
-rw-r--r-- root root 20748 2008-08-01 05:00 DefaultContainerService.a
pk
-rw-r--r-- root root 196150 2008-08-01 05:00 DownloadProvider.apk
-rw-r--r-- root root 106749 2008-08-01 05:00 DownloadProviderUi.apk
-rw-r--r-- root root 32432 2008-08-01 05:00 DrmProvider.apk
-rw-r--r-- root root 2315338 2008-08-01 05:00 Email.apk
-rw-r--r-- root root 16892 2008-08-01 05:00 Facebook.apk
-rw-r--r-- root root 833544 2008-08-01 05:00 Gallery3D.apk
-rw-r--r-- root root 22792 2008-08-01 05:00 HTMLViewer.apk
-rw-r--r-- root root 1685594 2008-08-01 05:00 IMDb-2.3.apk
-rw-r--r-- root root 16424244 2008-08-01 05:00 KindleForOtter.apk
-rw-r--r-- root root 1082002 2008-08-01 05:00 LatinIME.apk
-rw-r--r-- root root 12174497 2008-08-01 05:00 Launcher.apk
-rw-r--r-- root root 1140587 2008-08-01 05:00 LiveWallpapers.apk
-rw-r--r-- root root 51276 2008-08-01 05:00 LiveWallpapersPicker.apk
-rw-r--r-- root root 224152 2008-08-01 05:00 MagicSmokeWallpapers.apk
-rw-r--r-- root root 20778 2008-08-01 05:00 MarketIntentProxy.apk
-rw-r--r-- root root 62533 2008-08-01 05:00 MediaProvider.apk
-rw-r--r-- root root 149119 2008-08-01 05:00 MyAccount-unsigned.apk
-rw-r--r-- root root 253116 2008-08-01 05:00 OOBE-unsigned.apk
-rw-r--r-- root root 26983 2008-08-01 05:00 OTASilentInstall.apk
-rw-r--r-- root root 110563 2008-08-01 05:00 OtterAppManager.apk
-rw-r--r-- root root 1907710 2008-08-01 05:00 OtterTutorial.apk
-rw-r--r-- root root 122758 2008-08-01 05:00 PackageInstaller.apk
-rw-r--r-- root root 22282 2008-08-01 05:00 PicoTts.apk
-rw-r--r-- root root 10496 2008-08-01 05:00 Provision.apk
-rw-r--r-- root root 2305323 2008-08-01 05:00 Pulse-amazon.apk
-rw-r--r-- root root 412698 2008-08-01 05:00 QuickSearchBox.apk
-rw-r--r-- root root 320688 2008-08-01 05:00 QuickSettings.apk
-rw-r--r-- root root 6302776 2008-08-01 05:00 Quickoffice_AMAZON_4.1.46
7_VC.apk
-rw-r--r-- root root 3751962 2008-08-01 05:00 Settings.apk
-rw-r--r-- root root 48682 2008-08-01 05:00 SettingsProvider.apk
-rw-r--r-- root root 604484 2008-08-01 05:00 SystemUI.apk
-rw-r--r-- root root 30187 2008-08-01 05:00 TtsService.apk
-rw-r--r-- root root 16928 2008-08-01 05:00 UserDictionaryProvider.ap
k
-rw-r--r-- root root 165579 2008-08-01 05:00 VisualizationWallpapers.a
pk
-rw-r--r-- root root 34247 2008-08-01 05:00 VpnServices.apk
-rw-r--r-- root root 1669753 2008-08-01 05:00 Windowshop.apk
-rw-r--r-- root root 6113490 2008-08-01 05:00 air_runtime.apk
-rw-r--r-- root root 2109670 2008-08-01 05:00 amazonmp3-unsigned.apk
-rw-r--r-- root root 2500819 2008-08-01 05:00 com.amazon.dcp.apk
-rw-r--r-- root root 45888 2008-08-01 05:00 oem_install_flash_player_
signed.apk
-rw-r--r-- root root 843503 2008-02-28 10:33 Superuser.apk
-rw-rw-rw- root root 89707 2011-12-07 02:26 GoogleFeedback.apk
-rw-rw-rw- root root 1401398 2011-12-07 02:13 GoogleServicesFramework.a
pk
-rw-rw-rw- root root 1529836 2011-12-07 02:15 Vending.apk
-rw-rw-rw- root root 4089926 2011-12-07 02:22 GO_Launcher_EX_2.65.apk
-rw-rw-rw- root root 2053065 2012-03-19 05:49 hk.cedime.inputmethod.apk
#

C:\ADB>adb shell mount -o remount rw /system
mount: Operation not permitted
Click to expand...
Click to collapse
as you run a unsecure kernel i think the command should be:
adb shell su -c "remount"
or
adb shell su -c "mount -o remount rw /system"
C:\ADB>adb shell
$ su
su
# mount -o remount, rw -t yaffs2 /dev/block/mtdblock3 /system
mount -o remount, rw -t yaffs2 /dev/block/mtdblock3 /system
Usage: mount [-r] [-w] [-o options] [-t type] device directory
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
Click to expand...
Click to collapse
the second attempt succeeded - so your question seems to be answered or not ?
Any ONE can help?
My kindle fire already rooted, every time i want to install the input method by adb remount is fail.
remount failed: operation not permitted!
how can i fix it??
Click to expand...
Click to collapse

Expert!
i follow this link
http://forum.xda-developers.com/showthread.php?t=1364543
to fixed my problem, Thanks for your support again!!

glad to help ...
please mark the subject of the topic (edit first post) with [Solved]

CIFS and stock ICS on Acer a500

CIFS is one of the must haves for me with my tablet. I use it to mount Windows drives and then access comics, manga and video content on my PC. I was able to piece together items to make it work. Here's what I did:
1) Upgraded to stock ICS
2) Rooted ICS via this post: http://forum.xda-developers.com/showthread.php?t=1546593
3) Download kernel modules (cifs.ko, md4.ko): http://forum.xda-developers.com/showpost.php?p=23713310&postcount=2828
4) Setup a script to install the modules and mount your drives. I use this:
#!/system/bin/sh
insmod /system/lib/modules/md4.ko
insmod /system/lib/modules/cifs.ko
mount -t cifs -o user=test,password=test1 //192.168.1.100/acer /mnt/sdcard/cifs/acer
Note: I haven't been able to get this version to work with spaces in the user, password or drive names, so I had to setup a new account and revised share names on my Windows PC. In the Honeycomb release, I could just encase the user name in double quotes (example: "first last"). But that doesn't seem to work in ICS for some reason.
Hope this helps someone!

thanks, do you think it's ok on flexreeper rom ?

z-control said:
thanks, do you think it's ok on flexreeper rom ?
Click to expand...
Click to collapse
The thread I took it from was this one: [ROM][ICS4.0.3] Taboonay 3.0.1
I'd think the modules should work on any general rom based on the Acer ICS 4.0.3 build. The key is that when you do insmod to load these modules, there's a check on the version of the kernel vs the version in the module. These are built as:
2.6.39.4+ SMP preempt mod_unload ARMv7

Yes, it's working simply with cifs manager !

Hi, do you think these file will work on a510?, that's because I put the files on:
/system/lib/modules/
but when I run this command:
mount -t cifs -o user=nas,password=nas //192.168.10.1/mnt /mnt/sdcard/cifs/mnt
on terminal my device reboot, my device is rooted, the modules are loaded successful and are displayed on cifsmanager, I have other tablet with the same configuration and not have any problem to mount that path, the kernel on my a510 is 2.6.39.4+ with ICS 4.0.3, the reboot happens when I run the command or whit cifsmanager, can you help me? thanks in advance.
PS: Sorry for my English I'm Latin.

sparkly81 said:
Hi, do you think these file will work on a510?, that's because I put the files on:
/system/lib/modules/
but when I run this command:
mount -t cifs -o user=nas,password=nas //192.168.10.1/mnt /mnt/sdcard/cifs/mnt
on terminal my device reboot, my device is rooted, the modules are loaded successful and are displayed on cifsmanager, I have other tablet with the same configuration and not have any problem to mount that path, the kernel on my a510 is 2.6.39.4+ with ICS 4.0.3, the reboot happens when I run the command or whit cifsmanager, can you help me? thanks in advance.
PS: Sorry for my English I'm Latin.
Click to expand...
Click to collapse
Now that you've issued the mount command, was the /mnt/sdcard/cifs/mnt directory setup on your acer? I believe I had to use cifsmanager to initially do the mount and do the directory setup on the sdcard so I could then later use the mount command.

Thanks for you help, yes the path /mnt/sdcard/cifs/mnt is my dir setup, I have changed the dir to /sdcard/cifs that's because on my root dir I there's a link to a sdcard, but is doesn't work, it's always reboot, I have tried the commands via adb shell and local terminal on the device, but is the same story, one question, the cifs.ko and md4.ko they have this permission 777 and the owner is root, is this correct?

sparkly81 said:
Thanks for you help, yes the path /mnt/sdcard/cifs/mnt is my dir setup, I have changed the dir to /sdcard/cifs that's because on my root dir I there's a link to a sdcard, but is doesn't work, it's always reboot, I have tried the commands via adb shell and local terminal on the device, but is the same story, one question, the cifs.ko and md4.ko they have this permission 777 and the owner is root, is this correct?
Click to expand...
Click to collapse
mine are set as owner system and permissions are: ---rwxr-x
So... you do the insmod and it works and then you do a lsmod and the modules are listed?
In the terminal, if you just enter "mount", does it return and list the mounted devices?

Thanks! I run the commands and that's the results:
Code:
[email protected]:/ # insmod /system/lib/modules/md4.ko
insmod /system/lib/modules/md4.ko
[email protected]:/ # insmod /system/lib/modules/cifs.ko
insmod /system/lib/modules/cifs.ko
[email protected]:/ # lsmod
lsmod
cifs 207351 0 - Live 0xbf057000
md4 3019 0 - Live 0xbf051000
ufsd 320396 0 - Live 0xbf000000 (P)
[email protected]:/ # mount
mount
rootfs on / type rootfs (ro,relatime)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
tmpfs on /mnt/usb_storage type tmpfs (rw,relatime,mode=755,gid=1000)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/platform/sdhci-tegra.3/by-name/APP on /system type ext4 (ro,relatime,
user_xattr,acl,barrier=1,data=ordered)
/dev/block/platform/sdhci-tegra.3/by-name/UDA on /data type ext4 (rw,nosuid,node
v,noatime,user_xattr,acl,barrier=1,nomblk_io_submit,data=ordered)
/dev/block/platform/sdhci-tegra.3/by-name/CAC on /cache type ext4 (rw,nosuid,nod
ev,noatime,user_xattr,acl,barrier=1,nomblk_io_submit,data=ordered)
/dev/block/platform/sdhci-tegra.3/by-name/FLX on /system/vendor type ext4 (ro,re
latime,user_xattr,acl,barrier=1,data=ordered)
/dev/fuse on /mnt/sdcard type fuse (rw,nosuid,nodev,relatime,user_id=1023,group_
id=1023,default_permissions,allow_other)
/dev/block/vold/179:33 on /mnt/external_sd type vfat (rw,dirsync,nosuid,nodev,no
exec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=
cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
I didn't run the command
mount -t cifs -o user=nas,password=nas //192.168.10.1/mnt /sdcard/cifs
because make the tablet reboot.
Code:
[email protected]:/system/lib/modules # ls -l
ls -l
-rw-r--r-- root root 140644 2008-08-01 06:00 baseband_usb_chr.ko
----rwxr-x system system 3719757 2012-05-07 18:06 cifs.ko
-rw-rw-r-- system system 1079751 2012-05-07 18:06 hfs.ko
-rw-rw-r-- system system 1257749 2012-05-07 18:06 hfsplus.ko
----rwxr-x system system 65991 2012-05-07 18:06 md4.ko
-rw-rw-r-- system system 2155925 2012-05-07 18:06 ntfs.ko
-rw-r--r-- root root 170169 2008-08-01 06:00 raw_ip_net.ko
-rw-r--r-- root root 32779 2008-08-01 06:00 scsi_wait_scan.ko
-rw-r--r-- root root 130574 2008-08-01 06:00 tcrypt.ko
-rw-r--r-- root root 404760 2008-08-01 06:00 ufsd.ko
[email protected]:/system/lib/modules #

Well... I'm out of ideas.
Usually, what happens is that the modules don't load because they don't match the kernel. But the "lsmod" results shows they did load.
And the mount output shows that your mount command is there and working... so I have no other suggestions. Sorry, maybe someone else has a thought?

Thanks!, saeba for your help, I learn many things from you

#!/system/bin/sh
insmod /system/lib/modules/md4.ko
insmod /system/lib/modules/cifs.ko
Click to expand...
Click to collapse
I put this script in etc/init.d folder (name the file as you want without extension)
and the kernel in modul folder
and then, i use mount manager wich can auto mount a shared folder from PC when tablette is booting, and when the connexion wifi is ok

Per request, here are the cifs.ko and md4.ko files.

I am not familiar with CIFS
But I know for a fact that ES file explorer can read standard network shares and open any files across the network. Probably not much help

entropy.of.avarice said:
But I know for a fact that ES file explorer can read standard network shares and open any files across the network. Probably not much help
Click to expand...
Click to collapse
CIFS allows you to mount the network drive and use it as if it were a local drive. There are lots of apps that will only work with network files in this manner. I use it to play movies, read manga and comics, etc. that are located on my PC.

saeba said:
CIFS allows you to mount the network drive and use it as if it were a local drive. There are lots of apps that will only work with network files in this manner. I use it to play movies, read manga and comics, etc. that are located on my PC.
Click to expand...
Click to collapse
I knew I was missing something. I play a lot of movies, look at pictures, stuff like that from network shares - but the apps that I use seem to have no issue with that (MX Player, stock gallery photo view app, etc). Again, way out of practice

[Q] Shell/root expert question. Charging via USB - have a solution but not working?

Hi,
Let me start by saying that I just spend the last 7 hours searching everywhere on XDA and the net for this solution (!), but I really cannot find it. I've been a longtime reader of XDA and thought it was about time I posted something
I am looking to modify one single file (!) to get the USB charging to work whilst my Tab 7.7 (6800 3G) is on. Apparently this fix works (have seen youtube proof on Tab 10.1), but I don't have a clue how to get around the permissions! I want to connect to a USB power source whilst out and about.
This is the solution I've found (quoted verbatim from galaxytabhacks.com):
1. Get a root explorer.. I use es file explorer.
2. Change to mount file sys as rw in settings as well as enable root explorer in es settings
3. Navigate to the same sys/class/power_supply/battery
4. Find charging_source
5. Open file as text and edit to 0.5
6. Save file
You can also add the file force_USB_charging and edit as text to value 0.5. BE SURE YOUR ROOT FILE SYSTEM IS REWRITEABLE OR CHANGES WILL NOT STICK. YOU MUST BE ROOTED BUT IT DOES NOT MATER WHAT ROM OR KERNEL YOU ARE USING.
Click to expand...
Click to collapse
Now, I have a rooted device and everything seems to work for me apart from actually editing/saving/creating a file in /sys/class/power_supply/battery. The file system is rewritable (rw) but whatever I do I can't edit the above file or create a new one in this folder. Installed busybox, installed all sorts of rw mount and root tools. Nothing works. Drives me nuts because I'm convinced that once I can do this trick it'll work!
Code:
$ export PATH=/data/local/bin:$PATH
$ su
# cd /sys/class/power_supply
# ls -l
lrwxrwxrwx root root 2012-05-13 15:37 ac -> ../../devices/platform/sec-battery/power_supply/ac
lrwxrwxrwx root root 2012-05-13 15:35 battery -> ../../devices/platform/sec-battery/power_supply/battery
lrwxrwxrwx root root 2012-05-13 15:37 max8997-charger -> ../../devices/platform/s3c2440-i2c.5/i2c-5/5-0066/max8997-charger/power_supply/max8997-charger
lrwxrwxrwx root root 2012-05-13 15:35 usb -> ../../devices/platform/sec-battery/power_supply/usb
# cd battery
# ls -l
-rw-rw-r-- root root 4096 2012-05-13 15:37 batt_current_now
-rw-rw-r-- root root 4096 2012-05-13 15:37 batt_full_check
-rw-rw-r-- root root 4096 2012-05-13 15:37 batt_lp_charging
-rw-rw-r-- root root 4096 2012-05-13 15:35 batt_temp
-rw-rw-r-- root root 4096 2012-05-13 15:37 batt_temp_check
-rw-rw-r-- root root 4096 2012-05-13 15:37 batt_type
-rw-rw-r-- root root 4096 2012-05-13 15:37 batt_vol
-r--r--r-- root root 4096 2012-05-13 15:35 capacity
-rw-rw-rw- root root 4096 2012-05-13 13:35 charging_source
lrwxrwxrwx root root 2012-05-13 15:37 device -> ../../../sec-battery
-rw-rw-r-- root root 4096 2012-05-13 15:37 fg_reg
-rw-rw-r-- root root 4096 2012-05-13 15:37 fg_soc
-r--r--r-- root root 4096 2012-05-13 15:35 health
-rw-rw-r-- root root 4096 2012-05-13 15:37 jig_on
drwxr-xr-x root root 2012-05-13 12:38 power
-r--r--r-- root root 4096 2012-05-13 15:35 present
-rw-rw-r-- root root 4096 2012-05-13 15:37 reset_cap
-rw-rw-r-- radio system 4096 2012-05-13 12:37 reset_soc
-rw-rw-r-- radio system 4096 2012-05-13 12:37 siop_activated
-r--r--r-- root root 4096 2012-05-13 15:35 status
lrwxrwxrwx root root 2012-05-13 15:37 subsystem -> ../../../../../class/power_supply
-r--r--r-- root root 4096 2012-05-13 15:37 technology
-r--r--r-- root root 4096 2012-05-13 15:37 type
-rw-r--r-- root root 4096 2012-05-13 15:37 uevent
-rw-rw-r-- root root 4096 2012-05-13 15:35 voltage_now
# echo 1 > charging_source
# cat charging_source
0
# echo 1 > force_usb_charging
cannot create force_usb_charging: directory nonexistent
# id
uid=0(root) gid=0(root)
# pd
pd: not found
# pwd
/sys/devices/platform/sec-battery/power_supply/battery
# mount
rootfs / rootfs rw,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,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/mmcblk0p9 /system ext4 rw,relatime,errors=panic,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p10 /data ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p7 /cache ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p1 /efs ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p4 /mnt/.lfs j4fs rw,relatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/fuse /mnt/sdcard fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
tmpfs /mnt/sdcard/extStorages tmpfs ro,relatime,mode=755,gid=1000 0 0
/dev/block/vold/179:17 /mnt/sdcard/extStorages/SdCard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1023,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
#
Model: GT-P6800
Android: 3.2
Baseband: DXLB1
Kernel: 2.6.36 stock (via ODIN), with root
Build: DXLB3
Any help would be most appreciated. If this works, I'm sure others will immediately benefit too! Thanks.
cmmc

Are you sure that it doesn't charge albeit slowly? I've seen my battery percent rise even with the x over the battery icon
Sent from my PC36100 using XDA

You're right
porgybess said:
Are you sure that it doesn't charge albeit slowly? I've seen my battery percent rise even with the x over the battery icon
Click to expand...
Click to collapse
You're right. I've left it for a couple of hours to see if my PowerMonkey charges it and it seems to have moved from 40% to nearly 70% now. I wonder how it'll be in actual use so I have to report back on that (i.e. will my usage outperform the battery juice coming in?). Thanks for pointing out though.
That said, if there's a fix for the permissioning issue, still interested to hear from someone!!!!

Try using es explorer. In settings check the make /system rewritable
Then navigate to the file and open as text-> es note editor. I believe it has to do with the editor having to have root permissions before being able to save a file in system even if it's rw, and most editors do not request root access because it's not really needed for regular editing
Sent from my GT-P6800 using XDA

cmmc said:
Hi,
Let me start by saying that I just spend the last 7 hours searching everywhere on XDA and the net for this solution (!), but I really cannot find it. I've been a longtime reader of XDA and thought it was about time I posted something
I am looking to modify one single file (!) to get the USB charging to work whilst my Tab 7.7 (6800 3G) is on. Apparently this fix works (have seen youtube proof on Tab 10.1), but I don't have a clue how to get around the permissions! I want to connect to a USB power source whilst out and about.
This is the solution I've found (quoted verbatim from galaxytabhacks.com):
Click to expand...
Click to collapse
I believe that has nothing to do with permission. I ssh into my rooted tablet and attempted to change the charging_source in command line and it still returned to the value it used to be (2 - AC source):
Code:
/data/data/berserker.android.apps.sshdroid/home # cat /sys/class/power_supply/battery/charging_source
2
/data/data/berserker.android.apps.sshdroid/home # echo 0.5 > /sys/class/power_supply/battery/charging_source
/data/data/berserker.android.apps.sshdroid/home # cat /sys/class/power_supply/battery/charging_source
2
It doesn't seem to be an alterable flag but rather a display flag.
Can you show me the said working proof youtube for our further investigation?

[null]

Soldering Method: How do I disable SE Linux restrictions?

**UPDATE**
Here is my collection of scripts for rooting, blocking updates, and all kinds of stuff for ALL fire tv:
https://github.com/pwntrik/firetv/
Here's the video (2 parts) on howto root Fire TV 1st gen using soldering:
https://youtu.be/yhwYfudGiM8
https://youtu.be/Kn7zmXf08bk
**/UPDATE**
Greetings, AFTV hackers!
I have successfully soldered an emmc reader to the Fire TV 1st Gen, and I have complete r/w access. However, the tutorial for rooting appears to be a bit dated as the hacker (@maximus64) at the time was able to just copy the su binary to /system/xbin, modify the permissions, and run it.
Since FireOS 5.2.0.0, however, SELinux now prevents the binary from being executed:
(At this point, I have already copied su binary, chmod 6755 it, chown 0:0 it)
Code:
[email protected]:/ $ ls -la /system/xbin/su
ls -la /system/xbin/su
/system/xbin/su: Permission denied
1|[email protected]:/ $ su
su
/system/bin/sh: su: not found
127|[email protected]:/ $ ls -ld /system/xbin
ls -ld /system/xbin
drwxr-xr-x root shell 2017-01-05 01:35 xbin
[email protected]:/ $ ls -l /system/xbin/
ls -l /system/xbin/
-rwxr-xr-x root shell 63880 2016-05-27 17:00 dexdump
-rwxr-xr-x root shell 49816 2016-05-27 17:00 sqlite3
lstat '/system/xbin//su' failed: Permission denied
-rwxr-xr-x root shell 813248 2016-05-27 17:00 tcpdump
-rwxr-xr-x root shell 9384 2016-05-27 17:00 trapz
-rwxr-xr-x root shell 46456 2016-05-27 17:00 vitals_collection_agent
And just to make sure I did everything correctly, I hooked it up again then checked the binary:
Code:
[email protected]:/media/root/57f8f4bc-abf4-655f-bf67-946fc0f9f25b1/xbin# ls -la
total 1092
drwxr-xr-x. 2 root 2000 4096 Jan 5 04:35 .
drwxr-xr-x. 16 root root 4096 Jan 6 17:07 ..
-rwxr-xr-x. 1 root 2000 63880 May 27 2016 dexdump
-rwxr-xr-x. 1 root 2000 49816 May 27 2016 sqlite3
-rwsr-sr-x 1 root root 112576 Jan 5 04:31 su
-rwxr-xr-x. 1 root 2000 813248 May 27 2016 tcpdump
-rwxr-xr-x. 1 root 2000 9384 May 27 2016 trapz
-rwxr-xr-x. 1 root 2000 46456 May 27 2016 vitals_collection_agent
So at this point, I did some research and it seems that SELinux prevents this from being run. Does anyone have a workaround or could tell me how to give this binary permission? I have zero experience with SELinux, and even if anyone can point me to a similar thread for rooting when you have full r/w access, that'd be excellent..
Thanks!

cancelyourcable said:
Greetings, AFTV hackers!
I have successfully soldered an emmc reader to the Fire TV 1st Gen, and I have complete r/w access. However, the tutorial for rooting appears to be a bit dated as the hacker (@maximus64) at the time was able to just copy the su binary to /system/xbin, modify the permissions, and run it.
Since FireOS 5.2.0.0, however, SELinux now prevents the binary from being executed:
(At this point, I have already copied su binary, chmod 6755 it, chown 0:0 it)
Code:
[email protected]:/ $ ls -la /system/xbin/su
ls -la /system/xbin/su
/system/xbin/su: Permission denied
1|[email protected]:/ $ su
su
/system/bin/sh: su: not found
127|[email protected]:/ $ ls -ld /system/xbin
ls -ld /system/xbin
drwxr-xr-x root shell 2017-01-05 01:35 xbin
[email protected]:/ $ ls -l /system/xbin/
ls -l /system/xbin/
-rwxr-xr-x root shell 63880 2016-05-27 17:00 dexdump
-rwxr-xr-x root shell 49816 2016-05-27 17:00 sqlite3
lstat '/system/xbin//su' failed: Permission denied
-rwxr-xr-x root shell 813248 2016-05-27 17:00 tcpdump
-rwxr-xr-x root shell 9384 2016-05-27 17:00 trapz
-rwxr-xr-x root shell 46456 2016-05-27 17:00 vitals_collection_agent
And just to make sure I did everything correctly, I hooked it up again then checked the binary:
Code:
[email protected]:/media/root/57f8f4bc-abf4-655f-bf67-946fc0f9f25b1/xbin# ls -la
total 1092
drwxr-xr-x. 2 root 2000 4096 Jan 5 04:35 .
drwxr-xr-x. 16 root root 4096 Jan 6 17:07 ..
-rwxr-xr-x. 1 root 2000 63880 May 27 2016 dexdump
-rwxr-xr-x. 1 root 2000 49816 May 27 2016 sqlite3
-rwsr-sr-x 1 root root 112576 Jan 5 04:31 su
-rwxr-xr-x. 1 root 2000 813248 May 27 2016 tcpdump
-rwxr-xr-x. 1 root 2000 9384 May 27 2016 trapz
-rwxr-xr-x. 1 root 2000 46456 May 27 2016 vitals_collection_agent
So at this point, I did some research and it seems that SELinux prevents this from being run. Does anyone have a workaround or could tell me how to give this binary permission? I have zero experience with SELinux, and even if anyone can point me to a similar thread for rooting when you have full r/w access, that'd be excellent..
Thanks!
Click to expand...
Click to collapse
bueller_recovery_v2.zip begins with a shell script. If you open it in a text editor, you can see it. mkdir /system/recovery, unzip the contents of that zip to /system/recovery, and do the mv and ln commands. Make sure the selinux contexts of /system/recovery and it's contents match the other contents of /systems.
And also make sure the contents are chmod 755.

rbox said:
bueller_recovery_v2.zip begins with a shell script. If you open it in a text editor, you can see it. mkdir /system/recovery, unzip the contents of that zip to /system/recovery, and do the mv and ln commands. Make sure the selinux contexts of /system/recovery and it's contents match the other contents of /systems.
And also make sure the contents are chmod 755.
Click to expand...
Click to collapse
Thanks, rbox! I've managed to rewrite the script to do all that, but how do I make sure the SELinux contexts match? Sorry, not familiar with SELinux.
Is this the ACTUAL partition table, or is this the way the eMMC reader loads it?
Code:
[email protected]:/media/root# ls 5*
57f8f4bc-abf4-655f-bf67-946fc0f9f25b:
adb backup hostapd property system?
anr bugreports key_provisioning prReset time
app connectivity local radio tombstones
app-asec dalvik-cache logd resource-cache user
app_ext data lost+found securedStorageLocation vitals
app-lib debug_service media securestop webcrypto
app_ms dontpanic mediadrm security wiper
app-private dpm misc shared wpstiles
audio drm playready ssh
autotrace fota proffline system
57f8f4bc-abf4-655f-bf67-946fc0f9f25b1:
data lost+found usf
57f8f4bc-abf4-655f-bf67-946fc0f9f25b2:
com.amazon.avod.apk lost+found
com.amazon.venezia.apk recovery
com.amazon.vizzini-550901810.apk signed_com.amazon.kso.blackbird-1550000810.apk
dalvik-cache signed_CSAppFireTV-fireOs-release_v112.apk
57f8f4bc-abf4-655f-bf67-946fc0f9f25b3:
data lost+found usf
57f8f4bc-abf4-655f-bf67-946fc0f9f25b4:
app etc lib priv-app sqfs vendor
bin fonts lost+found recovery-from-boot.p tts xbin
build.prop framework media security usr
I ask because /system/bin is actually on a completely separate partition using this method. Is it possible to copy the actual init2stub in place of e2fsck instead of symlinking it? (in case the symlink doesn't work)
Here's my modified version of your script:
Code:
# Put your `recovery' folder in here, unzipped
SHARED="/media/sf_Shared"
# This is the directory created by the MMC reader
LABEL="/media/root/57f8f4bc-abf4-655f-bf67-946fc0f9f25b"
SYSTEM="${LABEL}/system"
BIN="${LABEL}4/bin"
echo "Copying recovery..."
cp -rf $SHARED/recovery $SYSTEM
echo "Chmodding..."
chmod -R 755 $SYSTEM/recovery
echo "Backup the old e2fsck..."
mv $BIN/e2fsck $BIN/e2fsck.real
echo "Symlink e2fsck to 2ndinitstub..."
# If symlink doesn't work, can I copy 2ndinitstub completely?
ln -sf ../recovery/2ndinitstub $BIN/e2fsck
echo "Done."
Thanks for your help otherwise I'd be so SCREWED! :laugh:

cancelyourcable said:
Thanks, rbox! I've managed to rewrite the script to do all that, but how do I make sure the SELinux contexts match? Sorry, not familiar with SELinux.
Is this the ACTUAL partition table, or is this the way the eMMC reader loads it?
Code:
[email protected]:/media/root# ls 5*
57f8f4bc-abf4-655f-bf67-946fc0f9f25b:
adb backup hostapd property system?
anr bugreports key_provisioning prReset time
app connectivity local radio tombstones
app-asec dalvik-cache logd resource-cache user
app_ext data lost+found securedStorageLocation vitals
app-lib debug_service media securestop webcrypto
app_ms dontpanic mediadrm security wiper
app-private dpm misc shared wpstiles
audio drm playready ssh
autotrace fota proffline system
57f8f4bc-abf4-655f-bf67-946fc0f9f25b1:
data lost+found usf
57f8f4bc-abf4-655f-bf67-946fc0f9f25b2:
com.amazon.avod.apk lost+found
com.amazon.venezia.apk recovery
com.amazon.vizzini-550901810.apk signed_com.amazon.kso.blackbird-1550000810.apk
dalvik-cache signed_CSAppFireTV-fireOs-release_v112.apk
57f8f4bc-abf4-655f-bf67-946fc0f9f25b3:
data lost+found usf
57f8f4bc-abf4-655f-bf67-946fc0f9f25b4:
app etc lib priv-app sqfs vendor
bin fonts lost+found recovery-from-boot.p tts xbin
build.prop framework media security usr
I ask because /system/bin is actually on a completely separate partition using this method. Is it possible to copy the actual init2stub in place of e2fsck instead of symlinking it? (in case the symlink doesn't work)
Here's my modified version of your script:
Code:
# Put your `recovery' folder in here, unzipped
SHARED="/media/sf_Shared"
# This is the directory created by the MMC reader
LABEL="/media/root/57f8f4bc-abf4-655f-bf67-946fc0f9f25b"
SYSTEM="${LABEL}/system"
BIN="${LABEL}4/bin"
echo "Copying recovery..."
cp -rf $SHARED/recovery $SYSTEM
echo "Chmodding..."
chmod -R 755 $SYSTEM/recovery
echo "Backup the old e2fsck..."
mv $BIN/e2fsck $BIN/e2fsck.real
echo "Symlink e2fsck to 2ndinitstub..."
# If symlink doesn't work, can I copy 2ndinitstub completely?
ln -sf ../recovery/2ndinitstub $BIN/e2fsck
echo "Done."
Thanks for your help otherwise I'd be so SCREWED! :laugh:
Click to expand...
Click to collapse
That is /data. Not /system. ls -lZ will show you contexts.

rbox said:
That is /data. Not /system. ls -lZ will show you contexts.
Click to expand...
Click to collapse
Well, not sure exactly what happened but I booted it back up and /system/recovery doesn't exist. Even if that's normal behavior, it didn't run TWRP.
The shell script I pasted above, it runs chcon and chmod, but perhaps chcon has no effect since it's being run on a host system (linux), instead of the actual android system (I kinda expected that.)
Code:
[email protected]:/system/bin $ ls -Z e2*
ls -Z e2*
e2fsck: Permission denied
e2fsck.real: Permission denied
Is there an init file I can edit to run chcon or completely disable selinux? Seems like that's probably preventing it. I can't see log files as user, but I feel like that might be part of it.
Thanks

cancelyourcable said:
Well, not sure exactly what happened but I booted it back up and /system/recovery doesn't exist. Even if that's normal behavior, it didn't run TWRP.
The shell script I pasted above, it runs chcon and chmod, but perhaps chcon has no effect since it's being run on a host system (linux), instead of the actual android system (I kinda expected that.)
Code:
[email protected]:/system/bin $ ls -Z e2*
ls -Z e2*
e2fsck: Permission denied
e2fsck.real: Permission denied
Is there an init file I can edit to run chcon or completely disable selinux? Seems like that's probably preventing it. I can't see log files as user, but I feel like that might be part of it.
Thanks
Click to expand...
Click to collapse
Did you properly unmount the filesystem after you were done changing it? That's really the only way the changes wouldn't stick and recovery wouldn't be there. You definitely need to verify all the permissions and contexts manually before booting back in. Don't just assume a script worked. Also, I think chcon isn't going to work, now that I think about it. I remember when I was messing around with this stuff with the Fire TV 2 I wound up having to use extended attributes manually. This page: http://unix.stackexchange.com/quest...on-mounted-ext4-image-from-non-selinux-system explains how to do. As for disabling selinux... that's half the whole point of 2ndinit

rbox said:
Did you properly unmount the filesystem after you were done changing it? That's really the only way the changes wouldn't stick and recovery wouldn't be there. You definitely need to verify all the permissions and contexts manually before booting back in. Don't just assume a script worked. Also, I think chcon isn't going to work, now that I think about it. I remember when I was messing around with this stuff with the Fire TV 2 I wound up having to use extended attributes manually. This page: http://unix.stackexchange.com/quest...on-mounted-ext4-image-from-non-selinux-system explains how to do. As for disabling selinux... that's half the whole point of 2ndinit
Click to expand...
Click to collapse
Ya, definitely unmounted it. I'm like 99% sure it's because of this selinux thing. Ideally if I can get these extended attributes to work and run either `su' or get the recovery to load, that'd be best.
But /system and /recovery are on two separate partitions. When I look at the layout from linux when I mount it using the soldering method, it looks like this:
Code:
# /dev/sdb1 on /media/root/57f8f4bc-abf4-655f-bf67-946fc0f9f25b3 type ext4 (rw,nosuid,nodev,relatime,data=ordered,uhelper=udisks2)
# /dev/sdb19 on /media/root/57f8f4bc-abf4-655f-bf67-946fc0f9f25b2 type ext4 (rw,nosuid,nodev,relatime,data=ordered,uhelper=udisks2)
# /dev/sdb2 on /media/root/57f8f4bc-abf4-655f-bf67-946fc0f9f25b1 type ext4 (rw,nosuid,nodev,relatime,data=ordered,uhelper=udisks2)
# /dev/sdb20 on /media/root/57f8f4bc-abf4-655f-bf67-946fc0f9f25b type ext4 (rw,nosuid,nodev,relatime,data=ordered,uhelper=udisks2)
# /dev/sdb18 on /media/root/57f8f4bc-abf4-655f-bf67-946fc0f9f25b4 type ext4 (rw,nosuid,nodev,relatime,data=ordered,uhelper=udisks2)
And from the firetv using adb shell, here's all the mounts:
Code:
[email protected]:/ $ mount
mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,nomblk_io_submit,nobarrier,commit=20,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware vfat ro,context=u:object_r:firmware_file:s0,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/loop0 /mnt/sqfs squashfs ro,context=u:object_r:squashfs_file:s0,relatime 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,context=u:object_r:persist_file:s0,nosuid,nodev,noatime,data=ordered 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /mnt/shell/emulated/0 fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
It looks very different. Like the /bin that appears in /system on the fire tv is actually on /media/root/57f8f4bc-abf4-655f-bf67-946fc0f9f25b4, yet /system appears on a completely separate partition /media/root/57f8f4bc-abf4-655f-bf67-946fc0f9f25b it's weird. Copying e2fsck did make it appear there, yet adding /system/recovery did nothing:
Code:
[email protected]:/ $ cd /system/recovery
cd /system/recovery
/system/bin/sh: cd: /system/recovery: No such file or directory
Not sure whether this is the firetv or the emmc reader which is displaying it oddly.
I'll wire it back up tomorrow and see if I can get extended permissions as well as try to figure out why the recovery dir is not showing up at all.
Thanks!

cancelyourcable said:
Ya, definitely unmounted it. I'm like 99% sure it's because of this selinux thing. Ideally if I can get these extended attributes to work and run either `su' or get the recovery to load, that'd be best.
But /system and /recovery are on two separate partitions. When I look at the layout from linux when I mount it using the soldering method, it looks like this:
Code:
# /dev/sdb1 on /media/root/57f8f4bc-abf4-655f-bf67-946fc0f9f25b3 type ext4 (rw,nosuid,nodev,relatime,data=ordered,uhelper=udisks2)
# /dev/sdb19 on /media/root/57f8f4bc-abf4-655f-bf67-946fc0f9f25b2 type ext4 (rw,nosuid,nodev,relatime,data=ordered,uhelper=udisks2)
# /dev/sdb2 on /media/root/57f8f4bc-abf4-655f-bf67-946fc0f9f25b1 type ext4 (rw,nosuid,nodev,relatime,data=ordered,uhelper=udisks2)
# /dev/sdb20 on /media/root/57f8f4bc-abf4-655f-bf67-946fc0f9f25b type ext4 (rw,nosuid,nodev,relatime,data=ordered,uhelper=udisks2)
# /dev/sdb18 on /media/root/57f8f4bc-abf4-655f-bf67-946fc0f9f25b4 type ext4 (rw,nosuid,nodev,relatime,data=ordered,uhelper=udisks2)
And from the firetv using adb shell, here's all the mounts:
Code:
[email protected]:/ $ mount
mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,nomblk_io_submit,nobarrier,commit=20,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware vfat ro,context=u:object_r:firmware_file:s0,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/loop0 /mnt/sqfs squashfs ro,context=u:object_r:squashfs_file:s0,relatime 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,context=u:object_r:persist_file:s0,nosuid,nodev,noatime,data=ordered 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /mnt/shell/emulated/0 fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
It looks very different. Like the /bin that appears in /system on the fire tv is actually on /media/root/57f8f4bc-abf4-655f-bf67-946fc0f9f25b4, yet /system appears on a completely separate partition /media/root/57f8f4bc-abf4-655f-bf67-946fc0f9f25b it's weird. Copying e2fsck did make it appear there, yet adding /system/recovery did nothing:
Code:
[email protected]:/ $ cd /system/recovery
cd /system/recovery
/system/bin/sh: cd: /system/recovery: No such file or directory
Not sure whether this is the firetv or the emmc reader which is displaying it oddly.
I'll wire it back up tomorrow and see if I can get extended permissions as well as try to figure out why the recovery dir is not showing up at all.
Thanks!
Click to expand...
Click to collapse
You're not looking for a partition with a directory called system in it. The partition IS /system. So the partition with 'bin' and 'xbin' is the /system partition. That other one is /data.

rbox said:
You're not looking for a partition with a directory called system in it. The partition IS /system. So the partition with 'bin' and 'xbin' is the /system partition. That other one is /data.
Click to expand...
Click to collapse
Alright, so I made some big progress
Here's my script which successfully installed your TWRP zip:
Code:
# Put your `recovery' folder in here, unzipped
SHARED="/media/sf_Shared"
# This is the directory created by the MMC reader
LABEL="/media/root/57f8f4bc-abf4-655f-bf67-946fc0f9f25b"
# WARNING: this CHANGED from 4 to 3. Always CHECK FIRST
SYSTEM="${LABEL}3"
if [ ! -e "${SYSTEM}/xbin" ]; then
echo "ERROR: couldn't find /system/xbin - is the mount point correct?"
exit 1
fi
echo "Copying recovery..."
cp -rf $SHARED/recovery $SYSTEM
echo "Backup the old e2fsck..."
cp -i $SYSTEM/bin/e2fsck $SHARED/e2fsck.real
mv -i $SYSTEM/bin/e2fsck $SYSTEM/bin/e2fsck.real
echo "Chmodding and chconing RECOVERY..."
chown -R 0:2000 $SYSTEM/recovery
chmod -R 755 $SYSTEM/recovery
chcon -R --reference=$SYSTEM/bin $SYSTEM/recovery
echo "Copying, chmodding and chconing SU (in case recovery doesn't work out)..."
cp $SHARED/su $SYSTEM/xbin/
chown 0:2000 $SYSTEM/xbin/su
chmod 6755 $SYSTEM/xbin/su
chcon --reference=$SYSTEM/xbin/trapz $SYSTEM/xbin/su
echo "Symlink e2fsck to 2ndinitstub..."
ln -sf ../recovery/2ndinitstub $SYSTEM/bin/e2fsck
echo "Done."
Then I booted into TWRP successfully.
However, when I tried to install your bueller-5.2.1.1-rooted_r1 I got this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After a long time it was clearly hung, so I rebooted and now it's bricked. But I did do a `dd if=/dev/sdb123 of=system.img` so i have that.
Would it be possible to just overwrite that partition with your system prerooted image while I have it connected to the emmc reader?
Thanks again for all the help!

cancelyourcable said:
Alright, so I made some big progress
Here's my script which successfully installed your TWRP zip:
Code:
# Put your `recovery' folder in here, unzipped
SHARED="/media/sf_Shared"
# This is the directory created by the MMC reader
LABEL="/media/root/57f8f4bc-abf4-655f-bf67-946fc0f9f25b"
# WARNING: this CHANGED from 4 to 3. Always CHECK FIRST
SYSTEM="${LABEL}3"
if [ ! -e "${SYSTEM}/xbin" ]; then
echo "ERROR: couldn't find /system/xbin - is the mount point correct?"
exit 1
fi
echo "Copying recovery..."
cp -rf $SHARED/recovery $SYSTEM
echo "Backup the old e2fsck..."
cp -i $SYSTEM/bin/e2fsck $SHARED/e2fsck.real
mv -i $SYSTEM/bin/e2fsck $SYSTEM/bin/e2fsck.real
echo "Chmodding and chconing RECOVERY..."
chown -R 0:2000 $SYSTEM/recovery
chmod -R 755 $SYSTEM/recovery
chcon -R --reference=$SYSTEM/bin $SYSTEM/recovery
echo "Copying, chmodding and chconing SU (in case recovery doesn't work out)..."
cp $SHARED/su $SYSTEM/xbin/
chown 0:2000 $SYSTEM/xbin/su
chmod 6755 $SYSTEM/xbin/su
chcon --reference=$SYSTEM/xbin/trapz $SYSTEM/xbin/su
echo "Symlink e2fsck to 2ndinitstub..."
ln -sf ../recovery/2ndinitstub $SYSTEM/bin/e2fsck
echo "Done."
Then I booted into TWRP successfully.
However, when I tried to install your bueller-5.2.1.1-rooted_r1 I got this:
View attachment 3996750
After a long time it was clearly hung, so I rebooted and now it's bricked. But I did do a `dd if=/dev/sdb123 of=system.img` so i have that.
Would it be possible to just overwrite that partition with your system prerooted image while I have it connected to the emmc reader?
Thanks again for all the help!
Click to expand...
Click to collapse
UPDATE...
I flashed my original system.img and brought it back to a working state. After that, I set up recovery again then tried to install bueller-5.2.1.1-rooted_r1.zip. Same as before, it froze, but this time at 80%:
Here's the only "log" I could find:
Code:
[email protected]:/media/root/57f8f4bc-abf4-655f-bf67-946fc0f9f25b4/recovery# cat log
Installing new recovery image: failed
So now I have the emmc reader connected again, and I'm *hoping* I can just flash the image in your bueller-5.2.1.1-rooted_r1.zip directly to the mmc using `dd if=system.new.dat of=/dev/sdb19`
But I thought I'd run it by your first before I brick it again :laugh:
Thanks again, @rbox

cancelyourcable said:
UPDATE...
I flashed my original system.img and brought it back to a working state. After that, I set up recovery again then tried to install bueller-5.2.1.1-rooted_r1.zip. Same as before, it froze, but this time at 80%:
View attachment 3997946
Here's the only "log" I could find:
Code:
[email protected]:/media/root/57f8f4bc-abf4-655f-bf67-946fc0f9f25b4/recovery# cat log
Installing new recovery image: failed
So now I have the emmc reader connected again, and I'm *hoping* I can just flash the image in your bueller-5.2.1.1-rooted_r1.zip directly to the mmc using `dd if=system.new.dat of=/dev/sdb19`
But I thought I'd run it by your first before I brick it again :laugh:
Thanks again, @rbox
Click to expand...
Click to collapse
The thread for TWRP talks about what to do if it hangs. You can use adb. You'll need to check the log while it's running. /tmp/recovery.log. The image in the rom is sparse, so you'll have to run sdat2img.py on it. And then you'll have to do all the steps listed in the updater-script. The image itself is 100% pure stock.

rbox said:
The thread for TWRP talks about what to do if it hangs. You can use adb. You'll need to check the log while it's running. /tmp/recovery.log. The image in the rom is sparse, so you'll have to run sdat2img.py on it. And then you'll have to do all the steps listed in the updater-script. The image itself is 100% pure stock.
Click to expand...
Click to collapse
I discovered your "updater-script" so I understand the process a lot better now (wish I had found this earlier)
How do I know which image to use for boot: boot.img or boot_unlocked.img? I'm running from a host system so I can't check the value of ro.boot.unlocked_kernel from within linux.
Thanks!
P.S. Almost finished a bash script others can use to flash your image from an emmc reader - I will post a guide on here!

cancelyourcable said:
I discovered your "updater-script" so I understand the process a lot better now (wish I had found this earlier)
How do I know which image to use for boot: boot.img or boot_unlocked.img? I'm running from a host system so I can't check the value of ro.boot.unlocked_kernel from within linux.
Thanks!
P.S. Almost finished a bash script others can use to flash your image from an emmc reader - I will post a guide on here!
Click to expand...
Click to collapse
Since it's running OS5, you have to use the regular boot.img, since your bootloader isn't unlocked.

cancelyourcable said:
P.S. Almost finished a bash script others can use to flash your image from an emmc reader - I will post a guide on here!
Click to expand...
Click to collapse
I would really appreciate this.

zexma said:
I would really appreciate this.
Click to expand...
Click to collapse
It's almost done! Will post very soon

cancelyourcable said:
It's almost done! Will post very soon
Click to expand...
Click to collapse
Don't want to bother, you
Is there any progress to expect, cause I'm stuck at the very same point, SELinux prevents loading su
(/system/xbin//su' failed: Permission denied)
Thanks in advance.

pwntrik said:
It's almost done! Will post very soon
Click to expand...
Click to collapse
Any progress on this?

zexma said:
Any progress on this?
Click to expand...
Click to collapse
Yes, it works 100%. Literally just ordered an overhead camera tripod for recording a video of the whole process. Sit tight -- I promise it's coming soon!

@pwntrik : any tricks to have your Linux (Ubuntu) box recognizing the FireTV in fastboot mode?
I can get it to connect in fastboot with Win7 on the same machine, but in Ubuntu 16.04 I'm not able to.
I did add ATTR{idVendor}== "1949" and ATTR{idProduct}=="0401" to /etc/udev/51-android.rules and rebooted, but no luck...
My FireTV (1st gen, last firmware was 5.0.5, rooted) is currently , after unsuccessful flash of "rooted-5.0.5_r1" ROM in TWRP stuck at this screen:
.
I know it's a longshot to recover it, but I have patience....
Sent from space

kozmo2k4 said:
@pwntrik : any tricks to have your Linux (Ubuntu) box recognizing the FireTV in fastboot mode?
I can get it to connect in fastboot with Win7 on the same machine, but in Ubuntu 16.04 I'm not able to.
I did add ATTR{idVendor}== "1949" and ATTR{idProduct}=="0401" to /etc/udev/51-android.rules and rebooted, but no luck...
My FireTV (1st gen, last firmware was 5.0.5, rooted) is currently , after unsuccessful flash of "rooted-5.0.5_r1" ROM in TWRP stuck at this screen:
.
I know it's a longshot to recover it, but I have patience....
Sent from space
Click to expand...
Click to collapse
I've been using Win10 for that. I only use Linux for writing the images.

can't find boot partition while trying to install usb host-mode on nook simple touch

Hello,
I am trying to install USB host-mode on my rooted nook simple touch so that I can use a keyboard or a mouse as a page turner. I am running 1.2.1, and rooted the nook using nook manager https://forum.xda-developers.com/showthread.php?t=2040351. This completed successfully. Then I installed a terminal app (can't find the link but it's called jackpal.androidterm.apk, can attach if needed) by putting it on a micro sd card and installing the file using relaunch (a file explorer app that appeared after rooting). Then I followed the instructions on https://forum.xda-developers.com/wiki/BN_Nook_Simple_Touch/Replacing_boot_files writing
su
mount -o rw,remount rootfs /
mkdir /boot
mount -t vfat /dev/block/mmcblk0p1 /boot
into the terminal app. It asked for permissions after su, which I granted and the other lines produced no errors but also no outputs. Now I am trying to find the /boot partition to replace uImage, as per the instructions, but I can't find /boot. It appears nowhere in the file explorer, and under advanced functions, the nook lists the following disks/partitions: /rom, /system, /data, /cache, /sdcard, /media, but no /boot
Any ideas? Really unsure as to why it's not showing up, because the commands that are supposed to create it seemed to complete without issue.
p.s. I also checked show hidden files in folders in the advanced settings

I dunno. Your "File Explorer" may be leading you astray.
Just do an ls -l in terminal and check.

ls -l produces:
drwxrwx--- system system 1969-12-31 16:00 rom
drwxrwxrwt root root 2018-02-26 11:11 sqlite_stmt_journals
d---rwxr-x system sdcard_rw 1969 -12-31 16:00 sdcard
drwxrwxr-x system sdcard_rw 1969 -12-31 16:00 media
drwxrwx--- system cache 2018-02-15 11:23 cache
drwxrwxrwx root root 2018-02-26 11:11 tmp
lrwxrwxrwx root root 2018-02-26 11:11 etc -> /system/etc
-rw-r--r-- root root 118 2018-02-15 12:03 init.rc.orig
-rw-r--r-- root root 118 2018-02-15 12:19 default.prop.orig
drwxr-xr-x root root 2018-02-05 12:19 system
drwxr-xr-x root root 1969-12-31 16:00 sys
drwxr-x--- root root 2018-02-15 12:03 sbin
dr-xr-xr-x root root 1969-12-31 16:00 proc
-rwxr-x--- root root 1677 2018-02-15 12:03 init.goldfish.rc
-rwxr-x--- root root 128000 2018-02-15 12:03 init
-rwxr-x--- root root 324 2018-02-15 12:03 env.txt
drwxrwx--x system system 2018-02-15 11:24 data
-rw-r--r-- root root 118 2018-02-15 12:03 default.prop
-rwxr-x--- root root 19284 2018-02-15 12:03 init.rc
drwx------ root root 2012-12-07 14:34 root
drwxr-xr-x root root 2018-02-26 11:11 dev
Further, I tried to copy uImage into /boot using the terminal and it acted as if /boot didn't exist, so I'm pretty sure that it isn't there for some reason.
Thanks

Well, something you're doing isn't working.
The commands are correct.
Code:
su
Did this work? Do you get a # prompt? Type "id", does it say you're root?
Code:
mount -o rw,remount rootfs /
Ok, did it remount? Type "mount" and see if rootfs is actually "rw".
Code:
mkdir /boot
Apparently this didn't work because you should see an empty directory at least.
Code:
mount -t vfat /dev/block/mmcblk0p1 /boot
Apparently this didn't work.

Did this work? Do you get a # prompt? Type "id", does it say you're root?
su produces a # prompt, and id produces: uid=0(root) gid=0(root), so i think this part worked.
Ok, did it remount? Type "mount" and see if rootfs is actually "rw".
mount produces: rootfs / rootfs rw 0 0, and then a bunch of other stuff, so i think this worked too.
mkdir /boot
this produces nothing, just another # prompt, so this might be the problem
mount -t vfat /dev/block/mmcblk0p1 /boot
this also produces nothing, just another # prompt.
Any idea why mkdir /boot would fail?
Thanks for being so helpful!

Well, the mkdir should have created an empty directory.
You should be able to "ls -l /" it.
If not, you could mkdir and mount anywhere.
Code:
cd /data/local/tmp
mkdir mybooty
mount -t vfat /dev/block/mmcblk0p1 /data/local/tmp/mybooty
There's nothing special about the name "boot".

Okay,
That solved the problem. Thanks for all your help!