Database Develop

Ubuntu partition dump from Stock Atrix

The link below is a dump of the /dev/block/mmcblk0p13 partition.
It is the entire ubuntu "distribution". However, it is not an OS per say. It is just an environment compiled and setup to run on the "android linux". Everything just runs from a second X session started on top of the native Android Arm linux redirected to the HDMI display port.
The partition has about 800MB in size and is mounted under /osh once the system boots.
Something worth to note, is that the webtop X session does not consume any RAM or system resource at all till when the phone enters RM_SM_DOCKED mode. While the phone is on RM_SM_MOBILE mode, that X session is complete shutdown.
http://www.usk.bz/android/ubuntu.img.bz2
If you use a linux or MacOS, just uncompress the file with bzip2 -d , then mount like this:
mount -t ext3 -o loop,ro ubuntu.img /mnt/loop
Of course, make sure the directory /mnt/loop exists.
Also, some directories, like /etc will not be available or will look like bugged/corrupted, it's because they are actually just a "link" to the /etc from the root partition. I can provide a dump for that partition as well, if that will help with any development. Let me know.
Have fun and post us if you find anything special.

A bit further: There's a chroot involved! And the adas account password is randomly set!
... Buuuuuuuuut, Motorola was smart and got rid of telnetd, etc in this production script...
See /usr/local/sbin/webtop-product.sh.
It's the script that makes the "production" webtop - and removes the fun stuff via dpkg in the process.
But here's a hint - if you can run an app within Webtop, get it to run /usr/bin/.lxterminal - they HID the terminal app.
EDIT: Hm. /usr/local/share/motorola/fireboxmake/ has some interesting readmes... on what .sh does what in /usr/local/sbin.
EDIT2: Check out what's in the OSH_tools.tgz. Motorola left a bootloader BIN in there along with some interesting flashing scripts for both Webtop and the Android side... and some interesting config files in nvflash...
Also, can I get the root filesystem for /etc/?

I have not downloaded the archive yet but did a search for RM_SM_DOCKED on google and came up with a hit elsewhere.
I can't post the link to this directly due to it being one of my first posts. It's only one of 3/4 hits on google.
I am guessing it is in the archive you posted.
Code:
#
#
on property:dev.bootcomplete=1
#
setprop ro.webtop.boot 1
#
start loadpreinstalls
#
#
on property:ro.webtop.boot=1
#
exec /system/bin/logwrapper /ubuntu.sh
#
#
on property:sys.SystemMode=RM_SM_DOCKED
#
exec /osh/etc/init.d/startX.sh
#

uskr said:
The link below is a dump of the /dev/block/mmcblk0p13 partition.
It is the entire ubuntu "distribution". However, it is not an OS per say. It is just an environment compiled and setup to run on the "android linux". Everything just runs from a second X session started on top of the native Android Arm linux redirected to the HDMI display port.
The partition has about 800MB in size and is mounted under /osh once the system boots.
Something worth to note, is that the webtop X session does not consume any RAM or system resource at all till when the phone enters RM_SM_DOCKED mode. While the phone is on RM_SM_MOBILE mode, that X session is complete shutdown.
http://www.usk.bz/android/ubuntu.img.bz2
If you use a linux or MacOS, just uncompress the file with bzip2 -d , then mount like this:
mount -t ext3 -o loop,ro ubuntu.img /mnt/loop
Of course, make sure the directory /mnt/loop exists.
Also, some directories, like /etc will not be available or will look like bugged/corrupted, it's because they are actually just a "link" to the /etc from the root partition. I can provide a dump for that partition as well, if that will help with any development. Let me know.
Have fun and post us if you find anything special.
Click to expand...
Click to collapse
uskr,
Excellent work & post, have a Thanks.
It's a shame that the webtop will probably flop (and I sure as heck won't buy one for the price they're asking). Here's to hoping a dockless hack comes up.

uskr,
Great post, Thanks

labsONE said:
Also, can I get the root filesystem for /etc/?
Click to expand...
Click to collapse
http://www.usk.bz/android/etc.tar.bz2
You will notice some files are just links to /system/etc. You can find the /system dump on another thread on this forum. If you cant, let me know and I will get a link here.

Can someone take a good look at the contents of:
/usr/local/share/motorola/fireboxmake/OSH_tools.tgz
There's lots of interesting stuff in there & I am completely unfamiliar with tegra and Motorola cruft.

uskr said:
The link below is a dump of the /dev/block/mmcblk0p13 partition.
It is the entire ubuntu "distribution". However, it is not an OS per say. It is just an environment compiled and setup to run on the "android linux". Everything just runs from a second X session started on top of the native Android Arm linux redirected to the HDMI display port.
The partition has about 800MB in size and is mounted under /osh once the system boots.
Something worth to note, is that the webtop X session does not consume any RAM or system resource at all till when the phone enters RM_SM_DOCKED mode. While the phone is on RM_SM_MOBILE mode, that X session is complete shutdown.
If you use a linux or MacOS, just uncompress the file with bzip2 -d , then mount like this:
mount -t ext3 -o loop,ro ubuntu.img /mnt/loop
Of course, make sure the directory /mnt/loop exists.
Also, some directories, like /etc will not be available or will look like bugged/corrupted, it's because they are actually just a "link" to the /etc from the root partition. I can provide a dump for that partition as well, if that will help with any development. Let me know.
Have fun and post us if you find anything special.
Click to expand...
Click to collapse
uskr, appreciate if you could also get us the root partition dump

