Related
Hello,
Related to this post :
http://forum.xda-developers.com/showthread.php?p=39762775#post39762775
I have the following problem with an Xperia J:
Initial Problem:
- The mobile belongs to my cousin, she updated it with the Sony update center to the latest version (JB 4.1.2) and there: problem with the wifi when the sim.
- I got the mobile, and downgrade to the 4.0.4 version, I've tried 4 different versions:
-> ST26i_11.0.A.3.18_Global
-> ST26i_11.0.A.7.5_CE
-> ST26i_11.0.A.3.28_WE
-> St26i_4.0.4_11.0.A.3.28_CE3
I had always the problem with the wifi when the sim plugged.
Finally I've tried also the UNOFFICIAL CM 10, with no success
- I found a solution with the apk wifix manager witch worked with the 28 WE version of the firmware.
But I've continued to search an other solution, and I've remarked that when I flash the rom I always get the Warn: "This file is ignored : simlock.ta "
After some research I get an advice by a member of XDA to rename the file as "preset.ta", AND THERE, it works no warning ... BUT the sim is blocked (not locked) and I have always the message (invalid card).
I've tried to re-flash the firmware many times, to re-lock the bootloader (with appropriate ftf proposed in this forum ), Tried to use the sony update service .. But I have always the same problem (INVALID CARD)
I've also tried to format everything with CWM (system,card,cache) and made a sdcard partition, and NO way.
In addition:
- I can't enter to the fastboot mode, the led doesn't turn on blue no more, it works when I've started to work with, and it was important to install CM10, now I can't retry the CM installation.
- I've rooted the device, but I can't edit the build.prop (with root explorer neither with a terminal ide with vi editor, even if I do a "su" command and then "whoami", I didn't show : root).
- I've tried several sim cards, and they work with other devices (as xperia P and xperia U).
So, can any body help me with that please?!
Note : I'm in the middle east zone, some suggestions in the web talk about re-installing the official O2 rom, but I've searched this ROM with no success.
RevoOSyr said:
- I've rooted the device, but I can't edit the build.prop (with root explorer neither with a terminal ide with vi editor, even if I do a "su" command and then "whoami", I didn't show : root).
Click to expand...
Click to collapse
What are the build.prop permissions? Of course "Root is god", but you can set flag in kernel, that makes root follow his own rules, i.e. if you want to write to a file, it must be writable. If it isn't, you must change the permissions and then write to it.
build.prop afaik is rw-r--r-- so you must make it rw-rw-rw to write anything.
chmod go+w build.prop
or
chmod 666 build.prop
to restore:
chmod go-w build.prop
or
chmod 644
In reality with the version CE3, we have a line in the file build.prob witch lock the APN and I would to comment the line, it's not needed now, because I haven't this line in the other version.
I've tried to make a chmod but I wasn't able to do it.
Regards,
0x4721 said:
What are the build.prop permissions? Of course "Root is god", but you can set flag in kernel, that makes root follow his own rules, i.e. if you want to write to a file, it must be writable. If it isn't, you must change the permissions and then write to it.
build.prop afaik is rw-r--r-- so you must make it rw-rw-rw to write anything.
chmod go+w build.prop
or
chmod 666 build.prop
to restore:
chmod go-w build.prop
or
chmod 644
Click to expand...
Click to collapse
It's OK for the root problem, it was a problem with the rooting procedure here:
http://forum.xda-developers.com/showthread.php?t=2033114
in reality I had an error (can't mount /system in rw), I've reinstalled busybox and it's ok, I've tried to change some parameters in the build.prop (such : hide some language) and it works.
But still having a problem with the (INVALID CARD)
Any help?!
Thanks.
Other precision:
When I go to : *#*#7378423#*#*
Then: Service info > Configuration > Rooting Status : Bootloader unlock allowed says no
And the SIM LOCK seems to be incorrect.
I think that I've locked the bootloader somewhere, because I've unlockd the booloader 2 days ago when I've installed CM10, and everything was OK!!!
ThnkX
Other problem, in the SIM LOCK menu I have : x everywhere with the counter set to 0
After research in the web, that means that even it could not be unlocked by code!
it's strange that there's no way to fix that ...
No body has an idea about the solution for this problem?! even a payant one!
Thanks
Return to sony service
I didn't find any solution to this problem, so I've sent the device to sony service, and they didn't fix the problem yet.
The lesson of the story, you have to be very carefull when you do something (as lashing your mobile)
You have to know exactly what you do. And never to try insecure operations.
Im in the same situation... any news?
nacxo said:
Im in the same situation... any news?
Click to expand...
Click to collapse
did you have TA BACK UP?
Does anyone have any information on how to root this phone?
It is a tracfone running Android 4.1 with 1ghz qualcomm cpu.
Thanks.
I'm also looking for someone who might have some pointers on how to root this phone or install KitKat apps from Nexus 5 dump!!!
I know it is a low end phone but there are lots of people in the Tracfone world who are now able to get Android phones and are NEW to the smartphone universe.
Thanks.
I'm thinking of buying this phone. As a low end Android, how does it hold up? And if you want to root it, try Bin4ry's root method here. Just be careful.
Tried Bin4ry on ZTE Valet but it failed to root
I've had the phone a couple of days so far and while I'm by no means a qualified reviewer of smartphones, I do like the ZTE Valet. I'm too cheap to pay the $70-100 USD/month for a post-paid service that I don't need.
After searching the forums and seeing that no one reported trying to root the phone, I took a brave pill and tried the Bin4ry method (v31). I got the same message that many users reported - after rebooting, it fails to mount and copy the necessary files. Both the new standard method and the old method failed. It did no apparent harm to the phone - just didn't work. Here's some details on the phone I have:
Android version 4.1.1
Kernel 3.4.0-perf [email protected]
Thanks for any ideas or advice.
I just picked one up at Kmart for $80 today and am checking things out, trying to see about rooting it. My Hisense Sero 7 Pro tab is rooted and running great with a DoPa custom ROM.
I also purchased one of these and am happy so far. I have a question on the magnetic and rotation sensor. They seem to show up as installed as ak8962 devices but apps like 'my android sensors' don't show any data being returned. are they just not actually installed?
thanks
sam
gberpa said:
I just picked one up at Kmart for $80 today and am checking things out, trying to see about rooting it. My Hisense Sero 7 Pro tab is rooted and running great with a DoPa custom ROM.
Click to expand...
Click to collapse
samcoinc said:
I also purchased one of these and am happy so far. I have a question on the magnetic and rotation sensor. They seem to show up as installed as ak8962 devices but apps like 'my android sensors' don't show any data being returned. are they just not actually installed?
thanks
sam
Click to expand...
Click to collapse
The rotation of the device changes the screen from portrait to landscape and 'maps', 'Gas Buddy' seems to show the right direction for magnetic north. I haven't had much time to check yet. AAMF, I haven't activated or transferred my number to the 'phone' yet as am deciding if is a 'keeper'. So far, I think it is as I can use WiFi and 'turn off' mobile data by option. Now checking things like battery life in standby.. Haven't found an option to shut WiFi when screen is off like in my JB 4.2.1 and HC 3.1 devices. Only seem to be able to turn WiFi on or off or see an option for airplane mode.
I agree - the screen rotates (how - I don't know ) I would assume gas buddy is using GPS to find north.
sam
gberpa said:
The rotation of the device changes the screen from portrait to landscape and 'maps', 'Gas Buddy' seems to show the right direction for magnetic north. I haven't had much time to check yet. AAMF, I haven't activated or transferred my number to the 'phone' yet as am deciding if is a 'keeper'. So far, I think it is as I can use WiFi and 'turn off' mobile data by option. Now checking things like battery life in standby.. Haven't found an option to shut WiFi when screen is off like in my JB 4.2.1 and HC 3.1 devices. Only seem to be able to turn WiFi on or off or see an option for airplane mode.
Click to expand...
Click to collapse
Any update on this?
It isn't looking good so far..
http://androidforums.com/zte-valet/799676-ill-help-find-root-method-if.html
They have tried a bunch of stuff so far.
sam
Unkn0wn0ne said:
Any update on this?
Click to expand...
Click to collapse
samcoinc said:
It isn't looking good so far..
They have tried a bunch of stuff so far.
sam
Click to expand...
Click to collapse
I'm going to get my hands on the phone soon. I'll proceed to attempt to get a recovery or something compiled for it if I can. First, I'd have to dump the rom and kernel which might require root access, but we will see. Once we have a recovery we can port CyanogenMod over to it.
Also I think I know why it's crashing, but I can't be sure until I can test it out myself.
Unkn0wn0ne said:
I'm going to get my hands on the phone soon. I'll proceed to attempt to get a recovery or something compiled for it if I can. First, I'd have to dump the rom and kernel which might require root access, but we will see. Once we have a recovery we can port CyanogenMod over to it.
Also I think I know why it's crashing, but I can't be sure until I can test it out myself.
Click to expand...
Click to collapse
Wish you luck..just got my replacement unit from TracFone after the first one's screen froze.
oooops. Sorry posted in wrong thread.
ZTE Valet Z665c - obtaining temporary root
After trying numerous root methods (Bin4ry, Framaroot, ...), I stumbled on a method of getting temporary root using Cydia Impactor. Cydia Impactor appears to be partially successful. First of all, please note that all credit goes to those involved with Cydia Impactor and the discovery of the original exploits (do a search if you want).
This method might seem a little convoluted, but it works reliably for me. Note that I use a Linux machine so you might have to adapt the steps to work on another platform.
Prerequisites:
1. Menu -> System settings -> Developer options -> USB debugging ->Enabled.
2. Menu -> System settings -> Developer options -> Stay awake ->Enabled (to keep the telnet session from going to sleep).
3. telnet (I am running on Ubuntu, but some sort of telnet program is needed).
4. Cydia Impactor
5. phone is connected to your wifi.
Steps:
1. Run the "Cydia Impactor" to "# drop SuperSU to /system/xbin/su". See what happens.
2. It failed for me giving an error related to not being able to remount /system or not being able to create /system/xbin/su.
3. In Cydia Impactor, run "# start telnetd as system on port 2222". You don't need to bother to telnet in. Just let it finish and then proceed to the next step.
4. In Cydia Impactor, run "# start telnetd as root on port 22". Let it finish.
5. Telnet into your phone from a terminal on your computer: "telnet 192.168.1.117 -l root 22". Note that the ip address is likely different on your network, e.g., 192.168.1.xxx.
6. If everything worked OK, you should be presented with a root prompt ("~ #"). I have busybox (obtained from the Bin4ry exploit download) that I adb pushed to /data/local/tmp. The command "/data/local/tmp/busybox whoami" tells me I am indeed root.
OK - now the bad news for me. I proceed to try to install su but remount fails. If I issue the command:
~ # mount -o rw,remount /system
~ #
A root prompt is returned with no error message suggesting that it successfully remounted /system. Woohoo! But a "mount" command (or cat /proc/mounts) says it is still "ro" or read only. Darn. Does it appear that ZTE has crippled the mount command in some way? Now the question is how to permanently install root? I have poked around and at least was able to make a backup to my sdcard using bzip2
This should at least help as a first step. Others including myself have posted elsewhere on this phone. At this point, I'm not willing to risk flashing anything. I'm a noob so I'm hoping someone who is more familiar with the permissions and that sort of thing can complete the root and post a solution.
Thanks.
Awesome!
These findings are great, I'd be willing to check this out soon. (Linux box is down do to hardware issue. ).
If we can obtain root the remounting issue can definitely be fixed. Also, does busybox have the premissions to run?
Try this:
Code:
mount | grep system
That will give you somewhere within the text the partition that is registered as /system . Then:
Code:
mount -o rw,remount [PARTITION-THAT-COMMAND-RETURNED-HERE-MINUS-BRACKETS] /system
See if that works. But anyways, if it doesn't it can still be rooted! (just temporarily, but it is no longer an 'unrootable' device)
Note: I am not responsible for what happens using those commands.
a little more info in response to your questions
Dear Unkn0wn0ne,
I had messed around with it and also tried something like you suggested, e.g.:
mount -o rw,remount,relatime,data=ordered -t ext4 /dev/block/mmcblk0p19 /system
Also tried it with the "-n" option to avoid a write to mtab although I don't remember seeing mtab while purusing the file system.
Hadn't noticed that busybox was available under /system/bin:
~ # ls -al /system/bin/busybox
-rwxr-xr-x 1 root shell 1075144 Jul 19 11:20 /system/bin/busybox
~ #
Could be that it has a more limited command set than the one I put in /data/local/tmp. A lot of the commands under /system/bin have a symbolic link to toolbox.
Note that the telnet connection needs to be made over wifi and not the one available over usb. I got the ip address from my router's client list.
Oh yes - thanks for the reminder. Forgot to include the disclaimer about harming the phone or voiding the warranty.
Hope it works out well for you. Glad to hear your encouraging remarks.
Awesome!
Alright so that didn't work. This guy over here has a suggestion (he has scene your thread): - I can't publish links so I'll pm the link to you.
Also if busybox is symbolically linked you'd have to tell it specifically to call to the busybox pushed over via adb to: /data/local/tmp/busybox and not the stock.
In this case: /data/loocal/tmp/busybox/mount
Also the disclaimer is a must. There will always be that person that tries to blame it on someone else.
Note: I am not responsible for whatever happens using the information provided in this post.
karmmisht said:
After trying numerous root methods (Bin4ry, Framaroot, ...), I stumbled on a method of getting temporary root using Cydia Impactor. Cydia Impactor appears to be partially successful. First of all, please note that all credit goes to those involved with Cydia Impactor and the discovery of the original exploits (do a search if you want).
This method might seem a little convoluted, but it works reliably for me. Note that I use a Linux machine so you might have to adapt the steps to work on another platform.
This should at least help as a first step. Others including myself have posted elsewhere on this phone. At this point, I'm not willing to risk flashing anything. I'm a noob so I'm hoping someone who is more familiar with the permissions and that sort of thing can complete the root and post a solution.
Thanks.
Click to expand...
Click to collapse
I attempted this myself on my Windows 8 machine. I had to enable telnet, but that was easy. I had to reararange the command to "telnet root 192.168.x.xxx:22" (xxx is my IP). It keeps giving me the error "Connect failed."
Any thoughts out there?
try putty
Ph0enix_216,
I tried to connect from a Windows 7 machine and it works using putty for telnet (www.putty.org, a great program). Be sure to set the Connection->Data->Auto-login name to root.
well the guy in the other thread bricked his it sounds like...
http://androidforums.com/zte-valet/799676-ill-help-find-root-method-if-3.html
They tried to modify the mmcblk0p16 boot image and re-copy it back. It seemed to re-copy but then didn't boot with a verify error.. (I am paraphrasing - and don't really understand what they where doing )
sam
Ph0enix_216 said:
I attempted this myself on my Windows 8 machine. I had to enable telnet, but that was easy. I had to reararange the command to "telnet root 192.168.x.xxx:22" (xxx is my IP). It keeps giving me the error "Connect failed."
Any thoughts out there?
Click to expand...
Click to collapse
Hi dear XDA users.
I have been researching for a while now to troubleshoot my own problem but i cant find anything.So i though maybe some of you guys could help me with this.So here is the story.
I rooted my Z3 via KingRoot ( One Click Root). Android 5.1.1 . Bootloader is locked. After these i installed some apps such as dsploit ,nmap, etc. And they all require BusyBox which i knew from the beginning because i used an Galaxy S3 and everything wokred perfectly. When i press install busybox tells me it failed and i should try to install it to a different location.I tried all of the locations but it does not work.After that i thought maybe i could install busybox with Terminal Emulator but it also doesnt work.I tried various codes and i had answers like Mount not permitted or DIrectory not found. Please help me.
So I have my 930-F S7 systemless rooted with Magisk and with encryption.
I noticed that after rooting I wasn't able to use SmartView on my TV anymore, I've tried lots of things but eventually came to a proposed solution of editing build.prop and adding the following line to the end of it and it should work:
wlan.wfd.hdcp = disable
Click to expand...
Click to collapse
Unfortunately when trying to alter build.prop there was always an error saying it was read only, after a quick research it seems it's because it's a systemless root, so I should try doing it directly with Magisk.
Found myself to a helpful thread, that told me to put the above command line into a blank .txt and paste it into:
/sbin/.core/img/.core/post-fs-data.d
Click to expand...
Click to collapse
But it failed, I wasn't able to paste the file.
So I don't know what to do, has anyone faced this issue and can help me?
I was able to fix this issue and FINALLY be able to Smart View / Screen Mirror to other devices.
To do so I installed Didgeridoohan's MagiskHide Props Config Module. Installed a Terminal Emulator and proceeded to include the line mentioned on my previous post to build.prop.
After that, voila it was finally fixed.
Done.
The line is already present in my custom Rom. The problem is elsewhere.
CyberBeaR said:
I was able to fix this issue and FINALLY be able to Smart View / Screen Mirror to other devices.
To do so I installed Didgeridoohan's MagiskHide Props Config Module. Installed a Terminal Emulator and proceeded to include the line mentioned on my previous post to build.prop.
After that, voila it was finally fixed.
Click to expand...
Click to collapse
can please tell me the steps how did u you do tha
please
thanks.
I've looked into the forums and haven't seen anyone ask about this, but ever since a update in January (I think) I've been unable to use my hotspot. I'm on an unlocked rooted phone with verizon as my serivce provider.
Normally I would just edit the build.prop, but lately I've been having issues since MagiskHide Props is a dead module. Does it still work for anyone else?
Am I missing a new feature?
I'm not that verse with how MagiskHide works, so I'll ask is there a way of changing / editing build.prop like the days of old?
rknee said:
I've looked into the forums and haven't seen anyone ask about this, but ever since a update in January (I think) I've been unable to use my hotspot. I'm on an unlocked rooted phone with verizon as my serivce provider.
Normally I would just edit the build.prop, but lately I've been having issues since MagiskHide Props is a dead module. Does it still work for anyone else?
Am I missing a new feature?
I'm not that verse with how MagiskHide works, so I'll ask is there a way of changing / editing build.prop like the days of old?
Click to expand...
Click to collapse
I had a similar issue on the Pixel 5. You should be able to turn the hotspot on while connected to WiFi. Turn Wifi off while leaving the hotspot on and see if it stays on. You shouldn't need to edit anything in the build.prop to get hotspot to work, but there does seem to be an elusive authentication issue.
V0latyle said:
I had a similar issue on the Pixel 5. You should be able to turn the hotspot on while connected to WiFi. Turn Wifi off while leaving the hotspot on and see if it stays on. You shouldn't need to edit anything in the build.prop to get hotspot to work, but there does seem to be an elusive authentication issue.
Click to expand...
Click to collapse
Gave it a try, but my hotspot immediately turns off as soon as I turn off wifi.
If I can figure out why the props command doesn't take. I've read some posts about people talking about "Settings version mismatch" when using props. I'll have to take a look at that thread and see if there are any new answers.
Thanks for the reply
rknee said:
is there a way of changing / editing build.prop like the days of old?
Click to expand...
Click to collapse
I haven't used this so can't comment on how well it works, but maybe it's something that will help your situation.
GitHub - HuskyDG/magic_overlayfs: Make system partition become read-write (it is also possible without Magisk)
Make system partition become read-write (it is also possible without Magisk) - GitHub - HuskyDG/magic_overlayfs: Make system partition become read-write (it is also possible without Magisk)
github.com
Lughnasadh said:
I haven't used this so can't comment on how well it works, but maybe it's something that will help your situation.
GitHub - HuskyDG/magic_overlayfs: Make system partition become read-write (it is also possible without Magisk)
Make system partition become read-write (it is also possible without Magisk) - GitHub - HuskyDG/magic_overlayfs: Make system partition become read-write (it is also possible without Magisk)
github.com
Click to expand...
Click to collapse
thanks for the resource, I'll take a look, as I'd like to learn more in depth of the inner workings.
I've found the issue, MagiskHide still works but for whatever reason the directory that I get started on when opening a terminal app is incorrect, so all that was needed was changing the directory ( /system/bin/ )
Thanks to anyone who took the time to look at this post, but my problem is now resolved
Great a file (no extension) in /data/adb/post-fs-data and put
resetprop prop value
So, "resetprop net.tethering.noprovisioning insert-value"
And reboot. Be sure to give 744 permission