I am trying to root a Lava Z60 phone, for which I try to enter fastboot mode. Using either "adb reboot bootloader" or powerbutton + volume up and selecting fastboot, I get to a blank screen. The device ID in USB changes to a different one from that of adb. I can see the device in dmesg as:
Code:
[30482.597989] usb 2-1.1: new high-speed USB device number 53 using ehci-pci
[30482.707638] usb 2-1.1: New USB device found, idVendor=0e8d, idProduct=20ff
[30482.707643] usb 2-1.1: New USB device strings: Mfr=3, Product=4, SerialNumber=5
[30482.707646] usb 2-1.1: Product: Android
[30482.707649] usb 2-1.1: Manufacturer: Android
[30482.707652] usb 2-1.1: SerialNumber: 0123456789ABCDEF
But when I run "fastboot devices" the result is empty ( I tested on Linux, windows and FreeBSD). To debug I downloaded the python version of adb and fastboot tools and put in some print statements for the data sent to the phone and returned by it . The library expects these values(settings) to be returned from the device in fastboot mode(they are hardcoded):
class = 0xff, subclass = 0x42, protocol = 0x03
Instead my phone returns:
class = 0x03, subclass = 0x00, protocol = 0x00
I tried changing the hardcoded values to the ones returned by the phone but it resulted in a USB error. So I think my phone is not properly entering fastboot mode. Why could that be, and how can it be fixed?
N30xda said:
I am trying to root a Lava Z60 phone, for which I try to enter fastboot mode..........
Click to expand...
Click to collapse
I don't have this device myself but, your best bet would be to check out one of the following Guides regarding Fastboot.
https://forum.xda-developers.com/showthread.php?t=3239537
https://forum.xda-developers.com/showthread.php?t=2277112
There's other similar Guides/Tutorials on the forum but, those should give you a good start for what you are looking to do. Don't be afraid to ask for some member guidance within one of them too.
Good Luck!
~~~~~~~~~~~~~~~
Unless asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Apple Macintosh.
How can i update my lava z 60 into android q pls tell
ASHOKJAIN said:
How can i update my lava z 60 into android q pls tell
Click to expand...
Click to collapse
Don't think stock Android Q firmware is available for this device. If available then you've to use SP Flash Tool in order to install it.
Related
ASUS TF201 / 64 gb. – No access to specific blob files.
I think I have APX mode after I run the below commands in Ubuntu
lsusb...
Bus 002 Device 085: ID 0955:7330 NVidia Corp.
and when I run
dmesg |tail
[15614.715848] usb 2-1.2: new high-speed USB device number 84 using ehci-pci
[15615.539331] usb 2-1.2: device not accepting address 84, error -71
[15615.539592] hub 2-1:1.0: unable to enumerate USB device on port 2
[15616.495015] usb 2-1.2: new high-speed USB device number 85 using ehci-pci
[15616.588212] usb 2-1.2: New USB device found, idVendor=0955, idProduct=7330
[15616.588224] usb 2-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[15616.588230] usb 2-1.2: Product: APX
[15616.588236] usb 2-1.2: Manufacturer: NVIDIA Corp.
[16007.391552] systemd-hostnamed[7142]: Warning: nss-myhostname is not installed. Changing the local hostname might make it unresolveable. Please install nss-myhostname!
[16008.688244] perf samples too long (2501 > 2500), lowering kernel.perf_event_max_sample_rate to 50000
I have tried Windows before Ubuntu, I was able to identify as APX in device manager but I could not understand and get any results, and decide to move to Ubuntu.
I appreciate if I can get straight answer that I can’t seem to find:
Since it’s visible as APX in ubuntu and Windows what are % chances to be recoverable?
I’m newbie and I have tried to learn as much as I can…but after a week of frustration I’m very down on energy, and lost …in commands that don’t seem to work as specified on forum.
I appreciate any help and direction on where should I start.
Newbie in need for help - Unknown BRICKED State….and Unknown how was bricked
ASUS TF201 / 64 gb. – No access to specific blob files.
I think I have APX mode after I run the below commands in Ubuntu
lsusb...
Bus 002 Device 085: ID 0955:7330 NVidia Corp.
and when I run
dmesg |tail
[15614.715848] usb 2-1.2: new high-speed USB device number 84 using ehci-pci
[15615.539331] usb 2-1.2: device not accepting address 84, error -71
[15615.539592] hub 2-1:1.0: unable to enumerate USB device on port 2
[15616.495015] usb 2-1.2: new high-speed USB device number 85 using ehci-pci
[15616.588212] usb 2-1.2: New USB device found, idVendor=0955, idProduct=7330
[15616.588224] usb 2-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[15616.588230] usb 2-1.2: Product: APX
[15616.588236] usb 2-1.2: Manufacturer: NVIDIA Corp.
[16007.391552] systemd-hostnamed[7142]: Warning: nss-myhostname is not installed. Changing the local hostname might make it unresolveable. Please install nss-myhostname!
[16008.688244] perf samples too long (2501 > 2500), lowering kernel.perf_event_max_sample_rate to 50000
I have tried Windows before Ubuntu, I was able to identify as APX in device manager but I could not understand and get any results, and decide to move to Ubuntu.
I appreciate if I can get straight answer that I can’t seem to find:
Since it’s visible as APX in ubuntu and Windows what are % chances to be recoverable?
I’m newbie and I have tried to learn as much as I can…but after a week of frustration I’m very down on energy, and lost …in commands that don’t seem to work as specified on forum.
I appreciate any help and direction on where should I start.
Thanks
reexon said:
Newbie in need for help - Unknown BRICKED State….and Unknown how was bricked
ASUS TF201 / 64 gb. – No access to specific blob files.
I think I have APX mode after I run the below commands in Ubuntu
lsusb...
Bus 002 Device 085: ID 0955:7330 NVidia Corp.
and when I run
dmesg |tail
[15614.715848] usb 2-1.2: new high-speed USB device number 84 using ehci-pci
[15615.539331] usb 2-1.2: device not accepting address 84, error -71
[15615.539592] hub 2-1:1.0: unable to enumerate USB device on port 2
[15616.495015] usb 2-1.2: new high-speed USB device number 85 using ehci-pci
[15616.588212] usb 2-1.2: New USB device found, idVendor=0955, idProduct=7330
[15616.588224] usb 2-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[15616.588230] usb 2-1.2: Product: APX
[15616.588236] usb 2-1.2: Manufacturer: NVIDIA Corp.
[16007.391552] systemd-hostnamed[7142]: Warning: nss-myhostname is not installed. Changing the local hostname might make it unresolveable. Please install nss-myhostname!
[16008.688244] perf samples too long (2501 > 2500), lowering kernel.perf_event_max_sample_rate to 50000
I have tried Windows before Ubuntu, I was able to identify as APX in device manager but I could not understand and get any results, and decide to move to Ubuntu.
I appreciate if I can get straight answer that I can’t seem to find:
Since it’s visible as APX in ubuntu and Windows what are % chances to be recoverable?
I’m newbie and I have tried to learn as much as I can…but after a week of frustration I’m very down on energy, and lost …in commands that don’t seem to work as specified on forum.
I appreciate any help and direction on where should I start.
Thanks
Click to expand...
Click to collapse
Sorry to say, but as you don't have the nvflash back up files APX mode is of no use to you, try buying a second hand motherboard of eBay and replacing it
Sent from my TF300T using XDA Premium HD app
Hi, suddenly (without any ROM flash attempt) my IAIWAI AW920 tablet got in a bootloop.
IIRC it's a RK3066 but the RKAndroidTool/Finn Flash Tool didn't recognized the tablet with either PWR Vol+ or PWR Vol- boot modes.
In the past I got the tablet successfully rooted through some tools, so in some past era I was able to communicate with ADB from the Android SDK (Linux Mint Kernel +3.10) but before it got soft-bricked I had not the USB debugging bridge set and due a failing HDD I lost that environment setup.
While being connected to my laptop through USB cable I can access two modes:
USB + PWR + Vol+: Blank black screen but I detect a USB device with VID: 10d6 PID: 10d6 that doesn't seems to be an adb client.
USB + PWR + Vol-: Appears a Fastboot kind of picture (Android mascot laying in the floor with his chest open and a Red Warning Symbol ) but no output whatsoever in [dmesg] or [udev monitor]
In neither these modes adb or fastboot detect something
---- For the Vol+ mode with the 10d6:10d6 device ----
I can't get adb or fastboot to work, even with adb_usb.ini edited in windows or linux or several different udev rules
The only udev rule I could trigger was
#IAIWAI
SUBSYSTEM=="usb", ENV{ID_VENDOR_ID}=="10d6", SYMLINK+="android_adb", MODE="0666", GROUP="plugdev"
Click to expand...
Click to collapse
But it seems android_usb is not a link to a proper block device (the last number increases on each test)
ls -l /dev/
android_adb -> bus/usb/001/010
Click to expand...
Click to collapse
Or at least I can't make it work with
adb -p /dev/android_adb devices
or
fastboot -s /dev/android_adb devices
Extra information of the device found in Vol+ mode
lsusb:
Bus 001 Device 003: ID 10d6:10d6 Actions Semiconductor Co., Ltd
dmesg:
[11102.331560] usb 1-2: new high-speed USB device number 10 using ehci-pci
[11102.464620] usb 1-2: New USB device found, idVendor=10d6, idProduct=10d6
[11102.464633] usb 1-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
udevadm monitor:
KERNEL[8596.157794] add /devices/pci0000:00/0000:00:12.2/usb1/1-2 (usb)
KERNEL[8596.158995] add /devices/pci0000:00/0000:00:12.2/usb1/1-2/1-2:1.0 (usb)
UDEV [8596.167280] add /devices/pci0000:00/0000:00:12.2/usb1/1-2 (usb)
UDEV [8596.171388] add /devices/pci0000:00/0000:00:12.2/usb1/1-2/1-2:1.0 (usb)
udevadm info --query=all --path=/devices/pci0000:00/0000:00:12.2/usb1/1-2/1-2:1.0
P: /devices/pci0000:00/0000:00:12.2/usb1/1-2/1-2:1.0
E: DEVPATH=/devices/pci0000:00/0000:00:12.2/usb1/1-2/1-2:1.0
E: DEVTYPE=usb_interface
E: ID_VENDOR_FROM_DATABASE=Actions Semiconductor Co., Ltd
E: INTERFACE=255/255/255
E: MODALIAS=usb:v10D6p10D6d0100dc00dsc00dp00icFFiscFFipFFin00
E: PRODUCT=10d6/10d6/100
E: SUBSYSTEM=usb
E: TYPE=0/0/0
E: USEC_INITIALIZED=434099056
udevadm info --query=all --path=/devices/pci0000:00/0000:00:12.2/usb1/1-2/1-2:1.0 --attribute-walk:
looking at device '/devices/pci0000:00/0000:00:12.2/usb1/1-2/1-2:1.0':
KERNEL=="1-2:1.0"
SUBSYSTEM=="usb"
DRIVER==""
ATTR{bInterfaceClass}=="ff"
ATTR{bInterfaceSubClass}=="ff"
ATTR{bInterfaceProtocol}=="ff"
ATTR{bNumEndpoints}=="02"
ATTR{supports_autosuspend}=="1"
ATTR{bAlternateSetting}==" 0"
ATTR{bInterfaceNumber}=="00"
looking at parent device '/devices/pci0000:00/0000:00:12.2/usb1/1-2':
KERNELS=="1-2"
SUBSYSTEMS=="usb"
DRIVERS=="usb"
ATTRS{bDeviceSubClass}=="00"
ATTRS{bDeviceProtocol}=="00"
ATTRS{devpath}=="2"
ATTRS{idVendor}=="10d6"
ATTRS{speed}=="480"
ATTRS{bNumInterfaces}==" 1"
ATTRS{bConfigurationValue}=="1"
ATTRS{bMaxPacketSize0}=="64"
ATTRS{busnum}=="1"
ATTRS{devnum}=="4"
ATTRS{configuration}==""
ATTRS{bMaxPower}=="128mA"
ATTRS{authorized}=="1"
ATTRS{bmAttributes}=="80"
ATTRS{bNumConfigurations}=="1"
ATTRS{maxchild}=="0"
ATTRS{bcdDevice}=="0100"
ATTRS{avoid_reset_quirk}=="0"
ATTRS{quirks}=="0x0"
ATTRS{version}==" 2.00"
ATTRS{urbnum}=="6"
ATTRS{ltm_capable}=="no"
ATTRS{removable}=="removable"
ATTRS{idProduct}=="10d6"
ATTRS{bDeviceClass}=="00"
looking at parent device '/devices/pci0000:00/0000:00:12.2/usb1':
KERNELS=="usb1"
SUBSYSTEMS=="usb"
DRIVERS=="usb"
ATTRS{bDeviceSubClass}=="00"
ATTRS{bDeviceProtocol}=="00"
ATTRS{devpath}=="0"
ATTRS{idVendor}=="1d6b"
ATTRS{speed}=="480"
ATTRS{bNumInterfaces}==" 1"
ATTRS{bConfigurationValue}=="1"
ATTRS{bMaxPacketSize0}=="64"
ATTRS{authorized_default}=="1"
ATTRS{busnum}=="1"
ATTRS{devnum}=="1"
ATTRS{configuration}==""
ATTRS{bMaxPower}=="0mA"
ATTRS{authorized}=="1"
ATTRS{bmAttributes}=="e0"
ATTRS{bNumConfigurations}=="1"
ATTRS{maxchild}=="5"
ATTRS{bcdDevice}=="0313"
ATTRS{avoid_reset_quirk}=="0"
ATTRS{quirks}=="0x0"
ATTRS{serial}=="0000:00:12.2"
ATTRS{version}==" 2.00"
ATTRS{urbnum}=="91"
ATTRS{ltm_capable}=="no"
ATTRS{manufacturer}=="Linux 3.13.0-37-generic ehci_hcd"
ATTRS{removable}=="unknown"
ATTRS{idProduct}=="0002"
ATTRS{bDeviceClass}=="09"
ATTRS{product}=="EHCI Host Controller"
looking at parent device '/devices/pci0000:00/0000:00:12.2':
KERNELS=="0000:00:12.2"
SUBSYSTEMS=="pci"
DRIVERS=="ehci-pci"
ATTRS{irq}=="17"
ATTRS{subsystem_vendor}=="0x1179"
ATTRS{broken_parity_status}=="0"
ATTRS{class}=="0x0c0320"
ATTRS{companion}==""
ATTRS{enabled}=="1"
ATTRS{consistent_dma_mask_bits}=="32"
ATTRS{dma_mask_bits}=="32"
ATTRS{local_cpus}=="00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000003"
ATTRS{device}=="0x4396"
ATTRS{uframe_periodic_max}=="100"
ATTRS{msi_bus}==""
ATTRS{local_cpulist}=="0-1"
ATTRS{vendor}=="0x1002"
ATTRS{subsystem_device}=="0xff1e"
ATTRS{numa_node}=="0"
ATTRS{d3cold_allowed}=="1"
looking at parent device '/devices/pci0000:00':
KERNELS=="pci0000:00"
SUBSYSTEMS==""
DRIVERS==""
Click to expand...
Click to collapse
I am trying to resurrect my old Samsung Galaxy i5500. A couple of years ago I tried installing some custom rom but failed and bricked the phone. The boot process halts at the Samsung logo (the very first logo to appear.)
Putting the phone into recovery mode (using the volume down button + center button + power button) works, at least i presume that it works - the logo with the android shoveling dirt and the word "Downloading..." beneath it appears - but neither adb nor fastboot can see the device.
My troubleshooting so far:
Code:
[email protected]:~# dmesg
...
[823736.755555] usb 2-1.1: new high-speed USB device number 6 using ehci-pci
[823736.851772] usb 2-1.1: unable to get BOS descriptor
[823736.857819] usb 2-1.1: New USB device found, idVendor=04e8, idProduct=6601
[823736.857829] usb 2-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[823736.857835] usb 2-1.1: Product: MSM7x27
[823736.857839] usb 2-1.1: Manufacturer: Sasmsung
[823739.903177] cdc_acm 2-1.1:2.0: ttyACM0: USB ACM device
[823739.903553] usbcore: registered new interface driver cdc_acm
[823739.903557] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[823761.102222] cdc_acm 2-1.1:2.0: failed to set dtr/rts
[email protected]:~# lsusb
...
Bus 002 Device 011: ID 04e8:6601 Samsung Electronics Co., Ltd Mobile Phone
...
[email protected]:~# adb devices
List of devices attached
[email protected]:~# fastboot devices
[email protected]:~#
I am running Lubuntu 12.04 on my laptop.
What do I need to do to be able to connect to the phone using adb and fastboot?
Thanks!
The "recovery mode" that you mentioned, is actually download mode and it's used to flash packages with Odin.
Use it to flash a custom recovery and then use that to flash a custom ROM. Format /system and /data as ext4 before flashing the ROM.
Sent from my LG G2 Mini using XDA Labs
I'm having problems with a Chinese tablet that I believe to be a Mediatek TAB910 with a MTK6592 processor.
It started by having problems with the SIM slots which I put down to a faulty SIM card. I obtained another from the telco but that didn't solve the problem. I concluded that the problem was with the SIM slots or with the software so I did a factory reset.
That appears to have gone well EXCEPT that I cannot get past the "Enter Privacy Protection password" screen (PPP). Let me say at this stage that I have never used PINs on my SIM cards; in fact, if I put a SIM card in which has a PIN then the screen asks for and accepts the SIM PIN but still presents the PPP screen.
I have tried to connect to the tablet by USB in order to try SP FLASH, but that tool doesn't see the tablet at all.
I then tried sudo dmesg|grep usb to see if there was any recognition of the USB and got the following results:
[237820.461318] usb 1-2: new high-speed USB device number 22 using xhci_hcd
[237820.611762] usb 1-2: New USB device found, idVendor=0e8d, idProduct=2000, bcdDevice= 1.00
[237820.611773] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[237820.611779] usb 1-2: Product: MT65xx Preloader
[237820.611783] usb 1-2: Manufacturer: MediaTek
[237823.266112] usb 1-2: USB disconnect, device number 22
[237830.885144] usb 1-2: new high-speed USB device number 23 using xhci_hcd
[237831.034440] usb 1-2: New USB device found, idVendor=0e8d, idProduct=2002, bcdDevice=ff.ff
[237831.034451] usb 1-2: New USB device strings: Mfr=2, Product=3, SerialNumber=4
[237831.034456] usb 1-2: Product: TAB910
[237831.034461] usb 1-2: Manufacturer: MediaTek
[237831.034465] usb 1-2: SerialNumber: 0123456789ABCDEF
[237831.038098] usb-storage 1-2:1.0: USB Mass Storage device detected
[237831.045186] scsi host2: usb-storage 1-2:1.0
[237831.471860] usb 1-2: USB disconnect, device number 23
Click to expand...
Click to collapse
It appears that the tablet is identifying itself, but immediately disconnecting again, hence no response from SP FLASH.
I can get the tablet to drop into two factory setting levels, one with English language instructions, the other with Chinese language instructions. Both of these appear to work as expected when I run through the menu items including, in the Chinese menu, "Eliminate eMMC".
I have also modified the udev files, but seemingly to no avail.
~$ cat /etc/udev/rules.d/80-persistent-usb.rules
SUBSYSTEM==”usb”, ACTION==”add”, ATTR{idVendor}==”0e8d”, ATTR{idProduct}==”2000“
SUBSYSTEM==”usb”, ACTION==”add”, ATTR{idVendor}==”0e8d”, ATTR{idProduct}==”2002“
~$ sudo service udev restart
Click to expand...
Click to collapse
My question is: Where do I go from here before I decide to bin this chablet.
TIA
For your reference.
https://visihow.com/Bypass_Privacy_Protection_Password_on_Android
James_Watson said:
For your reference.
https://visihow.com/Bypass_Privacy_Protection_Password_on_Android
Click to expand...
Click to collapse
Thanks for that but I have already been down that rabbit hole without success. My big problem is that the USB comes up but promptly disconnects again
Usually MTk preloader comport will disconnect if correct bootloader is not detected. So check you've got MTK6592 supported sp flashtool version and original firmware loaded. For privacy protection removal you need to format whole flash except bootloader and flash origin firmware then need to repair imei.
For some models you need to press and hold VOL+ or VOL- or both to get in to flash mode.