Actually, sorry for not posting this before. But right after I posted the first dump I noticed that pretty much everything on the root partition is just a link to /osh, like you can see here:
Code:
lrwxrwxrwx root root 2011-02-22 23:54 lib -> /osh/lib
lrwxrwxrwx root root 2011-02-22 23:54 etc -> /osh/etc
lrwxrwxrwx root root 2011-02-22 23:54 thumb2 -> /osh/thumb2
lrwxrwxrwx root root 2011-02-22 23:54 srv -> /osh/srv
lrwxrwxrwx root root 2011-02-22 23:54 usr -> /osh/usr
lrwxrwxrwx root root 2011-02-22 23:54 media -> /osh/media
lrwxrwxrwx root root 2011-02-22 23:54 upath.sh -> /osh/upath.sh
lrwxrwxrwx root root 2011-02-22 23:54 boot -> /osh/boot
lrwxrwxrwx root root 2011-02-22 23:54 sbin -> /osh/sbin
lrwxrwxrwx root root 2011-02-22 23:54 var -> /osh/var
lrwxrwxrwx root root 2011-02-22 23:54 root -> /osh/root
lrwxrwxrwx root root 2011-02-22 23:54 apath.sh -> /osh/apath.sh
lrwxrwxrwx root root 2011-02-22 23:54 bin -> /osh/bin
lrwxrwxrwx root root 2011-02-22 23:54 opt -> /osh/opt
lrwxrwxrwx root root 2011-02-22 23:54 selinux -> /osh/selinux
lrwxrwxrwx root root 2011-02-22 23:54 ubuntu.sh -> /osh/ubuntu.sh
lrwxrwxrwx root root 2011-02-22 23:54 lost+found -> /osh/lost+found
lrwxrwxrwx root root 2011-02-22 23:54 home -> /data/home
dr-x------ root root 2011-02-22 23:54 config
drwxrwx--- system misc 2011-02-22 23:54 misc
drwxrwx--- system cache 2011-02-23 00:58 cache
drwxr-xr-x root root 2011-01-30 05:54 pds
lrwxrwxrwx root root 2011-02-22 23:54 sdcard-ext -> /mnt/sdcard-ext
lrwxrwxrwx root root 2011-02-22 23:54 sdcard -> /mnt/sdcard
drwxr-xr-x root root 2011-02-22 23:54 acct
lrwxrwxrwx root root 2011-02-22 23:54 tmp -> /data/tmp
drwxr-xr-x root root 2010-12-22 17:39 preinstall
drwxr-xr-x root root 2011-01-20 21:49 osh
drwxrwxr-x root system 2011-02-22 23:54 mnt
lrwxrwxrwx root root 2011-02-22 23:54 d -> /sys/kernel/debug
drwxr-xr-x root root 2011-02-05 05:07 system
drwxr-xr-x root root 1969-12-31 19:00 sys
dr-xr-xr-x root root 1969-12-31 19:00 proc
-rwxr-x--- root root 32498 1969-12-31 19:00 init.rc
-rwxr-x--- root root 1954 1969-12-31 19:00 init.goldfish.rc
-rwxr-x--- root root 118156 1969-12-31 19:00 init
-rw-r--r-- root root 153 1969-12-31 19:00 default.prop
drwxrwx--x system system 2011-02-22 23:54 data
drwxr-xr-x root root 2011-02-22 23:54 dev
But for some reason when I dump the /osh partition, a couple of those folders come corrupted. Let me know if any of the folders you are interested are damaged on the dump and I will post a tar.bz2 like I did with /etc

htc g1 dmd64 - want start dreaimg.nbh

Hi, i just want to root my G1 T-mobile USA (works good). So i download RC29 and copy to SD, renamed to DREAIMG.nbh/DreaIMG.nbh and always get nothing... "Press end to start" but i cant press nothing, its like freeze, i can only remove battery.
I have tried 100 times with other DREAIMG.nbh.
FirmWare: 1.6
BuildNumber: DMD64
DREA100 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-2.22.23.02
imgup.pl/di-34OA.jpg
Is any way to root it?
ps. I have rooted my previous G1 UK with this SD card without problems, so proably I do not to do goldcard)

Root with Universal AndRoot,, this is how i got my DMD64 rooted. Its just an app you put on the phone..roots it in a couple seconds

I trying it too, but always get: Parse error
Edit: Ok, i will try one more time. Proably KIS delete some files from this pack...
Edit2: Yea, its work now

Ok, i rooted it. But i want now to install recovery and get another errors and problems...
Code:
method with flash_image:
flash_image: not found
# mv /sdcard/flash_image /system/bin
mv /sdcard/flash_image /system/bin
failed on '/sdcard/flash_image' - Cross-device link
method with fastboot:
C:\Tools>fastboot erase recovery
< waiting for device >
So, what can i try do next?

you can use fastboot to flash a recovery image.. or you can use ROM manager to flash clockwork recovery mod.. ROM Manager is available free on the market.

omajgat said:
Ok, i rooted it. But i want now to install recovery and get another errors and problems...
Code:
method with flash_image:
flash_image: not found
# mv /sdcard/flash_image /system/bin
mv /sdcard/flash_image /system/bin
failed on '/sdcard/flash_image' - Cross-device link
method with fastboot:
C:\Tools>fastboot erase recovery
< waiting for device >
So, what can i try do next?
Click to expand...
Click to collapse
it seems like your g1 is not in fastboot mode? for the fastboot command to work, you have to use the "camera+power" to get into fastboot mode. Then plug your phone into your computer and type "fastboot devices" to make sure it is properly connected. You should see your serial number to your phone.

Guys, the 0.95.0000 SPL is not fastboot capable so all suggestions to use fastboot will confuse more than helping him.
Did you download the flash_image binary and saved it on the root of your sd-card?
Did you download the recovery binary and saved it on the root of your sd-card?
If you did both, then start a shell in a terminal program and do an
Code:
su
.
Now you can start the flashing by
Code:
chmod +x /sdcard/flash_image
/sdcard/flash_image recovery /sdcard/<recovery.img>
Another hint: read here in the forum and try to understand what you are doing. ... and a bit knowledge of Linux will help you much.
Sent from my Gingerbread on Dream using XDA App

