Related
since the s-off thread is so long with all the discussion going on...
I like to create a new thread for all the materials related to s-off.
There is my partition dumps from my s-off htc evita (htc one xl / att/rogers ht one x)
mmcblk0p from 1 -38 excluding
33 system
22 recovery
34 cache
35 userdata
36 fat
https://www.dropbox.com/sh/tmpa7i7ibjy0ciy/lnAD6aSvBS
include:
s-off partitions from niceppl
"this is dumped from a supercid, 1.85 and cleanrom 2.1 s-off phone just fyi."
s-on partitions from dharani1234
"here are the partitions from an unlocked bootloader ,rooted RUU - 1.85 with superCID."
I have to replaced my imei sn and mb for the s-off partitions dumps.
with
000000000000000
999999999999
8888888888888
in 4-6 partitions...so if you see those, you know what they are...
Heres a mirror:
http://goo.im/devs/rohan/evita/soff
(feel free to update the OP with this link since this won't run out of bandwidth)
niceppl said:
since the s-off thread is so long with all the discussion going on...
I like to create a new thread for all the materials related to s-off.
There is my partition dumps from my s-off htc evita (htc one xl / att/rogers ht one x)
mmcblk0p from 1 -38 excluding
33 system
22 recovery
34 cache
35 userdata
36 fat
https://www.dropbox.com/sh/tmpa7i7ibjy0ciy/lnAD6aSvBS
include:
s-off partitions from niceppl
"this is dumped from a supercid, 1.85 and cleanrom 2.1 s-off phone just fyi."
s-on partitions from dharani1234
"here are the partitions from an unlocked bootloader ,rooted RUU - 1.85 with superCID."
I have to replaced my imei sn and mb for the s-off partitions dumps.
with
000000000000000
999999999999
8888888888888
in 4-6 partitions...so if you see those, you know what they are...
Click to expand...
Click to collapse
EDIT - I see these are from the 1.85 RUU, I need 1.73...
I'm gonna repost this here in the hopes that those checking this thread might actually care to share their thoughts...
JeepFreak said:
I'm trying to mount dd images of the partitions in /dev/block on my Linux box, but mount can't figure out the filesystem types used. I found some of them by running the "mount" command with no parameters on on the phone, but there are still a bunch of partitions that I can't identify (list below). I've tried ext4, vfat, sysfs, tmpfs, debugfs, and others with no luck. What else might they be?
Strangely, when I try to mount with sysfs, tmpfs, and debugfs it shows me files that aren't actually on the partition.
Anyway, the non-bolded ones below are the ones I'm still trying to mount:
mmcblk0p1
mmcblk0p2
mmcblk0p3
mmcblk0p4
mmcblk0p5
mmcblk0p6
mmcblk0p7
mmcblk0p8
mmcblk0p9
mmcblk0p10
mmcblk0p11
mmcblk0p12
mmcblk0p13
mmcblk0p14
mmcblk0p15
mmcblk0p16
mmcblk0p17
mmcblk0p18
mmcblk0p19
mmcblk0p20
mmcblk0p21
mmcblk0p22
mmcblk0p23
mmcblk0p24
mmcblk0p25
mmcblk0p26
mmcblk0p27
mmcblk0p28
mmcblk0p29
mmcblk0p30
mmcblk0p31
mmcblk0p32
mmcblk0p33
mmcblk0p34
mmcblk0p35
mmcblk0p36
mmcblk0p37
mmcblk0p38
Any insight is appreciated! I've been searching and guessing/checking for hours!
Click to expand...
Click to collapse
Thanks,
Billy
I am in need of the PIT file for a SCH-I535 32Gb version.
Anyone willing/able to rip one for me? My 32Gb phone got JTAG'd back to life but using files from a 16Gb version, so it's kinda confused as to how much internal storage it has. I'm hoping I can flash the PIT from a 32Gb phone, then do a reinstall of the ROM and it'll recognize all of my available storage....
Thanks for your help!
-Andy
EDIT:
Problem solved: See post#57
Bump
Sent from my SCH-I535 using xda app-developers app
letinsh said:
I am in need of the PIT file for a SCH-I535 32Gb version.
Anyone willing/able to rip one for me? My 32Gb phone got JTAG'd back to life but using files from a 16Gb version, so it's kinda confused as to how much internal storage it has. I'm hoping I can flash the PIT from a 32Gb phone, then do a reinstall of the ROM and it'll recognize all of my available storage....
Thanks for your help!
-Andy
Click to expand...
Click to collapse
do you have a pit from the 16 gb version
man that would be great if somebody would post a pitfile for both versions...I know that would help a few folks that corrupted thier emmc internal memory and get the "e cant mount" errors in recovery.
I am game ... how would I extract the PIT file?
Sent from my SCH-I535 using xda premium
Standby. Getting confirmation, then I'll post instructions.
Sent from my SCH-I535 using xda app-developers app
bump...
il gladly dump my 32gb blue if there's instructions.
here is some info from the i9300 forum
http://forum.xda-developers.com/showthread.php?t=1742668
What I'm trying to get confirmation on is using darkyy's dd command from the first post in this thread:
http://forum.xda-developers.com/showthread.php?t=960946
Just trying to verify that's the correct place to get it for the SGS3 and that that would produce a flashable .pit file.
Sent from my SCH-I535 using xda app-developers app
please post as soon as you get the ok because i think then we would also be able to use heimdall but i might be wrong.
Bump
Sent from my SCH-I535 using xda premium
aight, darkyy's method won't work as /dev/mount/bml2 (or any of the bml's) doesn't exist on the GS3. I think I posted without knowing enough info.
I don't know where the PIT file's located on the GS3, and whether it's a function of the phone or the OS (ie ICS vs Gingerbread). I didn't have time over the weekend to look into it, too much. Going to look on that i9300 thread posted and also try to learn a little about Heimdall, as I've only ever used Odin.
To sum up:
Goal is to have a .pit file for SCH-I535 for both the 16Gb and 32Gb versions.
Needed:
I don't know enough about Android/SGS3 to know where the .pit is located. Once that's determined, we'll figure out how to extract it and make a functional flash.
Sorry for the false start, still learning here.
letinsh said:
aight, darkyy's method won't work as /dev/mount/bml2 (or any of the bml's) doesn't exist on the GS3. I think I posted without knowing enough info.
I don't know where the PIT file's located on the GS3, and whether it's a function of the phone or the OS (ie ICS vs Gingerbread). I didn't have time over the weekend to look into it, too much. Going to look on that i9300 thread posted and also try to learn a little about Heimdall, as I've only ever used Odin.
To sum up:
Goal is to have a .pit file for SCH-I535 for both the 16Gb and 32Gb versions.
Needed:
I don't know enough about Android/SGS3 to know where the .pit is located. Once that's determined, we'll figure out how to extract it and make a functional flash.
Sorry for the false start, still learning here.[/QUOTE\]
Maybe try the code won't work is you have to use with yaffs2 in the middle or somewhere, i know that the phone runs off of that but that's pretty much all i say since i don't know much.
Click to expand...
Click to collapse
joka10 said:
Maybe try the code won't work is you have to use with yaffs2 in the middle or somewhere, i know that the phone runs off of that but that's pretty much all i say since i don't know much.
Click to expand...
Click to collapse
What I was saying is that /dev/block/bml2 doesn't exist in our file structure on this phone.
Code:
C:\Users\my_computer>adb shell
~ # cd /dev/block
cd /dev/block
/dev/block # ls
ls
loop0 mmcblk0boot0 mmcblk0p16 mmcblk0p3 platform ram2
loop1 mmcblk0boot1 mmcblk0p17 mmcblk0p4 ram0 ram3
loop2 mmcblk0p1 mmcblk0p18 mmcblk0p5 ram1 ram4
loop3 mmcblk0p10 mmcblk0p19 mmcblk0p6 ram10 ram5
loop4 mmcblk0p11 mmcblk0p2 mmcblk0p7 ram11 ram6
loop5 mmcblk0p12 mmcblk0p20 mmcblk0p8 ram12 ram7
loop6 mmcblk0p13 mmcblk0p21 mmcblk0p9 ram13 ram8
loop7 mmcblk0p14 mmcblk0p22 mmcblk1 ram14 ram9
mmcblk0 mmcblk0p15 mmcblk0p23 mmcblk1p1 ram15
/dev/block #
As you can see, no bml's of any kind.
I don't know if that's because darkyy was messing with a GB version of Android, or because the phone (Samsung) has put the PIT file in a different location. I've got a PM out to Odia from that I9300 thread and he should have some helpful info as to where it's stored and how to get it.
Stay tuned.
letinsh said:
What I was saying is that /dev/block/bml2 doesn't exist in our file structure on this phone.
Code:
C:\Users\my_computer>adb shell
~ # cd /dev/block
cd /dev/block
/dev/block # ls
ls
loop0 mmcblk0boot0 mmcblk0p16 mmcblk0p3 platform ram2
loop1 mmcblk0boot1 mmcblk0p17 mmcblk0p4 ram0 ram3
loop2 mmcblk0p1 mmcblk0p18 mmcblk0p5 ram1 ram4
loop3 mmcblk0p10 mmcblk0p19 mmcblk0p6 ram10 ram5
loop4 mmcblk0p11 mmcblk0p2 mmcblk0p7 ram11 ram6
loop5 mmcblk0p12 mmcblk0p20 mmcblk0p8 ram12 ram7
loop6 mmcblk0p13 mmcblk0p21 mmcblk0p9 ram13 ram8
loop7 mmcblk0p14 mmcblk0p22 mmcblk1 ram14 ram9
mmcblk0 mmcblk0p15 mmcblk0p23 mmcblk1p1 ram15
/dev/block #
As you can see, no bml's of any kind.
I don't know if that's because darkyy was messing with a GB version of Android, or because the phone (Samsung) has put the PIT file in a different location. I've got a PM out to Odia from that I9300 thread and he should have some helpful info as to where it's stored and how to get it.
Stay tuned.
Click to expand...
Click to collapse
Yea your right it's because he's using a exynos processor instead of the one we have, have you tried replacing the command with those listed above. I know from the odin thread it can't be mmcblk0p1, mmcblk0p15, mmcblk0p18,mmcblk0p14, mmcblk0p12, mmcblk0p13, mmcblk0p17, nor mmcblk0p7.
joka10 said:
Yea your right it's because he's using a exynos processor instead of the one we have, have you tried replacing the command with those listed above. I know from the odin thread it can't be mmcblk0p1, mmcblk0p15, mmcblk0p18,mmcblk0p14, mmcblk0p12, mmcblk0p13, mmcblk0p17, nor mmcblk0p7.
Click to expand...
Click to collapse
Here's the partition table as seen when using the "parted print" command on a properly formatted VZW SGS3 32Gb:
Code:
Disk /dev/block/mmcblk0: 31268536320B
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 4194304B 67108863B 62914560B modem
2 67108864B 67239935B 131072B sbl1
3 67239936B 67502079B 262144B sbl2
4 67502080B 68026367B 524288B sbl3
5 68026368B 70123519B 2097152B aboot
6 70123520B 70647807B 524288B rpm
7 70647808B 81133567B 10485760B boot
8 81133568B 81657855B 524288B tz
9 81657856B 82182143B 524288B pad
10 82182144B 92667903B 10485760B param
11 92667904B 106954751B 14286848B ext4 efs
12 106954752B 110100479B 3145728B modemst1
13 110100480B 113246207B 3145728B modemst2
14 113246208B 1686110207B 1572864000B ext4 system
15 1686110208B 30337400831B 28651290624B ext4 userdata
16 30337400832B 30345789439B 8388608B ext4 persist
17 30345789440B 31226593279B 880803840B ext4 cache
18 31226593280B 31237079039B 10485760B recovery
19 31237079040B 31247564799B 10485760B fota
20 31247564800B 31253856255B 6291456B backup
21 31253856256B 31257001983B 3145728B fsg
22 31257001984B 31257010175B 8192B ssd
23 31257010176B 31262253055B 5242880B grow
So, from this, we know it's not any of the mmcblk0p1 through mmcblk0p23 partitions.
If you notice, partition 1 starts 4Mb into storage. I think the PIT is located somewhere in the first 4Mb, but I don't know what memory addresses/file to look under to grab it.... is it in one of the other locations listed above under /dev/block ? Is it in /dev/block/mmcblk0/ ? I just don't know....
After looking at Heimdall, the tool has an option to rip the PIT, but I haven't been able to get it to recognize my SGS3. I've tried both 1.3.2 and 1.3.1
Once that's ripped, can we flash it using Odin in the PIT field? Or do we have to use Heimdall to to put it back?
letinsh said:
Here's the partition table as seen when using the "parted print" command on a properly formatted VZW SGS3 32Gb:
Code:
Disk /dev/block/mmcblk0: 31268536320B
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 4194304B 67108863B 62914560B modem
2 67108864B 67239935B 131072B sbl1
3 67239936B 67502079B 262144B sbl2
4 67502080B 68026367B 524288B sbl3
5 68026368B 70123519B 2097152B aboot
6 70123520B 70647807B 524288B rpm
7 70647808B 81133567B 10485760B boot
8 81133568B 81657855B 524288B tz
9 81657856B 82182143B 524288B pad
10 82182144B 92667903B 10485760B param
11 92667904B 106954751B 14286848B ext4 efs
12 106954752B 110100479B 3145728B modemst1
13 110100480B 113246207B 3145728B modemst2
14 113246208B 1686110207B 1572864000B ext4 system
15 1686110208B 30337400831B 28651290624B ext4 userdata
16 30337400832B 30345789439B 8388608B ext4 persist
17 30345789440B 31226593279B 880803840B ext4 cache
18 31226593280B 31237079039B 10485760B recovery
19 31237079040B 31247564799B 10485760B fota
20 31247564800B 31253856255B 6291456B backup
21 31253856256B 31257001983B 3145728B fsg
22 31257001984B 31257010175B 8192B ssd
23 31257010176B 31262253055B 5242880B grow
So, from this, we know it's not any of the mmcblk0p1 through mmcblk0p23 partitions.
If you notice, partition 1 starts 4Mb into storage. I think the PIT is located somewhere in the first 4Mb, but I don't know what memory addresses/file to look under to grab it.... is it in one of the other locations listed above under /dev/block ? Is it in /dev/block/mmcblk0/ ? I just don't know....
After looking at Heimdall, the tool has an option to rip the PIT, but I haven't been able to get it to recognize my SGS3. I've tried both 1.3.2 and 1.3.1
Once that's ripped, can we flash it using Odin in the PIT field? Or do we have to use Heimdall to to put it back?
Click to expand...
Click to collapse
Heimdall has never been able to recognize my phone...and I was looking somewhere and the developer said it wasn't working and to try 1.3.1 which was not successful either. I had to borrow a computer to use Odin...I know this isn't a solution for getting heimdall to work but I personally don't think it will...if you do get it to work the steps you took would be appreciated
Sent from my SCH-I535 using xda premium
letinsh said:
Here's the partition table as seen when using the "parted print" command on a properly formatted VZW SGS3 32Gb:
Code:
Disk /dev/block/mmcblk0: 31268536320B
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 4194304B 67108863B 62914560B modem
2 67108864B 67239935B 131072B sbl1
3 67239936B 67502079B 262144B sbl2
4 67502080B 68026367B 524288B sbl3
5 68026368B 70123519B 2097152B aboot
6 70123520B 70647807B 524288B rpm
7 70647808B 81133567B 10485760B boot
8 81133568B 81657855B 524288B tz
9 81657856B 82182143B 524288B pad
10 82182144B 92667903B 10485760B param
11 92667904B 106954751B 14286848B ext4 efs
12 106954752B 110100479B 3145728B modemst1
13 110100480B 113246207B 3145728B modemst2
14 113246208B 1686110207B 1572864000B ext4 system
15 1686110208B 30337400831B 28651290624B ext4 userdata
16 30337400832B 30345789439B 8388608B ext4 persist
17 30345789440B 31226593279B 880803840B ext4 cache
18 31226593280B 31237079039B 10485760B recovery
19 31237079040B 31247564799B 10485760B fota
20 31247564800B 31253856255B 6291456B backup
21 31253856256B 31257001983B 3145728B fsg
22 31257001984B 31257010175B 8192B ssd
23 31257010176B 31262253055B 5242880B grow
So, from this, we know it's not any of the mmcblk0p1 through mmcblk0p23 partitions.
If you notice, partition 1 starts 4Mb into storage. I think the PIT is located somewhere in the first 4Mb, but I don't know what memory addresses/file to look under to grab it.... is it in one of the other locations listed above under /dev/block ? Is it in /dev/block/mmcblk0/ ? I just don't know....
After looking at Heimdall, the tool has an option to rip the PIT, but I haven't been able to get it to recognize my SGS3. I've tried both 1.3.2 and 1.3.1
Once that's ripped, can we flash it using Odin in the PIT field? Or do we have to use Heimdall to to put it back?
Click to expand...
Click to collapse
We can use either or I thin for odin you flash using repartition checked and placing it in the pda field but it will allow us to flash with heimdall using that pit since it can't find the one on the phone. Lastly internal flash /dev/block/mmcblk0 becomes /dev/block/mmcblk1 is what i have found so it looks like either im wrong or it has to be one of the 24 blocks.
Can someone with a working 32 run this in a Terminal? It should pull the PIT from your phone and place it in the SD card. I'm sure those with a 16gb would love to have their PIT file as well.
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/pit.bin bs=4096 count=1 skip=4
Info from HERE (International device, but the blocks should be the same)
Hello
I want to make an image Back-up of my Core and I cannot find something!
I tried the search but I couldn't.
I tried also the rom manager but it does not support my Core.
I want to make this image back up so I can go back if i install an other ROM.
How can I do this?
I hope you can help me!!
(I have already succesfully rooted my phone)
Thank you for your time and help!
trelozakinthinos said:
Hello
I want to make an image Back-up of my Core and I cannot find something!
I tried the search but I couldn't.
I tried also the rom manager but it does not support my Core.
I want to make this image back up so I can go back if i install an other ROM.
How can I do this?
I hope you can help me!!
(I have already succesfully rooted my phone)
Thank you for your time and help!
Click to expand...
Click to collapse
Try this. https://play.google.com/store/apps/details?id=com.h3r3t1c.onnandbup PM me if u have any problems.
Smack that Thanks button if I helped!
KitKat came in on my OmniROM, running on my Note 2.
Sent from a small country called Singapore.
P.S. Time for school, not much time for XDA
Irwenzhao said:
Try this. nandroid PM me if u have any problems.
Smack that Thanks button if I helped!
KitKat came in on my OmniROM, running on my Note 2.
Sent from a small country called Singapore.
P.S. Time for school, not much time for XDA
Click to expand...
Click to collapse
Thank you for your reply... I have used already this app and I have some questions...
a) When it asks me for select device it says
"Your device code is arubaslimss. Please select the path that corresponds to your device!
If device is nit in list please click the Get Identified button"
So my phone is not on the list and I clicked the get identified button and it sends an email
Code:
Android version: REL 4.1.2
onandroid script version: 9.2
Device: arubaslimss samsung samsung GT-I8260
Contents of: /proc/partitions
major minor #blocks name
179 0 7634944 mmcblk0
179 1 20 mmcblk0p1
179 2 175 mmcblk0p2
179 3 20480 mmcblk0p3
179 4 1 mmcblk0p4
179 5 1000 mmcblk0p5
179 6 1000 mmcblk0p6
179 7 2000 mmcblk0p7
179 8 12288 mmcblk0p8
179 9 3072 mmcblk0p9
179 10 3072 mmcblk0p10
179 11 4096 mmcblk0p11
179 12 8192 mmcblk0p12
179 13 12288 mmcblk0p13
179 14 4096 mmcblk0p14
179 15 4096 mmcblk0p15
179 16 12288 mmcblk0p16
179 17 24576 mmcblk0p17
179 18 4096 mmcblk0p18
179 19 512 mmcblk0p19
179 20 2048 mmcblk0p20
179 21 1331200 mmcblk0p21
179 22 737280 mmcblk0p22
179 23 327680 mmcblk0p23
179 24 5115488 mmcblk0p24
179 32 3870720 mmcblk1
179 33 3869696 mmcblk1p1
I din't get any response yet...
b) Without identifying my phone I pressed the backup and it did a 2GB backup.
Although I don't know how to check if this works. I mean I can't my phone restore this backup. Any help?
trelozakinthinos said:
Thank you for your reply... I have used already this app and I have some questions...
a) When it asks me for select device it says
"Your device code is arubaslimss. Please select the path that corresponds to your device!
If device is nit in list please click the Get Identified button"
So my phone is not on the list and I clicked the get identified button and it sends an email
Code:
Android version: REL 4.1.2
onandroid script version: 9.2
Device: arubaslimss samsung samsung GT-I8260
Contents of: /proc/partitions
major minor #blocks name
179 0 7634944 mmcblk0
179 1 20 mmcblk0p1
179 2 175 mmcblk0p2
179 3 20480 mmcblk0p3
179 4 1 mmcblk0p4
179 5 1000 mmcblk0p5
179 6 1000 mmcblk0p6
179 7 2000 mmcblk0p7
179 8 12288 mmcblk0p8
179 9 3072 mmcblk0p9
179 10 3072 mmcblk0p10
179 11 4096 mmcblk0p11
179 12 8192 mmcblk0p12
179 13 12288 mmcblk0p13
179 14 4096 mmcblk0p14
179 15 4096 mmcblk0p15
179 16 12288 mmcblk0p16
179 17 24576 mmcblk0p17
179 18 4096 mmcblk0p18
179 19 512 mmcblk0p19
179 20 2048 mmcblk0p20
179 21 1331200 mmcblk0p21
179 22 737280 mmcblk0p22
179 23 327680 mmcblk0p23
179 24 5115488 mmcblk0p24
179 32 3870720 mmcblk1
179 33 3869696 mmcblk1p1
I din't get any response yet...
b) Without identifying my phone I pressed the backup and it did a 2GB backup.
Although I don't know how to check if this works. I mean I can't my phone restore this backup. Any help?
Click to expand...
Click to collapse
Guess the phone's not supported yet then. But if u already made a backup, backup all your apps using helium (backup to sd) and try restoring using the backup u have. (wipe data first)
Smack that Thanks button if I helped!
KitKat came in on my OmniROM, running on my Note 2.
Sent from a small country called Singapore.
P.S. Time for school, not much time for XDA
trelozakinthinos said:
Hello
I want to make an image Back-up of my Core and I cannot find something!
I tried the search but I couldn't.
I tried also the rom manager but it does not support my Core.
I want to make this image back up so I can go back if i install an other ROM.
How can I do this?
I hope you can help me!!
(I have already succesfully rooted my phone)
Thank you for your time and help!
Click to expand...
Click to collapse
Use CWM to backup the phone. It's way easier. Preferably backup to external sd card
sawan.aware.1 said:
Use CWM to backup the phone. It's way easier. Preferably backup to external sd card
Click to expand...
Click to collapse
CWM does not work with my phone! Not in the list! That's why I was searching for nandroid!
trelozakinthinos said:
CWM does not work with my phone! Not in the list! That's why I was searching for nandroid!
Click to expand...
Click to collapse
Dude follow guide in forum of galaxy core. Cwm is ported for galaxy core amd I am using cwm. It's yet not available in list.
sawan.aware.1 said:
Dude follow guide in forum of galaxy core. Cwm is ported for galaxy core amd I am using cwm. It's yet not available in list.
Click to expand...
Click to collapse
Sorry my friend but I do not understant this. What it means ported?
I downloaded but when i try to find my phone on the list i can't! so I can't use it. Right?
Where exavtly in the galaxy core forum? Give me a link please!
Thank you
trelozakinthinos said:
Sorry my friend but I do not understant this. What it means ported?
I downloaded but when i try to find my phone on the list i can't! so I can't use it. Right?
Where exavtly in the galaxy core forum? Give me a link please!
Thank you
Click to expand...
Click to collapse
Here is the link where you can find cwm for galaxy core and its working. The issues are also discussed.
http://forum.xda-developers.com/showthread.php?t=2517850
1) Remove SD card
2) Boot into CWM Recovery by pressing Power + Volume Up + Home button.
3) Choose "Backup and Restore" and then choose "Backup".
Wait for few minutes and you will get your Nandroid backup in phone's internal memory.
NOTE : You should have enough memory(around 1.8GB - it was in my case) and yup i have got BLACK screen when i did it without removing SD card so i have said remove SD card in the very first step.
I have succesfully backed up my phone's ROM without removing the SD CARD, many times. I haven't got any error's afterall.
Personally, I don't recommend backing up to the internal memory, because it's the /data partition, wich oftenly gets wiped (or you wipe it yourself) when flashing a new ROM.
Just some thought.
MirXas said:
I have succesfully backed up my phone's ROM without removing the SD CARD, many times. I haven't got any error's afterall.
Personally, I don't recommend backing up to the internal memory, because it's the /data partition, wich oftenly gets wiped (or you wipe it yourself) when flashing a new ROM.
Just some thought.
Click to expand...
Click to collapse
You are right friend but i just told him how to take nandroid backup and that is just a matter of common sense that anyone will transfer the backup either to PC or external SD card.
How big is nandroid backup for Core? (Stock rom)
friendfriend said:
How big is nandroid backup for Core? (Stock rom)
Click to expand...
Click to collapse
Depends on what you have. Mine was over 2GB
1 gb
Sent from my GT-I8260 using XDA Premium 4 mobile app
Depends on how much tada you have in your /data and /system partitions, 'cause all of that is backed up. Mine was from 1 to about 1,5 GB.
Sent from my Lenovo A3000-H using xda app-developers app
mine was 1.8 gb on stock odexed rom
Sent from my GT-I8262 using XDA Premium 4 mobile app
Mine iz 1.7gb.
Hi guys,
I have a device called "bingo future star fs1" which is not listed in your device listing. This is a pretty new company with this just one android phone. No official/unofficial ROM is available to reflash the firmware. The only good thing i have is CWM restorable backup in my 32gb SD card. I am unable to restore it because my internal partitions are messed up.
I had my device rooted and CWM installed. On reading from google search, i found an application that claimed to increase the application memory by resizing the internal card partition.(my device had 1gb app memory, 1.7gb internal card, 4gb ROM). I did everything correct and after restarting the device it only shows the logo forever. However, i am able to reach CWM recovery but cant restore the backup i have. It says
E : cant mount cache
E : unable to mount cache/last log or something similar
when i try to restore the backup, it gives "Error while formatting system"
E:format_volume : make_extf4fs failed on /dev/block/mmcblk0p5
I again read a lot of posts from google search and XDA and tried with parted. I pushed parted files via adb, chmodded them. After reaching the step where we can see all contents of partition 0, it says "Error:cant have partition outside the disk" .
Code:
loop0 loop4 mmcblk0 mmcblk0p2 mmcblk1p1
loop1 loop5 mmcblk0boot0 mmcblk0p3 platform
loop2 loop6 mmcblk0boot1 mmcblk0p4 zram0
loop3 loop7 mmcblk0p1 mmcblk1
I dont know what to do. Please help!
phploaded said:
Hi guys,
I have a device called "bingo future star fs1" which is not listed in your device listing. This is a pretty new company with this just one android phone. No official/unofficial ROM is available to reflash the firmware. The only good thing i have is CWM restorable backup in my 32gb SD card. I am unable to restore it because my internal partitions are messed up.
I had my device rooted and CWM installed. On reading from google search, i found an application that claimed to increase the application memory by resizing the internal card partition.(my device had 1gb app memory, 1.7gb internal card, 4gb ROM). I did everything correct and after restarting the device it only shows the logo forever. However, i am able to reach CWM recovery but cant restore the backup i have. It says
E : cant mount cache
E : unable to mount cache/last log or something similar
when i try to restore the backup, it gives "Error while formatting system"
E:format_volume : make_extf4fs failed on /dev/block/mmcblk0p5
I again read a lot of posts from google search and XDA and tried with parted. I pushed parted files via adb, chmodded them. After reaching the step where we can see all contents of partition 0, it says "Error:cant have partition outside the disk" .
Code:
loop0 loop4 mmcblk0 mmcblk0p2 mmcblk1p1
loop1 loop5 mmcblk0boot0 mmcblk0p3 platform
loop2 loop6 mmcblk0boot1 mmcblk0p4 zram0
loop3 loop7 mmcblk0p1 mmcblk1
I dont know what to do. Please help!
Click to expand...
Click to collapse
Sir can you please tell,how to install cwm in FS1.
Hello!
I need enlightenment and help from all of you, I spent hours looking for information and solutions but I wasn't able to find a situation similar to mine, rather small pieces from different scenarios.
Here's my situation:
After installing lj50036's pre-nightly OmniROM and setting it up, I decided to reboot and "clean" it. My BIG mistake was that for some reason (probably sleep-deprivation effects) I thought that doing a format in TWRP was a good idea...yeah, messed up.
I will try my best to describe the current situation and the solutions that I tried...
Currently, I am able to access fastboot and ADB sideload., even able to flash the recovery. The problem lies with not being able to install a ROM properly. What I can't do is access TWRP after a reboot, I must first flash it via fastboot in order to be able to access it, then of course it will reset after a reboot. TWRP will just keep being stuck in a loop if I don't go to fastboot. Whenever I try to install a ROM, it will fail not long after due to errors like : "Unable to mount data, system,cache etc."
I tried the following:
-The 'Repair' option in the advanced menu.
-Formatting using the 'ADB shell..." commands (I'm trying to find the correct command, as soon I arrive to my desktop, I'll update this post). What I did noticed is after entering that command, it would return strange characters. According to some posts, it could be some color formatting but I'm not sure.
-'sideloading' recoveries and ROMs.
INFO:
-Bootloader is 10.6.1.14.10
-Recovery is TWRP 2.8.6.0
From what I read, my guess is to correct the partition errors. Any tips on how to achieve this?
Could this be fixed by flashing a new bootloader or would it make it worse? I don't want to risk it further until I get some professional advice
Any assistance is greatly appreciated, Thank you all!
razgrizpr said:
Hello!
Here's my situation:
After installing lj50036's pre-nightly OmniROM and setting it up, I decided to reboot and "clean" it. My BIG mistake was that for some reason (probably sleep-deprivation effects) I thought that doing a format in TWRP was a good idea...yeah, messed up.
Click to expand...
Click to collapse
Why was doing a format a BIG mistake ???
Thx Josh
lj50036 said:
Why was doing a format a BIG mistake ???
Thx Josh
Click to expand...
Click to collapse
Doesn't formatting via TWRP erase all the data including the OS?
razgrizpr said:
Doesn't formatting via TWRP erase all the data including the OS?
Click to expand...
Click to collapse
Depends what partitions you formatted. The OS is in /system; your data is in /data.
_that said:
Depends what partitions you formatted. The OS is in /system; your data is in /data.
Click to expand...
Click to collapse
Makes sense. So I guess I erased them all? I honestly don't know since I left it formatting and returned a few hours later only to find it turned off. When I booted it, I experienced the mentioned issues. Battery was full as well. So maybe something went wrong during the formatting?
Is there a way to diagnose the partitions?
Did you try this?
http://forum.xda-developers.com/showpost.php?p=54521117&postcount=10
berndblb said:
Did you try this?
http://forum.xda-developers.com/showpost.php?p=54521117&postcount=10
Click to expand...
Click to collapse
Yes, I tried that. Upon entering 'make_ext4fs /dev/block/mmcblk0p8' I get the message 'Need size of file system'.
Found a similar thread where the issue was not being able to mount /data. It appears that for some people 'this' helped them although I'm not sure if I should try it. Others have mentioned 'downgrading' the bootloader and then go through all the process again with success.
razgrizpr said:
Yes, I tried that. Upon entering 'make_ext4fs /dev/block/mmcblk0p8' I get the message 'Need size of file system'.
Found a similar thread where the issue was not being able to mount /data. It appears that for some people 'this' helped them although I'm not sure if I should try it. Others have mentioned 'downgrading' the bootloader and then go through all the process again with success.
Click to expand...
Click to collapse
From recovery run this and post the output ....
Code:
adb pull /proc/partitions
You will get a file called 'partitions' in the current directory.....
Thx Josh
lj50036 said:
From recovery run this and post the output ....
Code:
adb pull /proc/partitions
You will get a file called 'partitions' in the current directory.....
Thx Josh
Click to expand...
Click to collapse
Thank you lj50036, I'm at work at the moment so I will try that as soon I get home and report back.
lj50036 said:
From recovery run this and post the output ....
Code:
adb pull /proc/partitions
You will get a file called 'partitions' in the current directory.....
Thx Josh
Click to expand...
Click to collapse
Here are the results:
Code:
major minor #blocks name
179 0 31039488 mmcblk0
179 32 2048 mmcblk0boot1
179 16 2048 mmcblk0boot0
179 48 31166976 mmcblk1
179 49 24901600 mmcblk1p1
razgrizpr said:
Here are the results:
Code:
major minor #blocks name
179 0 31039488 mmcblk0
179 32 2048 mmcblk0boot1
179 16 2048 mmcblk0boot0
179 48 31166976 mmcblk1
179 49 24901600 mmcblk1p1
Click to expand...
Click to collapse
Code:
major minor #blocks name
179 0 31039488 mmcblk0
179 1 786432 mmcblk0p1
179 2 438272 mmcblk0p2
179 3 2048 mmcblk0p3
179 4 835584 mmcblk0p4
179 5 5120 mmcblk0p5
179 6 512 mmcblk0p6
179 7 5120 mmcblk0p7
179 8 28924416 mmcblk0p8
179 9 8192 mmcblk0p9
179 10 8192 mmcblk0p10
179 32 2048 mmcblk0boot1
179 16 2048 mmcblk0boot0
That is what it should look like ....
So if you still have fastboot flash the pt.blob will give you these partition back ....
After you flash the pt.blob boot back into recovery and run the same command and see it matches mine ...
Thx Josh
lj50036 said:
Code:
major minor #blocks name
179 0 31039488 mmcblk0
179 1 786432 mmcblk0p1
179 2 438272 mmcblk0p2
179 3 2048 mmcblk0p3
179 4 835584 mmcblk0p4
179 5 5120 mmcblk0p5
179 6 512 mmcblk0p6
179 7 5120 mmcblk0p7
179 8 28924416 mmcblk0p8
179 9 8192 mmcblk0p9
179 10 8192 mmcblk0p10
179 32 2048 mmcblk0boot1
179 16 2048 mmcblk0boot0
That is what it should look like ....
So if you still have fastboot flash the pt.blob will give you these partition back ....
After you flash the pt.blob boot back into recovery and run the same command and see it matches mine ...
Thx Josh
Click to expand...
Click to collapse
Thank you so much lj50036!
Looks like correcting the partitions did the trick. After flashing the file, I managed to flash the ROM successfully.
All is good now, thank you all!
razgrizpr said:
Thank you so much lj50036!
Looks like correcting the partitions did the trick. After flashing the file, I managed to flash the ROM successfully.
All is good now, thank you all!
Click to expand...
Click to collapse
Great to see you up and running ....
Can you add 'SOLVED' to the thread tittle ...... :good:
Thx Josh