Database Info

My Xoom 2 MZ 616 can't boot normally

Hi!
I have an interesting problem with my XOOM 2 MZ 616: When I turn on, it keeps wiping internal partition or something like this. See attached dmesg logs to understand what I mean:
See the attached dmesg log.
Can anyone help me ? Does anyone know what's happening?
Thanks!

not sure but your system data seems corrupted
I would advice you to flash again with fastboot back to 3.2.2 and update to ICS, you will loose all personal data.
Sent from my XOOM 2 using xda premium

More info
I saw in the logs something about CDROM. So, this means my tablet is booting a recovery image everytime because there is a problem.
First, I remember the last time I used my xoom I installed Root Logger bash feature. ( Yes, my xoom was rooted ). I went to it's page play . google . com / store / apps/details?id=com.stericson.rootlogger.free and saw a quote:
Not kidding about a backup
Don't use this if you don't know more about using a shell than the developer. If you use this app, he installs his own custom bash shell, removes your /system/bin/sh and then he is too stupid to set permissions correctly and will ruin your day and your phone install. That's right he sets the /system/bin/sh to the wrong permissions. If you install this, you're gonna have a bad time
Click to expand...
Click to collapse
Too bad I didn't read it before. After I installed it, it was all right, untill I powered off.
Now, I digged a bit for linux file permissions and I found the /system/bin/sh permissions:
lrwxrwxrwx app_309 app_309 /system/bin/sh --> /system/bin/bash
As you see, it's a symlink.
$stat sh
File 'sh' -> '/system/bin/bash'
Size: 16 Blocks: 0 IO Block: 4096 symbolic link
Device: b311h/45841d Inode: 1587 Links: 1
Access: (0777/lrwxrwxrwx) Uid: (10309/ UNKNOWN) Gid: (10309/ UNKNOWN)
Access:.....................
Modify :......................
Change: ...................... (date)
Now, can anyone help me fixing the permissions? I think this could be replicated.
Thanks!

OK, seems that your sh is linking to another link, which is weird
In my tablet the /system/bin/sh is linking to /system/bin/mksh, and this mksh is the real sh binary
You can then try to log to your tablet, change the destination of sh link to /system/bin/mksh instead of /system/bin/bash
I uploaded the mksh binary in case you're missing it.
Here you can find it
https://app.box.com/s/pg22fskoxt1toif2u5kt
Sent from my XOOM 2 using xda premium

Proximity Sensor Bug Fixed, .Screen turns off during call.ISSUE FIXED

Methods that worked for me.
Method 1.
Blow Air it will solve your prob hopefully.
Method 2.
go to samsung code *#0*#. then SENSORS and Read your Proximity sensor values.
<<< DECISION >>>>>
####Calibration isnot needed if ####
.
your phone doesnt vibrate in normal but does so when u physically put your finger on the Sensor.
#### Calibration needed if ####
.
your phone is vibrating in this menu no matter what, you put your finger on the sensor or not
Follow these steps
1. download Android Terminal from store
2. type these commands to calibrate automatically
$ su
# echo 0 > /sys/devices/virtual/sensors/proximity_sensor/prox_cal
# echo 1 > /sys/devices/virtual/sensors/proximity_sensor/prox_cal
Reboot and see if it works.go to *#0*# and check if it continuously vibrating or only does so when you put your finger on the SENSOR.
<<<< IF Continuously Vibrating Follow these steps>>>>
you need to manually put values in ur /efs/prox_cal.it Reads Hexadecimal value. so you have to convert your decimal values into HEX.
##### FIND YOUR Decimal Values and pushing them into /efs/prox_cal ######
Method : finding two values for calibration . offset + normal value.
##.. FINDING OFFSET ######
cat /sys/devices/virtual/sensors/proximity_sensor/prox_cal
note down the values it returns.. mine is 5,64,100.. you only need the 1st value which is 5.
### FINDING NORMAL STATE ######
cat /sys/devices/virtual/sensors/proximity_sensor/state
note down the value if returns. mine is 64
now ADD OFFSET value + Normal Value
5 + 64 = 69
Convert in Hexadecimal which is 45.
NOTE: sometimes normal value is 0, its OK you do you math and convert 1st OFFSET into hex. using lower case for Hex values in steps below.
<<<<<<<<<<< Pushing the value in /efs/prox_cal >>>>>>>>>>>>>>
# echo -en $ '\x45' > /efs/prox_cal
then
# chown system:system /efs/prox_cal
# chmod 644 /efs/prox_cal
# sync
# Reboot
All done. after that go to *#0*# then SENSORS and move your finger on the sensor, yout phone will Vibrate only when you put your finger on the sensors.
Manual method worked for me.
ENJOY.
NOTE: I am not a developer. i was just stuck with this problem for so long so now i found it from "mcelicalderon". who posted this method some where

