Repack CM12.1 boot.img using mkbootimg - Galaxy Note II, Galaxy S III Developer Discussion

Can someone point out what am I doing wrong? I am trying to repack boot.img, but resulting image will not boot. I built mkbootimg/unpackbootimg from source found here: https://github.com/osm0sis/mkbootimg . Then I do following:
Code:
$ mkdir boot2
$ ../unpackbootimg -i boot.img -o boot2
BOARD_KERNEL_CMDLINE androidboot.hardware=qcom user_debug=31 zcache androidboot.bootdevice=msm_sdcc.1
BOARD_KERNEL_BASE 80200000
BOARD_NAME
BOARD_PAGE_SIZE 2048
BOARD_KERNEL_OFFSET 00008000
BOARD_RAMDISK_OFFSET 01500000
BOARD_TAGS_OFFSET 00000100
This unpacks boot.img into:
Code:
$ ls -l boot2
total 7360
-rw-rw---- 1 galets galets 9 Apr 22 08:59 boot.img-base
-rw-rw---- 1 galets galets 1 Apr 22 08:59 boot.img-board
-rw-rw---- 1 galets galets 81 Apr 22 08:59 boot.img-cmdline
-rw-rw---- 1 galets galets 9 Apr 22 08:59 boot.img-kerneloff
-rw-rw---- 1 galets galets 5 Apr 22 08:59 boot.img-pagesize
-rw-rw---- 1 galets galets 663238 Apr 22 08:59 boot.img-ramdisk.gz
-rw-rw---- 1 galets galets 9 Apr 22 08:59 boot.img-ramdiskoff
-rw-rw---- 1 galets galets 9 Apr 22 08:59 boot.img-tagsoff
-rw-rw---- 1 galets galets 6842760 Apr 22 08:59 boot.img-zImage
Then I repackage files without any modification:
Code:
$ ../mkbootimg --kernel boot2/boot.img-zImage \
> --ramdisk boot2/boot.img-ramdisk.gz \
> --cmdline "androidboot.hardware=qcom user_debug=31 zcache androidboot.bootdevice=msm_sdcc.1" \
> --base 0x80200000 \
> --pagesize 2048 \
> --output boot2.img
$ ../boot_info boot2.img
Page size: 2048 (0x00000800)
Kernel size: 6842760 (0x00686988)
Ramdisk size: 663238 (0x000a1ec6)
Second size: 0 (0x00000000)
Board name:
Command line: 'androidboot.hardware=qcom user_debug=31 zcache androidboot.bootdevice=msm_sdcc.1'
Base address: 2149580800 (0x80200000)
For comparison, original boot:
Code:
$ ../boot_info boot.img
Page size: 2048 (0x00000800)
Kernel size: 6842760 (0x00686988)
Ramdisk size: 663238 (0x000a1ec6)
Second size: 0 (0x00000000)
Board name:
Command line: 'androidboot.hardware=qcom user_debug=31 zcache androidboot.bootdevice=msm_sdcc.1'
Base address: 2149580800 (0x80200000)
All seems fine. Then I flash it:
Code:
$ heimdall flash --BOOT boot2.img
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading BOOT
100%
BOOT upload successful
Ending session...
Rebooting device...
Releasing device interface...
Re-attaching kernel driver...
and piece of crap won't boot. wtf!? help!

In case anybody wonders what the issue was, check here: http://stackoverflow.com/questions/...img-using-mkbootimg-cyanogenmod-12-1-lollipop

Thank you, exactly what I needed!

Related

Help: JF1.41, Apps and Data on SD - No space error

