Related
So far I have tested redbend_ua for backup purposes, and got the bml7 and bml8 partitions backed up, and tested just restoring the bml8 partition with the clockwork recovery that is being tested on the epic. The utility did write the image / partition correctly (afaik) and rebooted the phone upon completion. The phone booted correctly to android, but then upon another reboot to test recovery, it just boot loops, even a normal boot and trying to get to the downloader mode.
This utility seems to work and do what it was meant to, but i would not use this tool without knowledge of what you are doing. On that note, i will not post a link to the tool, just as a safeguard, for now at least.
it is known to work on bml7 (the kernel partition).
for the last few fays ive been trying to gather information regarding flashing an entire rom (all the partitions resides in an odin update file) using redbend_ua only, but i couldn't get a clear understanding of what todo with the two cache.rfs & dbdata.rfs files (each located on both the PDA and the CSC files). also, repartitioning the disk is also needed when flashing a new rom, so i need to recognize the new partition table layout (which i assume resides in the .pit file).
as for now, its only a lot of assumptions for me. they only confirmation i could get was from here: hxxp://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S
z4ziggy said:
it is known to work on bml7 (the kernel partition).
for the last few fays ive been trying to gather information regarding flashing an entire rom (all the partitions resides in an odin update file) using redbend_ua only, but i couldn't get a clear understanding of what todo with the two cache.rfs & dbdata.rfs files (each located on both the PDA and the CSC files). also, repartitioning the disk is also needed when flashing a new rom, so i need to recognize the new partition table layout (which i assume resides in the .pit file).
as for now, its only a lot of assumptions for me. they only confirmation i could get was from here: hxxp://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S
Click to expand...
Click to collapse
Both cache and dbdata can largely be ignored; I actually had to nuke my /dbdata partition earlier due to something I did. It gets rebuilt on boot, it's just a SQLite store for the applications and on most Android phones resides within /data. No idea why Samsung felt it necessary to separate this partition.
if this is so, and both cache.rfs & dbdata.rfs can be ignored, then updating an entire rom using redbend_ua from within update.zip is possible (right now the project-voodoo is using the redbend_ua method to flash kernel only from within update.zip file, but the idea is the same).
i think we need to get some more confirmation before actually testing this because failure on flashing the rom will break the phone... and no one wants to have that
z4ziggy said:
if this is so, and both cache.rfs & dbdata.rfs can be ignored, then updating an entire rom using redbend_ua from within update.zip is possible (right now the project-voodoo is using the redbend_ua method to flash kernel only from within update.zip file, but the idea is the same).
i think we need to get some more confirmation before actually testing this because failure on flashing the rom will break the phone... and no one wants to have that
Click to expand...
Click to collapse
I did some more testing and can confirm that cache and dbdata can both be empty on boot.
this is excellent news!
i will work later today on a template for update.zip using redbend_ua and post here for reference.
also, a thought came to mind - what is the difference between redbend_ua and dd? if all redbend_ua does is dumping data from/to a partition, then it is simply a dd replacement. isn't it?
z4ziggy said:
this is excellent news!
i will work later today on a template for update.zip using redbend_ua and post here for reference.
also, a thought came to mind - what is the difference between redbend_ua and dd? if all redbend_ua does is dumping data from/to a partition, then it is simply a dd replacement. isn't it?
Click to expand...
Click to collapse
If you currently have redbend_ua on your device, could i get you to dump /dev/block/BML7 to /sdcard/recovery.bin and upload it / link it? i need it
fallingup said:
If you currently have redbend_ua on your device, could i get you to dump /dev/block/BML7 to /sdcard/recovery.bin and upload it / link it? i need it
Click to expand...
Click to collapse
Yeah.. I could've used that yesterday too.. I ended up swapping out my device this morning.
Sounds like some progress is being made. Very good to hear confirmation on cache and dbdata
i actually got it working now, after my brick anyways. Now i need to find the verizon dump not a USC dump
fallingup said:
i actually got it working now, after my brick anyways. Now i need to find the verizon dump not a USC dump
Click to expand...
Click to collapse
Glad to hear it.. I was getting seg-faults trying to mount /system .
Hi!
I know that I'm asking about forbidden subjects but I have no intention of doing something stupid just want to understand some things about S2.
That's what I think I understand:
- PIT is a file that contains partition layout on our device, that partitions are later flashed with files from rom package (files are partition images in fact)
- Normally we do not need to re-partition because there is only one partition description available on S2 - so all ROM share it (also it's not recommented coz if sth goes wrong we have big problem - device without partitions)
- EFS is one of the partitions and it shouldn't be touched (contains IMEI etc)
Here is my question:
Some people flash ROM with PIT and repartition and still have working device - how is it possible ?? - re-partition should wipe everything including EFS.
EDIT:
One more thing - when exploring XXKP8 rom package from sammobile.com noticed that there is PIT file and some file named
I9100_EFS_I9100XXKP8_CL42141_REV02_user_low_ship.tar.md5
that contains efs.img file I wonder what is this file for. Some generic EFS image ??
Regards
Slig
The pit is used for partition mapping, basically telling the program which block device is which partition. You dont need to use the pit as Odin can pull it from the phone, this also prevents people from using i9000 pits (sgs1, and yes this has happened)
Efs has both generic files and device specific files, I think.
Sent from my GT-I9100 using Tapatalk
Thanks for response !
veyka said:
this also prevents people from using i9000 pits (sgs1, and yes this has happened)
Click to expand...
Click to collapse
Yeah I read about that epic failure. That is why I'm asking - want to know everything before doing anything.
Regards
Slig
slig said:
Hi!
Here is my question:
Some people flash ROM with PIT and repartition and still have working device - how is it possible ?? - re-partition should wipe everything including EFS.
The recommendation is not to flash PIT file or repartition unless you know what you are doing .
PIT does not wipe EFS .
Their is a PIT file description post on the forum .
jje
jje
Click to expand...
Click to collapse
Hi ! Thank You for Your response.
JJEgan said:
The recommendation is not to flash PIT file or repartition unless you know what you are doing .
Click to expand...
Click to collapse
Yes, I'm fully aware of that. I'm just the kind of person that like to know why so I decided to investigate this subject deeper. Another thing is that I'll probably try to use heimdall and that program requires better understanding than "use PDA field in Odin".
You can just flash a .pit file and check repartition. You just have to make sure your flash won't fail. If you have faulty drivers or a damaged usb cable, then it will brick your phone.
If you want to try it, make a flash without .pit and repartition and if it works you can use them. Its just something unexperienced users should not use.
Unless something changes, we don't need to repartition, (one case might be if android plus tw is bigger than 500 ish megs Samsung would need to make the system partition bigger) so we just don't need to use it, and making the risks sound worse it keeps newbies away.
Sent from my GT-I9100 using Tapatalk
I've found Odia's thread GT-9100 PIT v Flash analysis
http://forum.xda-developers.com/showthread.php?t=1104139
Very interesting informations that answers many of my questions.
I'm just writting this because i've recently had this problem. I managed to sort it out by my own but didn't really find it written anywhere, just bits and pieces scavenged from so many pages that might point to a solution (granted, part of my problem was also finding what was really my problem since the phone stopped working so fast i didn't really had the time to get what happened)
I was trying out swap for my S3, i had created a swap partition in my external card and then followed a guide here from xda to use an app called swapper2 (from market) to enable swap. I must have done something wrong because what it did was format my /efs partition instead as if it was a swap partition. Phone stopped working on the spot, obviously, and wouldn't past samsung's bootscreen.
Also, keep in mind while this worked for me there might be other ways of doing this which may be simpler. This is just what i figured for a solution.
When this helps:
- you accidentally formated your /efs partition
- you have a backup from your /efs partition, files copied with root explorer but not an image you can just flash back to the partition.
- your phone boots to download and to recovery but not to main system (which every tutorial i found seemed to assume to be able to do, i just figured their /efs was not as screwed as mine was)
- your recovery won't mount the /efs partition because it expects it to be ext4 but it's formated to something else and it showing the message:
"e: failed to mount /efs (Invalid argument)"
What doesn't work:
- any kind of standard solution like reflashing a stock rom with odin, with or without .pit file, clear EFS, whatever. It will flash, just won't solve since, apparently, nothing touches the /efs partition because it's so sensible. Even custom recoveries do mount it and apparently format and replace every single other partition but the /efs, which is why i had to do it manually.
Solution:
- simply format the /efs partition back to ext4 and copy your backup files there
What's needed:
- phone drivers installed on the computer. If you had kies installed, this should be covered already. Think you can't have it running while doing this though. Also, for what's worth, i've done this with windows 8 x64.
- updated android sdk tool, mainly adb. If adb is saying device not connected or not found, you may be using an outdated adb.exe (i was). I used adb.exe that came with this software here:
http://forum.xda-developers.com/showthread.php?t=1308546
- root. If your rom isn't rooted you can always flash CF-root from odin in download mode.
http://forum.xda-developers.com/showthread.php?t=1695238
- busybox, am not really sure if i actually got to need this, think so for the formating tool. Can't hurt to have more options though. This is how to install:
http://www.omappedia.com/wiki/Android_Installing_Busybox_Command_Line_Tools
- custom recovery that allows root through adb, i used Philz which is pretty awesome
http://forum.xda-developers.com/showthread.php?t=2002953
- backup files from your /efs. I had mine unzipped and copied to my externalsd while in windows. They were in an efs folder in the sd card. You can push this through adb to the phone later, but i found this way simpler.
How to:
- get into recovery (vol up+home+power button) and plug your phone to the computer. You'll hear an usb connected sound from windows after a bit.
- in recovery, navigate to Mounts and try the "mount /efs". It'll fail. Now, navigate to advanced and "view log". You'll see below that the phone tried to mount a partition and failed, in my case, it had unsucessfully tried to mount /dev/block/mmcblk0p3 which is the partition /efs uses. Take note of this partition name.
- On windows, open a command line (type cmd on you start menu), navigate to where you have adb.exe and type:
adb shell
If all went well, command prompt has changed. You can now issue commands directly to your phone from terminal.
- type "su" to get root permissions. Your command line should change to something like [email protected] Before i had this working i needed to use "Fix permissions". It's an option in the recovery menus on the phone.
- this step is optional but i did it anyway. I created an image of the partition i was going to mess with. If anything went wrong i could always flash it back even if it was broken. By the way, this is what i should have done in the first place instead of just copying /efs files. Would have made the process so much simpler... also, do this if you ever get the phone back working again. Type:
dd if=/dev/block/mmcblk0p3 of=/externalsd/efs.img
The /externalsd/efs.img is just a place you can save stuff to, like your external sd card. You can check what's your mounting point for the card with the command "mount" and look for something relevant like "externalsd".
Also, you may want to copy that efs.img to somewhere else from your phone (like your computer) for safekeeping. Literally remove card from phone, put in computer and copy files there. Notice you may need to reboot phone to recovery if you remove your card so it detects and mounts your card again. Sure, you can also do that from the command line, but it's just easier to reboot the phone.
- Now, we'll format the partition to something your phone can mount (ext4) and is expecting. Be careful, by doing this, you're actually erasing what's left of your partition and replacing by something clean. Type:
mk2fs /dev/block/mmcblk0p3
If all went well, you should see some kind of small report about what was just done.
- To mount this we'll need a mounting point. Type:
mkdir /efs
this will create an /efs folder in root, if it doesn't exist already, and to mount, type:
mount -t ext4 /dev/block/mmcblk0p3 /efs
- if all went well, you now have access to the /efs folder and can copy you files back:
cp -r /externalsd/efs/* /efs
where externalsd was my external sd card mounted on my phone.
- Check if your /efs folder has it's contents properly
ls /efs
I had to reboot the phone to recovery once more at this point and use the "fix permissions" option again.
After this, my phone booted up normally again.
I'm getting Segmentation fault, I guess there's some kinda hardware error on my phone. Gonna take it to Sammy's tomorrow.
Code:
mke2fs -F /dev/block/mmcblk0p11
Segmentation fault
sh-4.2#
Hi thnx for your Guide. I have the EFS problem, after installin 4 diferent rom in 2 hours my imei and baseband lost.( dont now why) i dont have a backup. I was thinking if it take the EFS from another S3 does it work?
Will this work with a Galaxy S4? I545
Enea307 said:
Hi thnx for your Guide. I have the EFS problem, after installin 4 diferent rom in 2 hours my imei and baseband lost.( dont now why) i dont have a backup. I was thinking if it take the EFS from another S3 does it work?
Click to expand...
Click to collapse
No. Read General > Sticky roll-up thread > "IMEI / EFS - Know this stuff"
is normal this output? (i'm meaning the tar.gz unfinding file)
Code:
*****************************************
* BACKUP EFS *
*****************************************
WARNING: Do you wish to Continue? (This will make EFS BACKUP) [Y,N]?Y
--- STARTING ----
--- WAITING FOR DEVICE
--- Backup efs image ---
761 KB/s (9357 bytes in 0.012s)
7 KB/s (39 bytes in 0.005s)
SM-N9000ZWEXXV_N900XXUCMJ3_RF1DA111EAY_
Creating filesystem with parameters:
Size: 20971520
Block size: 4096
Blocks per group: 32768
Inodes per group: 1280
Inode size: 256
Journal blocks: 1024
Label:
FLEX_BG size: 0
Blocks: 5120
Block groups: 1
Reserved block group size: 0
Created filesystem with 59/1280 inodes and 2432/5120 blocks
40960+0 records in
40960+0 records out
20971520 bytes transferred in 7.271 secs (2884269 bytes/sec)
unknown option -- ZBusyBox v1.19.4-cm9 bionic (2012-02-05 18:40 +0100) multi-cal
l binary.
Usage: tar -[cxtzjahmvO] [-X FILE] [-T FILE] [-f TARFILE] [-C DIR] [FILE]...
Create, extract, or list files from a tar file
Operation:
c Create
x Extract
t List
f Name of TARFILE ('-' for stdin/out)
C Change to DIR before operation
v Verbose
z (De)compress using gzip
j (De)compress using bzip2
a (De)compress using lzma
O Extract to stdout
h Follow symlinks
m Don't restore mtime
exclude File to exclude
X File with names to exclude
T File with names to include
2684 KB/s (9962352 bytes in 3.623s)
2805 KB/s (20971520 bytes in 7.299s)
remote object '/sdcard/SM-N9000ZWEXXV_N900XXUCMJ3_RF1DA111EAY_EFS.tar.gz' does n
ot exist
7-Zip (A) 4.65 Copyright (c) 1999-2009 Igor Pavlov 2009-02-03
Scanning
SM-N9000ZWEXXV_N900XXUCMJ3_RF1DA111EAY_EFS.tar.gz: WARNING: Impossibile trovare
il file specificato. [COLOR=Red](impossible to find the specify file)[/COLOR]
Creating archive SM-N9000ZWEXXV_N900XXUCMJ3_RF1DA111EAY_EFS.zip
Compressing getprop.txt
Compressing SM-N9000ZWEXXV_N900XXUCMJ3_RF1DA111EAY_EFS.raw.img
Compressing SM-N9000ZWEXXV_N900XXUCMJ3_RF1DA111EAY_EFS.tar.md5
WARNINGS for files:
SM-N9000ZWEXXV_N900XXUCMJ3_RF1DA111EAY_EFS.tar.gz : Impossibile trovare il file
specificato.[COLOR=Red] (impossible to find the specify file)[/COLOR]
----------------
WARNING: Cannot find 1 file
-
-
Finished. Output file is SM-N9000ZWEXXV_N900XXUCMJ3_RF1DA111EAY_EFS BACKUP
Premere un tasto per continuare . . .
well in the zip there are only the txt + md5 + .raw.img
Thanks for this great tutorial. It was my final step to recover my efs partition, without any backup. I copied the efs folder from another device and modified the files according my devices info (bluetooth mac, serial etc). Worked great on my SGS4
By the way I had the same error:
Code:
mke2fs /dev/block/mmcblk0p10
Segmentation fault
You get this error if you run adb shell when you booted to your ROM.
You need to run adb shell in recovery mode
Great tutorial but i hope you can help me, I can't seem to properly find the SDcard. When I type cp -r /externalsd/efs/* /efs
it comes back with cp: can't stat '/sdcard/efs*' : No such file or directory
I cleared my whole sdcard card except for efs directory. I also tried sdcard instead of externalsd but same thing.
I am getting stuck trying to fix this as I have a boot loop or corrupt /efs or something. I have tried to get my phone working by installing my ROM ( Omega v58 ) and also by trying to flash the latest stock 4.3 through Odin v3.09. I havent tried total stock 4.0.3 yet. No matter what I have done though I can't get past the boot logo ( or the walking Omega droid ). My phone just sits there and hangs
I have followed your steps and I have Philz ( 6.07.9.19 ) installed ( but not busybox unless it is sat there somehow from the Omega install ) but when i try to get adb shell running nothing happens or works..as you can see
What am i doing wrong? OR is my phone totally borked?
hi..
Blackwatch said:
I am getting stuck trying to fix this as I have a boot loop or corrupt /efs or something. I have tried to get my phone working by installing my ROM ( Omega v58 ) and also by trying to flash the latest stock 4.3 through Odin v3.09. I havent tried total stock 4.0.3 yet. No matter what I have done though I can't get past the boot logo ( or the walking Omega droid ). My phone just sits there and hangs
I have followed your steps and I have Philz ( 6.07.9.19 ) installed ( but not busybox unless it is sat there somehow from the Omega install ) but when i try to get adb shell running nothing happens or works..as you can see
What am i doing wrong? OR is my phone totally borked?
Click to expand...
Click to collapse
I have successfully fix my efs partition follwing this thread.
you are receiving such message in cmd. I faced it too.
Sol: Use Philoz Recovery 5.0.
Fix permissions.
there you are.. done..
Philz 6.0 do not have an option for "fix permission".
hope it helps..
I wrote a script that attempts to recover your nv_data.bin from a corrupted EFS partition for the i9300. Thus if you don't have a backup and your EFS is corrupt, try the script. The script is still in Alpha phase and may not work for other devices. Feedback would be much appreciated.
You can find the script at: https://github.com/chriscz/efs_recover
I dont have /efs backed up
Hi ,
If i dont have /efs backed up , can I copy any other mobile (same model) efs data to my mobile and try?
Thanks and Regards
Vamshi Pulumati
vamshipulumati said:
Hi ,
If i dont have /efs backed up , can I copy any other mobile (same model) efs data to my mobile and try?
Thanks and Regards
Vamshi Pulumati
Click to expand...
Click to collapse
No, it won't work and trying to clone another imei is illegal.
boomboomer said:
No, it won't work and trying to clone another imei is illegal.
Click to expand...
Click to collapse
How to register for a new IMEI ? Is it possible?? Could you please help me with any site or link?? I don't want to replace motherboard..
Any help are highly appreciated.
No, it isn't possible and discussion about changing imei is banned on xda.
Take your phone to a service centre and pay then to recode it for you, make sure it works on 4.3 before you pay.
boomboomer said:
No, it isn't possible and discussion about changing imei is banned on xda.
Take your phone to a service centre and pay then to recode it for you, make sure it works on 4.3 before you pay.
Click to expand...
Click to collapse
Hey I would like to tell you that a miracle happened for my S3. Yesterday i tried to do same as per in this guide. After taking backup of broken efs backup i tried to clear the efs folder with this command "mk2fs /dev/block/mmcblk0p3"
After that i just flashed 4.4.4 based stock ROM and somehow phone booted up perfectly. No network issues. Bluetooth wifi sim card everything works. IMEI & Serial No is there. But when i'm checking network unlock status it is showing as everything locked. But still I can use everything... I'm amazed.!!!!
Do you have any idea how this happened??
@boomboomer
Same problem with a Samsung gt-i9070 - Galaxy S Advance
Hi!
My i9070 has the same problem, but when i run the command: "mke2fs /dev/block/mmcblk0p3" shows the "Segmentation fault" error message.
Some one can help?
Thanks.
Bro U stated to format but How to format /efs partition
/efs not backed up
boomboomer said:
No, it won't work and trying to clone another imei is illegal.
Click to expand...
Click to collapse
I Dont have efs backed up and I also have formatted efs partition from adb shell and using that Dev type commands now i am in factory mode and my network is not working please give me any solution.
kaynpayn said:
I'm just writting this because i've recently had this problem. I managed to sort it out by my own but didn't really find it written anywhere, just bits and pieces scavenged from so many pages that might point to a solution (granted, part of my problem was also finding what was really my problem since the phone stopped working so fast i didn't really had the time to get what happened)
I was trying out swap for my S3, i had created a swap partition in my external card and then followed a guide here from xda to use an app called swapper2 (from market) to enable swap. I must have done something wrong because what it did was format my /efs partition instead as if it was a swap partition. Phone stopped working on the spot, obviously, and wouldn't past samsung's bootscreen.
Also, keep in mind while this worked for me there might be other ways of doing this which may be simpler. This is just what i figured for a solution.
When this helps:
- you accidentally formated your /efs partition
- you have a backup from your /efs partition, files copied with root explorer but not an image you can just flash back to the partition.
- your phone boots to download and to recovery but not to main system (which every tutorial i found seemed to assume to be able to do, i just figured their /efs was not as screwed as mine was)
- your recovery won't mount the /efs partition because it expects it to be ext4 but it's formated to something else and it showing the message:
"e: failed to mount /efs (Invalid argument)"
What doesn't work:
- any kind of standard solution like reflashing a stock rom with odin, with or without .pit file, clear EFS, whatever. It will flash, just won't solve since, apparently, nothing touches the /efs partition because it's so sensible. Even custom recoveries do mount it and apparently format and replace every single other partition but the /efs, which is why i had to do it manually.
Solution:
- simply format the /efs partition back to ext4 and copy your backup files there
What's needed:
- phone drivers installed on the computer. If you had kies installed, this should be covered already. Think you can't have it running while doing this though. Also, for what's worth, i've done this with windows 8 x64.
- updated android sdk tool, mainly adb. If adb is saying device not connected or not found, you may be using an outdated adb.exe (i was). I used adb.exe that came with this software here:
http://forum.xda-developers.com/showthread.php?t=1308546
- root. If your rom isn't rooted you can always flash CF-root from odin in download mode.
http://forum.xda-developers.com/showthread.php?t=1695238
- busybox, am not really sure if i actually got to need this, think so for the formating tool. Can't hurt to have more options though. This is how to install:
http://www.omappedia.com/wiki/Android_Installing_Busybox_Command_Line_Tools
- custom recovery that allows root through adb, i used Philz which is pretty awesome
http://forum.xda-developers.com/showthread.php?t=2002953
- backup files from your /efs. I had mine unzipped and copied to my externalsd while in windows. They were in an efs folder in the sd card. You can push this through adb to the phone later, but i found this way simpler.
How to:
- get into recovery (vol up+home+power button) and plug your phone to the computer. You'll hear an usb connected sound from windows after a bit.
- in recovery, navigate to Mounts and try the "mount /efs". It'll fail. Now, navigate to advanced and "view log". You'll see below that the phone tried to mount a partition and failed, in my case, it had unsucessfully tried to mount /dev/block/mmcblk0p3 which is the partition /efs uses. Take note of this partition name.
- On windows, open a command line (type cmd on you start menu), navigate to where you have adb.exe and type:
adb shell
If all went well, command prompt has changed. You can now issue commands directly to your phone from terminal.
- type "su" to get root permissions. Your command line should change to something like [email protected] Before i had this working i needed to use "Fix permissions". It's an option in the recovery menus on the phone.
- this step is optional but i did it anyway. I created an image of the partition i was going to mess with. If anything went wrong i could always flash it back even if it was broken. By the way, this is what i should have done in the first place instead of just copying /efs files. Would have made the process so much simpler... also, do this if you ever get the phone back working again. Type:
dd if=/dev/block/mmcblk0p3 of=/externalsd/efs.img
The /externalsd/efs.img is just a place you can save stuff to, like your external sd card. You can check what's your mounting point for the card with the command "mount" and look for something relevant like "externalsd".
Also, you may want to copy that efs.img to somewhere else from your phone (like your computer) for safekeeping. Literally remove card from phone, put in computer and copy files there. Notice you may need to reboot phone to recovery if you remove your card so it detects and mounts your card again. Sure, you can also do that from the command line, but it's just easier to reboot the phone.
- Now, we'll format the partition to something your phone can mount (ext4) and is expecting. Be careful, by doing this, you're actually erasing what's left of your partition and replacing by something clean. Type:
mk2fs /dev/block/mmcblk0p3
If all went well, you should see some kind of small report about what was just done.
- To mount this we'll need a mounting point. Type:
mkdir /efs
this will create an /efs folder in root, if it doesn't exist already, and to mount, type:
mount -t ext4 /dev/block/mmcblk0p3 /efs
- if all went well, you now have access to the /efs folder and can copy you files back:
cp -r /externalsd/efs/* /efs
where externalsd was my external sd card mounted on my phone.
- Check if your /efs folder has it's contents properly
ls /efs
I had to reboot the phone to recovery once more at this point and use the "fix permissions" option again.
After this, my phone booted up normally again.
Click to expand...
Click to collapse
I have restored my s6 edge by following this method. The EFS partition name is "sda3" for s6 edge if anyone want to restore s6 edge. There is typo in command "mk2fs /dev/block/mmcblk0p3" it should be mke2fs i think.
After restoring EFS my phone recovered from boot loop. But the imei is still invalid. Do you know any method to repair imei for s6 edge?. Thank You
---------- Post added at 02:18 PM ---------- Previous post was at 02:14 PM ----------
Blackwatch said:
I am getting stuck trying to fix this as I have a boot loop or corrupt /efs or something. I have tried to get my phone working by installing my ROM ( Omega v58 ) and also by trying to flash the latest stock 4.3 through Odin v3.09. I havent tried total stock 4.0.3 yet. No matter what I have done though I can't get past the boot logo ( or the walking Omega droid ). My phone just sits there and hangs
I have followed your steps and I have Philz ( 6.07.9.19 ) installed ( but not busybox unless it is sat there somehow from the Omega install ) but when i try to get adb shell running nothing happens or works..as you can see
What am i doing wrong? OR is my phone totally borked?
Click to expand...
Click to collapse
You don't have to run "su" command. "#" shows you already have root access.
Hi people. I've been browsing a lot lately and Reading about roms, kernel, and other stuff related to customization of Android devices. I consider myself enough tech-savvy to understand technical things about hardware on this devices but when it comes to all the thing related to flashing roms and kernels and related things i have no clue of what you're talking about, lol.
However, I'm really interested on "installing" Cyanogenmod 10 on my Galaxy Player 4 just to see what happens and how flashing roms feels like, so i can try different roms later and enhance my device. But no matter how hard I try to find a tutorial about how to begin from total stock (as the device comes from the store) haven't been lucky finding one. As far as I know the first step is flashing a new kernet with CWM, so then i can flash the roms. But I'm stuck on Step One :s
So, if there's a link you can post here to help begin with this flashing trend it'd be great. Or if you can redact a "custom" tutorial for me, a total programming noob but interested as hell about modifying my GP4 that would be a thousand times better.
Also, feel free to recommend me kernels or roms or whatever you feel i could use
Thanks!!!
PD: not native english speaker
I just finished doing this exact thing myself, so its fresh in my mind First, BACK UP!! there are different methods with varying degrees of how much they back up, search the forum for them. Definitely backup the efs. Instructions are in the first post for the CM10 ROM. Then, I began by flashing a custom kernel using Odin. Instructions on how to do this can be found in the Tips and Tricks section of this post:
http://forum.xda-developers.com/showthread.php?p=27615927
Kernels can also be found in the appropriate section of that post. Make sure you get one for your device. All of them include CWM (ClockworkMod) which is what you need to easily flash a full ROM. The kernel won't actually effect your current operating system accept to maybe improve performance.
Next, download the ROM file(s) onto your device. ROMs are also in the above post. Again, make sure you get one for your device. Read the instructions in the ROM thread on how exactly to flash them, but the general procedure is to boot into CWM by holding some set of buttons during start up (probably power + volume up) and navigate the CWM menu to flash the ROM.
Sent from my YP-G1 using xda app-developers app
from stock
download odin: https://docs.google.com/file/d/0B2ZcXCdM0CVJS196MFRtaUhfSUk/edit?usp=sharing
boot into download mode
flash terra silent: http://forum.xda-developers.com/showthread.php?t=1643384
download rom and gapps: rom: http://forum.xda-developers.com/showthread.php?t=2233983 gapps: http://goo.im/gapps/gapps-jb-20121011-signed.zip
put on sdcard
BACKUP!!!
flash rom and gapps
reboot
thanks a lot for the help!
Now a question... When you tell me to make a backup, what exactly should I backup and with what program or app? Installed Titanium BAckup app and all i see is the option to backup individual apps. I expected to find something like "total backup of the device" or a similar thing that bacups the whole thing...
please tell me what to use and what to do
thanks a lot again
kennethac said:
thanks a lot for the help!
Now a question... When you tell me to make a backup, what exactly should I backup and with what program or app? Installed Titanium BAckup app and all i see is the option to backup individual apps. I expected to find something like "total backup of the device" or a similar thing that bacups the whole thing...
please tell me what to use and what to do
thanks a lot again
Click to expand...
Click to collapse
Create a backup in cwm
This is so if anything goes wrong, you can get back
Sent from my Kindle Fire running CM10.1/SGT7
Ok i downloaded both Odin and the Terra Silent kernel. Samsung kies is already installed so Odin is detecting my galaxy player.
But the terra silent kernel is a zip file, if i extract it the extracted file has no extension, only says zlimage and i have no idea what it is. Then, when I open Odin, there are the next options:
PIT
BOOTLOADER
PDA
PHONE
CSC
where should i upload the zlimage?
kennethac said:
Ok i downloaded both Odin and the Terra Silent kernel. Samsung kies is already installed so Odin is detecting my galaxy player.
But the terra silent kernel is a zip file, if i extract it the extracted file has no extension, only says zlimage and i have no idea what it is. Then, when I open Odin, there are the next options:
PIT
BOOTLOADER
PDA
PHONE
CSC
where should i upload the zlimage?
Click to expand...
Click to collapse
That's because you're suppose to flash it via CWM. If it's a tar file, you flash it via Odin. And you're not suppose to extract it, lol.
TheKryptonite said:
That's because you're suppose to flash it via CWM. If it's a tar file, you flash it via Odin. And you're not suppose to extract it, lol.
Click to expand...
Click to collapse
haha ok i'm not extracting it anymore. But from those options that shows Odin, where i have to upload the "TerraSilent_usa-1.3.5" file?
This is what i see...
PIT
BOOTLOADER
PDA
PHONE
CSC
that's where i need help for the moment
kennethac said:
haha ok i'm not extracting it anymore. But from those options that shows Odin, where i have to upload the "TerraSilent_usa-1.3.5" file?
This is what i see...
PIT
BOOTLOADER
PDA
PHONE
CSC
that's where i need help for the moment
Click to expand...
Click to collapse
PDA is the one, I believe.
Is Terra Silent compatible with CM10??? Reading the thread of Terra Silent a user made a comment on this asking the developer (i guess) to make Terra Silent compatible with CM10.... :s
ok now i have some problems...
got to flash the Terra Silent Kernel. After rebooting everything was ok. Installed Rom Manager in order to install CWM. Rom Manager installed CMW and then came back to main menu. There was an option for creating a copy of the stock rom, thought it wolud be a good idea to make a copy. When i did it, phone went black and then reboted. after rebooting came back to the lock screen but changed language (spanish -> english). Algo noticed there was missing the google search bar. When entered to the apps menu there were a lot of icons of the android robot with an SD card symbol over. When clicked them it says that the apps are not installed on the system.
installed rom manager again, and went to recovery boot. flashed both cm9 and cm 10 included in the cm 10 thread. Now my playr is stuck in the recovery screen...
what do i do?
kennethac said:
ok now i have some problems...
got to flash the Terra Silent Kernel. After rebooting everything was ok. Installed Rom Manager in order to install CWM. Rom Manager installed CMW and then came back to main menu. There was an option for creating a copy of the stock rom, thought it wolud be a good idea to make a copy. When i did it, phone went black and then reboted. after rebooting came back to the lock screen but changed language (spanish -> english). Algo noticed there was missing the google search bar. When entered to the apps menu there were a lot of icons of the android robot with an SD card symbol over. When clicked them it says that the apps are not installed on the system.
installed rom manager again, and went to recovery boot. flashed both cm9 and cm 10 included in the cm 10 thread. Now my playr is stuck in the recovery screen...
what do i do?
Click to expand...
Click to collapse
Did you wipe the data, cache, and Davik cache?
TheKryptonite said:
Did you wipe the data, cache, and Davik cache?
Click to expand...
Click to collapse
Sorry. False alarm, i finally found i was doing something wrong so corrected it and now i'm using Jelly Bean in my galaxy player. But now there's another problem: system won't read the external SD card.
How can i fix this?
kennethac said:
Sorry. False alarm, i finally found i was doing something wrong so corrected it and now i'm using Jelly Bean in my galaxy player. But now there's another problem: system won't read the external SD card.
How can i fix this?
Click to expand...
Click to collapse
You internal SD card is probably switched for the external.
Find "vold.fstab. (system/etc)" open it, and change "/mnt/sdcard/sdcard1" to "/mnt/sdcard/sdcard0."
TheKryptonite said:
You internal SD card is probably switched for the external.
Find "vold.fstab. (system/etc)" open it, and change "/mnt/sdcard/sdcard1" to "/mnt/sdcard/sdcard0."
Click to expand...
Click to collapse
This is what the file shows:
#internal sdcard
dev mount sdcard / storage /sdcard0 1 /
devices/platform/s3c-sdhci.0/mmc host/mmco
#external sdcard
dev mount emmc /storage/sdcard1 auto /
devices/platform/s3c-sdhci.2/mmc_host/mmc1
what's the part that i have to edit???
kennethac said:
This is what the file shows:
#internal sdcard
dev mount sdcard / storage /sdcard0 1 /
devices/platform/s3c-sdhci.0/mmc host/mmco
#external sdcard
dev mount emmc /storage/sdcard1 auto /
devices/platform/s3c-sdhci.2/mmc_host/mmc1
what's the part that i have to edit???
Click to expand...
Click to collapse
#internal sdcard
dev mount sdcard / storage /sdcard1
#external sdcard
dev mount emmc /storage/sdcard0
Wait, before doing any changes like this, have you tried on going mnt/emmc or storage/sdcard1? @TheKryptonite he have a 4.0 and the sdcard is working without changing the paths.
Envoyé depuis mon Nexus 7 avec Tapatalk
zaclimon said:
Wait, before doing any changes like this, have you tried on going mnt/emmc or storage/sdcard1? @TheKryptonite he have a 4.0 and the sdcard is working without changing the paths.
Envoyé depuis mon Nexus 7 avec Tapatalk
Click to expand...
Click to collapse
That is the same thing four me. I did not have to switch storages at all
Sent from my Kindle Fire running CM10.1/SGT7
TheKryptonite said:
#internal sdcard
dev mount sdcard / storage /sdcard1
#external sdcard
dev mount emmc /storage/sdcard0
Click to expand...
Click to collapse
I did this change, switched numbers and now i can see the files on the sd card. Only that before flashing CM 10 the access to the sd card was through a folder calles "externa sd", now the sd card files and folders are scattered on the home screen of any file explorer i acess the sd card with. It's not a big ideal but i dont like it.
When i edited the file you told me there was a 1 after where now says sdcard 1. Shoud that number be erased or better keep it?
kennethac said:
I did this change, switched numbers and now i can see the files on the sd card. Only that before flashing CM 10 the access to the sd card was through a folder calles "externa sd", now the sd card files and folders are scattered on the home screen of any file explorer i acess the sd card with. It's not a big ideal but i dont like it.
When i edited the file you told me there was a 1 after where now says sdcard 1. Shoud that number be erased or better keep it?
Click to expand...
Click to collapse
I'd keep it.
Recently I was studying android recovery mode, and I have some questions. Anyone knows the answer? Thanks very much.
1. Can recovery flash bootloader?
From this link====>http://forum.xda-developers.com/showthread.php?t=2321310, I think it can do that. But I'm not sure.
2. Can recovery flash recovery partition itself?
I think it can not do this. Not confirm that.
3. We know in update.zip, boot.img is corresponding boot partition, but why system is a folder, not system.img? There is a system partition also.
4. While OTA upgrade system, why the update package downloaded under /cache path? Can we change it to sdcard?
5. Most important, what exactly update-script do things under recovery mode? How the command executed?
BTW, there are other questions, but not related to Recovery Mode.
1. How can I see the flash partitions? I know to use the command cat /proc/mtd, but as Samsung, it use emmc flash, while I type that command, no results printed. How to see?
2. About userdata partition, we know that when first run android OS, system will copy files from /system to /data, but does it do it every time that we turn on the phone or just do it once after the first booting after we update our system?
Hello,
I can answer some questions, and I hope someone else can fill the blanks.
1. Can recovery flash bootloader?
=> Yes, you have to modify your boot image, but it still possible, just include the modified boot image in the update file, and give good command in update.zip
2. Can recovery flash recovery partition itself?
=> I am not sure, but I think its possible, I saw code of recovery in Android code, so if you modify it, and include the good image in update.zip, I think you will see the modification. Never tried for now.
3. We know in update.zip, boot.img is corresponding boot partition, but why system is a folder, not system.img? There is a system partition also.
=> In fact is depend witch compilation system you use. For Cyanogen, yes in fact its a folder, but for AOSP its System.img
The difference comes from the command file in update, theire not the same. But finally the result in the same. We have a system partition.
4. While OTA upgrade system, why the update package downloaded under /cache path? Can we change it to sdcard?
=> Reasons I can see :
--> In past, sdcard was not mounted by default in recovery mode, so can't see the update.zip file
--> sdcard can be removed at any time, its dangerous, when do the update to loose the file
--> To be sure have right to remove the update.zip when installation done
--> Old phone didn't have all a sdcard, cache is sure to exists
=>Yes we can change it, but we have to be sure the sdcard is mounted on recovery mode. And be sure of the path of sdcard on recovery mode. For exemple in Nexus one it is /sdcard, in Samsung Galaxy S2 is /emmc/, in Samsung S4 mini its /sdcard/0/ ... So it could be a reason why its not in sdcard, because the path is not generic.
5. Most important, what exactly update-script do things under recovery mode? How the command executed?
=>It does lot of stufs, like mount partitions, copy system files, ...
The update-script is in elf script. Generally, an elf interpreter is given just next to the update-script.
I hope it helped you,
JHelp
1 yes, but flashing firmware from recovery can be dangerous and all though unlikely I have seen many brick there phone doing so
2. Yes, rather easily so long as the .zip is put together properly. But like bootloader, it is safest so flash through fastboot or download mode but a very unlikely brick so mostly safe
3. This is how a ROM gets built from source but it needs not be in this setup. At the same note I can't see a better way to flash through recovery than like it is. Using flash_raw_image would work but due to size a system.img shouldn't be flashed in recovery rather through fastboot, bootloader or download mode
4 mostly because you couldn't have an oem ota update without an SD card which isn't a prerequisite for using a phone. Also I believe there is some added safety flashing directly from nand, but in truth this is all speculation. Yes with a rooted phone this could be changed but most often it isn't wise to flash an oem ota on a rooted device
5 lots of things, take a look at my threads for a guide I made explaining this
1 cat /proc/partitions
mount
ls -l /dev/block/
And then keep searching until you get /by-name which many phones have, but this isn't always the same path so if you need further help ask and I'll walk you through it
2 I think this depends on a lot of things, but I don't have a good answer so rather than speculating I'll choose not to answer
Feel free to ask other questions
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
1 yes, but flashing firmware from recovery can be dangerous and all though unlikely I have seen many brick there phone doing so
2. Yes, rather easily so long as the .zip is put together properly. But like bootloader, it is safest so flash through fastboot or download mode but a very unlikely brick so mostly safe
3. This is how a ROM gets built from source but it needs not be in this setup. At the same note I can't see a better way to flash through recovery than like it is. Using flash_raw_image would work but due to size a system.img shouldn't be flashed in recovery rather through fastboot, bootloader or download mode
4 mostly because you couldn't have an oem ota update without an SD card which isn't a prerequisite for using a phone. Also I believe there is some added safety flashing directly from nand, but in truth this is all speculation. Yes with a rooted phone this could be changed but most often it isn't wise to flash an oem ota on a rooted device
5 lots of things, take a look at my threads for a guide I made explaining this
1 cat /proc/partitions
mount
ls -l /dev/block/
And then keep searching until you get /by-name which many phones have, but this isn't always the same path so if you need further help ask and I'll walk you through it
2 I think this depends on a lot of things, but I don't have a good answer so rather than speculating I'll choose not to answer
Feel free to ask other questions
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I've got /by-num, but no /by-name, device is Sansumg GT-9288
not sure what a Sansumg GT-9288 is, gsmarena and google dont give me results
what happens with
cat /proc/partitions
or just
mount
?
demkantor said:
not sure what a Sansumg GT-9288 is, gsmarena and google dont give me results
what happens with
cat /proc/partitions
or just
mount
?
Click to expand...
Click to collapse
Sorry, type wrong, should be GT-9228, it's a customer made smartphone only for CMCC.
I can get the partition info by GT-9220, so I think it's because of the customer made that I can not get the by-name folder.
Thanks again.