Wow thanks. Skype totally killed my phone because of this and I thought it was a bug but the manual calibration fixed it. Cheers.
Sent from my GT-I9505 using Tapatalk

THANKS
Manual Method worked for me,
ps there is no SPACE after $ sign e.g. $'\x0a'

no needed for 4.4.2
i_fain said:
Manual Method worked for me,
ps there is no SPACE after $ sign e.g. $'\x0a'
Click to expand...
Click to collapse

EclipseX said:
no needed for 4.4.2
Click to expand...
Click to collapse
Thank you very much, which rom are you using> I want to try if everything is working. Of course I need knox :silly:

just the leak release from samsung 4.4.2 the last one 2 january 2014
i_fain said:
Thank you very much, which rom are you using> I want to try if everything is working. Of course I need knox :silly:
Click to expand...
Click to collapse

EclipseX said:
just the leak release from samsung 4.4.2 the last one 2 january 2014
Click to expand...
Click to collapse
Yes, I have that, please tell me if there is anything not working that you have noticed. One more thing did you wipe data or apps remains working after install?
Sent from my GT-I9505 using Tapatalk

I came from 4.3 stock
Install via Odin without wipe.....after install I've wipe the dalvik cache
I have only one complain...the taskmanager don't work propretly
Everything else work like a charm
i_fain said:
Yes, I have that, please tell me if there is anything not working that you have noticed. One more thing did you wipe data or apps remains working after install?
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse

Method 2. go to samsung code *#0*#. - doesn't work
Is there any reason why it shouldn't work on i9505g version 4.4.2?

Stunn2 said:
Is there any reason why it shouldn't work on i9505g version 4.4.2?
Click to expand...
Click to collapse
I fixed mine on an i9505 using an i9505g rom, so I guess not.
Sent from my GT-I9505G using Tapatalk 2

Edgio60 said:
I fixed mine on an i9505 using an i9505g rom, so I guess not.
Sent from my GT-I9505G using Tapatalk 2
Click to expand...
Click to collapse
I thought there would be an equivalent tester on the google edition....

