Recovery.img - Galaxy S III Mini General

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/

Related

Is there sch-i815 Cwm or firmware

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

Someone please. Need nvflashable ROM

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

required: mount partitions for s5360

Could somebody please provide the following (yes, searched here and google - no luck):
Partitions
Code:
# cat /proc/partitions
and
Mounted partitions
Code:
# mount
Could please somebody post their results from (preferable stock 2.3.6 and rooted) device here.
Thank you!
Solved my issue I was having, managed to get it, in case anybody else may need it:
Code:
# cat /proc/partitions
major minor #blocks name
137 0 513024 bml0/c
137 1 256 bml1
137 2 2048 bml2
137 3 2048 bml3
137 4 256 bml4
137 5 12800 bml5
137 6 5120 bml6
137 7 5120 bml7
137 8 5120 bml8
137 9 235520 bml9
137 10 40960 bml10
137 11 201984 bml11
137 12 256 bml12
137 13 256 bml13
137 14 256 bml14
137 15 1024 bml15
138 6 1280 stl6
138 9 227840 stl9
138 10 36864 stl10
138 11 194816 stl11
Code:
# mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/stl9 /system rfs ro,relatime,vfat,log_off,check=no,gid/uid/rwx,iocharset=cp437 0 0
/dev/stl10 /cache rfs rw,nosuid,nodev,relatime,vfat,llw,gid/uid/rwx,iocharset=cp437 0 0
/dev/stl6 /mnt/.lfs j4fs rw,relatime 0 0
/dev/stl11 /data rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=cp437 0 0

Trying to recreate entire partition table for Nexus 7 2013 (flo)

Hi
To cut a long story short I went about trying to extend my system partition using GNU Parted and it has failed terribly to the point I have bricked my tablet. At the moment I have managed to execute the command
Code:
fastboot boot twrp-3.2.3-0-flo.img
but this is running from RAM as I'm unable to flash any of the partitions as they are "missing".
This is the my original partition table:-
Code:
Number Start End Size File system Name Flags
1 67108864B 156745727B 89636864B fat16 radio
2 201326592B 204472319B 3145728B modemst1
3 204472320B 207618047B 3145728B modemst2
4 268435456B 283795455B 15360000B ext4 persist
5 335544320B 336343039B 798720B m9kefs1
6 336343040B 337141759B 798720B m9kefs2
7 402653184B 403451903B 798720B m9kefs3
8 403451904B 406597631B 3145728B fsg
9 469762048B 471298047B 1536000B sbl1
10 471298048B 472834047B 1536000B sbl2
11 472834048B 474931199B 2097152B sbl3
12 474931200B 480174079B 5242880B aboot
13 480174080B 480698367B 524288B rpm
14 536870912B 553648127B 16777216B boot
15 603979776B 604504063B 524288B tz
16 604504064B 604505087B 1024B pad
17 604505088B 606041087B 1536000B sbl2b
18 606041088B 608138239B 2097152B sbl3b
19 608138240B 613381119B 5242880B abootb
20 613381120B 613905407B 524288B rpmb
21 613905408B 614429695B 524288B tzb
22 671088640B 1551892479B 880803840B ext2 system
23 1551892480B 2139095039B 587202560B ext4 cache
24 2147483648B 2148532223B 1048576B misc
25 2214592512B 2225078271B 10485760B recovery
26 2281701376B 2281709567B 8192B DDR
27 2281709568B 2281717759B 8192B ssd
28 2281717760B 2281718783B 1024B m9kefsc
29 2348810240B 2348843007B 32768B metadata
30 2415919104B 15468576255B 13052657152B ext4 userdata
From some reading on the internet Linux can only have 4 primary partitons. All I know is that I have 30 partitions and I don't know what partition type to set them to; primary, logical and extended.
I've played around with the three partition types but I get an error message saying "Too many primary partitions".
Could someone shine some light here please?
Many thanks
Will
Bump
Bump
Don't know if it helps, but here is some partition info from stock flo:
Code:
[email protected]:/ $ cat /proc/partitions
major minor #blocks name
179 0 15388672 mmcblk0
179 1 87536 mmcblk0p1
179 2 3072 mmcblk0p2
179 3 3072 mmcblk0p3
179 4 15000 mmcblk0p4
179 5 780 mmcblk0p5
179 6 780 mmcblk0p6
179 7 780 mmcblk0p7
179 8 3072 mmcblk0p8
179 9 1500 mmcblk0p9
179 10 1500 mmcblk0p10
179 11 2048 mmcblk0p11
179 12 5120 mmcblk0p12
179 13 512 mmcblk0p13
179 14 16384 mmcblk0p14
179 15 512 mmcblk0p15
179 16 1 mmcblk0p16
179 17 1500 mmcblk0p17
179 18 2048 mmcblk0p18
179 19 5120 mmcblk0p19
179 20 512 mmcblk0p20
179 21 512 mmcblk0p21
179 22 860160 mmcblk0p22
179 23 573440 mmcblk0p23
179 24 1024 mmcblk0p24
179 25 10240 mmcblk0p25
179 26 8 mmcblk0p26
179 27 8 mmcblk0p27
179 28 1 mmcblk0p28
179 29 32 mmcblk0p29
179 30 13029359 mmcblk0p30
127|[email protected]:/ $ df
Filesystem Size Used Free Blksize
/dev 903.9M 76.0K 903.8M 4096
/sys/fs/cgroup 903.9M 12.0K 903.9M 4096
/mnt 903.9M 0.0K 903.9M 4096
/system 827.8M 823.8M 4.0M 4096
/cache 551.7M 10.6M 541.2M 4096
/data 12.2G 5.1G 7.1G 4096
/persist 14.5M 4.2M 10.2M 4096
/storage 903.9M 0.0K 903.9M 4096
/mnt/runtime/default/emulated: Permission denied
/storage/emulated 12.2G 5.1G 7.1G 4096
/mnt/runtime/read/emulated: Permission denied
/mnt/runtime/write/emulated: Permission denied
1|[email protected]:/ $ mount
rootfs / rootfs ro,seclabel,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,seclabel,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
tmpfs /mnt tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,nomblk_io_submit,errors=panic,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,nomblk_io_submit,errors=panic,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,relatime,nodelalloc,data=ordered 0 0
tmpfs /storage tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
/dev/fuse /mnt/runtime/default/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /mnt/runtime/read/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /mnt/runtime/write/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0

