5.0.0.77 Recovery mode

Bug Reports
1

REPRODUCIBILITY: Always
OS VERSION: 5.0.0.77/5.1.0.7
HARDWARE: X10II
UI LANGUAGE: EN
REGRESSION: Yes?

DESCRIPTION:

I am unable to ping 10.42.66.66 and forward, hence tethering does not work.

PRECONDITIONS:

Boot to recovery.

STEPS TO REPRODUCE:

  1. Got to fastbootmode
  2. fastboot flash boot_a hybris-recovery.img
  3. fastboot flash boot_b hybris-recovery.img
  4. fastoot recovery
  5. go to shell an ping

EXPECTED RESULT:

Be able to run tethering in recovery mode.

ACTUAL RESULT:

Be able to ping even 10.42.66.66

MODIFICATIONS:

All

ADDITIONAL INFORMATION:

bash-5.0# ip address
1: lo: mtu 65536 qdisc noop qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: bond0: <BROADCAST,MULTICAST400> mtu 1500 qdisc noop qlen 1000
link/ether 76:10:6a:87:86:a8 brd ff:ff:ff:ff:ff:ff
3: ip_vti0@NONE: mtu 1480 qdisc noop qlen 1000
link/ipip 0.0.0.0 brd 0.0.0.0
4: ip6_vti0@NONE: mtu 1500 qdisc noop qlen 1000
link/tunnel6 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00 brd 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00
5: sit0@NONE: mtu 1480 qdisc noop qlen 1000
link/sit 0.0.0.0 brd 0.0.0.0
6: ip6tnl0@NONE: mtu 1452 qdisc noop qlen 1000
link/tunnel6 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00 brd 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00
7: usb0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 7e:54:e1:7c:d4:0f brd ff:ff:ff:ff:ff:ff
inet 10.42.66.66/29 brd 10.42.66.255 scope global usb0
valid_lft forever preferred_lft forever
inet6 fe80::7c54:e1ff:fe7c:d40f/64 scope link
valid_lft forever preferred_lft forever

bash-5.0# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
10.42.66.64 0.0.0.0 255.255.255.248 U 0 0 0 usb0

bash-5.0# ping 10.42.66.66
PING 10.42.66.66 (10.42.66.66): 56 data bytes
^C
— 10.42.66.66 ping statistics —
2 packets transmitted, 0 packets received, 100% packet loss

2

What makes you believe it is a SFOS bug as opposed to something else?

3

I am not sure indeed but this it is a very limited environment.

4

Then assume it is something on your end and troubleshoot accordingly - don’t assume it is a SFOS bug, and especially don’t wait for it to be “resolved”.

5

To reboot to SFOS recovery (after flashing the hybris-recovery.img), use fastboot reboot instead of fastboot reboot recovery.

That’s because SFOS Recovery is flashed onto boot partition, not recovery partition.

1 Like