Sorry, for creating a new thread, but the others are getting so deep reading through them, and I have seen a few others with this problem, moving /data/app and /data/data
Below is EVERYTHING I have done. Ive installed the modded JF1.41 that includes the modded mountd.conf and init.rc. Everything works.. essentially.
busybox df -h shows the proper mount as /system/sd, system/sd exists.
init.rc contains
mount ext2 /dev/mmcblk0p2 /system/sd noatime nodiratime
mountd.conf contains
block_device /dev/block/mmcblk0p1
The commands I run are
busybox cp -a /data/app /system/sd
rm -r /data/app
ln -s /system/sd/app /data/app
busybox cp -a /data/app-private /system/sd/app-private
rm -r /data/app-private
ln -s /system/sd/app-private /data/app-private
cp -a /data/data /system/sd
rm -r /data/data
ln -s /system/sd/data /data/data
reboot, and I get the error.
Ok I've narrowed it down to the data/data move.
I did it again, this time using the Batch files that were posted in the other thread(Great work!) Everything worked until I moved the /data/data..
adb shell mkdir /system/sd/data
adb shell cp -rp /data/data /system/sd
adb shell rm -r /data/data
adb shell ln -s /system/sd/data /data/data
These were the commands used. Please help
Immediately upon reversing this using
C:\Google\SDK\tools>adb shell
# rm -r /data/data
rm -r /data/data
# busybox cp -a /system/sd/data /data/data
busybox cp -a /system/sd/data /data/data
#
I was able to install applications again.
busybox df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 48.4M 0 48.4M 0% /dev
tmpfs 4.0M 0 4.0M 0% /sqlite_stmt_journals
/dev/block/mtdblock3 67.5M 64.0M 3.5M 95% /system
/dev/block/loop0 1.5M 1.5M 0 100% /system/modules
/dev/block/loop1 3.1M 3.1M 0 100% /system/xbin
/dev/mmcblk0p2 2.3G 6.8M 2.1G 0% /system/sd
/dev/block/mtdblock5 74.8M 9.9M 64.8M 13% /data
/dev/block/mtdblock4 67.5M 1.1M 66.4M 2% /cache
/dev/block/mmcblk0p1 5.2G 1.4G 3.8G 27% /sdcard
I have created a large partition, 2.3GB on an 8GB c6, so its not a space issue, I have previously formated the ext2 partition with paragon and still have the problem. When I move /data/data my phone displays 67MB free. Thats when the problems arrise.
the /data dir should look like this
#
Code:
cd /data
cd /data
# ls -l
ls -l
drwxrwxrwx 1 1000 1000 2048 Jan 25 07:23 anr
lrwxrwxrwx 1 0 0 14 Jan 25 07:35 app -> /system/sd/app
lrwxrwxrwx 1 0 0 22 Jan 25 07:36 app-private -> /system/s
d/app-private
drwxrwx--x 1 1000 1000 2048 Jan 25 21:24 dalvik-cache
lrwxrwxrwx 1 0 0 15 Jan 28 02:53 data -> /system/sd/data
drwxrwx--x 1 2000 2000 2048 Jan 25 07:23 local
drwxrwx--- 1 0 0 2048 Jan 25 07:23 lost+found
drwxrwx--t 1 1000 9998 2048 Jan 25 07:23 misc
drwx------ 1 0 0 2048 Jan 25 07:23 property
drwxrwxr-x 1 1000 1000 2048 Jan 25 07:23 system
#
/data/data dir on the sdcard should look like something like this:
Code:
# ls -l
ls -l
drwxr-xr-x 3 10028 10028 4096 Jan 25 07:36 bz.ktk.bubble
drwxr-xr-x 4 10079 10079 4096 Jan 25 08:31 com.NamcoNetworks.PacMan
drwxr-xr-x 5 10076 10076 4096 Jan 25 07:37 com.acme.android.powerma
nager
drwxr-xr-x 3 10002 10002 4096 Jan 25 07:23 com.amazon.mp3
drwxr-xr-x 4 10026 10026 4096 Jan 25 07:23 com.android.alarmclock
drwxr-xr-x 4 10032 10032 4096 Jan 25 07:36 com.android.app.schwarz
drwxr-xr-x 10 10025 10025 4096 Jan 28 04:27 com.android.browser
drwxr-xr-x 3 10024 10024 4096 Jan 25 07:23 com.android.bugreport
drwxr-xr-x 3 10023 10023 4096 Jan 25 07:23 com.android.calculator2
drwxr-xr-x 4 10022 10022 4096 Jan 25 07:23 com.android.calendar
drwxr-xr-x 3 10016 10016 4096 Jan 25 07:23 com.android.camera
drwxr-xr-x 4 10018 10018 4096 Jan 25 07:23 com.android.contacts
drwxr-xr-x 3 10072 10072 4096 Jan 25 07:37 com.android.development
drwxr-xr-x 3 10021 10021 4096 Jan 25 07:23 com.android.email
drwxr-xr-x 3 10018 10018 4096 Jan 25 07:23 com.android.googlesearch
drwxr-xr-x 3 10019 10019 4096 Jan 25 07:23 com.android.htmlviewer
drwxr-xr-x 4 10018 10018 4096 Jan 25 07:23 com.android.launcher
drwxr-xr-x 4 10015 10015 4096 Jan 25 07:23 com.android.mms
drwxr-xr-x 3 10014 10014 4096 Jan 25 07:23 com.android.music
drwxr-xr-x 4 10013 10013 4096 Jan 25 07:23 com.android.packageinsta
ller
drwxr-xr-x 4 1001 1001 4096 Jan 25 07:23 com.android.phone
drwxr-xr-x 4 10022 10022 4096 Jan 25 07:23 com.android.providers.ca
lendar
drwxr-xr-x 4 10018 10018 4096 Jan 25 07:23 com.android.providers.co
ntacts
drwxr-xr-x 4 10016 10016 4096 Jan 25 07:23 com.android.providers.do
wnloads
drwxr-xr-x 4 10016 10016 4096 Jan 25 07:23 com.android.providers.dr
m
drwxr-xr-x 4 10018 10018 4096 Jan 25 07:23 com.android.providers.im
drwxr-xr-x 4 10016 10016 4096 Jan 25 07:23 com.android.providers.me
dia
drwxr-xr-x 4 1000 1000 4096 Jan 25 07:23 com.android.providers.se
ttings
drwxr-xr-x 5 1000 1000 4096 Jan 25 07:23 com.android.providers.su
bscribedfeeds
drwxr-xr-x 4 1001 1001 4096 Jan 25 07:23 com.android.providers.te
lephony
drwxr-xr-x 5 1000 1000 4096 Jan 25 07:23 com.android.settings
drwxr-xr-x 3 10012 10012 4096 Jan 25 07:23 com.android.setupwizard
drwxr-xr-x 3 10011 10011 4096 Jan 25 07:23 com.android.soundrecorde
r
drwxr-xr-x 3 10008 10008 4096 Jan 25 07:23 com.android.sync
drwxr-xr-x 4 10001 10001 4096 Jan 25 07:23 com.android.term
drwxr-xr-x 3 10073 10073 4096 Jan 25 07:37 com.android.trystania.vo
lumecontrol
drwxr-xr-x 3 10006 10006 4096 Jan 25 07:23 com.android.updater
drwxr-xr-x 6 10005 10005 4096 Jan 28 04:26 com.android.vending
drwxr-xr-x 5 10004 10004 4096 Jan 28 14:29 com.android.voicedialer
drwxr-xr-x 3 10033 10033 4096 Jan 25 07:36 com.appdroid.anycut
drwxr-xr-x 3 10034 10034 4096 Jan 25 07:36 com.appdroid.videoplayer
drwxr-xr-x 5 10027 10027 4096 Jan 28 05:26 com.biggu.shopsavvy
drwxr-xr-x 6 10029 10029 4096 Jan 28 05:56 com.compareeverywhere
drwxr-xr-x 3 10037 10037 4096 Jan 25 07:37 com.dynamix.mobile.Smart
TacToe
drwxr-xr-x 4 10053 10053 4096 Jan 25 07:37 com.evancharlton.g1centr
al
drwxr-xr-x 4 10060 10060 4096 Jan 25 07:37 com.fsck.k9
drwxr-xr-x 4 10075 10075 4096 Jan 25 07:37 com.geekyouup.android.bo
okmarker
drwxr-xr-x 3 10000 10000 4096 Jan 25 07:23 com.google.android.apps.
gtalkservice
drwxr-xr-x 6 10017 10017 4096 Jan 25 07:23 com.google.android.apps.
maps
drwxr-xr-x 3 10038 10038 4096 Jan 25 07:37 com.google.android.apps.
uploader
drwxr-xr-x 3 10039 10039 4096 Jan 25 07:37 com.google.android.check
ers
drwxr-xr-x 3 10040 10040 4096 Jan 25 07:37 com.google.android.chess
drwxr-xr-x 6 10020 10020 4096 Jan 25 07:23 com.google.android.gm
drwxr-xr-x 4 10000 10000 4096 Jan 25 07:23 com.google.android.googl
eapps
drwxr-xr-x 4 10000 10000 4096 Jan 25 07:23 com.google.android.provi
ders.gmail
drwxr-xr-x 3 10010 10010 4096 Jan 25 07:23 com.google.android.stree
t
drwxr-xr-x 3 1000 1000 4096 Jan 25 07:23 com.google.android.syste
mupdater
drwxr-xr-x 3 10007 10007 4096 Jan 25 07:23 com.google.android.talk
drwxr-xr-x 5 10003 10003 4096 Jan 25 07:23 com.google.android.youtu
be
drwxr-xr-x 3 10041 10041 4096 Jan 25 07:37 com.google.tts
drwxr-xr-x 6 10031 10031 4096 Jan 28 05:46 com.google.zxing.client.
android
drwxr-xr-x 3 1001 1001 4096 Jan 25 07:23 com.htc.fieldtest
drwxr-xr-x 3 10043 10043 4096 Jan 25 07:37 com.ideal.speakingpad
drwxr-xr-x 6 10030 10030 4096 Jan 25 07:36 com.imeem.gynoid
drwxr-xr-x 4 10009 10009 4096 Jan 25 07:23 com.koushikdutta.superus
er
drwxr-xr-x 3 10045 10045 4096 Jan 25 07:37 com.metago.astro
drwxr-xr-x 3 10046 10046 4096 Jan 25 07:37 com.metaworldsolutions.a
ndroid.ruler
drwxr-xr-x 3 10047 10047 4096 Jan 25 07:37 com.mmg.appin
drwxr-xr-x 4 10049 10049 4096 Jan 25 07:37 com.p1.chompsms
drwxr-xr-x 5 10050 10050 4096 Jan 25 07:37 com.quirkconsulting.tick
er
drwxr-xr-x 4 10051 10051 4096 Jan 25 07:37 com.rerware.android.MyBa
ckup
drwxr-xr-x 3 10052 10052 4096 Jan 25 07:37 com.rerware.android.MyBo
okmarks
drwxr-xr-x 3 10074 10074 4096 Jan 25 07:37 com.schwimmer.andrew.tog
gleair
drwxr-xr-x 3 10054 10054 4096 Jan 25 07:37 com.schwimmer.android.to
gglebluetooth
drwxr-xr-x 3 10055 10055 4096 Jan 25 07:37 com.schwimmer.android.to
gglewifi
drwxr-xr-x 4 10057 10057 4096 Jan 25 07:37 com.skwid.systemmonitor
drwxr-xr-x 4 10058 10058 4096 Jan 25 07:37 com.starobject.android.s
tarcontact
drwxr-xr-x 6 10071 10071 4096 Jan 28 04:26 com.stylem.wallpapers
drwxr-xr-x 3 10061 10061 4096 Jan 25 07:37 com.swwomm.ringtoggle
drwxr-xr-x 3 10077 10077 4096 Jan 25 07:37 com.taskManager.rootTask
Manager
drwxr-xr-x 5 10062 10062 4096 Jan 25 07:37 com.weather.Weather
drwxr-xr-x 3 10066 10066 4096 Jan 25 07:37 koushikdutta.screenshot
drwxr-xr-x 3 10068 10068 4096 Jan 25 07:37 org.mmin.handycalc
drwxr-xr-x 3 10069 10069 4096 Jan 25 07:37 org.openintents.flashlig
ht
drwxr-xr-x 3 10070 10070 4096 Jan 25 07:37 posimotion.Tic_Tac_Toe
#
cd data
Code:
# ls -l
ls -l
drwxrwxrwx 1 1000 1000 2048 Jan 28 20:17 anr
lrwxrwxrwx 1 0 0 14 Jan 28 20:52 app -> /system/sd/app
lrwxrwxrwx 1 0 0 22 Jan 28 20:52 app-private -> /system/s
d/app-private
drwxrwx--x 1 1000 1000 2048 Jan 28 20:17 dalvik-cache
lrwxrwxrwx 1 0 0 15 Jan 28 23:33 data -> /system/sd/data
drwxrwx--x 1 2000 2000 2048 Jan 28 20:17 local
drwxrwx--- 1 0 0 2048 Jan 28 20:17 lost+found
drwxrwx--t 1 1000 9998 2048 Jan 28 20:17 misc
drwx------ 1 0 0 2048 Jan 28 20:17 property
drwxrwxr-x 1 1000 1000 2048 Jan 28 20:17 system
#
cd system/sd/data
Code:
cd ..
# cd system
cd system
# cd sd
cd sd
# cd data
cd data
# ls -l
ls -l
drwxr-xr-x 4 10034 10034 1024 Jan 28 21:22 com.acme.android.powerma
nager
drwxr-xr-x 3 10002 10002 1024 Jan 28 20:17 com.amazon.mp3
drwxr-xr-x 4 10027 10027 1024 Jan 28 20:17 com.android.alarmclock
drwxr-xr-x 10 10026 10026 1024 Jan 28 20:17 com.android.browser
drwxr-xr-x 3 10025 10025 1024 Jan 28 20:17 com.android.bugreport
drwxr-xr-x 3 10024 10024 1024 Jan 28 20:17 com.android.calculator2
drwxr-xr-x 4 10023 10023 1024 Jan 28 20:17 com.android.calendar
drwxr-xr-x 3 10017 10017 1024 Jan 28 20:17 com.android.camera
drwxr-xr-x 3 10014 10014 1024 Jan 28 20:17 com.android.contacts
drwxr-xr-x 3 10022 10022 1024 Jan 28 20:17 com.android.email
drwxr-xr-x 3 10014 10014 1024 Jan 28 20:17 com.android.googlesearch
drwxr-xr-x 3 10020 10020 1024 Jan 28 20:17 com.android.htmlviewer
drwxr-xr-x 3 10019 10019 1024 Jan 28 20:17 com.android.im
drwxr-xr-x 3 10014 10014 1024 Jan 28 20:17 com.android.launcher
drwxr-xr-x 4 10016 10016 1024 Jan 28 20:17 com.android.mms
drwxr-xr-x 3 10015 10015 1024 Jan 28 20:17 com.android.music
drwxr-xr-x 3 10013 10013 1024 Jan 28 20:17 com.android.packageinsta
ller
drwxr-xr-x 4 1001 1001 1024 Jan 28 20:17 com.android.phone
drwxr-xr-x 4 10023 10023 1024 Jan 28 20:17 com.android.providers.ca
lendar
drwxr-xr-x 4 10017 10017 1024 Jan 28 20:17 com.android.providers.do
wnloads
drwxr-xr-x 4 10017 10017 1024 Jan 28 20:17 com.android.providers.dr
m
drwxr-xr-x 4 10014 10014 1024 Jan 28 20:17 com.android.providers.im
drwxr-xr-x 3 10019 10019 1024 Jan 28 20:17 com.android.providers.im
credential
drwxr-xr-x 4 10017 10017 1024 Jan 28 20:17 com.android.providers.me
dia
drwxr-xr-x 4 1000 1000 1024 Jan 28 20:17 com.android.providers.se
ttings
drwxr-xr-x 5 1000 1000 1024 Jan 28 20:17 com.android.providers.su
bscribedfeeds
drwxr-xr-x 4 1001 1001 1024 Jan 28 20:17 com.android.providers.te
lephony
drwxr-xr-x 5 1000 1000 1024 Jan 28 20:17 com.android.settings
drwxr-xr-x 3 10012 10012 1024 Jan 28 20:17 com.android.setupwizard
drwxr-xr-x 3 10011 10011 1024 Jan 28 20:17 com.android.soundrecorde
r
drwxr-xr-x 3 10008 10008 1024 Jan 28 20:17 com.android.sync
drwxr-xr-x 3 10001 10001 1024 Jan 28 20:17 com.android.term
drwxr-xr-x 3 10006 10006 1024 Jan 28 20:17 com.android.updater
drwxr-xr-x 5 10005 10005 1024 Jan 28 20:17 com.android.vending
drwxr-xr-x 3 10004 10004 1024 Jan 28 20:17 com.android.voicedialer
drwxr-xr-x 3 10037 10037 1024 Jan 28 21:09 com.angryredplanet.andro
id.rings_extended
drwxr-xr-x 3 10030 10030 1024 Jan 28 21:04 com.appdroid.anycut
drwxr-xr-x 5 10035 10035 1024 Jan 28 21:22 com.aws.android
drwxr-xr-x 3 10031 10031 1024 Jan 28 21:08 com.biggu.shopsavvy
drwxr-xr-x 3 10036 10036 1024 Jan 28 21:09 com.bonfiremedia.android
_ebay
drwxr-xr-x 3 10000 10000 1024 Jan 28 20:17 com.google.android.apps.
gtalkservice
drwxr-xr-x 3 10018 10018 1024 Jan 28 20:17 com.google.android.apps.
maps
drwxr-xr-x 6 10021 10021 1024 Jan 28 20:17 com.google.android.gm
drwxr-xr-x 4 10000 10000 1024 Jan 28 20:17 com.google.android.googl
eapps
drwxr-xr-x 4 10000 10000 1024 Jan 28 20:17 com.google.android.provi
ders.gmail
drwxr-xr-x 3 10039 10039 1024 Jan 28 21:10 com.google.android.radar
drwxr-xr-x 3 10010 10010 1024 Jan 28 20:17 com.google.android.stree
t
drwxr-xr-x 3 10007 10007 1024 Jan 28 20:17 com.google.android.talk
drwxr-xr-x 3 10003 10003 1024 Jan 28 20:17 com.google.android.youtu
be
drwxr-xr-x 3 10038 10038 1024 Jan 28 21:09 com.google.tts
drwxr-xr-x 3 1001 1001 1024 Jan 28 20:17 com.htc.fieldtest
drwxr-xr-x 3 10009 10009 1024 Jan 28 20:17 com.koushikdutta.superus
er
drwxr-xr-x 3 10029 10029 1024 Jan 28 20:58 com.myspace.android
drwxr-xr-x 3 10032 10032 1024 Jan 28 21:08 com.ringdroid
drwxr-xr-x 3 10033 10033 1024 Jan 28 21:08 com.shazam.android
drwxr-xr-x 5 10014 10014 1024 Jan 28 20:17 com.tmobile.myfaves
drwxr-xr-x 5 10028 10028 1024 Jan 28 20:27 com.weather.Weather
#
Looks right, not sure why I'm getting the error, as I am using the Data2ext2.bat which as stated above contains
Code:
adb shell mkdir /system/sd/data
adb shell cp -rp /data/data /system/sd
adb shell rm -r /data/data
adb shell ln -s /system/sd/data /data/data
Have rebooted afterwards with and without the USB cable attached to the computer.
Thanks so much for any help!
Has anyone else encountered the insuffecient space problem after the /data/data move that has found a fix for it?
I am also using rc30 mod(1.41) not ADP1.
forceshield said:
Has anyone else encountered the insuffecient space problem after the /data/data move that has found a fix for it?
I am also using rc30 mod(1.41) not ADP1.
Click to expand...
Click to collapse
i did before but i only moved apk files at that time... i reinstalled jf41.. now also you using the old command to move data/data ... see the updated thread will fix your issues with foreclosing and possibly the low space..
I've had the same issue as well. I downloaded an application from a site OTA and had the "low disk space" issue. I could download to pc and put the application on the SD card manually and that works fine.