Tmo Galaxy S8 Eng build

I found a Tmo GS8 with exploded battery in the trash, and when I replaced the battery and booted it up, realized it had an old eng build on it. Would anyone be interested in looking into whether this could be flashed to retail Tmo GS8s in order to unlock them for custom ROMs?
I'm currently uploading to AFH: https://www.androidfilehost.com/?w=files&flid=325176
Just be aware that while the 7z download is only 4.3GB, it extracts to the full 64GB flash.
This is meant for developers, NOT for users!
Spoiler: mount output
Code:
rootfs on / type rootfs (ro,seclabel,size=1628820k,nr_inodes=407205)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,size=1699556k,nr_inodes=424889,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime,gid=3009,hidepid=2)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,seclabel,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
none on /dev/stune type cgroup (rw,relatime,schedtune)
tmpfs on /mnt type tmpfs (rw,seclabel,relatime,size=1699556k,nr_inodes=424889,mode=755,gid=1000)
none on /config type configfs (rw,relatime)
tmpfs on /mnt/secure type tmpfs (rw,seclabel,relatime,size=1699556k,nr_inodes=424889,mode=700)
tmpfs on /mnt/secure/asec type tmpfs (rw,seclabel,relatime,size=1699556k,nr_inodes=424889,mode=700)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
none on /dev/cpuset type cgroup (rw,relatime,cpuset,noprefix,release_agent=/sbin/cpuset_release_agent)
pstore on /sys/fs/pstore type pstore (rw,seclabel,relatime)
/dev/block/sda19 on /system type ext4 (ro,seclabel,relatime)
/dev/block/sda20 on /cache type ext4 (rw,seclabel,nosuid,nodev,noatime,journal_checksum,noauto_da_alloc)
/dev/block/sda5 on /persist type ext4 (rw,seclabel,nosuid,nodev,noatime,journal_checksum,noauto_da_alloc)
/dev/block/sdd7 on /dsp type ext4 (ro,seclabel,nosuid,nodev,relatime,data=ordered)
/dev/block/sda6 on /efs type ext4 (rw,seclabel,nosuid,nodev,noatime,journal_checksum,noauto_da_alloc)
/dev/block/sda15 on /firmware type vfat (ro,context=u:object_r:firmware_file:s0,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=437,iocharset=iso8859-1,shortname=lower,errors=remount-ro)
/dev/block/sda16 on /firmware-modem type vfat (ro,context=u:object_r:firmware_file:s0,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=437,iocharset=iso8859-1,shortname=lower,errors=remount-ro)
/dev/block/sda21 on /carrier type ext4 (rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc)
/dev/block/sda22 on /omr type ext4 (rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc)
tmpfs on /storage type tmpfs (rw,seclabel,relatime,size=1699556k,nr_inodes=424889,mode=755,gid=1000)
tracefs on /sys/kernel/debug/tracing type tracefs (rw,seclabel,relatime)
adb on /dev/usb-ffs/adb type functionfs (rw,relatime)
/dev/block/sda19 on /system/carrier type ext4 (ro,seclabel,relatime)
/dev/block/dm-0 on /data type ext4 (rw,seclabel,nosuid,nodev,noatime,journal_checksum,noauto_da_alloc)
/data/knox/tmp_sdcard on /mnt/knox type sdcardfs (rw,nosuid,nodev,relatime,mask=0077)
/data/knox/sdcard on /mnt/knox/default/knox-emulated type sdcardfs (rw,nosuid,nodev,relatime,low_uid=1000,low_gid=1000,gid=1015,multi_user,mask=0006)
/data/knox/sdcard on /mnt/knox/read/knox-emulated type sdcardfs (rw,nosuid,nodev,relatime,low_uid=1000,low_gid=1000,gid=9997,multi_user,mask=0027)
/data/knox/sdcard on /mnt/knox/write/knox-emulated type sdcardfs (rw,nosuid,nodev,relatime,low_uid=1000,low_gid=1000,gid=9997,multi_user,mask=0007)
/data/knox/secure_fs/enc_media on /mnt/shell/enc_media type sdcardfs (rw,nosuid,nodev,relatime,low_uid=1000,low_gid=1000,gid=9997,multi_user,reserved=20MB)
/data/media on /mnt/runtime/default/emulated type sdcardfs (rw,nosuid,nodev,noexec,noatime,low_uid=1023,low_gid=1023,gid=1015,multi_user,mask=0006,reserved=20MB)
/data/media on /storage/emulated type sdcardfs (rw,nosuid,nodev,noexec,noatime,low_uid=1023,low_gid=1023,gid=1015,multi_user,mask=0006,reserved=20MB)
/data/media on /mnt/runtime/read/emulated type sdcardfs (rw,nosuid,nodev,noexec,noatime,low_uid=1023,low_gid=1023,gid=9997,multi_user,mask=0027,reserved=20MB)
/data/media on /mnt/runtime/write/emulated type sdcardfs (rw,nosuid,nodev,noexec,noatime,low_uid=1023,low_gid=1023,gid=9997,multi_user,mask=0007,reserved=20MB)
/data/knox/secure_fs/enc_user on /data/enc_user type ecryptfs (rw,seclabel,nodev,relatime,ecryptfs_fnek_sig=30cbf87c57ba04e7,ecryptfs_sig=30cbf87c57ba04e7,userid=0,sdp_enabled,partition_id=0,ecryptfs_cipher=aes,ecryptfs_key_bytes=32,ecryptfs_enable_cc,ecryptfs_passthrough,base=,label=)
/mnt/shell/enc_media on /mnt/shell/enc_emulated type ecryptfs (rw,seclabel,nodev,relatime,ecryptfs_fnek_sig=30cbf87c57ba04e7,ecryptfs_sig=30cbf87c57ba04e7,userid=0,sdp_enabled,partition_id=1,ecryptfs_cipher=aes,ecryptfs_key_bytes=32,ecryptfs_enable_cc,ecryptfs_passthrough,base=,label=)
/dev/block/vold/public:179,1 on /mnt/media_rw/0000-0000 type sdfat (rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,fs=exfat,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,utf8,namecase=0,adj_req,symlink=0,bps=512,errors=remount-ro)
/dev/block/vold/public:179,1 on /mnt/secure/asec type sdfat (rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,fs=exfat,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,utf8,namecase=0,adj_req,symlink=0,bps=512,errors=remount-ro)
/mnt/media_rw/0000-0000 on /mnt/runtime/default/0000-0000 type sdcardfs (rw,nosuid,nodev,noexec,noatime,low_uid=1023,low_gid=1023,gid=1015,mask=0006)
/mnt/media_rw/0000-0000 on /storage/0000-0000 type sdcardfs (rw,nosuid,nodev,noexec,noatime,low_uid=1023,low_gid=1023,gid=1015,mask=0006)
/mnt/media_rw/0000-0000 on /mnt/runtime/read/0000-0000 type sdcardfs (rw,nosuid,nodev,noexec,noatime,low_uid=1023,low_gid=1023,gid=9997,mask=0022)
/mnt/media_rw/0000-0000 on /mnt/runtime/write/0000-0000 type sdcardfs (rw,nosuid,nodev,noexec,noatime,low_uid=1023,low_gid=1023,gid=9997,mask=0022)
Spoiler: partitions
Code:
major minor #blocks name
1 0 8192 ram0
1 1 8192 ram1
1 2 8192 ram2
1 3 8192 ram3
1 4 8192 ram4
1 5 8192 ram5
1 6 8192 ram6
1 7 8192 ram7
1 8 8192 ram8
1 9 8192 ram9
1 10 8192 ram10
1 11 8192 ram11
1 12 8192 ram12
1 13 8192 ram13
1 14 8192 ram14
1 15 8192 ram15
253 0 2097152 vnswap0
8 16 4096 sdb
8 17 3940 sdb1
8 0 62418944 sda
8 1 2048 sda1
8 2 2048 sda2
8 3 4 sda3
8 4 8 sda4
8 5 32768 sda5
8 6 20480 sda6
8 7 10240 sda7
8 8 1024 sda8
8 9 512 sda9
8 10 30720 sda10
8 11 21504 sda11
8 12 512 sda12
8 13 4096 sda13
8 14 16384 sda14
8 15 97280 sda15
259 0 87040 sda16
259 1 65536 sda17
259 2 65536 sda18
259 4 4812800 sda19
259 6 614400 sda20
259 8 46080 sda21
259 10 10240 sda22
259 12 6144 sda23
259 14 10240 sda24
259 16 56460112 sda25
8 48 61440 sdd
8 49 512 sdd1
8 50 2048 sdd2
8 51 512 sdd3
8 52 2048 sdd4
8 53 16 sdd5
8 54 512 sdd6
8 55 16384 sdd7
8 56 20480 sdd8
8 57 4 sdd9
8 58 1024 sdd10
8 59 384 sdd11
8 60 512 sdd12
8 61 512 sdd13
8 62 512 sdd14
8 63 256 sdd15
259 3 256 sdd16
259 5 4 sdd17
259 7 4 sdd18
259 9 128 sdd19
259 11 512 sdd20
259 13 1024 sdd21
259 15 13640 sdd22
8 32 4096 sdc
8 33 3940 sdc1
254 0 56460096 dm-0
179 0 125042688 mmcblk0
179 1 125026304 mmcblk0p1
boot screen
download screen
Yeah, ENG kernel's usually are open to ADB at recovery, making it easy to unlock, wipe FRP and put on a custom rom. I have two Tmo S8's here and I just fixed one, I'll report back about your kernel.... Thanks
AND BTW, thats a trip, both of the one's I have say fuse blown like that, I guess that from the battery's blowing up, but out of the two I managed to piece together a beautiful one.. Anyhow, I'll report back after flashing. I'm gonna slap lineage 19.1 on there. Even if your kernel doesn't work, which I'm sure it will, there's a full setup of eng boot, root, and modified odin @ https://forum.xda-developers.com/t/eng-boot-root.3608353/ that we can both use if this one is no good.

Categories

Resources