Related
So,
I am at a loss on how to get the GN to activate USB storage in CM Recovery.
parted shows:
Code:
~ # parted /dev/block/platform/omap/omap_hsmmc.0/mmcblk0 print
Model: MMC VYL00M (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 524kB 4194kB 3670kB sbl
3 4194kB 25.2MB 21.0MB ext4 efs
4 25.2MB 33.6MB 8389kB param
5 33.6MB 37.7MB 4194kB misc
6 37.7MB 41.9MB 4194kB dgs
7 41.9MB 50.3MB 8389kB boot
8 50.3MB 62.8MB 12.5MB recovery
13 62.8MB 62.9MB 65.5kB metadata
9 62.9MB 79.7MB 16.8MB radio
10 79.7MB 765MB 686MB ext4 system
11 765MB 1218MB 453MB ext4 cache
12 1218MB 15.8GB 14.5GB ext4 userdata
so, I see part 12 as my "/mnt/sdcard" partition..
previous versions I looked at had syntax like:
Code:
case $1 in
on)
echo /dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file
echo "USB Mass Storage enabled"
;;
off)
echo "" > /sys/devices/platform/usb_mass_storage/lun0/file
echo "USB Mass Storage disabled"
;;
--)
;;
On this device, there is:
Code:
[email protected]:/sys/devices/platform/omap/omap_hsmmc.0
lrwxrwxrwx root root 2012-01-26 10:15 driver -> ../../../../bus/platform/drivers/omap_hsmmc
-r--r--r-- root root 4096 2012-01-26 10:15 microamps_requested_omap_hsmmc.0-vmmc
drwxr-xr-x root root 2012-01-26 09:49 mmc_host
-r--r--r-- root root 4096 2012-01-26 10:15 modalias
drwxr-xr-x root root 2012-01-26 09:49 power
lrwxrwxrwx root root 2012-01-26 10:15 subsystem -> ../../../../bus/platform
-rw-r--r-- root root 4096 2012-01-26 09:49 uevent
Anyone have any ideas how to do this before I spend a day figuring it out?
Thanks!
Anyone have any ideas how to do this [...] ?
Click to expand...
Click to collapse
You can't. There is no UMS/mass storage support with the Galaxy Nexus.
(This thread should be in the q&a section.)
gokpog said:
You can't. There is no UMS/mass storage support with the Galaxy Nexus.
(This thread should be in the q&a section.)
Click to expand...
Click to collapse
+1
(10 chars)
use adb push pull for your basic requirements
It's also not CM Recovery. It's Clockwork Recovery.
Also wrong section.
gokpog said:
You can't. There is no UMS/mass storage support with the Galaxy Nexus.
(This thread should be in the q&a section.)
Click to expand...
Click to collapse
There actually is.. It is in the kernel I am using, and I can successfully send a block device out it using /sys/devices/platform/omap/musb-omap2430/musb-hdrc/gadget/lun0/file
The nexus has to have it's persistent usb modes set properly (turn off MTP)..
I just cannot make it work in recovery even though it's kernel has the feature as well. Recovery is the only place I want it too
Oh well, I'll keep using ad like I have been.
Thanks
ghost_o said:
There actually is.. It is in the kernel I am using, and I can successfully send a block device out it using /sys/devices/platform/omap/musb-omap2430/musb-hdrc/gadget/lun0/file
The nexus has to have it's persistent usb modes set properly (turn off MTP)..
I just cannot make it work in recovery even though it's kernel has the feature as well. Recovery is the only place I want it too
Oh well, I'll keep using ad like I have been.
Thanks
Click to expand...
Click to collapse
ghost_o, I really want to know how you can make it work. I setted the persistent usb config to only adb (no mtp) and tried to sent the userdata block device to that lun0 but the block device is not properly sent to the usb connected computer. My goal is to be able to use an app called usb sharer or something similar.
Hey all,
So I was able to run KFU and it got me stuck on the boot screen. Got help with that and was able to run KFU again but it got stuck on removing boot check and now I'm stuck with the TWRP homescreen.
My device was recognized in device manager but in the KFU it says ADB Status: Offline and Boot Status Unknown. ADB Device List is empty.
I am unable to mount the device from TWRP it keeps failing. I am also unable to mount the sdcard partition what-so-ever.
Pooch sent me info on how to boot up via usb drive into Linux (Mint) and I can find the device in the adb device list but I am not familiar enough with Linux to know how to push the ROM to the device as well as a better/newer version of TWRP. Any help in this would be greatly appreciated. Thanks.
I sent you full instructions on how to proceed in a pm the reason I chose that system is because its nice and small it will get you going.. you only have 150 mb to work with follow instructions and you should be fine
Issues persist
Hello! So, I was able to detect my device via adb in Linux with the help of ThePooch. (thanks a bunch!!!) However we have a small problem.
I am unable to mount my SD Card partition in TWRP at all. I wasn't sure why so we tried a bunch of stuff: We tried pushing a ROM, We tried mounting it via adb in terminal on Linux... We tried "fastboot oem format"... We tried adb shell echo /dev/block/mmcblk0p12 >> /sys/devices/platform/usb_mass_storage/lun0/file
We tried updating the recovery to TWRP 2.2.2.0.
We tried a lot of things however we were very unsuccessful in this and I am still unable to click "Mount SD Card" in TWRP or format it or wipe it.
What's confusing is that I was able to push files (zips) to the sd card temporarily and see them when we click "install" on TWRP however they fail to install and anything pushed to the sd card is, or course, erased on rebooting.
Really don't know what to do at this point as I am at a loss and would appreciate any assistance in this. Thanks so much!
Boot into recovery and enter:
Code:
adb shell
parted /dev/block/mmcblk0
print
...and post the results here.
soupmagnet said:
Boot into recovery and enter:
Code:
adb shell
parted /dev/block/mmcblk0
print
...and post the results here.
Click to expand...
Click to collapse
Model: MMC MMC08G (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 262kB 524kB 262kB bootloader
3 524kB 11.0MB 10.5MB dkernel
4 11.0MB 212MB 201MB ext4 dfs
5 212MB 229MB 16.8MB recovery
6 229MB 296MB 67.1MB ext4 backup
7 296MB 307MB 10.5MB boot
8 307MB 312MB 5243kB ext4 splash
9 312MB 849MB 537MB ext4 system
10 849MB 2041MB 1192MB ext4 userdata
11 2041MB 2309MB 268MB ext4 cache
12 2309MB 7690MB 5380MB media
hmm wish I knew what I was looking at it looks to me like some things still exist even after a full wipe if I`m reading it correct glad soup knows what to look for
sphinxdog said:
Really don't know what to do at this point as I am at a loss and would appreciate any assistance in this. Thanks so much!
Click to expand...
Click to collapse
I've ran into this a couple of times and what I usually do is to delete the "media" partition, create it again with parted, name it "media", and then finally let the stock Kindle Fire recovery repair it. You may be able to skip the delete/create part and just boot into the stock recovery to see if it can repair it.
probably would work if in fact he had a working system but there isnt a bootable one at least..
Code:
Model: MMC MMC08G (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 262kB 524kB 262kB bootloader
3 524kB 11.0MB 10.5MB dkernel
4 11.0MB 212MB 201MB ext4 dfs
5 212MB 229MB 16.8MB recovery
6 229MB 296MB 67.1MB ext4 backup
7 296MB 307MB 10.5MB boot
8 307MB 312MB 5243kB ext4 splash
9 312MB 849MB 537MB ext4 system
10 849MB 2041MB 1192MB ext4 userdata
11 2041MB 2309MB 268MB ext4 cache
12 2309MB 7690MB 5380MB media
Thepooch said:
hmm wish I knew what I was looking at it looks to me like some things still exist even after a full wipe if I`m reading it correct glad soup knows what to look for
Click to expand...
Click to collapse
The 'parted' program manipulates the partition table, which basically tells the device how the storage partitions are laid out. The 'print' command used to obtain the output above just displays the information stored in the partition table. I set the output in CODE so it's easier to read. The bottom portion of the data is the more interesting part and you can see the column names there...
Number - This is the partition number. You may have seen "/dev/block/mmcblk0p5" in the past referring to the recovery partition. That number after the letter 'p' refers to the partition number.
Start - This is the offset value for where the partition begins.
End - This is the offset value for where the partition ends.
Size - This is the size of the partition calculated by the difference of the two offset values above. Imagine a ruler where your "Start" offset is the 1 inch tick mark and your "End" offset is the 6 inch tick mark. The "Size" between the tick marks... 6 - 1 is 5.
File system - This is how the partition has been formatted... ext4 is a commonly used filesystem for linux. It's blank if parted doesn't recognize the filesystem type or none has been specified.
Name - The name given to the partition. You'll recognize some as ones you've used to refer to these partitions in fastboot. FYI, userdata typically gets mounted to /data and media gets mounted to /sdcard.
Flags - Used to indicate special characteristics of the filesystem.
The significant part of the output above is the missing filesystem for the media partition. It should have a fat32 filesystem. I'll leave it to soupmagnet to explain how to fix it.
kinfauns said:
The significant part of the output above is the missing filesystem for the media partition. It should have a fat32 filesystem.
Click to expand...
Click to collapse
As always, kinfains is correct. I've dealt with an issue similar to this on my own device pretty recently, so I knew immediately what we'd be dealing with. So you're going to remove, recreate and repartition your sdcard and then you'll be all set. Needless to say, any data on your sdcard will be lost, if it isn't already. Not to worry though, considering everything you have gone through up until this point, this part should be pretty painless.
Code:
adb shell
parted /dev/block/mmcblk0
rm 12
mkpartfs primary fat32 2309 7690
name 12 media
quit
mount /sdcard
exit
adb reboot
You may not need to reboot, but in my case, I did. You'll then be able to mount your sdcard over USB, or use "adb push" to transfer a ROM to flash in recovery. Just remember to wipe System and "Factory Reset" in recovery first, or you may very well find yourself in the exact same situation as before.
Have fun.
SUCCESS!!!! That took care of it! And I was able to load up the ROM with no problem. Thanks for all the help ThePooch & SoupMagnet!!!
Sent from my Kindle Fire using xda app-developers app
Any help will be appreciated :good:
As you know backup and restore partitions can be done using dd command in linux.
I know it's not noob friendly, but since custom kernels and recoveries raises flash counter, it's a good idea.
rotohammer has made a detailed explanation here for Galaxy Tab.
So all we need the block device list for note 2
/dev/block/mmcblk0 Whole Internal Storage
/dev/block/mmcblk0p1 4194kB BOTA0
/dev/block/mmcblk0p2 4194kB BOTA1
/dev/block/mmcblk0p3 21.0MB EFS
/dev/block/mmcblk0p4 4194kB m9kefs1
/dev/block/mmcblk0p5 4194kB m9kefs2
/dev/block/mmcblk0p6 4194kB m9kefs3
/dev/block/mmcblk0p7 8389kB PARAM
/dev/block/mmcblk0p8 8389kB BOOT (Kernel)
/dev/block/mmcblk0p9 8389kB RECOVERY
/dev/block/mmcblk0p10 92.3MB RADIO (Modem)
/dev/block/mmcblk0p11 4194kB TOMBSTONES
/dev/block/mmcblk0p12 1434MB CACHE
/dev/block/mmcblk0p13 2147MB SYSTEM
/dev/block/mmcblk0p14 587MB HIDDEN
/dev/block/mmcblk0p15 8389kB OTA
/dev/block/mmcblk0p16 11.4GB USERDATA (User Accessible Storage and /DATA folder)
[email protected] said:
As you know backup and restore partitions can be done using dd command in linux.
I know it's not noob friendly, but since custom kernels and recoveries raises flash counter, it's a good idea.
rotohammer has made a detailed explanation here for Galaxy Tab.
So I need all the block device list for note 2
So far I know
/dev/block/mmcblk0p13 = /system
/dev/block/mmcblk0p12 = /cache
/dev/block/mmcblk0p16 = /data
/dev/block/mmcblk0p3 = /efs
/dev/block/mmcblk0p9 = /recovery
/dev/block/mmcblk0p8 = /boot (kernel)
I'm not a linux expert, can somebody confirm/correct these?
Click to expand...
Click to collapse
Perhaps you should find out what the mount command does before you start using dd to read and write directly to the partitions. These sort of commands don't take prisoners
I said I'm not a linux expert, it doesn't mean I'm totally noob. I'm using Lubuntu on my netbook.
I'm well aware of risks, I'm using dd on PC time to time.
Mount only shows mounted partitions. I'm asking those partitions. I couldn't find a full partitions list anywhere
There are many partitions and I want to know what they are
Code:
cat /proc/partitions
major minor #blocks name
179 0 15388672 mmcblk0
179 1 4096 mmcblk0p1
179 2 4096 mmcblk0p2
179 3 20480 mmcblk0p3
179 4 4096 mmcblk0p4
179 5 4096 mmcblk0p5
179 6 4096 mmcblk0p6
179 7 8192 mmcblk0p7
179 8 8192 mmcblk0p8
179 9 8192 mmcblk0p9
179 10 90112 mmcblk0p10
179 11 4096 mmcblk0p11
179 12 1400832 mmcblk0p12
179 13 2097152 mmcblk0p13
179 14 573440 mmcblk0p14
179 15 8192 mmcblk0p15
259 0 11141120 mmcblk0p16
179 16 62367744 mmcblk1
179 17 62351360 mmcblk1p1
[email protected]:/ # ls -l /dev/block/mmcblk*
ls -l /dev/block/mmcblk*
brw------- root root 179, 0 2013-04-01 00:14 mmcblk0
brw------- root root 179, 1 2013-04-01 00:14 mmcblk0p1
brw-rw---- system radio 179, 10 2013-04-01 00:14 mmcblk0p10
brw-rw---- system radio 179, 11 2013-04-01 00:14 mmcblk0p11
brw------- root root 179, 12 2013-04-01 00:14 mmcblk0p12
brw------- root root 179, 13 2013-04-01 00:14 mmcblk0p13
brw------- root root 179, 14 2013-04-01 00:14 mmcblk0p14
brw------- root root 179, 15 2013-04-01 00:14 mmcblk0p15
brw------- root root 259, 0 2013-04-01 00:14 mmcblk0p16
brw------- root root 179, 2 2013-04-01 00:14 mmcblk0p2
brw------- root root 179, 3 2013-04-01 00:14 mmcblk0p3
brw-rw---- system radio 179, 4 2013-04-01 00:14 mmcblk0p4
brw-rw---- system radio 179, 5 2013-04-01 00:14 mmcblk0p5
brw-rw---- system radio 179, 6 2013-04-01 00:14 mmcblk0p6
brw-rw---- system root 179, 7 2013-04-01 00:14 mmcblk0p7
brw------- root root 179, 8 2013-04-01 00:14 mmcblk0p8
brw------- root root 179, 9 2013-04-01 00:14 mmcblk0p9
brw------- root root 179, 16 2013-04-01 00:14 mmcblk1
brw------- root root 179, 17 2013-04-01 00:14 mmcblk1p1
For some reason listing partitions by-label doesn't work either for android or block devices.
Code:
[email protected]:/ # ls -l /dev/block/by-label
ls -l /dev/block/by-label
/dev/block/by-label: No such file or directory
[email protected] said:
...So far I know
/dev/block/mmcblk0p13 = /system
/dev/block/mmcblk0p12 = /cache
/dev/block/mmcblk0p16 = /data
/dev/block/mmcblk0p3 = /efs
/dev/block/mmcblk0p9 = /recovery
/dev/block/mmcblk0p8 = /boot (kernel)
I'm not a linux expert, can somebody confirm/correct these?
Click to expand...
Click to collapse
These partitions are correct. Radio/modem partition is missing. /dev/block/mmcblk0p10 = /modem/baseband/radio
Edit:
For the list of all partitions, use 'parted' command.
Partitions from the international GNote2 N7100 are:
Code:
Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. Alle Rechte vorbehalten.
C:\Users\cargo>cd tools
C:\Users\cargo\tools>adb shell
~ # ←[6nparted /dev/block/mmcblk0
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Model: MMC VTU00M (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 4194kB 8389kB 4194kB BOTA0
2 8389kB 12.6MB 4194kB BOTA1
3 12.6MB 33.6MB 21.0MB ext4 EFS
4 33.6MB 37.7MB 4194kB m9kefs1
5 37.7MB 41.9MB 4194kB m9kefs2
6 41.9MB 46.1MB 4194kB m9kefs3
7 46.1MB 54.5MB 8389kB PARAM
8 54.5MB 62.9MB 8389kB BOOT
9 62.9MB 71.3MB 8389kB RECOVERY
10 71.3MB 164MB 92.3MB RADIO
11 164MB 168MB 4194kB TOMBSTONES
12 168MB 1602MB 1434MB ext4 CACHE
13 1602MB 3750MB 2147MB ext4 SYSTEM
14 3750MB 4337MB 587MB ext4 HIDDEN
15 4337MB 4345MB 8389kB OTA
16 4345MB 15.8GB 11.4GB ext4 USERDATA
(parted)
cargobr151 said:
These partitions are correct. Radio/modem partition is missing. /dev/block/mmcblk0p10 = /modem/baseband/radio
Edit:
For the list of all partitions, use 'parted' command.
Partitions from the international GNote2 N7100 are:
Code:
Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. Alle Rechte vorbehalten.
C:\Users\cargo>cd tools
C:\Users\cargo\tools>adb shell
~ # ←[6nparted /dev/block/mmcblk0
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Model: MMC VTU00M (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 4194kB 8389kB 4194kB BOTA0
2 8389kB 12.6MB 4194kB BOTA1
3 12.6MB 33.6MB 21.0MB ext4 EFS
4 33.6MB 37.7MB 4194kB m9kefs1
5 37.7MB 41.9MB 4194kB m9kefs2
6 41.9MB 46.1MB 4194kB m9kefs3
7 46.1MB 54.5MB 8389kB PARAM
8 54.5MB 62.9MB 8389kB BOOT
9 62.9MB 71.3MB 8389kB RECOVERY
10 71.3MB 164MB 92.3MB RADIO
11 164MB 168MB 4194kB TOMBSTONES
12 168MB 1602MB 1434MB ext4 CACHE
13 1602MB 3750MB 2147MB ext4 SYSTEM
14 3750MB 4337MB 587MB ext4 HIDDEN
15 4337MB 4345MB 8389kB OTA
16 4345MB 15.8GB 11.4GB ext4 USERDATA
(parted)
Click to expand...
Click to collapse
Thank you a lot, parted is not working on mine. Probably busybox related?
Edit: Nevermind I found the executable file of parted . Worked fine. Thanks again.
You must have installed a custom recovery. (with parted command included)
Like cwm or twrp v2.4.4.0. I use twrp v2.4.4.0.
@OP updated my thread with this thread info...You can visit here
@[email protected]
So continue here
Question is if we makes tar file form dump file we have created like system.img, can we flash it with odin?
dr.ketan said:
@[email protected]
So continue here
Question is if we makes tar file form dump file we have created like system.img, can we flash it with odin?
Click to expand...
Click to collapse
Roger that
here http://forum.xda-developers.com/showthread.php?t=1777579 @das7982 well explained the instructions for Galaxy SIII
According to his post, he's recommending to make an ODIN package from only system.img
To make system.img of note 2
Code:
dd if=/dev/block/mmcblk0p13 of=/storage/extSdCard/system.img bs=4096
Here we need a linux pc or Cygwin for Windows. If we going to use Cygwin, we need to install it along with tar, md5sum commands
Code:
tar -H ustar -c system.img > system.img.tar
Then we need to make Md5 checksum
Code:
md5sum -t system.img.tar >> system.img.tar
rename it
Code:
mv system.img.tar system.img.tar.md5
I haven't tried this yet but I'll try soon
I have already made this and also in try to test it.
Sent from my GT-N7100 using xda premium
---------- Post added at 11:00 PM ---------- Previous post was at 10:55 PM ----------
I have read it, I think it shouldn't raise counter unless we have custom recovery /kernel
B'coz I don't think custom tar will raise counter, i am regularly extract recovery and kernel from stock and packing it separately in tar, it never raised counter.
Sent from my GT-N7100 using xda premium
dr.ketan said:
I have already made this and also in try to test it.
Sent from my GT-N7100 using xda premium
---------- Post added at 11:00 PM ---------- Previous post was at 10:55 PM ----------
I have read it, I think it shouldn't raise counter unless we have custom recovery /kernel
B'coz I don't think custom tar will raise counter, i am regularly extract recovery and kernel from stock and packing it separately in tar, it never raised counter.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
You're correct, stock kernel and recovery shouldn't increase the flash counter.
To backup /data we can use
Code:
adb shell
stop
busybox tar -cZvf /storage/extSdCard/data.ext4.tar --exclude media --exclude dalvik-cache /data
reboot
To restore
Code:
adb shell
stop
busybox tar -xvf /storage/extSdCard/data.ext4.tar -C /
reboot
Hello!
I have Samsung Galaxy tab 3 10.1 GT-P5210, some time ago i Tried "dd" some files in /dev/block from @moonbutt74, i was supposed to dd recovery in mmcblk0p11 but instead i did it in mmcblk0 and since then the tab is stuck on samsung logo, i tried re-flashing rom didn't help, factory setting, deleting cache, wipe system... nothing helped.
please help me!!
mohali256 said:
Hello!
I have Samsung Galaxy tab 3 10.1 GT-P5210, some time ago i Tried "dd" some files in /dev/block from @moonbutt74, i was supposed to dd recovery in mmcblk0p11 but instead i did it in mmcblk0 and since then the tab is stuck on samsung logo, i tried re-flashing rom didn't help, factory setting, deleting cache, wipe system... nothing helped.
please help me!!
Click to expand...
Click to collapse
mohali256,
that was a very bad mistake. you've written to mmcblk0, you most likely are completely irreversably bricked.
try to boot into recovery mode, then try to boot into odin mode. if you boot into recovery okay stay there and plug your tab in to
hopefully keep it charged. do this first then write back. if you cannot do either then yes your device is truly finished.
m
moonbutt74 said:
mohali256,
that was a very bad mistake. you've written to mmcblk0, you most likely are completely irreversably bricked.
try to boot into recovery mode, then try to boot into odin mode. if you boot into recovery okay stay there and plug your tab in to
hopefully keep it charged. do this first then write back. if you cannot do either then yes your device is truly finished.
m
Click to expand...
Click to collapse
cool... i can boot in to odin mode and i can boot in to recovery mode without any problem?
so what should i do? @moonbutt74
mohali256 said:
cool... i can boot in to odin mode and i can boot in to recovery mode without any problem?
so what should i do? @moonbutt74
Click to expand...
Click to collapse
@moonbutt74 It's charged and ready to go, can you please tell me what should i do?
No more rushing through things. Got it ?
mohali256 said:
@moonbutt74 It's charged and ready to go, can you please tell me what should i do?
Click to expand...
Click to collapse
M,
keep in mind this may fail, keep calm, be patient
do you have a custom recovery already installed ?
if so restore your backup.
do so then write back.
when you respond to this post, do so by clicking the reply button and i will recieve notification by email.
it speeds up the process.
m
moonbutt74 said:
M,
keep in mind this may fail, keep calm, be patient
do you have a custom recovery already installed ?
if so restore your backup.
do so then write back.
when you respond to this post, do so by clicking the reply button and i will recieve notification by email.
it speeds up the process.
m
Click to expand...
Click to collapse
I could do that but there is one problem which is that i restored my backup when I had philzadvcwm which can't be flashed using Odin or twmr, and twmr doesn't read philzadvcwm restore files.
Can't you give me the mmcblk0 file and i push to the tab using adb... Or as I read in other forums mmcblk0 is the partition table files can't you upload pit file for me
Sorry for troubling you
mohali256 said:
I could do that but there is one problem which is that i restored my backup when I had philzadvcwm which can't be flashed using Odin or twmr, and twmr doesn't read philzadvcwm restore files.
Can't you give me the mmcblk0 file and i push to the tab using adb... Or as I read in other forums mmcblk0 is the partition table files can't you upload pit file for me
Sorry for troubling you
Click to expand...
Click to collapse
M,
you need this version of my philz build - old twrp friendly http://d-h.st/SSY
while in recovery adb push to sdcard - the entry may be /sdcard , /sdcard/ , or, /data/media/0
mount all partitions using the twrp mount function first
reboot recovery and you should be in philz
m
moonbutt74 said:
M,
you need this version of my philz build - old twrp friendly http://d-h.st/SSY
while in recovery adb push to sdcard - the entry may be /sdcard , /sdcard/ , or, /data/media/0
mount all partitions using the twrp mount function first
reboot recovery and you should be in philz
m
Click to expand...
Click to collapse
By the way any good news about the mmcblk0 recovery.img or something like that?
Please help me....
M,
okay, try this
this is recovery flashable zip meant to write the first 4mb of mmcblk0 that you overwrote.
the thought is since we share the same partition scheme the 4mb i pulled from my tab should fill in that part
you are now missing. this is step 1. i need you to tell me which recovery build and version you are running.
m
FYI - this is our partition table via parted:
Code:
Model: MMC MAG2GC (sd/mmc)
Disk /dev/block/mmcblk0: 15.7GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
18 4194kB 6291kB 2097kB BOTA0 <------you also overwrote
19 6291kB 8389kB 2097kB BOTA1 <------these two and
2 8389kB 29.4MB 21.0MB ext4 EFS <-----most of this if i got you right
16 37.7MB 41.9MB 4194kB PARAM
1 41.9MB 45.1MB 3146kB RESERVED1
20 45.1MB 46.1MB 1049kB DNX
21 46.1MB 54.5MB 8389kB OTA
10 54.5MB 75.5MB 21.0MB BOOT
11 75.5MB 96.5MB 21.0MB RECOVERY
12 96.5MB 101MB 4194kB RESERVED3
3 101MB 117MB 16.8MB ext4 CONFIG
4 117MB 120MB 2097kB FACTORY
5 120MB 122MB 2097kB MEDIA
7 122MB 126MB 4194kB RESERVED2
14 126MB 130MB 4194kB CARRIER
15 130MB 134MB 4194kB TDATA
17 134MB 147MB 12.6MB PERSDATA
8 147MB 2621MB 2475MB ext4 SYSTEM
13 2621MB 2726MB 105MB ext4 HIDDEN
6 2726MB 3093MB 367MB ext4 CACHE
9 3093MB 15.7GB 12.7GB ext4 USERDATA
moonbutt74 said:
M,
okay, try this
this is recovery flashable zip meant to write the first 4mb of mmcblk0 that you overwrote.
the thought is since we share the same partition scheme the 4mb i pulled from my tab should fill in that part
you are now missing. this is step 1. i need you to tell me which recovery build and version you are running.
m
FYI - this is our partition table via parted:
Code:
Model: MMC MAG2GC (sd/mmc)
Disk /dev/block/mmcblk0: 15.7GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
18 4194kB 6291kB 2097kB BOTA0 <------you also overwrote
19 6291kB 8389kB 2097kB BOTA1 <------these two and
2 8389kB 29.4MB 21.0MB ext4 EFS <-----most of this if i got you right
16 37.7MB 41.9MB 4194kB PARAM
1 41.9MB 45.1MB 3146kB RESERVED1
20 45.1MB 46.1MB 1049kB DNX
21 46.1MB 54.5MB 8389kB OTA
10 54.5MB 75.5MB 21.0MB BOOT
11 75.5MB 96.5MB 21.0MB RECOVERY
12 96.5MB 101MB 4194kB RESERVED3
3 101MB 117MB 16.8MB ext4 CONFIG
4 117MB 120MB 2097kB FACTORY
5 120MB 122MB 2097kB MEDIA
7 122MB 126MB 4194kB RESERVED2
14 126MB 130MB 4194kB CARRIER
15 130MB 134MB 4194kB TDATA
17 134MB 147MB 12.6MB PERSDATA
8 147MB 2621MB 2475MB ext4 SYSTEM
13 2621MB 2726MB 105MB ext4 HIDDEN
6 2726MB 3093MB 367MB ext4 CACHE
9 3093MB 15.7GB 12.7GB ext4 USERDATA
Click to expand...
Click to collapse
I have reflashed twmr ver. 2.7 that angel666 made, but if you want I could flash phiz recovery that you made... I will let you notified on every thing I do.
mohali256 said:
I have reflashed twmr ver. 2.7 that angel666 made, but if you want I could flash phiz recovery that you made... I will let you notified on every thing I do.
Click to expand...
Click to collapse
just work with the one you have for now. flash the zip and reboot. if you're still hanging, reboot to recovery and get adb up and ready.
then write back.
Can anybody confirm that the follow strings working on the T805?
Use Terminal Emulator and enter follow:
su (Enter)
dd if=/dev/block/mmcblk0 of=/sdcard/out.pit bs=8 count=580 skip=2176 (Enter)
Click to expand...
Click to collapse
This Code is from the Galaxy S5 but i think that the mmcblk0 is the same or i wrong?
Here are the partition from the S10.5 and S8.4 Tab
Code:
Größe Device Name Kommentar Mountpoint
15388672 mmcblk0
4096 mmcblk0p1 BOTA0
4096 mmcblk0p2 BOTA1
20480 mmcblk0p3 EFS EFS Filesystem /efs
4096 mmcblk0p4 m9kefs1 EFS Filesystem
4096 mmcblk0p5 m9kefs2 EFS Filesystem
4096 mmcblk0p6 m9kefs3 EFS Filesystem
4096 mmcblk0p7 CARRIER Modemfirmware
8192 mmcblk0p8 PARAM Param
8192 mmcblk0p9 BOOT Kernel
10240 mmcblk0p10 RECOVERY Recovery
10240 mmcblk0p11 OTA FOTA Partition
4096 mmcblk0p12 CDMA-RADIO Modemfirmware
49152 mmcblk0p13 RADIO Modemfirmware
4096 mmcblk0p14 TOMBSTONES
4096 mmcblk0p15 TDATA
12288 mmcblk0p16 PERSDATA /persdata/absolute
4096 mmcblk0p17 RESERVED2
2447360 mmcblk0p18 SYSTEM System Partition /system
204800 mmcblk0p19 CACHE Cache /cache
235520 mmcblk0p20 HIDDEN Hidden Partition
12333056 mmcblk0p21 USERDATA Userdaten /data
4096 mmcblk0rpmb
4096 mmcblk0boot1
4096 mmcblk0boot0
Chrack said:
Can anybody confirm that the follow strings working on the T805?
Click to expand...
Click to collapse
Did you find out which dd values would do the trick ?
I want to save PIT from my Tab S and A5.... http://forum.xda-developers.com/gal...t-efs-rest-t3169643/post62128668#post62128668
gggg said:
Did you find out which dd values would do the trick ?
I want to save PIT from my Tab S and A5.... http://forum.xda-developers.com/gal...t-efs-rest-t3169643/post62128668#post62128668
Click to expand...
Click to collapse
Efs professional
ashyx said:
Efs professional
Click to expand...
Click to collapse
It cannot read PIT on A5 this is why I want to dd, but I need the right params ... please reply here:
http://forum.xda-developers.com/gal...t-efs-rest-t3169643/post62128668#post62128668