Database Develop

[Q] JP6 doesn't recognise my SIM card???

I have gotten myself into a mess and having upgraded to JP6 my SIM card is no longer recognised. Has anyone else had this issue and does anyone know of a Fix that they could give me to sort this mess out.
Thanks

james.boot said:
I have gotten myself into a mess and having upgraded to JP6 my SIM card is no longer recognised. Has anyone else had this issue and does anyone know of a Fix that they could give me to sort this mess out.
Thanks
Click to expand...
Click to collapse
Don't panic, this is easy to fix..
Do a reset, cache erase from recovery mode (Volume up + Home + Turn on).
Root the device, install busybox and run it, install andoid terminal emulator the execute the followings in terminal emulator:
- su
- busybox chown 1001:1001 /efs/nv_data.bin
- reboot
That is it.

EXCELLENT!,
When you say wipe the cache is that option called "wipe cache partition" and where can I download busybox from etc? Im a bit of a noob with the fixing my screw ups business.

james.boot said:
EXCELLENT!,
When you say wipe the cache is that option called "wipe cache partition" and where can I download busybox from etc? Im a bit of a noob with the fixing my screw ups business.
Click to expand...
Click to collapse
Yes "wipe cache partition".
Root using the program from here (if not rooted yet): http://forum.xda-developers.com/showthread.php?t=803682
Busy box and emulator from the market. run busy box and click install and wait till it installs then run emulator. You must choose allow when prompted in both programs.

Hi, did all of this, it would not accept the reboot command so I turned the phone off and on. I dont know if the reboot command is integral to solving the problem but it has not worked. Is there something else I need to do?
it says
---------------------------------------------------------------------------------------------------------------------------------
change the owner and/or group or each FILE to OWNER and/or GROUP
Options:
-R Recurse
-h affect symlinks instead of symlink targets
-L Traverse all symlinks to directories
-H Traverse symlinks on command line only
-P Dont traverse symlinks (default)
-c List changed files
-v List all files
-f hide errors
------------------------------------------------------------------------------------------------------------------------------------------------
What does this mean?

I don't think that you have executed the commands right, maybe because that I should have written them more clearly.
Execute in emulator:
su
(hit Enter)
Choose "Allow" and exit the program when done.
Start Emulator again and execute:
su
(hit Enter)
busybox chown 1001:1001 /efs/nv_data.bin
(hit Enter)
reboot
(hit Enter)
The phone will reboot and it will accept the card if the nv_data.bin staill intact. Try the steps above and I hope that every thing is right.

Unfortunately it has not worked. Have you got any more ideas? I appreciate your help with this.

james.boot said:
Unfortunately it has not worked. Have you got any more ideas? I appreciate your help with this.
Click to expand...
Click to collapse
Did the commands execute right, no errors?
If so then check the IMEI number: Click on Phone in the home screen as when you dial a number and dial *#06# see the number that comes off, is it your correct IMEI number?

There is no IMEI number there, which is slightly worrying haha
no errors either

james.boot said:
There is no IMEI number there, which is slightly worrying haha
Click to expand...
Click to collapse
in this case you might need to read here: http://forum.xda-developers.com/showthread.php?t=780509
It might be that the nv_data.bin file in your mobile is damaged, I'm only saying that it might be that, the only way to know for sure is to check the IMEI number in the phone under "Settings"--> "About phone" --> "Status" if there is no IMEI number then a reflash might correct that, if the IMEI number is like 000044...etc then the nv_data.bin file is damaged and can only be corrected if you have backed up the /efs folder. Please read in the linked thread to find out before doing anything.

I had this problem. I just reset my phone. When it rebooted it installed Sim Toolkit and now it works fine & reconises the Sim. Do you have Sim Toolkit installed?

I had this exact problem spent 2 hours trying fixes etc, I had my SIM card in the wrong way around, I was so used to putting it in like my old phone i did not notice the little picture saying the way to put it haha I had taken it out to flash a new ROM and assumed it was the ROMS fault cause it stopped working

no mate it doesn't. Just done a quick factory reset without success.

newb help please... help with adb copying files.... no permissions??

