Hello there !
It's my first post, sorry to disturb you (by the way, the video for the noobs is great ! ). I'm French, so please excuse me if my language isn't fluent. I used the search function, I don't think there's already a relevant thread.
I've got a problem with my YP-G1. I tried to flash terrasilent, it worked, then I tried to flash CM10, it didn't : my device started the install, rebooted 3 times as expected, then rebooted in the new recovery mode, but it crashed, rebooted and did it again, indefinitely. (if you have a solution for that too, please tell me).
Now I'm trying to get it back to the stock rom. It worked a first time by flashing the stock G1XXKPQ INTL with heimdall. But then I tried to flash pacman, and it did just the same thing. Plus, I think I messed with the drivers, and now heimdall doesn't work anymore (I can't get zadig install the good drivers). But Odin seems to be working perfectly. Can somebody tell me how to convert this heimdall package (http://forum.xda-developers.com/showthread.php?t=1531850) to Odin ?
Thank you for the answers,
Antonin
Your problem concerning your installation may lies in the fact that you don't have a good efs maybe. Also have you tried uninstalling the drivers and reinstalling them? Maybe it will help you reinstalling the heimdall after.
Envoyé depuis mon Nexus 7 avec Tapatalk
knostut not
Thank you for the answer.
I'm trying uninstall and reinstall drivers. I'll let you know.
EDIT :I must be a complete noob ! well, it worked. I already tried this, but this time, zadig managed to setup the driver. Hurrah ! I'm now running the stock rom.
Any idea on what's the problem with CM10 and pacman ? I just checked, my EFS folder is not empty, at least. But the files are maybe corrupted, or something like that ?
I'll try to describe you what happened during the install of CM10/Pacman, but it's quite difficult to do so in English. Well, as I said, the first steps (kernel preflash and beginning of the full setup) were good, but right after the 3 reboots, when the new recovery interface started, it shut down (showing a picture of the android lying down, and an error message, which disappeared too quickly for me to read) and rebooted.
anto-shturmovik said:
Thank you for the answer.
I'm trying uninstall and reinstall drivers. I'll let you know.
EDIT :I must be a complete noob ! well, it worked. I already tried this, but this time, zadig managed to setup the driver. Hurrah ! I'm now running the stock rom.
Any idea on what's the problem with CM10 and pacman ? I just checked, my EFS folder is not empty, at least. But the files are maybe corrupted, or something like that ?
I'll try to describe you what happened during the install of CM10/Pacman, but it's quite difficult to do so in English. Well, as I said, the first steps (kernel preflash and beginning of the full setup) were good, but right after the 3 reboots, when the new recovery interface started, it shut down (showing a picture of the android lying down, and an error message, which disappeared too quickly for me to read) and rebooted.
Click to expand...
Click to collapse
Hmm can you send me a copy of your cyanogenmod_mtd.log please?
Envoyé depuis mon Nexus 7 avec Tapatalk
zaclimon said:
Hmm can you send me a copy of your cyanogenmod_mtd.log please?
Envoyé depuis mon Nexus 7 avec Tapatalk
Click to expand...
Click to collapse
Here it is :
Code:
+ /tmp/busybox test -e /sdcard/cyanogenmod.cfg
+ /tmp/busybox rm -f /sdcard/cyanogenmod.cfg
+ /tmp/busybox umount -l /system
umount: can't forcibly umount /system: Invalid argument
+ /tmp/erase_image system
+ /tmp/busybox mount -t yaffs2 /dev/block/mtdblock2 /system
+ /tmp/busybox umount -l /cache
+ /tmp/erase_image cache
+ /tmp/busybox umount /data
umount: can't umount /data: Invalid argument
+ /tmp/make_ext4fs -b 4096 -g 32768 -i 8192 -I 256 -a /data /dev/block/mmcblk0p2
Creating filesystem with parameters:
Size: 2013265920
Block size: 4096
Blocks per group: 32768
Inodes per group: 560
Inode size: 256
Journal blocks: 7680
Label:
Blocks: 491520
Block groups: 15
Reserved block group size: 119
Created filesystem with 11/8400 inodes and 8964/491520 blocks
+ /tmp/busybox umount -l /datadata
umount: can't forcibly umount /datadata: No such file or directory
+ /tmp/erase_image dbdatafs
can't find dbdatafs partition+ /tmp/busybox test -e /sdcard/backup/efs/serial.info
+ /tmp/busybox echo Cannot restore efs.
Cannot restore efs.
+ exit 7
Yeah well you miss one file in your efs which is serial.info, add it into your efs and it should work after.
Envoyé depuis mon Nexus 7 avec Tapatalk
zaclimon said:
Yeah well you miss one file in your efs which is serial.info, add it into your efs and it should work after.
Envoyé depuis mon Nexus 7 avec Tapatalk
Click to expand...
Click to collapse
I don't have such a file in my backup... Any way to have a new one ?
anto-shturmovik said:
I don't have such a file in my backup... Any way to have a new one ?
Click to expand...
Click to collapse
Check in the recovery thread for getting a dummy one.
zaclimon said:
Check in the recovery thread for getting a dummy one.
Click to expand...
Click to collapse
OK. Should I completely replace the entire folder by the dummy one, or just serial.info ?
EDIT : another noob question : does flashing custom Roms work on a non-rooted device ? Or maybe flashing a custom kernel (Terrasilent) automatically roots the device ?
anto-shturmovik said:
OK. Should I completely replace the entire folder by the dummy one, or just serial.info ?
EDIT : another noob question : does flashing custom Roms work on a non-rooted device ? Or maybe flashing a custom kernel (Terrasilent) automatically roots the device ?
Click to expand...
Click to collapse
Just the serial.info and you can flash custom roms and kernels without having a rooted device.
zaclimon said:
Just the serial.info and you can flash custom roms and kernels without having a rooted device.
Click to expand...
Click to collapse
OK, thank you very much.
I'll try that tomorrow, and I'll let you know.
I tried to use ES explorer to copy-paste the serial.info into my efs directory, it doesn't work ("access denied")...
anto-shturmovik said:
I tried to use ES explorer to copy-paste the serial.info into my efs directory, it doesn't work ("access denied")...
Click to expand...
Click to collapse
Have you given it root permission?
Sent from my YP-G1 using Tapatalk 4 Beta
goldflame09 said:
Have you given it root permission?
Sent from my YP-G1 using Tapatalk 4 Beta
Click to expand...
Click to collapse
My device isn't rooted. Has it something to do with that ?
Moreover, I just had a problem when flashing terrasilent, so I just did a restart from scratch using the recovery with heimdall (YPG1IntlRestoreHeimdall). Is it supposed to fix my efs anyway ?
EDIT : Root permission given to ES explorer. I was able to copy-paste the file. But a lot of files from the "dummy" efs seems to be missing to my efs folder. Is it normal ?
EDIT 2 : Now that the drivers for heimdall are working, Odin doesn't work anymore... Can I flash TerraSilent with heimdall ? Or maybe I can skip this step ?
anto-shturmovik said:
My device isn't rooted. Has it something to do with that ?
Moreover, I just had a problem when flashing terrasilent, so I just did a restart from scratch using the recovery with heimdall (YPG1IntlRestoreHeimdall). Is it supposed to fix my efs anyway ?
EDIT : Root permission given to ES explorer. I was able to copy-paste the file. But a lot of files from the "dummy" efs seems to be missing to my efs folder. Is it normal ?
EDIT 2 : Now that the drivers for heimdall are working, Odin doesn't work anymore... Can I flash TerraSilent with heimdall ? Or maybe I can skip this step ?
Click to expand...
Click to collapse
yes extracta the zimage from inside the tar and you should be able to flash it
goldflame09 said:
yes extracta the zimage from inside the tar and you should be able to flash it
Click to expand...
Click to collapse
When I try to load the zimage it shows an error message: "Tar header contained an invalid file size"
But I was able to have Odin working !
EDIT : Pacman Flashed successfully. The loading is a bit long, though, I've been waiting for 5 mins and still showing the loading screen.
EDIT 2 : It works ! Thanks a lot to goldflame and zaclimon !
Related
Hi,
some days ago i brought a new Prestigio Tablet. There was no Root Tool available for this tablet and i did a lot of searching to find a way to achieve root rights.
Today I found a way and want to share my results with you.
The solution is similar to the one described in this Post.
The main difference is the file system of the system image.
In the PMP5080B Rom the system.img is in cramfs and the wendal script unpacks this image onto disk.
The system.img in the PMP5097C is ext3 so you can mount the image directly on a Linux system and copy the Superuser binaries and set the rights with chmod.
copy /B su system\bin\
copy /B Superuser.apk system\app\
chmod -R 0777 system/*
chmod 6755 system/bin/su
chmod 6755 system/app/Superuser.apk
Click to expand...
Click to collapse
after you did this and copied the modified image back into the Temp/Image folder you can use the script to pack the ROM back together.
Now you can flash the new ROM on the usual way like described in the manual.
Hope this helps
Please can you upload the patched image file ..
THX a lot
Here you are:
https://www.dropbox.com/s/lwa1d0v6lotuhwi/rootrom.zip
teddybt said:
Here you are:
https://www.dropbox.com/s/lwa1d0v6lotuhwi/rootrom.zip
Click to expand...
Click to collapse
thx .. i have install the rom but i have no root .....
I checked the uploaded Rom.
The owner of the Superuser files was not root.
Hope this will fix the issue.
Link: https://www.dropbox.com/s/lwa1d0v6lotuhwi/rootrom.zip
Thx Thx Thx... Rooted pmp 5097 now... Your the Best... 1000 Thx
OMG thank you so much for this! I have been waiting a long time for this. You are awesome!
You don't happen to know how to install clockworkmod if its possible do u? Cheers.
Sent from CrazyD's Galaxy II via XDA Android App
Is there any link for this?
I have 1.06 on my tablet and I would like to root it.
I have 1.06 also.
Is there a way to root it?
I found 1.06 root version on a RU site.
This version has 512 MB for apps and later on 1GB for apps ver. should be available.
iJohnny said:
I found 1.06 root version[/URL] on a RU site.
This version has 512 MB for apps and later on 1GB for apps ver. should be available.
Click to expand...
Click to collapse
I installed this onto my 5097 and it hasn't seemed to give me root access at all have i missed something?
smithaz1212 said:
I installed this onto my 5097 and it hasn't seemed to give me root access at all have i missed something?
Click to expand...
Click to collapse
Same problem here
I dont suppose anyone has had any progress with the russian firmware which was posted earlier, still cant seem to gain root access through it for some reason. It might possibly be the same problem as was detailed before in that the owner of the superuser is not root? although i have noticed that there is no superuser app on this firmware, any ideas anyone?
Ok found a firmware that seems to be rooted and is working 100% on my device only small issue is that it is for another tablet (eFun M1005) which seems to be the exact same tablet just rebranded for sale in asia possibly. Anyway:
h t t p ://narod.ru/disk/48873776001.bacdb0ce2f72ba9a6bd089bf055f247a/M1005HN_20120419_V1.0.3_OS4.0_mod_v2.7z.html
As i said is working fine on my tablet and seems to have no problems but i have only tested it for ~1 hour
1.06 root
I found 1.06 root version on a RU site.
This version has 512 MB for apps and later on 1GB for apps ver. should be available.
Click to expand...
Click to collapse
Its no root
I made rooted version of latest v.1.0.6 firmware. But as a new user, I cannot post link
Thanks to daddycruel for posting my link in next post.
Here is the link for download, thank's to gregyk!
http://www.sendspace.com/file/ignk4l
mount
Hi,
I've just downloaded official and rooted 1.0.6 img and I wanted to look into it before flashing. For some reason
Code:
mount -t ext3 -o loop ASBSM1005HN_20120802_V1.0.6.img /mnt
on my box doesn't work (wrong superblock). Did they changed fs or I'm doing something wrong?
BTW thanks for sharing the rom.
Ficik said:
Hi,
I've just downloaded official and rooted 1.0.6 img and I wanted to look into it before flashing. For some reason
Code:
mount -t ext3 -o loop ASBSM1005HN_20120802_V1.0.6.img /mnt
on my box doesn't work (wrong superblock). Did they changed fs or I'm doing something wrong?
BTW thanks for sharing the rom.
Click to expand...
Click to collapse
You must extract firmware file with Wendal RK29xx Image Tools and then you get images (.img) that you can mount in linux (system.img, etc ..).
I rooted like this: extracted firmware with wendal, than mounted system.img in linux - copied "su" and "superuser.apk" and set right permissions to this files. Than packed firmware back together also with wendal tools.
Today I had to send my 5097 for repair ... it won't turn on no more normally. I had to press few times reset, then power and if that didn't work - sometimes it started when I connected it to PC. I tried several different firmwares, but same situation with all.
Anyone heard of or had similar problems?
I posted this question in several threads and I got no answer, so once again, can someone post here a boot.img from stock rom, base 1.18, or a boot.img from nand backup of the same rom. I''m interested only for boot.img from STOCK rom, not from custom rom that can be obtained here on forum?
If someone has factory rom on his/her phone and he installed custom recovery and rooted it, please make a nand backup and post me boot.img from backup.
Thanks in advance.
So, nobody willing to help?
I'm sorry man, don't know how I could get it, I already flashed sense revo R3 :l
Sent from my awesome fridge
Thank's anyway.
However you can help me in another way. First a question, can you remove apps from system partition without reappearing after reboot? Then, did you flash boot.img separately from fastboot or you just flashed the rom.zip? And when you give me the answers, can you post me a file located on the system root of phone (the same location where system, data, sdcard and the rest of the stuff is mounted) called default.prop?
nlooooo said:
I posted this question in several threads and I got no answer, so once again, can someone post here a boot.img from stock rom, base 1.18, or a boot.img from nand backup of the same rom. I''m interested only for boot.img from STOCK rom, not from custom rom that can be obtained here on forum?
If someone has factory rom on his/her phone and he installed custom recovery and rooted it, please make a nand backup and post me boot.img from backup.
Thanks in advance.
Click to expand...
Click to collapse
here u go bro. as requested, its stock rom base 1.18, customer recovery and rooted.
Yup, will do, but it'll take some time, just coming back from iceskating.
Sent from my awesome fridge
MaartenXDA said:
Yup, will do, but it'll take some time, just coming back from iceskating.
Sent from my awesome fridge
Click to expand...
Click to collapse
I think I'm getting somewhere, now I need your stuff to post me.
And I'm sure you've made a nand backup of your current rom so if you're willing post me your boot.img from the backup, not from the rom I already have it.
Don't have a backup
But the system app removal worked.
I'm on Sense Revolution R3, used aroma file manager 1.80 to remove the files, worked like a charm.
Sent from my awesome fridge
MaartenXDA said:
Don't have a backup
But the system app removal worked.
I'm on Sense Revolution R3, used aroma file manager 1.80 to remove the files, worked like a charm.
Sent from my awesome fridge
Click to expand...
Click to collapse
Aroma yes, but how about using Titanium Backup, wipe data first, then uninstall and reboot? The point is to do it when phone booted.
And I need that default.prop, please.
nlooooo said:
Aroma yes, but how about using Titanium Backup, wipe data first, then uninstall and reboot? The point is to do it when phone booted.
And I need that default.prop, please.
Click to expand...
Click to collapse
Here it is, sorry had to use .zip, .prop is invalid
No doesn't work with titanium and delete data.
Then it's not a problem with secure kernel, cause you boot with unsecure, this is from your default.prop
ro.secure=0
Click to expand...
Click to collapse
so this means that you successfully flashed boot.img when you flasher rom. Have you ever flashed it separetely, I mean when you installed previous versions of rom?
And one more question which SU app do you have Superuser on SuperSU?
nlooooo said:
Then it's not a problem with secure kernel, cause you boot with unsecure, this is from your default.prop
so this means that you successfully flashed boot.img when you flasher rom. Have you ever flashed it separetely, I mean when you installed previous versions of rom?
And one more question which SU app do you have Superuser on SuperSU?
Click to expand...
Click to collapse
Yeah, I flashed the one with R1 or R2, to fix the WiFi bug.
MaartenXDA said:
Yeah, I flashed the one with R1 or R2, to fix the WiFi bug.
Click to expand...
Click to collapse
So definitely, boot.img flashing via recovery is mandatory to get it all working.
Apps uninstalling still looks kinda weird to me. You didn't tell me about SU app.
@nlooooo
Do you still want the boot.img that not yet go thru android kitchen ?
I have one that in CWM backup.
ckpv5 said:
@nlooooo
Do you still want the boot.img that not yet go thru android kitchen ?
I have one that in CWM backup.
Click to expand...
Click to collapse
Thanks but I've already got it, I unpacked it to see default.prop settings, but it all seems that uninstalling of system apps doesn't depend on the way how kernel boots, even if it boots as unsecure apps still can't be uninstalled.
However I confirmed my claims that boot.img can't be flashed installing rom, only via fastboot.
Yep.. correct.
What I notice is the system/app folder's permission is rwxr-xr-x instead of the normal rwxrwxrwx and I can't find where the permission is set.
ckpv5 said:
Yep.. correct.
What I notice is the system/app folder's permission is rwxr-xr-x instead of the normal rwxrwxrwx and I can't find where the permission is set.
Click to expand...
Click to collapse
Maybe it's set here in ramdisk in int.protou.rc
on emmc
mkdir /system
mkdir /data 0771 system system
mkdir /cache 0770 system cache
mkdir /devlog 0700 root root
devwait [email protected]
mount ext4 [email protected] /system ro barrier=1
devwait [email protected]
# exec /system/bin/e2fsck -p [email protected]
mount ext4 [email protected] /data nosuid nodev barrier=1 noauto_da_alloc
mount ext4 [email protected] /cache nosuid nodev barrier=1
mount ext4 [email protected] /devlog nosuid nodev barrier=1
I'm not a programmer so I dont know, or maybe in init.rc.
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 there i recently upgraded to CM10.2 experimental and all worked fine. After playing around a bit i decided to go back to my CM10.1 rom and that went off without a hitch but my phone sat in the boot for over an hour so i decided to go into recovery and wipe my data when i was faced with (unable to mount /sdcard. I then checked in my log and this is what i found
Install from sdcard complete
minzip: Extracted file "/system/xbin/strace"
minzip: Extracted file "/system/xbin/su"
about to run program [/tmp/install/bin/persist.sh] with 2 args
cat: can't open '/temp/save/prop': no such file or directory
sed: -i requires an argument
script result was [/system]
Install from sdcard complete.
I:Can't partition non-vfat: datamedia
I:can't partition non-vfat: ext4
I:Can't format unknown volume: /emmc
W: failed to mount /dev/block/mmcblk0p12 (invalid argument)
I was going to install stock rom and recovery using odin but a friend said that it would make it worse. Any help will be appreciated... Thanks in advance
P.S i have been rooting for about 6 years and have had 4 phones and this has never happened
-Athlon
the problem is about the partition?
Probably the best flash samsung official rom via Odin, for your country
misacek said:
the problem is about the partition?
Probably the best flash samsung official rom via Odin, for your country
Click to expand...
Click to collapse
thank you for the reply i was worried it would mess up even more. I will be flashing tonight (my time) to see if it works and will let you know.:good:
-Athlon
Read everything here on xda about everything / basics /
Important backup / EFS folder /
misacek said:
Read everything here on xda about everything / basics /
Important backup / EFS folder /
Click to expand...
Click to collapse
Yeah after i screwed up my phone a while back because of EFS i never do anything without reading up about it:silly::good:
Thanks for the help:angel:
I do not know what is the problem exactly?
I did all the installation / ICS, JB / so as download, it should go fix it?
misacek said:
I do not know what is the problem exactly?
I did all the installation / ICS, JB / so as download, it should go fix it?
Click to expand...
Click to collapse
Could you explain a bit further by what you mean?
I also had a big problem? Initially flash JB / help me / then flash / ICS older fw / phone and ran and offered the update via OTA
misacek said:
I also had a big problem? Initially flash JB / help me / then flash / ICS older fw / phone and ran and offered the update via OTA
Click to expand...
Click to collapse
Ok i dont quite get what the issue is though?
Fixed
Hi all
I fixed my phone using Galaxy S3 i9300 Unbrick [restore to stock rom] [noobs][easy] but probably the most important part is just below step 8 :good:
Thanks.
P.S: how do i close this
Closed on OP request.
P.s. To bring anything to a moderator's attention, use the yellow triangle button (commonly referred to as the report button) and report the relevant post
Problem solved!
**********************
I think my problem happened because a flashed a ROM with MG4 baseband, and then flashed UltimaROM with another baseband which caused my baneband to corrupt.
I tried to flash Stock ROM and install different baseband but non of this worked.
finally I flashed BTU stock ROM (Which comes with MG4) but the problem still here.
Then I installed root, deleted the efs folder and replaced all the files with the files in the backup - restart and everything is working! my IMEI returned to normal.
**********************
Original question
Hello devs,
I have Siyah kernel which auto backup my EFS, i have backup named "efs_28Aug2013-1852.tar.gz"
I want to restore from this backup because I lost my IMEI when I flashed UltimaROM
I renamed it to "efsbackup.tar.gz" and put it in the root of the sdcard
then I started adb shell & run the code
Code:
su
umount /efs
mke2fs /dev/block/mmcblk0p1
mount -w -t ext4 /dev/block/mmcblk0p1 /efs
busybox tar zxvf /sdcard/ efsbackup.tar.gz -C /
I granted ADB shell root access
then i went to recovery and run the command (because I can't run umount /efs while device's running it gives resource busy message)
However when I run the first command "su" in gives me this message
Code:
/sbin/sh: su: not found
so I skipped to the next command
but I get the message
Code:
umount: can't umount /efs: Invalid argument
Please guys any help appreciated
Click to expand...
Click to collapse
Unzip it with a file manager and use a root explorer to replace manually
Sent from my GT-I9300 using Tapatalk 4
.
I've backup my efs with adb but how do you have a file on tar format, i've got a file on .img, it's normal ?
There's about nine different ways to backup the efs, .img is fine but a little on the large side at 20mb. A .tar of the same is only 5mb.
rootSU said:
Unzip it with a file manager and use a root explorer to replace manually
Sent from my GT-I9300 using Tapatalk 4
Click to expand...
Click to collapse
Thank you for your reply, I did as you said but this only changed my IMEI from "Unknown" to the generic IMEI "004999..."
Is there something wrong in the method or my backup may be corrupt
Sent from my Nexus 7 using Tapatalk 2
Read the imei / efs thread in general.
Sent from my GT-I9300 using Tapatalk 4
Thank you again, I read the thread in the past but it looks like it has been updated recently.
I think my problem happened because a flashed a ROM with MG4 baseband, and then flashed UltimaROM with another baseband which caused my baneband to corrupt.
I tried to flash Stock ROM and install different baseband but non of this worked.
finally I flashed BTU stock ROM (Which comes with MG4) but the problem still here.
Then I installed root, deleted the efs folder and replaced all the files with the files in the backup - restart and everything is working! my IMEI returned to normal.
Thank you RootSU for your help.
hey bro,
i am stuck
help me out
- my efs(folder) is blank
- i installed stock with pit file but no help!
- right now my cell is in bootloop!
- it goes to recovery, download mode.
i have efs.tar.gz file and a folder named efs in my ext sd
how do i copy that to int memory?
can't even create a cwm flashable zip file of the same?????
help me bro.....
You are posting in a thread that tells you how to restore an efs backup, how much more could you possibly need?
Go to recovery, factory reset.
Get the phone to boot, unpack the .tar file and follow the instructions in the OP.
boomboomer said:
You are posting in a thread that tells you how to restore an efs backup, how much more could you possibly need?
Go to recovery, factory reset.
Get the phone to boot, unpack the .tar file and follow the instructions in the OP.
Click to expand...
Click to collapse
Dear boomboomer,
i am sorry, but my phone is in "bootloop" how am i suppose to delete the "EFS" ? that s what i am asking!!!!!
i have both efs.tar.gz and extracted folder ready in my ext-sd......
i wonder if somebody can help me with creating a cwm.zip from the .tar file
thanks ....
try to install stock again via odin but this time install a diffrent version (for example if you installed INU this time try INS).. before that factory reset your phone and wipe cache via recovery mode.. don't lose your efs backup it's very important copy it to your PC in case something wrong happens
i already did so
almousawi said:
try to install stock again via odin but this time install a diffrent version (for example if you installed INU this time try INS).. before that factory reset your phone and wipe cache via recovery mode.. don't lose your efs backup it's very important copy it to your PC in case something wrong happens
Click to expand...
Click to collapse
bro, thanks for your help recently i tried cm 10 also but nothing happened.
believe me i tried everything now the only option is left that is
to restore efs backup from efs.tar.gz (which is about 12 MB)
OR
create a cwm flashable zip from the efs folder which is about 22 MB)
OR
take my phone to download mode and try to push whole "efs" folder to the location with help of "ADB"
hello
mikks said:
bro, thanks for your help recently i tried cm 10 also but nothing happened.
believe me i tried everything now the only option is left that is
to restore efs backup from efs.tar.gz (which is about 12 MB)
OR
create a cwm flashable zip from the efs folder which is about 22 MB)
OR
take my phone to download mode and try to push whole "efs" folder to the location with help of "ADB"
Click to expand...
Click to collapse
hello nobody is here to help......??????
mikks said:
hello nobody is here to help......??????
Click to expand...
Click to collapse
Correct this is not a paid for service .
Suggest you take it to a service centre .
know that i did that already....
JJEgan said:
Correct this is not a paid for service .
Suggest you take it to a service centre .
Click to expand...
Click to collapse
thanks for the reply, respect to your reply and interest no disrespect ...
i took that to the center but they failed and by the way they come to me in some cases... so they give me free service...
my phone is in boot loop, i have efs.tar.... can i use phills recovery ????? or can i use someone elses backup... just to boot up my device ...then i'll be good .... i just need to get my device booted up.....