10 Million thanks for this!!!
Ammar Saood said:
Methods that worked for me.
Method 1.
Blow Air it will solve your prob hopefully.
Method 2.
go to samsung code *#0*#. then SENSORS and Read your Proximity sensor values.
<<< DECISION >>>>>
####Calibration isnot needed if ####
.
your phone doesnt vibrate in normal but does so when u physically put your finger on the Sensor.
#### Calibration needed if ####
.
your phone is vibrating in this menu no matter what, you put your finger on the sensor or not
Follow these steps
1. download Android Terminal from store
2. type these commands to calibrate automatically
$ su
# echo 0 > /sys/devices/virtual/sensors/proximity_sensor/prox_cal
# echo 1 > /sys/devices/virtual/sensors/proximity_sensor/prox_cal
Reboot and see if it works.go to *#0*# and check if it continuously vibrating or only does so when you put your finger on the SENSOR.
<<<< IF Continuously Vibrating Follow these steps>>>>
you need to manually put values in ur /efs/prox_cal.it Reads Hexadecimal value. so you have to convert your decimal values into HEX.
##### FIND YOUR Decimal Values and pushing them into /efs/prox_cal ######
Method : finding two values for calibration . offset + normal value.
##.. FINDING OFFSET ######
cat /sys/devices/virtual/sensors/proximity_sensor/prox_cal
note down the values it returns.. mine is 5,64,100.. you only need the 1st value which is 5.
### FINDING NORMAL STATE ######
cat /sys/devices/virtual/sensors/proximity_sensor/state
note down the value if returns. mine is 64
now ADD OFFSET value + Normal Value
5 + 64 = 69
Convert in Hexadecimal which is 45.
<<<<<<<<<<< Pushing the value in /efs/prox_cal >>>>>>>>>>>>>>
# echo -en $ '\x45' > /efs/prox_cal
then
# chown system:system /efs/prox_cal
# chmod 644 /efs/prox_cal
# sync
# Reboot
All done. after that go to *#0*# then SENSORS and move your finger on the sensor, yout phone will Vibrate only when you put your finger on the sensors.
Manual method worked for me.
ENJOY.
NOTE: I am not a developer. i was just stuck with this problem for so long so now i found it from "mcelicalderon". who posted this method some where
Click to expand...
Click to collapse
10 million thanks for this!!!, I´d say you were sent by an angel, I was looking for my opperator's stock ROM to flash it and ask for warranty because of this problem and I accidentally found your thread. The manual method worked perfectly.
Now one question: Is it necessary to follow this procedure each time I install a new rom?

0ptimus82 said:
10 million thanks for this!!!, I´d say you were sent by an angel, I was looking for my opperator's stock ROM to flash it and ask for warranty because of this problem and I accidentally found your thread. The manual method worked perfectly.
Now one question: Is it necessary to follow this procedure each time I install a new rom?
Click to expand...
Click to collapse
Thanks Dear.. it delighted me that it worked for your ..
nope ... i flashed 100 other roms .. and it stays the same .. and sensor works properly.. :

Thank for this. It has fixed my wifes samsung s3. A few things that might help others..
My problem stared when I replaced a cracked screen
The echo 0 & 1 worked, but didn't keep after a reboot
After putting the new calibration value in /efs/prox_cal, I forgot (read 'too lazy') to do the chown and chmod and it was lost when I rebooted. The next time I did the chown & chmod and the value was saved.
For me, after I did the echo 0 & 1, I could see that /efs/prox_cal had been updated (which was then lost on reboot)
I tried doing a echo 0 & 1 (which updated /efs/prox_cal) and then I did the chown & chmod. This permanently saved the values for me.
Summary - If echo'ing 0 & 1 into prox_cal is lost after a reboot, try the following before going to the effort to calculate the calibration value
Code:
$ su
$ echo 0 > /sys/devices/virtual/sensors/proximity_sensor/prox_cal
$ echo 1 > /sys/devices/virtual/sensors/proximity_sensor/prox_cal
$ chown system:system /efs/prox_cal
$ chmod 644 /efs/prox_cal
$ sync
YMMV

seamusph said:
Thank for this. It has fixed my wifes samsung s3. A few things that might help others..
My problem stared when I replaced a cracked screen
The echo 0 & 1 worked, but didn't keep after a reboot
After putting the new calibration value in /efs/prox_cal, I forgot (read 'too lazy') to do the chown and chmod and it was lost when I rebooted. The next time I did the chown & chmod and the value was saved.
For me, after I did the echo 0 & 1, I could see that /efs/prox_cal had been updated (which was then lost on reboot)
I tried doing a echo 0 & 1 (which updated /efs/prox_cal) and then I did the chown & chmod. This permanently saved the values for me.
Summary - If echo'ing 0 & 1 into prox_cal is lost after a reboot, try the following before going to the effort to calculate the calibration value
Code:
$ su
$ echo 0 > /sys/devices/virtual/sensors/proximity_sensor/prox_cal
$ echo 1 > /sys/devices/virtual/sensors/proximity_sensor/prox_cal
$ chown system:system /efs/prox_cal
$ chmod 644 /efs/prox_cal
$ sync
YMMV
Click to expand...
Click to collapse
Just want to say that just performing these steps has fixed the problem. (which was that the sensor would turn the screen off and then would be stuck at " near possition" until the process using it was terminated and restared e.g a phone call)

