Database Users

cross device link ERROR!!!!

I have looked and looked but im still having problems. im trying to use a mv /sdcard Camera.apk /system/app/ command to try to move a modded Camera.apk to the /system/app/ folder , but i keep getting a cross-device link. ive mounted it over again but still the same thing. Please help if this is even possible. thanks

Bump bump bump

I don't even know why I"m answering but ...
/system is not writable
unless you use something like this :
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
Please people please use the search fonction.

dixxa said:
I don't even know why I"m answering but ...
/system is not writable
unless you use something like this :
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
Please people please use the search fonction.
Click to expand...
Click to collapse
I have done that command several times both to /system and to /sdcard. But asoon as i do mv /sdcard/(file) /system/app/ it gives me that error!!!!!!

Any solutions to this?

move it using root explorer or some file manager that allows you to write in the system... thats what i do...

barger01 said:
I have looked and looked but im still having problems. im trying to use a mv /sdcard Camera.apk /system/app/ command to try to move a modded Camera.apk to the /system/app/ folder , but i keep getting a cross-device link. ive mounted it over again but still the same thing. Please help if this is even possible. thanks
Click to expand...
Click to collapse
It means that you can't create a hard link on one device (filesystem) that refers to a file on a different filesystem.
The mv command does NOT MOVE THE DATA!!! It moves the HARDLINK TO THE DATA.
Consider yourself fortunate that you have a SANE VERSION of the mv command that doesn't try anyway -- some old versions will actually TRY to do this, which will result in a hard link that points to NOTHING, and the original data being INACCESSIBLE.
If you want to move the file to a different filesystem, you need to use the "cp" command. Copy the file to create a SECOND COPY of it on a different filesystem, and then DELETE the OLD one with the "rm" command.
A simple move command:
Code:
#!/bin/bash
if ( cp "$1" "$2" ); then
rm -f "$1"
fi
You will note that the "cp" command returns true or false depending on the successful completion of the copy, therefore the original will only be removed IF the file copied successfully.
This script can be copied into some place referenced by the PATH variable and set executable.

lbcoder said:
It means that you can't create a hard link on one device (filesystem) that refers to a file on a different filesystem.
The mv command does NOT MOVE THE DATA!!! It moves the HARDLINK TO THE DATA.
Consider yourself fortunate that you have a SANE VERSION of the mv command that doesn't try anyway -- some old versions will actually TRY to do this, which will result in a hard link that points to NOTHING, and the original data being INACCESSIBLE.
If you want to move the file to a different filesystem, you need to use the "cp" command. Copy the file to create a SECOND COPY of it on a different filesystem, and then DELETE the OLD one with the "rm" command.
A simple move command:
Code:
#!/bin/bash
if ( cp "$1" "$2" ); then
rm -f "$1"
fi
You will note that the "cp" command returns true or false depending on the successful completion of the copy, therefore the original will only be removed IF the file copied successfully.
This script can be copied into some place referenced by the PATH variable and set executable.
Click to expand...
Click to collapse
Maybe I'm reviving a dead thread, but lbcoder really deserved appreciation. I was stuck at the exact same issue with mv on my Moto Defy, and you saved the day. Thanks!

I agree - thank you lbcoder!

Just use dd if=/.... of=/.....

sony66 said:
Just use dd if=/.... of=/.....
Click to expand...
Click to collapse
dd never desapoints !
Thanks!

lbcoder said:
The mv command does NOT MOVE THE DATA!!! It moves the HARDLINK TO THE DATA.
Click to expand...
Click to collapse
Thanks! Useful even for some of us not-so-n00bs on Linux -- I never knew that.

I tried to copy and not move and ended up with the same error
Code:
:/data/sdext3/WhatsApp/ModsBackup/com.whatsapp #
cp files databases shared_prefs /data/data/com
cp: Skipped dir '/data/data/com.whatsapp/files': Cross-device link
cp: Skipped dir '/data/data/com.whatsapp/databases': Cross-device link
cp: Skipped dir '/data/data/com.whatsapp/shared_prefs': Cross-device link
apparently the advice given by one of our members was the one I found on stack exchange with the same wording
here
solution is not cp instead of mv because
mv hard links and across devices it is not possible.
the BusyBox version of copy worked for me to copy across different devices
it sounds like even cp from android shell behaves much like mv
Code:
busybox cp -rvf files databases shared_prefs targetdir