AndDiSa said:
Guys, the 0.95.0000 SPL is not fastboot capable so all suggestions to use fastboot will confuse more than helping him.
Did you download the flash_image binary and saved it on the root of your sd-card?
Did you download the recovery binary and saved it on the root of your sd-card?
If you did both, then start a shell in a terminal program and do an
Code:
su
.
Now you can start the flashing by
Code:
chmod +x /sdcard/flash_image
/sdcard/flash_image recovery /sdcard/<recovery.img>
Another hint: read here in the forum and try to understand what you are doing. ... and a bit knowledge of Linux will help you much.
Sent from my Gingerbread on Dream using XDA App
Click to expand...
Click to collapse
Code:
C:\Tools>adb shell
$ su
su
# cd /sdcard
cd /sdcard
# ls -l
ls -l
d---rwxr-x system sdcard_rw 2011-10-22 13:04 LOST.DIR
----rwxr-x system sdcard_rw 6188 2011-10-22 14:31 UniversalAndroot.log
----rwxr-x system sdcard_rw 524288000 2011-10-22 16:56 Linux.loop
d---rwxr-x system sdcard_rw 2011-10-22 13:20 backup
d---rwxr-x system sdcard_rw 2011-10-24 18:25 DCIM
----rwxr-x system sdcard_rw 964401 2011-10-22 14:27 UniversalAndroot-1.6.2-beta5.apk
d---rwxr-x system sdcard_rw 2011-10-22 21:11 factory.widgets.skins
----rwxr-x system sdcard_rw 4712448 2011-10-22 15:04 recovery.img
----rwxr-x system sdcard_rw 9181622 2011-10-22 15:27 update.zip
----rwxr-x system sdcard_rw 26172 2009-10-03 17:07 flash_image
----rwxr-x system sdcard_rw 91564352 2009-01-01 12:58 DREAIMG.nbh
# chmod 700 flash_image
chmod 700 flash_image
# ls -l
ls -l
d---rwxr-x system sdcard_rw 2011-10-22 13:04 LOST.DIR
----rwxr-x system sdcard_rw 6188 2011-10-22 14:31 UniversalAndroot.log
----rwxr-x system sdcard_rw 524288000 2011-10-22 16:56 Linux.loop
d---rwxr-x system sdcard_rw 2011-10-22 13:20 backup
d---rwxr-x system sdcard_rw 2011-10-24 18:25 DCIM
----rwxr-x system sdcard_rw 964401 2011-10-22 14:27 UniversalAndroot-1.6.2-beta5.apk
d---rwxr-x system sdcard_rw 2011-10-22 21:11 factory.widgets.skins
----rwxr-x system sdcard_rw 4712448 2011-10-22 15:04 recovery.img
----rwxr-x system sdcard_rw 9181622 2011-10-22 15:27 update.zip
----rwxr-x system sdcard_rw 26172 2009-10-03 17:07 flash_image
----rwxr-x system sdcard_rw 91564352 2009-01-01 12:58 DREAIMG.nbh
# chmod 777 flash_image
chmod 777 flash_image
# ls -l
ls -l
d---rwxr-x system sdcard_rw 2011-10-22 13:04 LOST.DIR
----rwxr-x system sdcard_rw 6188 2011-10-22 14:31 UniversalAndroot.log
----rwxr-x system sdcard_rw 524288000 2011-10-22 16:56 Linux.loop
d---rwxr-x system sdcard_rw 2011-10-22 13:20 backup
d---rwxr-x system sdcard_rw 2011-10-24 18:25 DCIM
----rwxr-x system sdcard_rw 964401 2011-10-22 14:27 UniversalAndroot-1.6.2-beta5.apk
d---rwxr-x system sdcard_rw 2011-10-22 21:11 factory.widgets.skins
----rwxr-x system sdcard_rw 4712448 2011-10-22 15:04 recovery.img
----rwxr-x system sdcard_rw 9181622 2011-10-22 15:27 update.zip
----rwxr-x system sdcard_rw 26172 2009-10-03 17:07 flash_image
----rwxr-x system sdcard_rw 91564352 2009-01-01 12:58 DREAIMG.nbh
# chmod +x flash_image
chmod +x flash_image
Bad mode
# ls -l
ls -l
d---rwxr-x system sdcard_rw 2011-10-22 13:04 LOST.DIR
----rwxr-x system sdcard_rw 6188 2011-10-22 14:31 UniversalAndroot.log
----rwxr-x system sdcard_rw 524288000 2011-10-22 16:56 Linux.loop
d---rwxr-x system sdcard_rw 2011-10-22 13:20 backup
d---rwxr-x system sdcard_rw 2011-10-24 18:25 DCIM
----rwxr-x system sdcard_rw 964401 2011-10-22 14:27 UniversalAndroot-1.6.2-beta5.apk
d---rwxr-x system sdcard_rw 2011-10-22 21:11 factory.widgets.skins
----rwxr-x system sdcard_rw 4712448 2011-10-22 15:04 recovery.img
----rwxr-x system sdcard_rw 9181622 2011-10-22 15:27 update.zip
----rwxr-x system sdcard_rw 26172 2009-10-03 17:07 flash_image
----rwxr-x system sdcard_rw 91564352 2009-01-01 12:58 DREAIMG.nbh
#
Code:
C:\Tools>adb.exe shell
$ su
su
# cd /sdcard
cd /sdcard
# ls -l
ls -l
d---rwxr-x system sdcard_rw 2011-10-22 13:04 LOST.DIR
----rwxr-x system sdcard_rw 6188 2011-10-22 14:31 UniversalAndroot.log
----rwxr-x system sdcard_rw 524288000 2011-10-22 16:56 Linux.loop
d---rwxr-x system sdcard_rw 2011-10-22 13:20 backup
d---rwxr-x system sdcard_rw 2011-10-24 18:25 DCIM
----rwxr-x system sdcard_rw 964401 2011-10-22 14:27 UniversalAndroot-1.6.2-beta5.apk
d---rwxr-x system sdcard_rw 2011-10-22 21:11 factory.widgets.skins
----rwxr-x system sdcard_rw 4712448 2011-10-22 15:04 recovery.img
----rwxr-x system sdcard_rw 9181622 2011-10-22 15:27 update.zip
----rwxr-x system sdcard_rw 26172 2009-10-03 17:07 flash_image
----rwxr-x system sdcard_rw 91564352 2009-01-01 12:58 DREAIMG.nbh
# ./flash_image recovery.img
./flash_image recovery.img
./flash_image: permission denied
# ./flash_image recovery recovery.img
./flash_image recovery recovery.img
./flash_image: permission denied
# ./flash_image
./flash_image
./flash_image: permission denied
# flash_image
flash_image
flash_image: not found
# /sdcard/flash_image recoveery /sdcard/recovery.img
/sdcard/flash_image recoveery /sdcard/recovery.img
/sdcard/flash_image: permission denied
#
Any ideas?

/sdcard mounted in read only mode?
Nevertheless as I can see, its already executable, so give it a try.
If it's not working directly from /sdcard, it's probably due to FAT format of sdcard. Try to copy the files to /cache and try do the same from there.

Code:
# cp
cp
cp: not found
# mv flash_image /cache/
mv flash_image /cache/
failed on 'flash_image' - Cross-device link
#
What your magic ball say now?

omajgat said:
Code:
# cp
cp
cp: not found
# mv flash_image /cache/
mv flash_image /cache/
failed on 'flash_image' - Cross-device link
#
What your magic ball say now?
Click to expand...
Click to collapse
Need a hint, i.e. have to look here and we see, that running apps from /sdcard is not alowed and you need to remount /sdcard with exec permissions.

Thanks, im on froyo by laszlo now

Dual Boot Atrix: Simplified and Standalone (30 Jan 2013)

