Related
I’ve compiled a quick guide to instruct how to make a copy of the /efs folder. I’ve found in many threads suggestions about backing up this folder but the methods itself are very general. Most of the times they suggest to “root and copy the folder” with Root Explorer or similar, but usually it’s not that easy or it just doesn't work for everyone (my case).
This guide ASUMES you have read this Excellent Guide by Darkstrikerfirst:
H E R E <-- Make sure to read the ADB Guide.
I recommend doing this with a Mobile just taken out of the box or with any Official ROM of its Service Provider. If you have already Flashed your phone with another ROM but its working fine, then you can use that /efs also.
Why the /efs folder?
This is a very sensitive system folder that contains Phone-specific information such as the IMEI (encrypted in the nv_data.bin), wireless devices MAC addresses, product code (also in the nv_data.bin), and much more. Often users trying to change product codes or trying to unlock the mobile will end up corrupting data in this location.
Why back it up?
Well, let’s resume it saying that backing-up this little folder will keep you away from Samsung service centers.
***WARNING: I take no responsibility to any damage caused by the methods cited and/or written here. Their sole purpose is to back-up data and not to alter in any way the integrity of the original files of the mobile***
Please don’t ask how to recover your IMEI if you have previously messed your SGS without backing up this folder. I’m not familiar with such methods plus it is UNRELATED to this thread.
What you will need:
Rooted SGS to get permissions as a SU (Super User) and perform the backup
I would suggest learning a little about the terminal commands used (in case you are not familiar with them), as it’s better to know what you are doing rather than typing strings like a little chimp without knowing what they are; if you are a little lazy, then you have a good chance bricking your mobile.<- Busybox Commands(or Google them)
Terminal Emulator by Jack Palevich (available from the market) <-Terminal Emulator or use ADB which is included in the SDK Development Tools
IMPORTANT: If getting "error: device not found" under ADB (happened to me under CM7 2.3.4), you need to update your ADB drivers. Go HERE and follow the instructions to download the USB Driver for Windows, Revision 4 (Nexus S Support). Then update the drivers under your Windows Device Manager.
--------------------------------------
Backup commands
--------------------------------------
Depending on the type of root, you might have to use “busybox” at the beginning of the sting or just the string:
The standard prompt of terminal (adb) is a $ sign. Once you enter “SU” it will become a # Sign.
***NOTE: Make sure to keep an eye on the screen of your SGS during this process, because it will request SU permissions; else, you will get an error (just if it’s the first time). In Terminal Emulator you will need to reset the app after granting permissions cause it usually freezes***
*Remember: to use ADB you need to enable USB DEBUGGING under Applications/Development in your SGS. Once you are finished with the files, you need to turn it off so you can get the files.
Code:
su
tar zcvf /sdcard/efs-backup.tar.gz /efs or
busybox tar zcvf /sdcard/efs-backup.tar.gz /efs
After this, you will end up with the file efs-backup.tar.gz in your INTERNAL SDCARD, which is a “tarball” or a ZIP of the /efs folder. That file is your backup. You can expand it with Winrar.
In another forum I also saw a recommendation to back up the st13 under /dev/block which can support greatly to recoveryour IMEI in case of a screw-up:
Code:
su
cat /dev/block/stl3 > /sdcard/efs_dev-block-stl3.img or
busybox cat /dev/block/stl3 > /sdcard/efs_dev-block-stl3.img
Same thing, the target is the INTERNAL SDCARD, so go ahead and copy the file.
----------------------------
nv_data.bin - Restore
----------------------------
In case you screwed your IMEI by playing with the nv_data.bin and you are experiencing issues like:
Fake IMEI (usually 004999010640000)
Unable to download apps from the market
Unable to unlock your SIM card using your PIN
Weird apps are downloading automatically from the market
Blinking SIM card icon on the top tray… ETC
You may want to upload your fresh copy of this file back to the phone. Use this commands:
(thanks to Methyldioxide method to recover the product code http://forum.xda-developers.com/showthread.php?t=780509 )
Copy the file from your backup (efs-backup.tar.gz) and paste it in the INTERNAL SDCARD:
Code:
cp /sdcard/nv_data.bin /efs/nv_data.bin
rm -rf /efs/nv_data.bin.md5 OR
busybox rm -rf /efs/nv_data.bin.md5
Reboot your SGS
The md5 hash/signature is removed (rm) as the system will generate a new one.
**Most likely your SIM code won’t work after this and you won’t be able to log into the phone**
Pop off your SIM card, boot your SGS and execute the following commands to change ownership of the file under ADB or Terminal as well:
Code:
su
busybox chown 1001:1001 /efs/nv_data.bin or
chown 1001:1001 /efs/nv_data.bin
Hope this can help anyone with doubts. Cheers!
An alternative to the backup part is to use Root Explorer and zip the whole /efs folder onto your external sd card. (or wherever you want)
How about a method to restore the IMEI if you never had a good back up to begin with ?
Candanga said:
Please don’t ask how to recover your IMEI if you have previously messed your SGS without backing up this folder. I’m not familiar with such methods plus it is UNRELATED to this thread.
Click to expand...
Click to collapse
EarlZ said:
How about a method to restore the IMEI if you never had a good back up to begin with ?
Click to expand...
Click to collapse
How did you manage to miss that?
EarlZ said:
How about a method to restore the IMEI if you never had a good back up to begin with ?
Click to expand...
Click to collapse
had the feeling you would be here LMAO..
funny thing
the other day i messed up nv_data.bak trying to get my old product code back
the phone would not recognise the sim card
i deleted the whole /efs folder and the phone made a new one
i got my imei but no product code
sim card started working everything looked ok appart from sgs tools reporting nothing as phone !?!
i did restore /efs from a backup i had and then my product code came back
weird though
I was on jpo when all this happened
pele78 said:
had the feeling you would be here LMAO..
Click to expand...
Click to collapse
I guess you find it entertaining if people messed up their IMEI, well we all have our kinkiness.
EarlZ said:
I guess you find it entertaining if people messed up their IMEI, well we all have our kinkiness.
Click to expand...
Click to collapse
@EarlZ - I myself was a victim of this, but I managed to make a duplicate of my nv_data.bin as per instructions of the guide that I was following to unlock my SGS.
The only "tip" that I can give you (geez.. Im going against my own disclaimer lol ) is to try to flash it back to JM1 or the earliest release of your mobile. I think I remember to get my IMEI back doing this, but then lost it flashing to a newer ROM. AGAIN, my "research" didn't go past this as I managed to get my IMEI back, reason why I got inspired to throw this little guide.
Hope this can get you started on your IMEI recovery journey.
Cheers mate.
The restore should also be done with tar - in this way you won't lose the permissions on the files.
ingineru said:
The restore should also be done with tar - in this way you won't lose the permissions on the files.
Click to expand...
Click to collapse
Just for future reference (in case I need it ) can you give us the full command line?
Thanks
Thanks for the HowTo.
I ended up deleting my nv_data files in order to restore the backup files to get back the orig product code. As far as I can tell, it worked perfectly.
Code:
busybox rm -rf /efs/nv_data.bin
busybox rm -rf /efs/nv_data.bin.md5
In case you really boink your EFS
I wanted to add a small piece to this thread that not really consolidated anywhere I can fine. I toasted my /EFS yesterday - to the point of no cellular unless I was at JF6. I couldn't use tar because I'd get "out of room" errors and "numerical value out of range". I mean I SERIOUSLY borked the /EFS. But then I've been flashing this phone from the day it was available from AT&T.
I used ODIN to restore my /EFS. I have a permanent generic IMEI.
There are several good threads on backup of the /EFS, but not on restoring. If you follow the OP post to backup, here's a good discussion on how to restore.
http://forum.xda-developers.com/showthread.php?t=882039
What wasn't clear in Da_G's thread is the you don't have to use DD to use ODIN to restore. There's no discussion on using the .img file to restore. That's scattered across a couple of threads and lots of reading. I'm not a linux guy, so I had to figure this out. . . .
Deep in rotohammer's following thread, there is a discussion about using a cat .img file to do create an ODIN .rfs file that allows you to restore from ODIN.
http://forum.xda-developers.com/showthread.php?t=850359
So here's what I did to restore my /EFS to functional. You MUST have a backup of your functional /EFS using either dd or cat and ADB installed.
On your PC do the following:
c:\Android\tools> adb shell
$ su (you're now on your phones Android command line; watch your home screen on the phone in case Superuser comes up asking for permission)
#
Now we're going to take the efs_folder_backup_stl3.img that you did with the cat file and make it usable by ODIN. Change directory locations to your cat .img location. Mine is on /sdcard/external_sd/.
#cd /sdcard/external_sd/
#busybox cat efs_folder_backup_stl3.img > /sdcard/efs.rfs (this is the key step!!)
# cd /sdcard
# tar -cf efs.tar efs.rfs
# exit
$ exit
Now your back at your PC. Do the following step to get the .tar file off your phone.
c:\Android\tools> adb pull /sdcard/efs.tar
Almost done. Move the efs.tar file to the same direction as ODIN and the follow the last directions in Da_G's thread. I'll post them below for just for clarity.
"Now, get into download mode, open odin, stick efs.tar in PDA slot, and press start. Bam! EFS fixed"
This worked for me, several times. Once you have the /EFS directory in ODIN flashable tar format - you really have to work hard to brick your phone.
Hope this helps!
If I flash back to stock using ODIN, would that also put things back to right ?
@bsc7080xsc
It should. You might have to do a factory reset if the device shows as locked, but otherwise it's worked for me many times.
Hi
backedup my efs folder through this thread in combination with roto.
cellgeek in your post you say : " busybox cat efs_folder_backup_stl3.img > /sdcard/efs.rfs (this is the key step!!)"
But i never made an .img file/folder.
both the dd and cat created an rfs file which i turned to tar.
am i missing a step?
thank you for your little extra guide.
that's a very useful Candanga
several times saved my ass
thanks !
Thank you VERY much OP, that worked for me
Sorry to revive if this is old;
Why won't rm -rf /efs/nv_data.bin.md5 work in terminal? It gives me an error along the lines of this is a read-only file etc?
geesamsungs said:
Sorry to revive if this is old;
Why won't rm -rf /efs/nv_data.bin.md5 work in terminal? It gives me an error along the lines of this is a read-only file etc?
Click to expand...
Click to collapse
Try "busybox rm -rf /efs/nv_data.bin.md5"
Thanks that was very useful but I have a problem here.
When I copy my nv_data.bin file to efs directory I can only change the ownership but not the group!
I tried both of this:
su
busybox chown 1001:1001 /efs/nv_data.bin or
chown 1001:1001 /efs/nv_data.bin
Click to expand...
Click to collapse
and
su
busybox chown radio:radio /efs/nv_data.bin or
chown radio:radio /efs/nv_data.bin
Click to expand...
Click to collapse
Hello guys.
Once again I need your help.
Following my last thread:
http://forum.xda-developers.com/showthread.php?t=847320
(AKA "Help! no SD recognition, USB link doesn't work and no signal!")
After taking martijn_bakker's and ianmufc's advice regarding how to issue the correct command from fastboot:
- My phone regained sd functionality.
- My phone had proper signal again.
- BUT I still have USB issues, AND more:
I am currently running Cyanogenmod 6.1.1 for HTC Desire, and I have the following issues:
- When I try to go back to the stock Froyo, or anything that resembles it really (LeeDroid for example), my signal goes bananas: When I try to call anyone, it rings the person, then "ends" the call, only to bring it back again after a few seconds and then disconnect again.
I've also tried different radios (including the one LeeDroid recommended) to no avail.
So basically I cannot make calls with the original ROM.
- USB: When I connect my phone to my PC it charges it, BUT my PC doesn't recognize it, and I cannot transfer files between the SD card and the PC, or sync etc.
- I've got no Bluetooth! (Not sure if this is a Cyanogenmod issue or not though)
- Phone turns off when released from electricity charging (Doesn't happen with PC USB charging though).
The thing is I really didn't mind the original Froyo 2.2 ROM, infact I like it very much. I really like the HTC Sense features and the weather+clock widget with the animations.
The only reason I ever rooted my phone was to get apps2sd on it, so I don't keep running out of space when installing new apps. But I never even got that to work...
My question to you guys is how can I fix my current problems and have a properly working HTC Desire with a stock/custom Froyo ROM (that can make phone calls ) with apps2sd on it?
Thanks in advance!
Liran
First how have you been getting stock on your phone? Have you tried the ruu? If you are zip flashing have you wiped everything? Go to recovery wipe data/factory reset, wipe cache, advanced then wipe dalvik cache, back button, mounts then wipe everything except sd-card. Make sure you wipe sdext. Then try to flash.
Sent from my HTC Desire using Tapatalk
Well as you still don't have usb-connectivity, it sounds like you need to continue on the usb-brick fix. You have issued the command, which let you use the sd-card again. Now you just need to write a new misc partition as described here:
http://forum.xda-developers.com/showthread.php?t=691639
Doing this should make your phone work like it used to, as this is the only thing that is not fixable by flashing another rom if you need some help on it, i might be able to help, but in short terms, you need to flash a misc image, which have the right values, as the one on your phone have been changed in some way. The image is provided in the thread.
edit: and for god's sake do not try to run a ruu, as flashing the misc image might require root, and you may not be able to regain root without usb-connectivity. Also an ruu does not overwrite the misc partition, so it won't help your problem.
edit2: also you should try flashing a new radio that is known to work like 5.09.05.30_2 just to make sure this isn't also causing problems. It should be possible from a zip file using recovery.
_Dennis_ said:
First how have you been getting stock on your phone? Have you tried the ruu? If you are zip flashing have you wiped everything? Go to recovery wipe data/factory reset, wipe cache, advanced then wipe dalvik cache, back button, mounts then wipe everything except sd-card. Make sure you wipe sdext. Then try to flash.
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
TBH I don't exactly know what RUU is. I've heard it before but I'm not sure exactly what it means.
When I said I flashed the stock Froyo I meant this: Official_FroYo_2.10.405.2
and I also tried LeeDrOiD_v2.2f_A2SD.
Regarding the wipes I've done everything you wrote above to no avail.
mortenmhp said:
Well as you still don't have usb-connectivity, it sounds like you need to continue on the usb-brick fix. You have issued the command, which let you use the sd-card again. Now you just need to write a new misc partition as described here:
http://forum.xda-developers.com/showthread.php?t=691639
Doing this should make your phone work like it used to, as this is the only thing that is not fixable by flashing another rom if you need some help on it, i might be able to help, but in short terms, you need to flash a misc image, which have the right values, as the one on your phone have been changed in some way. The image is provided in the thread.
edit: and for god's sake do not try to run a ruu, as flashing the misc image might require root, and you may not be able to regain root without usb-connectivity. Also an ruu does not overwrite the misc partition, so it won't help your problem.
Click to expand...
Click to collapse
Thanks mate I will try that.
One thing I forgot to mention though - My phone is S-ON.
I'm not sure if it used to be S-OFF or not though.
Does that make any difference or does it not matter?
Hum. I appologize I never had a USB brick (knock in wood) so I assumed his problem would be in the rom possibly something he did while fixing the USB brick.
Sent from my HTC Desire using Tapatalk
It does make a difference yes, but you doesn't need s-off for this. It would just make it a whole lot easier. But just get your CID like described in the thread and change the misc image to this. Then flash it like described
edit:
dennis: np something else is wrong as well, but fixing the usb is very urgent, and the other problem should be fixable by running a ruu or simply flashing a new radio+rom afterwards.
mortenmhp said:
It does make a difference yes, but you doesn't need s-off for this. It would just make it a whole lot easier. But just get your CID like described in the thread and change the misc image to this. Then flash it like described
Click to expand...
Click to collapse
Will do!
I'll update when I'm done
liranh said:
Will do!
I'll update when I'm done
Click to expand...
Click to collapse
A bit stuck... Here is what I've done:
1. Got the CID.
2. Got a hex editor. wrote the new CID instead of the one in the img file. Saved it.
3. I put the new img file and flash_image.zip in the /data on my sd card.
I Put the card in my phone, started my phone, opened Terminal Emulator and typed in "/data/flash_image misc /data/mtd0.img" (without the quotes of course). the phone said: "/data/flash_image: not found".
What am I doing wrong?
Well you should not have a /data folder on your sd card it is a partition on the phone. In order to put it there, save the 2 files in the root of the sd-card and issue those commands in a terminal emulator:
cat /sdcard/flash_image > /data/flash_image
cat /sdcard/mtd0.img > /data/mtd0.img
As written in the thread, you might have to do 'chmod u+x /data/flash_image' before you run the commands (or chmod 755 /data/flash_image) but try to do it without those
Then you should be able to run the command you specified in the previous post
Edit: and the reason you got the error before was of course, that your files was in /sdcard/data and not in /data
liranh said:
A bit stuck... Here is what I've done:
1. Got the CID.
2. Got a hex editor. wrote the new CID instead of the one in the img file. Saved it.
3. I put the new img file and flash_image.zip in the /data on my sd card.
I Put the card in my phone, started my phone, opened Terminal Emulator and typed in "/data/flash_image misc /data/mtd0.img" (without the quotes of course). the phone said: "/data/flash_image: not found".
What am I doing wrong?
Click to expand...
Click to collapse
Actually, should it not be like this:
su
cat /sdcard/flash_image > /data/flash_image
cat /sdcard/mtd0.img > /data/mtd0.img
chmod 755 /data/flash_image
/data/flash_image misc /data/mtd0.img
Reboot.
Masdroid: Yes exactly apart from that he apparently didn't have the files on the sdcard root
MasDroid said:
Actually, should it not be like this:
su
cat /sdcard/flash_image > /data/flash_image
cat /sdcard/mtd0.img > /data/mtd0.img
chmod 755 /data/flash_image
/data/flash_image misc /data/mtd0.img
Reboot.
Click to expand...
Click to collapse
mortenmhp said:
Well you should not have a /data folder on your sd card it is a partition on the phone. In order to put it there, save the 2 files in the root of the sd-card and issue those commands in a terminal emulator:
cat /sdcard/flash_image > /data/flash_image
cat /sdcard/mtd0.img > /data/mtd0.img
As written in the thread, you might have to do 'chmod u+x /data/flash_image' before you run the commands (or chmod 755 /data/flash_image) but try to do it without those
Then you should be able to run the command you specified in the previous post
Edit: and the reason you got the error before was of course, that your files was in /sdcard/data and not in /data
Click to expand...
Click to collapse
Using a file manager on my phone, I put both files on the root of my SD card.
I then issued the following commands using Terminal Emulator:
su
(granted)
cat /sdcard/flash_image > /data/flash_image
Phone says: /sdcard/flash_image: No such file or directory
I should mention that I took out the card and connected it to my PC again to confirm the files have actually gone onto the root of the SD card (and they have), put the SD card back in my phone, issued the same commands in Terminal Emulator and got the same message...
Any ideas?
Sounds strange, just to make sure. You have unzipped the flash_image, so that it is not the flash_image.zip you have on you sd-card.
Also run "ls /sdcard" in terminal emulator to see a list of the files in the root and check, that it's there, and do not have a file extension. If it's there and the name is "flash_image" then it should work.
mortenmhp said:
Sounds strange, just to make sure. You have unzipped the flash_image, so that it is not the flash_image.zip you have on you sd-card.
Also run "ls /sdcard" in terminal emulator to see a list of the files in the root and check, that it's there, and do not have a file extension. If it's there and the name is "flash_image" then it should work.
Click to expand...
Click to collapse
Mate you are spot on with your first sentence. Give me a minute
Haha nice one thought i could've made the same mistake
mortenmhp said:
Haha nice one thought i could've made the same mistake
Click to expand...
Click to collapse
Yeah cause you know how when you put files on your phone to flash them you usually keep them in their zip format - that's what tricked me...
Haha yea let us know if you get it sorted
mortenmhp said:
Haha nice one thought i could've made the same mistake
Click to expand...
Click to collapse
Well spotted
mortenmhp and MasDroid thank you both so much!
Everything is working perfectly now!
I thought I would never get my phone to work properly again!
If any of you is ever in London - drinks are on me!
Hi there,
i'm actually trying to do the wimax backup found here:
http://forum.xda-developers.com/showthread.php?t=887900
I went through all of this trouble trying to install busybox until I found out that Titanium backup already installed 1.16 on my phone. However I can't seem to find where it was installed to and the,
busybox sed -n '/BEGIN CERTIFICATE/,$p' /dev/mtd/mtd0 > /sdcard/rsa_OEM.key
command isn't working. Any thoughts? Sorry if this is the wrong spot to post. I'm still getting the hang of this forum.
I have the same problem. I think I'm getting this error in the terminal emulator because I don't have the system Busybox installed, just Titanium's app busybox, which is apparently different?. When I try to run Busybox installer, it errors saying I'm possibly not nand unlocked... I used UR3 and UR forever, and can confirm that I am S-Off. Doesn't S-Off = nand-unlock?
I haven't played too much with busybox to know much of its capabilities, but if you want to know the directory it is located in, run this from Terminal Emulator, or adb.
find -iname "*busybox*"
that will get you any and all file listings with busybox in it.
says denied, so I typed su, and get the #
then I type the find command, and tells me that 'find' is not found.
topdawgn8 said:
I haven't played too much with busybox to know much of its capabilities, but if you want to know the directory it is located in, run this from Terminal Emulator, or adb.
find -iname "*busybox*"
that will get you any and all file listings with busybox in it.
Click to expand...
Click to collapse
greyopaque said:
says denied, so I typed su, and get the #
then I type the find command, and tells me that 'find' is not found.
Click to expand...
Click to collapse
you should be able to run find without a hitch. I have had issues running a find while executing a remove, but find had always worked...
try remounting the system:
Code:
su
remount rw
find -iname "*busybox*"
Edit: I just ran find with only SU. What rom and kernel are you running? The only two things I can think of are:
1: The dev removed it from the rom
2: User error-- ensure the commands are lower case, there is a space where appropriate (denoted by ">")
Code:
find>-iname>"*busybox*"
The busy box that tb installs doesn't have all the commands. I had to install from the market to get all the commands.
Sent from my PC36100 using XDA App
its in system/bin most of the time but can be in different spots
Usually you can find busybox in /system/xbin
OMG... I feel stupid... I had install location set for SDCard. That's why busybox installer was failing. I changed it back to auto, and installed busybox, and now everything is working!
Don't waste your time with the rsa keys backup. You'll never be able to restore them.
Use the recovery (amon's 2.2.x) to make a backup of the entire wimax partition. Should the need arise, recovery will be easy. To date, i've yet to see instructions how to restore just the keys.
That's exactly what I did. Thanx!
gpz1100 said:
Don't waste your time with the rsa keys backup. You'll never be able to restore them.
Use the recovery (amon's 2.2.x) to make a backup of the entire wimax partition. Should the need arise, recovery will be easy. To date, i've yet to see instructions how to restore just the keys.
Click to expand...
Click to collapse
I've never used adb push or pull successfully. I'm trying to pull my CWM backups from the phone to mac. Im on 4.2.1, and CWM backups store in data/media/clockworkmod. No matter how I try [/data/media/clockworkmod/, etc.], I get terminal output of "remote object does not exist". I wonder if this is because it is not the sdcard, and it is protected? Do I need to mount as writable, and how would i issue the pull command in a shell (seems unlikely)? Anybody have any idea why i cannot get this to work?
bodh said:
I've never used adb push or pull successfully. I'm trying to pull my CWM backups from the phone to mac. Im on 4.2.1, and CWM backups store in data/media/clockworkmod. No matter how I try [/data/media/clockworkmod/, etc.], I get terminal output of "remote object does not exist". I wonder if this is because it is not the sdcard, and it is protected? Do I need to mount as writable, and how would i issue the pull command in a shell (seems unlikely)? Anybody have any idea why i cannot get this to work?
Click to expand...
Click to collapse
Since you are on 4.2, your CWM backups should be moved to /data/media/0.
Code:
[I]adb pull /sdcard/clockworkmod[/I]
^should work.
Alternatively,
Code:
adb pull /data/media/0/clockworkmod
^should work as well.
Old ones, yes. New ones will be in /data/media/clockworkmod
Sent from my Galaxy Nexus using xda premium
"Macintosh:3 x09177310519$ ./adb devices
List of devices attached
...002 device
Macintosh:3 x09177310519$ ./adb pull /data/media/0/2LatinImeGoogle.odex
remote object '/data/media/0/2LatinImeGoogle.odex' does not exist
Macintosh:3 x09177310519$ ./adb pull /sdcard/2LatinImeGoogle.odex
2890 KB/s (642672 bytes in 0.217s)
Macintosh:3 x09177310519$ "
I have a backup of my stock keyboard .odex on the sdcard. So why can i pull it from the directory sdcard, but not /data/media/0? This is the essence of my question, since the backups are in data/media.
SOLVED
So after browsing the CWM image thread, I've got a working solution, in case others need this:
./adb pull /mnt/shell/emulated/clockworkmod/
pull: building file list...
Finally, I've been waiting on this for a while.
Again, in case anyone else is looking for this, I've got a second solution: adbd insecure by chainfire.
bodh said:
So after browsing the CWM image thread, I've got a working solution, in case others need this:
./adb pull /mnt/shell/emulated/clockworkmod/
pull: building file list...
Finally, I've been waiting on this for a while.
Again, in case anyone else is looking for this, I've got a second solution: adbd insecure by chainfire.
Click to expand...
Click to collapse
Thanks man, just what i needed
bodh said:
So after browsing the CWM image thread, I've got a working solution, in case others need this:
./adb pull /mnt/shell/emulated/clockworkmod/
pull: building file list...
Finally, I've been waiting on this for a while.
Again, in case anyone else is looking for this, I've got a second solution: adbd insecure by chainfire.
Click to expand...
Click to collapse
Thanks,I'm it,but i dont know why cannot copy /data/media/clockworkmod?
bodh said:
So after browsing the CWM image thread, I've got a working solution, in case others need this:
./adb pull /mnt/shell/emulated/clockworkmod/
pull: building file list...
Finally, I've been waiting on this for a while.
Again, in case anyone else is looking for this, I've got a second solution: adbd insecure by chainfire.
Click to expand...
Click to collapse
Old but still helpful ! Thanks!
It worked for me using "adb pull /mnt/shell/emulated/clockworkmod/backup C:\nandroid"
bodh said:
./adb pull /mnt/shell/emulated/clockworkmod/
pull: building file list...
Click to expand...
Click to collapse
Still helpful! I wonder why the intuitive command does not work?! Something to do with permissions maybe?
Hey folks,
Last night I was editing a file located under "data/system/users/0/settings_ssaid.xml" and upon rebooting my phone, it's been stuck in a boot loop. I have an original copy saved in a different folder, but unable to access anything to replace it.
Is there any specific fastboot command I can run to swap the files (adb push, pull etc)? Only boot slot A is giving me an issue, and I was reading flashing system.img would be able to help, but I don't wanna do anything I'm unsure will wipe any of my data where I'd have to start over unless I've recovered some of that data first.
If I do have to flash any stock images, pls post the instructions for clarity.
Thanks in advance.
Assuming adb can actually access your device, while it's stuck in a boot loop (test this by running 'adb devices' and see if you receive a response)
You can run the following command to list all the files in your specific folder.
adb shell ls FILEPATH
Every file in your specific folder will be listed. You can then do the following to pull/push your file
adb pull FILEPATH
adb push FILENAME FILEPATH
Of course you need to place the file that you want to push in your ADB folder.
Mind though, that simply replacing your edited file with the backup might not solve your bootloop.
You can always look up available commands here
adb shell ls - Android ADB Shell Commands Manual
Morgrain said:
Assuming adb can actually access your device, while it's stuck in a boot loop (test this by running 'adb devices' and see if you receive a response)
Click to expand...
Click to collapse
Yes, I can access adb and my device while it's booting up, but once it reboots I lose connection. Unless I can interrupt the process I'd have to be very quick in my typing to copy files lol.
Even with the few seconds I have to type some commands to access the directory of the file I edited, I do get a permission denied error.
Would swapping to Slot B during boot allow me into the system, or even flashing the system.img file?
RetroTech07 said:
Yes, I can access adb and my device while it's booting up, but once it reboots I lose connection. Unless I can interrupt the process I'd have to be very quick in my typing to copy files lol.
Even with the few seconds I have to type some commands to access the directory of the file I edited, I do get a permission denied error.
Would swapping to Slot B during boot allow me into the system, or even flashing the system.img file?
Click to expand...
Click to collapse
No because your file is on /data.
The issue is that you can't push your file to /scard since (I guess) you can't even get beyond to the point where /sdcard is mounted.
So copying it from /sdcard will likely be too late in the boot process.
Pushing directly into /data does not work either as you would have to be root. In the old days you could run and in root mode but I'm not sure that is still possible.
Factory reset will work.
On devices with separate recovery partition it would be possible to change recovery to allow adb access to /data so then push old file via recovery... But I would not know how to do that on Pixel as recovery is s part of the boot partition.
So effectively, it's likely you're only solution is to do a full firmware flash along with wipe.
I would first try a full flash removing the -w to avoid the wipe. It may work.
TonikJDK said:
I would first try a full flash adding the -w to avoid the wipe. It may work.
Click to expand...
Click to collapse
Probably a typo, but I think you meant you need to "remove" the -w to avoid a wipe.
Lughnasadh said:
Probably a typo, but I think you meant you need to "remove" the -w to avoid a wipe.
Click to expand...
Click to collapse
Thank you! My post is fixed.
TonikJDK said:
I would first try a full flash removing the -w to avoid the wipe. It may work.
Click to expand...
Click to collapse
Ok, I'm rooted so to be sure I don't mess anything up, lol can you list the steps just as a precaution?
Obviously I'd be in fastboot / recovery mode, then perform a flash-all but remove the -w so as to not erase my data?
Once the system boots, all of my texts and setup should remain as is, or do I have to go and recover it?
Would I be able to install the OS again on the inactive slot to recover data, or does that not work that way?
RetroTech07 said:
Would I be able to install the OS again on the inactive slot to recover data, or does that not work that way?
Click to expand...
Click to collapse
Nope ... there is only 1 data partition, so even when you flash the OS to the inactive slot, it would still use the same data partition. Moreover, it is then likely to upgrade/convert some files on /data which might result in not being able to go to the previous version in the old slot.
RetroTech07 said:
Ok, I'm rooted so to be sure I don't mess anything up, lol can you list the steps just as a precaution?
Click to expand...
Click to collapse
See https://forum.xda-developers.com/t/...thout-wiping-data-and-retaining-root.4356065/
so, unfortunately doing a full flash without wiping data didn't work. I'm almost inclined to believe that if TWRP was available for the P6/P, that I could go and push the file I had saved back into the directory of where it was and save myself from this mess.
I'm kicking myself because I'm usually backing up my data before I modify any system files, but this one time I hadn't done so and I had Google's backup turned off at the time, so I'm gonna have to lose some text messages over the last few days with some folks I enjoy speaking to. I do have some saved from late last week, but nothing from the weekend up until now.
As you said you can access ADB while booting, why not push/remove/replace the file while booting, even if this takes multiple boots to perform all commands, it should work assuming you can also use SU, if you can't, none of the below will work.
Code:
adb push <backup file location> /sdcard
adb shell
su
rm data/system/users/0/settings_ssaid.xml
cp /sdcard/settings_ssaid.xml /data/system/users/0/
chmod 600 data/system/users/0/settings_ssaid.xml
I don't know why it's affecting your boot though, there's a .fallback file that the system should fall back to when the system notes that this file is corrupt.
If the above doesn't work, and you could try:
Code:
adb shell
su
rm data/system/users/0/settings_ssaid.xml
cp /data/system/users/0/settings_ssaid.xml.fallback /data/system/users/0/settings_ssaid.xml
If that doesn't work, try:
Code:
adb shell
su
rm data/system/users/0/settings_ssaid.xml
And reboot, but again, I don't know why you're bootlooping from this, that file shouldn't be integral to booting.
Also, if you need to back up your data, why not just boot to boot_b, if it's not causing you issues? You really shouldn't have to reset your device to fix one problem - you could do a /data & /sdcard pull while booted to boot_b, or just run something like Titanium & SMS backup/restore.
DanielF50 said:
As you said you can access ADB while booting, why not push/remove/replace the file while booting, even if this takes multiple boots to perform all commands, it should work assuming you can also use SU, if you can't, none of the below will work.
Code:
adb push <backup file location> /sdcard
adb shell
su
rm data/system/users/0/settings_ssaid.xml
cp /sdcard/settings_ssaid.xml /data/system/users/0/
chmod 600 data/system/users/0/settings_ssaid.xml
I don't know why it's affecting your boot though, there's a .fallback file that the system should fall back to when the system notes that this file is corrupt.
If the above doesn't work, and you could try:
Code:
adb shell
su
rm data/system/users/0/settings_ssaid.xml
cp /data/system/users/0/settings_ssaid.xml.fallback /data/system/users/0/settings_ssaid.xml
If that doesn't work, try:
Code:
adb shell
su
rm data/system/users/0/settings_ssaid.xml
And reboot, but again, I don't know why you're bootlooping from this, that file shouldn't be integral to booting.
Also, if you need to back up your data, why not just boot to boot_b, if it's not causing you issues? You really shouldn't have to reset your device to fix one problem - you could do a /data & /sdcard pull while booted to boot_b, or just run something like Titanium & SMS backup/restore.
Click to expand...
Click to collapse
I appreciate the help but I can't go back as I've already wiped everything minutes before you sent this. If I had the above commands sooner I would have loved to try, although I'm not really sure why this became an issue in the first place. I tried booting to slot B, using both patched and normal boot images but it wasn't working, unless I did something wrong.
All I remember is installing an app to edit UDID for individual apps that I've used in the past, but because it wasn't identifying root properly, to which I'm assuming is an Android 12 issue, I decided to follow instructions for manually editing such IDs in the file I edited in my OP.
After I rebooted, I remember the main system about to start and seeing the Google boot logo with a percentage # go all the way up to 90%, then that's where the boot loop started. My guess at this point is either the app or the file I edited caused an issue, because I did nothing else up until that point. What's odd, is that after I formatted the whole system and rebooted, I saw the same percentage appear on screen after installing the same app to see if that was the issue, but it booted fully just fine.
I was going to just keep fighting this and keep the phone the way it was until I could maybe fix everything, but figured there's nothing I could do at this point since trying a flash of everything failed. I was up until 5am last night and it's almost 4 am with me trying to fix this. I feel defeated and upset because I don't believe I had to wipe this in the first place, and could have likely saved all of my data. I didn't have Google's backup option turned on and hadn't backed up my text messages because I was dumb. I'm more upset with myself than the phone honestly.
RetroTech07 said:
I appreciate the help but I can't go back as I've already wiped everything minutes before you sent this. If I had the above commands sooner I would have loved to try, although I'm not really sure why this became an issue in the first place. I tried booting to slot B, using both patched and normal boot images but it wasn't working, unless I did something wrong.
All I remember is installing an app to edit UDID for individual apps that I've used in the past, but because it wasn't identifying root properly, to which I'm assuming is an Android 12 issue, I decided to follow instructions for manually editing such IDs in the file I edited in my OP.
After I rebooted, I remember the main system about to start and seeing the Google boot logo with a percentage # go all the way up to 90%, then that's where the boot loop started. My guess at this point is either the app or the file I edited caused an issue, because I did nothing else up until that point. What's odd, is that after I formatted the whole system and rebooted, I saw the same percentage appear on screen after installing the same app to see if that was the issue, but it booted fully just fine.
I was going to just keep fighting this and keep the phone the way it was until I could maybe fix everything, but figured there's nothing I could do at this point since trying a flash of everything failed. I was up until 5am last night and it's almost 4 am with me trying to fix this. I feel defeated and upset because I don't believe I had to wipe this in the first place, and could have likely saved all of my data. I didn't have Google's backup option turned on and hadn't backed up my text messages because I was dumb. I'm more upset with myself than the phone honestly.
Click to expand...
Click to collapse
Ah damn, I was too late!
The 90% thing sounds like the November Google Play services updated - mine updated yesterday and I got the same thing when I rebooted, maybe something between the two got corrupt.
Yeah, I get that, I've had more than my fair share of self inflicted (and not so self inflicted) problems that have lost me data but you live and you learn I suppose