I'm still watching on, but looks like it really works... in my case, my values were different and based on it I still had the problem, then I tried input 45 as in OP and it solved. Thank you very much for sharing!
Enviado de meu GT-I9500 usando Tapatalk

When I try this it says ussd code running..... Unable to process request.
Any idea why I can't access that menu?
Sent from my GT-I9505G using Tapatalk

I fixed my sensor by opening my phone and disconnecting the sensor and cleaning it from the inside! But good guide tho.

i changed the digitizer like twice.... then i start to have this issue when calling.... and i couldn't end the call because the screen won't turn on.... blowing air amazingly worked for me
Sent from dish washer

thank you
This is caused by dirt

[Q] Doubt about Shell commands

Hello,
Recently I changed my device. I had a Xperia S with Root and BusyBox installed, running with JB. Now I have a Xperia Z3 Dual without Root and BusyBox, running with KK.
Before I performed two commands Shell by Tasker and after the exchange I can no longer run them:
cat / proc // $ (pidof com.plexapp.android) / oom_adj
and
awk '! x [$ 0] ++' sdcard / Tasker / Torres / torre.txt> sdcard / Tasker / Torres / torreclean.txt
I believe the cat / proc, no longer work due to lack of Root and the AWK due to lack of Root and BusyBox.
Could someone confirm this information?
Or this is happening because of KK?
Is there any workaround?
I'm sorry for my English.

Wink-Relay touchscreen runs android 4.3

Unscrew the back cover.
Bottom right corner, under the green D1 LED there are 4 soldering pads,
Top to bottom, GND, RX, TX (Serial: 115200,N,8,1)
Use the RPI adafruit serial to USB cable and connect it as:
BlackGND-GND, GreenTX-RX, WhiteRX-TX , leave Red not connected.
Open a terminal in Linux and type:
$screen /dev/ttyUSB0 115200
Reset the board from the small button on the edge under the display.
Watch the Android boot messages.
You are root.
[email protected]_xxx:/ #
Tips:
wget,netstat,iperf,iwconfig,iwlist,su,wl
127|[email protected]_xxx:/system/xbin # getprop | grep edis
[build.edison.sig]: [20150520]
[edison-i7020h-corr]: [255=45,365=35,448=52,534=66,623=77,707=95,775=125]
[edison-i7020t-corr]: [-17]
[edison-runasroot]: [/data/edison/scripts/edison.sh]
[edison.backup]: [/device/edison.zip]
[edison.initialised]: [1]
[edison.otaenabled]: [0]
[edison.otafile]: [edison-ota]
[init.svc.edisonwink]: [running]
[init.svc.edisonwl]: [stopped]
[ro.build.description]: []
[ro.build.fingerprint]: []

Hacking from buttons
...factory mode by holding down top button upon reset get's to recovery menu.
flash to factory. ...
reboot the systemwait the wink app, cover light sensor and press the lower button for 1 minute or the relay clicks several times. Android OS desktop should appear. Connect the device over wifi to local network, find the device IP, then from a computer do adb connect device-ip:5554, the adb shell has root access.

wink relay version 2.3.1
marinapang said:
...factory mode by holding down top button upon reset get's to recovery menu.
flash to factory. ...
reboot the systemwait the wink app, cover light sensor and press the lower button for 1 minute or the relay clicks several times. Android OS desktop should appear. Connect the device over wifi to local network, find the device IP, then from a computer do adb connect device-ip:5554, the adb shell has root access.
Click to expand...
Click to collapse
Looks like version 2.3.1 has adb root access, just a bug
adb connect the-device-ip
adb shell
su
mount -o remount,rw /dev/block/mmcblk0p5 /system​
Of bring on front the android launcher
am start -n com.android.launcher/com.android.launcher2.Launcher​

