In the works? Sure carrier branding is a step redded child. But at least others and myself might be more adventurous if we had backups and a stock firm
I can hope right
Sent from my DROID BIONIC using Tapatalk
Finding very little info myself. Patience is virtue I guess.
Sent from my SCH-I815 using xda premium
I don't really have the extra time to devote to developing for this tablet, but if someone builds CWM for it, that might be what I need to crank out a custom kernel for it. =)
geeknik said:
I don't really have the extra time to devote to developing for this tablet, but if someone builds CWM for it, that might be what I need to crank out a custom kernel for it. =)
Click to expand...
Click to collapse
that'd be cool. I want to look more into messaging.apk, framework, and small things. been timid without cwm backups. I already made a fc cycle issue when playing with the telephony service - thank you for adb.
So, just gotta sit back and wait calmly
Sent from my SCH-I815 using Tapatalk 2
geeknik said:
I don't really have the extra time to devote to developing for this tablet, but if someone builds CWM for it, that might be what I need to crank out a custom kernel for it. =)
Click to expand...
Click to collapse
Man that would be awesome. I'll start praying now for CWM.
The main thing that is preventing me from making a CWM for your device is that I don't know the partition layout. If I had that, it wouldn't take too much work to make one. Also, getting my WIP CM port working (obviously with only partial hardware support, which is the case for the P68x0 as well) on the i815 shouldn't be too bad either. They way I've set stuff up, most changes go in a common repository that is shared by 4 devices (the P68x0 and the P62x0), which the i815 would also inherit from.
Currently I don't really have the time to work on an additional device, but if someone who is familiar with deving is interested in working on the i815, feel free to PM me.
how can I find the partition layout of the device?
Sent from my ADR6425LVW using Tapatalk 2
To help gague interest, I would certainly like this to happen.
Sent from my SCH-I815 using XDA Premium HD app
If someone would like to open a terminal emulator and type in the following:
cat /proc/partitions
Copy and paste the output here
I'll get it in a few hours off mine and would be for helping others test. On work time atm
Sent from my DROID BIONIC using Tapatalk
if nobody beats me to it, ill do this tonight when I get home from work.
Sent from my ADR6425LVW using Tapatalk 2
nitroglycerine33 said:
If someone would like to open a terminal emulator and type in the following:
cat /proc/partitions
Copy and paste the output here
Click to expand...
Click to collapse
Code:
$ cat /proc/partitions
major minor #blocks name
179 0 15388672 mmcblk0
179 1 20480 mmcblk0p1
179 2 1280 mmcblk0p2
179 3 1280 mmcblk0p3
179 4 8192 mmcblk0p4
179 5 8192 mmcblk0p5
179 6 8192 mmcblk0p6
179 7 409600 mmcblk0p7
179 8 16384 mmcblk0p8
179 9 851968 mmcblk0p9
179 10 13492224 mmcblk0p10
179 11 561152 mmcblk0p11
179 16 31166976 mmcblk1
179 17 31162880 mmcblk1p1
Hope this is what you need
Beat me to it...
PLEASE develop CWM for this device. I can't believe it isn't more popular. It is perfect in every respect I can think of. I just wish I could find a decent otterbox-type case. Thanks again! I would gladly donate to the cause.
Can you grab this for me as well:
cat /proc/mounts
Usually the partitions command brings up an alias but I guess not on the gtab. This last one should tell me that partitions.
Here's mine
$ export PATH=/data/local/bin:$PATH
$ cat /proc/mounts
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p9 /system ext4 ro,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p10 /data ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p7 /cache ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p1 /efs ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p11 /preinstall ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p4 /mnt/.lfs j4fs rw,relatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/fuse /mnt/sdcard fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
tmpfs /mnt/sdcard/extStorages tmpfs ro,relatime,mode=755,gid=1000 0 0
/dev/block/vold/179:17 /mnt/sdcard/extStorages/SdCard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1023,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
$
Thank you VERY MUCH! I can also get you a dump from Mobile Odin Pro if that would help?
-Rob
if anybody can do it it is definitely Nitro
I have a terminal emulator installed and both rooted and supersu. ES File Manager as well. Ask away!!!
I too, will gladly make a donation for this dev.
You guys actually have the same partitions as the 6800. If there is a recovery out there for odin that does not include a kernel (recovery.bin) the 6800 should work just fine for you. If there isn't one out there that is just the recovery I will see if I can get something done today or tomorrow for you.
The only thing is you would have to boot into recovery right away after flashing and I can create a zip for you to flash that would remove system/etc/install-recovery.sh. Otherwise it will pull the stock recovery from the boot.img and override clockworkmod.
The other option would be to include recovery with a kernel that you can flash with odin.
Next Step
Nitro,
Thank you VERY much. Let me know how or what I can do to move this forward. I am eager to get it going.
Thanks,
-Rob
Related
After hours reading tons of posts I got my ADP1 (Android Developer Phone1) rooted. My current setup is
Phone: ADP1 G1 | 32B | HTC Dream
Rom: COS-DS (http://forum.xda-developers.com/showthread.php?t=950765)
Recovery: Amon RA-Dream-v1.7.0 (http://forum.xda-developers.com/showthread.php?t=566669)
Radio: 2.22.28.25 (http://forum.xda-developers.com/showthread.php?t=831139)
SPL: 1.33.0013d (http://forum.xda-developers.com/showthread.php?t=831139)
microSD: 96MB swap + 512MB ext4 + FAT32
Code:
~ # free
total used free shared buffers
Mem: 112616 110680 1936 0 604
Swap: 23548 20476 3072
Total: 136164 131156 5008
# cat /proc/partitions
major minor #blocks name
7 0 668 loop0
7 1 4508 loop1
7 2 1760 loop2
31 0 256 mtdblock0
31 1 5120 mtdblock1
31 2 2560 mtdblock2
31 3 93184 mtdblock3
31 4 27648 mtdblock4
31 5 93952 mtdblock5
253 0 23552 zram0
179 0 992000 mmcblk0
179 1 398437 mmcblk0p1
179 2 500000 mmcblk0p2
179 3 93562 mmcblk0p3
~ # mount
rootfs on / type rootfs (ro,relatime)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/mtdblock3 on /system type yaffs2 (ro,relatime)
/dev/block/mtdblock5 on /data type yaffs2 (rw,nosuid,nodev,relatime)
/dev/block/mtdblock4 on /cache type yaffs2 (rw,nosuid,nodev,relatime)
/dev/block/loop0 on /system/lib/modules type squashfs (ro,relatime)
/dev/block/loop1 on /system/fonts type squashfs (ro,relatime)
/dev/block/loop2 on /system/xbin type squashfs (ro,relatime)
/dev/block/vold/179:2 on /sd-ext type ext4 (rw,nodev,noatime,nodiratime,barrier=1,data=ordered,noauto_da_alloc)
/dev/block/vold/179:1 on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/vold/179:1 on /mnt/secure/asec type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
tmpfs on /mnt/sdcard/.android_secure type tmpfs (ro,relatime,size=0k,mode=000)
I would like to know if there is any optimization?
Why should I do the customMTD? (http://forum.xda-developers.com/showthread.php?p=7061471#post7061471)
I'm not using ClockworksMOD as described by COS-DS. Should I? (http://forum.xda-developers.com/showthread.php?t=950765)
My partition order is different as described by COS-DS. Does it matter?
Using customMTD you could assign your cache memory (around 27MB) as internal memory.
Clockwork, I don't like much, but this is my personal opinion. Advantage(?) of Clockwork: you can flash unsigned zip files.
Partition layout probably matters, because on system startup there is a chance, that they are not mounted.
Sent from my Gingerbread on Dream using XDA App
I found customMTD to be difficult to install (I did it with firerat's Magpie ROM), but worth it for the extra space it gave me. Prior to, I was getting low on disk space messages and random shutdowns galore.
I don't recall why, but during my research I recall learning that Amon-Ra is stable and Clockwork isn't if you're going to use customMTD.
Please if someone have, upload your backedup mmcblk0_start with partition configuration data from mmcblk0p8, my tablet has only 7 partitions although My flash.cfg makes 8 partitions and last one is mmcblk0p8 with size FFFF... But after flashing it I get always same thing- when i boot into ubuntu and check my partitions I get only last one mmcblk0p7 who is data, so I can't flash second boot image and make dualboot+recovery. On picasso.init.rc i get just some words and digits, so I can not do anything with it, I tryed all EUU's, but get the same. So please if you can, upload it, if it wery hard then jus system.img it will be better than nothing. Thanks and sorry for bad English.
There is no such partition. It is only defined this way in nvflash flash.cfg but whole space is taken by the user data parition, which takes as much space as it can get (depending on emmc size) and this last one is not actually created.
yaworski said:
There is no such partition. It is only defined this way in nvflash flash.cfg but whole space is taken by the user data parition, which takes as much space as it can get (depending on emmc size) and this last one is not actually created.
Click to expand...
Click to collapse
So what I need to do that I can flash second boot image, and why mmcblk0p7 in nvflash .cfg is about just 7 or more megabytes? And http://projects.pappkartong.se/a500/ do you read it, in that table is write 8 partitions and mmcblk0p8 is data, then it is strange. Thanks for reply. Sorry for bad english.
Tautvaldas said:
Please if someone have, upload your backedup mmcblk0_start with partition configuration data from mmcblk0p8, my tablet has only 7 partitions although My flash.cfg makes 8 partitions and last one is mmcblk0p8 with size FFFF... But after flashing it I get always same thing- when i boot into ubuntu and check my partitions I get only last one mmcblk0p7 who is data, so I can't flash second boot image and make dualboot+recovery. On picasso.init.rc i get just some words and digits, so I can not do anything with it, I tryed all EUU's, but get the same. So please if you can, upload it, if it wery hard then jus system.img it will be better than nothing. Thanks and sorry for bad English.
Click to expand...
Click to collapse
If you don't have a mmcblk0p8 I would be interested to see what /proc/partitions and /proc/mounts looks like.
With mmcblk0p8:
Code:
$ cat /proc/partitions
major minor #blocks name
179 0 31259648 mmcblk0
179 1 5120 mmcblk0p1
179 2 8192 mmcblk0p2
179 3 614400 mmcblk0p3
179 4 1253376 mmcblk0p4
179 5 4096 mmcblk0p5
179 6 102400 mmcblk0p6
179 7 10240 mmcblk0p7
179 8 29253632 mmcblk0p8
$
$ cat /proc/mounts
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p3 /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p8 /data ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p4 /cache ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p6 /system/vendor ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/fuse /mnt/sdcard fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
$
The partition table parsed from raw dump of /dev/block/mmcblk:
Code:
nvtegrapart: #0 [BCT ] start=0 size=6144 (6)
nvtegrapart: #1 [PT ] start=2048 size=1024 (1)
nvtegrapart: #2 [EBT ] start=3072 size=8192 (8)
nvtegrapart: #3 [GP1 ] start=11264 size=2048 (2)
nvtegrapart: #4 [SOS ] start=13312 size=10240 (10)
nvtegrapart: #5 [LNX ] start=23552 size=16384 (16)
nvtegrapart: #6 [APP ] start=39936 size=1228800 (1200)
nvtegrapart: #7 [CAC ] start=1268736 size=2506752 (2448)
nvtegrapart: #8 [MSC ] start=3775488 size=8192 (8)
nvtegrapart: #9 [FLX ] start=3783680 size=204800 (200)
nvtegrapart: #10 [AKB ] start=3988480 size=20480 (20)
nvtegrapart: #11 [UDA ] start=4008960 size=58507264 (57136)
nvtegrapart: #12 [GPT ] start=62516224 size=1024 (1)
Try the thread called rollback from ics leak, it has a rooted 3.2 image so uh, good luck with that
Sent from my A501 using xda app-developers app
Wery strange now, I got mmcblk0p8, but when I flash second boot image then my data is gone (can't boot into tegraowners 170 ROM) it says that can't use data partition and need data reset, after that it is same thing again. In root 3.2.1 is same as EUUs, same,.cfg, maybe I'm doing something wrong. Sorry for bad english. Now I have a501 stock ROM in my a500 and I will try flash second boot again. And thanks for replies.
Taks for help, it seems working now, maybe I should check what ROM I am using next time thanks. Sorry for bad english.
Haha i don't know who your referring to but uh if it worked , your welcome
Sent from my A501 using xda app-developers app
*EDIT - Since 5.5 of available storage is normal for an 8 GB, please note that I had a 16 GB*
I only have 5.5 GB of TOTAL storage. No clue where the other GB's went. This happened at some point today, perhaps after flashing the latest CM nightly.
First I restored a b/u, no luck, fixed permissions, etc... nothing worked. I then reflashed all the stock img's via fastboot, wiped everything, etc... but still no luck. I'm assuming the mounting point was broken somehow? Flashed the factory images did not fix.
Code:
[email protected]:/ $ mount
mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/secure tmpfs rw,relatime,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,nosuid,nodev,noatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,nosuid,nodev,noatime,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,nosuid,nodev,relatime,nodelalloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware vfat ro,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,sho
rtname=mixed,errors=remount-ro 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
Someone had this problem the other day. Try this, http://forum.xda-developers.com/showpost.php?p=34906845&postcount=71
Sent from my Nexus 7 using xda premium
El Daddy said:
Someone had this problem the other day. Try this, http://forum.xda-developers.com/showpost.php?p=34906845&postcount=71
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thanks, I didn't fastboot erase anything, lets hope this is the ticket. Thankfully I have a very recent adb b/u of all my data.
El Daddy said:
Someone had this problem the other day. Try this, http://forum.xda-developers.com/showpost.php?p=34906845&postcount=71
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Boom, done, thanks. All is well now. I didn't realize -w formatted the partitions as well.
No problem. Glad it worked!
Sent from my Nexus 7 using xda premium
El Daddy said:
No problem. Glad it worked!
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
12.92 GB of available storage sound about right?
Edit: 16 GB = 12.92 free
8 GB = 5.67 free
Thanks again for the lead.
I'm have the 8GB but that sounds right to me
Sent from my Nexus 7 using xda premium
Hi can anyone dump the recovery.img off thier galaxy s3mini. Im going to try and make a cwm but need this .img. i think its easier for people that a rooted there phones. Thanks in advance
Sent from my GT-I9300 using xda premium
you can get it sinply by extract recovery.img from the firmware.
avicohh said:
you can get it sinply by extract recovery.img from the firmware.
Click to expand...
Click to collapse
Its not in the firmware unfortunately
Sent from my GT-I9300 using xda premium
No it isn't. I already tried and failed.
Maybe we can extract it through ADB SHELL.
Currently i get:
$ cat /proc/mounts
cat /proc/mounts
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /dev/shm tmpfs rw,relatime,mode=755,gid=1000 0 0
none /debug debugfs rw,relatime 0 0
/dev/block/mmcblk0p22 /system ext4 ro,noatime,errors=panic,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p12 /modemfs ext4 rw,nosuid,nodev,noatime,errors=panic,barrier=1,journal_async_commit,data=ordered 0 0
/dev/block/mmcblk0p23 /cache ext4 rw,nosuid,nodev,noatime,errors=panic,barrier=1,journal_async_commit,data=ordered 0 0
/dev/block/mmcblk0p11 /efs ext4 rw,nosuid,nodev,noatime,errors=panic,barrier=1,journal_async_commit,data=ordered 0 0
/dev/block/mmcblk0p24 /preload ext4 ro,noatime,errors=panic,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p25 /data ext4 rw,nosuid,nodev,noatime,errors=panic,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard 0 0
/dev/block/mmcblk0p19 /mnt/.lfs j4fs rw,relatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
$
But which one is the recovery ???
Try modem.
quendil said:
Maybe we can extract it through ADB SHELL.
Currently i get:
$ cat /proc/mounts
cat /proc/mounts
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /dev/shm tmpfs rw,relatime,mode=755,gid=1000 0 0
none /debug debugfs rw,relatime 0 0
/dev/block/mmcblk0p22 /system ext4 ro,noatime,errors=panic,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p12 /modemfs ext4 rw,nosuid,nodev,noatime,errors=panic,barrier=1,journal_async_commit,data=ordered 0 0
/dev/block/mmcblk0p23 /cache ext4 rw,nosuid,nodev,noatime,errors=panic,barrier=1,journal_async_commit,data=ordered 0 0
/dev/block/mmcblk0p11 /efs ext4 rw,nosuid,nodev,noatime,errors=panic,barrier=1,journal_async_commit,data=ordered 0 0
/dev/block/mmcblk0p24 /preload ext4 ro,noatime,errors=panic,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p25 /data ext4 rw,nosuid,nodev,noatime,errors=panic,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard 0 0
/dev/block/mmcblk0p19 /mnt/.lfs j4fs rw,relatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
$
But which one is the recovery ???
Click to expand...
Click to collapse
Lol i dont have a clue. Could you try downloading this tool http://forum.xda-developers.com/showthread.php?t=1703488 its for normal galaxy s3. When installed click any firmware version and then select option to make nandroid backup through adb to computer. You need to have root to do it. Thanks again
Sent from my GT-I9300 using xda premium
I don't think recovery partition is mounted in normal boot. Try adb in recovery mode?
Skickat från min GT-P7500 via Tapatalk 2
---------- Post added at 01:30 PM ---------- Previous post was at 12:50 PM ----------
In terminal, cat /proc/partition gives me:
$ export PATH=/data/local/bin:$PATH
$ su
# cat /proc/partitions
major minor #blocks name
7 0 14585 loop0
7 1 2111 loop1
7 2 4190 loop2
7 3 5229 loop3
7 4 47849 loop4
7 5 2111 loop5
7 6 4190 loop6
7 7 13545 loop7
179 0 7634944 mmcblk0
179 1 128 mmcblk0p1
179 2 384 mmcblk0p2
179 3 1024 mmcblk0p3
179 4 1024 mmcblk0p4
179 5 512 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 512 mmcblk0p8
179 9 1024 mmcblk0p9
179 10 1024 mmcblk0p10
179 11 16384 mmcblk0p11
179 12 16384 mmcblk0p12
179 13 16384 mmcblk0p13
179 14 51200 mmcblk0p14
179 15 64 mmcblk0p15
179 16 14336 mmcblk0p16
179 17 2048 mmcblk0p17
179 18 2048 mmcblk0p18
179 19 16384 mmcblk0p19
179 20 16384 mmcblk0p20
179 21 16384 mmcblk0p21
179 22 1228800 mmcblk0p22
179 23 860160 mmcblk0p23
179 24 327680 mmcblk0p24
179 25 4945920 mmcblk0p25
179 64 2048 mmcblk0boot1
179 32 2048 mmcblk0boot0
179 96 32113664 mmcblk1
179 97 16056320 mmcblk1p1
179 98 16048128 mmcblk1p2
254 0 14584 dm-0
254 1 2110 dm-1
254 2 4189 dm-2
254 3 5229 dm-3
254 4 47848 dm-4
254 5 2110 dm-5
254 6 4189 dm-6
254 7 13545 dm-7
7 8 21861 loop8
254 8 21861 dm-8
7 9 29138 loop9
254 9 29137 dm-9
7 10 13545 loop10
254 10 13545 dm-10
7 11 2111 loop11
254 11 2110 dm-11
7 12 5229 loop12
254 12 5229 dm-12
7 13 55125 loop13
254 13 55125 dm-13
7 14 2111 loop14
254 14 2110 dm-14
7 15 15624 loop15
254 15 15624 dm-15
#
Skickat från min GT-I8190
ops.. i forgot something.
the recovery built in the kernal, its more complicated then S3.
C:\Android>adb reboot recovery
C:\Android>adb shell
$ cat /proc/mounts
cat /proc/mounts
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
/dev/block/mmcblk0p1 /mnt/.lfs j4fs rw,relatime 0 0
/dev/block/mmcblk0p22 /system ext4 rw,nodev,noatime,nodiratime,barrier=1,data=ordered 0 0
$
This is what I get in recovery mode. Hope it helps
Edit: Or not, damn it!
avicohh said:
ops.. i forgot something.
the recovery built in the kernal, its more complicated then S3.
Click to expand...
Click to collapse
Why do they have to make things so confusing. I dont think im able to do it now
Sent from my GT-I9300 using xda premium
You were right, it is in the kernel. I've managed to disassemble boot.img and found a recovery in there. This indeed complicates things.
Benzonat0r said:
You were right, it is in the kernel. I've managed to disassemble boot.img and found a recovery in there. This indeed complicates things.
Click to expand...
Click to collapse
Oh, damn! We need someone like chainfire to get this device goin' custom!
Skickat från min GT-P7500 via Tapatalk 2
Benzonat0r said:
You were right, it is in the kernel. I've managed to disassemble boot.img and found a recovery in there. This indeed complicates things.
Click to expand...
Click to collapse
Can you extract that recovery.img i will then try and add cwm to it. What operating system are yiu using to unpack boot.img?
Sent from my GT-I9300 using xda premium
Windows 7 emulating Linux via Cygwin + dsixda's Android Kitchen
This it an extracted boot.img, the recovery is in here.
Benzonat0r said:
Windows 7 emulating Linux via Cygwin + dsixda's Android Kitchen
This it an extracted boot.img, the recovery is in here.
Click to expand...
Click to collapse
Ahh yeah ive dont that but there is no recovery.img in there
Sent from my GT-I9300 using xda premium
There's no image in there no, but I think it's integrated in it, just like in Galaxy Ace 2 there's no recovery.img in the stock firmware but the recovery its packed directly in kernel.bin
Benzonat0r said:
There's no image in there no, but I think it's integrated in it, just like in Galaxy Ace 2 there's no recovery.img in the stock firmware but the recovery its packed directly in kernel.bin
Click to expand...
Click to collapse
Yeah thats what i thought. Looks like im going to have to set up ubuntu to create it. Not many tools made for windows. Hopefully can get it set up in the next week. Dont hold me to it though as ive never done anything like this before. I usually do theming over at the galaxy s3 intetnational forum. Only problem is people are going to have to try it out for me if i can get it together as my girlfriend has the s3mini and doesnt like me doing thing to her phone.
Sent from my GT-I9300 using xda premium
Hahahaha that's totally understandable man girls are like that don't sweat it. We'd appreciate that very much.
Thing is that I don't have a spare hard drive to install Ubuntu and my disk space is nearly full, around 8 gigs free of 2TB of space.
hey i build a cwm version on koushik-lion for Galaxy S3 mini (alias Golden) ... its cwm recovery 6.0.2.7 Touch recovery.img - 6.10 MB but i don´t know how i can test it..... because its my first samsung device and I don´t want to brick it .... can i try "fastboot flash recovery recovery.img" or .... I hope someone knows a way ...
ps: link to recovery-builder: http://jenkins.cyanogenmod.com/job/recovery/14184/
Hi everybody,
i have a galaxy S4 korean version E300L, i been trying to install on it a custom rom of a korean gs4 i9500 through CWM, everything went smooth till i came to discover that there's no signal and the baseband is unknown and the IMEI is blank! and before doing so i made sure to backup my rom and also the efs partition with a dd command using the following command: dd if=/dev/block/mmcblk0p3 of=/sdcard/efs and here's the 20mb efs backup if anybody can tell me how to use it:
http://www.4shared.com/file/Ajc7gjXB/efs.html
because trying to restore that backup using dd command like that:
[email protected]:/ # dd if=/sdcard/efs of=/dev/block/mmcblk0p3
dd if=/sdcard/efs of=/dev/block/mmcblk0p3
40960+0 records in
40960+0 records out
20971520 bytes transferred in 4.253 secs (4930994 bytes/sec)
[email protected]:/ # reboot
reboot
as you can see everything goes well but when i check /efs using root explorer the partition would be the same, a blank folder with few recreated files by the system with no nv-data.bin files., so please can you suggest anything to restore my wiped efs partition? i tried to restore the cwm backup many times but it didn't work, and here's the partition table:
[email protected]:/ # mount
mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/secure tmpfs rw,seclabel,relatime,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p17 /persdata/absolute ext4 rw,seclabel,nosuid,nodev,relatime,
data=ordered 0 0
/dev/block/mmcblk0p20 /system ext4 ro,seclabel,relatime,errors=panic,data=ordere
d 0 0
/dev/block/mmcblk0p3 /efs ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_
checksum,journal_async_commit,noauto_da_alloc,data=ordered 0 0
/dev/block/mmcblk0p19 /cache ext4 rw,seclabel,nosuid,nodev,noatime,discard,journ
al_checksum,journal_async_commit,noauto_da_alloc,errors=panic,data=ordered 0 0
/dev/block/mmcblk0p21 /data ext4 rw,seclabel,nosuid,nodev,noatime,discard,journa
l_checksum,journal_async_commit,noauto_da_alloc,data=ordered 0 0
/dev/block/mmcblk0p14 /tombstones ext4 rw,seclabel,nosuid,nodev,noatime,data=ord
ered 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
none /dev/memcgrp cgroup rw,relatime,memory 0 0
/data/media /mnt/shell/emulated sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1
023 0 0
[email protected]:/ #
yakie47 said:
Hi everybody,
i have a galaxy S4 korean version E300L, i been trying to install on it a custom rom of a korean gs4 i9500 through CWM, everything went smooth till i came to discover that there's no signal and the baseband is unknown and the IMEI is blank! and before doing so i made sure to backup my rom and also the efs partition with a dd command using the following command: dd if=/dev/block/mmcblk0p3 of=/sdcard/efs and here's the 20mb efs backup if anybody can tell me how to use it:
http://www.4shared.com/file/Ajc7gjXB/efs.html
because trying to restore that backup using dd command like that:
[email protected]:/ # dd if=/sdcard/efs of=/dev/block/mmcblk0p3
dd if=/sdcard/efs of=/dev/block/mmcblk0p3
40960+0 records in
40960+0 records out
20971520 bytes transferred in 4.253 secs (4930994 bytes/sec)
[email protected]:/ # reboot
reboot
as you can see everything goes well but when i check /efs using root explorer the partition would be the same, a blank folder with few recreated files by the system with no nv-data.bin files., so please can you suggest anything to restore my wiped efs partition? i tried to restore the cwm backup many times but it didn't work, and here's the partition table:
[email protected]:/ # mount
mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/secure tmpfs rw,seclabel,relatime,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p17 /persdata/absolute ext4 rw,seclabel,nosuid,nodev,relatime,
data=ordered 0 0
/dev/block/mmcblk0p20 /system ext4 ro,seclabel,relatime,errors=panic,data=ordere
d 0 0
/dev/block/mmcblk0p3 /efs ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_
checksum,journal_async_commit,noauto_da_alloc,data=ordered 0 0
/dev/block/mmcblk0p19 /cache ext4 rw,seclabel,nosuid,nodev,noatime,discard,journ
al_checksum,journal_async_commit,noauto_da_alloc,errors=panic,data=ordered 0 0
/dev/block/mmcblk0p21 /data ext4 rw,seclabel,nosuid,nodev,noatime,discard,journa
l_checksum,journal_async_commit,noauto_da_alloc,data=ordered 0 0
/dev/block/mmcblk0p14 /tombstones ext4 rw,seclabel,nosuid,nodev,noatime,data=ord
ered 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
none /dev/memcgrp cgroup rw,relatime,memory 0 0
/data/media /mnt/shell/emulated sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1
023 0 0
[email protected]:/ #
Click to expand...
Click to collapse
Wrong forum.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
First: Questions go in Q&A
Second: make sure you are in the correct forum for your device
Moved to International S4 and Q&A
FNM
sir, it is not enough to backup only efs partition in s4, you must backup also m9kefs1, 2 and 3 partitions
http://forum.xda-developers.com/showthread.php?t=2284357
samersh72 said:
sir, it is not enough to backup only efs partition in s4, you must backup also m9kefs1, 2 and 3 partitions
http://forum.xda-developers.com/showthread.php?t=2284357
Click to expand...
Click to collapse
what about the CWM back up i have? is there any chance to extract those hidden partitions from it? if my Korean version has that same divided into 4 efs partition?
yakie47 said:
what about the CWM back up i have? is there any chance to extract those hidden partitions from it? if my Korean version has that same divided into 4 efs partition?
Click to expand...
Click to collapse
efs and m9kefs partitions are not a part of the firmware, they are not flashed with it
samersh72 said:
efs and m9kefs partitions are not a part of the firmware, they are not flashed with it
Click to expand...
Click to collapse
you mean that those m9kefs blocks are not part of the system so cwm would never back'em up then..?
and what's the size of each one of those m9kefs blocks in your gs4, for me after making those m9kefs partitions backups i got 4mb size in each one of them as for the main one: /dev/block/mmcblk0p3 partition, it was 20mb, and cheking them with an hex editor they don't seem like an efs partition similar to the gs2 or the gs3 only the 20mb /dev/block/mmcblk0p3 partition that contains some information that seem to have something to do with the efs partition data, and here's a link to one of those partitions check it out yourself:
http://www.mediafire.com/download.php?cwrbz26cdowowuk
yakie47 said:
you mean that those m9kefs partitions are not part of the system so cwm would never backed'em up then..?
and what's the size of each one of those m9kefs partitions in your gs4, for me after making those m9kefs partitions backups i got 4mb size in each one of them as for the main one: /dev/block/mmcblk0p3 partition, it was 20mb, and cheking them with an hex editor they don't seem like an efs partition similar to the gs2 or the gs3 only the 20mb /dev/block/mmcblk0p3 partition that contains some information that seem to have something to do with the efs partition data, and here's a link to one of those partitions check it out yourself:
http://www.mediafire.com/download.php?cwrbz26cdowowuk
Click to expand...
Click to collapse
yes
right size.
those EFS partitions that need to be secured for the S4.
m9kefs contain NV_DATA files
EDIT: in S2 & S3 all are included in efs partition
samersh72 said:
efs and m9kefs partitions are not a part of the firmware, they are not flashed with it
Click to expand...
Click to collapse
samersh72 said:
yes
right size.
those EFS partitions that need to be secured for the S4.
m9kefs contain NV_DATA files
EDIT: in S2 & S3 all are included in efs partition
Click to expand...
Click to collapse
well.. good to know that even though it's too late!
Hi,
May I ask you a link to your efs partition? I might have an idea to fix your device (and in the same time, getting access to an exynos s4 efs might help me adding support to galaxsim unlock)
I believe the link is above, hope you could find a way to restore that efs.bin file.
Sent from my SHV-E300L using xda premium