Trouble with Cheap Chinese Chablet - Android Q&A, Help & Troubleshooting

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.

Related

USB stopped working - doesn't charge or mount internal memory

I have noticed this morning that while my Xperia S is connected via USB cable to the PC it does not charge, ie. it indicates charging but battery level goes down rather than up. Also I've noticed that my OS (Fedora 16) stopped mounting Xperia's internal memory. Dmesg output is just that:
Code:
[34723.804074] usb 2-1.2: new full-speed USB device number 61 using ehci_hcd
[34723.877051] usb 2-1.2: device descriptor read/64, error -32
[34724.050920] usb 2-1.2: device descriptor read/64, error -32
[34724.224867] usb 2-1.2: new full-speed USB device number 62 using ehci_hcd
[34724.287808] usb 2-1.2: device descriptor read/64, error -32
[34724.461715] usb 2-1.2: device descriptor read/64, error -32
[34724.635655] usb 2-1.2: new full-speed USB device number 63 using ehci_hcd
[34725.037264] usb 2-1.2: device not accepting address 63, error -32
[34725.110414] usb 2-1.2: new full-speed USB device number 64 using ehci_hcd
[34725.512050] usb 2-1.2: device not accepting address 64, error -32
[34725.512180] hub 2-1:1.0: unable to enumerate USB device on port 2
Did a bit of research around the interwebs, found advice to clear data of the MtpApp app (settings -> applications -> all -> MtpApp), which I did but that didn't solve the problem, yet dmesg output changed a bit:
Code:
[34734.683275] usb 3-1: new full-speed USB device number 67 using xhci_hcd
[34734.686432] usb 3-1: Device not responding to set address.
[34734.890333] usb 3-1: Device not responding to set address.
[34735.091046] usb 3-1: device not accepting address 67, error -71
[34735.243993] usb 3-1: new full-speed USB device number 68 using xhci_hcd
[34735.247164] usb 3-1: Device not responding to set address.
[34735.451046] usb 3-1: Device not responding to set address.
[34735.651757] usb 3-1: device not accepting address 68, error -71
[34735.804727] usb 3-1: new full-speed USB device number 69 using xhci_hcd
[34735.807836] usb 3-1: Device not responding to set address.
[34736.011768] usb 3-1: Device not responding to set address.
[34736.212469] usb 3-1: device not accepting address 69, error -71
[34736.365416] usb 3-1: new full-speed USB device number 70 using xhci_hcd
[34736.368521] usb 3-1: Device not responding to set address.
[34736.572448] usb 3-1: Device not responding to set address.
[34736.773180] usb 3-1: device not accepting address 70, error -71
[34736.773208] hub 3-0:1.0: unable to enumerate USB device on port 1
Seems to also depend on the USB port I use in my laptop, ie. in one port it says "Device not responding", while on the other "device descriptor read/64, error -32". UPDATE: On double check it seems like USB 3.0 ports saying "not responding", while USB 2.0 port returns "descriptor error".
I obviously tried rebooting (including hard-reboot with volume-up key held), tried different cables, different PCs, including Windows one which just popped a balloon saying something about "unrecognized device". Nothing seems to rectify the issue. Needless to say it was working perfectly up until today.
Thankfully, it seems that's a software-related issue rather than physically borked USB port as I successfully managed to put device into flashmode (volume-up + usb plug). UPDATE: Unfortunately, even if physical plug to the port is recognized and green or blue light comes up, dmesg still returns "descriptor errors" and device is turning itself into charging-only mode (I initially thought just seeing blue/green light means either of modes is entered).
Running out of ideas what else I could do to get USB work again, apart from hard reset. Any suggestions more than welcome.
UPDATE: Out of the sudden, after 1525th reboot cycle somehow charging via USB cable works fine again, however internal storage is still not mounted to the PC. Doh! I guess I'll end up with warranty repair/replacement.
FINAL UPDATE: USB port died completely, plugging USB cable to the PC doesn't trigger any dmesg activity at all and handset after a while of doubt recognises connection as a standard wall charger. Sorting out warranty replacement as we speak.
Have you tried cleaning of the USB port/connector (of your phone)?
cognosco said:
Have you tried cleaning of the USB port/connector (of your phone)?
Click to expand...
Click to collapse
No, I haven't, but I doubt that's the case, as it wouldn't enter flashmode either.

Diag mode in Galaxy S2

I was trying to restore IMEI and stuffs using QPST.
1. *#7284# and selected USB-> Modem
2. Connected to Windows XP, Device Manager shows 7CDCs as the device with yellow mark showing cannot install device.
3. Tried almost every drivers on the earth.
Connecting this to a linux pc i found the following logs:
103722.210314] usb 1-8: default language 0x0409
[103722.212814] usb 1-8: udev 15, busnum 1, minor = 14
[103722.212817] usb 1-8: New USB device found, idVendor=1519, idProduct=0020
[103722.212821] usb 1-8: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[103722.212824] usb 1-8: Product: 7 CDCs
[103722.212827] usb 1-8: Manufacturer: Comneon
[103722.212829] usb 1-8: SerialNumber: 004999010640000
[103722.212964] usb 1-8: usb_probe_device
[103722.212969] usb 1-8: configuration #1 chosen from 1 choice
Doing some dirty digging I found the following in Samsung open source code:
/drivers/usb/core/quirks.c
/* IMC_MAIN - XMM6260, XMM6262 */
{ USB_DEVICE(0x1519, 0x0020), .driver_info = USB_QUIRK_HSIC_TUNE },
I dont see many people reporting this problem.
I saw the same behaviour with Galaxy R too that in diag mode, it is sending idVendor=1519, idProduct=0020.
Anyone faced this before? Any help would be great.
Hey mate, did you ever find a solution to this problem? Im also having trouble connective my phone to QPST.
Hello friends,
I am facing same problem with SGS2.
Please help.

[Q] 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.

[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

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

Categories

Resources