This is a great find.
Is the Relay interface essentially an APK on top of the Android base?

mustardPersona said:
This is a great find.
Is the Relay interface essentially an APK on top of the Android base?
Click to expand...
Click to collapse
Yes
linux$ adb kill-server
linux$ adb connect 192.168.1.126
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
connected to 192.168.1.126:5555
linux$ adb shell
[email protected]_xxx:/ $ ps
USER PID PPID VSIZE RSS WCHAN PC NAME
.....
u0_a13 2881 2304 660344 21444 ffffffff 00000000 S com.android.inputmethod.latin
system 2898 2304 878728 44580 ffffffff 00000000 S com.quirky.android.wink.projectone
u0_a9 2903 2304 661576 20584 ffffffff 00000000 S android.process.media
wifi 2930 1 3192 1772 ffffffff 00000000 S /system/bin/wpa_supplicant
system 2940 2304 666764 18076 ffffffff 00000000 S com.android.settings
u0_a18 2956 2304 658464 16668 ffffffff 00000000 S com.android.music
system 2976 2304 659388 16176 ffffffff 00000000 S com.flex.edisonservice:edisonsrv
u0_a10 3000 2304 657908 15020 ffffffff 00000000 S com.flex.edison.edisonplayer
bluetooth 3031 2304 683660 21316 ffffffff 00000000 S com.android.bluetooth
u0_a5 3043 2304 657672 18116 ffffffff 00000000 S com.android.providers.calendar
u0_a8 3076 2304 660352 17680 ffffffff 00000000 S com.android.deskclock
system 3119 2304 656808 14868 ffffffff 00000000 S com.flex.edisonservice
u0_a11 3143 2304 661628 17848 ffffffff 00000000 S com.android.gallery3d
u0_a20 3158 2304 656756 15468 ffffffff 00000000 S com.android.onetimeinitializer
dhcp 3185 1 936 452 ffffffff 00000000 S /system/bin/dhcpcd
radio 3226 2304 656948 16872 ffffffff 00000000 S com.android.phone
u0_a14 3243 2304 660164 18068 ffffffff 00000000 S com.android.launcher
u0_a24 3261 2304 658488 16256 ffffffff 00000000 S com.android.quicksearchbox
u0_a19 3296 2304 656908 15016 ffffffff 00000000 S com.android.musicfx
shell 3405 2319 832 460 c004d9f0 4014ae1c S /system/bin/sh
root 3411 2 0 0 ffffffff 00000000 S kworker/0:0
shell 3412 3405 1152 460 00000000 40205060 R ps
[email protected]_xxx:/ $

wink relay issues, problems
I found several problems with the Wink application.
The UI sucks, the settings are one way.
After a power down the touch and switches are non responsive, then comes all in a blast. There is a lot of network activity. Junior level development ... all over.
If the network is slow the touch commands are delayed. Wink is relying the commands to Wink servers forward and back, instead doing it locally and updating the server asynchronous. Looks like the software was all developed in the far east, it sucks.

Thanks for the guide. I wonder what more practical things I can do with it like this. Great for visuals at the very least! Automate on :good:

thanks for the helps, it really works for me. thanks !

marinapang said:
I found several problems with the Wink application.
The UI sucks, the settings are one way.
After a power down the touch and switches are non responsive, then comes all in a blast. There is a lot of network activity. Junior level development ... all over.
If the network is slow the touch commands are delayed. Wink is relying the commands to Wink servers forward and back, instead doing it locally and updating the server asynchronous. Looks like the software was all developed in the far east, it sucks.
Click to expand...
Click to collapse
Actually, check if you have the latest Wink hub update - they added local radio support (I could be wording that wrong) and now certain actions can be done without going to the cloud. It is being deployed in waves, so it may not have hit all of them by now.
I wouldn't say it is more stable, but it definitely is quicker now.

Anyone have a system dump from the Relay?

