I'm trying to port Clockwork recovery for the device, according to Koush's Post. However, the phone appears to be a non-MTD device, so the instructions for finding the boot.img do not apply.
Any idea on how to locate the boot.img on the device?
Thank you.
hope someone can help you.
you need to use the linux command "dd" instead of the dump_image tool.
it's only mildly more complicated.
http://www.debianhelp.co.uk/ddcommand.htm
there is a guide at the bottom of this page...
http://www.addictivetips.com/mobile...es-boot-recovery-and-system-partition-images/
"alternative method"
try that.
note; i don't know for certain that this will work as i haven't tried it since i don't have an O3D yet.
should this thread not be in development too?
hefonthefjords said:
you need to use the linux command "dd" instead of the dump_image tool.
it's only mildly more complicated.
Click to expand...
Click to collapse
Of course dd will have to be used.
The problem, though, is that you need to specify an "if" for the command - and what I'm trying to find is the location off the boot image in a non-MTD device.
adb cat /proc/partitions
dunno what will come up but that lists partitions for you.
edit: please post what came up actually. i'm curious.
hefonthefjords said:
adb cat /proc/partitions
dunno what will come up but that lists partitions for you.
edit: please post what came up actually. i'm curious.
Click to expand...
Click to collapse
Code:
major minor #blocks name
7 0 13545 loop0
7 1 13545 loop1
7 2 13545 loop2
7 3 5229 loop3
7 4 9387 loop4
7 5 18743 loop5
7 6 4190 loop6
7 7 31217 loop7
179 0 7757824 mmcblk0
179 1 128 mmcblk0p1
179 2 128 mmcblk0p2
179 3 128 mmcblk0p3
179 4 512 mmcblk0p4
179 5 10240 mmcblk0p5
179 6 10240 mmcblk0p6
179 7 614400 mmcblk0p7
179 8 1048576 mmcblk0p8
179 9 512 mmcblk0p9
179 10 65536 mmcblk0p10
179 11 2048 mmcblk0p11
179 12 512 mmcblk0p12
179 13 20480 mmcblk0p13
179 14 3072 mmcblk0p14
179 15 5979008 mmcblk0p15
179 16 7761920 mmcblk1
179 17 7760896 mmcblk1p1
254 0 13545 dm-0
254 1 13545 dm-1
254 2 13545 dm-2
254 3 5229 dm-3
254 4 9387 dm-4
254 5 18742 dm-5
254 6 4189 dm-6
254 7 31216 dm-7
7 8 14585 loop8
254 8 14584 dm-8
7 9 9387 loop9
254 9 9387 dm-9
7 10 3150 loop10
254 10 3150 dm-10
7 11 4190 loop11
254 11 4189 dm-11
7 12 19782 loop12
254 12 19782 dm-12
7 13 28098 loop13
254 13 28098 dm-13
7 14 16664 loop14
254 14 16663 dm-14
7 15 4190 loop15
254 15 4189 dm-15
7 16 19782 loop16
254 16 19782 dm-16
7 17 10427 loop17
254 17 10426 dm-17
7 18 8348 loop18
254 18 8347 dm-18
7 19 7308 loop19
254 19 7308 dm-19
7 20 11466 loop20
254 20 11466 dm-20
7 21 15624 loop21
254 21 15624 dm-21
7 22 10427 loop22
254 22 10426 dm-22
7 23 9387 loop23
254 23 9387 dm-23
7 24 15624 loop24
254 24 15624 dm-24
7 25 4190 loop25
254 25 4189 dm-25
7 26 5229 loop26
254 26 5229 dm-26
dump all the "mmcblkxxx" partitions (where xxx is the numerical digits and p off the end). one of them is your boot image. dunno which one as lg could really have picked whichever one they want to be boot. i assume ti will be fairly obvious which is which once you examine the content.
i think you're "if=" arg has to be this format; "if=/dev/block/mmcblkxxx"
you'll jsut have to dump them to sd as like "mmcblk0.img", "mmcblk0p1.img" etc and then figure out which is which by examining them.
from what i have seen on google "mmcblk0p1" is normally the boot image but i don't know if this is totally standardised or not.
Well, we're back to the beginning This is basically my original question - where is the boot.img
Thank you for trying, though.
sorry.
is it that hard to tell when you extract all the partitions?
Yes, as I'm not even sure what should be in the boot.img
Have a look here for info on splitting boot images and what's generally in them: http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
Hi,
Any news about extracting boot.img?
Br,
Normally, in HTC desire, boot image is something about 3 MB; so you might want to dump the partitions which are close to that (not much smaller ones, tho, I presume)
zizouth said:
Hi,
Any news about extracting boot.img?
Br,
Click to expand...
Click to collapse
Great question! I'm having the most difficult time extracting boot images from roms in the O3d/Thrill forums ONLY! I'm able to extract roms from lots of other devices BUT the O3D/Thrill. The error message I get while trying to extract the boot image using cygwin on windows 7 is:
Android Magic not found in ./boot.img. Giving up.
gzip: ../../boot.img-ramdisk.gz: No such file or directory
cpio: premature end of archive
What is different about the boot image of the O3D/Thrill than other devices?
Related
So guys i would like to develop cmw for our J.
In adb shell i'v made
Code:
cat /proc/partitions
and it returns something like this:
Code:
major minor #blocks name
7 0 5229 loop0
7 1 7308 loop1
7 2 27059 loop2
7 3 2111 loop3
179 0 3817472 mmcblk0
179 1 1024 mmcblk0p1
179 2 2048 mmcblk0p2
179 3 20480 mmcblk0p3
179 4 1 mmcblk0p4
179 5 30720 mmcblk0p5
179 6 8192 mmcblk0p6
179 7 5120 mmcblk0p7
179 8 8192 mmcblk0p8
179 9 8192 mmcblk0p9
179 10 665600 mmcblk0p10
179 11 163840 mmcblk0p11
179 12 3072 mmcblk0p12
179 13 3072 mmcblk0p13
179 14 3072 mmcblk0p14
179 15 784384 mmcblk0p15
179 16 2103296 mmcblk0p16
179 32 1927168 mmcblk1
179 33 1927100 mmcblk1p1
254 0 5229 dm-0
254 1 7308 dm-1
254 2 27058 dm-2
254 3 2110 dm-3
Anyone have an idea which of those are for example boot partition etc?
Hey guys I've made some progress I've found boot and recovery partitions. Right now I'm developing CMW so stay tuned
Wysłane z mojego ST26i
I'd like to bring this to the attention of all developers. It's CWM, which stands for ClockworkMod. Therefore, writing CMW instead of CWM may convey the wrong idea. Cheers.
Ya xperia j needs developing !!
Sent from my ST26i using xda app-developers app
rachit7 said:
Ya xperia j needs developing !!
Sent from my ST26i using xda app-developers app
Click to expand...
Click to collapse
I second that.
Sent from my ST26i
any one know which block name the /data partition is? (/dev/block/mmcblk0pxx)
This is my first post on xda, and I'm pretty much a noob. So I hope I'm posting this in the correct section, if not please feel free to correct me if I'm wrong.
I'm trying my hand at some developing and have a couple questions I'm hoping someone can help me with.
The goal is Cyanogenmod 10.2 on my LG Lucid VS840. Currently I'm using an unofficial CM10 ROM Android version 4.1.2 (Not my work)
Partition Information? I'm unsure how to convert the information from the /proc/partitions file into something I can use for my BoardConfig.mk file as follows
# fix this up by examining /proc/mtd on a running device
BOARD_BOOTIMAGE_PARTITION_SIZE := 0x105c0000
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 0x105c0000
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 0x105c0000
BOARD_USERDATAIMAGE_PARTITION_SIZE := 0x105c0000
BOARD_FLASH_BLOCK_SIZE := 131072
My device does not have a /proc/mtd file. I do have the /proc/partitions file as follows
major minor #blocks name
7 0 7308 loop0
7 1 2111 loop1
179 0 7577600 mmcblk0
179 1 32768 mmcblk0p1
179 2 1024 mmcblk0p2
179 3 1024 mmcblk0p3
179 4 1 mmcblk0p4
179 5 1024 mmcblk0p5
179 6 5120 mmcblk0p6
179 7 5120 mmcblk0p7
179 8 10240 mmcblk0p8
179 9 1024 mmcblk0p9
179 10 3072 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 8192 mmcblk0p12
179 13 16384 mmcblk0p13
179 14 32768 mmcblk0p14
179 15 3072 mmcblk0p15
179 16 3072 mmcblk0p16
179 17 3072 mmcblk0p17
179 18 3072 mmcblk0p18
179 19 1024 mmcblk0p19
179 20 8192 mmcblk0p20
179 21 16384 mmcblk0p21
179 22 73728 mmcblk0p22
179 23 8192 mmcblk0p23
179 24 24576 mmcblk0p24
179 25 8192 mmcblk0p25
179 26 1048576 mmcblk0p26
179 27 270336 mmcblk0p27
179 28 1622016 mmcblk0p28
179 29 16384 mmcblk0p29
179 30 4194304 mmcblk0p30
179 31 5120 mmcblk0p31
179 32 15637504 mmcblk1
179 33 15633408 mmcblk1p1
254 0 7308 dm-0
254 1 2110 dm-1
I believe this is the proper fix for the message:
Need size of filesystem
+ '[' 1 -ne 0 ']'
+ exit 4
error: failed to build /home/ben/vs840/out/target/product/vs840/userdata.img from /home/ben/vs840/out/target/product/vs840/data
make: *** [/home/ben/vs840/out/target/product/vs840/userdata.img] Error 1
make: *** Deleting file `/home/ben/vs840/out/target/product/vs840/userdata.img'
make: *** Waiting for unfinished jobs....
Someone please help me! Thanks to everyone in advance!
https://www.aesonlabs.ca/blogs/android-internal-storage-sector-by-sector-copy-clone/#comment-131
that was very useful
i have HTC11U, i want to make an entire backup of all sectors to recover lost data by Recuva or any other recovery progs on windows
the blocks i see for my phone when i apply this command " cat /proc/partitions "
is :
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 2928884 zram0
8 0 124280832 sda
8 1 40 sda1
8 2 65536 sda2
8 3 65536 sda3
8 4 3915776 sda4
8 5 57344 sda5
8 6 61440 sda6
8 7 120102912 sda7
8 8 4012 sda8
8 80 57344 sdf
8 81 16 sdf1
8 82 256 sdf2
8 83 2048 sdf3
8 84 4 sdf4
8 85 4096 sdf5
8 86 24256 sdf6
8 87 10240 sdf7
8 88 4 sdf8
8 89 10240 sdf9
8 90 1024 sdf10
8 91 5116 sdf11
8 48 458752 sdd
8 49 1024 sdd1
8 50 512 sdd2
8 51 512 sdd3
8 52 2048 sdd4
8 53 512 sdd5
8 54 512 sdd6
8 55 512 sdd7
8 56 512 sdd8
8 57 512 sdd9
8 58 128 sdd10
8 59 1024 sdd11
8 60 65536 sdd12
8 61 107520 sdd13
8 62 5120 sdd14
8 63 1024 sdd15
259 7 256 sdd16
259 8 20480 sdd17
259 9 256 sdd18
259 10 16384 sdd19
259 11 2048 sdd20
259 12 128 sdd21
259 13 229376 sdd22
259 14 2772 sdd23
8 32 4096 sdc
8 33 4052 sdc1
8 16 4096 sdb
8 17 4052 sdb1
8 64 163840 sde
8 65 1024 sde1
8 66 2048 sde2
8 67 2048 sde3
8 68 8 sde4
8 69 32768 sde5
8 70 128 sde6
8 71 4 sde7
8 72 46080 sde8
8 73 1024 sde9
8 74 20480 sde10
8 75 30720 sde11
8 76 1284 sde12
8 77 64 sde13
8 78 1024 sde14
8 79 512 sde15
259 0 10240 sde16
259 1 32 sde17
259 2 4 sde18
259 3 1024 sde19
259 4 8192 sde20
259 5 2048 sde21
259 6 3040 sde22
252 0 120102912 dm-0
7 64 65536 loop64
but what i saw on the internet is different blocks like:
major minor #blocks name
7 0 98304 loop0
179 0 30535680 mmcblk0
179 1 65536 mmcblk0p1
179 2 1024 mmcblk0p2
179 3 512 mmcblk0p3
[...]
179 27 716800 mmcblk0p27
179 28 28551146 mmcblk0p28
179 29 5 mmcblk0p29
179 32 4096 mmcblk0rpmb
i know how to change the command according to the busybox installation path.
but for my blocks there, i am not able to retrieve any of these blocks, as it gives me
dd: writing 'standard output': Connection reset by peer
347+0 records in
i tried to retrieve the largest one and random partitions, but the file i get in the NEXUS folder is 0 KB
this is driving me crazy
please i need your help
Any Luck?
Hey OP any luck yet? I have the same problem
Safe to say I have messed up badly. This morning, I was trying to update EvolutionX build (by dirty flashing) and I received an error: Cannot mount /product (invalid argument). After few tries, I still couldn't flash anything and neither could I now boot into the system. So I decided to wipe the data as well as system partition and then try to install the ROM zip. It failed again, but now the error said that it didn't find the /system and /vendor as well.
From the TWRP Recovery > Mount section, I verified that I could not check the system, vendor, and product partitions. I could select the rest. Recovery seems to be working fine.
I checked the partitions on phone:
>adb shell cat /etc/fstab
/system_root ext4 ro 0 0
/vendor ext4 ro 0 0
/product ext4 ro 0 0
/dev/block/sda10 /metadata ext4 rw 0 0
/dev/block/sda16 /data f2fs rw 0 0
/dev/block/sda11 /cache ext4 rw 0 0
/dev/block/sde4 /firmware vfat rw 0 0
/dev/block/sda7 /cust ext4 rw 0 0
/dev/block/sda2 /persist ext4 rw 0 0
/usb_otg vfat rw 0 0
/dev/block/mmcblk0p1 /external_sd vfat rw 0 0
>adb shell cat /proc/partitions
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
8 0 120479744 sda
8 1 8 sda1
8 2 32768 sda2
8 3 1024 sda3
8 4 512 sda4
8 5 512 sda5
8 6 131072 sda6
8 7 1048576 sda7
8 8 131072 sda8
8 9 64 sda9
8 10 16384 sda10
8 11 393216 sda11
8 12 393216 sda12
8 13 16384 sda13
8 14 8192 sda14
8 15 8388608 sda15
259 0 109918092 sda16
8 16 8192 sdb
8 17 7168 sdb1
8 18 128 sdb2
8 32 8192 sdc
8 33 7168 sdc1
8 34 128 sdc2
8 64 4194304 sde
8 65 512 sde1
8 66 4096 sde2
8 67 512 sde3
8 68 262144 sde4
8 69 1024 sde5
8 70 4096 sde6
8 71 32768 sde7
8 72 8192 sde8
8 73 32768 sde9
8 74 512 sde10
8 75 512 sde11
8 76 512 sde12
8 77 128 sde13
8 78 64 sde14
8 79 2048 sde15
259 1 2048 sde16
259 2 512 sde17
259 3 4096 sde18
259 4 512 sde19
259 5 4096 sde20
259 6 32768 sde21
259 7 8192 sde22
259 8 512 sde23
259 9 512 sde24
259 10 512 sde25
259 11 2048 sde26
259 12 2048 sde27
259 13 4 sde28
259 14 1024 sde29
259 15 256 sde30
259 16 8192 sde31
259 17 33424 sde32
259 18 4 sde33
259 19 1024 sde34
259 20 8192 sde35
259 21 2048 sde36
259 22 65536 sde37
259 23 128 sde38
259 24 32 sde39
259 25 32 sde40
259 26 512 sde41
259 27 28 sde42
259 28 512 sde43
259 29 1024 sde44
259 30 64 sde45
259 31 131072 sde46
259 32 24576 sde47
8 48 131072 sdd
8 49 104 sdd1
8 50 128 sdd2
8 51 1024 sdd3
8 80 131072 sdf
8 81 104 sdf1
8 82 2048 sdf2
8 83 2048 sdf3
8 84 10240 sdf4
8 85 128 sdf5
179 0 7761920 mmcblk0
179 1 7757824 mmcblk0p1
It seems that system_root, vendor and product do not have any block (?) assigned to them. Is there a way to identify what were the original assigned blocks to these partitions and assign them through fastboot/adb/recovery?
Any help is appreciated thanks!!
UPDATE: Flashed the fastboot rom and it solved the issue. Got the stock MIUI and flashed the custom recovery/rom from there on. See last reply for details.
Not what you asked but the standard rescue procedure: flash MIUI stock ROM (~2.4GB) with MiFlash and start again...
pnin said:
Not what you asked but the standard rescue procedure: flash MIUI stock ROM (~2.4GB) with MiFlash and start again...
Click to expand...
Click to collapse
This worked!! I literally thought that the phone was toast. But this worked. Downloaded the fastboot rom for IN variant (filename: surya_in_global_images_V12.0.9.0.QJGINXM_20210202.0000.00_10.0_in_8...) and ran the flash_all script while the phone was in fastboot mode. Got the stock MIUI on the phone and then flashed the recovery and the custom rom.
Also, one of the issues I was getting when running flash_all script was that the pathname where I had extracted the fastboot rom had space in it (eg. "path/to/A B/rom"). Copied it to another drive so that path didn't have any space.
vjsa said:
This worked!! I literally thought that the phone was toast. But this worked. Downloaded the fastboot rom for IN variant (filename: surya_in_global_images_V12.0.9.0.QJGINXM_20210202.0000.00_10.0_in_8...) and ran the flash_all script while the phone was in fastboot mode. Got the stock MIUI on the phone and then flashed the recovery and the custom rom.
Also, one of the issues I was getting when running flash_all script was that the pathname where I had extracted the fastboot rom had space in it (eg. "path/to/A B/rom"). Copied it to another drive so that path didn't have any space.
Click to expand...
Click to collapse
Did you manage to install a custom ROM again? I got the same error a few weeks ago and rescued my phone with the fastboot ROM but whenever I try to install a custom ROM since then, I keep getting the same error.
Srivihar said:
Did you manage to install a custom ROM again? I got the same error a few weeks ago and rescued my phone with the fastboot ROM but whenever I try to install a custom ROM since then, I keep getting the same error.
Click to expand...
Click to collapse
Yep, installed the latest EvolutionX build (one that caused the issue in first place). Everything is working fine till now.
Hi all,
I was trying to identify userdata partition after
- adb shell
- cat /proc/partitions
on an unrooted Oneplus 2.
Here below was the result.
How to identify which one is userdata partition?
Thanks in advance.
Cheers,
Wen
Code:
major minor #blocks name
179 0 15388672 mmcblk0
179 1 81920 mmcblk0p1
179 2 1024 mmcblk0p2
179 3 128 mmcblk0p3
179 4 128 mmcblk0p4
179 5 1 mmcblk0p5
179 6 1024 mmcblk0p6
179 7 128 mmcblk0p7
179 8 1536 mmcblk0p8
179 9 1 mmcblk0p9
179 10 1024 mmcblk0p10
179 11 1024 mmcblk0p11
179 12 256 mmcblk0p12
179 13 256 mmcblk0p13
179 14 1 mmcblk0p14
179 15 1 mmcblk0p15
179 16 8 mmcblk0p16
179 17 1536 mmcblk0p17
179 18 1536 mmcblk0p18
179 19 10240 mmcblk0p19
179 20 10240 mmcblk0p20
179 21 1024 mmcblk0p21
179 22 8096 mmcblk0p22
179 23 16192 mmcblk0p23
179 24 16384 mmcblk0p24
179 25 32768 mmcblk0p25
179 26 1024 mmcblk0p26
179 27 1024 mmcblk0p27
179 28 96 mmcblk0p28
179 29 1024 mmcblk0p29
179 30 1024 mmcblk0p30
179 31 500 mmcblk0p31
259 0 500 mmcblk0p32
259 1 512 mmcblk0p33
259 2 512 mmcblk0p34
259 3 65536 mmcblk0p35
259 4 65536 mmcblk0p36
259 5 32768 mmcblk0p37
259 6 1024 mmcblk0p38
259 7 512 mmcblk0p39
259 8 512 mmcblk0p40
259 9 262144 mmcblk0p41
259 10 2621440 mmcblk0p42
259 11 11980783 mmcblk0p43
179 32 4096 mmcblk0rpmb
If you have an eMMC internal storage you can see names and partitions at same time:
Code:
ls -l /dev/block/platform/msm_sdcc.1/by-name/
xXx yYy said:
If you have an eMMC internal storage you can see names and partitions at same time:
Code:
ls -l /dev/block/platform/msm_sdcc.1/by-name/
Click to expand...
Click to collapse
Thanks for your reply.
After
Code:
ls -l /dev/block/platform/msm_sdcc.1/by-name/
It returns
Code:
/dev/block/platform/msm_sdcc.1/by-name/: Permission denied
How to resolve it?
Thanks.
Android must be root to successfully run the cmd.
xXx yYy said:
Android must be root to successfully run the cmd.
Click to expand...
Click to collapse
Thanks for your reply.
I just rooted the device.
But after
Code:
adb root
It returns
Code:
adbd cannot run as root in production builds
How to solve it?
Thanks in advance.
No way.