Related
Does anyone know where I can find property files for Folio 100. I think that mblaster and DerArtem know the answer and when I type
Code:
sudo make_ext4fs -l 268435456 -a system output_file/system.img path_to_your_rom/folder_name
I get:
Creating filesystem with parameters:
Size: 268435456
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 65536
Block groups: 2
Reserved block group size: 15
Created filesystem with 999/16384 inodes and 65063/65536 blocks
error: open_output_file: open: No such file or directory
Click to expand...
Click to collapse
Please help and sorry if I posted in wrong path
The system.prop is in the root of the repository, the default.prop is in the ramdisk subdirectory.
Here is DerArtems repository (seems to be the most up to date atm): https://github.com/DerArtem/android-device-betelgeuse
Don't know what is wrong with the make_ext4fs. I usually don't run it as root, but in principle this should not be a problem.
Thanks and do you know is this folio honeycomb kernel source?
https://github.com/DerArtem/android-tegra-2.6.36-honeycomb-folio-nvidia
What this mean? Can't find system.img?????????
error: open_output_file: open: No such file or directory
Found solution!!!
>>>>x_x<<<<...>>>>new error:
error: do_inode_allocate_extents: Failed to allocate 418 blocks
Jon2555 said:
Thanks and do you know is this folio honeycomb kernel source?
https://github.com/DerArtem/android-tegra-2.6.36-honeycomb-folio-nvidia
Click to expand...
Click to collapse
DerArtem started this, but afaik he never finished it.
Jon2555 said:
>>>>x_x<<<<...>>>>new error:
error: do_inode_allocate_extents: Failed to allocate 418 blocks
Click to expand...
Click to collapse
Sorry, never seen this error...
Thanks
Sent from my IDEOS S7 Slim using XDA App
I found what was the error. Size of files was bigger than 268 mb that I set when I want to pack system.img.
EDIT: It won't flash system.img. Only hope is to delete some files when packing if size is larger than 268.4 mb.
[Recovery] Working CWM 6.0.2.8 & CWM 6.0.3.7 for Samsung Galaxy Star ( S5280 &S5282 )
Hey guys,
We got another victory. CWM 6.0.2.8 & CWM 6.0.3.7 has been released for our device galaxy star.
STATUS - Tested
Use at your own risk i will not responsible for any mishappening
Contributor :
@Doc_cheilvenerdi.org
Procedure -
i) Boot your phone in odin mode.
ii) Then open odin.
iii) Flash it & Enjoy.
Link - CWM 6.0.2.8 - https://drive.google.com/folderview...sp=drive_web&tid=0B3qe_9NlA1D_Q2RTRzVBRmFkeDA
CWM 6.0.3.7 - https://drive.google.com/folderview?id=0B3qe_9NlA1D_c3dmNm1yQzdyX2M&usp=drive_web
Here is the screenshot-
did u test it?
Pleas Hold on and read carefully!
Please Hold on!
No Release yet!
Releasing software is a long and hard process...
...actually my Phone is on Jellybean 4.1.2 but I don't have yet a local copy of my european archive due to hotfile.com shutdown...
...so I'm still waiting for a mirror to back it up:
it's a strong option to recover a phone from a soft brick...
So what I'm doing here now?
I build Cyanogenmod from long time ago... starting with Gingerbread 7.2 up to KitKat 11.0 (for me it's really a different beast from older ones...)...
Now i prepared a device Skeleton for my mintss phone, I populated it looking online (many thanks to Ankur850, Batman38102, Requisite0, Sakindia123, TeamRegular and many others) and followed the Cyanogenmod guidelines to build a CWm recovery...
And I built a 6.0.2.8 (tuned to Cyanogenmod 10.0) with a working Kernel, a simple ramdisk, and so on...
...But I didn't test it yet...
...I'm still waiting due to my lack of a full firmware archive...
I also tried - for fun - to build the CWM 6.0.4.5 for Cyanogenmod 11.0 (beware: just a Blind Shot)
...using the 10.0 Kernel... working kernel but wrong configuration: it lacks Selinux capabilities (Working on it right now)...
...using a ramdisk tuned to JellyBean...
...filesystem nor permissive neither enforced...
..etc...
All things which can lead to a disaster while testing...
So, please, hold on until I'll test it on my own phone...
...if everything will be fine I'll be really happy to share it for the community...
See you soon on this thread then...
...news scheduled on incoming new year...
Doc_cheilvenerdi.org said:
Please Hold on!
No Release yet!
Releasing software is a long and hard process...
...actually my Phone is on Jellybean 4.1.2 but I don't have yet a local copy of my european archive due to hotfile.com shutdown...
...so I'm still waiting for a mirror to back it up:
it's a strong option to recover a phone from a soft brick...
So what I'm doing here now?
I build Cyanogenmod from long time ago... starting with Gingerbread 7.2 up to KitKat 11.0 (for me it's really a different beast from older ones...)...
Now i prepared a device Skeleton for my mintss phone, I populated it looking online (many thanks to Ankur850, Batman38102, Requisite0, Sakindia123, TeamRegular and many others) and followed the Cyanogenmod guidelines to build a CWm recovery...
And I built a 6.0.2.8 (tuned to Cyanogenmod 10.0) with a working Kernel, a simple ramdisk, and so on...
...But I didn't test it yet...
...I'm still waiting due to my lack of a full firmware archive...
I also tried - for fun - to build the CWM 6.0.4.5 for Cyanogenmod 11.0 (beware: just a Blind Shot)
...using the 10.0 Kernel... working kernel but wrong configuration: it lacks Selinux capabilities (Working on it right now)...
...using a ramdisk tuned to JellyBean...
...filesystem nor permissive neither enforced...
..etc...
All things which can lead to a disaster while testing...
So, please, hold on until I'll test it on my own phone...
...if everything will be fine I'll be really happy to share it for the community...
See you soon on this thread then...
...news scheduled on incoming new year...
Click to expand...
Click to collapse
excelent will wait for it :good:
I cant test it
Chirtagh said:
did u test it?
Click to expand...
Click to collapse
I cant test it bcoz i have S5282.:crying:
Download stock firmware
Doc_cheilvenerdi.org said:
Please Hold on!
No Release yet!
Releasing software is a long and hard process...
...actually my Phone is on Jellybean 4.1.2 but I don't have yet a local copy of my european archive due to hotfile.com shutdown...
...so I'm still waiting for a mirror to back it up:
it's a strong option to recover a phone from a soft brick...
So what I'm doing here now?
I build Cyanogenmod from long time ago... starting with Gingerbread 7.2 up to KitKat 11.0 (for me it's really a different beast from older ones...)...
Now i prepared a device Skeleton for my mintss phone, I populated it looking online (many thanks to Ankur850, Batman38102, Requisite0, Sakindia123, TeamRegular and many others) and followed the Cyanogenmod guidelines to build a CWm recovery...
And I built a 6.0.2.8 (tuned to Cyanogenmod 10.0) with a working Kernel, a simple ramdisk, and so on...
...But I didn't test it yet...
...I'm still waiting due to my lack of a full firmware archive...
I also tried - for fun - to build the CWM 6.0.4.5 for Cyanogenmod 11.0 (beware: just a Blind Shot)
...using the 10.0 Kernel... working kernel but wrong configuration: it lacks Selinux capabilities (Working on it right now)...
...using a ramdisk tuned to JellyBean...
...filesystem nor permissive neither enforced...
..etc...
All things which can lead to a disaster while testing...
So, please, hold on until I'll test it on my own phone...
...if everything will be fine I'll be really happy to share it for the community...
See you soon on this thread then...
...news scheduled on incoming new year...
Click to expand...
Click to collapse
Bro here is link to your country stock firmware & its not on hotfile.
http://terafile.co/5a3646396569
hey
rahulsinghal said:
I cant test it bcoz i have S5282.:crying:
Click to expand...
Click to collapse
umm i dont think this cwm is only compatible for s5280
you can try it
even if it doesnt work,it wont give you a bootloop,just a cwm error which can be recovered easily by flashing stock recovery
link
rahulsinghal said:
Hey guys,
We got another victory. CWM 6.0.4.5 has been released for our device galaxy star.
STATUS - Untested
Use at your own risk i will not responsible for any mishappening
Contributor :
@Doc_cheilvenerdi.org
Link - https://docs.google.com/file/d/0B3qe_9NlA1D_bm5WbDc2YWM3ck0/edit
Click to expand...
Click to collapse
the download link is denying access :/
hmmm
swhackeristahsan said:
the download link is denying access :/
Click to expand...
Click to collapse
Hey just request that file after some minute you will get access. n whats going on akshaymod
Doc_cheilvenerdi.org said:
Please Hold on!
No Release yet!
Releasing software is a long and hard process...
...actually my Phone is on Jellybean 4.1.2 but I don't have yet a local copy of my european archive due to hotfile.com shutdown...
...so I'm still waiting for a mirror to back it up:
it's a strong option to recover a phone from a soft brick...
So what I'm doing here now?
I build Cyanogenmod from long time ago... starting with Gingerbread 7.2 up to KitKat 11.0 (for me it's really a different beast from older ones...)...
Now i prepared a device Skeleton for my mintss phone, I populated it looking online (many thanks to Ankur850, Batman38102, Requisite0, Sakindia123, TeamRegular and many others) and followed the Cyanogenmod guidelines to build a CWm recovery...
And I built a 6.0.2.8 (tuned to Cyanogenmod 10.0) with a working Kernel, a simple ramdisk, and so on...
...But I didn't test it yet...
...I'm still waiting due to my lack of a full firmware archive...
I also tried - for fun - to build the CWM 6.0.4.5 for Cyanogenmod 11.0 (beware: just a Blind Shot)
...using the 10.0 Kernel... working kernel but wrong configuration: it lacks Selinux capabilities (Working on it right now)...
...using a ramdisk tuned to JellyBean...
...filesystem nor permissive neither enforced...
..etc...
All things which can lead to a disaster while testing...
So, please, hold on until I'll test it on my own phone...
...if everything will be fine I'll be really happy to share it for the community...
See you soon on this thread then...
...news scheduled on incoming new year...
Click to expand...
Click to collapse
Dude batman38102 is me I changes my username long time back. Also dudes I got my Galaxy star unbricked so Im back. Ill help in anyway I can
Its Going To Be LEGEND--wait for it--DARY!- Barney Stinson(How I Met Your Mother)
---------- Post added at 10:46 AM ---------- Previous post was at 10:42 AM ----------
Also can u please pm me the test recovery. Im willing to test in anyway i can.
Its Going To Be LEGEND--wait for it--DARY!- Barney Stinson(How I Met Your Mother)
Hmmm
Ironman38102 said:
Dude batman38102 is me I changes my username long time back. Also dudes I got my Galaxy star unbricked so Im back. Ill help in anyway I can
Its Going To Be LEGEND--wait for it--DARY!- Barney Stinson(How I Met Your Mother)
---------- Post added at 10:46 AM ---------- Previous post was at 10:42 AM ----------
Also can u please pm me the test recovery. Im willing to test in anyway i can.
Its Going To Be LEGEND--wait for it--DARY!- Barney Stinson(How I Met Your Mother)
Click to expand...
Click to collapse
Hey thats gr8 hope we will get cm now.:victory:
CWM 6.0.2.8 Up and Running!
News about CWM 6.0.2.8 from CyanogenMod 10.0 (Jellybean 4.1.2):
I don't have a Github account (I'm not a developer) so I'll post here exactly what I did to build and set "up and running" this ClockWorkMod Recovery!
First of all, in my Google Drive you'll find everything we are Talking about... the experimental device tree, the recovery Odin archive, tools, binaries, ...
On first build everything was fine but the LCD screen didn't light up...
...Recovery was running, anyway, but I could not see anything...
...I could, perhaps, control the phone from PC with "adb shell"!
Code:
[email protected]:~$ [b]adb shell[/b]
~ # [b]ls[/b]
cache init.rc sdcard1
data preload sys
default.prop proc system
dev res tmp
efs root ueventd.goldfish.rc
etc sbin ueventd.rc
fstab.sp8810 sd-ext ueventd.sp8810.rc
init sdcard
~ #
Recovery log recorded the problem:
Code:
...
failed to put fb0 info
...
It's a framebuffer problem and the solution is pretty known; I pasted it from TeamRegular repository and put inside BoardConfig.mk with related sources:
Code:
...
BOARD_CUSTOM_GRAPHICS := ../../../device/samsung/sp8810/recovery/graphics.c
...
Well done! Recovery 6.0.2.8 up and running
Now testing:
- I can mount/unmount and list all filesystems
- I can backup the current firmware
- I can format and restore the external second partition (I use it a lot):
Code:
Creating filesystem with parameters:
Size: 1034944512
Block size: 4096
Blocks per group: 32768
Inodes per group: 7904
Inode size: 256
Journal blocks: 3948
Label:
Blocks: 252672
Block groups: 8
Reserved block group size: 63
Created filesystem with 11/63232 inodes and 8244/252672 blocks
...
Found new backup image: /sdcard/clockworkmod/backup/2013-12-26.17.17.06//sd-ext.ext4.tar
Restoring sd-ext...
...
Code:
~ # [b]ls -l /sd-ext/[/b]
drwxrwx--x 2 system system 4096 Dec 22 12:54 dalvik-cache
drwxrwx--x 2 system system 4096 Dec 22 12:54 data
drwx------ 2 root root 4096 Dec 17 10:14 lost+found
~ #
- I can restore the boot image (and recovery of course):
Code:
...
Checking MD5 sums...
boot.img: OK
...
Erasing boot before restore...
I:Formatting unknown device.
Restoring boot image...
Restore complete!
- I can Install boot images inside zip files from sdcard:
Code:
-- Installing: /sdcard/update_boot.zip
Finding update package...
I:Update location: /sdcard/update_boot.zip
Opening update package...
Installing update...
########################
# Doc Modded #
# new boot image #
########################
Installing Boot...
script result was [ ]
Installation Completed!!!!
- I can install zip files from sideload:
Code:
Sideload started ...
Now send the package you want to apply
to the device with "adb sideload <filename>"...
sideload_service invoked
adbd exiting after successful sideload
E:listen on USB
E:userid is 2000
E:Event loop starting
Restarting adbd...
Finding update package...
I:Update location: /tmp/update.zip
Opening update package...
Installing update...
if you read this, you
own a relaxed recovery!
Cheers :)
~ #
- I can "wipe cache":
Code:
-- Wiping cache...
Formatting /cache...
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
Created filesystem with 11/32768 inodes and 4206/131072 blocks
Cache wipe complete.
- I can "wipe data/factory reset" :
Code:
-- Wiping data...
Formatting /data...
Creating filesystem with parameters:
Size: 2172633088
Block size: 4096
Blocks per group: 32768
Inodes per group: 7808
Inode size: 256
Journal blocks: 8287
Label:
Blocks: 530428
Block groups: 17
Reserved block group size: 135
Created filesystem with 11/132736 inodes and 17442/530428 blocks
warning: wipe_block_device: Wipe via secure discard failed, used discard instead
...
Data wipe complete.
/tmp #
Notice: Actually this "CWM build" deals with /data encryption so ther is no need to apply any patch after factory reset
I took an extra-check with the following 'shell command' before and after the wipe action:
Code:
/ # [b]tune2fs -l /dev/block/mmcblk0p25[/b]
...
looking for no relevant differences!
..after boot... everything fine!
- Last but not least:
- I fully restored the previously backupped firmware:
Code:
...
...
Restore complete!
Easy Play
What's Wrong in this recovery?
I Dont Know...
Wish List?
Sure: I cannot handle /efs partition via 'menu options'...
...and everybody knows how dangerous could be wander around it
Doc_cheilvenerdi.org said:
News about CWM 6.0.2.8 from CyanogenMod 10.0 (Jellybean 4.1.2):
I don't have a Github account (I'm not a developer) so I'll post here exactly what I did to build and set "up and running" this ClockWorkMod Recovery!
First of all, in my Google Drive you'll find everything we are Talking about... the experimental device tree, the recovery Odin archive, tools, binaries, ...
On first build everything was fine but the LCD screen didn't light up...
...Recovery was running, anyway, but I could not see anything...
...I could, perhaps, control the phone from PC with "adb shell"!
Code:
[email protected]:~$ [b]adb shell[/b]
~ # [b]ls[/b]
cache init.rc sdcard1
data preload sys
default.prop proc system
dev res tmp
efs root ueventd.goldfish.rc
etc sbin ueventd.rc
fstab.sp8810 sd-ext ueventd.sp8810.rc
init sdcard
~ #
Recovery log recorded the problem:
Code:
...
failed to put fb0 info
...
It's a framebuffer problem and the solution is pretty known; I pasted it from TeamRegular repository and put inside BoardConfig.mk with related sources:
Code:
...
BOARD_CUSTOM_GRAPHICS := ../../../device/samsung/sp8810/recovery/graphics.c
...
Well done! Recovery 6.0.2.8 up and running
Now testing:
- I can mount/unmount and list all filesystems
- I can backup the current firmware
- I can format and restore the external second partition (I use it a lot):
Code:
Creating filesystem with parameters:
Size: 1034944512
Block size: 4096
Blocks per group: 32768
Inodes per group: 7904
Inode size: 256
Journal blocks: 3948
Label:
Blocks: 252672
Block groups: 8
Reserved block group size: 63
Created filesystem with 11/63232 inodes and 8244/252672 blocks
...
Found new backup image: /sdcard/clockworkmod/backup/2013-12-26.17.17.06//sd-ext.ext4.tar
Restoring sd-ext...
...
Code:
~ # [b]ls -l /sd-ext/[/b]
drwxrwx--x 2 system system 4096 Dec 22 12:54 dalvik-cache
drwxrwx--x 2 system system 4096 Dec 22 12:54 data
drwx------ 2 root root 4096 Dec 17 10:14 lost+found
~ #
- I can restore the boot image (and recovery of course):
Code:
...
Checking MD5 sums...
boot.img: OK
...
Erasing boot before restore...
I:Formatting unknown device.
Restoring boot image...
Restore complete!
- I can Install boot images inside zip files from sdcard:
Code:
-- Installing: /sdcard/update_boot.zip
Finding update package...
I:Update location: /sdcard/update_boot.zip
Opening update package...
Installing update...
########################
# Doc Modded #
# new boot image #
########################
Installing Boot...
script result was [ ]
Installation Completed!!!!
- I can install zip files from sideload:
Code:
Sideload started ...
Now send the package you want to apply
to the device with "adb sideload <filename>"...
sideload_service invoked
adbd exiting after successful sideload
E:listen on USB
E:userid is 2000
E:Event loop starting
Restarting adbd...
Finding update package...
I:Update location: /tmp/update.zip
Opening update package...
Installing update...
if you read this, you
own a relaxed recovery!
Cheers :)
~ #
- I can "wipe cache":
Code:
-- Wiping cache...
Formatting /cache...
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
Created filesystem with 11/32768 inodes and 4206/131072 blocks
Cache wipe complete.
- I can "wipe data/factory reset" :
Code:
-- Wiping data...
Formatting /data...
Creating filesystem with parameters:
Size: 2172633088
Block size: 4096
Blocks per group: 32768
Inodes per group: 7808
Inode size: 256
Journal blocks: 8287
Label:
Blocks: 530428
Block groups: 17
Reserved block group size: 135
Created filesystem with 11/132736 inodes and 17442/530428 blocks
warning: wipe_block_device: Wipe via secure discard failed, used discard instead
...
Data wipe complete.
/tmp #
Notice: Actually this "CWM build" deals with /data encryption so ther is no need to apply any patch after factory reset
I took an extra-check with the following 'shell command' before and after the wipe action:
Code:
/ # [b]tune2fs -l /dev/block/mmcblk0p25[/b]
...
looking for no relevant differences!
..after boot... everything fine!
- Last but not least:
- I fully restored the previously backupped firmware:
Code:
...
...
Restore complete!
Easy Play
What's Wrong in this recovery?
I Dont Know...
Wish List?
Sure: I cannot handle /efs partition via 'menu options'...
...and everybody knows how dangerous could be wander around it
Click to expand...
Click to collapse
Will dis wrk on s5282...??
Pls say Yes...
Yup u can use it
Sent from my GT-S5282 using Tapatalk
thanks
:good:
Doc_cheilvenerdi.org said:
News about CWM 6.0.2.8 from CyanogenMod 10.0 (Jellybean 4.1.2):
I don't have a Github account (I'm not a developer) so I'll post here exactly what I did to build and set "up and running" this ClockWorkMod Recovery!
First of all, in my Google Drive you'll find everything we are Talking about... the experimental device tree, the recovery Odin archive, tools, binaries, ...
On first build everything was fine but the LCD screen didn't light up...
...Recovery was running, anyway, but I could not see anything...
...I could, perhaps, control the phone from PC with "adb shell"!
Code:
[email protected]:~$ [b]adb shell[/b]
~ # [b]ls[/b]
cache init.rc sdcard1
data preload sys
default.prop proc system
dev res tmp
efs root ueventd.goldfish.rc
etc sbin ueventd.rc
fstab.sp8810 sd-ext ueventd.sp8810.rc
init sdcard
~ #
Recovery log recorded the problem:
Code:
...
failed to put fb0 info
...
It's a framebuffer problem and the solution is pretty known; I pasted it from TeamRegular repository and put inside BoardConfig.mk with related sources:
Code:
...
BOARD_CUSTOM_GRAPHICS := ../../../device/samsung/sp8810/recovery/graphics.c
...
Well done! Recovery 6.0.2.8 up and running
Now testing:
- I can mount/unmount and list all filesystems
- I can backup the current firmware
- I can format and restore the external second partition (I use it a lot):
Code:
Creating filesystem with parameters:
Size: 1034944512
Block size: 4096
Blocks per group: 32768
Inodes per group: 7904
Inode size: 256
Journal blocks: 3948
Label:
Blocks: 252672
Block groups: 8
Reserved block group size: 63
Created filesystem with 11/63232 inodes and 8244/252672 blocks
...
Found new backup image: /sdcard/clockworkmod/backup/2013-12-26.17.17.06//sd-ext.ext4.tar
Restoring sd-ext...
...
Code:
~ # [b]ls -l /sd-ext/[/b]
drwxrwx--x 2 system system 4096 Dec 22 12:54 dalvik-cache
drwxrwx--x 2 system system 4096 Dec 22 12:54 data
drwx------ 2 root root 4096 Dec 17 10:14 lost+found
~ #
- I can restore the boot image (and recovery of course):
Code:
...
Checking MD5 sums...
boot.img: OK
...
Erasing boot before restore...
I:Formatting unknown device.
Restoring boot image...
Restore complete!
- I can Install boot images inside zip files from sdcard:
Code:
-- Installing: /sdcard/update_boot.zip
Finding update package...
I:Update location: /sdcard/update_boot.zip
Opening update package...
Installing update...
########################
# Doc Modded #
# new boot image #
########################
Installing Boot...
script result was [ ]
Installation Completed!!!!
- I can install zip files from sideload:
Code:
Sideload started ...
Now send the package you want to apply
to the device with "adb sideload <filename>"...
sideload_service invoked
adbd exiting after successful sideload
E:listen on USB
E:userid is 2000
E:Event loop starting
Restarting adbd...
Finding update package...
I:Update location: /tmp/update.zip
Opening update package...
Installing update...
if you read this, you
own a relaxed recovery!
Cheers :)
~ #
- I can "wipe cache":
Code:
-- Wiping cache...
Formatting /cache...
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
Created filesystem with 11/32768 inodes and 4206/131072 blocks
Cache wipe complete.
- I can "wipe data/factory reset" :
Code:
-- Wiping data...
Formatting /data...
Creating filesystem with parameters:
Size: 2172633088
Block size: 4096
Blocks per group: 32768
Inodes per group: 7808
Inode size: 256
Journal blocks: 8287
Label:
Blocks: 530428
Block groups: 17
Reserved block group size: 135
Created filesystem with 11/132736 inodes and 17442/530428 blocks
warning: wipe_block_device: Wipe via secure discard failed, used discard instead
...
Data wipe complete.
/tmp #
Notice: Actually this "CWM build" deals with /data encryption so ther is no need to apply any patch after factory reset
I took an extra-check with the following 'shell command' before and after the wipe action:
Code:
/ # [b]tune2fs -l /dev/block/mmcblk0p25[/b]
...
looking for no relevant differences!
..after boot... everything fine!
- Last but not least:
- I fully restored the previously backupped firmware:
Code:
...
...
Restore complete!
Easy Play
What's Wrong in this recovery?
I Dont Know...
Wish List?
Sure: I cannot handle /efs partition via 'menu options'...
...and everybody knows how dangerous could be wander around it
Click to expand...
Click to collapse
---------- Post added at 12:12 PM ---------- Previous post was at 12:09 PM ----------
after cwm recovery 6 when cm 10.1 will release
Here is the screenshot. Check it out. Its tested by me on my s5282.
Here is screenshots. Tested by me on my s5282. I have also tested geatures like wipe data and back up rom ans flash zip from sd card and its working perfecly. Sure you should go for it
Sent from my GT-S5282 using Tapatalk
rahulsinghal said:
Here is screenshots. Tested by me on my s5282. I have also tested geatures like wipe data and back up rom ans flash zip from sd card and its working perfecly. Sure you should go for it
Sent from my GT-S5282 using Tapatalk
Click to expand...
Click to collapse
GR8...Congratulations....now we can expect a cm rom for our star.....
I know you guys must be counting on me for compiling. But I cant untill u guys setup a working device tree and kernel. Also my pc cant compile cm as I have a pc with very low spec. Sorry
Although I will still try but I cant promise anything since I have never worked on a device like this. Spreadtrum cpus are pretty much hard to hack.
also dudes I know how much your excited but we need to keep all development threads on topic!
Its Going To Be LEGEND--wait for it--DARY!- Barney Stinson(How I Met Your Mother)
Doc_cheilvenerdi.org said:
News about CWM 6.0.2.8 from CyanogenMod 10.0 (Jellybean 4.1.2):
I don't have a Github account (I'm not a developer) so I'll post here exactly what I did to build and set "up and running" this ClockWorkMod Recovery!
First of all, in my Google Drive you'll find everything we are Talking about... the experimental device tree, the recovery Odin archive, tools, binaries, ...
On first build everything was fine but the LCD screen didn't light up...
...Recovery was running, anyway, but I could not see anything...
...I could, perhaps, control the phone from PC with "adb shell"!
Code:
[email protected]:~$ [b]adb shell[/b]
~ # [b]ls[/b]
cache init.rc sdcard1
data preload sys
default.prop proc system
dev res tmp
efs root ueventd.goldfish.rc
etc sbin ueventd.rc
fstab.sp8810 sd-ext ueventd.sp8810.rc
init sdcard
~ #
Recovery log recorded the problem:
Code:
...
failed to put fb0 info
...
It's a framebuffer problem and the solution is pretty known; I pasted it from TeamRegular repository and put inside BoardConfig.mk with related sources:
Code:
...
BOARD_CUSTOM_GRAPHICS := ../../../device/samsung/sp8810/recovery/graphics.c
...
Well done! Recovery 6.0.2.8 up and running
Now testing:
- I can mount/unmount and list all filesystems
- I can backup the current firmware
- I can format and restore the external second partition (I use it a lot):
Code:
Creating filesystem with parameters:
Size: 1034944512
Block size: 4096
Blocks per group: 32768
Inodes per group: 7904
Inode size: 256
Journal blocks: 3948
Label:
Blocks: 252672
Block groups: 8
Reserved block group size: 63
Created filesystem with 11/63232 inodes and 8244/252672 blocks
...
Found new backup image: /sdcard/clockworkmod/backup/2013-12-26.17.17.06//sd-ext.ext4.tar
Restoring sd-ext...
...
Code:
~ # [b]ls -l /sd-ext/[/b]
drwxrwx--x 2 system system 4096 Dec 22 12:54 dalvik-cache
drwxrwx--x 2 system system 4096 Dec 22 12:54 data
drwx------ 2 root root 4096 Dec 17 10:14 lost+found
~ #
- I can restore the boot image (and recovery of course):
Code:
...
Checking MD5 sums...
boot.img: OK
...
Erasing boot before restore...
I:Formatting unknown device.
Restoring boot image...
Restore complete!
- I can Install boot images inside zip files from sdcard:
Code:
-- Installing: /sdcard/update_boot.zip
Finding update package...
I:Update location: /sdcard/update_boot.zip
Opening update package...
Installing update...
########################
# Doc Modded #
# new boot image #
########################
Installing Boot...
script result was [ ]
Installation Completed!!!!
- I can install zip files from sideload:
Code:
Sideload started ...
Now send the package you want to apply
to the device with "adb sideload <filename>"...
sideload_service invoked
adbd exiting after successful sideload
E:listen on USB
E:userid is 2000
E:Event loop starting
Restarting adbd...
Finding update package...
I:Update location: /tmp/update.zip
Opening update package...
Installing update...
if you read this, you
own a relaxed recovery!
Cheers :)
~ #
- I can "wipe cache":
Code:
-- Wiping cache...
Formatting /cache...
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
Created filesystem with 11/32768 inodes and 4206/131072 blocks
Cache wipe complete.
- I can "wipe data/factory reset" :
Code:
-- Wiping data...
Formatting /data...
Creating filesystem with parameters:
Size: 2172633088
Block size: 4096
Blocks per group: 32768
Inodes per group: 7808
Inode size: 256
Journal blocks: 8287
Label:
Blocks: 530428
Block groups: 17
Reserved block group size: 135
Created filesystem with 11/132736 inodes and 17442/530428 blocks
warning: wipe_block_device: Wipe via secure discard failed, used discard instead
...
Data wipe complete.
/tmp #
Notice: Actually this "CWM build" deals with /data encryption so ther is no need to apply any patch after factory reset
I took an extra-check with the following 'shell command' before and after the wipe action:
Code:
/ # [b]tune2fs -l /dev/block/mmcblk0p25[/b]
...
looking for no relevant differences!
..after boot... everything fine!
- Last but not least:
- I fully restored the previously backupped firmware:
Code:
...
...
Restore complete!
Easy Play
What's Wrong in this recovery?
I Dont Know...
Wish List?
Sure: I cannot handle /efs partition via 'menu options'...
...and everybody knows how dangerous could be wander around it
Click to expand...
Click to collapse
Lol i have uploaded all those codes to github. http://github.com/batman38102/android_device_samsung_mint
Hi,
I have searched the forums and still haven't found any useful information.
I've been trying to edit a ubifs image (system.img) for a generic mediatek tablet.
These are the many things I have tried:
1) Edit the boot.img so that ro.secure=0 etc to see if I can get root. Unfortunately selinux is enabled and I don't even have busybox on the system (something called toolbox)
2) Work out what nand flash is being used (in my case its - SanDisk SDTNRGAMA 64G 3.3V 8-bit). And emulate the nand by using nandsim on a linux computer, but it causes a segmentation fault:
Code:
sudo modprobe nanDsim id_bytes=0x45,0xde,0x94,0x93,0x76,0x50 cache_file=./test.img
Note - I have included a spelling mistake (nanDsim should be nandsim) because I dont' want anyone to just cut and paste this command - it causes a segmentation fault on Ubuntu and Debian and I have found that if you are running on an ssd system it will hard lock your pc! (You have been warned).
3) Use ubireader (github.com/jrspruitt/ubi_reader).
Code:
$ ubireader_display_info ./system.img
UBI File
---------------------
Min I/O: 16384
LEB Size: 4161536
PEB Size: 4194304
Total Block Count: 122
Data Block Count: 120
Layout Block Count: 2
Internal Volume Block Count: 0
Unknown Block Count: 0
First UBI PEB Number: 0
Image: 1101756791
---------------------
Image Sequence Num: 1101756791
Volume Name:system
PEB Range: 0 - 121
Volume: system
---------------------
Vol ID: 0
Name: system
Block Count: 120
Volume Record
---------------------
alignment: 1
crc: 3336263623
data_pad: 0
errors:
flags: autoresize
name: system
name_len: 6
padding:
rec_index: 0
reserved_pebs: 248
upd_marker: 0
vol_type: dynamic
but when I run 'ubireader_extract_files' I get all the files, but they are all corrupted.
I'm currently trying to use the information in the ubireader_display_info to create a blank ubifs image and using 'linux dd' to try and read the image that I have.
Has anyone got any tips on how to progress, your help and advice would be appreciated.
Official LineageOS 14.1 for Samsung Galaxy Note 8.0 GT-N51xx
### REQUIRES FULL WIPE A.K.A. CLEAN INSTALL ###
# download odin for windows
http://forum.xda-developers.com/showthread.php?t=2711451
# flash this recovery via odin (AP button)
https://forum.xda-developers.com/galaxy-note-8-0/development/recovery-twrp-2-8-5-0-t3035004
# unofficial nightly build
https://visi0nary.de/builds/full/
# official weekly build - n5100 3G
https://download.lineageos.org/n5100
# official weekly build - n5110 WIFI
https://download.lineageos.org/n5110
# official weekly build - n5120 LTE
https://download.lineageos.org/n5120
# flash gapps via recovery
http://opengapps.org/
Thanks a lot to @BlueFlame4 and @walter79 for their build server !
XDA:DevDB Information
[ROM] Official LineageOS 14.1 for GT-N51xx, ROM for the Samsung Galaxy Note 8.0
Contributors
rgib
Source Code: https://github.com/LineageOS/android_kernel_samsung_smdk4412/tree/cm-14.1
ROM OS Version: 7.x Nougat
Version Information
Status: Alpha
Created 2017-01-06
Last Updated 2017-03-06
Congrats Sir. Always the best. Thank you
Congratulations Roberto! You should be really proud of this as a first release.
I promise you all you will NOT be disappointed with this first Lineage release and marshmallow will be but a distant memory..... ?
Thanks Roberto. Excellent effort. ???
Sent from my GT-N5120 using Tapatalk
Just for information, for my N5100 the SIM-card was not detected after a dirty flash. Didn't want to wipe and clean flash so I went back and can't provide logs. As written, just for information.
mielletseed said:
Just for information, for my N5100 the SIM-card was not detected after a dirty flash. Didn't want to wipe and clean flash so I went back and can't provide logs. As written, just for information.
Click to expand...
Click to collapse
New OS, therefore requires a clean flash to start with, a dirty would just cause no end of pain...
mielletseed said:
Just for information, for my N5100 the SIM-card was not detected after a dirty flash. Didn't want to wipe and clean flash so I went back and can't provide logs. As written, just for information.
Click to expand...
Click to collapse
Try to backup you cm-13.0. Then clean install my unofficial LineageOS 14.1 build and report if you get SIM-card.
Mine works.
rgib said:
Try to backup you cm-13.0. Then clean install my unofficial LineageOS 14.1 build and report if you get SIM-card.
Mine works.
Click to expand...
Click to collapse
After a full wipe I got SIM-PIN-dialog, seems to be working
No I try to use your build and restore my data ...
@rgib: an other information: there were two errors while installing.
Code:
I:operation_start: 'Flashing'
Installing zip file '/external_sd/0_Installation/lineage-14.1-20170106-UNOFFICIAL-n5100.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment initialized.
Target: samsung/kona3gxx/kona3g:4.4.4/KTU84P/N5100ZTCNL6:user/release-keysTarget: samsung/kona3gxx/kona3g:4.4.4/KTU84P/N5100ZTCNL6:user/release-keys
detected filesystem ext4 for /dev/block/platform/dw_mmc/by-name/SYSTEM
detected filesystem ext4 for /dev/block/platform/dw_mmc/by-name/SYSTEM
about to run program [/tmp/install/bin/backuptool.sh] with 2 args
run_program: child exited with status 127
about to run program [/tmp/install/bin/otasigcheck.sh] with 1 args
Patching system image unconditionally...
performing update
Patching system image unconditionally...
blockimg version is 4
maximum stash entries 0
creating stash /cache/recovery/13c23145f94d68015632f2cd29899c1aaf9ad199/
1557766144 bytes free on /cache (0 needed)
erasing 224813 blocks
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 757 blocks of new data
zeroing 1024 blocks
zeroing 1024 blocks
zeroing 1024 blocks
zeroing 1024 blocks
zeroing 1024 blocks
zeroing 1024 blocks
zeroing 1024 blocks
zeroing 1024 blocks
zeroing 1024 blocks
zeroing 1024 blocks
zeroing 1024 blocks
zeroing 734 blocks
wrote 168403 blocks; expected 168403
stashed 0 blocks
max alloc needed was 4096
[COLOR="Red"]E:unknown command [log]
E:unknown command [log][/COLOR]
deleting stash 13c23145f94d68015632f2cd29899c1aaf9ad199
detected filesystem ext4 for /dev/block/platform/dw_mmc/by-name/SYSTEM
detected filesystem ext4 for /dev/block/platform/dw_mmc/by-name/SYSTEM
about to run program [/tmp/install/bin/backuptool.sh] with 2 args
/tmp/install/bin/backuptool.sh: cd: line 113: can't cd to /tmp/addon.d/
md5sum: can't open '*sh': No such file or directory
script succeeded: result was [1.000000]I:Updater process ended with RC=0
I:Legacy property environment disabled.
Updating partition details...
I:Data backup size is 0MB, free: 8872MB.
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
...done
I:Set page: 'flash_done'
I:operation_end - status=0
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'advanced'
I:Set page: 'confirm_action'
I:Set page: 'action_page'
I:operation_start: 'Copy Log'
I:Copying file /tmp/recovery.log to /external_sd/recovery.log
@rgib
Installed your lineage-14.1-20170107-UNOFFICIAL-n5120.zip from firmware stock after a wipe data and cache.
Gps not work
Sim not work
Bluetooth instable
wifi with mac correct :works
camera works
Here my logs
Thanks for your what you are doing for us and Happy new Year!!
mielletseed said:
@rgib: an other information: there were two errors while installing.
Code:
E:unknown command [log]
E:unknown command [log
Click to expand...
Click to collapse
All cm14 based builds have given / are likely to give this error. It's nothing to bother about.
kaworuxda said:
@rgib
Installed your lineage-14.1-20170107-UNOFFICIAL-n5120.zip from firmware stock after a wipe data and cache.
Gps not work
Sim not work
Bluetooth instable
wifi with mac correct :works
camera works
Here my logs
Thanks for your what you are doing for us and Happy new Year!!
Click to expand...
Click to collapse
Flashed Rom found the same as quoted
Logs attached
Cheers
Al
tu sei il migliore
installed the 7.01.2017 build for gt-n5100 :
GPS/location works fine
SIM works fine ( incoming outgoing ok, haven't tested data though ...)
WIFI Mac ... Works fine
Bluetooth transfers ... works fine
camera can take photos but not videos app crashes in video mode
SD cards work but inbuilt file manager won't open SD card files, asks for root access mode, tried enabling root access for apps and adb in dev mode as well as file manager but nothing happens...
wish you a very Happy New Year and thank you for your efforts .....
arnob2014 said:
camera can take photos but not videos app crashes in video mode
SD cards work but inbuilt file manager won't open SD card files, asks for root access mode, tried enabling root access for apps and adb in dev mode as well as file manager but nothing happens...
Click to expand...
Click to collapse
CM file manager is very buggy still - try deleting a directory named ".android_secure" from your sdcard if it exists (but you will need different file manager to do this, others will work)
Camera - try 3rd party apps, e.g. camu, cameringo, open camera - some / all / none may work better
All work fine..thanks very much dev for your works..thumb up.!
ROM - lineage-14.1-20170107-UNOFFICIAL-n5100
GApps - open_gapps-arm-7.1-pico-20170107
Root(systemless) - SR2-SuperSU-v2.79-SR2-20170103215521
Camera - Open Camera
@rgib FYI if you wanna use the built in update mechanism from LOS use https://visi0nary.de/api as OTA host. Example: https://github.com/visi0nary/android_device_elephone_p8000/blob/cm-12.1/system.prop#L170
Buff99 said:
All cm14 based builds have given / are likely to give this error. It's nothing to bother about.
Click to expand...
Click to collapse
I can confirm that. Exactly the same errors during installation. Beside that I get the "new SIM card detected" error which was there sometimes in CM13. I need to do some further testing, but the device seems pretty stable.
rgib, you really make me appreciate my Note 8 after all this years. Thanks!
i'm very impressed with the first build ! thanks a lot Roberto !
TibReg said:
I can confirm that. Exactly the same errors during installation. Beside that I get the "new SIM card detected" error which was there sometimes in CM13. I need to do some further testing, but the device seems pretty stable.
rgib, you really make me appreciate my Note 8 after all this years. Thanks!
Click to expand...
Click to collapse
Try to update baseband
I read the super block from the UFS memory chip on a Huawei P30
Code:
Welcome to Medusa Pro Software version 2.1.0.
Started.
Reader #0: Generic EMV Smartcard Reader 0
Loading firmware. Please wait... Done.
Selected UFS interface.
Selected PIN - CONNECTOR socket.
Please use USB3.0 for better speed.
Connected. Reading information.
Manufacturer name: SAMSUNG
Product name: KLUDG4U1EA-B0C1
Serial Number: 365c76002705
OEM ID: SAMSUNG_OEM_ID
Page size : 4096 B
Block size : 4096 B
Block count : 31246336
Size : 119.20 GB (122056.00 MB)
AttrRefClkFreeq = 0
MaxDataInSize = 32768
MaxDataOutSize = 32768
Connect successful.
---------------------------------------------------------------
Physical partition number: 0
Block count : 1024 (0x400)
Size : 4.00 MB
Physical partition number: 1
Block count : 1024 (0x400)
Size : 4.00 MB
Physical partition number: 2
Block count : 2048 (0x800)
Size : 8.00 MB
P00: GPT (00000000, 00000080) 512 KB
P01: frp (00000080, 00000080) 512 KB
P02: persist (00000100, 00000600) 6 MB
P03: reserved1 (00000700, 00000100) 1024 KB
Physical partition number: 3
Block count : 31234048 (0x1DC9800)
Size : 119.15 GB (122008.00 MB)
P00: GPT (00000000, 00000080) 512 KB
P01: vrl (00000080, 00000080) 512 KB
P02: vrl_backup (00000100, 00000080) 512 KB
P03: modem_secure (00000180, 00000880) 8.5 MB
P04: nvme (00000A00, 00000500) 5 MB
P05: certification (00000F00, 00000100) 1024 KB
P06: oeminfo (00001000, 00006000) 96 MB
P07: secure_storage (00007000, 00002000) 32 MB
P08: modemnvm_factory (00009000, 00001000) 16 MB
P09: modemnvm_backup (0000A000, 00001000) 16 MB
P10: modemnvm_img (0000B000, 00002200) 34 MB
P11: hisee_encos (0000D200, 00000400) 4 MB
P12: veritykey (0000D600, 00000100) 1024 KB
P13: ddr_para (0000D700, 00000100) 1024 KB
P14: lowpower_para (0000D800, 00000100) 1024 KB
P15: batt_tp_para (0000D900, 00000100) 1024 KB
P16: reserved2 (0000DA00, 00001900) 25 MB
P17: splash2 (0000F300, 00005000) 80 MB
P18: bootfail_info (00014300, 00000200) 2048 KB
P19: misc (00014500, 00000200) 2048 KB
P20: dfx (00014700, 00001000) 16 MB
P21: rrecord (00015700, 00001000) 16 MB
P22: cache (00016700, 00006800) 104 MB
P23: fw_lpm3 (0001CF00, 00000100) 1024 KB
P24: reserved3 (0001D000, 00000600) 6 MB
P25: ivp (0001D600, 00000300) 3072 KB
P26: hdcp (0001D900, 00000100) 1024 KB
P27: hisee_img (0001DA00, 00000400) 4 MB
P28: hhee (0001DE00, 00000400) 4 MB
P29: hisee_fs (0001E200, 00000800) 8 MB
P30: fastboot (0001EA00, 00000C00) 12 MB
P31: vector (0001F600, 00000400) 4 MB
P32: isp_boot (0001FA00, 00000200) 2048 KB
P33: isp_firmware (0001FC00, 00000E00) 14 MB
P34: fw_hifi (00020A00, 00000C00) 12 MB
P35: teeos (00021600, 00000800) 8 MB
P36: sensorhub (00021E00, 00001000) 16 MB
P37: erecovery_kernel (00022E00, 00001800) 24 MB
P38: erecovery_ramdisk (00024600, 00002000) 32 MB
P39: erecovery_vendor (00026600, 00001000) 16 MB
P40: kernel (00027600, 00001800) 24 MB
P41: eng_system (00028E00, 00000C00) 12 MB
P42: recovery_ramdisk (00029A00, 00002000) 32 MB
P43: recovery_vendor (0002BA00, 00001000) 16 MB
P44: dts (0002CA00, 00000100) 1024 KB
P45: dto (0002CB00, 00001400) 20 MB
P46: trustfirmware (0002DF00, 00000200) 2048 KB
P47: modem_fw (0002E100, 00003800) 56 MB
P48: eng_vendor (00031900, 00000C00) 12 MB
P49: modem_patch_nv (00032500, 00000400) 4 MB
P50: modem_driver (00032900, 00001400) 20 MB
P51: reserved4 (00033D00, 00000C00) 12 MB
P52: ramdisk (00034900, 00000200) 2048 KB
P53: vbmeta_system (00034B00, 00000100) 1024 KB
P54: vbmeta_vendor (00034C00, 00000100) 1024 KB
P55: vbmeta_odm (00034D00, 00000100) 1024 KB
P56: vbmeta_cust (00034E00, 00000100) 1024 KB
P57: vbmeta_hw_product (00034F00, 00000100) 1024 KB
P58: recovery_vbmeta (00035000, 00000200) 2048 KB
P59: erecovery_vbmeta (00035200, 00000200) 2048 KB
P60: vbmeta (00035400, 00000400) 4 MB
P61: modemnvm_update (00035800, 00001000) 16 MB
P62: modemnvm_cust (00036800, 00001000) 16 MB
P63: patch (00037800, 00002000) 32 MB
P64: preas (00039800, 00012800) 296 MB
P65: preavs (0004C000, 00002000) 32 MB
[B][COLOR="Red"]P66: super (0004E000, 00160000) 5.5 GB[/COLOR][/B]
P67: version (001AE000, 00024000) 576 MB
P68: preload (001D2000, 00047800) 1144 MB
P69: userdata (00219800, 01BB0000) 110.8 GB
Backuping nvme partition...
Opening C:/Program Files/Medusa Pro Software/Backups/SAMSUNG_KLUDG4U1EA-B0C1_nvme_0xa00_0x500_11_06_2020_17_48_51.bin file...
Reading. Please wait... Done.
Elapsed time 00:00:00
SW: 2.1.0; FW: 1.00.
Backuping oeminfo partition...
Opening C:/Program Files/Medusa Pro Software/Backups/SAMSUNG_KLUDG4U1EA-B0C1_oeminfo_0x1000_0x6000_11_06_2020_17_48_51.bin file...
Reading. Please wait... Done.
Elapsed time 00:00:05
SW: 2.1.0; FW: 1.00.
---------------------------------------------------------------Searching Android build info...
Not found
---------------------------------------------------------------RPMB: Counter of the successful data write requests = 196.
Partition table has been found on device.
RPMB: Counter of the successful data write requests = 196.
Save to E:/tmp file...
Reading partition super... Done.
Reading is finished.
SW: 2.1.0; FW: 1.00.
Then I used the tool "lpunpack" to unpack super. Img, and got this
Code:
cust.img
hw_product.img
odm.img
system.img
vendor.img
Oddly, though, none of these files are in ext4 or Android Sparse:
Code:
λ file *
cust.img: data
hw_product.img: data
odm.img: data
system.img: data
vendor.img: data
I tried using the command mount under ubuntu18, but unfortunately it failed
Code:
[email protected]:~/Desktop/tmp$ sudo mount -t erofs -o loop system.img /mnt
mount: /mnt: wrong fs type, bad option, bad superblock on /dev/loop9, missing codepage or helper program, or other error.
I've extracted using: imjtool.
http://newandroidbook.com/tools/imjtool.html
VD171 said:
I've extracted using: imjtool.
http://newandroidbook.com/tools/imjtool.html
Click to expand...
Click to collapse
I tried, and the result is the same
They are erofs partitions.