Unlock X10 idea...

Hi,
A friend of mine will get his X10 soon so i tried to find a way to unlock his phone.
Here is the idea:
Basicaly there is a way to unlock the Samsung Galaxy S and i'm wondering if we can apply the same idea on the X10.
WARNING: DON'T TRY UNLESS YOU KNOW WHAT I'M TALKING ABOUT (VERY DANGEROUS)
- Backup the /efs (just in case)
- copy the nv_data.bin in /sdcard
- transfer nv_data.bin to your computer
- edit the nv_data.bin with an hex editor
- go to the adress 0x181469
- change 0x01 to 0x00
0x01 mean locked
0x00 mean unlocked
- then remove nv_data.bin in efs and replace with the new one (don't forget the md5, chown and chmod)
----
Here are the commands once the nv_data.bin is done and back in /sdcard:
Code:
su
rm /efs/nv_data.bin
rm /efs/nv_data.bin.md5
cat /sdcard/nv_data.bin >> /efs/nv_data.bin
chmod 755 /efs/nv_data.bin
chown radio.radio /efs/nv_data.bin || chown 1001.1001 /efs/nv_data.bin
reboot
So it's just a thought cause Android is Android... the lock system should be the same on any devices (the unlock code change but the way it's stored in the OS shoudn't)
Just few tips to make sure you won't screw your phone:
- to backup properly use:
Code:
busybox tar zcvf /sdcard/efs-backup.tar.gz /efs
and
Code:
cat /dev/block/stl3 > /sdcard/efs_dev-block-stl3.img
Trust me you when you play with the /efs you MUST have backups (and better have 2 or 3...)
I almost forgot all credits goes to the guys who found this on the Galaxy S... http://forum.xda-developers.com/showthread.php?t=761045

scoonydeus said:
Hi,
A friend of mine will get his X10 soon so i tried to find a way to unlock his phone.
Here is the idea:
Basicaly there is a way to unlock the Samsung Galaxy S and i'm wondering if we can apply the same idea on the X10.
WARNING: DON'T TRY UNLESS YOU KNOW WHAT I'M TALKING ABOUT (VERY DANGEROUS)
- Backup the /efs (just in case)
- copy the nv_data.bin in /sdcard
- transfer nv_data.bin to your computer
- edit the nv_data.bin with an hex editor
- go to the adress 0x181469
- change 0x01 to 0x00
0x01 mean locked
0x00 mean unlocked
- then remove nv_data.bin in efs and replace with the new one (don't forget the md5, chown and chmod)
----
Here are the commands once the nv_data.bin is done and back in /sdcard:
Code:
su
rm /efs/nv_data.bin
rm /efs/nv_data.bin.md5
cat /sdcard/nv_data.bin >> /efs/nv_data.bin
chmod 755 /efs/nv_data.bin
chown radio.radio /efs/nv_data.bin || chown 1001.1001 /efs/nv_data.bin
reboot
So it's just a thought cause Android is Android... the lock system should be the same on any devices (the unlock code change but the way it's stored in the OS shoudn't)
I almost forgot all credits goes to the guys who found this on the Galaxy S... http://forum.xda-developers.com/showthread.php?t=761045
Click to expand...
Click to collapse
Very interesting proposition. I hope someone with a locked phone can try it and report back.

Just few tips to make sure you won't screw your phone:
- to backup properly use:
Code:
busybox tar zcvf /sdcard/efs-backup.tar.gz /efs
and
Code:
cat /dev/block/stl3 > /sdcard/efs_dev-block-stl3.img
trust me you when you play with the /efs you MUST have backups (and better have 2 or 3...)
I add this to the main post...

I can try it at home.
if phone gets bricked, will the sony ericsson update unbrick it?

post it into x10 Android Development Forum

Will try it today
I am kinda disappointed with AT&T. I have an Xperia X10a for over three months now on an eight years account and they still refuse to provide me the unlock code. Online sites like Unlocking.com cannot find the code in their database.
I will do my best to try this today and will report back soon.
Thanks for the tip.
Karim Benayed

If you have any issue you just have to put the original nv_data.bin in /efs...

I have read somewhere that the galaxy S phones are easy to unlock because the unlock is based on the same partition of the android system, in the same site they stated that the X10 unlock is based on the radio portion, not accesible from the android itself.

Just done a search with RootExplorer and couldn't even find the nv_data.bin. My phone is already unlocked but thought I could have seen 0x00 to confirm.

hmmm
I don't have /efs actually. and can't find nv_data.bin on the phone.

XperiaX10iUser said:
Just done a search with RootExplorer and couldn't even find the nv_data.bin. My phone is already unlocked but thought I could have seen 0x00 to confirm.
Click to expand...
Click to collapse
+1. I did the same thing and could not find that file either!

didnt mean to cut in like this, but dose the OP have any idea that this method is for samsung SGS only?

Lancez said:
didnt mean to cut in like this, but dose the OP have any idea that this method is for samsung SGS only?
Click to expand...
Click to collapse
To be fair it was just an idea, but if we don't even have a nv_data.bin file then it's a flawed one.

XperiaX10iUser said:
To be fair it was just an idea, but if we don't even have a nv_data.bin file then it's a flawed one.
Click to expand...
Click to collapse
i have both SGS and X10a. i unlocked my SGS by this method a month ago and it worked like a charm. just because samsung wasn't aware that they have stored unlock code inside of that file. but it dose not work on newer SGS anymore.

benayed said:
I am kinda disappointed with AT&T. I have an Xperia X10a for over three months now on an eight years account and they still refuse to provide me the unlock code. Online sites like Unlocking.com cannot find the code in their database.
Click to expand...
Click to collapse
AT&T will not just give you the unlock code unless you manage to talk to a dumb representative, you have to give them a legit reason for them to provide you the unlock code. If you have had the phone for three months or longer you can the reason I always use, that I'm going on vacation to Canada or Mexico or any other country for two weeks or so and need the unlock code to use a sim card from that country. I have never had this reason fail but in case it does I suggest calling back until you find a representative who will provide the unlock code for this reason

Weak Flipout mobile network signal

I've debranded a UK Orange Flipout and unlocked to use on Vodafone UK.
The mobile signal is terribly weak and spends more time with no bars that with. It makes the phone useless as a phone however great the design is.
Sitting next to another android phone on the same network the bars are almost full on the other phone - when showing nothing on the Flipout.
Does anyone else have this problem? Is there something I can do to re-configure the phone and make it work as a phone? I've had all the data settings from Vodafone reset for MMS and data etc.
If no answer it will have to go back to stock ROM and back to the shop.
Thanks.

Hey, I got the same problem. Had me temporarily switch back to Milestone 'cause Flipout wasn't able to even connect to the service..no signal at all. I noticed that Flipout has slow network acquiration compare to Milestone. But, I have to point out that I flashed it from stock to UK ROM without BLUR so it's more likely possible that something just went wrong. For now I blame the basebands and try to solve it that way..somehow. let me know if any news
Sent from my Milestone using XDA App

ok, it was the baseband.. i changed it from what it was to this (attachment) and everything's fine.
you have to be rooted, and remount system as r/w
the original baseband files are located in /system/etc/motorola/bp_nvm_default
basically you need to replace this folder with the new one and set the same permissions as the original files had. i don't know if you know how so just for sure, here's the how-to
i suggest you doing this:
0]if you are not rooted, install Universal Androot and press Go Root, then reboot your phone
1]unrar the attachment to your phone's sdcard
2]boot up the phone, switch to airplane mode
3a]if you have Root Explorer, navigate to /system/etc and push remount as r/w
3b]if you don't have that, install Root Toolbox go to Mount-System Mount Options-Mount System R/W
4]fire up Terminal Emulator
5]enter those commands: (enter after each line)
Code:
su
cd /system/etc/motorola
cp -R /sdcard/bp_nvm_default bp_nvm_default_nw
cp -R bp_nvm_default /sdcard/bp_nvm_default_BACKUP
chmod 755 bp_nvm_default_nw
chown root.root bp_nvm_default_nw
cd bp_nvm_default_nw
chmod 644 *
chown root.root *
cd ..
rm -R bp_nvm_default
mv bp_nvm_default_nw bp_nvm_default
reboot
6]after the reboot, turn off flight mode, let the phone get registered to network and see what happens.. hope this will fix your problem.
it's a bit tricky, i actually had to reboot after mounting system to R/W and giving Superuser permissions and mount again because somehow it didn't work for the first time.. anyway, let me know if anything goes wrong