[GUIDE] Unpack/repack ext4 Android system images

I didn't find any good info for modifying and creating ext4 sparsed images so i decided to share
This is for all who wants to unpack and modify the original system.img that you can flash using recovery.
system.img (what you get from the google factory images for example) represents a sparsed ext4 loop mounted file system.
It is mounted into /system of your device. Note that this tutorial is for ext4 file system, you may have system image which is yaffs2 for example.
the way it is mounted on Galaxy Nexus:
"/dev/block/platform/omap/omap_hsmmc.0/by-name/system /system ext4 ro,relatime,barrier=1,data=ordered 0 0"
Prerequisites:
1. Linux box or virtual machine
2. simg2img, make_ext4fs binaries which can be downloaded from here http://web.djodjo.org/?a=download:android:tools:x86_linux:ext4tools
Procedure:
place you system.img and the 2 binaries in one directory, and make sure the binaries have exec permission.
Part 1 - mount the filesystem
1. mkdir sys
2. ./simg2img system.img sys.raw
3. sudo mount -t ext4 -o loop sys.raw sys/
Then you have all your system partition mouned in 'sys' and you can modify whatever you want in 'sys'. For example de-odex apks and framework jars.
Part 2 - create a new flashable system image.
1. sudo ./make_ext4fs -s -l 512M -a system new.img sys/
2. sudo umount sys
3. rm -fr sys
Now you can simply type:
fastboot flash system new.img
enjoy
Hey thanks for the guide .
I tried to make use of you command to make the .img but I get this error
Code:
[email protected]:~/ext4_utils$ sudo ./make_ext4fs -s -l 512M -a system new.img ~/system/
[sudo] password for vijai:
Creating filesystem with parameters:
Size: 536870912
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 2048
Label:
Blocks: 131072
Block groups: 4
Reserved block group size: 31
error: do_inode_allocate_extents: Failed to allocate 134 blocks
for what is that 512m ?
This is the same problem...
any idea?
vijai2011 said:
Hey thanks for the guide .
I tried to make use of you command to make the .img but I get this error
Code:
[email protected]:~/ext4_utils$ sudo ./make_ext4fs -s -l 512M -a system new.img ~/system/
[sudo] password for vijai:
Creating filesystem with parameters:
Size: 536870912
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 2048
Label:
Blocks: 131072
Block groups: 4
Reserved block group size: 31
error: do_inode_allocate_extents: Failed to allocate 134 blocks
Click to expand...
Click to collapse
TiBiSMART said:
This is the same problem...
any idea?
Click to expand...
Click to collapse
This is the solution for sgs3:
./make_ext4fs -s -l 1610612736 -a system new_system.img sys/
You need to use the correct size for your new system image.
Use tune2fs -l sys.raw and "Block count" * "Block size" for make_ext4fs -s parameter.
You can also use "cat /proc/partitions" and your device to find out the correct size
Note: If your Samsung Device does not support fastboot, you can use heimdall instead.
Tom
You can just get the size of the original sys.raw and create the new image the same size. You can create the new image whatever size you like that can fit the files you put in but have to bear in mind not to ovrflow the dedicated partition size by the system as it wont be mounted correctly. For example if you create 1gb system for Galaxy Nexus it will be fine and flashed but it will not boot.
RealBorg said:
You need to use the correct size for your new system image.
Use tune2fs -l sys.raw and "Block count" * "Block size" for make_ext4fs -s parameter.
You can also use "cat /proc/partitions" and your device to find out the correct size
Note: If your Samsung Device does not support fastboot, you can use heimdall instead.
Tom
Click to expand...
Click to collapse
after mounting i cant modify and cant unmount it
after mounting the sys i cant write maybe there is no root permission and i cant unmout also and tell me one more thing when i use the fastboot flash command its says command not found. please help me, i have mtk .img files
Good time of the day for everyone. Finnaly I found what I need. I need to make an image of the system of the Kindle Fire. I have problem with my KF. It can be seen only from Fastboot. It was absolutly dead. Now partitions mounted and even its boot till Kindle Fire (white and yellow). All I've done in the terminal of the TWRP. But to finish I need to make system.img and flash it in Fastboot. As I understood I need Linux, I prepare USB disk right now that to install. Then as wrote:
------------------------------------------------------------------------
1. Linux box or virtual machine
2. make_ext4fs binary which can be downloaded from here http://andwise.net/?attachment_id=406
Procedure:
Create a new flashable system image.
1. sudo ./make_ext4fs -s -l 512M -a system new.img sys/
2. sudo umount sys
3. rm -fr sys
Now you can simply type:
fastboot flash system new.img
----------------------------------------------------------------------------------------------
So, I rebooting my Windows to install Linux
thanks .
Waiting for any solution
thanks .
Recheck
thinh182009 said:
This is the same problem...
Click to expand...
Click to collapse
make sure that your calculation is correct(block size*number of blocks)
otherwise ur system image might be large
try to do (number of blocks+number of blocks failed to be allocated)*(block size)
@ my english is not good. sorry
Big thankssssss:good:
---------- Post added at 03:22 PM ---------- Previous post was at 02:32 PM ----------
thinh182009 said:
You can tell me how? I use the phone S7562i size?
@ my english is not good. sorry
Big thankssssss:good:
---------- Post added at 03:22 PM ---------- Previous post was at 02:32 PM ----------
Thank, Thank many to have successfully, wait to close package tar and uprom
Click to expand...
Click to collapse
the image should be enough to contain the new data but it do not make it lager than the size of img.raw.
make: ls -l img.raw get the size and use it instead of 512M
thanks you.....................
[email protected]:/ $ export PATH=/data/local/bin:$PATH
[email protected]:/ $ su
[email protected]:/ # cat proc/partitions
major minor #blocks name
7 0 14585 loop0
7 1 4190 loop1
179 0 15388672 mmcblk0
179 1 61440 mmcblk0p1
179 2 128 mmcblk0p2
179 3 256 mmcblk0p3
179 4 512 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 512 mmcblk0p6
179 7 10240 mmcblk0p7
179 8 512 mmcblk0p8
179 9 512 mmcblk0p9
179 10 10240 mmcblk0p10
179 11 13952 mmcblk0p11
179 12 3072 mmcblk0p12
179 13 3072 mmcblk0p13
179 14 1536000 mmcblk0p14
179 15 12832768 mmcblk0p15
179 16 8192 mmcblk0p16
179 17 860160 mmcblk0p17
179 18 10240 mmcblk0p18
179 19 10240 mmcblk0p19
179 20 6144 mmcblk0p20
179 21 3072 mmcblk0p21
179 22 8 mmcblk0p22
179 23 5120 mmcblk0p23
179 64 2048 mmcblk0boot1
179 32 2048 mmcblk0boot0
179 96 30702592 mmcblk1
179 97 30698496 mmcblk1p1
254 0 14584 dm-0
254 1 4189 dm-1
[email protected]:/ #
This is the output of running # cat proc/partition. The number before mmc**** is the block size. My system is mmcblk0p15. So my system needs to be that size.
Sent from my SPH-L710 using xda app-developers app
thanks .
You won't be able to use any of the methods that I know.
Sent from my SPH-L710 using xda app-developers app
thanks .

