I've managed to brick my ace by mounting /dev/block/stl5 on /efs and forgetting to unmount it before turning it off. Now everytime I turn it on the screen blinks at me and that's it. However, I did do a cat /dev/block/stl5 > /mnt/sdcard/efs.img and got the file over to my PC before the disaster happenned. I've tried using Odin multiloader to flash a stock rom which I know works in normal circumstances but no joy. Is there anyway to restore the above image file and get my phone working again? Many thanks in advance!
From dmesg output:
Code:
<4>Machine: GT-S5830 Board
<6>Partition (from atag) mibib -- Offset:0 Size:6
<6>Partition (from atag) qcsbl -- Offset:6 Size:2
<6>Partition (from atag) oemsbl -- Offset:8 Size:3
<6>Partition (from atag) amss -- Offset:b Size:64
<6>Partition (from atag) efs2 -- Offset:6f Size:24
<6>Partition (from atag) nv_backup -- Offset:93 Size:14
<6>Partition (from atag) arm11boot -- Offset:a7 Size:8
<6>Partition (from atag) boot -- Offset:af Size:20
The correct way to backup could be:
Code:
bml_unlock -> this is my own binary to unlock bml from koush's CWM source
dd if=/dev/block/bml5 of=/sdcard/efs2.img bs=4096
But I too scared to try it.
Go to Samsung Service Center. No one can help you here.
I've seen in the Odin flash tool there's an option to upload an efs file system. I've tried putting my efs.img in a tar file and uploading it but odin complains. There must be a way to do it somehow??
systemshq said:
I've seen in the Odin flash tool there's an option to upload an efs file system. I've tried putting my efs.img in a tar file and uploading it but odin complains. There must be a way to do it somehow??
Click to expand...
Click to collapse
Complain ? How ?
Herpderp Adreno + Tegra.
Just to summarise I did a cat /dev/block/stl5 > /mnt/sdcard/efs.img on the phone
and then on my linux pc I did tar -cvf efs.tar efs.img because odin wants a tar file. When I try to upload the file with odin it won't do it.
systemshq said:
Just to summarise I did a cat /dev/block/stl5 > /mnt/sdcard/efs.img on the phone
and then on my linux pc I did tar -cvf efs.tar efs.img because odin wants a tar file. When I try to upload the file with odin it won't do it.
Click to expand...
Click to collapse
Did you take a look at how full package files are done up for EFS ?
Herpderp Adreno + Tegra.
No I haven't been able to find out how to do this. If you could please give me a link to which shows me how I can package files up for the efs option to work I would be very grateful. Many thanks
systemshq said:
...
When I try to upload the file with odin it won't do it.
Click to expand...
Click to collapse
try:
Code:
busybox md5sum efs.tar >> efs.tar
and see, if Odin still doesn't like it. If Odin still complains, it would be interesting, what Odin is complaining about (may be Odin expects the file name efs.tar.md5, then rename efs.tar to efs.tar.md5). ...
EDIT: Remember to backup efs.tar to a safe place, before doing any further experiments!
^^
Oh yes....the contents of the .tar file must have rw-r--r-- permissions
Herpderp Adreno + Tegra.
I have the backup file on my linux pc. Just to check the experts before I proceed:-
chmod 644 efs.rfs
tar -cvf efs.tar efs.rfs
md5sum efs.tar >> efs.tar
And then put the bricked phone into download mode and use odin to upload the file.
Many thanks for all your help guys!
systemshq said:
I have the backup file on my linux pc. Just to check the experts before I proceed:-
chmod 644 efs.rfs
tar -cvf efs.tar efs.rfs
md5sum efs.tar >> efs.tar
And then put the bricked phone into download mode and use odin to upload the file.
Many thanks for all your help guys!
Click to expand...
Click to collapse
I think you should chmod the tar as well just to play safe
Herpderp Adreno + Tegra.
Gave that a try and Odin compalined with "Invalid Model Binary". Anyway many thanks for all the advice so far.
May be a solution? Sounds promising to me. Want to give it another try?
=> Restoring a dd backup with Odin (A fix for a badly broken EFS)
^^
Tried that method originally and no joy
systemshq said:
I've managed to brick my ace by mounting /dev/block/stl5 on /efs and forgetting to unmount it before turning it off. Now everytime I turn it on the screen blinks at me and that's it. However, I did do a cat /dev/block/stl5 > /mnt/sdcard/efs.img and got the file over to my PC before the disaster happenned. I've tried using Odin multiloader to flash a stock rom which I know works in normal circumstances but no joy. Is there anyway to restore the above image file and get my phone working again? Many thanks in advance!
Click to expand...
Click to collapse
where is the efs file stored? Is it on the SD card?
Yes - the file is on the sd card but I can only get the phone to start in download mode. So the sd card is useless for now
Can you put the file up here or send it to me... I need it urgently!!! Please
systemshq said:
Tried that method originally and no joy
Click to expand...
Click to collapse
Did you also tried:
(A) Give Samsung Service Center a try?
1. Safest way to get a working ACE back.
(B) Odin procedure?
---------------------------------
1. rename your efs.img backup to efs.rfs
2. tar efs.rfs to efs.tar
3. load efs.tar into EFS slot
(C) dd procedure?
-------------------------------
1. dd if=efs.img of=/dev/block/stl5 bs=4096
2. then reflash a stock samsung on top of that
The problem maybe also, that you've made a stl5 backup and not a bml5 backup. They differ completely in size:
/ # dd if=/dev/block/stl5 of=/sdcard/efs_stl5_dd.rfs bs=4096
1344+0 records in
1344+0 records out
5505024 bytes transferred in 0.930 secs (5919380 bytes/sec)
/ # dd if=/dev/block/bml5 of=/sdcard/efs_bml5_dd.rfs bs=4096
2304+0 records in
2304+0 records out
9437184 bytes transferred in 2.625 secs (3595117 bytes/sec)
Click to expand...
Click to collapse
If you want, you can upload your efs.img and I'll try to compare it to my backup.
The file has got my IMEI etc in it so please forgive that I do not upload it. If someone has a restore method which they know works please post
what folder is it stored under?
Related
[Update-Download KE8 Kernel & firmware]Dump System Image of SGS2 w/o Root Permission?
Hi,
Is there any way to dump system image and then extract Kernel files(zimage) from the current rom running on my Indian version SGS2?( which Samsung is claiming to have put the NFC chip in, but none have found it/or a way to find it yet! ) I don't have root permission ( and i know i can root using CF root but that would overwrite the kernel! ) As, you might be knowing the Indian version of SGS2 came pre-installed with KE8 firmware and we don't have a kernel repository of it yet.
The HIDSWVER on my phone is
I9100XWKE8/I9100ODDKE2/I9100DDKE2/I9100XWKE8
& *#1234# gives me,
PDA-I9100XWKE8
Phone-I9100DDKE2
CSC-I9100DDKE2
Build Info - Wed May 18 13:55:45 KST 2011
I tried to pull the /system using adb but that is not much of a help i guess. I can't use "dd if=/dev/block/*** of=/sdcard/system bs=4096" unless m rooted and i don't know the location of kernel and system images in /dev/block/? either.
Doing this in adb shell,
dd if=/dev/block/mmcblk0p9 of=/sdcard/system.img bs=4096 ( For System Image )
dd if=/dev/block/mmcblk0p5 of=/sdcard/zImage bs=4096 ( For Recovery + Kernel Image )
Click to expand...
Click to collapse
gives error that can't open /dev/block/mmcblk0p9 for read. Permission Denied.
Can you guys please help me to dump my Rom when it's not rooted? It will also make you guys upgrade it to the latest firmware. Although KE7 & KE8 are packaged on the same date and we seem to find not a single difference for now.
Update 1 :
Odia is having Samsung AnySVC access and he said he will try to put up a link to the KE8 System dump. He will also try to make an insecure KE8 kernel.
Update 2 :
For now we are trying to work on this idea as suggested by sgstwo
- Dump Rom with overwritten KE7 kernel ( We need it! )
- Extract Rooted factoryfs.img
- Flash factoryfs.img in another SGS2 with KE8 kernel
- Extract zImage
- Make a full rom dump from previous system.Img ( one we got from rooted KE7 Kernel Indian SGS2 ) and zImage from the other SGS2.
Hope this works out.
Anyone who has a Indian SGS2 and rooted with CF Root can post the whole system dump. We need it! Drop me a PM if you are unsure on how to dump your rom.
Update 3 :
XWKE8 Kernel : Download
Update 4 : So, now when we have the Full System Dump and it's also available in Samfirmware Repo.
Untouched Copy of KE8 firmware direct from Samsung Servers : Download KE8 Firmware Part 1 Part 2 Part 3
Interchangeable Links on Uploaded.to
Part 1 Part 2 Part 3
Password : gadgets.apnafundaz.com
I'm also interested about what dev/block/xxx is for Kernel zImage.
Another question i tried to dump my system image by doing this procedure:
Code:
adb shell
rootsh
dd if=/dev/block/mmcblk0p9 of=/sdcard/factoryfs.rfs bs=4096
tar -H ustar -c factoryfs.rfs > package_name.tar
md5sum -t package_name.tar >> package_name.tar
mv package_name.tar package_name.tar.md5
However i can't flash it through Odin because i got error while flashing. The Md5 check is ok, but i don't know what i am missing!
Thanks in advance!
Ghostbustersin said:
Hi,
Is there any way to dump system image and then extract Kernel files(zimage) from the current rom running on my Indian version SGS2?( which Samsung is claiming to have put the NFC chip in, but none have found it/or a way to find it yet! ) I don't have root permission ( and i know i can root using CF root but that would overwrite the kernel! ) As, you might be knowing the Indian version of SGS2 came pre-installed with KE8 firmware and we don't have a kernel repository of it yet.
The HIDSWVER on my phone is
I9100XWKE8/I9100ODDKE2/I9100DDKE2/I9100XWKE8
& *#1234# gives me,
PDA-I9100XWKE8
Phone-I9100DDKE2
CSC-I9100DDKE2
Build Info - Wed May 18 13:55:45 KST 2011
I tried to pull the /system using adb but that is not much of a help i guess. I can't use "dd if=/dev/block/*** of=/sdcard/system bs=4096" unless m rooted and i don't know the location of kernel and system images in /dev/block/? either.
I can't run #cat /proc/mtd either.
Can you guys please help me to dump my Rom when it's not rooted? It will also make you guys upgrade it to the latest firmware. Although KE7 & KE8 are packaged on the same date and we seem to find not a single difference for now. You won't be able to find KE8 even in the Sam firmware collections.
Click to expand...
Click to collapse
$ cat /proc/partitions gives you a list of all partitions, $ mount should give you the system partition. I haven't found the recovery partition yet.
Thijs96 said:
$ cat /proc/partitions gives you a list of all partitions, $ mount should give you the system partition. I haven't found the recovery partition yet.
Click to expand...
Click to collapse
There is no recovery partition. It's in the kernel, which is /dev/block/mmcblk0p5
You can't get near it without root
pulser_g2 said:
There is no recovery partition. It's in the kernel, which is /dev/block/mmcblk0p5
You can't get near it without root
Click to expand...
Click to collapse
First of all thanks a lot for your prompt reply.
However, I can't create a Custom ODIN Images for Backup/Restore...
Here is what i did so far
Code:
dd if=/dev/block/mmcblk0p9 of=/sdcard/factoryfs.rfs bs=4096
dd if=/dev/block/mmcblk0p5 of=/sdcard/zImage bs=4096
tar -H ustar -c factoryfs.rfs zImage > my_temp_package.tar
md5sum -t my_temp_package.tar >> my_temp_package.tar
mv my_temp_package.tar my_temp_package.tar.md5
At this point when i flash this through Odin by selecting my_temp_package.tar.md5 in PDA, it fail and i got the following output:
Code:
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Get PIT for mapping..
<ID:0/011> Firmware update start..
<ID:0/011> factoryfs.rfs
<ID:0/011> NAND Write Start!!
<ID:0/011>
<ID:0/011> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
This is driving my crazy!!!
Any clues?
LeoMar75 said:
I'm also interested about what dev/block/xxx is for Kernel zImage.
Another question i tried to dump my system image by doing this procedure:
Code:
adb shell
rootsh
dd if=/dev/block/mmcblk0p9 of=/sdcard/factoryfs.rfs bs=4096
tar -H ustar -c factoryfs.rfs > package_name.tar
md5sum -t package_name.tar >> package_name.tar
mv package_name.tar package_name.tar.md5
However i can't flash it through Odin because i got error while flashing. The Md5 check is ok, but i don't know what i am missing!
Thanks in advance!
Click to expand...
Click to collapse
Galaxy s II uses .img not .rfs i think
coldflid said:
Galaxy s II uses .img not .rfs i think
Click to expand...
Click to collapse
Yep, but i even tried with .img and still it doesn't work
pulser_g2 said:
There is no recovery partition. It's in the kernel, which is /dev/block/mmcblk0p5
You can't get near it without root
Click to expand...
Click to collapse
I meant the kernel, it was a typo.
It doesn't matter which extension you give the output file, because dd transfers raw data. Heck, you could even make the output file an mp3
If you're working with Linux, you should run the command 'file' on whateveryounamedit.img : 'file system.img' It will say: 'raw data' or something like that. What you could do as well (Again, you must be running Linux), is mount the file.
Code:
sudo bash
mkdir /media/sgs2
mount -t ext4 system.img /media/sgs2
[code]
If it says it isn't a block device, try adding '-o loop' after '-t ext4'
Sent from my GT-I9100 using XDA App
You can't dump the kernel or any other partition from Android unless you have root access.
If you have access to two indian SGS2s (eg. another friend) with the same firmware, one of you could flash a rooted factoryfs.img and the other could flash an insecure zImage file. The 1st user dumps zImage, the 2nd user dumps /system.
sgstwo said:
You can't dump the kernel or any other partition from Android unless you have root access.
If you have access to two indian SGS2s (eg. another friend) with the same firmware, one of you could flash a rooted factoryfs.img and the other could flash an insecure zImage file. The 1st user dumps zImage, the 2nd user dumps /system.
Click to expand...
Click to collapse
I have a rooted indian sgs2..
PDA : I9100XWKE8
PHONE : I9100ODDKE2
CSC : I9100ODDKE2
i can help in dumping system folder..
I dont know how to..
can I copy the whole system folder frm rootexplorer and upload it?
I am not good with commands and stuff..
plz help..
sumeshd said:
I have a rooted indian sgs2..
PDA : I9100XWKE8
PHONE : I9100ODDKE2
CSC : I9100ODDKE2
i can help in dumping system folder..
I dont know how to..
can I copy the whole system folder frm rootexplorer and upload it?
I am not good with commands and stuff..
plz help..
Click to expand...
Click to collapse
How did you root it?
by cf-root 3.6..
so m now on ke7 kernel so need ke8 kernel..
can help you in pulling /system..only if I knew how
KE8 Kernel
Hi All Devs,
Can anybody Help porting KE8 Kernels (Secure & insecure) for rooting Indian Galaxy S 2.
suman_pal78 said:
Hi All Devs,
Can anybody Help porting KE8 Kernels (Secure & insecure) for rooting Indian Galaxy S 2.
Click to expand...
Click to collapse
Please read the thread. You need to get a dump of the kernel first
sgstwo said:
You can't dump the kernel or any other partition from Android unless you have root access.
If you have access to two indian SGS2s (eg. another friend) with the same firmware, one of you could flash a rooted factoryfs.img and the other could flash an insecure zImage file. The 1st user dumps zImage, the 2nd user dumps /system.
Click to expand...
Click to collapse
Thats seems to plausible idea. Well, I have access to more than 2 Indian SGS2 for that matter. Can you please upload rooted factoryfs.img?
sumeshd said:
I have a rooted indian sgs2..
PDA : I9100XWKE8
PHONE : I9100ODDKE2
CSC : I9100ODDKE2
i can help in dumping system folder..
I dont know how to..
can I copy the whole system folder frm rootexplorer and upload it?
I am not good with commands and stuff..
plz help..
Click to expand...
Click to collapse
And you can dump your system.img using this command in adb shell,
dd if=/dev/block/mmcblk0p9 of=/sdcard/system.img bs=4096
Ghostbustersin said:
Thats seems to plausible idea. Well, I have access to more than 2 Indian SGS2 for that matter. Can you please upload rooted factoryfs.img?
Click to expand...
Click to collapse
We would need a dump of the ROM first to do that...
pulser_g2 said:
We would need a dump of the ROM first to do that...
Click to expand...
Click to collapse
Would it matter if i upload the dump of rooted ROM with overwritten KE7 Kernel? We just need factoryfs.img, right? Or the overwritten kernel makes a difference there?
Ghostbustersin said:
Would it matter if i upload the dump of rooted ROM with overwritten KE7 Kernel? We just need factoryfs.img, right? Or the overwritten kernel makes a difference there?
Click to expand...
Click to collapse
I does make a difference since the xwke8 kernel would have been pretty interesting (better power management??). But having factoryfs.img isn't bad either. With the patched ke7 kernel you should be able to dump factoryfs - but you will not be able to get the ke8 kernel back. I guess gingerbreak does not work?
gladiac said:
I does make a difference since the xwke8 kernel would have been pretty interesting (better power management??). But having factoryfs.img isn't bad either. With the patched ke7 kernel you should be able to dump factoryfs - but you will not be able to get the ke8 kernel back. I guess gingerbreak does not work?
Click to expand...
Click to collapse
No Gingerbreak doesn't work. And, yes the KE8 kernel seems to have better Power management plus banding issue seems to be improved as well.( Although, i haven't used the KE7 Kernel but there is no Android System Resource power hogging in my SGS2 with KE8 kernel ). And People with Indian SGS2 who rooted using KE7 kernel is experiencing the android system ( or whatever it is! ) bug!
Well the whole idea is a bit complex, let me explain
- Dump Rom with overwritten KE7 kernel
- Extract Rooted factoryfs.img
- Flash factoryfs.img in another SGS2 with KE8 kernel
- Extract zImage
- Make a full rom dump from previous system.Img ( one we got from rooted KE7 Kernel Indian SGS2 ) and zImage from the other SGS2.
Hope this works out.
Ghostbustersin said:
Well the whole idea is a bit complex, let me explain
- Dump Rom with overwritten KE7 kernel
- Extract Rooted factoryfs.img
- Flash factoryfs.img in another SGS2 with KE8 kernel
- Extract zImage
- Make a full rom dump from previous system.Img ( one we got from rooted KE7 Kernel Indian SGS2 ) and zImage from the other SGS2.
Hope this works out.
Click to expand...
Click to collapse
Sounds good to me...
Hello,i accidently deleted all the files inside /efs while messing with root explorer.Now the /efs folder is empty.
but i had done backup (both clean and raw).(have both tar.gz and .img of mmcblk0p1)
So when i try to restore it :
1)Using Hellcat's kTool .It gives the msg "efs restored.you may want to reboot now."
but when i check in /efs folder it is still empty.And after reboot there is only 1 file named cryptprop_essiv (1 byte) in it.
using terminal emulator
a)i type
Code:
su
busybox tar zxvf /sdcard/efs/efs-backup.tar.gz -C /
it says
Code:
efs/
efs/cryptprop_rebootMode
tar:can't remove old file efs/cryptprop_rebootMode:
read-only file system
#tar:write: Broken pipe
then when i try the above after mounting /efs as r/w in root explorer,then this happens
Code:
efs/
efs/cryptprop_rebootMode
efs/cryptprop_onetimeboot
efs/cryptprop_securewipedata
efs/.files/
efs/.files/.dx1/
efs/.files/.dm33/
efs/.files/.mp301/
efs/nv_data.bin
efs/nv.log
efs/nv_data.bin.md5
efs/dmp/
efs/dmp/sett/
efs/dmp/sett/system/
efs/dmp/sett/system/volume_ring_last_audible
efs/dmp/sett/system/vibrate_on
efs/dmp/sett/system/time_12_24
efs/dmp/sett/system/screen_brightness_mode
efs/dmp/sett/system/volume_ring
efs/dmp/sett/system/volume_notification
efs/dmp/sett/system/volume_notification_last_audible
efs/dmp/sett/system/dtmf_tone
efs/dmp/sett/system/sound_effects_enabled
efs/dmp/sett/system/haptic_feedback_enabled
efs/dmp/sett/system/VIB_FEEDBACK_MAGNITUDE
efs/dmp/sett/system/screen_brightness
efs/dmp/sett/system/screen_off_timeout
efs/dmp/sett/system/mode_ringer
efs/dmp/sett/system/volume_system
efs/dmp/sett/system/volume_system_last_audible
efs/dmp/sett/system/vibrate_in_silent
efs/dmp/sett/system/airplane_mode_on
efs/dmp/sett/system/power_saving_mode
efs/dmp/sett/secure/
efs/dmp/sett/secure/mobile_data
efs/cryptprop_applied_result
efs/imei/
efs/imei/mps_code.dat
efs/imei/bt.txt
efs/imei/keystr
efs/calibration_data
efs/.nv_core.bak
efs/.nv_core.bak.md5
efs/.nv_data.bak
efs/.nv_data.bak.md5
efs/.nv_state
efs/redata.bin
efs/edk_p
efs/cryptprop_persist.sys.timezone
efs/cryptprop_lockscreen.patterneverchosen
efs/cryptprop_lockscreen.password_type
efs/cryptprop_lock_pattern_autolock
efs/cryptprop_lock_pattern_visible_pattern
efs/cryptprop_lock_pattern_tactile_feedback_enabled
efs/cryptprop_lockscreen.lockoutattemptdeadline
#
After this all files get back in /efs,but after i reboot.same problem occurs.no imei.Only 1 file present in folder
cryptprop_essiv
b)when i try to use this method
Code:
su
busybox umount /efs
dd if=/sdcard/efs.img of=/dev/block/mmcblk0p1 bs=4096
it says
Code:
umount:can't umount /efs:Invalid argument
and i just did a little experiment.i just copied a small random file in the efs folder.after i reboot it is gone and replaced by that cryptprop_essiv file.
even if i delete this file and reboot it comes back again.
Please any help would be appreciated.
i have the same problem too but i did't play with those folder it happened when my phone run out of battery and shut down it self when turn on no signal imei gone. inside efs folder only have cryptprop_essiv file
Seems like you have permission problems. I don't know if this will help any, but in CWM, goto Advanced, and Fix Permissions.
You could try using Heimdall to flash the efs.img using download mode.
You can get Heimdall at http://www.glassechidna.com.au/products/heimdall/
Using the command line should be as easy as when the phone is connected in download mode.
"heimdall flash --efs efs.img"
*If it is possible using Odin I don't know since I don't have Windows and have never used it.
** I have also never used the Heimdall GUI
i solved it... i extract the tar.gz file and rename the .nv_data.bak to nv_data.bin and copy to efs folder then reboot and wait for awhile all done in root explorer ...by the way i also got fix permission but i dont know whether got effect anot.
seemsoweird said:
i solved it... i extract the tar.gz file and rename the .nv_data.bak to nv_data.bin and copy to efs folder then reboot and wait for awhile all done in root explorer ...by the way i also got fix permission but i dont know whether got effect anot.
Click to expand...
Click to collapse
please can you explain more how can you copy file in efs folder? becuase its system file read only?
I kinda screwed my efs folder.
I have no IMEI and my Baseband is Unkown.
I tried re-flashing a modem, re-flashing to stock, but nothing seems to work.
So I tried restoring my backup of the efs folder.
I have a backup of my efs folder in 2 forms:
efs_28Oct2011-2110.tar.gz
and
efs.autobackup.img
But I can't get any of these to work. I search all forums, but it just fail everytime.
Anyone has any advice? I really don't know how to apply these backups.
Firstly, be very careful with what you're doing!
You can restore your EFS .img with helcat's kernel companion tool. Download from this post
http://forum.xda-developers.com/showthread.php?t=1182922
OR, in your EFS gz file, find and extract nv_data.bin and copy to your internal sdcard. Now in a terminal emulator or adb
cp /sdcard/nv_data.bin /efs/nv_data.bin
rm -rf /efs/nv_data.bin.md5
After restoring your IMEI using one of the methods above, your SIM might not work. If that should happen, remove the sim card, boot your phone and run this command
su
chown 1001:1001 /efs/nv_data.bin
Well the first way didn't work, actually it cleared the whole efs folder, I don't understand why.
Now i'm trying the second way, but it gives:
Can't create /efs/nv_data.bin : Read-only file system
Ok I managed to restore my complete efs folder, by using Root Explorer and the Tar.gz backup it all went fine, but I still don't have baseband: unkown and no IMEI, so I suppose it was al about the rom after all?
arcshooter said:
Ok I managed to restore my complete efs folder, by using Root Explorer and the Tar.gz backup it all went fine, but I still don't have baseband: unkown and no IMEI, so I suppose it was al about the rom after all?
Click to expand...
Click to collapse
>> First take backup using mybackup pro
>> Flash the ROM Using Odin method,once rebooted do factory reset
>>I believe u should get back
sendhiloo7 said:
>> First take backup using mybackup pro
>> Flash the ROM Using Odin method,once rebooted do factory reset
>>I believe u should get back
Click to expand...
Click to collapse
Well thx, I'm gonna try this, but I just realized that every time I reboot my device, my just restored efs with root explorer is empty again, think I have to fix this first?
This is exactly what happened too me:
http://forum.xda-developers.com/showthread.php?p=18026421
So when i try to restore it :
1)Using Hellcat's kTool .It gives the msg "efs restored.you may want to reboot now."
but when i check in /efs folder it is still empty.And after reboot there is only 1 file named cryptprop_essiv (1 byte) in it.
using terminal emulator
a)i type
Code:
su
busybox tar zxvf /sdcard/efs/efs-backup.tar.gz -C /
it says
Code:
efs/
efs/cryptprop_rebootMode
tar:can't remove old file efs/cryptprop_rebootMode:
read-only file system
#tar:write: Broken pipe
then when i try the above after mounting /efs as r/w in root explorer,then this happens
Code:
efs/
efs/cryptprop_rebootMode
efs/cryptprop_onetimeboot
efs/cryptprop_securewipedata
efs/.files/
efs/.files/.dx1/
efs/.files/.dm33/
efs/.files/.mp301/
efs/nv_data.bin
efs/nv.log
efs/nv_data.bin.md5
efs/dmp/
efs/dmp/sett/
efs/dmp/sett/system/
efs/dmp/sett/system/volume_ring_last_audible
efs/dmp/sett/system/vibrate_on
efs/dmp/sett/system/time_12_24
efs/dmp/sett/system/screen_brightness_mode
efs/dmp/sett/system/volume_ring
efs/dmp/sett/system/volume_notification
efs/dmp/sett/system/volume_notification_last_audible
efs/dmp/sett/system/dtmf_tone
efs/dmp/sett/system/sound_effects_enabled
efs/dmp/sett/system/haptic_feedback_enabled
efs/dmp/sett/system/VIB_FEEDBACK_MAGNITUDE
efs/dmp/sett/system/screen_brightness
efs/dmp/sett/system/screen_off_timeout
efs/dmp/sett/system/mode_ringer
efs/dmp/sett/system/volume_system
efs/dmp/sett/system/volume_system_last_audible
efs/dmp/sett/system/vibrate_in_silent
efs/dmp/sett/system/airplane_mode_on
efs/dmp/sett/system/power_saving_mode
efs/dmp/sett/secure/
efs/dmp/sett/secure/mobile_data
efs/cryptprop_applied_result
efs/imei/
efs/imei/mps_code.dat
efs/imei/bt.txt
efs/imei/keystr
efs/calibration_data
efs/.nv_core.bak
efs/.nv_core.bak.md5
efs/.nv_data.bak
efs/.nv_data.bak.md5
efs/.nv_state
efs/redata.bin
efs/edk_p
efs/cryptprop_persist.sys.timezone
efs/cryptprop_lockscreen.patterneverchosen
efs/cryptprop_lockscreen.password_type
efs/cryptprop_lock_pattern_autolock
efs/cryptprop_lock_pattern_visible_pattern
efs/cryptprop_lock_pattern_tactile_feedback_enabled
efs/cryptprop_lockscreen.lockoutattemptdeadline
#
After this all files get back in /efs,but after i reboot.same problem occurs.no imei.Only 1 file present in folder
cryptprop_essiv
b)when i try to use this method
Code:
su
busybox umount /efs
dd if=/sdcard/efs.img of=/dev/block/mmcblk0p1 bs=4096
it says
Code:
umount:can't umount /efs:Invalid argument
and i just did a little experiment.i just copied a small random file in the efs folder.after i reboot it is gone and replaced by that cryptprop_essiv file.
even if i delete this file and reboot it comes back again.
Click to expand...
Click to collapse
But I can't figure out how he fixed it, just doing whats said there isn't working.
To restore your EFS from your tar.gz file the commands are as following:
Code:
su
umount /efs
mke2fs /dev/block/mmcblk0p1
mount -w -t ext4 /dev/block/mmcblk0p1 /efs
busybox tar zxvf /sdcard/efs_28Oct2011-2110.tar.gz -C /
reboot
Not sure about how to restore your img file though but the tar.gz file should work.
Wow, out of the blue, after I tried every and really every way to restore it, your code just works! HERO! Thx
Now I'm sure my efs folder is fine and not corrupt, but still it gives
IMEI (nothing)
Baseband: Unknown
And it won't recognize my sim.
What is the problem here?
I installed the UCKK6 update for the purpose of pulling out the rom parts, by updating from rooted stock UCKH7. This successfully retained root on UCKK6.
From the mount command, I found that the system partition is listed as mmcblk0p9. I used dd to transfer the modem, kernel, and system partitions, and created Odin flashable tar files from each individually. I found that the kernel and the modem flash successfully, but that the system image flash fails almost immediately. Here is the code I used to pull the system partition in android terminal emulator:
Code:
# dd if=/dev/block/mmcblk0p9 of=/sdcard/factoryfs.img
I didn't remember to include bs=4096 in the command line, but then I didn't include it in the pull for the kernel (mmcblk0p5) and modem (mmcblk0p8) partitions either.
So, to those who know, how do I correctly pull the system partition, so that I can obtain a flashable image?
I'm also interested to know if pulling the image from a rooted phone will include root in the image, or how do you pull/create both a rooted and non-rooted system image?
This looks like a job for... GTG or ENTROPY!
creepyncrawly said:
I installed the UCKK6 update for the purpose of pulling out the rom parts, by updating from rooted stock UCKH7. This successfully retained root on UCKK6.
From the mount command, I found that the system partition is listed as mmcblk0p9. I used dd to transfer the modem, kernel, and system partitions, and created Odin flashable tar files from each individually. I found that the kernel and the modem flash successfully, but that the system image flash fails almost immediately. Here is the code I used to pull the system partition in android terminal emulator:
Code:
# dd if=/dev/block/mmcblk0p9 of=/sdcard/factoryfs.img
I didn't remember to include bs=4096 in the command line, but then I didn't include it in the pull for the kernel (mmcblk0p5) and modem (mmcblk0p8) partitions either.
So, to those who know, how do I correctly pull the system partition, so that I can obtain a flashable image?
I'm also interested to know if pulling the image from a rooted phone will include root in the image, or how do you pull/create both a rooted and non-rooted system image?
Click to expand...
Click to collapse
Always asking the hard questions...
In case this helps... Here's what I have for partition commands:
# dd if=/dev/block/mmcblk0p5 of=/sdcard/zImage bs=4096
# dd if=/dev/block/mmcblk0p8 of=/sdcard/modem.bin bs=4096
# dd if=/dev/block/mmcblk0p7 of=/sdcard/cache.img bs=4096
# dd if=/dev/block/mmcblk0p9 of=/sdcard/factoryfs.img bs=4096
# dd if=/dev/block/mmcblk0p10 of=/sdcard/data.img bs=4096
They have worked for me so far.... did you try including "bs=4096" for the factoryfs.img?
Regarding the root image... When pulling the a factoryfs.img, it pulls EVERYTHING in the system partition (folders). Files effecting root are contained within the system folders, so when you pull the factoryfs.img you get that too. The thing I don't know is if you can pull the img without having root. My phone is always rooted.
I keep a odin flashable image of my entire phone (all partitions listed above) as a fail proof backup in case I totality dork something up. The odin tar is about 2-3 gig. I can completely wipe my phone and return it to stock, then flash my odin to bring it back. I've used it (in testing) to COMPLETELY restore my phone and data... etc... etc. Pretty cool and comforting to know a can fix a bad screw up.
Peaster111 said:
Always asking the hard questions...
...did you try including "bs=4096" for the factoryfs.img?
Click to expand...
Click to collapse
No but I think I will go back and try again this afternoon to see if that was the problem.
By the way, there was a UCKK6 system partition dump with root prepared by vlara and posted in another thread. He named the file system.img instead of factoryfs.img. When I used it to make an Odin flashable tar, it failed immediately, just like the one I made.
# dd if=/dev/block/mmcblk0p5 of=/sdcard/zImage bs=4096
# dd if=/dev/block/mmcblk0p8 of=/sdcard/modem.bin bs=4096
# dd if=/dev/block/mmcblk0p7 of=/sdcard/cache.img bs=4096
# dd if=/dev/block/mmcblk0p9 of=/sdcard/factoryfs.img bs=4096
# dd if=/dev/block/mmcblk0p10 of=/sdcard/data.img bs=4096
Click to expand...
Click to collapse
BTW, you left out mmcblk0p1 = /efs and mmcblk0p4 = /mnt/.lfs. Wouldn't you need the efs for a complete backup? And isn't 0p4 the param.lfs?
Also just wondering. Entropy said that a backup of the efs partition should be done while booted into recovery so that it doesn't get hosed by a write during the backup. Would that be true for any of the other partitions? 1, 4, 7 and 10 are read/write. Not sure about 5 and 8.
creepyncrawly said:
By the way, there was a UCKK6 system partition dump with root prepared by vlara and posted in another thread. He named the file system.img instead of factoryfs.img. When I used it to make an Odin flashable tar, it failed immediately, just like the one I made.
BTW, you left out mmcblk0p1 = /efs and mmcblk0p4 = /mnt/.lfs. Wouldn't you need the efs for a complete backup? And isn't 0p4 the param.lfs?
Also just wondering. Entropy said that a backup of the efs partition should be done while booted into recovery so that it doesn't get hosed by a write during the backup. Would that be true for any of the other partitions? 1, 4, 7 and 10 are read/write. Not sure about 5 and 8.
Click to expand...
Click to collapse
Interesting on the system.img... Hard to stay what the story is there.
I did leave out the "efs" blocks... I forgot about that one. I dumped it once when I originally got the phone and just reuse the file. Interesting on the recovery part, I've not heard of that. I don't remember if mine was in recovery or not. It seems to work fine.
As long as you are in adb shell as su, whether the partition is r/w or r/o doesn't matter. You are just dumping (reading) it not writing.
The PARM partition is where SBL stores information. This is the settings for boot and contains the image you see on startup as well as the Download Mode image and others. Unless you need to mess with the bootloader related stuff, I wouldn't do the param.lfs. I'd rather reflash from a stock odin to fix any boatloader related issues. A clean PARM partition would ensure you avoid any bootloader anomalies.
I've attached the full mapping of the partitions along with some info on each.
OK.
Wiped data. Odin installed UCKH7 stock plus root. Updated to UCKK6 OTA.
Used adb to pull the system image, this time including the block size bs=4096.
Odin installed UCKH7 stock plus root again (so about phone would show UCKH7). Installed Mobile Odin. Flashed factoryfs.img. Flash failed. Phone still reports Gingerbread.UCKH7.
Mobile Odin rebooted into recovery and then the text goes by really fast, but it essentially printed quickly Clearing... Flashing... and then immediately rebooted. I think this is about the same experience that I had with the Odin flashable tar before. If the system partition was going to install, it would take at least a couple of minutes to write half a gig of info to the phone.
So, bad factoryfs.img? Is there any point in even making a tar and checking it out?
I'm at a loss. This should have worked shouldn't it?
Maybe Entropy will pitch in with some helpful advice.
creepyncrawly said:
So, bad factoryfs.img? Is there any point in even making a tar and checking it out?
I'm at a loss. This should have worked shouldn't it?
Maybe Entropy will pitch in with some helpful advice.
Click to expand...
Click to collapse
I've had mixed results using mobile odin. I had a soft brick once trying to flash a kernel. I would try making an actual odin tar image and try flashing that way. That's the way I do it.
There is a good thread in the international SGS2 forums on creating an odin tar. You'll need Cygwin on your computer (assuming you're on windows).
Here's the short "How to" version:
To create a flashable Odin package, you need to pull all of the files off of the phone/sdcard and onto your computer.
Open a Cygwin and change directory to where you are storing your ROM dumps.
Run the following commands to build a package. Be sure to use identifiable names with versions or dates:
$ tar -H ustar -c factoryfs.img modem.bin zImage > package_name.tar
$ md5sum -t package_name.tar >> package_name.tar
$ mv package_name.tar package_name.tar.md5
Include what images you want after the "-c" and before the ">".
A second opinion is always good!
Why not nand and just pull factoryfs.img that way
Indeed.. You could. That would work too.
UPDATE: I just pulled mine. I reflashed to my old UCKH7 build (wiped and flashed just the basics) and back to my new UCKK6 build plus all my data, etc. It all seemed to work.
jivy26 said:
Why not nand and just pull factoryfs.img that way
Click to expand...
Click to collapse
I've never lived in linux land, so I don't have the background to quickly grasp this. I know nand is our phone's memory, but what does your statement mean? I'd appreciate it if you could explain a little. I'd be happy with something to study, but I don't even know what to look for.
creepyncrawly said:
I've never lived in linux land, so I don't have the background to quickly grasp this. I know nand is our phone's memory, but what does your statement mean? I'd appreciate it if you could explain a little. I'd be happy with something to study, but I don't even know what to look for.
Click to expand...
Click to collapse
On the rooted system I assume you have CWM as well. If that is the case go into CWM backup your phone then boot up the phone. Mount SDCARD and navigate to Clockworkmod > backup > then whatever date and time you backed up and you will see factoryfs.img in there as well as other img files.
jivy26 said:
On the rooted system I assume you have CWM as well. If that is the case go into CWM backup your phone then boot up the phone. Mount SDCARD and navigate to Clockworkmod > backup > then whatever date and time you backed up and you will see factoryfs.img in there as well as other img files.
Click to expand...
Click to collapse
Jivy,
I'm not sure on yours, but my folders only have 3 tar files (cache.ext4.tar, data.ext4.tar, system.ext4.tar) and a 2 img's (boot and recovery). They are each only 8mb. The tar files have all the data. They reflash fine in CWM, but they are not odiin compatible.
Also for the non-rooted system try this, assuming you have Android-sdk installed.
Plug phone into PC with usb debugging enabled.
Download busybox here
Put it on c:\
Run CMD with Admin privileges.
Below are the commands you will type in CMD. For below I am assuming your SDK is in the same location as default, if not just change as neccessary.
cd\
cd program files
cd android-sdk
cd platform-tools
adb devices (to make sure your phone shows up)
adb push busybox /data/local/busybox
adb shell
cd /sdcard
chmod 755 /data/local/busybox
/data/local/busybox tar cvf stock_unrooted.tar /system
Click to expand...
Click to collapse
Once its done you can mount sdcard and the tar with system will be there waiting
jivy26 said:
On the rooted system I assume you have CWM as well. If that is the case go into CWM backup your phone then boot up the phone. Mount SDCARD and navigate to Clockworkmod > backup > then whatever date and time you backed up and you will see factoryfs.img in there as well as other img files.
Click to expand...
Click to collapse
Oh. nand for nandroid backup. It does not contain factoryfs.img. It has system.ext4.tar which contains the directory sturcture and contents of system in the file system, not a partition image.
creepyncrawly said:
Oh. nand for nandroid backup. It does not contain factoryfs.img. It has system.ext4.tar which contains the directory sturcture and contents of system in the file system, not a partition image.
Click to expand...
Click to collapse
Misunderstood what your goal was. Like earlier mentioned you need to have:
Code:
dd if=/dev/block/mmcblk0p9 of=/sdcard/factoryfs.img bs=4096
That wont flash in odin you still need to make it 512M so quick run down in linux
Download this http://dl.dropbox.com/u/53644280/ext4_utils.zip
So you can view contents of .img
Code:
mkdir tempdir; mount -o loop factoryfs.img tempdir
To repack img w/ 512M
Code:
./mkuserimg.sh -s /some/directory/ ./factoryfs_custom.img ext4 ./temp 512M
Then making a TAR ball. *Just included everything i've normally seen in one*
Code:
tar -c boot.bin factoryfs.img hidden.img modem.bin param.lfs zImage >> PDA.tar
jivy26 said:
Also for the non-rooted system try this, assuming you have Android-sdk installed.
Plug phone into PC with usb debugging enabled.
Download busybox here
Put it on c:\
Run CMD with Admin privileges.
Below are the commands you will type in CMD. For below I am assuming your SDK is in the same location as default, if not just change as neccessary.
Once its done you can mount sdcard and the tar with system will be there waiting
Click to expand...
Click to collapse
Kewl. That non-rooted dump will include the busybox directory though won't it? On a rooted system, it would capture the root tools too I expect.
Only, when developers provide a package like Entropy's Return/Unbrick to stock packages, or DesignGears original One-Click downloader for Captivate, those packages contain partition images, not file system images. I would really like to learn how to dump the system partition so that it can be used to create Odin flashable tar files.
Thanks for your input.
creepyncrawly said:
Kewl. That non-rooted dump will include the busybox directory though won't it? On a rooted system, it would capture the root tools too I expect.
Only, when developers provide a package like Entropy's Return/Unbrick to stock packages, or DesignGears original One-Click downloader for Captivate, those packages contain partition images, not file system images. I would really like to learn how to dump the system partition so that it can be used to create Odin flashable tar files.
Thanks for your input.
Click to expand...
Click to collapse
I posted that before I knew what your intentions were. The above would give you a stock /system in .tar . Since busybox is stored in data/local not system/xbin, it wont be in that tar. So you'd have a stock /system, but not the .img you're looking for.
jivy26 said:
Misunderstood what your goal was. Like earlier mentioned you need to have:
Code:
dd if=/dev/block/mmcblk0p9 of=/sdcard/factoryfs.img bs=4096
That wont flash in odin you still need to make it 512M so quick run down in linux
Download this http://dl.dropbox.com/u/53644280/ext4_utils.zip
So you can view contents of .img
Code:
mkdir tempdir; mount -o loop factoryfs.img tempdir
To repack img w/ 512M
Code:
./mkuserimg.sh -s /some/directory/ ./factoryfs_custom.img ext4 ./temp 512M
Then making a TAR ball. *Just included everything i've normally seen in one*
Code:
tar -c boot.bin factoryfs.img hidden.img modem.bin param.lfs zImage >> PDA.tar
Click to expand...
Click to collapse
When I pulled the system image using the above dd command including the bs=4096, the resulting file did come out 512M. It still didn't flash.
So do I need a linux box to do this? Don't have one of course. I've been making the tar files on my phone in Terminal. Can I do the above commands on the phone?
creepyncrawly said:
When I pulled the system image using the above dd command including the bs=4096, the resulting file did come out 512M. It still didn't flash.
So do I need a linux box to do this? Don't have one of course. I've been making the tar files on my phone in Terminal. Can I do the above commands on the phone?
Click to expand...
Click to collapse
Never tried from phone. Cygwin is an option to run linux scripts and what not in windows, but not sure if it can handle the above mentioned.
jivy26 said:
Never tried from phone. Cygwin is an option to run linux scripts and what not in windows, but not sure if it can handle the above mentioned.
Click to expand...
Click to collapse
OK. I'll play around with it and see what happens. Really appreciate the help.
Hi everyone,
I made this guide for users of a Galaxy Player 4.0 USA or INTL who want to get backups of every partition in case they completely brick their device. This will be very useful if you have somehow screwed up your partitions beyond just /system, which is what most ROMs only include. It even backs up /efs, which contains the serial numbers unique to every player and other things that even complete restore ROMs and nandroid backups don't include. It's also good to just have a backup of your partitions stored somewhere safe, because you never know when you might need them. Also, if you're reverting from CM7 (the second release or later) you will need to use this with a PIT file because CM7 uses MTD partitions. Basically, flashing this backup will allow you to completely return to how your device was before, including all your personal data and apps. Hopefully soon we'll begin to have less "bricked my player help" threads clogging up the General (and sometimes Dev) sections. Enjoy
This backup does not back up bootloaders, which can increase your chances of a hard-brick and are almost never needed. Also, this is for the YP-G1 / Player 4.0 USA or INTL only, not for 5.0 users.
Disclaimer: I am not responsible for your device if anything happens blah blah blah
*Pre-requisites*
- Rooted device or ROM
- Busybox (Most rooted ROMs have this, but you can still download Busybox Installer from the Play Store and update to the latest busybox version just to make sure)
- ADB properly set up
- Some space on your internal SD card (about 1-2 GBs should be fine)
- Player set to "USB Debugging Mode" found in Settings
Alright, let's begin. First we will need to make a dump of every partition on the device. However, dumping the PIT is not needed because Adamoutler has a thread with a master list of PITs. Open a Command Prompt (or Terminal if you're using Linux), make sure your device is connected and type:
Code:
adb remount
adb shell
su
Now, to back up EFS:
Code:
dd if=/dev/block/stl3 of=/sdcard/efs.rfs bs=4096
PARAM
Code:
dd if=/dev/block/stl6 of=/sdcard/param.lfs bs=4096
KERNEL
Code:
dd if=/dev/block/bml7 of=/sdcard/zImage bs=4096
SYSTEM
Code:
dd if=/dev/block/stl9 of=/sdcard/factoryfs.rfs bs=4096
DBDATA
Code:
dd if=/dev/block/stl10 of=/sdcard/dbdata.rfs bs=4096
CACHE
Code:
dd if=/dev/block/stl11 of=/sdcard/cache.rfs bs=4096
DATA (Optional if you want your apps)
Code:
tar -czvf /sdcard/data.tar.gz /data
You can exit out of the current window and open a new one once all the processes above are completed.
Now to pull all of the backups to your computer:
Code:
adb remount
adb pull /sdcard/efs.rfs
adb pull /sdcard/param.lfs
adb pull /sdcard/zImage
adb pull /sdcard/factoryfs.rfs
adb pull /sdcard/dbdata.rfs
adb pull /sdcard/cache.rfs
adb pull /sdcard/data.tar.gz
I recommend keeping these files in a safe place on your hard drive for when you need to use them. Feel free to delete them from your player now to save space.
How to Flash
First grab the correct PIT for your device here
For Heimdall, just load the PIT, click "Re-Partition", and select the correct files for each partition. Then click flash.
For ODIN, you have to tar the files together first.
Using Cygwin or Terminal, browse to the directory where all your backup files are. Then, type in:
Code:
tar -H ustar -c efs.rfs param.lfs zImage factoryfs.rfs dbdata.rfs cache.rfs > backup_package.tar
Now load the PIT, click "Re-Partition", and under the PDA section browse to your backup_package.tar (or whatever you named it to). Click flash.
After it is done flashing, here's how to restore your apps. Open Terminal or Command Prompt to the directory of data.tar.gz on your computer:
Code:
adb remount
adb push data.tar.gz /sdcard/
adb shell su -c "tar -zxvf /sdcard/data.tar.gz"
And you're done! If all goes well you should have completely restored your device, with a perfectly safe method and no bootloaders! I hope that this will be helpful to people.
Reserved for future use....
I did this, and i believe that AdamOutlers .pit is what messed up my device. Can you please give me a copy of your or another copy?
Tcollins412 said:
I did this, and i believe that AdamOutlers .pit is what messed up my device. Can you please give me a copy of your or another copy?
Click to expand...
Click to collapse
AdamOutler's pit is not messed up... I used it to repartition my player and it worked perfectly with the right partitions.
Sent using Tapatalk
when i tried it, it messed up my player. do you know how i could fix it?
Hey klin1344, not sure if you still watch this thread, but I was wondering if anyone has had success using heimdall 1.3.2 with the 4.0? I see it says it broke compatibility with some devices.
iJimaniac said:
Hey klin1344, not sure if you still watch this thread, but I was wondering if anyone has had success using heimdall 1.3.2 with the 4.0? I see it says it broke compatibility with some devices.
Click to expand...
Click to collapse
No problem for me
i wanted to use this method to backup my /efs (like daniel advicd me to do ) but i cant seem to do it. It says Can't open 'sdcard/efs.rfs': Read only file system
pls answer
crancpiti said:
i wanted to use this method to backup my /efs (like daniel advicd me to do ) but i cant seem to do it. It says Can't open 'sdcard/efs.rfs': Read only file system
pls answer
Click to expand...
Click to collapse
You have to be rooted to do this.
Sent from my A500 using xda app-developers app
klin1344 said:
You have to be rooted to do this.
Sent from my A500 using xda app-developers app
Click to expand...
Click to collapse
i think either i hadnt BuSY box installed(my device was rooted before) or it was bcause i connected my device to the PC / i mounted my sdcards
now i have a efs.rfs file and that should do it i hope
thanks . i have problem with heimdall to download my wifi 4 int PIt file
is there any ADB command for downloading pit file from device?
aminking2005 said:
thanks . i have problem with heimdall to download my wifi 4 int PIt file
is there any ADB command for downloading pit file from device?
Click to expand...
Click to collapse
I do remember that there is the dd command from the adb shell in order to get your pit, but it's not the recommended way to get it.
You can download the pit files right here:
http://forum.xda-developers.com/showthread.php?t=1531850
zaclimon said:
I do remember that there is the dd command from the adb shell in order to get your pit, but it's not the recommended way to get it.
You can download the pit files right here:
http://forum.xda-developers.com/showthread.php?t=1531850
Click to expand...
Click to collapse
most pit file are represented for wifi4 8GB . but mine is 16GB.
so im not sure about pit files in forum.
if i install a custom rom and it faild can i recover my yp-g1 by having above backups?
aminking2005 said:
most pit file are represented for wifi4 8GB . but mine is 16GB.
so im not sure about pit files in forum.
if i install a custom rom and it faild can i recover my yp-g1 by having above backups?
Click to expand...
Click to collapse
Sorry for the long reply time, and yeah you should be able to restore with those backups.
Envoyé de mon Nexus 4 en utilisant Tapatalk