Quickly and conveniently leverage the strengths of mainstream ROMs and kernels using my new simplified and standalone dual boot tools!
Here I assume that your rooted Atrix with unlocked boot loader already hosts a ROM on EMMC. Even if you're not dual booting, I think you will find some or all of these tools helpful!
Steps
Code:
1. Boot to Recovery
2. Flash SmartPart FZ (partition SD card right on your phone!)
3. Flash Copy-ROM (copy ROM --- all except boot image --- from EMMC to SD card)
4. Flash Atrix Boot Emporium V3.0 (boot ROM on SD card to verify success)
5. Flash another ROM of your choice to EMMC and reboot (optional)
Links
SmartPart-V1.0-signed.zip: http://www.mediafire.com/?wm96y92g3lla3ot
Copy-ROM-V1.0-signed.zip: http://www.mediafire.com/?i068xs1ktdkd183
Atrix-Boot-Emporium-V3.0-signed.zip: http://www.mediafire.com/?zsf4is8fbzs7sf9
All zips tested working on my AT&T Atrix + Samsung 32GB Class 10 SD using ClockworkMod Recovery 5.0.2.0.
If everything goes well, you will have demonstrated "standalone" dual boot capability on your Atrix beauty without a computer! In fact, "unlisted" ROMs may be supported. For example I downloaded upndwn4par's CSROM V7.0 (26 Jan 2013), ported it to SD and then successfully booted it with faux's 1.0 GHz GB boot image featured in Emporium.
Walk-Through
Step 1: I prefer ClockworkMod Recovery 5.0.2.0 as it appears to be the most compatible recovery for Atrix.
Step 2: SmartPart FZ shrinks your (external) SD card's FAT32 partition by 4GB and adds three new “ext” partitions: /system, /cache and /data of ample size to host virtually any Android ROM. SmartPart FZ takes about 30-45 seconds to partition a Class 10 card.
Important! You MUST flash SmartPart FZ from internal memory (“choose zip from internal sdcard”) because if you flash it from external memory, your SD card gets mounted and you can't partition a mounted filesystem. Also it is a good idea to flash SmartPart FZ immediately after booting to CWM; else your SD card could get mounted accidentally.
Not sure you want dual boot? Just select the “Restore” option and Smart Part FZ restores your SD to its original state by removing any existing ext partitions (up to three consecutive partitions) and growing your FAT32 partition back to its original size. This takes about 10-15 seconds on a Class 10.
Note: SmartPart FZ is fundamentally the same as its shell script predecessor ( http://forum.xda-developers.com/showthread.php?t=1651356 ) --- except that FZ runs unattended and does not backup anything.
Step 3: Copy-ROM, with the “EMMC to SD Card” option selected, copies all files on /system, /cache and /data files to the equivalent SD card ext partitions created in Step 2. Your EMMC ROM becomes a “live backup” on SD that you can boot to, thus freeing up EMMC to host another ROM of your choice.
One advantage of copying a ROM to SD is that you can first configure it the way you wish (GApps etc.), and then copy it over instead of having to flash individual customized zip files to SD. Then you're ready to flash a different ROM to EMMC, or blast off with a fully redundant system.
Copy-ROM uses the “cp -a” command, which I have found to be several times faster than cloning partitions. How much faster depends partly on disk usage since cloning copies everything, including empty space. Example: Port CM10 Liquid Smooth with ~100 total apps to a Class 10 SD. Clone ROM takes 15 minutes. Copy-ROM takes less than 2 minutes.
Another advantage of copying files over cloning partitions is that you don't have to worry about partition size mismatch. And I would not want to modify EMMC partitions --- too scary for me.
Step 4: Use Emporium V3.0 to boot a supported ROM whether it is hosted on EMMC or SD. Emporium contains boot images and corresponding /system/lib/modules for:
Code:
ICS MROM
ICSROM
CM10 epinter (Stock and OC1300)
CM10 Th3Bill (AOKP, Liquid Smooth and MIUI)
CM7 MROM (HV and SV)
CM7 Neutrino (EE, GT and GT+)
GB MROM (HV and SV)
GB NottachTrix (ATT and faux 1.00, 1.30 and 1.45)
Emporium V3.0 is less than 120 MB compressed and 10-15% more uncompressed. Each file named “boot.img” was lifted from its respective ROM zip. Each file named “boot-sd.img” exactly matches its big brother boot.img, except that ramdisk was modified to redirect ROM filesystem mounts from EMMC to SD:
Code:
/system: mmcblk0p12 to mmcblk1p2
/cache: mmcblk0p15 to mmcblk1p3
/data: mmcblk0p16 to mmcblk1p4
except for CM10 boot images. Please read CM10 Notes below.
Emporium Options
One of the dilemmas associated with dual booting is how to clear /cache and or /data. Of course CWM can do this, but only for ROMs hosted on EMMC: It does not recognize ROMs hosted on SD. And CWM is a little cumbersome to use since the clearing options are not all on one page. Emporium addresses these issues by displaying a single page with options to:
Code:
Clear /cache and /data/dalvik-cache
Clear /data (BE CAREFUL)
on EMMC or SD depending on the option selected on the first page. Now you can conveniently boot to a jet clean ROM whether it is hosted on EMMC or SD. Of course if you just copied a healthy ROM to SD, it is probably not necessary to clear.
I will explain the third option: Extract Boot Files to /sdcard/Boot later.
All three options are null by default.
Step 5: Nothing new here if you've ever flashed a ROM.
Now if for some reason you want to reverse the process and copy a ROM from SD Card to EMMC, just flash Copy-ROM and this time select the “SD to EMMC” option. Then flash Emporium or fastboot your EMMC ROM with the boot image of your choice. You may want to Nandroid-backup or Titanium Backup before doing a reverse copy.
Of course there are faster ways to switch between ROMs. But the tools presented here give your Atrix a simplified, standalone dual boot capability using all flashable zips.
Once you're comfortable using these flashable zip tools, you can then move onto “live” boot switching using all soft keys. To that end, I rolled up all of Emporium's boot images and my simplified boot switcher “boot-rom.sh” to a single directory named “Boot” which also includes the user-configurable subdirectories ROM1 and ROM2. Just select Emporium's option: Extract Boot Files. This extracts Emporium's Boot directory and its contents to the top directory of your SD card. After that you can copy your ROM boot images to Boot/ROM1 and Boot/ROM2 using Root Explorer or other suitable app. Copy boot.img to {path-to-SD}/Boot/ROM1 and boot-sd.img to {path-to-SD}/Boot/ROM2.
Now you can switch “live” between ROMs or boot to recovery using the appropriate command string:
Code:
sh boot-rom.sh (reboot to current ROM)
sh boot-rom.sh 1 (boot to ROM1)
sh boot-rom.sh 2 (boot to ROM2)
sh boot-rom.sh 3 (boot to Recovery)
Here is Emporium's boot-rom.sh:
Code:
#!/system/bin/sh
echo Motorola Atrix Dual Boot ROM1 emmc or ROM2 SD card
echo sendust7 @ xda developers
echo
echo Usage: sh boot-rom.sh N
echo where N = blank \(reboot to current ROM\)
echo 1 \(reboot to ROM1\)
echo 2 \(reboot to ROM2\)
echo 3 \(reboot to recovery\)
echo
echo "Home directory: $HOME"
echo
if [ $# -eq 0 ]; then
echo Rebooting to current ROM. Please wait...
sleep 3
reboot
elif [ $1 -eq 1 ]; then
if [ -f $HOME/ROM1/boot.img ]; then
cat $HOME/ROM1/boot.img > /dev/block/mmcblk0p11
echo Rebooting to ROM1. Please wait...
sleep 3
reboot
else
echo "boot.img not found. Check home directory."
exit 1
fi
elif [ $1 -eq 2 ]; then
if [ -f $HOME/ROM2/boot-sd.img ]; then
cat $HOME/ROM2/boot-sd.img > /dev/block/mmcblk0p11
echo Rebooting to ROM2. Please wait...
sleep 3
reboot
else
echo "boot-sd.img not found. Check home directory."
exit 1
fi
elif [ $1 -eq 3 ]; then
echo Rebooting to recovery. Please wait...
sleep 3
reboot recovery
else
echo "Invalid option. See Usage."
exit 1
fi
return 0
Note that boot-rom.sh is more robust than previous versions. The improved logic displays the $HOME directory and also displays an error message if it can't find ROM1/boot.img or ROM2/boot-sd.img under $HOME. If you are using Script Manager to launch boot-rom.sh, go to Settings>More>Advanced>Configuration, set Home directory to {path-to-Boot} (for example, “/storage/sdcard1/Boot” for CM10), press field at bottom to select Home directory, then select “Export $HOME” and “Browse as root”. So when you launch boot-rom.sh from Script Manager, the $HOME directory should be: {path-to-SD-card}/Boot. If not, you get an error message if you enter an argument of 1 or 2 in the command string.
Be sure to launch boot-rom.sh as root.
CM10 Notes
If you unpack any of Emporium's CM10 files named “boot-sd.img”, note that I made two small changes in ramdisk in addition to rerouting filesystem mounts:
The “init” executable was replaced with the MROM ICS init
init.olympus.rc was modified to grant elevated privileges in mkdir /storage/sdcard{0,1} per the MROM ICS init.olympus.rc
I found these two additional steps necessary to successfully boot CM10 from SD and to make apps run properly. That said, these “boot-sd.img” files should be viewed as experimental, as your mileage may differ. But no kernels were modified.
I think that porting CM10 to SD has some merit as the /system partition is easily up-sized to hold apps moved from the /data partition. Why would I make this obscure statement? Well it turns out that CM10 apps running under /system appear to have more privileges than those running under /data. I demonstrated this behavior on at least two different CM10 builds hosted on both EMMC and SD using “aLogcat” a GUI-based system logcat generator. When I launched aLogcat under /data/app, it would not display logcat to screen nor save results to a file. Then I moved it to /system/app and the problems disappeared.
Enjoy.
Troubleshooting
No wifi? Try re-flashing with Emporium since it refreshes /system/lib/modules.
Soft-brick? You may have attempted to boot a non-existent, corrupt or incompatible ROM.
Unusually fast completion of zip flash? An error has probably occurred, and you may need adb and recovery log to debug.
Disclaimer: Standard disclaimers apply.
Credits: Embedded in the zip files.
Photos and Screenshots
SmartPart FZ Before and After (in adb shell):
{
"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"
}
Emporium V3.0 Directory Structure
More on the way!

beautiful
B-e-a-u-t-i-f-u-l

Great work......I will try it. Thanks
from the (M)ATRIX...

Awesome stuff, as usual.

can you explain what exactly is this? what we will be able to do with it?

antmiu2 said:
can you explain what exactly is this? what we will be able to do with it?
Click to expand...
Click to collapse
It automates dual ROM setup and usage.

antmiu2 said:
can you explain what exactly is this? what we will be able to do with it?
Click to expand...
Click to collapse
It generates a "live" backup of your existing ROM on your SD card --- a ROM you can boot to. Then you can flash another ROM to internal memory just as you normally would.
If all goes well, you will have successfully dual booted your Atrix.
Here's the original xda article on dual booting Atrix: http://www.xda-developers.com/android/atrix-4g-dual-booting-method-for-linux-and-windows/

sendust7 said:
If you are using Script Manager to launch boot-rom.sh, go to Settings>More>Advanced>Configuration, set Home directory to {path-to-Boot} (for example, “/storage/sdcard1/Boot” for CM10), press field at bottom to select Home directory, then select “Export $HOME” and “Browse as root”. So when you launch boot-rom.sh from Script Manager, the $HOME directory should be: {path-to-SD-card}/Boot. If not, you get an error message if you enter an argument of 1 or 2 in the command string.
Click to expand...
Click to collapse
Hi sendust. Thank you very much! :good:
Managed to succesfully run TheBill's PA 299 from my sdcard (using AOKP boot.img) and restore and run a backup of a GB rom (nottachtrix based) to/from emmc.
I also managed to reboot from GB to PA299 using Script Manager by following the above quoted steps.
I can't seem to get Script Manager to run the same script from PA299 using 1 as argument to reboot into my GB rom. I did set Home directory as instructed to /storage/sdcard1/Boot but the log still says Home = / and it returns boot.img not found.
Any help would be appreciated
cheers
n1c00_

n1c00_ said:
Hi sendust. Thank you very much! :good:
Managed to succesfully run TheBill's PA 299 from my sdcard (using AOKP boot.img) and restore and run a backup of a GB rom (nottachtrix based) to/from emmc.
I also managed to reboot from GB to PA299 using Script Manager by following the above quoted steps.
I can't seem to get Script Manager to run the same script from PA299 using 1 as argument to reboot into my GB rom. I did set Home directory as instructed to /storage/sdcard1/Boot but the log still says Home = / and it returns boot.img not found.
Any help would be appreciated
cheers
n1c00_
Click to expand...
Click to collapse
Great to hear of your success!
I experienced similar behaviour with Script Manager (SM) running under /system/app. Then I moved it to /data/app and the problem went away.
If SM resides in /data/app and still doesn't work, uninstall it and download the latest version from Play Store.
Here is SM (under /data/app) in action, booting from Neutrino 2.91 (ROM1) to Liquid Smooth (ROM2) ...

sendust7 said:
Great to hear of your success!
I experienced similar behaviour with Script Manager (SM) running under /system/app. Then I moved it to /data/app and the problem went away.
If SM resides in /data/app and still doesn't work, uninstall it and download the latest version from Play Store.
Click to expand...
Click to collapse
Thanks. SM already resides in data/app and reinstalation from Store didn't help.
I realise the problem is with SM and not with the script cause it runs fine in GB
Are there any other options?
Here's what I get
Thanks a million!
n1c00_

[Deleted --- Redundant.]

n1c00_ said:
Thanks. SM already resides in data/app and reinstalation from Store didn't help.
I realise the problem is with SM and not with the script cause it runs fine in GB
Are there any other options?
Here's what I get
Thanks a million!
n1c00_
Click to expand...
Click to collapse
I would check permissions for SM. Below is what I have for CM10 Liquid Smooth (scroll down to "os.tools.scriptmanager-1.apk"). Note that the permissions match those of the other apps.
Another option would be to configure a different app like Terminal Emulator to execute boot-rom.sh as root from the Boot directory.
[email protected]:~# adb kill-server
[email protected]:~# adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:/ $ su
[email protected]:/ # cd /data/app
[email protected]:/data/app # ls -ld *.apk
-rw-r--r-- root root 5433305 2013-02-02 16:35 Magazines.apk
-rw-r--r-- root root 6160306 2013-02-02 16:35 com.android.vending-1.apk
-rw-r--r-- root root 1345436 2013-02-02 16:35 com.devuni.flashlight-2.apk
-rw-r--r-- root root 5615781 2013-02-02 16:35 com.ebay.mobile-1.apk
-rw-r--r-- root root 6284122 2013-02-01 13:50 com.google.android.apps.currents-1.apk
-rw-r--r-- root root 7232165 2013-02-01 13:50 com.google.android.apps.maps-2.apk
-rw-r--r-- root root 3591566 2013-02-01 13:50 com.google.android.gm-2.apk
-rw-r--r-- root root 4075228 2013-02-01 13:50 com.google.android.gms-1.apk
-rw-r--r-- root root 6149925 2013-02-01 13:50 com.google.android.youtube-2.apk
-rw-r--r-- root root 16600426 2013-02-02 16:35 com.instagram.android-1.apk
-rw-r--r-- root root 5787419 2013-02-02 16:35 com.keramidas.TitaniumBackup-1.apk
-rw-r--r-- root root 316047 2013-02-02 16:35 com.liveov.shotuxtrial-1.apk
-rw-r--r-- root root 7116916 2013-02-02 16:35 com.mediafire.android-1.apk
-rw-r--r-- root root 6869418 2013-02-02 16:35 com.sirma.mobile.bible.android-1.apk
-rw-r--r-- root root 853905 2013-02-02 16:35 com.socialnmobile.dictapps.notepad.color.note-1.apk
-rw-r--r-- root root 417303 2013-02-02 16:35 com.speedsoftware.rootexplorer-1.apk
-rw-r--r-- root root 1004380 2013-02-02 16:35 com.sportstracklive.stopwatch-1.apk
-rw-r--r-- root root 98247 2013-02-02 16:35 eu.chainfire.cfbench-1.apk
-rw-r--r-- root root 1020803 2013-02-02 16:35 eu.chainfire.supersu-1.apk
-rw-r--r-- root root 84111 2013-02-02 16:35 eu.kowalczuk.rsync4android-1.apk
-rw-r--r-- root root 73631 2013-02-02 16:35 fr.depoortere.android.CircleBatteryWidget-1.apk
-rw-r--r-- root root 343102 2013-02-02 16:35 jackpal.androidterm-1.apk
-rw-r--r-- root root 781592 2013-02-02 16:35 jp.sblo.pandora.jota-1.apk
-rw-r--r-- root root 492578 2013-02-02 16:35 org.cohortor.gstrings-1.apk
-rw-r--r-- root root 1193795 2013-02-02 16:35 os.tools.scriptmanager-1.apk
-rw-r--r-- root root 141061 2013-02-02 16:35 se.qzx.isoextractor-1.apk
-rw-r--r-- root root 671989 2013-02-02 16:35 spinninghead.talkingstopwatchlite-1.apk
-rw-r--r-- root root 303317 2013-02-02 16:35 uk.co.nickfines.RealCalc-1.apk
[email protected]:/data/app #

sendust7 said:
I would check permissions for SM. Below is what I have for CM10 Liquid Smooth (scroll down to "os.tools.scriptmanager-1.apk"). Note that the permissions match those of the other apps. Another option would be to configure a different app like Terminal Emulator to execute boot-rom.sh as root from the Boot directory.
Click to expand...
Click to collapse
After few hours of trial and error finally managed to get it working!
Sendust you're a star!
SM just didn't want to configure (probably) because it was installed while running rom from sd. Once I got it installed running the rom on emmc and copied emmc to sd it kept the configuration. I just had to change the argument.
Thanks and keep up the good work :good:

I dont knlw if i am the only one but its seems I cant use dualboot with ICSROM on SD and CM10 on EMMC, everything show to have been done properly but when i try to boot into ICSROM i have a black screen (no bootlogo ), and when i flashed mrom kernel on ICSROM i get the bootlogo for ever ... :crying:
Any ideas ?
PS i use bootemporium

DBSS Troubleshooting
johnannis said:
I dont knlw if i am the only one but its seems I cant use dualboot with ICSROM on SD and CM10 on EMMC, everything show to have been done properly but when i try to boot into ICSROM i have a black screen (no bootlogo ), and when i flashed mrom kernel on ICSROM i get the bootlogo for ever ... :crying:
Any ideas ?
PS i use bootemporium
Click to expand...
Click to collapse
Troubleshooting manual in work.. I will try to have something in a few hours.
[UPDATE, 05 Feb 2012 1315 PST]
I duplicated the problem on my Atrix. In fact I couldn't even get ICSROM 1.4.6 to boot from EMMC. I tried reformatting /system, /cache and /data and re-flashing. Got a fixed Big-M with fadeout, followed by a single-blink and then blank for many minutes.
Then I CWM flashed MROM boot.img using Emporium 3.0 but it hung up at the pulsating Big-M. In retrospect, I may not have waited long enough.
Then I flashed MROM ICS right over ICSROM and it booted.
Then I reflashed ICSROM 1.4.6 and rebooted. Same behavior as at the start.
Then I CWM factory reset and flashed ICSROM 1.4.3 (previous version). This time, I got pulsating Big-M for several minutes (expected due to factory reset) followed by Location Consent screen, indicating a successful boot. So ICSROM 1.4.3 appears to work.
Then I flashed Emporium's ICSROM 1.4.6 boot.img (EMMC) and rebooted. Big-M came up and then... blank --- as before.
So I reinstalled 1.4.6 ROM, factory reset, fastbooted the 1.4.3 boot image (pulled from ICSROM 1.4.3 zip file) and voila... 1.4.6 came up.
These results intimate an issue with the ICSROM 1.4.6 kernel.
Unfortunately there is not a straightforward means of obtaining kernel debug messages (dmesg >> dmesg.txt) on a failed boot: http://bootloader.wikidot.com/linux:android:kmsg
Now if you Copy-ROM ICSROM 1.4.6 to SD, you need a modified boot image. Try this one:
Link (boot-icsrom-1.4.3-sd.img): http://www.mediafire.com/?57b25z5hkid2bc2
Modified init.olympus.rc code (ramdisk):
Code:
mount ext3 /dev/block/mmcblk1p2 /system noatime nodiratime wait ro barrier=1
mount ext3 /dev/block/mmcblk1p4 /data nosuid nodev noatime nodiratime wait barrier=1
mount ext3 /dev/block/mmcblk1p3 /cache nosuid nodev noatime nodiratime wait barrier=1
[UPDATE, 05 Feb 2012 1630 PST]
OK. I may have found a problem with the stock ICSROM 1.4.6 boot.img. If you unpack it and navigate to /ramdisk/default.prop, you will notice several "read-only" settings --- ones that can only be modified in ramdisk. I made one small change: Set ro.debuggable=1 (instead of 0). Here is the modified default.prop:
Code:
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
persist.sys.usb.config=mtp
After making this one simple change, I repacked the 1.4.6 boot.img (boot-repack.img) then did the following:
Code:
Reboot to CWM
Perform factory-reset
Flash ICSROM 1.4.6
Reboot to fastboot
fastboot flash boot boot-repack.img
fastboot reboot
This time, I still got the familiar Big-M fadeout followed by the single-blink Big-M. But then 30 seconds later, the pulsating Big-M appeared, and several minutes after that, ICSROM 1.4.6 finally came up.
Link (boot-icsrom-146-emmc.img): http://www.mediafire.com/?5da1ngcny8px14w
Note: In the ICS MROM boot.img, "ro.debuggable" is already set to 1.
The short answer is that the ICS kernels are presently not stable, which is why I hesitated to include them in Atrix Boot Emporium.
Hope this helps.

what happens if i use the smart formater to my ext.sdcard and on the card are swap partitions and webtop partition? do i lose them??

Hai_Duong said:
what happens if i use the smart formater to my ext.sdcard and on the card are swap partitions and webtop partition? do i lose them??
Click to expand...
Click to collapse
I deliberated much about this and decided that for V1.0 I would stick with three (primary) ext partitions.
So yes, if you flash SmartPart FZ V1.0 and select the "Create" option, it will first do this:
Code:
echo "We first remove any existing partitions beyond the FAT32 partition..."
#echo "ENTER to continue; CNTL-Z to exit." ; read
parted /dev/block/mmcblk1 rm 4 > /dev/null 2>&1
parted /dev/block/mmcblk1 rm 3 > /dev/null 2>&1
parted /dev/block/mmcblk1 rm 2 > /dev/null 2>&1
parted /dev/block/mmcblk1 print
and then it wll create three new partitions, one each for /system, /cache and /data:
Code:
parted /dev/block/mmcblk1 mkpartfs primary ext2" $val3" "$val4"
parted /dev/block/mmcblk1 mkpartfs primary ext2" $val5" "$val6"
parted /dev/block/mmcblk1 mkpartfs primary ext2" $val7" "$val8"
where the $val parameter values are partition boundaries based on the FAT32 right-hand boundary and fixed partition sizes defined in the shell script.

sendust7 said:
I deliberated much about this and decided that for V1.0 I would stick with three (primary) ext partitions.
So yes, if you flash SmartPart FZ V1.0 and select the "Create" option, it will first do this:
Code:
echo "We first remove any existing partitions beyond the FAT32 partition..."
#echo "ENTER to continue; CNTL-Z to exit." ; read
parted /dev/block/mmcblk1 rm 4 > /dev/null 2>&1
parted /dev/block/mmcblk1 rm 3 > /dev/null 2>&1
parted /dev/block/mmcblk1 rm 2 > /dev/null 2>&1
parted /dev/block/mmcblk1 print
and then it wll create three new partitions, one each for /system, /cache and /data:
Code:
parted /dev/block/mmcblk1 mkpartfs primary ext2" $val3" "$val4"
parted /dev/block/mmcblk1 mkpartfs primary ext2" $val5" "$val6"
parted /dev/block/mmcblk1 mkpartfs primary ext2" $val7" "$val8"
where the $val parameter values are partition boundaries based on the FAT32 right-hand boundary and fixed partition sizes defined in the shell script.
Click to expand...
Click to collapse
oh thats sad. i wanted to try this because i love to test roms but i dont want to give up on my webtop partition.

Using your 1.4.3 boot.img and it still doesnt want to boot in the rom Dont know why, but after i flash the emmc with another rom it doesnt boot, before that it booted from sd
Sent from my Nexus 4 using xda app-developers app

johnannis said:
Using your 1.4.3 boot.img and it still doesnt want to boot in the rom Dont know why, but after i flash the emmc with another rom it doesnt boot, before that it booted from sd
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
OK that's good info. The file: boot-icsrom-1.4.3-sd.img was intended to boot 1.4.6 on SD. But of course it does not have the "ro.debuggable=1" fix. So when I got 1.4.6 to boot on EMMC using the fix:
Link (boot-icsrom-146-emmc.img): http://www.mediafire.com/?5da1ngcny8px14w
I realized that boot-icsrom-1.4.3-sd.img probably would not boot 1.4.6 on SD. And such was the case for me.
Did you try this:
Code:
Reboot to CWM
Perform factory-reset
Flash ICSROM 1.4.6
Reboot to fastboot
fastboot flash boot boot-icsrom-146-emmc.img
fastboot reboot
I would not be surprised if you got different results based on what the ICSROM author says...
http://forum.xda-developers.com/showthread.php?p=37561654&highlight=work#post37561654 ,
]If someone can post a link I will definitely take a look at it.
But please don't your hopes too high guys. Remember this ROM runs different on every device.
Click to expand...
Click to collapse
[UPDATE 07 Feb 2013, 0745 PST]
So I unpacked the ICSROM 1.4.6 and MROM boot images and found that the ICSROM init.olympus.rc (the device-specific script launched at boot time by the init process) is three times the size of MROM's init.olympus.rc.]. More to follow...

Cannot delete files/folders from internal memory

Hey everyone!
I recently installed the Google Pixel Launcher as a system app using Solid Explorer by installing it normally, then moving the app's folder from /data/app to /system/app and setting the folder's permissions to: Owner - Read/Write/Execute Group - Read/Execute Global - Read/Execute (755 - drwxr-xr-x) and the base.apk file to: Owner - Read/Write Group - Read Global - Read (644 -rw-r--r--) Now I can't seem to delete any files in the user internal storage space. I can however delete them if I browse there directly from /data/media/0. I imagine this is because I'm using root privileges when I navigate there directly. I'm pretty sure this is a simple permissions issue, but I honestly know little about permissions, and was only following the guide here. Can anyone give me a hand in sorting this mess out? Thanks in advance!

Let's see if I can make any sense here
First, Android is a flavor of Linux. So I'm going to talk about Linux permissions, but it applies equally to Android.
The groups (Linux term) that have access are dependant on which mount point you are accessing the internal storage from. Each directory/file has an owner and a group. Linux permissions address privileges for: owner, group, all users. The permissions for each look like: rwx. So when you look at a complete permission string it might look like:
rwxrwxrw
That's three sets of read, write, execute. If only the owner has full permissions, and the group has partial permissions, and all users have no permissions it might look like:
-rw-rw----
The very first character in that example is a "-" so I know it's not a directory. If it was a directory, the first character would be a "d". With the same permissions it would look like:
drw-rw----
Here are some examples of the same directory and file in the internal storage, but reached via different mount points. Inside a terminal app on your device, if you type "ls -al" in each of these directories, you should see something similar.
The owner and group are also indicated in a directory listing. In the first example, the owner is root and the group is sdcard_rw.
A final thing, in each example, the first line ends in a single dot "." and the second line in a double "..". The single represents the current directory you are in and the double the current directory's parent.
/storage/emulated
drwxrwx--x 50 root sdcard_rw 4096 2017-06-12 19:06 .
drwx--x--x 4 root sdcard_rw 4096 2016-06-13 19:22 ..
drwxrwx--x 6 root sdcard_rw 4096 2016-09-20 10:45 Android
-rw-rw---- 1 root sdcard_rw 629591 2017-05-27 13:17 image.jpg
Click to expand...
Click to collapse
/data/media/0
drwxrwx--- 50 media_rw media_rw 4096 2017-06-12 19:06 .
drwxrwx--- 4 media_rw media_rw 4096 2016-06-13 19:22 ..
drwxrwxr-x 6 media_rw media_rw 4096 2016-09-20 10:45 Android
-rw-rw-r-- 1 media_rw media_rw 629591 2017-05-27 13:17 image.jpg
Click to expand...
Click to collapse
/sdcard
drwxrwx--x 50 root sdcard_rw 4096 2017-06-12 19:06 .
drwx--x--x 4 root sdcard_rw 4096 2016-06-13 19:22 ..
drwxrwx--x 6 root sdcard_rw 4096 2016-09-20 10:45 Android
-rw-rw---- 1 root sdcard_rw 629591 2017-05-27 13:17 image.jpg
Click to expand...
Click to collapse
So now my question in your case is, what does a directory listing (ls -al) of /sdcard look like in your device? If it's different than my - very abbreviated - example, then you have a permissions problem.

ktmom said:
Let's see if I can make any sense here
First, Android is a flavor of Linux. So I'm going to talk about Linux permissions, but it applies equally to Android.
The groups (Linux term) that have access are dependant on which mount point you are accessing the internal storage from. Each directory/file has an owner and a group. Linux permissions address privileges for: owner, group, all users. The permissions for each look like: rwx. So when you look at a complete permission string it might look like:
rwxrwxrw
That's three sets of read, write, execute. If only the owner has full permissions, and the group has partial permissions, and all users have no permissions it might look like:
-rw-rw----
The very first character in that example is a "-" so I know it's not a directory. If it was a directory, the first character would be a "d". With the same permissions it would look like:
drw-rw----
Here are some examples of the same directory and file in the internal storage, but reached via different mount points. Inside a terminal app on your device, if you type "ls -al" in each of these directories, you should see something similar.
The owner and group are also indicated in a directory listing. In the first example, the owner is root and the group is sdcard_rw.
A final thing, in each example, the first line ends in a single dot "." and the second line in a double "..". The single represents the current directory you are in and the double the current directory's parent.
/storage/emulated
/data/media/0
/sdcard
So now my question in your case is, what does a directory listing (ls -al) of /sdcard look like in your device? If it's different than my - very abbreviated - example, then you have a permissions problem.
Click to expand...
Click to collapse
Screenshot attached.

cfhsncb said:
Screenshot attached.
Click to expand...
Click to collapse
There doesn't seem to be anything wrong there. If you can reproduce the problem, try capturing a logcat and see if it gives a clue.

ktmom said:
There doesn't seem to be anything wrong there. If you can reproduce the problem, try capturing a logcat and see if it gives a clue.
Click to expand...
Click to collapse
Yeah, I had been messing around with the permissions based on the information in your post before I took that screenshot. I think I have everything working now, and if it looks good to you, I'm just going to roll with it.

Double folders after update to latest factory image

Hello, since updating my rooted Pixel 5 to the November Image (via fastboot, flash-all.bat without -w switch) several folders in my internal storage are shown twice. The mentioned folders are in fact identical, if I create a file in one of them it also shows up in the other. After deleting a duplicated directory its twin is also gone but when I recreate it the twin gets resurrected as well.
Please see the following example (excerpt from ls -l in /data/media/0, called in an adb root shell):
Code:
drwx------ 2 u0_a250 u0_a250 3452 2020-11-08 14:31 Download
drwx------ 2 u0_a250 u0_a250 3452 2020-11-08 14:31 Download
After deleting the Download directory it looks like this:
Code:
d????????? ? ? ? ? ? Download
Any ideas how to solve this (without wiping)?
Thanks in advance.

Still nobody?