Internal memory screwed up

Hallo guys,
got a little problem with my phone
it crashed while restoring an backup, now internal memory seems to be messed up.
1. Download Mode is working (flashed StockRom and Broodrom rc5)
2. I can reboot to recovery (I can flash other recovery, from internal sdcard, mounting USB works)
3. Mounting /system /data -> Recovery crashes
4. Factroy Reset does not work
3. When i try to flash a rom.zip it seems that only kernel is changed.
4. Factory Reset is not working
5. I can connect with adb
Perhaps you can have a look on the following outputs
fdisk -l
Code:
~ # ←[6nfdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0
~ # ←[6nfdisk -l /dev/block/mmcblk0p1
fdisk -l /dev/block/mmcblk0p1
fdisk: can't open '/dev/block/mmcblk0p1': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p2
fdisk -l /dev/block/mmcblk0p2
fdisk: can't open '/dev/block/mmcblk0p2': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p3
fdisk -l /dev/block/mmcblk0p3
fdisk: can't open '/dev/block/mmcblk0p3': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p4
fdisk -l /dev/block/mmcblk0p4
fdisk: can't open '/dev/block/mmcblk0p4': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p5
fdisk -l /dev/block/mmcblk0p5
fdisk: can't open '/dev/block/mmcblk0p5': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p6
fdisk -l /dev/block/mmcblk0p6
fdisk: can't open '/dev/block/mmcblk0p6': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p7
fdisk -l /dev/block/mmcblk0p7
fdisk: can't open '/dev/block/mmcblk0p7': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p8
fdisk -l /dev/block/mmcblk0p8
fdisk: can't open '/dev/block/mmcblk0p8': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p9
fdisk -l /dev/block/mmcblk0p9
fdisk: can't open '/dev/block/mmcblk0p9': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p10
fdisk -l /dev/block/mmcblk0p10
fdisk: can't open '/dev/block/mmcblk0p10': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p11
fdisk -l /dev/block/mmcblk0p11
fdisk: can't open '/dev/block/mmcblk0p11': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p12
fdisk -l /dev/block/mmcblk0p12
fdisk: can't open '/dev/block/mmcblk0p12': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p13
fdisk -l /dev/block/mmcblk0p13
fdisk: can't open '/dev/block/mmcblk0p13': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p14
fdisk -l /dev/block/mmcblk0p14
fdisk: can't open '/dev/block/mmcblk0p14': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p15
fdisk -l /dev/block/mmcblk0p15
fdisk: can't open '/dev/block/mmcblk0p15': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p16
fdisk -l /dev/block/mmcblk0p16
Disk /dev/block/mmcblk0p16: 104 MB, 104857600 bytes
4 heads, 16 sectors/track, 3200 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p16 doesn't contain a valid partition table
~ # ←[6nfdisk -l /dev/block/mmcblk0p17
fdisk -l /dev/block/mmcblk0p17
fdisk: can't open '/dev/block/mmcblk0p17': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p18
fdisk -l /dev/block/mmcblk0p18
fdisk: can't open '/dev/block/mmcblk0p18': I/O error
mounting /data in recovery:
Code:
I:Actual block device: '/dev/block/mmcblk0p17', current file system: 'ext4'
E:Unable to mount '/data'
Same error on all recoverys CWM / TWRP
Perhaps someone can give an advice
Try formatting system, data and cache then install broodROM RC5 again, it might work.
Did you use the correct recovery while changing roms? you need to use cwm 5.0.0.4 atleast
Flash recovery through ODIN...
Sent from my GT-I9001 using Tapatalk 2
broodplank1337 said:
Try formatting system, data and cache then install broodROM RC5 again, it might work.
Did you use the correct recovery while changing roms? you need to use cwm 5.0.0.4 atleast
Click to expand...
Click to collapse
How can i format data with adb?
I used CWM 6.0.2.7
recovery stucks always at formating data... until i kill by pressing power button
In recovery all functions where mounting /data is not needed are working.
Works
format system
format cache
wipe android secur
Fails
mount data
wipe dalvik
fix permissions
buffo1987 said:
Hallo guys,
got a little problem with my phone
it crashed while restoring an backup, now internal memory seems to be messed up.
1. Download Mode is working (flashed StockRom and Broodrom rc5)
2. I can reboot to recovery (I can flash other recovery, from internal sdcard, mounting USB works)
3. Mounting /system /data -> Recovery crashes
4. Factroy Reset does not work
3. When i try to flash a rom.zip it seems that only kernel is changed.
4. Factory Reset is not working
5. I can connect with adb
Perhaps you can have a look on the following outputs
fdisk -l
Code:
~ # ←[6nfdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0
~ # ←[6nfdisk -l /dev/block/mmcblk0p1
fdisk -l /dev/block/mmcblk0p1
fdisk: can't open '/dev/block/mmcblk0p1': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p2
fdisk -l /dev/block/mmcblk0p2
fdisk: can't open '/dev/block/mmcblk0p2': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p3
fdisk -l /dev/block/mmcblk0p3
fdisk: can't open '/dev/block/mmcblk0p3': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p4
fdisk -l /dev/block/mmcblk0p4
fdisk: can't open '/dev/block/mmcblk0p4': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p5
fdisk -l /dev/block/mmcblk0p5
fdisk: can't open '/dev/block/mmcblk0p5': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p6
fdisk -l /dev/block/mmcblk0p6
fdisk: can't open '/dev/block/mmcblk0p6': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p7
fdisk -l /dev/block/mmcblk0p7
fdisk: can't open '/dev/block/mmcblk0p7': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p8
fdisk -l /dev/block/mmcblk0p8
fdisk: can't open '/dev/block/mmcblk0p8': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p9
fdisk -l /dev/block/mmcblk0p9
fdisk: can't open '/dev/block/mmcblk0p9': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p10
fdisk -l /dev/block/mmcblk0p10
fdisk: can't open '/dev/block/mmcblk0p10': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p11
fdisk -l /dev/block/mmcblk0p11
fdisk: can't open '/dev/block/mmcblk0p11': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p12
fdisk -l /dev/block/mmcblk0p12
fdisk: can't open '/dev/block/mmcblk0p12': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p13
fdisk -l /dev/block/mmcblk0p13
fdisk: can't open '/dev/block/mmcblk0p13': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p14
fdisk -l /dev/block/mmcblk0p14
fdisk: can't open '/dev/block/mmcblk0p14': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p15
fdisk -l /dev/block/mmcblk0p15
fdisk: can't open '/dev/block/mmcblk0p15': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p16
fdisk -l /dev/block/mmcblk0p16
Disk /dev/block/mmcblk0p16: 104 MB, 104857600 bytes
4 heads, 16 sectors/track, 3200 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p16 doesn't contain a valid partition table
~ # ←[6nfdisk -l /dev/block/mmcblk0p17
fdisk -l /dev/block/mmcblk0p17
fdisk: can't open '/dev/block/mmcblk0p17': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p18
fdisk -l /dev/block/mmcblk0p18
fdisk: can't open '/dev/block/mmcblk0p18': I/O error
Perhaps someone can give an advice
Click to expand...
Click to collapse
did you use TWRP recovery ??
zikozoko said:
did you use TWRP recovery ??
Click to expand...
Click to collapse
cwm 6.0.2.7
Now i tried several recoverys TWRP and CWM but they are all working same without /data
flased broodrom rc5 again, stuck on boot. Can not factory reset, /data still not mountabel
I think your solution must be this:
You need to flash an empty data.img.ext4 to your phone using odin, I did it once, and it succeeded! But you first need to make it:
busybox dd if=/dev/zero of=/sdcard/data.img.ext4 bs=1M count=1024
1gb empty data.img.ext4 file, which can be flashed to restore the paritition
pack the file for odin:
tar -c data.img.ext4 > fix.tar
md5sum -t fix.tar >> fix.tar
mv fix.tar fix.tar.md5
So you either need cygwin or a native linux shell.
Or u can flash a stock rom via Odin and after booting install another recovery (ex 5.5.0.4 the most stable for me) and another costum rom.
VEREY IMPORTANT make sure u have the right AriesVE.ops. Try to download from SamMobile.
broodplank1337 said:
I think your solution must be this:
You need to flash an empty data.img.ext4 to your phone using odin, I did it once, and it succeeded! But you first need to make it:
busybox dd if=/dev/zero of=/sdcard/data.img.ext4 bs=1M count=1024
1gb empty data.img.ext4 file, which can be flashed to restore the paritition
pack the file for odin:
tar -c data.img.ext4 > fix.tar
md5sum -t fix.tar >> fix.tar
mv fix.tar fix.tar.md5
So you either need cygwin or a native linux shell.
Click to expand...
Click to collapse
Looks quite interesting.
I#m not sure what i have to do:
connect phone to ubuntu vm
Terminal:
Code:
$ adb busybox dd if=/dev/zero of=/sdcard/data.img.ext4 bs=1M count=1024
$ cd /sdcard/
$ tar -c data.img.ext4 > fix.tar
$ md5sum -t fix.tar >> fix.tar
$ mv fix.tar fix.tar.md5
2. Flash fix.tar.md5 as one package with odin
right?
broodplank1337 said:
I think your solution must be this:
You need to flash an empty data.img.ext4 to your phone using odin, I did it once, and it succeeded! But you first need to make it:
busybox dd if=/dev/zero of=/sdcard/data.img.ext4 bs=1M count=1024
1gb empty data.img.ext4 file, which can be flashed to restore the paritition
pack the file for odin:
tar -c data.img.ext4 > fix.tar
md5sum -t fix.tar >> fix.tar
mv fix.tar fix.tar.md5
So you either need cygwin or a native linux shell.
Click to expand...
Click to collapse
Hi , TNX
What about this script should run on recovery :
Code:
cat /dev/zero > /dev/block/mmcblk0pX
Code:
[email protected]:~$ adb shell
~ # busybox dd if=/dev/zero of=/sdcard/data.img.ext4 bs=1M count=1024
phone crashes -> data.img.ext4 is only 661 MB
will retry...
I think you did not meant me to do this on the phone.
Code:
[email protected]:~$ cd resc/
[email protected]:~/resc$ busybox dd if=/dev/zero of=^Cata.img.ext4 bs=1M count=1024
[email protected]:~/resc$ busybox dd if=/dev/zero of=data.img.ext4 bs=1M count=1024
1024+0 records in
1024+0 records out
[email protected]:~/resc$ tar -c data.img.ext4 > fix.tar
[email protected]:~/resc$ md5sum -t fix.tar >> fix.tar
[email protected]:~/resc$ mv fix.tar fix.tar.md5
I got the file now
Odin
Code:
Check MD5 FileName...
MD5 File Name : fix.tar
Open File Name : fix.tar
Check MD5 ...
Tail MD5 : 5654164EA05D41668D50F97731E2EB5A
Image MD5 : 5654164EA05D41668D50F97731E2EB5A
Check MD5 ... ok
<1> Added!!!
<1> Detected!!!
Download Start...
<0> Create File...
<1> StartThread Detected : 1
<2> StartThread Detected : 0
<3> StartThread Detected : 0
<4> StartThread Detected : 0
<5> StartThread Detected : 0
<6> StartThread Detected : 0
<7> StartThread Detected : 0
<8> StartThread Detected : 0
<1> setup connection...
<1> odin mode.. check plcatform verification.
<1> VerifyPlatform:V0, P0,R0
<1> START!!!
<1> e - unknown file - "data.img.ext4"
<1> set download environment.
<1> reset pda..
<0> Started Timer
<1> Close serial port and wait until rebooting.
Problem still exits
buffo1987 said:
Hallo guys,
got a little problem with my phone
it crashed while restoring an backup, now internal memory seems to be messed up.
1. Download Mode is working (flashed StockRom and Broodrom rc5)
2. I can reboot to recovery (I can flash other recovery, from internal sdcard, mounting USB works)
3. Mounting /system /data -> Recovery crashes
4. Factroy Reset does not work
3. When i try to flash a rom.zip it seems that only kernel is changed.
4. Factory Reset is not working
5. I can connect with adb
Perhaps you can have a look on the following outputs
fdisk -l
mounting /data in recovery:
Code:
I:Actual block device: '/dev/block/mmcblk0p17', current file system: 'ext4'
E:Unable to mount '/data'
Same error on all recoverys CWM / TWRP
Perhaps someone can give an advice
Click to expand...
Click to collapse
Hey Buffo,
I have the same problem after trying your test-versions. I could "revive" all partitions but data by downgrading recovery to 5.5.04 and formating system and cache then. But also data could not be formatted via 5.5.04 so I also will try broods proposal...
btw. this does not work to solve it.
Code:
cat /dev/zero > /dev/block/mmcblk0pX
magicw said:
Hey Buffo,
I have the same problem after trying your test-versions. I could "revive" all partitions but data by downgrading recovery to 5.5.04 and formating system and cache then. But also data could not be formatted via 5.5.04 so I also will try broods proposal...
btw. this does not work to solve it.
Code:
cat /dev/zero > /dev/block/mmcblk0pX
Click to expand...
Click to collapse
Sad to here that,
removed all cwm 6.0.2.7 downloads from my post.
At least flashing a stock rom makes the phone look untouched, so i will send it for repair...
I already tried to format data with adb: mke2fs -L data -b 4096 -m 0 -F /dev/block/mmcblk0p17, but also just works with /system + /cache
When exactly did it happen for you?
hey here i found something
i do not know if it helps but read it and decide it looks like your problem in a way
for another device but maybe helpful
http://forum.cyanogenmod.org/topic/6433-solved-messed-up-partitions-on-internal-storage/
krislibaeer said:
hey here i found something
i do not know if it helps but read it and decide it looks like your problem in a way
for another device but maybe helpful
http://forum.cyanogenmod.org/topic/6433-solved-messed-up-partitions-on-internal-storage/
Click to expand...
Click to collapse
interesting. I've run parted via adb and mmcblk0p17 shows 1447 MB - shouldn't this be 1024 MB only?
magicw said:
interesting. I've run parted via adb and mmcblk0p17 shows 1447 MB - shouldn't this be 1024 MB only?
Click to expand...
Click to collapse
Code:
179 0 7755776 mmcblk0
179 1 106495 mmcblk0p1 //secboot2 partition map
179 2 500 mmcblk0p2 //dbl (boot loader)
179 3 3596 mmcblk0p3 //osbl (boot loader)
179 4 1 mmcblk0p4 //mbr extended partition table
179 5 5120 mmcblk0p5 //emmcboot (boot loader, download mode)
179 6 20000 mmcblk0p6 //amss
179 7 3072 mmcblk0p7 //emmcparam
179 8 5120 mmcblk0p8 //boot
179 9 7000 mmcblk0p9 //adsp
179 10 3072 mmcblk0p10 //rmt
179 11 3072 mmcblk0p11 //rmt
179 12 8192 mmcblk0p12 //persist
179 13 7680 mmcblk0p13 //recovery
179 14 5120 mmcblk0p14 //param
179 15 532480 mmcblk0p15 //system
179 16 102400 mmcblk0p16 //cache
179 17 1413120 mmcblk0p17 //data
179 18 204800 mmcblk0p18 //preload
179 19 500 mmcblk0p19 // These
179 20 3596 mmcblk0p20 // partitions
179 21 5120 mmcblk0p21 // are
179 22 20000 mmcblk0p22 // either
179 23 5120 mmcblk0p23 // empty
179 24 7000 mmcblk0p24 // or
179 25 5120 mmcblk0p25 // backup
179 26 5120 mmcblk0p26 // partitions
179 27 5120 mmcblk0p27 //efs
179 28 5228544 mmcblk0p28 //internal sdcard
Xistance said:
Code:
# cat /proc/partitions
major minor #blocks name
179 0 3864576 mmcblk0
179 1 106495 mmcblk0p1 //secboot2 partition map
179 2 500 mmcblk0p2 //dbl (boot loader)
179 3 3596 mmcblk0p3 //osbl (boot loader)
179 4 1 mmcblk0p4 //mbr extended partition table
179 5 5120 mmcblk0p5 //emmcboot (boot loader, download mode)
179 6 20000 mmcblk0p6 //amss
179 7 3072 mmcblk0p7 //emmcparam
179 8 5632 mmcblk0p8 //boot
179 9 6488 mmcblk0p9 //adsp
179 10 3072 mmcblk0p10 //rmt
179 11 3072 mmcblk0p11 //rmt
179 12 8192 mmcblk0p12 //persist
179 13 7680 mmcblk0p13 //recovery
179 14 5120 mmcblk0p14 //param
179 15 547840 mmcblk0p15 //system
179 16 61440 mmcblk0p16 //cache
179 17 1136640 mmcblk0p17 //data
179 18 51200 mmcblk0p18 //preload
179 19 500 mmcblk0p19
179 20 3596 mmcblk0p20
179 21 5120 mmcblk0p21
179 22 20000 mmcblk0p22
179 23 5120 mmcblk0p23
179 24 7000 mmcblk0p24
179 25 5120 mmcblk0p25
179 26 5120 mmcblk0p26
179 27 5120 mmcblk0p27 //efs
179 28 1787904 mmcblk0p28 //internal sdcard
Click to expand...
Click to collapse
wtf your internal sdcard is 4gb? (if you look at the total blocks)
check my output with 8gb internal
Code:
cat proc/partitions
major minor #blocks name
179 0 7755776 mmcblk0
179 1 106495 mmcblk0p1
179 2 500 mmcblk0p2
179 3 3596 mmcblk0p3
179 4 1 mmcblk0p4
179 5 5120 mmcblk0p5
179 6 20000 mmcblk0p6
179 7 3072 mmcblk0p7
179 8 5120 mmcblk0p8
179 9 7000 mmcblk0p9
179 10 3072 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 8192 mmcblk0p12
179 13 7680 mmcblk0p13
179 14 5120 mmcblk0p14
179 15 532480 mmcblk0p15
179 16 102400 mmcblk0p16
179 17 1413120 mmcblk0p17
179 18 204800 mmcblk0p18
179 19 500 mmcblk0p19
179 20 3596 mmcblk0p20
179 21 5120 mmcblk0p21
179 22 20000 mmcblk0p22
179 23 5120 mmcblk0p23
179 24 7000 mmcblk0p24
179 25 5120 mmcblk0p25
179 26 5120 mmcblk0p26
179 27 5120 mmcblk0p27
179 28 5228544 mmcblk0p28
broodplank1337 said:
wtf your internal sdcard is 4gb? (if you look at the total blocks)
check my output with 8gb internal
Code:
cat proc/partitions
major minor #blocks name
179 0 7755776 mmcblk0
179 1 106495 mmcblk0p1
179 2 500 mmcblk0p2
179 3 3596 mmcblk0p3
179 4 1 mmcblk0p4
179 5 5120 mmcblk0p5
179 6 20000 mmcblk0p6
179 7 3072 mmcblk0p7
179 8 5120 mmcblk0p8
179 9 7000 mmcblk0p9
179 10 3072 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 8192 mmcblk0p12
179 13 7680 mmcblk0p13
179 14 5120 mmcblk0p14
179 15 532480 mmcblk0p15
179 16 102400 mmcblk0p16
179 17 1413120 mmcblk0p17
179 18 204800 mmcblk0p18
179 19 500 mmcblk0p19
179 20 3596 mmcblk0p20
179 21 5120 mmcblk0p21
179 22 20000 mmcblk0p22
179 23 5120 mmcblk0p23
179 24 7000 mmcblk0p24
179 25 5120 mmcblk0p25
179 26 5120 mmcblk0p26
179 27 5120 mmcblk0p27
179 28 5228544 mmcblk0p28
Click to expand...
Click to collapse
Oh yeah sorry. I took it from arco on his Galaxy W and forgot they had different sizes =.=.
Edit : Fixed ^^
Code:
(parted) check
check
check
Error: Can't have a partition outside the disk!
Code:
major minor #blocks name
179 0 [COLOR="Red"]7552000 [/COLOR]mmcblk0
179 1 106495 mmcblk0p1
179 2 500 mmcblk0p2
179 3 3596 mmcblk0p3
179 4 1 mmcblk0p4
179 5 5120 mmcblk0p5
179 6 20000 mmcblk0p6
179 7 3072 mmcblk0p7
179 8 5120 mmcblk0p8
179 9 7000 mmcblk0p9
179 10 3072 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 8192 mmcblk0p12
179 13 7680 mmcblk0p13
179 14 5120 mmcblk0p14
179 15 532480 mmcblk0p15
179 16 102400 mmcblk0p16
179 17 1413120 mmcblk0p17
179 18 204800 mmcblk0p18
179 19 500 mmcblk0p19
179 20 3596 mmcblk0p20
179 21 5120 mmcblk0p21
179 22 20000 mmcblk0p22
179 23 5120 mmcblk0p23
179 24 7000 mmcblk0p24
179 25 5120 mmcblk0p25
179 26 5120 mmcblk0p26
179 27 5120 mmcblk0p27
179 28 [COLOR="Red"]5024768 [/COLOR]mmcblk0p28
buffo1987 said:
Code:
(parted) check
check
check
Error: Can't have a partition outside the disk!
Code:
major minor #blocks name
179 0 [COLOR="Red"]7552000 [/COLOR]mmcblk0
179 1 106495 mmcblk0p1
179 2 500 mmcblk0p2
179 3 3596 mmcblk0p3
179 4 1 mmcblk0p4
179 5 5120 mmcblk0p5
179 6 20000 mmcblk0p6
179 7 3072 mmcblk0p7
179 8 5120 mmcblk0p8
179 9 7000 mmcblk0p9
179 10 3072 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 8192 mmcblk0p12
179 13 7680 mmcblk0p13
179 14 5120 mmcblk0p14
179 15 532480 mmcblk0p15
179 16 102400 mmcblk0p16
179 17 1413120 mmcblk0p17
179 18 204800 mmcblk0p18
179 19 500 mmcblk0p19
179 20 3596 mmcblk0p20
179 21 5120 mmcblk0p21
179 22 20000 mmcblk0p22
179 23 5120 mmcblk0p23
179 24 7000 mmcblk0p24
179 25 5120 mmcblk0p25
179 26 5120 mmcblk0p26
179 27 5120 mmcblk0p27
179 28 [COLOR="Red"]5024768 [/COLOR]mmcblk0p28
Click to expand...
Click to collapse
the partition has a shift of 203776 (both have same size )
that is weird

