Hi,
Can anyone help me, why my bricked Flytouch (ePad) won't be recovered by manual flashing? (SD card flashing doesn't work, the tablet displays no picture, and only the green LED lights). Previous owner updated it with an incorrect SW.
I downloaded BurnTool, and 1170 update, connected the ePad to PC with USB cable (cable plugged into the top USB socket on the USB/Ethernet adaptor). PC recognizes, that there is an unknown USB device, but i cannot install Burntool's driver (32bit XP; it doesn't accept the driver for this device), or flash it with Burntool. (The status bar in Burntool window doesn't set to green).
It is not sure that is a Superpad or sg. ... I have some pictures of it, inside, and outside, but i actually cannot insert them... See on attachments, but they are limited to 640x480... I can send a better quality ones...
Code on the PCB is WMS-8088B, CPU board is WMS8060B2... i think it's a 256Mb-version, originally came maybe with Android 1.6.
Can anyone help me in this issue?
Related
Well for a while I thought my usb just died on my phone. I thought it got wrecked by physical damage like a power surge coming through mah pc when booting up and such...
But I just thought, well what the heck, and I flashed an old htc stock rom.
Now when I connected my phone to the pc, my touch pro gave me the 3 option screen.
activesync,sd,internet
But the pc did not detect any new hardware .
So I sadly flashed back to my energy rom. But al of the sudden when I wanted to connect my touchpro to the pc for charging, it asked me what to do (3 option scnreen), and the also detected my touch pro (well now my touchpro, it just saw something got connected).
So my pc tried ti install the drivers, it said it installed pockec sync usb something. But device center didn't notice any phone.
So I thought, too bad, but whne I disconnected the phone I heard a sound when disconnecting usb hardware.
Now the pc doesn't detect my touch pro when plugging in.
But this is proof it isn't physical damage (atleast I think).
Cause of the usb failure.
I was flashing a couple of months ago, when it suddenly started to stop at the middle. (each time it was another point so no damaged rom).
so I was able to flash it form my pc that time, but the times after that I had to flash from sd. Also when I tried to connect my phone, the pc lost connection with the phone after 40 secs.
Does someone know what to do? Please help me, usb is kinda important .
Btw, I have got this problem at every pc, also with every cable.
And now windows keeps saying an unkown device connected.
And shortly after windows detected my phone it undetects its.
(i hear two beeps in a row)
Yes I have disabled fast usb to pc
I forgat to mention that my pc doesnt reconize the device,
and with this rom my touchpro doesn't know it is connected
(It doesnt want to sync or anything), doesnt see it got plugged in.
Is there n1 here wich knows the solution??!
This problem is caused by damaged mini usb port on your device.
Actually this this new mini usb with 11 pin used in Touch Pro in & many other HTC device has a very delicate & thin plastic piece in middle. Quite visible from outside, this acts both as separator for the 2 layered pins of mini usb & base for connectors when u insert a usb to connect a pc or the audio cord.
This small plastic separator gets cracked if you do not handle usb connections properly.
Now here is the solution -
1.Remove battery
2.Look into mini usb port on device, see if there is a crack in between
3.If yes take a fine needle just press the cracked part so that the whole piece gets leveled.
4. Then you can put a small drop of quick drying fixer at the outer tip of this plastic part,take care it doesn't go inside otherwise it will create a layer on connecting plates.
Hope it helps you.
Hi, I have recently purchaced a Giada Q11 Mini and am having some wierd issues with it.
If anyone can help me with this, it would be great.
The issues are as followed:
-Cannot install any apps, apparently there's "System Storage" which is completely filled, and "Flash Storage" which has practically nothing.
-Settings do not save. Once it's turned off and turned back on, it looses all it's settings. I suspect it's due to the issue above.
-Cannot enter any form of recovery. If i press the recovery button, all it does is stall the booting of the Q11.
-No visible way of connecting to a computer for ADB usage. I have read through the manual and the only thing in it is that it has USB OTG through the mic port for some reason. I have tried a jerry rigged usb (white & green) to 3.5mm headphone connector (tip & ring) and connected it to my computer. my computer "seems" to detect it but throws a unknown usb device error on it.
It's a really nice device and I would love to use it as a home theater device but due to the issues above, it stands to say that I cant even use it for anything other than a cheap toy...
If I can install root, i can see if i can junction the /data folder to the sata drive that i have installed in it.
It runs android 4.0.4 but without adb or any form of recovery, i cant seem to do anything with it...
Here's what the device is: http://www.newegg.com/Product/Product.aspx?Item=N82E16856660005R
Any help is appreciated.
So some good news and some bad news:
Good news:
-it has an allwinner A10 cpu
-can boot off the sd card
-successfully booted a linux image for a MK802 found here: http://liliputing.com/2012/07/linux-distributions-that-can-run-on-an-mk802-mini-pc.html
Bad news:
-cant see the internal flash nor the sata drive installed in it.
Anyone have any ideas?
So good news, apparently the blue USB 3.0 port on the right side of the device is the OTG port and was able to flash a firmware on it and it is now working magnificently.
Don't remember doing anything special, but the tab no longer boots. Charging light turns green, I've tried all sorts of power/volume button presses without success. The screen stays completely black. Interestingly (?), when I plug it into my laptop USB, it recognizes the device, but I can't mount it, adb doesn't work (ubuntu box). Here's the dmesg output:
Code:
[165629.593151] usb 4-2: new full-speed USB device number 3 using ohci-pci
[165629.751635] usb 4-2: not running at top speed; connect to a high speed hub
[165629.761646] usb 4-2: New USB device found, idVendor=0955, idProduct=7330
[165629.761653] usb 4-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[165629.761657] usb 4-2: Product: APX
[165629.761660] usb 4-2: Manufacturer: NVIDIA Corp.
that looks like vol-up power on (black screen on tab and APX mode on commputer).
if you have NVflash backup this is the time to use it, if you dont have those files already I'm affraid you are screwed.
each tab needs different files for NVflash (generated on said tab first) so no one would be able to give you their files
No, this was my stock device. Haven't messed with it at all. Looks like this sort of bricking is common with this tab? I had another with a broken screen, so I swapped motherboards and all is well. However, I this and another stock 301t. What should I do to recover from this situation should it happen again?
search for NVflash backup here on forum. Those files generated and storred in few safe locations (dropbox, google drive, laptop, usb stick ...) makes your tab virtually unbrickable (unless phisical damage). NVflash is pretty much starting from scratch - like you have chips on motherboard fresh of their separate boxes and just soldered together, no code on them at all. Restoring files from NVbackup breathes new life to tablet.
You will need unlocked bootloader and possibly root to gather needed files, and they will work only for certain motherboard (I would say chips fingerprint is somewhere on those files). It is worth it if you plan to mess around flashing new stuff on the tab. If it was just stock tab and you didn't flash anything before it started acting like that It is possible that one chip died and there was no bootloader to be found to start booting process.
Hello,
i have a big problem with an Allview windows 10 tablet, during windows 10 reset i got a blue screen and my tablet got stuck into a boot loop restarting after windows logo appears. It didnt boot from windows usb stick that i made with rufus in multiple ways with different settings and when i was trying to get it boot from usb i accidentally disabled XHCI or EHCI from bios ,the attached keyboard does not respond, otg cable connected keyboard does not respond, touch not working.
Any solution will be greatly appreciated,
Thank you.
The only option I can suggest is to open it up, desodder the battery (as it's soldered to the motherboard). Wait for a couple of minutes (maybe even hours) and then solder the battery back in and see if the BIOS has been reset.
This may work similarly to taking out the CMOS battery and putting it back in.
I can provide you with this info as I've just stumbled upon your post having the same issue as you. I haven't yet tried this method as I don't have the tools required to desolder the battery right now but I'll post an update as soon as I can to let you know if it worked.
There's also a debug header available on the board but no resources online on how to use it.
Hello people,
I bought a used TrekStor Surftab theatre L15 TFMTKAW01232 and the MT8163 in the hope that I can repair it.
The problem with the device is that it is not possible to boot and after pressing the Volume + and On button for some time, I get into the boot menu. Here I have the choice of recovery, fastboot, norma bootl. No matter which selection I make, the tablet remains dark and nothing happens next.
I got myself a USB-A to USB-A cable and searched for the original Rom and found it. When trying to flash it with the SP_Flash_Tool I get the error "ERROR: S_BROM_CMD_JUMP_DA_FAIL".
What I notice is that the device seems to stay connected via USB only very briefly. I have already installed several drivers and in the tool it also shows me
the connected device "MediaTek USB Port_V1633 (COM4 on)".
Do you have any other idea how I could solve the problem?
Hi,
could you help me please?
I have here same model as you mentioned for repair.
A reverse polarity power source was attached to it, which resulted in a burned chip.
That chip I am unable to identify because it was destroyed.
I am attaching a photo of the mainboard where I've marked the position of that chip.
Would it be possible for you to have a look at your board and take a picture of the chip for me?
I would really appreciate it!
Thank you!