Thanks, that looks a bit technical but ill give it a go... thanks for info.
Sent from my Transformer TF101 using Tapatalk

Well I gave this a go - and I kept getting permission denied. sounds like problem you had with the system RW refusing to allow a copy.
Anyhow I am hoping I might have fixed it by using this link
http://dext3r.komodin.org/
And there is a radio file you can install under Quick FAQ with different country baseband radio files. Might help someone else ...

it didnt work
well, i did everything as written except i used ES File Manager to mount the /system as R/W and when it came to:
cp -R bp_nvm_default /sdcard/bp_nvm_default_BACKUP
it said "cp: can't create symlink '/sdcard....': Operation not permitted" for every file so i just did it manually with ES File Manager... that is only a backup anyway and shouldnt affect anything.
it just doesnt work.
and why cant i just drop the baseband files in there with copy and paste? that didnt work either.
i need baseband files for T-Mobile on the US network for the Flipout. does anyone have any others i could try?
thanks!

[SOLVED] Using Terminal Emulator to write to system

Not sure if this will help anyone else, but I searched forever trying to figure out how to write into the system folder using Terminal Emulator on the Note 3 to no avail. I found a slew of posts that said to type "mount -o rw,remount /system" to achieve this. When I used this command it didn't return any errors so I assumed it worked, however no files ended up being copied and pasted to the location I wanted. I found numerous other examples that were supposed to enable writing to the system as well, but none of them worked. I finally figured out how to get it to work on my Note 3 by typing "mount" in terminal emulator and noticing that at the very beginning of the string that was returned was "rootfs". So if you are wanting write to your system using Terminal Emulator on the VZW Note 3 here is what ended up working for me:
Code:
mount -o remount,rw rootfs
to return to read only enter:
Code:
mount -o remount,ro rootfs
I wanted to figure this out because a bug in TWRP v2.6.3.0 maimed my efs partition and bricklooped my phone. Even flashing the Stock Developer tar by Beans wouldn't bring it out of the brickloop. I was able to get out of the brickloop by following this thread, but even though my phone booted up and the IMEI # was correct, my /efs folder was missing in action. This caused odd things to happen like my lock screen not functioning and the power button instantly turning the phone off instead of bringing up the power menu. I discovered this was because the phone was placed into something called "factory mode" and that to fix it you needed to edit some files in the efs folder, which were completely missing on my device. Member js0uth graciously sent me his efs folder from his Developer Note 3 and when I copied it to my phone it began to function normally again (big shout out to js0uth!). However, this folder was completely deleted once again after a reboot. So now you can see why I was looking for a way to copy these files using Terminal Emulator. I ended up making a Tasker profile with the Secure Settings plugin that automatically copies the files from my ext SD card to my system folder on boot of the device. In order to mount, copy/paste the files while retaining the correct permissions from the folder that js0uth sent me, and unmount the system I had the set up my Secure Settings command as follows:
Code:
mount -o remount,rw rootfs;cp -Rpf /storage/extSdCard/efs/* /efs/;mount -o remount,ro rootfs
So now I have a livable workaround for my problem until I can discover a way for the phone to rebuild my own /efs folder.
Edit: See radionerd's post for a permanent fix to this issue and be sure to hit thanks under his name if it helps you.

I did the same to my DE. Corrupted EFS about a month ago after a few flashes using TWRP 2.6.3.0. Boot loops for 28 hours of hell until I followed your tracks to the trick that deleted my corrupted EFS folder, and created a new empty folder. I guess this would wipe out IMEI, Mac, and more in models that store phone specific data in EFS. We lucked out I've read that our phones have that info in a few other folder not EFS
Since wiping EFS I have run stock ROM, CM11, and now bean V6. I didn't see the factory mode popup until recently. I noticed that the screen will flash when leaving or entering cell service.
My corrupted EFS was 3MB. I'm curious what's the size of the EFS folder from js0uth?
Were you able to enter the factory mode on string? something like this?
Code:
# echo -n ON > /efs/FactoryApp/factorymode
this is from an S3
Thanks for documenting your steps to recovery.
radionerd

radionerd said:
My corrupted EFS was 3MB. I'm curious what's the size of the EFS folder from js0uth?
Click to expand...
Click to collapse
It's 1.04 MB. Sorry for taking so long to respond. I thought I had it set up to send instant emails for replies to this thread, but apparently I didn't.
radionerd said:
Were you able to enter the factory mode on string? something like this?
Code:
# echo -n ON > /efs/FactoryApp/factorymode
this is from an S3
Click to expand...
Click to collapse
Setting the Factorymode folder to ON is actually what disables that mode. Seems backwards I know, but when it's set to OFF (or if the folder is completely missing as in my case) that warning message will display. If that folder is intact on your phone then you should be able to use a string to disable or enable Factorymode.

It got worse before it got better
bodieism said:
It's 1.04 MB. Sorry for taking so long to respond. I thought I had it set up to send instant emails for replies to this thread, but apparently I didn't.
No worries, I went from an annoyance of no lock screen to bricked for over 6 weeks. This happened after trying to do an EFS backup.
I've learned a lot since back then, My DE is back 100%, EFS is repaired. I think we ran the same script which actually points to the wrong mount in our phones. It brought us out of bootloops, but efs was pointed to block12. Qualcom snapdragon Note-3's use mmblk0p11 to load /efs.
If you still have to load the tasker script, I think I figured out an easy fix to rebuild your original efs folder.
I would backup mounts first, delete /efs folder. Then run the original script, but this time change from 12 to 11.
Code:
adb shell
su
mke2fs /dev/block/mmcblk0p11
mkdir /efs
mount -t ext4 /dev/block/mmcblk0p11 /efs
Bet that would do the trick
Here is my thread
Click to expand...
Click to collapse

^ That did do the trick! :good:
Phone is back to 100% working order :highfive:

[Q] i337m Null imei and unknown baseband help

Hello
I have a Galaxy S4 i337m canadian model (firmware i337MVLUFNC1) that has unknown baseband and null imei.
WIfi and blutooth work. it does not recognize sim card.
I have been reading for two weeks about this problem and tried all the methods that i found on google.
I dont have efs backup.
I don't see the nv_data files in efs folder ( file manager =show hidden files enabled)
Any chance I can fix this phone without the original efs folder backup?
Thanks.

Twisteddd said:
Hello
I have a Galaxy S4 i337m canadian model (firmware i337MVLUFNC1) that has unknown baseband and null imei.
WIfi and blutooth work. it does not recognize sim card.
I have been reading for two weeks about this problem and tried all the methods that i found on google.
I dont have efs backup.
I don't see the nv_data files in efs folder ( file manager =show hidden files enabled)
Any chance I can fix this phone without the original efs folder backup?
Thanks.
Click to expand...
Click to collapse
Haven't done it on the gs4 but you'd have to be able to connect it to qpst
I've actually been looking around at this but haven't been able to find much most information is under backup gs3 imei.

Asadullah said:
Haven't done it on the gs4 but you'd have to be able to connect it to qpst
I've actually been looking around at this but haven't been able to find much most information is under backup gs3 imei.
Click to expand...
Click to collapse
Thanks for replay
But that is a way to explore the phone files?
I did a lot of research to find out if the efs file on this model s4 actually contains the .nv_data.bin at all? or it is somewhere else?
Do you know if these files are actually missing from efs folder on i337m? or they are stored somewhere else?
Thanks.

Tried the following method with no luck
http://forum.xda-developers.com/showthread.php?t=1852255

Twisteddd said:
Tried the following method with no luck
http://forum.xda-developers.com/showthread.php?t=1852255
Click to expand...
Click to collapse
Taking the device back to your carrier and letting them factory restore it your best option other then that you are limited without a backup.
You can try this method... if your rooted but there are no guarantees.
Do these commands from ADB from your PC.
adb shell
su
mke2fs -t ext4 /dev/block/mmcblk0p10
mount -w -t ext4 /dev/block/mmcblk0p10
reboot
On your S4, download the Android Terminal Emulator from the Play Store and enter the following commands.
su
echo -n ON > /efs/FactoryApp/factorymode
sync
exit
exit
Reboot into Recovery, and preform a Factory Reset.

NighthawkXL said:
Taking the device back to your carrier and letting them factory restore it your best option other then that you are limited without a backup.
You can try this method... if your rooted but there are no guarantees.
Do these commands from ADB from your PC.
adb shell
su
mke2fs -t ext4 /dev/block/mmcblk0p10
mount -w -t ext4 /dev/block/mmcblk0p10
reboot
On your S4, download the Android Terminal Emulator from the Play Store and enter the following commands.
su
echo -n ON > /efs/FactoryApp/factorymode
sync
exit
exit
Reboot into Recovery, and preform a Factory Reset.
Click to expand...
Click to collapse
Tried and gave me the following error in shell
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>adb shell
[email protected]:/ $ su
su
root[email protected]:/ # mke2fs -t ext4 /dev/block/mmcblk0p10
mke2fs -t ext4 /dev/block/mmcblk0p10
mke2fs: invalid option -- t
BusyBox v1.22.1-Stericson (2014-01-25 17:27:18 CET) multi-call binary.
Usage: mke2fs [-Fn] [-b BLK_SIZE] [-i INODE_RATIO] [-I INODE_SIZE] [-m RESERVED_
PERCENT] [-L LABEL] BLOCKDEV [KBYTES]
-b BLK_SIZE Block size, bytes
-F Force
-i RATIO Max number of files is filesystem_size / RATIO
-I BYTES Inode size (min 128)
-L LBL Volume label
-m PERCENT Percent of blocks to reserve for admin
-n Dry run
1|[email protected]:/ #

Twisteddd said:
Thanks for replay
But that is a way to explore the phone files?
Thanks.
Click to expand...
Click to collapse
Thats how people were re-writing / repairing their meids

Asadullah said:
Thats how people were re-writing / repairing their meids
Click to expand...
Click to collapse
I cant find anything for i337m
I don't have service menu either. it says service mode on top of the phone and nothing on the screen.
This phone has to be completely reformated even the system partition. There must be a way of rebuilding the whole phone software.

Twisteddd said:
I cant find anything for i337m
I don't have service menu either. it says service mode on top of the phone and nothing on the screen.
This phone has to be completely reformated even the system partition. There must be a way of rebuilding the whole phone software.
Click to expand...
Click to collapse
Yeah its a rough road ahead of you. I know it can be done because people advertise it on craigslist. But I don't know exactly how.
get on stock nb1 and dial *#0808# change usb settings to dm+modem+adb might get you on the right road.

Looks like they use service box like z3x
I am trying to find alternative ways to do this because where I live, nobody offers this sort of services

Twisteddd said:
Looks like they use service box like z3x
I am trying to find alternative ways to do this because where I live, nobody offers this sort of services
Click to expand...
Click to collapse
There's definitely a different way z3x is such a rip off. I don't know it but as I get time I'm looking around. I'm wondering if you can locate all of the spots that carry the imei if you can change them to something else.

Can some one tell me if the following z3x box sold on ebay enough for repairing baseband on my phone i337m? Or do I need to buy the smart card with it also?
http://m.ebay.ca/itm/151500466184?nav=SEARCH
I know i will need the uart micro usb.
Thanks.

Does null IMEI cause unknown baseband or unknown baseband causes null IMEI?
Which one should be fixed first?
Also the service mode (*#0011#) being blank is it because of the modem is not working?
Thatnks.

When I try qpst in windows 7 to connect to the phone in order to rewrite IMEI;
I can change usb setting to RMNET by dialling *#0808#, the device manager it installs two usb ports under ports. Com6 and com7
RMNET SAMSUNG network driver installs but cant be started. it shows a yellow caution sign on the driver. Restarting windows and phone does not fix it.
When I enter the com ports to qpst configuration, it says active but says no phone.
Any help is appreciated.