ok so i made the move to remix os after receive my laptop back from repairs with a empty HDD running windows 8 rather than 10 there is no longer a free upgrade available for windows 8 to 10 so i decided to try out remix os on it looks spot on but i wanted to know if there was a way to try and access the partition windows 8 was on to erase and make into a larger storage box for things like pictures and movies. im not the tech savist when it comes to coding or anything so if i need that some screenshots or simplified directions would help
Showing posts with label partition. Show all posts
Showing posts with label partition. Show all posts
Saturday, 30 July 2016
Friday, 29 July 2016
Missing external partition
Hello guys,
Im using CM12 on my Xperia l device where this happens suddenly and I'm unable to use my external sdcard and cant even format so i changed my SD and no result came .Here is the screenshot of my partition in which i couldn't find any solution ..its been two days of search and not close to finding answer
Im using CM12 on my Xperia l device where this happens suddenly and I'm unable to use my external sdcard and cant even format so i changed my SD and no result came .Here is the screenshot of my partition in which i couldn't find any solution ..its been two days of search and not close to finding answer
Wednesday, 27 July 2016
How to Increasing system partition size
Is there anyway to Increasing system partition size?
Like this
http://forum.xda-developers.com/gala...-size-t3011162
Anyone?
Like this
http://forum.xda-developers.com/gala...-size-t3011162
Anyone?
Monday, 25 July 2016
[ROOT] Partitions backup & other partition info :
Before rooting, do backup your /boot and /system partitions via SPFT, as described here (whenever the post is filled in properly :D ) :
http://forum.xda-developers.com/r1-h...oting-t3426041
Since it's pretty tedious to run that for each and every partition, I propose to backup other ones after you get root. But note that copying the partitions back to the device is a lot quicker since all the necessary info can be preset in a scatter file !
I recommend that you follow other threads to get root, such as, for example, here :
http://forum.xda-developers.com/r1-h...-root-t3425677
Some partitions will still be mounted, but I don't think it matters that much. Anyway, here is a list of what is usually mounted :
To backup whatever partitions are out there, run these commands :
These are the files that you'll get
And this is another map of partitions to names :
And mount output :
And partition sizes in blocks:
http://forum.xda-developers.com/r1-h...oting-t3426041
Since it's pretty tedious to run that for each and every partition, I propose to backup other ones after you get root. But note that copying the partitions back to the device is a lot quicker since all the necessary info can be preset in a scatter file !
I recommend that you follow other threads to get root, such as, for example, here :
http://forum.xda-developers.com/r1-h...-root-t3425677
Some partitions will still be mounted, but I don't think it matters that much. Anyway, here is a list of what is usually mounted :
Code:
Filesystem Size Used Free Blksize
/dev 970.2M 84.0K 970.1M 4096
/sys/fs/cgroup 970.2M 12.0K 970.2M 4096
/mnt 970.2M 0.0K 970.2M 4096
/mnt/runtime/default/emulated 11.2G 522.4M 10.7G 4096
/mnt/runtime/read/emulated 11.2G 522.4M 10.7G 4096
/mnt/runtime/write/emulated 11.2G 522.4M 10.7G 4096
/system 2.5G 2.0G 516.5M 4096
/data 11.2G 522.4M 10.7G 4096
/cache 387.4M 988.0K 386.5M 4096
/protect_f 5.8M 60.0K 5.8M 4096
/protect_s 5.8M 56.0K 5.8M 4096
/nvdata 27.5M 2.2M 25.3M 4096
/storage 970.2M 0.0K 970.2M 4096
/storage/emulated 11.2G 522.4M 10.7G 4096
/su 90.5M 676.0K 89.8M 4096Code:
adb shell
su
mkdir /sdcard/images/
cd /sdcard/images
dd if=/dev/block/mmcblk0boot0 of=00_boot0.img
dd if=/dev/block/mmcblk0boot1 of=01_boot1.img
dd if=/dev/block/mmcblk0rpmb of=02_rpmb.img
dd if=/dev/block/mmcblk0p1 of=p1_proinfo.img
dd if=/dev/block/mmcblk0p2 of=p2_nvram.img
dd if=/dev/block/mmcblk0p3 of=p3_protect1.img
dd if=/dev/block/mmcblk0p4 of=p4_protect2.img
dd if=/dev/block/mmcblk0p5 of=p5_lk.img
dd if=/dev/block/mmcblk0p6 of=p6_para.img
dd if=/dev/block/mmcblk0p7 of=p7_boot.img
dd if=/dev/block/mmcblk0p8 of=p8_recovery.img
dd if=/dev/block/mmcblk0p9 of=p9_logo.img
dd if=/dev/block/mmcblk0p10 of=p10_expdb.img
dd if=/dev/block/mmcblk0p11 of=p11_seccfg.img
dd if=/dev/block/mmcblk0p12 of=p12_oemkeystore.img
dd if=/dev/block/mmcblk0p13 of=p13_secro.img
dd if=/dev/block/mmcblk0p14 of=p14_keystore.img
dd if=/dev/block/mmcblk0p15 of=p15_tee1.img
dd if=/dev/block/mmcblk0p16 of=p16_tee2.img
dd if=/dev/block/mmcblk0p17 of=p17_frp.img
dd if=/dev/block/mmcblk0p18 of=p18_nvdata.img
dd if=/dev/block/mmcblk0p19 of=p19_metadata.img
#dd if=/dev/block/mmcblk0p20 of=p20_system.img
#dd if=/dev/block/mmcblk0p21 of=p21_cache.img
#dd if=/dev/block/mmcblk0p22 of=p22_userdata.img
dd if=/dev/block/mmcblk0p23 of=p23_flashinfo.img
md5sum *.img
exit
exit
adb pull /sdcard/imagesCode:
-rw-rw---- root sdcard_rw 4194304 2016-01-01 18:31 00_boot0.img
-rw-rw---- root sdcard_rw 4194304 2016-01-01 18:31 01_boot1.img
-rw-rw---- root sdcard_rw 0 2016-01-01 18:47 02_rpmb.img
-rw-rw---- root sdcard_rw 3145728 2016-01-01 18:31 p1_proinfo.img
-rw-rw---- root sdcard_rw 5242880 2016-01-01 18:31 p2_nvram.img
-rw-rw---- root sdcard_rw 10485760 2016-01-01 18:31 p3_protect1.img
-rw-rw---- root sdcard_rw 10485760 2016-01-01 18:31 p4_protect2.img
-rw-rw---- root sdcard_rw 524288 2016-01-01 18:31 p5_lk.img
-rw-rw---- root sdcard_rw 524288 2016-01-01 18:31 p6_para.img
-rw-rw---- root sdcard_rw 16777216 2016-01-01 18:31 p7_boot.img
-rw-rw---- root sdcard_rw 16777216 2016-01-01 18:31 p8_recovery.img
-rw-rw---- root sdcard_rw 8388608 2016-01-01 18:31 p9_logo.img
-rw-rw---- root sdcard_rw 10485760 2016-01-01 18:31 p10_expdb.img
-rw-rw---- root sdcard_rw 524288 2016-01-01 18:31 p11_seccfg.img
-rw-rw---- root sdcard_rw 2097152 2016-01-01 18:31 p12_oemkeystore.img
-rw-rw---- root sdcard_rw 6291456 2016-01-01 18:31 p13_secro.img
-rw-rw---- root sdcard_rw 8388608 2016-01-01 18:31 p14_keystore.img
-rw-rw---- root sdcard_rw 5242880 2016-01-01 18:31 p15_tee1.img
-rw-rw---- root sdcard_rw 5242880 2016-01-01 18:31 p16_tee2.img
-rw-rw---- root sdcard_rw 1048576 2016-01-01 18:31 p17_frp.img
-rw-rw---- root sdcard_rw 33554432 2016-01-01 18:31 p18_nvdata.img
-rw-rw---- root sdcard_rw 38797312 2016-01-01 18:32 p19_metadata.img
-rw-rw---- root sdcard_rw 16777216 2016-01-01 18:32 p23_flashinfo.imgCode:
lrwxrwxrwx root root 2016-01-01 17:30 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2016-01-01 17:30 cache -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2016-01-01 17:30 expdb -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2016-01-01 17:30 flashinfo -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2016-01-01 17:30 frp -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2016-01-01 17:30 keystore -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2016-01-01 17:30 lk -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2016-01-01 17:30 logo -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2016-01-01 17:30 metadata -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2016-01-01 17:30 nvdata -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2016-01-01 17:30 nvram -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2016-01-01 17:30 oemkeystore -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2016-01-01 17:30 para -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2016-01-01 17:30 proinfo -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2016-01-01 17:30 protect1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2016-01-01 17:30 protect2 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2016-01-01 17:30 recovery -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2016-01-01 17:30 seccfg -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2016-01-01 17:30 secro -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2016-01-01 17:30 system -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2016-01-01 17:30 tee1 -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2016-01-01 17:30 tee2 -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2016-01-01 17:30 userdata -> /dev/block/mmcblk0p22Code:
rootfs / rootfs ro,seclabel 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
adb /dev/usb-ffs/adb functionfs rw,relatime 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,seclabel,relatime 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
pstore /sys/fs/pstore pstore rw,seclabel,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
/dev/fuse /mnt/runtime/default/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /mnt/runtime/read/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /mnt/runtime/write/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/system /system ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,discard,noauto_da_alloc,resuid=10010,data=ordered 0 0
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/protect1 /protect_f ext4 rw,seclabel,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,commit=1,data=ordered 0 0
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/protect2 /protect_s ext4 rw,seclabel,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,commit=1,data=ordered 0 0
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/nvdata /nvdata ext4 rw,seclabel,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered 0 0
tmpfs /storage tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
/dev/fuse /storage/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/loop1 /su ext4 rw,seclabel,noatime,data=ordered 0 0Code:
major minor #blocks name
7 0 1254 loop0
7 1 98304 loop1
179 0 15392768 mmcblk0
179 1 3072 mmcblk0p1
179 2 5120 mmcblk0p2
179 3 10240 mmcblk0p3
179 4 10240 mmcblk0p4
179 5 512 mmcblk0p5
179 6 512 mmcblk0p6
179 7 16384 mmcblk0p7
179 8 16384 mmcblk0p8
179 9 8192 mmcblk0p9
179 10 10240 mmcblk0p10
179 11 512 mmcblk0p11
179 12 2048 mmcblk0p12
179 13 6144 mmcblk0p13
179 14 8192 mmcblk0p14
179 15 5120 mmcblk0p15
179 16 5120 mmcblk0p16
179 17 1024 mmcblk0p17
179 18 32768 mmcblk0p18
179 19 37888 mmcblk0p19
179 20 2736128 mmcblk0p20
179 21 409600 mmcblk0p21
179 22 12049920 mmcblk0p22
179 23 16384 mmcblk0p23
179 96 4096 mmcblk0rpmb
179 64 4096 mmcblk0boot1
179 32 4096 mmcblk0boot0Backing up/ restoring /Data partition manually
Hello everyone!
I would like to know if it was possible to backup and restore /data without a custom recovery, like, manually
1-Copy pasting /data to an SD card or PC
2-Reset my phone
3-Copy pasting /data
I know these three steps only didn't work for a friend of mine who tried it, so.. could these help?
4-Using terminal emulator to mount data?
4-Giving higher permission to the folder with root browser?
I'm just wondering, as I personnally would use TWRP for it but the friend that tried was rooted but did not have custom recovery at that time.
I would have done it with Titanium backup but well... he tried another method :D
This is all just out of curiosity, as this friend is now back running with his phone normally, as this happened a few months ago, but this question never got out of my brain so I decided to ask here.
Sorry for the long life story, It was just to set up why I got to this question :D
Have a good day.
I would like to know if it was possible to backup and restore /data without a custom recovery, like, manually
1-Copy pasting /data to an SD card or PC
2-Reset my phone
3-Copy pasting /data
I know these three steps only didn't work for a friend of mine who tried it, so.. could these help?
4-Using terminal emulator to mount data?
4-Giving higher permission to the folder with root browser?
I'm just wondering, as I personnally would use TWRP for it but the friend that tried was rooted but did not have custom recovery at that time.
I would have done it with Titanium backup but well... he tried another method :D
This is all just out of curiosity, as this friend is now back running with his phone normally, as this happened a few months ago, but this question never got out of my brain so I decided to ask here.
Sorry for the long life story, It was just to set up why I got to this question :D
Have a good day.
[HELP] Partition issue, no more space for apps
Hi all, thanks for kind support,
I've a 900V CID11 bootloader locked, unrooted, I installed MM 6.0.1 by safestrap.
MY phone is 16GB but it looks I've really small space for apps, someone can kindly describe me how the storage is allocated?
As I guess reading around, the safestrap eat me 2,5gb for some reason, then there is the rom space, then the "sdcard" folder for data. On sdcard I still have 500MB available but I think the phone doesn't want to use them for installing apps. I've 32GB SD but it looks also that with uroot phone I can't move apps there.
Any way to expand the space for installing apps? Any way to repartition the space? Use the 2,5gb of safestrap? Maybe repeat the procedure using flashfire?
By now I've a serious limitation. Thank you for help
I've a 900V CID11 bootloader locked, unrooted, I installed MM 6.0.1 by safestrap.
MY phone is 16GB but it looks I've really small space for apps, someone can kindly describe me how the storage is allocated?
As I guess reading around, the safestrap eat me 2,5gb for some reason, then there is the rom space, then the "sdcard" folder for data. On sdcard I still have 500MB available but I think the phone doesn't want to use them for installing apps. I've 32GB SD but it looks also that with uroot phone I can't move apps there.
Any way to expand the space for installing apps? Any way to repartition the space? Use the 2,5gb of safestrap? Maybe repeat the procedure using flashfire?
By now I've a serious limitation. Thank you for help
Sunday, 24 July 2016
[Help] Accidentally removed the Internal Storage Partition
I accidentally removed the partition of the Internal storage on my Moto E XT1022 while flashing a ROM (I seriously don't know how), and now I am not able to flash anything else, No Gapps, Capps, Xposed framework. Can anyone help me out resolve this issue?
If anyone is not able to understand, basically, in general, my device gave 2.2GB of internal storage to me(the user), same as all other Moto E(s), but now it is giving me 4 GB of internal storage (Screenshot attached).
If anyone is not able to understand, basically, in general, my device gave 2.2GB of internal storage to me(the user), same as all other Moto E(s), but now it is giving me 4 GB of internal storage (Screenshot attached).
Saturday, 23 July 2016
Flashtool Closing TA partition error
Hello,
i`m trying to flash SonyXperia C Dual C2305 with flashtool-0.9.22.3 ..... firmware : C2305_16.0.B.2.16_Customized MEA.ftf
but it ends with errors :crying: , here is the log:
23/054/2016 12:54:17 - INFO - <- This level is successfully initialized
23/054/2016 12:54:18 - INFO - Flashtool Version 0.9.22.3 built on 08-06-2016 22:30:00
23/054/2016 12:54:18 - INFO - Executing search strategies to find proxy selector
23/054/2016 12:54:21 - INFO - No proxy found for IE. Trying next one
23/054/2016 12:54:21 - INFO - Strategy firefox failed trying next one : No Firefox installation found
23/054/2016 12:54:21 - INFO - No proxy found for java. Trying next one
23/054/2016 12:54:21 - INFO - Syncing devices from github
23/054/2016 12:54:21 - INFO - Opening devices repository.
23/054/2016 12:54:21 - INFO - Scanning devices folder for changes.
23/054/2016 12:54:29 - INFO - Pulling changes from github.
23/054/2016 12:54:31 - INFO - Quietly closing devices repository.
23/054/2016 12:54:31 - INFO - Devices sync finished.
23/054/2016 12:54:31 - INFO - Loading devices database
23/054/2016 12:54:31 - INFO - Loaded 91 devices
23/054/2016 12:54:31 - INFO - Starting phone detection
23/054/2016 12:54:35 - INFO - Device disconnected
23/055/2016 12:55:05 - INFO - Selected Bundle for Sony Xperia C(C2305). FW release : 16.0.B.2.16. Customization : Customized MEA
23/055/2016 12:55:05 - INFO - Preparing files for flashing
23/055/2016 12:55:21 - INFO - Please connect your device into flashmode.
23/055/2016 12:55:55 - INFO - Device connected in flash mode
23/055/2016 12:55:55 - INFO - Opening device for R/W
23/055/2016 12:55:55 - INFO - Reading device information
23/055/2016 12:55:55 - INFO - Phone ready for flashmode operations.
23/055/2016 12:55:55 - INFO - Opening TA partition 2
23/055/2016 12:55:55 - INFO - Current device : C2305 - QO4414C03993 - 1277-6019_R2A - 1275-5177_16.0.B.2.16 - WORLD-i_16.0.B.2.16
23/055/2016 12:55:55 - INFO - Closing TA partition
23/055/2016 12:55:55 - INFO - Start Flashing
23/055/2016 12:55:55 - INFO - Processing loader.sin
23/055/2016 12:55:55 - INFO - Checking header
23/055/2016 12:55:56 - INFO - Flashing data
23/055/2016 12:55:57 - INFO - Loader : S1_Root_bb35 - Version : MT6589_12 / Boot version : 2.14.J.2.16 / Bootloader status : NOT_ROOTABLE
23/055/2016 12:55:57 - INFO - Max packet size set to 512K
23/055/2016 12:55:57 - INFO - USB buffer size set to 512K
23/056/2016 12:56:00 - INFO - No flash script found. Using 0.9.18 flash engine
23/056/2016 12:56:00 - INFO - Opening TA partition 2
23/056/2016 12:56:00 - INFO - Writing TA unit 00002774. Value : 01
23/056/2016 12:56:00 - INFO - Closing TA partition
23/056/2016 12:56:44 - INFO - Ending flash session
23/056/2016 12:56:44 - ERROR -
23/056/2016 12:56:44 - ERROR - Error flashing. Aborted
23/056/2016 12:56:44 - INFO - Flashing finished.
23/056/2016 12:56:44 - INFO - Please unplug and start your phone
23/056/2016 12:56:44 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings
23/056/2016 12:56:45 - INFO - Device connected in flash mode
23/056/2016 12:56:45 - INFO - Device disconnected
solution plz.
i`m trying to flash SonyXperia C Dual C2305 with flashtool-0.9.22.3 ..... firmware : C2305_16.0.B.2.16_Customized MEA.ftf
but it ends with errors :crying: , here is the log:
23/054/2016 12:54:17 - INFO - <- This level is successfully initialized
23/054/2016 12:54:18 - INFO - Flashtool Version 0.9.22.3 built on 08-06-2016 22:30:00
23/054/2016 12:54:18 - INFO - Executing search strategies to find proxy selector
23/054/2016 12:54:21 - INFO - No proxy found for IE. Trying next one
23/054/2016 12:54:21 - INFO - Strategy firefox failed trying next one : No Firefox installation found
23/054/2016 12:54:21 - INFO - No proxy found for java. Trying next one
23/054/2016 12:54:21 - INFO - Syncing devices from github
23/054/2016 12:54:21 - INFO - Opening devices repository.
23/054/2016 12:54:21 - INFO - Scanning devices folder for changes.
23/054/2016 12:54:29 - INFO - Pulling changes from github.
23/054/2016 12:54:31 - INFO - Quietly closing devices repository.
23/054/2016 12:54:31 - INFO - Devices sync finished.
23/054/2016 12:54:31 - INFO - Loading devices database
23/054/2016 12:54:31 - INFO - Loaded 91 devices
23/054/2016 12:54:31 - INFO - Starting phone detection
23/054/2016 12:54:35 - INFO - Device disconnected
23/055/2016 12:55:05 - INFO - Selected Bundle for Sony Xperia C(C2305). FW release : 16.0.B.2.16. Customization : Customized MEA
23/055/2016 12:55:05 - INFO - Preparing files for flashing
23/055/2016 12:55:21 - INFO - Please connect your device into flashmode.
23/055/2016 12:55:55 - INFO - Device connected in flash mode
23/055/2016 12:55:55 - INFO - Opening device for R/W
23/055/2016 12:55:55 - INFO - Reading device information
23/055/2016 12:55:55 - INFO - Phone ready for flashmode operations.
23/055/2016 12:55:55 - INFO - Opening TA partition 2
23/055/2016 12:55:55 - INFO - Current device : C2305 - QO4414C03993 - 1277-6019_R2A - 1275-5177_16.0.B.2.16 - WORLD-i_16.0.B.2.16
23/055/2016 12:55:55 - INFO - Closing TA partition
23/055/2016 12:55:55 - INFO - Start Flashing
23/055/2016 12:55:55 - INFO - Processing loader.sin
23/055/2016 12:55:55 - INFO - Checking header
23/055/2016 12:55:56 - INFO - Flashing data
23/055/2016 12:55:57 - INFO - Loader : S1_Root_bb35 - Version : MT6589_12 / Boot version : 2.14.J.2.16 / Bootloader status : NOT_ROOTABLE
23/055/2016 12:55:57 - INFO - Max packet size set to 512K
23/055/2016 12:55:57 - INFO - USB buffer size set to 512K
23/056/2016 12:56:00 - INFO - No flash script found. Using 0.9.18 flash engine
23/056/2016 12:56:00 - INFO - Opening TA partition 2
23/056/2016 12:56:00 - INFO - Writing TA unit 00002774. Value : 01
23/056/2016 12:56:00 - INFO - Closing TA partition
23/056/2016 12:56:44 - INFO - Ending flash session
23/056/2016 12:56:44 - ERROR -
23/056/2016 12:56:44 - ERROR - Error flashing. Aborted
23/056/2016 12:56:44 - INFO - Flashing finished.
23/056/2016 12:56:44 - INFO - Please unplug and start your phone
23/056/2016 12:56:44 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings
23/056/2016 12:56:45 - INFO - Device connected in flash mode
23/056/2016 12:56:45 - INFO - Device disconnected
solution plz.
Friday, 22 July 2016
What is your /system partition size?
im only showing 1.5gb as the total size of my system partition the seems way small? is this right?
Thursday, 21 July 2016
Odin error: There is no PIT partition.
I gave the gf's kid an old S2 Skyrocket to use with CM9 I believe on it. Something went wrong and the kid couldn't boot it anymore. I took a look. Flashed it with an old Odin but tried something else, flashed it with a newer Odin and completely screwed it up now. It's been a couple months since I tried fixing it so what I can remember is I think i accidentally wiped Clockwork recovery somehow and then the PIT file. Tried using a newer ODID to flash and just kept getting errors. The only way I can get into download mode now is with that little USB device that boots it into download mode. Otherwise it just stalls at SAMSUNG logo.
So i tried messing with it again today. Using Odin 3.04 I tried flashing to stock firmware and just get this
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_I727UCMC1_I727ATTMC1_844945_REV02_user_l ow_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> There is no PIT partition.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1
Cant seem to find any PIT files for the i727 Skyrocket. I found something called SGH-I727-PIT(modified_6GB) but no clue what that is. Tried it anyway and just get this:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_I727UCMC1_I727ATTMC1_844945_REV02_user_l ow_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1
After messing with hours I'm about to give up and throw it in the trash...but read that if you can get into download mode then it could be fixed and i'm just doing it wrong.
Any ideas?
So i tried messing with it again today. Using Odin 3.04 I tried flashing to stock firmware and just get this
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_I727UCMC1_I727ATTMC1_844945_REV02_user_l ow_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> There is no PIT partition.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1
Cant seem to find any PIT files for the i727 Skyrocket. I found something called SGH-I727-PIT(modified_6GB) but no clue what that is. Tried it anyway and just get this:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_I727UCMC1_I727ATTMC1_844945_REV02_user_l ow_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1
After messing with hours I'm about to give up and throw it in the trash...but read that if you can get into download mode then it could be fixed and i'm just doing it wrong.
Any ideas?
Restore a deleted partition
Hiya! I don't believe my problem is device specific. The background of how I ended up in this crappy situation is, but I believe the resulting issue is general. Should I be wrong, tell me and I'll move this to my device's section.
Short question: how can I (and can I?) restore data in a partition that got deleted, if no new filesystem has been created over it?
Long background: I have a Xiaomi Mi2-S 32GB. It used to have a peculiar layout: a double system partition (/system1 and /system2)¹, a small internal storage (/userdata)², and a big emulated SD card (/storage)³.
Let's explain why:
¹ False dual boot: the active system is installed in the first partition. When installing an update with the official app, the newer system gets installed in the second and that one gets booted. So, should this newer system fail to boot, you have an older one correctly working and ready to boot.
² and ³: so that the whole storage partition containing photos, music, videos, downloads, backups, saved games and such can be accessed with MTP, while the userdata containing apps and complementary system things is kept safe. This last decision, however, brings up a new problem: userdata can't be accessed by user to put his files or by apps without root permissions to store data (like photos), while storage can't be used to install apps, or even to move them using Link2SD or such. Some users might find storage is insufficient for their videos and music, while others might find userdata is too little for their games, and they are both stuck in this situation.
I was in the second group, so I altered my layout using stillka's guide on xiaomi.eu (Sorry, I can't post links). I extended my userdata, so that my storage resulted smaller. Plus, I understood altering a partition would mean deleting all the partitions before that one, and recreating them thereafter.
Until this point, all was OK. I installed Ivan's AOSP Lollipop for unmerged partitions, and found out it would experience random reboots with True Dual Boot. So I stuck with False one and forgot about everything. I kept that version without updating for a long time.
Then, several months later, my phone started rebooting randomly anyway. I figured I would come back to MIUI to get Xiaomi's support for an official ROM.
Little did I know they decided to change layout in the meantime. MIUI got so big the size of the two systems was insufficient. So they decided to merge them into an unique partition big enough. So, while flashing with the official tool MiFlash, it practically altered my system layout, having to delete all that was placed before them (cache, userdata and storage), never telling me what it was going to do, advising me to back my storage up somewhere. All I did was back up my userdata into storage, confident flashing their official ROM with their official tool would just write into system, since nobody told me otherwise.
So this is the result: the old, small size of userdata is back, and everything that comes after is left without any filesystem: these are the last line in parted's print output
I've tried parted's rescue command, but it is unable to find a partition lying there. I don't have my old layout, so I'm not able to precisely know where my old storage began, but I remember it to be around 18 GiB in size. I've tried all ranges possible (from the current end of userdata, 18 G from the end and so on) but no dice.
Can someone tell me if there is any hope, and what can I try?
Short question: how can I (and can I?) restore data in a partition that got deleted, if no new filesystem has been created over it?
Long background: I have a Xiaomi Mi2-S 32GB. It used to have a peculiar layout: a double system partition (/system1 and /system2)¹, a small internal storage (/userdata)², and a big emulated SD card (/storage)³.
Let's explain why:
¹ False dual boot: the active system is installed in the first partition. When installing an update with the official app, the newer system gets installed in the second and that one gets booted. So, should this newer system fail to boot, you have an older one correctly working and ready to boot.
² and ³: so that the whole storage partition containing photos, music, videos, downloads, backups, saved games and such can be accessed with MTP, while the userdata containing apps and complementary system things is kept safe. This last decision, however, brings up a new problem: userdata can't be accessed by user to put his files or by apps without root permissions to store data (like photos), while storage can't be used to install apps, or even to move them using Link2SD or such. Some users might find storage is insufficient for their videos and music, while others might find userdata is too little for their games, and they are both stuck in this situation.
I was in the second group, so I altered my layout using stillka's guide on xiaomi.eu (Sorry, I can't post links). I extended my userdata, so that my storage resulted smaller. Plus, I understood altering a partition would mean deleting all the partitions before that one, and recreating them thereafter.
Until this point, all was OK. I installed Ivan's AOSP Lollipop for unmerged partitions, and found out it would experience random reboots with True Dual Boot. So I stuck with False one and forgot about everything. I kept that version without updating for a long time.
Then, several months later, my phone started rebooting randomly anyway. I figured I would come back to MIUI to get Xiaomi's support for an official ROM.
Little did I know they decided to change layout in the meantime. MIUI got so big the size of the two systems was insufficient. So they decided to merge them into an unique partition big enough. So, while flashing with the official tool MiFlash, it practically altered my system layout, having to delete all that was placed before them (cache, userdata and storage), never telling me what it was going to do, advising me to back my storage up somewhere. All I did was back up my userdata into storage, confident flashing their official ROM with their official tool would just write into system, since nobody told me otherwise.
So this is the result: the old, small size of userdata is back, and everything that comes after is left without any filesystem: these are the last line in parted's print output
Quote:
20 327MB 336MB 8389kB ext4 persist 21 336MB 1409MB 1074MB ext4 system 22 1409MB 1812MB 403MB ext4 cache 23 1812MB 5570MB 3758MB ext4 userdata 24 5570MB 31.3GB 25.7GB storage |
Can someone tell me if there is any hope, and what can I try?
Wednesday, 20 July 2016
Need rooted stock TW ROM that won't re-lock bootloader or touch recovery partition
Short story: I need a TouchWiz ROM that I can flash from TWRP that won't re-lock my bootloader or touch the TWRP partition. What's the best one to use?
Longer story: I have SM-G900V running CM 13 that is currently unable to get a GPS lock unless airplane mode is enabled. So far I've been told the only fix for this is (high level instructions):
Some of the troubleshooting steps involve root, hence the need for a rooted ROM. Can anyone help?
Longer story: I have SM-G900V running CM 13 that is currently unable to get a GPS lock unless airplane mode is enabled. So far I've been told the only fix for this is (high level instructions):
- Nandroid backup of CM 13
- Flash TouchWiz ROM
- Get GPS lock in TouchWiz ROM
- Restore CM 13 nandroid backup
Some of the troubleshooting steps involve root, hence the need for a rooted ROM. Can anyone help?
Monday, 18 July 2016
[Q] Chuwi vi8 ultimate bricked. how to restore with only the android partition?
i bricked my tablet and i'm able to install windows 10 with a pen drive, but i want to restore the android partition and use ONLY android. someone can help me?
Storage Partition Issue
I just installed the Viper4G ROM (Latest Version) the other day and love it, but I have a storage problem on my phone, the INTERNAL storage is partitioned into two parts, the first partition is labeled App Storage 15.91GB, the second is labeled Phone Storage 93.79MB. When I use apps such as ES File manager or try to browse my phone via PC/USB I can only browse the Phone Storage (93.79MB) but when I install apps it goes to the App Storage (15.91GB). Before I installed this ROM the storage was all one big partition, I would like it to be that way again. The previously installed ROM was just a rooted stock ROM if I remember correctly or some Liquid something ROM. I would like to know how to merge the two storage partitions so I can use my Internal Storage to the full. Also I have tried many types of format resets (Factory Reset) via TWRP (recovery) mode and have had no results. If you need my phone info check details below and if there is something else you need feel free to ask.
!!!NONE OF THIS PERTAINS TO MY SD-CARD (EXTERNAL STORAGE) DEVICE!!!
--------------------------------------------
!!!!PHONE INFORMATION!!!!
Phone Model: HTC EVO 4G LTE
HBoot v2.10.00
Viper ROM currently installed
16GB Internal Storage
OS: Jelly Bean (JB)
32GB SD Card Storage (External)
ROOTED (Obviously)
JEWEL
S-OFF
TWRP v2.8.0.3
--------------------------------------------
!!!NONE OF THIS PERTAINS TO MY SD-CARD (EXTERNAL STORAGE) DEVICE!!!
--------------------------------------------
!!!!PHONE INFORMATION!!!!
Phone Model: HTC EVO 4G LTE
HBoot v2.10.00
Viper ROM currently installed
16GB Internal Storage
OS: Jelly Bean (JB)
32GB SD Card Storage (External)
ROOTED (Obviously)
JEWEL
S-OFF
TWRP v2.8.0.3
--------------------------------------------
Cannot mount /data partition
today i accidentally flashed cf auto root package of sm-g920f on galaxy s7 sm-g930f and the device was stuck loop in galaxy s7 logo with senforcing red word so i reflashed stock recovery and cache.img and rebooted this time it keeps restarting on galaxy s7 logo so i flashed twrp and in twrp it said unable to mount /data.
how can i repari data partition ?
how can i repari data partition ?
Sunday, 17 July 2016
Adding support for encrypted /data partition into TWRP
Is it possible to make a build of TWRP with support for encrypted /data partitions in TWRP? Currently, if the phone is encrypted, and I want to flash a new nightly of CM 13, then I can't wipe the dalvik cache from TWRP.
SW3 may need partition repair
My sw3 has been stuck on the 4 dots/symbols for some time now. I have tried XC (even though it ran with success, it did not fix the watch), by way of fastboot, adb and twrp I have run, installed, pushed various files such as recovery, roms, .simg, etc to no avail. I had a thread going on the 4 dots that describes each of these functions with the 4 dot thread title if you care to see what has been done and the results.
The last entry of that thread suggested there may be an issue with my partitions. So, I wondering if anyone knows either how to check/compare and better yet, repair if needed?
Thank you.
The last entry of that thread suggested there may be an issue with my partitions. So, I wondering if anyone knows either how to check/compare and better yet, repair if needed?
Thank you.
Saturday, 16 July 2016
Corrupt partition /data
Okay so I recently updated my s4(att) from cyanogen 12 to cyanogen 13 (latest nightly). I went to settings/security and chose encrypt phone. After about 30 minutes of encrypting it reboot and got stuck in a bootloop. I thought no problem Ill just reflash. I go to reflash my backup and it says error mounting /data. I try formating data, factory reset, and installing the rom from scratch. It seems my data partition corrupt. So I figure fastboot. Yet upon loading fastboot I cant get adb to see my device. I think I got the right drivers installed. But nothing. Any help would be greatly appreciated.
Thursday, 14 July 2016
Oneplus 3 partition table
Hi !
I rescently flashed a zip on OP3 i made for my good old Nexus 5, but it failed, as it didnt mounted system and set_perms had failed so.
So i started to dig in /dev/block to find where were the system partition and the idea of searching for full partition table crossed my head.
So here's what i found :
Partitions names are here :
What i wrote on terminal, using adb shell with root access :
I assigned each partition with its space, in kb, to get the full partition table :
I rescently flashed a zip on OP3 i made for my good old Nexus 5, but it failed, as it didnt mounted system and set_perms had failed so.
So i started to dig in /dev/block to find where were the system partition and the idea of searching for full partition table crossed my head.
So here's what i found :
Partitions names are here :
Code:
/dev/block/platform/soc/624000.ufshc/by-nameI assigned each partition with its space, in kb, to get the full partition table :
Code:
Size (in Kb) Partitions names and paths
---------------------------------------------------------
98304 loop0
---------------------------------------------------------
56582144 sda
8 ssd -> /dev/block/sda1
32768 persist -> /dev/block/sda2
262144 cache -> /dev/block/sda3
1024 misc -> /dev/block/sda4
512 keystore -> /dev/block/sda5
128 devcfg -> /dev/block/sda6
128 devcfgbak -> /dev/block/sda7
512 frp -> /dev/block/sda8
10240 oem_dycnvbk -> /dev/block/sda9
10240 oem_stanvbk -> /dev/block/sda10
1024 param -> /dev/block/sda11
8096 reserve1 -> /dev/block/sda12
16192 reserve2 -> /dev/block/sda13
512 config -> /dev/block/sda14
56238572 userdata -> /dev/block/sda15
---------------------------------------------------------
4096 sdb
4052 xbl -> /dev/block/sdb1
---------------------------------------------------------
4096 sdc
4052 xblbak -> /dev/block/sdc1
---------------------------------------------------------
131072 sdd
32 reserve -> /dev/block/sdd1
4 cdt -> /dev/block/sdd2
1024 ddr -> /dev/block/sdd3
---------------------------------------------------------
4194304 sde
512 rpm -> /dev/block/sde1
512 rpmbak -> /dev/block/sde2
2048 tz -> /dev/block/sde3
2048 tzbak -> /dev/block/sde4
512 hyp -> /dev/block/sde5
512 hypbak -> /dev/block/sde6
2048 fsg -> /dev/block/sde7
16 sec -> /dev/block/sde8
512 pmic -> /dev/block/sde9
512 pmicbak -> /dev/block/sde10
97280 modem -> /dev/block/sde11
16384 dsp -> /dev/block/sde12
1024 dip -> /dev/block/sde13
32768 mdtp -> /dev/block/sde14
8192 aboot -> /dev/block/sde15
8192 abootbak -> /dev/block/sde16
16384 LOGO -> /dev/block/sde17
65536 boot -> /dev/block/sde18
65536 boot_aging -> /dev/block/sde19
3080192 system -> /dev/block/sde20
65536 recovery -> /dev/block/sde21
4 devinfo -> /dev/block/sde22
1024 bluetooth -> /dev/block/sde23
512 keymaster -> /dev/block/sde24
512 keymasterbak -> /dev/block/sde25
256 cmnlib -> /dev/block/sde26
256 cmnlibbak -> /dev/block/sde27
256 cmnlib64 -> /dev/block/sde28
256 cmnlib64bak -> /dev/block/sde29
256 apdp -> /dev/block/sde30
256 msadp -> /dev/block/sde31
4 dpo -> /dev/block/sde32
33424 splash -> /dev/block/sde33
2048 sti -> /dev/block/sde34
---------------------------------------------------------
1572864 sdf
2048 modemst1 -> /dev/block/sdf1 (EFS1 i suppose)
2048 modemst2 -> /dev/block/sdf2 (EFS1 i suppose)
4 fsc -> /dev/block/sdf3
512 md5 -> /dev/block/sdf4
Subscribe to:
Posts (Atom)