[Q] ln command dont work on a directory with write permissions

Hi there,
I'm working with a stock, non rooted, lollipop 5.0.2 for xt1032 Moto G ROM, I'm trying to create a symbolic link from "popcorn download" folder to "my downloads" folder, so other programs can take the movies for streaming or whatever (who cares why anyways) but even when a touch or rm command works fine, ln commands doesn't like to lend a hand.
bad boy LN, bad boy.
Here is an exerpt on what i did:
1|[email protected]_umts:/sdcard/Download $ pwd
/sdcard/Download
[email protected]_umts:/sdcard/Download $ ls -l /sdcard/time4popcorn/downloads
drwxrwx--- 3 root 1028 4096 Apr 25 02:29 3980d0dd-29a9-4711-9a83-7955661b1aef
drwxrwx--- 3 root 1028 4096 Apr 25 02:34 3f02c279-84bb-4d74-bb69-2a7959a23774
drwxrwx--- 2 root 1028 4096 Apr 25 02:31 50548bf9-6cf6-436b-9b80-179ec8fc8bca
drwxrwx--- 3 root 1028 4096 Apr 25 02:00 c20989ae-375b-46e0-aa6e-d373c0bf2659
[email protected]_umts:/sdcard/Download $ touch popcorn
[email protected]_umts:/sdcard/Download $ ls -l
-rw-rw---- 1 root 1028 457290 Apr 24 22:29 422.pdf
drwxrwx--- 2 root 1028 4096 Apr 19 04:17 BigBang Theory
drwxrwx--- 2 root 1028 4096 Apr 19 04:12 Super_Mario_Theme
-rw-rw---- 1 root 1028 0 Apr 25 18:00 popcorn
[email protected]_umts:/sdcard/Download $ rm popcorn
[email protected]_umts:/sdcard/Download $ ln -s /sdcard/time4popcorn/downloads popcorn
ln: popcorn: Operation not permitted
1|[email protected]_umts:/sdcard/Download $ whoami
app_135
[email protected]_umts:/sdcard/Download $ id
uid=10135(app_135) gid=10135(app_135) groups=1015(sdcard_rw),1028,3003(inet),9997,50135(app_40135)
[email protected]_umts:/sdcard/Download $
I hope you can trhow some light to me and help me out
.
Thanks in advance, and kind regards to everyone! :highfive:
Gnokix

