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!
Ok, after using my phone for a while i decided to root it. Since I have the stock Gingerbread rom i followed the guide to downgrade to the stock froyo rom. http://forum.xda-developers.com/showthread.php?t=1178912
I reached the part Temp-Rooting to Backup However, when i run titanium backup it says Error: Sorry, I could not acquire root privileges. This application will *not* work.
What am I supposed to do? I followed the guide to the letter and everything up till that point was exactly as the guide said.
My phone's details are
Android version 2.3.3
Baseband version 12.56.60.25U_26.10.04.03_M
Kernel version 2.6.35.10-g7b95729
Software number 2.42.415.17
Here is what i did in adb
http://pastebin.com/jkxE55Yh
For some reason, new users are not allowed to post links in their replies. Nipqer, i redid all my steps and did what you told me.
here is the link of all what i did:
http://pastebin.com/Fze9uB33
First, thank you so much for linking a pastebin of what you've done, makes it so much easier to try help.
However I'd really like to see if there was any output after running 'adb shell /data/local/
tmp/fixsu.sh' so if you can get that ouput and post it, would be much appreciated.
You might have to run it from inside shell:
adb shell
cd /data/local/tmp
./fixsu.sh
-Nipqer
Thanks Nipqer and sorry for the late reply.
I did what you told me and this is what i got
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
# cd /data/local/tmp
cd /data/local/tmp
# ./fixsu.sh
./fixsu.sh
#
though i don't know if it helps with anything.
I just got confused because in the guide it says to install Titanium backup and backup my data. I have already done a manual backup myself but i figured doing a backup using Titanium backup will not hurt. I have used other programs like Root Checker Basic and it tells me that i don't have proper root access.
Can I just ignore this issue and go ahead with the downgrade? Or will there be some problems?
Thanks again in advance!
Hmm, it should give you root permissions after running fixsu.sh.
The lack of output shows it should've worked.
That part of the guide is entirely optional anyway, so If you already have what you want backed up, go ahead and downgrade.
-Nipqer
Nipqer said:
Hmm, it should give you root permissions after running fixsu.sh.
The lack of output shows it should've worked.
Click to expand...
Click to collapse
Well. fixsu.sh returned no error for me, too. But Titanium backup did not get root and trying to call "su", I got I/O error. And looking to dmesg, I seen corrupted file system.
After a bit of research I got the reason: rw remount succeeds, Linux thinks, that data are written to flash, but no data are written for real. Once data leave cache, they are lost and system "returns" to intact state.
I wrote a different fixsu.sh, which does not have this problem, but I am still failing to get root privileges, even with the latest Superuser+su. I got only a pop-up about refused root access. (But "su number_of_any_existing_uid" and then "su" in adb shell says says about permitted access.)
Here is my preliminary fixsu.sh:
Code:
#!/system/bin/sh
chmod 755 /data/local/tmp/busybox
chmod 4755 /data/local/tmp/su
/data/local/tmp/busybox cp -a /system/xbin /data/local/tmp/
mount -o bind /data/local/tmp/xbin /system/xbin
/data/local/tmp/busybox --install -s /system/xbin/
/system/bin/rm /system/xbin/su 2>/dev/null
/data/local/tmp/busybox cp -a /data/local/tmp/su /system/xbin/
/data/local/tmp/busybox cp -a /system/bin /data/local/tmp/
mount -o bind /data/local/tmp/bin /system/bin
/data/local/tmp/busybox cp -a /data/local/tmp/su /system/bin/
# /etc/* changes are needed only for some busybox utils, not for Superuser's su
/data/local/tmp/busybox cp -a /system/etc /data/local/tmp/
mount -o bind /data/local/tmp/etc /system/etc
/data/local/tmp/busybox echo "root::0:0:root:/data/local:/system/bin/sh" > /system/etc/passwd
chmod 0666 /system/etc/passwd
/data/local/tmp/busybox echo "root::0:0:root:/data/local:/system/bin/sh" > /system/etc/passwd
/data/local/tmp/busybox echo "root::0:" > /system/etc/group
chmod 0666 /system/etc/group
# Optional:
ln /data/local/tmp/busybox /data/local/tmp/xbin/busybox
And here is the code to recover "writable" state after reboot:
Code:
#!/system/bin/sh
mount -o bind /data/local/tmp/xbin /system/xbin
mount -o bind /data/local/tmp/bin /system/bin
mount -o bind /data/local/tmp/etc /system/etc
Unfortunately I can't tell you why it won't work. Might just be your partitions are too corrupted or something.
Have you tried a full power cycle (turn phone off, pull battery), it's helped other phones work in the past.
Otherwise I'd say just use adb to pull your entire /data dir, so you have everything saved and can mess round with trying to put it back in later.
-Nipqer
Nipqer said:
Unfortunately I can't tell you why it won't work. Might just be your partitions are too corrupted or something.
Have you tried a full power cycle (turn phone off, pull battery), it's helped other phones work in the past.
Click to expand...
Click to collapse
I tried to reboot without battery removal. Partition was "corrupted" before reboot and intact after reboot. I tried to write again. I again got corruption. And ffter reboot it was again byte-equal to the original system.img. It means, that not write actually happens. Linux kernel just assumes that data are written, but they are lost after leaving kernel cache.
Hopefully, Android mount command supports -o bind, so one can bind mount directories from /data and /system is seemingly writable then.
Nipqer said:
Otherwise I'd say just use adb to pull your entire /data dir, so you have everything saved and can mess round with trying to put it back in later.
Click to expand...
Click to collapse
I saved all mmcblk0p* before starting my experiments. It should be the most complete way to backup, but it does not easily allow partial restore.
utx said:
I saved all mmcblk0p* before starting my experiments. It should be the most complete way to backup, but it does not easily allow partial restore.
Click to expand...
Click to collapse
If you saved the data from the partitions, restoring would just be placing the apk in /data/app/ and then placing the data files back into /data/data/ - if you do it this way, you must run fix_permissions whether you saved it with or without preserving the permissions (owner, read/write/execute, et cetera). The app, when you put it on the different rom, will have a different UID (more than likely) than it did before and the data files permissions would be incorrectly set. Running fix_permissions should resolve that issue.
*EDIT*
I may of misunderstood what you meant by saving mmcblk0p*. How did you do this? At first I was thinking you just meant you did a tar backup of each partition, but after re-reading sounds more like you something like
Code:
# dd if=/dev/block/mmcblk0p# of=/sdcard/mmcblk0p#.img
Is that what you did? If so, are you trying to restore it by the same method?
Code:
# dd if=/sdcard/mmcblk0p#.img of=/dev/block/mmcblk0p#
If so, I'm not sure that would work properly… You might have to extract the data from it then copy it over to the partition...
I've had that problem after geting temp root. Titanium would say no root premissions. So I redid the steps after reboot...but I found the problem was that if you open titanium back up be for u root it will throw yu that msg so if yu have did that that's why so go back after you root in to applications and force close titanium and then reopen app then it shuld give you root premssions at least it worked for me but I still wasn't able to down grade and another thing are u using the gfree method kus that didn't work for me to get root... I had to use the freevo method to get temp root as gfree kept giving me errors after doing the adb coommands
sent from my Tmobile G2 Rush Vision
And if that dosnt work yu can use sdcard maid to back up your system apps n such or delete them ....
sent from my Tmobile G2 Rush Vision
Setherio said:
If you saved the data from the partitions, restoring would just be placing the apk in /data/app/ and then placing the data files back into /data/data/ - if you do it this way, you must run fix_permissions whether you saved it with or without preserving the permissions (owner, read/write/execute, et cetera). The app, when you put it on the different rom, will have a different UID (more than likely) than it did before and the data files permissions would be incorrectly set. Running fix_permissions should resolve that issue.
Click to expand...
Click to collapse
I am aware of this problem. But if one returns exactly equal /system as it was there before, the /data will need no change.
Setherio said:
I may of misunderstood what you meant by saving mmcblk0p*. How did you do this? At first I was thinking you just meant you did a tar backup of each partition, but after re-reading sounds more like you something like
Code:
# dd if=/dev/block/mmcblk0p# of=/sdcard/mmcblk0p#.img
Is that what you did? If so, are you trying to restore it by the same method?
Code:
# dd if=/sdcard/mmcblk0p#.img of=/dev/block/mmcblk0p#
If so, I'm not sure that would work properly… You might have to extract the data from it then copy it over to the partition...
Click to expand...
Click to collapse
It was just an abbreviation:
Code:
cd /dev/block
for PARTITION in mmcblk0p* ; do
dd if=/dev/block/$PARTITION of=/sdcard/$PARTITION.img
done
I guess, that the most straightforward way to restore that /data would be: First run
Code:
fsck mmcblk0p26.img
(on Linux machine) on that /data image (when you don't have root and custom recovery yet, you cannot backup /data in read-only mode, so the image is corrupted a bit for sure; if the fsck puts something to /lost+found, you can delete it after finishing of the rooting process). Then rename mmcblk0p26.img to userdata.img and add it to the PC10IMG.zip that restores stock system. Otherwise you will again fight with "partition in use" problem when trying to restore.
I did not test this method, as I did not understand the partition layout that deeply before I root. But there is no reason why it would not work.
Hello everybody,
for quite a while i am reading several guide for rooting my desire z (android 2.3.3, not branded, USB debugging activated, Fast boot deactivated). In Germany most of the guides refer to Setherio's guide. So working with the source is as usual the best.
Unfortunately - even after 3 tries, with factory resets, rebooting, removing the battery, etc. - I cannot gain a temporary root. neither titanium backup nor MyBackUp Root gain access for making a backup. So I ended up here. I am not sure, if Sayedamir had the same problem. Nevertheless, I appreciate every help.
This is what I have done so far:
http://pastebin.com/NKD6D7Av
Furthermore, referring to Nipquer's 1st post, I executed fixsu as described with following results:
http://pastebin.com/0EQS0UnF
I am not sure, if I should proceed with the downgrading without having a backup and I guess, when the backup isn't working (lack of temporary root), the downgrading would not work anyway?!
Hi Vince683,
Yes I had exactly the same problem. I too followed Setherio's guide and after 2 attempts I still couldnt get temp root. I ended up not being able to back up any of my apps.
However i suggest you back up your messages and contact as that was the only stuff I could back up. there are alot of apps in the market that do that and i guess they dont need root.
If backing up your app data is that not important you can proceed with the downgrade. It worked in my case. I guess the only nuisance would be that you have to manually install and configure all yours apps again.
Tell us how it goes.
Perfect, it worked. Thank you for encouraging me
And Cyanogenmod 7.2 works fine.
Vince683 said:
Perfect, it worked. Thank you for encouraging me
And Cyanogenmod 7.2 works fine.
Click to expand...
Click to collapse
You're welcome
1. I ODIN BACK TO STOCK WITH ROOT
2. DOWNLOADED TERMINAL EMULATOR
FOLLOW DIRECTIONS IN LINK WORKED GREAT
I THOUGHT I F***ED MY DEVICE TIL I FOUND THIS
http://www.444android.com/samsung-g...xy-note-ii-factory-mode-sorunu.html#post86539
Excellent...
Thank you, this is sure to help other users...g
taylormade772 said:
1. I ODIN BACK TO STOCK WITH ROOT
2. DOWNLOADED TERMINAL EMULATOR
FOLLOW DIRECTIONS IN LINK WORKED GREAT
I THOUGHT I F***ED MY DEVICE TIL I FOUND THIS
http://www.444android.com/samsung-g...xy-note-ii-factory-mode-sorunu.html#post86539
Click to expand...
Click to collapse
I tried all the other methods and suggestions. Finally I tried this one and it worked. The post is in another language, but the code works. Don't worry if terminal tells you bla bla bla not found, just keep typing in the next code. When you reboot, factory mode will be a thing of the past.
how this gonna work ? mind helping me out ?
Did you try pulling the battery? How do you know if you're stuck in factory mode?
You want have lock screen and a small box with system info will be on display
sent from Notetorious B.I.G.
Holy crap finally I'm out of this DAMN factory mode.. Nothing else worked!
I got in there initially by trying to repair my EFS partition.
Thank you thank you thank you.
I really appreciate the help here. I had a i605 that had that annoying Factory Mode box because I messed up my EFS folder with Root Explorer. Now at least I have a baseband and 000000000's for my ESN. Much appreciative to the developers who share their knowledge with us.
FIX for getting out out of Factory Mode-Must be rooted
Might as well post the fix since it does work.
From terminal emulator or adb shell
su
rm /efs/FactoryApp/keystr
rm /efs/FactoryApp/factorymode
echo -n ON >> /efs/FactoryApp/keystr
echo -n ON >> /efs/FactoryApp/factorymode
chown 1000.1000 /efs/FactoryApp/keystr
chown 1000.1000 /efs/FactoryApp/factorymode
chmod 0744 /efs/FactoryApp/keystr
chmod 0744 /efs/FactoryApp/factorymode
reboot
Also located here, on XDA. What a coincidence
http://forum.xda-developers.com/showpost.php?p=42794146&postcount=1
To cut down on errors you can copy-paste these commands into the terminal emulator.
rangercaptain said:
To cut down on errors you can copy-paste these commands into the terminal emulator.
Click to expand...
Click to collapse
Excellent suggestion. Factory mode is an inconvenience, but repairable. Hosing up your /efs,4 and without a backup. Painful.
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
"Permission denied"
rangercaptain said:
To cut down on errors you can copy-paste these commands into the terminal emulator.
Click to expand...
Click to collapse
But how can i change permissions in the terminal. On every command is answering with "Permission denied"?
Tnx in advance for your answer.
zupanoski said:
But how can i change permissions in the terminal. On every command is answering with "Permission denied"?
Tnx in advance for your answer.
Click to expand...
Click to collapse
You need to be root. Type su, approve the root request when the message pops up.
If you phone is not rooted, then you need to root it.
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Unmodified factory images extracted from the Robin - Updated for Android 6.0.1 build 00WW_1_450 (released on 07 Oct 2016)
This is flashable zip, and it requires TWRP. Note that while the zip includes the boot.img, it doesn't include the recovery - so you can continue using TWRP if you've flashed it. If you wish to return to 100% stock, flash the included recovery.img file as well.
Download:
https://www.androidfilehost.com/f/Robin-Factory-Images
Note: If your Robin is currently unencrypted and you want it to remain that way, don't forget to flash the modified boot.img immediately after flashing the ROM, or else your device will become encrypted again.
Note:The official fastboot images can be found here: https://community.nextbit.com/t5/Tools/Nextbit-Robin-Factory-Images/m-p/10649
Disclaimer: The files and instructions provided herein are meant for users who understand and accept the risks of flashing firmware files. I will not be held responsible for any loss or damages that could occur as a result of following these instructions, downloading or flashing these files.
Good job @[deXter]! We'll get the official ones posted soon.
Thanks for posting that!
D
Nextbit_Khang said:
Good job @[deXter]! We'll get the official ones posted soon.
Click to expand...
Click to collapse
Any news Khang? Not to push, but I remember you saying your original plan was to get these out by the end of the month.
Hey @Nickamina - Foxconn is working with us, but it's been slow going. We don't have an ETA just yet, but are hoping soon we'll have the factory images available since people have been having trouble with the OTA (if they have TWRP installed).
the update zip is corrupt, i believe it so. thts why ppl keep getting error in update.
Nextbit_Khang said:
Hey @Nickamina - Foxconn is working with us, but it's been slow going. We don't have an ETA just yet, but are hoping soon we'll have the factory images available since people have been having trouble with the OTA (if they have TWRP installed).
Click to expand...
Click to collapse
i second that. did the update today. went to stock recovery. little robot and everything. got about 1/4 of the way and went to stock recovery menu. wiped data and cache thinking that it had finished the update. now i have a robin that won't boot. i did not wipe system, but the phone will not boot. any thoughts on how to get it back up and running? adb twrp and then flash stock image from this thread? any help would be appreciated.
@lordlittlebrooks yes, enter twrp and push the system image and mentioned above
D
Hi all,
I've uploaded the factory images for the new build 00WW1_19F (released on 29th March).
Please see the updated OP for full instructions.
So being a flashable zip in TWRP, would it be possible to just sideload? Or push and move to /cache/ since my data is encrypted? If so, just flash and wipe cache and I'll be golden then? Thanks!
Both sideloading and flashing from /cache should be possible, in theory. I'm currently running unencrypted so I can't confirm, so I would be interested to see what your results are.
[deXter] said:
Both sideloading and flashing from /cache should be possible, in theory. I'm currently running unencrypted so I can't confirm, so I would be interested to see what your results are.
Click to expand...
Click to collapse
Alright, well I'll do this when I get home then, seems like a more reliable way than unrooting and going back to stock to update!
The only thing that gets me is not being able to wipe dalvik through recovery though. Is it possible to wipe beforehand on terminal emulator, and then continue on through recovery by any chance?
PhlexPlexico said:
Is it possible to wipe beforehand on terminal emulator, and then continue on through recovery by any chance?
Click to expand...
Click to collapse
su
cd /data
rm -rf dalvik-cache
mkdir dalvik-cache
chmod 0771 dalvik-cache
Don't forget to reboot immediately, or else apps may start to crash and weird things will happen.
[deXter] said:
su
cd /data
rm -rf dalvik-cache
mkdir dalvik-cache
chmod 0771 dalvik-cache
Don't forget to reboot immediately, or else apps may start to crash and weird things will happen.
Click to expand...
Click to collapse
Would it be possible just to:
cd /data/dalvik-cache
rm -f *
Reboot
Could I do that since I won't have to mess with chmod as well? I mean, it's obviously no big deal but would this work too?
PhlexPlexico said:
Would it be possible just to:
cd /data/dalvik-cache
rm -f *
Reboot
Could I do that since I won't have to mess with chmod as well? I mean, it's obviously no big deal but would this work too?
Click to expand...
Click to collapse
No, because the dalvik-cache contains sub-folders.
You could rm -rf the sub-folders if you wanted to though, but that's just extra commands.
PhlexPlexico said:
Would it be possible just to:
cd /data/dalvik-cache
rm -f *
Reboot
Could I do that since I won't have to mess with chmod as well? I mean, it's obviously no big deal but would this work too?
Click to expand...
Click to collapse
I just tested this out in the terminal - you could cd to the dalvik-cache folder and run "rm -rf *". This will get rid of all the files and subfolders in the dalvik-cache folder, and you don't have to mess with the permissions.
[deXter] said:
I just tested this out in the terminal - you could cd to the dalvik-cache folder and run "rm -rf *". This will get rid of all the files and subfolders in the dalvik-cache folder, and you don't have to mess with the permissions.
Click to expand...
Click to collapse
Oh perfect! Thanks!
[deXter] said:
I just tested this out in the terminal - you could cd to the dalvik-cache folder and run "rm -rf *". This will get rid of all the files and subfolders in the dalvik-cache folder, and you don't have to mess with the permissions.
Click to expand...
Click to collapse
Sorry about the double post, but here's an update so far. Gonna try sideloading next but when I tried to move it to cache adb spat out an error stating: failed to copy 'update.zip' to '/cache//update.zip': No space left on device
So yeah, will try sideloading in a little bit here!
Alright! Went through sideload and so far success! Here's the steps that I did:
1) Get Terminal Emulator
1.a) su
1.b) cd /data/dalvik-cache/
1.c) rm -rf *
1.d) reboot recovery
2) Navigate to sideload feature (Advanced -> ADB Sideload)
3) On PC (got superSU back because I like my root)
Code:
G:\Users\XXXX\Downloads>adb sideload update.zip
Total xfer: 1.00x
G:\Users\XXXX\Downloads>adb sideload BETA-SuperSU-v2.68-20160228150503.zip
Total xfer: 1.56x
G:\Users\XXXX\Downloads>
Afterwards, wiped cache from recovery, and rebooted! Now just optimizing apps! May install xposed here after all is said and done, but seems to be golden! Thanks Dexter! You may have to teach me how to create some of these update zips!
Sorry, dumb question that everyone hates. I'm currently rooted, unencrypted with TWRP installed: is it possible to just dirty flash over the top of my current ROM and not lose my system data without losing everything and then flash the no-encryption zip?
Thanks a lot.
mnp said:
Sorry, dumb question that everyone hates. I'm currently rooted, unencrypted with TWRP installed: is it possible to just dirty flash over the top of my current ROM and not lose my system data without losing everything and then flash the no-encryption zip?
Thanks a lot.
Click to expand...
Click to collapse
Yep you can dirty flash. Just make sure you flash the no-encryption mod, followed by supersu immediately after (in that order).