LazyPanda problem.. soft bricked? - Sprint HTC EVO 4G LTE

HTML:
Hey all,
So after successfully going S-off on my own phone, I was unable to do so on a friends. The problem now it seems is my linux box does not see the phone as /dev/ttyusb0 when plugged in.
lsusb shows as:
Code:
Bus 001 Device 016: ID 05c6:9008 Qualcomm, Inc.
But I am unable to complete the LazyPanda Unbricker because it does not see my phone. ADB devices does not show it either.
I have run modprobe qcserial many many times, as well as plug and unplug, hold power for 30 seconds etc etc to no avail but no /dev/ttyusb0.
So what are my options here? Any advice would be greatly appreciated. Really frustrated.
Upon further investigation the Qualcomm USB modem is registering
Code:
[11087.431154] usbcore: registered new interface driver usbserial_generic
[11087.431160] usbserial: USB Serial Driver core
[11087.434594] USB Serial support registered for Qualcomm USB modem
[11087.434839] usbcore: registered new interface driver qcserial

For the archives:
I was able to get the unbricker to work finally by using a different distro. Apparently older versions of Ubuntu server don't work. You must unplug any usb to serial converters as well because they will be bound to /dev/ttyUSB0.
run
Code:
sudo modprobe -r qcserial
Plug your phone in then run
Code:
modprobe qcserial
type dmesg and look to see if your phone is bound to /dev/ttyUSB0
if it is, you are good to go.
Hope this helps anyone who had the same issue as I did.

Related

[Q] adb devices (Ubuntu) does not show device after upgrade to ICS

Hi!
I got OTA update to ICS today, and everything went smooth. The phone is working fine. I connect it to iMac, run adb devices, and there is see my device. I'm also using vmware fusion with Ubuntu, where I develop Android apps. Ubuntu does not see this device. Previously, it worked fine. Yes, the device is connected and configured to be available to guest machine.
dmesg and lsusb output follows:
[email protected]:~$ lsusb
Bus 002 Device 005: ID 0e0f:0008 VMware, Inc.
Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[email protected]:~$ dmesg
[ 3751.650501] hub 1-0:1.0: unable to enumerate USB device on port 1
[ 3763.141707] usb 1-1: new high speed USB device using ehci_hcd and address 46
[ 3778.252927] hub 1-0:1.0: unable to enumerate USB device on port 1
[ 3778.936251] usb 1-1: new high speed USB device using ehci_hcd and address 47
[ 3794.048386] hub 1-0:1.0: unable to enumerate USB device on port 1
Does anybody know what is going on?
Thanks!
Regards,
Miha.
Am I the only one having this problem? Any other Ubuntu users with Galaxy S2 and ICS update?
On the phone. Go to setttings/Wireless and networks/USB utilities/connect storage to PC.
bored_stupid said:
On the phone. Go to setttings/Wireless and networks/USB utilities/connect storage to PC.
Click to expand...
Click to collapse
This disables USB debugging. I did it anyway, but it still does not show up. Unfortunately.
I solved this by editing Ubuntu.vmx file. I added the following lines (I believe the last line makes a difference):
Code:
usb.quirks.device0 = "0x4e8:0x681d skip-reset" # Mass Storage
usb.quirks.device1 = "0x4e8:0x68a9 skip-reset" # Media
usb.quirks.device2 = "0x4e8:0x6877 skip-reset" # Kies
usb.quirks.device3 = "0x4e8:0x6866 skip-reset" # SGS2 ICS

[Q] Unknown BRICKED State….and Unknown how was bricked

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

ADB sees device but cannot connect

Hello, I m after some help.
I ve got an Allwinner A20 tv box, it worked fine for a few months then one day, after being on (but idle) for a few hours, I noticed the screen was blank but the light on the front was blue (indicating it was on, red is standby). It would not respond to the remote control or to anything, so I unplugged it and since then it will not boot and the screen is blank, the red light will light up but that is it. I ve eliminated the remote controller not working, but I cant boot the device.
So I ve tried connecting via ADB (with Ubuntu) but I cant get the device to show up after typing "adb devices".
I can get the vendor id and device id and I ve added it and the manufacturer to udev/modeswitch devices, but when I type "sudo usb_modeswitch -v 0x1f3a -p 0xefe8 -S -R -W"
I get the following error:
~/Android/sdk/platform-tools$ sudo usb_modeswitch -v 0x1f3a -p 0xefe8 -S -R -W
Take all parameters from the command line
* usb_modeswitch: handle USB devices with multiple modes
* Version 2.1.1 (C) Josua Dietze 2014
* Based on libusb1/libusbx
! PLEASE REPORT NEW CONFIGURATIONS !
DefaultVendor= 0x1f3a
DefaultProduct= 0xefe8
SierraMode=1
NeedResponse=0
Look for default devices ...
found USB ID 048d:1336
found USB ID 1d6b:0002
found USB ID 19a8:2036
found USB ID 1f3a:efe8
vendor ID matched
product ID matched
found USB ID 1d6b:0001
found USB ID 062a:0102
found USB ID 1d6b:0001
Found devices in default mode (1)
Access device 004 on bus 003
Current configuration number is 1
Use interface number 0
USB description data (for identification)
-------------------------
Manufacturer: not provided
Product: not provided
Serial No.: not provided
-------------------------
Send Sierra control message
Error: Sierra control message failed (error -7). Abort
I ve searched Google for the error code but I cannot find anything.
The device was rooted and USB debugging was on.
Any help would really be appreciated.
Thanks

Connecting to i5500 using adb and fastboot on Linux

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

Trouble with Cheap Chinese Chablet

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.

Categories

Resources