Sorry... newb question... can not figure out this deal...
Trying to copy the jupiter files to my phone... can not.
I dont have permissions... how can I get permissions opened up?
Below is some of what I am getting in regards to errors -
C:\Documents and Settings\Kevin\My Documents\Downloads\android-sdk_r07-windows\a
ndroid-sdk-windows\tools>adb push jupiter.xml /system/etc/jupiter.xml
failed to copy 'jupiter.xml' to '/system/etc/jupiter.xml': Permission denied
C:\Documents and Settings\Kevin\My Documents\Downloads\android-sdk_r07-windows\a
ndroid-sdk-windows\tools>adb push jupiter.xml /sdcard/jupiter.xml
failed to copy 'jupiter.xml' to '/sdcard/jupiter.xml': Permission denied
C:\Documents and Settings\Kevin\My Documents\Downloads\android-sdk_r07-windows\a
ndroid-sdk-windows\tools>adb shell
$ su
su
Permission denied
$
Note - this is a samsung captivate phone with a fresh cognition 2.36b rom and I used one click root on it to root the phone after the build..... (but I think the rom was rooted to start with??
Sorry ... just need a way to get access to this phone - trying adb.... also is there a windows file manager that would browse/edit the contents of this phone?
thanks in advance Kevin

PLEASE DIVERT ALL QUESTIONS TO Q&A FORUM NEXT TIME.
IF you're on Froyo.. for some reason froyo does not allow pushing to /system .. at least for me that's the case (someone correct me)
root your phone:
1. adb push /sdcard/jupiter.xml
2. adb shell
3. su
4. cp /sdcard/jupiter.xml /system/gps/jupiter.xml (or wherever you need to put it)
5. do the same for the rest of the files.. but tbh
THERE'S NO FIXING GPS YET

darkamikaze said:
PLEASE DIVERT ALL QUESTIONS TO Q&A FORUM NEXT TIME.
THERE'S NO FIXING GPS YET
Click to expand...
Click to collapse
What he said.

If froyo didn't fix your gps then you are sol. But don't be so sure its still broke, it can take some time on the first lock. Once it gets a lock within 5-10 meters it should work decent afterwards with the occasional hiccup usually when its not used every day. But some are reporting poor performance still with froyo.
A factory reset can fix some bugs I have seen on jf7 and ji6 on my phone causing the gps to turn off. Jj4 doesn't seem to have that bug on my phone. Cog2.3b6 is jj4 based
Some claim to have performance degrade over time, I think that's all placebo but others have completely different experiences with gps than I do. I notice it having to occasionally need to get new gps data causing a delay in the initial lock but it seems more random than progressive and I never fail to get a lock.
If you are trying to use the jupiter.xml file in the gps solution thread from clshortfuse our what ever his name is, you will likely see an no improvement to a slight improvement. It gets faster locks on eclair roms but on froyo the jupiter file already resembles his and the major difference being that his forces the google server for gps data.
Sent from my SAMSUNG-SGH-I897

OK thanks for all the help so far -
I had a n82 phone, like 2-3 years ago, it was awesome.... google maps and all... blue dot was where the phone was... I could watch me walk around my house... it would show me getting the mail walking down the drive way to the mail box and back....
I have an iphone 3gs....works fine.... maybe not quite as good as the n82 did, but works ok, locks quick and will the blue dot with in a few feet of me IN MY HOUSE.
While I dont get this whole GPS problem on this phone I hear you about not trying to fix it.
I have some limited unix experience... used vi and other stuff, was able to move,copy, edit and replace files... change permissions and other standard stuff.
So if the cognition rom is rooted as is, and I was rooted before the rom, I assume I still am rooted....
Why wont the commands I tried work?
I did not try the other commands noted in this thread, yet, I will soon.
So is it my phone? or do I have the commands/syntax wrong?
If I am going to stick it out with the phone I need to figure out how to fix it.
thanks again for your help.
Kevin

Any ideas or reasons why this command would not work?
C:\Documents and Settings\Kevin\My Documents\Downloads\android-sdk_r07-windows\android-sdk-windows\tools>adb push jupiter.xml /sdcard/jupiter.xml
failed to copy 'jupiter.xml' to '/sdcard/jupiter.xml': Permission denied
My file on my PC is in the folder I am working from ....\tools and I assume I should have permissions to the sdcard folder?
Any help would be appreciated.
thanks Kevin

Have you made sure to grant superuser permission on the phone?
I had that issue the first time I tried it and found that I hadn't granted superuser access.
Also to the OP, if you switch to Perception, DG includes the Jupiter fix in the ROM.

You can't push to /system in FROYO.
you have to push it to /sdcard first
adb shell
su
cp /sdcard/jupiter.xml /<LOCATION>
and chmod it
and chown it.

thanks for the help... to make sure I have the right permissions I need to use the chmod and chown commands -
Do I need to mount the system first? Something like -
Code:
adb shell
$ su
# mount -o rw,remount /dev/stl9 /system
# chmod 777 /system/etc/*
thanks again, Kevin

haeffnkr said:
thanks for the help... to make sure I have the right permissions I need to use the chmod and chown commands -
Do I need to mount the system first? Something like -
Code:
adb shell
$ su
# mount -o rw,remount /dev/stl9 /system
# chmod 777 /system/etc/*
thanks again, Kevin
Click to expand...
Click to collapse
I would never do 777 on any file. Jupiter.xml should be 644 and user and group root.
Sent from my SAMSUNG-SGH-I897 using XDA App

su: must be suid to work properly

Rooted my hero 2.1 and when I try to $ su , I get "must be suid to work properly". I've not ran into this before, What needs to be done to fix this ? thanks.

dude what are you talking about when u root u have super user aka su

Bierce22 said:
dude what are you talking about when u root u have super user aka su
Click to expand...
Click to collapse
Yea, you'd think that would'nt you.. When I run Regs "root me" , It tells me I'm already rooted, but when I try the command, $ su , I get the above message..or permission denied..

Houndog101 said:
Yea, you'd think that would'nt you.. When I run Regs "root me" , It tells me I'm already rooted, but when I try the command, $ su , I get the above message..or permission denied..
Click to expand...
Click to collapse
Also, I see # from adb shell command, but the phone thinks its not rooted. What up with that. If I try to install busybox it says " No root access" , rom manager the same thing...all I want to do is install a recovery so I can get off the stock rom..

Have you tried something as simple as updating su in the play store and trying? If not, try flashing an HERCIMG recovery through hboot.
Sent from my PC36100 using xda premium

anthony_s said:
Have you tried something as simple as updating su in the play store and trying? If not, try flashing an HERCIMG recovery through hboot.
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
Yes and Yes, Niether worked,, thanks tho.

Have you tried updating the su binary from within the su app itself?
Sent from my PC36100 using xda premium

Yes, that worked, thanks.

Houndog101 said:
Rooted my hero 2.1 and when I try to $ su , I get "must be suid to work properly". I've not ran into this before, What needs to be done to fix this ? thanks.
Click to expand...
Click to collapse
Old old thread but if someone encounters this again, it is due to busybox SU not having the correct permissions and can be corrected easily.
I got the info from here: ttp://forum.nas-forum.org/index.php?page=Thread&threadID=526
Quoted from that page:
Code:
su: must be suid to work properly
I finally discovered that /bin/busybox which provides su (and in fact almost all commands) has not its set UID , i.e. the unix rights are
Code:
rwxr-xr-x instead of rwsr-xr-x
i could finally change the rights with
Code:
chmod 4755 /bin/busybox
and su works fine again
Click to expand...
Click to collapse
Just thought I would share since I saw this on my synology NAS and it pretty much directly applies to this issue from an age ago.

yes, you need to su in order to make it work as administrator.

[Q] Issue with recent returned tablet from repair centre and factory mode

HI All,
I just have recieved my Tablet back after it would no longer power up - looks like they had to re flash it and put it into factory mode and left it there, problem with this is that I cannot lock the screen, I have researched and found a temp fix where you put a engineers code in - but as soon as you re-boot it loses this.
I have also found some code
adb shell
su
echo -n ON > /efs/imei/keystr
chown 1001:1001 /efs/imei/keystr
which i have tried using a terminal emulater (on the andriod market) not sure if its me being dumb but i cant get this to work, when it boots now it looks like nvflash is now unlocked. I'm hoping i dont have to send it back again - is there any other things I can try? I have tried other ROMS but because of this factory mode its the same
Thanks in advance

whitehart said:
HI All,
I just have recieved my Tablet back after it would no longer power up - looks like they had to re flash it and put it into factory mode and left it there, problem with this is that I cannot lock the screen, I have researched and found a temp fix where you put a engineers code in - but as soon as you re-boot it loses this.
I have also found some code
adb shell
su
echo -n ON > /efs/imei/keystr
chown 1001:1001 /efs/imei/keystr
which i have tried using a terminal emulater (on the andriod market) not sure if its me being dumb but i cant get this to work, when it boots now it looks like nvflash is now unlocked. I'm hoping i dont have to send it back again - is there any other things I can try? I have tried other ROMS but because of this factory mode its the same
Thanks in advance
Click to expand...
Click to collapse
A friend of mine followed this thread and he made it.i think he has the same issue with factory mode.Did u try?if not u can try and see how it works.Good luck.
http://forum.xda-developers.com/showthread.php?t=1870564

thovu1980 said:
A friend of mine followed this thread and he made it.i think he has the same issue with factory mode.Did u try?if not u can try and see how it works.Good luck.
http://forum.xda-developers.com/showthread.php?t=1870564
Click to expand...
Click to collapse
cheers yes thats what i tried following
I wonder if I'm not doing the
adb shell
su
echo -n ON > /efs/imei/keystr
chown 1001:1001 /efs/imei/keystr
code correctly, whats the best way to enter this code? I think I may need an idiots guide !!

im going to phone the repair place see what they say

Phoned up samsung - they not able to do anything on the phone, sigh!!!!
it has to go back to the repair place - samsung i dont think understood the issue fully - lets hope it gets fixed - i learnt they replaced the motherboard!

Why don't you ask over here? http://forum.xda-developers.com/showthread.php?t=1870561
You can use Terminal Emular and enter:
Code:
su
echo -n ON > /efs/imei/keystr
chown 1001:1001 /efs/imei/keystr
Make sure you are rooted! (SuperSU or Superuser installed)

tracid said:
Why don't you ask over here? http://forum.xda-developers.com/showthread.php?t=1870561
You can use Terminal Emular and enter:
Code:
su
echo -n ON > /efs/imei/keystr
chown 1001:1001 /efs/imei/keystr
Make sure you are rooted! (SuperSU or Superuser installed)
Click to expand...
Click to collapse
just tried teh code again to see if i was going mad - no it doesnt seem to work? the engineers code temp works but the emulator code doesnt
EDITI just did a reset - after doing the code - guess what so far so good I think i have fixed it
Yayyy!!!

xmodgames issue with supersu

Hi all,
I have SuperSU Pro 2.46 installed on a lifetab P8912.
Everything worked and I got checked with rootchecker that everything works fine.
Xmodgames also starts with the message that it has root permissions granted.
The ClashofClans mod has a problem: "Mod start fails. Please confirm XModgames is authorized with root permission".
What can I do ? Does anybody else encounter the same problem or fixed that already ?
THANKS a lot for your help,
Alecz

alecz2012 said:
The ClashofClans mod has a problem: "Mod start fails. Please confirm XModgames is authorized with root permission".
Click to expand...
Click to collapse
This should be brought to the attention of the developer of "ClashofClans" -- it might be looking for 'su' at a hard-coded path. You could test for this (and perhaps even fix the problem for you) by copying or linking '/system/xbin/su' to other common paths -- such as '/system/bin/su'.
At a terminal enter:
which su
It should reply '/system/xbin/su'.
Frank

hmm, thanks , but perhaps I didn't find the right shell to work with:
I do not have write access to that folder /system/bin
Shall I chmod 777 to that folder, at least temporary ?
Sorry for not having worked since a long time on linux..

alecz2012 said:
I do not have write access to that folder /system/bin
Click to expand...
Click to collapse
That partition is normally mounted for reading only, not for writing. Remount it as writable, copy the file, then remount as read-only again:
mount -o remount,rw /system
cp /system/xbin/su /system/bin
mount -o remount,ro /system
The SuperSU installation script will delete that copy when you flash the update again so it isn't permanent, and there is only a small chance that this is the problem.
Frank

Hi Frank,
your mount description worked fine, but still I get the error when starting the mod from xmodgames.....
Perhaps you got another tip or trick .....
THX
Alex
Frank Westlake said:
That partition is normally mounted for reading only, not for writing. Remount it as writable, copy the file, then remount as read-only again:
mount -o remount,rw /system
cp /system/xbin/su /system/bin
mount -o remount,ro /system
The SuperSU installation script will delete that copy when you flash the update again so it isn't permanent, and there is only a small chance that this is the problem.
Frank
Click to expand...
Click to collapse

alecz2012 said:
Perhaps you got another tip or trick .
Click to expand...
Click to collapse
In a terminal, run
logcat -c
Then run the application which is failing to get root; then immediately after it fails run
logcat -d > /sdcard/dump.txt
Then examine '/sdcard/dump.txt' to see if it contains an error message which might help.
Frank

Hi Frank,
done, but in the txt file it is a bunch of - at least for me - magic !
I can find lotz of krsdk stuff, looks like a former try of kingroot is still existant and might prevent something there, or perhaps that's because xmodgames is checking for kingroot ...
Really do not know .....
Anyway,
I think I am getting closer , but still the last mile to take
Frank Westlake said:
In a terminal, run
logcat -c
Then run the application which is failing to get root; then immediately after it fails run
logcat -d > /sdcard/dump.txt
Then examine '/sdcard/dump.txt' to see if it contains an error message which might help.
Frank
Click to expand...
Click to collapse

alecz2012 said:
...looks like a former try of kingroot is still existant and might prevent something there, or perhaps that's because xmodgames is checking for kingroot ...
Click to expand...
Click to collapse
That's a very reasonable guess. I assume that you rooted with Kingo Root then replaced that with SuperSU. Maybe Kingo Root is still active on your device. Maybe SuperSU did not install and the root checker found Kingo's 'su'. Take a good look at both installations and try to figure out what is there. Does the SuperSU Android application run? See if 'su' will tell you whose it is by running
su --version
Frank

Kingroot didn't work when I tried it, therefore I went through the SuperSU installation.
su --version gives me
"2.45:SUPERSU"
Best regards,
Alex
Frank Westlake said:
That's a very reasonable guess. I assume that you rooted with Kingo Root then replaced that with SuperSU. Maybe Kingo Root is still active on your device. Maybe SuperSU did not install and the root checker found Kingo's 'su'. Take a good look at both installations and try to figure out what is there. Does the SuperSU Android application run? See if 'su' will tell you whose it is by running
su --version
Frank
Click to expand...
Click to collapse

I can't see what's happening from here but the cause could very well be the incomplete KingRoot attempt. It might be that your solution is to revert to stock to remove that Kingo stuff then root again using the procedure that succeeded.
Frank

i have same problem as OP, i have moto e stock 5.0.2 rooted with supersu can anyone help me

demoakka said:
i have same problem as OP, i have moto e stock 5.0.2 rooted with supersu can anyone help me
Click to expand...
Click to collapse
Same problem with me also i really need the mod working, few other apps like freedom is working but gltools arent working

The ClashofClans mod has a problem: "Mod start fails. Please confirm XModgames is authorized with root permission".
same problem with me also..

xmodgames needs to be updated, not SuperSU.

Some problem for me with Xmod for Boom Beach. Before i updated to Android 5.0.1 it was working.
Edit: Had an old Xmod version which i installed from titanium backup. New Xmod Version fixed the problem for me.

i have this problems but i have runned root please help me

~
i have Samsung Tab 10.5 (SN-T805) .. and it has the same issue
me and one of my expert friends analyzed the application to see what is the problem, we found out that XMODGAMES doesn't check the root properly
So, if there was an expert person that can reverse engineer the application and fix this issue, that would be great
PS: we don't have time to do it, because of our final college exams, we might do it in the summer.
~

alecz2012 said:
Hi all,
I have SuperSU Pro 2.46 installed on a lifetab P8912.
Everything worked and I got checked with rootchecker that everything works fine.
Xmodgames also starts with the message that it has root permissions granted.
The ClashofClans mod has a problem: "Mod start fails. Please confirm XModgames is authorized with root permission".
What can I do ? Does anybody else encounter the same problem or fixed that already ?
THANKS a lot for your help,
Alecz
Click to expand...
Click to collapse
make ur device language tu english

My xmodgames can't work either?have you found a way to fix it?

Here is the solution How to run Xmod games in android lollipop