Need help with R765L gear s3 frontier

Hi,
I bought gear s3 LTE from korea model is SM-R765L ,,It is tied to LG U+ operator,,I am not able to Use samsung pay in india,,Is there any firmware which I can flash in my watch to make samsung pay work in india???,,Pls help
Oh, wow.
I have not known about SM-R765L.
But similar problem IMHO like with all the other devices from this family/group.
NO Firmware available for netOdin.
Code:
SM-R765(S)
SM-R765A
SM-R765T
SM-R765F
SM-R765V
SM-R765N
Few Firmware leaked... but ALL are obsolete.
Be carefully! Not try to experiment. Otherwise you have similar problem like these users:
https://forum.xda-developers.com/gear-s3/help/sm-r765f-teardown-t3659431
https://forum.xda-developers.com/gear-s3/help/please-help-bricked-gear-s3-sm-r765s-t3665558
unsolved... :crying:
But can you give us please Firmware info on device?
Code:
*#1234#
This Code shows Firmware Version on device.
Please post Photo or write all 3 infos...
Code:
AP
CP
CSC
Thanx in advance.
Best Regards
Now I remember why I not know SM-R765L...
Because it is like SM-R765S... only as SM-R765 in Bootloader...
Product Name in Download Mode should be like this:
https://forum.xda-developers.com/showpost.php?p=73607036&postcount=1
Code:
SM-R765
Latest Firmware is still:
Code:
R765KOU2BQHA/R765OKA2BQHA/R765KOU2BQB6
I have only 2 files from this Firmware:
https://forum.xda-developers.com/showpost.php?p=73796534&postcount=8
Nowhere SM-R765 Firmware leaked...
But I need your help.
Please.
I need infos about partition. :angel:
Can you please check partition infos with SDB Tool?
Code:
ls -l /dev/disk/by-partlabel
ls -l /dev/disk/by-label
cat /proc/partitions
Please post result.
If you need help with SDB Tool... write here or contact me via PM.
Please, these infos are very important for me.
Thanx in advance.
Best Regards
AP:; R765KOU2BQHA
CP : R765KOU2BQB6
CSC : R765OKA2BQHA
I dont know how to use sdb
If you have time... :angel:
SDB is here + some instruction how to connect over WiFi:
https://forum.xda-developers.com/showpost.php?p=74585286&postcount=330
After connection over your IP address...
Then simple enter:
Code:
sdb shell
You should see something like this:
Code:
[B]sh-3.2$[/B]
Then possible to Copy & Paste these 3 Commands:
Code:
ls -l /dev/disk/by-partlabel
Code:
ls -l /dev/disk/by-label
Code:
cat /proc/partitions
With right Mouse Button... you can mark text... for copy and paste.
Example of output:
Code:
sh-3.2$ ls -l /dev/disk/by-label
total 0
lrwxrwxrwx 1 root root 16 Dec 11 06:35 modules -> ../../mmcblk0p10
lrwxrwxrwx 1 root root 10 Dec 11 06:35 ramdisk -> ../../ram0
lrwxrwxrwx 1 root root 15 Dec 11 06:35 ramdisk-recovery -> ../../mmcblk0p4
lrwxrwxrwx 1 root root 16 Dec 11 06:35 rootfs -> ../../mmcblk0p15
lrwxrwxrwx 1 root root 16 Dec 11 06:35 tizen -> ../../mmcblk0p14
Thank you.
Only if time...
But I have since monthS nobody with SM-R765 from Korea...
Best Regards
C:\Users\rages\Downloads\SDBstarterKidv1\sdb_2.2.60_windows\data\tools>sdb shell
sh-3.2$ ls -l /dev/disk/by-partlabel
ls: cannot access /dev/disk/by-partlabel/csc: Permission denied
ls: cannot access /dev/disk/by-partlabel/steady: Permission denied
ls: cannot access /dev/disk/by-partlabel/recovery: Permission denied
ls: cannot access /dev/disk/by-partlabel/radio: Permission denied
ls: cannot access /dev/disk/by-partlabel/rootfs: Permission denied
ls: cannot access /dev/disk/by-partlabel/csa: Permission denied
ls: cannot access /dev/disk/by-partlabel/cm: Permission denied
ls: cannot access /dev/disk/by-partlabel/ramdisk1: Permission denied
ls: cannot access /dev/disk/by-partlabel/boot: Permission denied
ls: cannot access /dev/disk/by-partlabel/system-data: Permission denied
ls: cannot access /dev/disk/by-partlabel/ramdisk2: Permission denied
ls: cannot access /dev/disk/by-partlabel/cpnvcore: Permission denied
ls: cannot access /dev/disk/by-partlabel/module: Permission denied
ls: cannot access /dev/disk/by-partlabel/tup: Permission denied
total 0
l????????? ? ? ? ? ? boot
l????????? ? ? ? ? ? cm
l????????? ? ? ? ? ? cpnvcore
l????????? ? ? ? ? ? csa
l????????? ? ? ? ? ? csc
l????????? ? ? ? ? ? module
lrwxrwxrwx 1 root root 15 Dec 15 00:00 param -> ../../mmcblk0p6
l????????? ? ? ? ? ? radio
l????????? ? ? ? ? ? ramdisk1
l????????? ? ? ? ? ? ramdisk2
l????????? ? ? ? ? ? recovery
l????????? ? ? ? ? ? rootfs
l????????? ? ? ? ? ? steady
l????????? ? ? ? ? ? system-data
l????????? ? ? ? ? ? tup
lrwxrwxrwx 1 root root 16 Dec 12 18:31 user -> ../../mmcblk0p14
sh-3.2$ ls -l /dev/disk/by-label
ls: cannot access /dev/disk/by-label/ramdisk: Permission denied
ls: cannot access /dev/disk/by-label/rootfs: Permission denied
ls: cannot access /dev/disk/by-label/ramdisk-recovery: Permission denied
ls: cannot access /dev/disk/by-label/modules: Permission denied
total 0
l????????? ? ? ? ? ? modules
l????????? ? ? ? ? ? ramdisk
l????????? ? ? ? ? ? ramdisk-recovery
l????????? ? ? ? ? ? rootfs
lrwxrwxrwx 1 root root 16 Dec 12 18:31 tizen -> ../../mmcblk0p14
sh-3.2$ 
sh-3.2$ -l /dev/disk/by-[[email protected]label
sh-3.2$ 
sh-3.2$
sh-3.2$ ls -l /dev/disk/by-partlabel
ls: cannot access /dev/disk/by-partlabel/csc: Permission denied
ls: cannot access /dev/disk/by-partlabel/steady: Permission denied
ls: cannot access /dev/disk/by-partlabel/recovery: Permission denied
ls: cannot access /dev/disk/by-partlabel/radio: Permission denied
ls: cannot access /dev/disk/by-partlabel/rootfs: Permission denied
ls: cannot access /dev/disk/by-partlabel/csa: Permission denied
ls: cannot access /dev/disk/by-partlabel/cm: Permission denied
ls: cannot access /dev/disk/by-partlabel/ramdisk1: Permission denied
ls: cannot access /dev/disk/by-partlabel/boot: Permission denied
ls: cannot access /dev/disk/by-partlabel/system-data: Permission denied
ls: cannot access /dev/disk/by-partlabel/ramdisk2: Permission denied
ls: cannot access /dev/disk/by-partlabel/cpnvcore: Permission denied
ls: cannot access /dev/disk/by-partlabel/module: Permission denied
ls: cannot access /dev/disk/by-partlabel/tup: Permission denied
total 0
l????????? ? ? ? ? ? boot
l????????? ? ? ? ? ? cm
l????????? ? ? ? ? ? cpnvcore
l????????? ? ? ? ? ? csa
l????????? ? ? ? ? ? csc
l????????? ? ? ? ? ? module
lrwxrwxrwx 1 root root 15 Dec 15 00:00 param -> ../../mmcblk0p6
l????????? ? ? ? ? ? radio
l????????? ? ? ? ? ? ramdisk1
l????????? ? ? ? ? ? ramdisk2
l????????? ? ? ? ? ? recovery
l????????? ? ? ? ? ? rootfs
l????????? ? ? ? ? ? steady
l????????? ? ? ? ? ? system-data
l????????? ? ? ? ? ? tup
lrwxrwxrwx 1 root root 16 Dec 12 18:31 user -> ../../mmcblk0p14
sh-3.2$ ls -l /dev/disk/by-label
ls: cannot access /dev/disk/by-label/ramdisk: Permission denied
ls: cannot access /dev/disk/by-label/rootfs: Permission denied
ls: cannot access /dev/disk/by-label/ramdisk-recovery: Permission denied
ls: cannot access /dev/disk/by-label/modules: Permission denied
total 0
l????????? ? ? ? ? ? modules
l????????? ? ? ? ? ? ramdisk
l????????? ? ? ? ? ? ramdisk-recovery
l????????? ? ? ? ? ? rootfs
lrwxrwxrwx 1 root root 16 Dec 12 18:31 tizen -> ../../mmcblk0p14
sh-3.2$ cat /proc/partitions
major minor #blocks name
7 0 45300 loop0
254 0 310192 zram0
179 0 3817472 mmcblk0
179 1 32768 mmcblk0p1
179 2 8192 mmcblk0p2
179 3 2048 mmcblk0p3
179 4 20480 mmcblk0p4
179 5 8192 mmcblk0p5
179 6 8192 mmcblk0p6
179 7 3072 mmcblk0p7
259 0 16384 mmcblk0p8
259 1 16384 mmcblk0p9
259 2 16384 mmcblk0p10
259 3 65536 mmcblk0p11
259 4 194560 mmcblk0p12
259 5 161792 mmcblk0p13
259 6 1920000 mmcblk0p14
259 7 1337344 mmcblk0p15
259 8 256 mmcblk0p16
179 24 512 mmcblk0rpmb
179 16 4096 mmcblk0boot1
179 8 4096 mmcblk0boot0
253 0 1337344 dm-0
sh-3.2$
:good:
Thank you very much.
This helps me alot.
SM-R765L seems stronger secured...
Here is from SM-R765A from ATT:
Code:
sh-3.2$ cat /proc/partitions
major minor #blocks name
7 0 44216 loop0
254 0 310184 zram0
179 0 3817472 mmcblk0
179 1 32768 mmcblk0p1
179 2 8192 mmcblk0p2
179 3 2048 mmcblk0p3
179 4 20480 mmcblk0p4
179 5 8192 mmcblk0p5
179 6 8192 mmcblk0p6
179 7 3072 mmcblk0p7
259 0 16384 mmcblk0p8
259 1 16384 mmcblk0p9
259 2 16384 mmcblk0p10
259 3 65536 mmcblk0p11
259 4 194560 mmcblk0p12
259 5 161792 mmcblk0p13
259 6 1920000 mmcblk0p14
259 7 1337344 mmcblk0p15
259 8 256 mmcblk0p16
179 24 512 mmcblk0rpmb
179 16 4096 mmcblk0boot1
179 8 4096 mmcblk0boot0
253 0 1280000 dm-0
Code:
sh-3.2$ ls -l /dev/disk/by-partlabel
total 0
lrwxrwxrwx 1 root root 15 Dec 10 17:22 boot -> ../../mmcblk0p8
lrwxrwxrwx 1 root root 15 Dec 10 17:22 cm -> ../../mmcblk0p7
lrwxrwxrwx 1 root root 15 Dec 10 17:22 cpnvcore -> ../../mmcblk0p3
lrwxrwxrwx 1 root root 15 Dec 10 17:22 csa -> ../../mmcblk0p2
lrwxrwxrwx 1 root root 16 Dec 10 17:22 csc -> ../../mmcblk0p12
lrwxrwxrwx 1 root root 16 Dec 10 17:22 module -> ../../mmcblk0p10
lrwxrwxrwx 1 root root 15 Dec 10 17:23 param -> ../../mmcblk0p6
lrwxrwxrwx 1 root root 16 Dec 10 17:22 radio -> ../../mmcblk0p11
lrwxrwxrwx 1 root root 15 Dec 10 17:22 ramdisk1 -> ../../mmcblk0p5
lrwxrwxrwx 1 root root 15 Dec 10 17:22 ramdisk2 -> ../../mmcblk0p4
lrwxrwxrwx 1 root root 15 Dec 10 17:22 recovery -> ../../mmcblk0p9
lrwxrwxrwx 1 root root 16 Dec 10 17:22 rootfs -> ../../mmcblk0p15
lrwxrwxrwx 1 root root 16 Dec 10 17:22 steady -> ../../mmcblk0p16
lrwxrwxrwx 1 root root 16 Dec 10 17:22 system-data -> ../../mmcblk0p13
lrwxrwxrwx 1 root root 15 Dec 10 17:22 tup -> ../../mmcblk0p1
lrwxrwxrwx 1 root root 16 Dec 10 17:22 user -> ../../mmcblk0p14
Code:
sh-3.2$ ls -l /dev/disk/by-label
total 0
lrwxrwxrwx 1 root root 16 Dec 11 06:35 modules -> ../../mmcblk0p10
lrwxrwxrwx 1 root root 10 Dec 11 06:35 ramdisk -> ../../ram0
lrwxrwxrwx 1 root root 15 Dec 11 06:35 ramdisk-recovery -> ../../mmcblk0p4
lrwxrwxrwx 1 root root 16 Dec 11 06:35 rootfs -> ../../mmcblk0p15
lrwxrwxrwx 1 root root 16 Dec 11 06:35 tizen -> ../../mmcblk0p14
I would guess... this is "similar" partition layout...
I will send you PM about 1 idea Samsung Pay related...
Please wait...
Best Regards
@rageshkr2699
Please I need your help.
This is 1 way to dump PIT partition.pit from alive Gear S2 and S3:
https://forum.xda-developers.com/showpost.php?p=75571582&postcount=455
Over WiFi from alive Gear...
Maybe you can help us.
As we have still no Firmware nor PIT partition.pit from Korean SM-R765...
Best Regards
I have the same watch. I was wondering if someone could help me change the embedded sim information so i may replace the embedded one with another one please

Categories

Resources