johnny grep said:
Anyone have a system dump from the Relay?
Click to expand...
Click to collapse
I think this page used to have a rom dump. But the link looks broken. Let us know if you find a working one!
http://wink-internals.org/index.php?title=Relay#Rom_Dump

Progress?
Anyone make any further progress with this? Love the hardware but the software as already noted is terrible. Would be cool to install an intercom app to gain the functionality that wink promised but never provided.

The latest version of the Wink Relay firmware still has some form of root access via adb, but /system is read-only and I can't remount it. It used to work on the factory image.

dear Firehawk
i have a backup from my wink relay that i can share
made with adb pull

Relay backup
squeds said:
dear Firehawk
i have a backup from my wink relay that i can share
made with adb pull
Click to expand...
Click to collapse
I would like a copy of the relay backup if you still have it. Thanks.

If the factory ROM or a backup is available, I'd really like to get a copy too! It seems they lock things down with each subsequent update to the OS. Would like to have a way to revert should they cripple it too much.
Thanks!
Ben

I don't think there is a factory ROM, There is an Android FS factory image
in one of the partitions, which by default is not mounted.
Is a *.zip file, which from Recovery menu Option, Reset to factory
is flashed on top of the existent Image.
Can you get into recovery menu ?

So a factory reset flashes the Out of the Box image back on? That's interesting. Hmmn
I've never been able to get to the recovery screen.
Ben

Zottig said:
So a factory reset flashes the Out of the Box image back on? That's interesting. Hmmn
I've never been able to get to the recovery screen.
Ben
Click to expand...
Click to collapse
EDIT:
To get into recovery after the newest update:
Cover photoeye and press the top button
Press and release the reset button while holding the photoeye and top button.
You are in recovery mode
Now, I wish we could clean up the interface. Change brightness/colors at LEAST. We have these nicely sized color screens and they use all of 2-3 colors. Looks very bland.

What about resetting (bottom small button behind the bottom edge, accessible from bottom edge, pressit with your nail ... might need a guitar player nails) , while covering the motion sensor and:
1. try top button hold down then reset for .. until something happen (could play jessie girl / or go in recovery menu)
2. try bottom button hold down then reset, until something happen (could play jessie girl / or go in recovery menu)
2. try both buttons hold down then reset, until something happen (could play jessie girl / or go in recovery menu)
from recovery menu, reset to factory (one button navigates, one selects). If the factory image is the original one ( aka March .. May 2015) the switch to Android
procedure (while wink ap is running covering sensor and holding down button till relays click 3 times and you get android desktop / warning there is no back button, but an adb over wifi on 5554 or 5555 can help issuing keyevents ) works.
if they have been replaced the factory image during an update, there is a possibility that the feature is disabled.
I'll upload sometime this week the default factory image zip to some share location.

How do I root a Teclast Tbook 16 Power (M5F6) Tablet

Has anyone successfully rooted a Teclast Tbook 16 power (M5F6)?
How did you do it?
Solved:
downoal TWRP-2.8.7.0 for teclast Tbook 16 Power (M5F6) ver. beta03 on Needrom.com to ROOT your device
only for Boot via -> fastboot boot C:\TWRP-2.8.7.0_teclast_Tbook16Power-beta03.img
and Install SuperSU binaries ZIP.
unlock your Bootloader and change SELinuxMode ->
C:\tools>adb root
restarting adbd as root
C:\tools>adb shell
[email protected]_m5f6:/ # setenforce 0
Mod your boot.img ad to comand line -> androidboot.selinux=permissive
install SuperSU.apk
and install SELinuxModeChanger.apk to set SELinux back to "Enforcing"
now its ROOTed.
best regards.

Hello, thanks for the info, but I'm stuck by the end of the process.
I have reached as far as doing:
C:\tools>adb shell
[email protected]_m5f6:/ # setenforce 0
But after that I don't know how to go on or how to do the next couple of steps, could someone explain it 'dummy' style? So far I got no errors, but the tablet is not rooted yet.
Thank you very much!