Hi friends,
I am having a very weird situation here and I need your help.
My phone was working perfectly after the last time I have upgraded the rom which happened a couple days ago. Then yesterday I have discovered that my phone is turning on and off on its own. It turns on, then after a few seconds it turns off and then turns on again.
When I hard reset, it gets stuck at the smart mobility screen.
I can enter the bootloader screen by pressing the camera key and inserting the usb cable. The tri-color screen shows usb at the bottom left corner. When I run mtty, it says the usb port cannot open.
I know that it has sufficient power in the batteries (tried with two different batteries I have). However, when I plug it to a wall charger the charging light doesn't turn on.
So basically I have a tornado which cannot boot, mtty seems not able to recognize it. Is there any way to push an SPL, radio rom or OS rom to the phone? Is it possible to flash a tornado with an SDcard?
I really need some help here as I am out of ideas. thanks in advance.
Did you try hard resetting it? (While off holding both softkeys and then pushing the power button)? If so, flashing from card is possible...you just have to install the original ROM though. Google this: Tor_TMOUS_10140_191916_10900_SHIP.exe
Extract it then copy the nbf file to your memory card.
You may have to rename it and change the headers though...that I don't know
Here might help you by the way
http://forum.xda-developers.com/showthread.php?t=409286&highlight=original+rom
Good luck!
Your problem is more likely seems the power key is stuck.
thacen said:
Your problem is more likely seems the power key is stuck.
Click to expand...
Click to collapse
I am almost sure that this is not the case because I can use the power button for shutting the device off and restarting it, etc.
My only hope is to be able to flash from the SDCard now, as unforsakenrule mentioned. The problem is I need a step by step guide to do that.
burkay said:
When I run mtty, it says the usb port cannot open.
Click to expand...
Click to collapse
Did you disable the USB connection from ActiveSync properties?
I had had a similar problem which was solved after reinstalling the ROM.
NiTroGenious said:
Did you disable the USB connection from ActiveSync properties?
I had had a similar problem which was solved after reinstalling the ROM.
Click to expand...
Click to collapse
sure I did. The problem is no matter what the device is not recognized by the pc. mtty, activesync, tera term, etc. all fail whether usb connection is enabled or not. Weirdly, in the bootloader menu it says USB in the bottom left.
It really sucks, because I have the bootloader there but I cannot load anything to the device to recover it.
While it is in bootloader screen activesync couldn't connect or it could not detect your device. If you want to connect by teratermpro you need to disable USB connection from active sync otherwise teraterm could not connect your device.
I think your PC will not show you any connection symbol while connecting in bootloader but you may hear some sound while connecting or disconnecting.
One thing you can try is just try reflashing a stable rom by just running RomUpdateUtility. If it cannot find your device then check on your PC's Hardware device manager, if there is any unworking driver. if such driver is there just uninstall it and try connecting again.
May be it can solve your problem.
thanks for the advise, but I pretty much tried everything... everything except an SDCard flash. And that, I don't know how to do. I have been an HTC user for the last few years. This iMate SP5, which I owned a year ago, belongs to my sister now. I now have a Hermes, waiting for the prices to come down before ordering my touch pro. I flashed tens of roms in both devices, connected using mtty, teraterm etc. many times. This is the first time I am totally left clueless and I believe this is what we call a brick, indeed
Hello everyone.
Once upon a time i came to my TP and tried to activate the screen. nothing happened. Screen dead - only very faint backlight showed up. So i thought, maybe the ROM went bad somehow. So i tried soft reset. No change. I tried Hard-reset (which is not as easy when you dont see a thing). Now i thought, ok, just flash it again. BUT thats when the heavy thing came in. The USB cabel doesnt work. It does charge through the cable, but the PC doesnt recognize it at all. Anyone has an idea how i could get in connection with it? If i cannot bring up a USB connection will the guys at the repair factory be ale to connect somehow? I still have warranty (time-wise).
I will be gratefull for any idea on how to make the USB connection or how to flash without USB connection.
After some trying i found out that Windows somehow reserves USB slots for certain devices and after plugging the cable into different slot i managed to get a Sync and USB connection.
Then i faced the problem with returning "blinded" stock ROM and stock SPL. Thanks to the great guides here i managed to download a Stock ROM and flash it onto the Raphael. Then i faced the problem with putting in the Stock SPL, but it worked once i put the device into bootloader mode with Volume Down + reset.
So now i hope my device is as Stock as i bought it, and i will be sending it in for warranty repair or exchange. I hope its just some minor problem with display.
I have Android head unit sold by Witson, processor PX30, MX, MTCE. I did a big mistake and give rw permissions (with ES explorer) for all folders for my rooted head unit... After restart the unit did not work anymore. There is booting image on the display for appox. 40 second, after this unit shut's down. At least it seem to do so because at same time usb ports lost their power. So unit is not totally dead/ bricked but it wont boot or I can't enter recovery mode anymore.
My unit do not have any buttons (no hard or soft buttons) and there is no RST button.
I have try to enter recovery mode several times by keyboard with different key combinations ( alt / right alt + print scr + E or I) but with no luck. I also tried to flash firmware with SD-card or with USB-stick but without success. I also removed MCU or SOM and tried to flash it by OTG method but my SOM did not respond (PC did not recognice it) and I do not know how PX30 can be forced to Maskrom -mode?
Is there anything to anymore? How I can save my PX30 board, any good comments, please?
Timpuli said:
I
have Android head unit sold by Witson, processor PX30, MX, MTCE. I did a big mistake and give rw permissions (with ES explorer) for all folders for my rooted head unit... After restart the unit did not work anymore. There is booting image on the display for appox. 40 second, after this unit shut's down. At least it seem to do so because at same time usb ports lost their power. So unit is not totally dead/ bricked but it wont boot or I can't enter recovery mode anymore.
My unit do not have any buttons (no hard or soft buttons) and there is no RST button.
I have try to enter recovery mode several times by keyboard with different key combinations ( alt / right alt + print scr + E or I) but with no luck. I also tried to flash firmware with SD-card or with USB-stick but without success. I also removed MCU or SOM
and tried to flash it by OTG method but my SOM did not respond (PC did not recognice it) and I do not know how PX30 can be forced to Maskrom -mode?
Is there anything to anymore? How I can save my PX30 board, any good comments, please?
Click to expand...
Click to collapse
Good efforts made in trying to restore.
If your unit is an MTC(D/E) and the OTG cable is correct, with USB powering OK, forcing MASKROM should enable SOM connectivity via USB. To force MASKROM, typically there are two pads that must be shorted while powering on the SOM while connected to OTG.
Take a close look at the board for pads close to the eMMC/NAND. Attach a high res image here for further help.
Thank you for the comments so far. Yes, unit if MTCE and I think that OTG cable is fine also. I have even tried it with different resistors but SOM is not recognized by PC...
Here is some links for the pictures, it would be great if someone could help me find points where SOM can be forced to MASKROM mode.
https://drive.google.com/file/d/1WVujL00jDu6RYLzpD7xxoNL1gY_15R2-/view?usp=sharing
https://drive.google.com/file/d/1bF6Kxu1k3DtSquUenu508qXxL-CI2hGx/view?usp=sharing
https://drive.google.com/file/d/1ioM8vtH-zuU5seyLaBnt2qdzN02kNfNW/view?usp=sharing
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Timpuli said:
Thank you for the comments so far. Yes, unit if MTCE and I think that OTG cable is fine also. I have even tried it with different resistors but SOM is not recognized by PC...
Here is some links for the pictures, it would be great if someone could help me find points where SOM can be forced to MASKROM mode.
https://drive.google.com/file/d/1WVujL00jDu6RYLzpD7xxoNL1gY_15R2-/view?usp=sharing
https://drive.google.com/file/d/1bF6Kxu1k3DtSquUenu508qXxL-CI2hGx/view?usp=sharing
https://drive.google.com/file/d/1ioM8vtH-zuU5seyLaBnt2qdzN02kNfNW/view?usp=sharing
Click to expand...
Click to collapse
Hi, excellent hi-res images. I have annotated one of the images I believe are the Maskrom pads.
Sounds like you've had a thorough read through OTG threads, which explain the sequence - basically short while device is being plugged in/powered on by USB. nice one. Let me know how you get on.
marchnz said:
Hi, excellent hi-res images. I have annotated one of the images I believe are the Maskrom pads.
Sounds like you've had a thorough read through OTG threads, which explain the sequence - basically short while device is being plugged in/powered on by USB. nice one. Let me know how you get on.
Click to expand...
Click to collapse
Success!!! Thank you so much to encourage me! MASKROM pads confirmed for PX30, after shorting those pads SOM went directly to MASKROM and I was able to restore my system. Only problem is that only FW image what I found was Android 8.1 and my "bricked" android was 9.0 But even this is much better than bricked unit
I made also some other modifications before trying to MASKROM-mode and I'm not sure were there other issues before. Anyway, I made new OTG cable with a little bit thicker wires. I also changed resistor values from 12k // 22k to 6k // 11k. And finally I made dedicated pliers to short MASKROM pads.
Is there anything else to do for upgrade to Android 9 than use ModInstallerPro by Hal9k?
Thank you so much marchnz!!! You are great!
HELLO
please give me the .img software you wrote through otg / maskroom for px30
Timpuli said:
I have Android head unit sold by Witson, processor PX30, MX, MTCE. I did a big mistake and give rw permissions (with ES explorer) for all folders for my rooted head unit... After restart the unit did not work anymore. There is booting image on the display for appox. 40 second, after this unit shut's down. At least it seem to do so because at same time usb ports lost their power. So unit is not totally dead/ bricked but it wont boot or I can't enter recovery mode anymore.
My unit do not have any buttons (no hard or soft buttons) and there is no RST button.
I have try to enter recovery mode several times by keyboard with different key combinations ( alt / right alt + print scr + E or I) but with no luck. I also tried to flash firmware with SD-card or with USB-stick but without success. I also removed MCU or SOM and tried to flash it by OTG method but my SOM did not respond (PC did not recognice it) and I do not know how PX30 can be forced to Maskrom -mode?
Is there anything to anymore? How I can save my PX30 board, any good comments, please?
Click to expand...
Click to collapse
Sorry for late answer, I haven't noticed this... I hope that you have already find a proper .img file for yourself, but if not, I just downloaded some Android 8 installation package from 4PDA site. And when you unzip this package, usually there is .img file also. I haven't found any .img file to Android 9, so can't help with that, sorry.
Hello! @Timpuli, I am in the same kind of a problem that you had.Can you help me? I made the OTG cable but the SOM in the thread has 2 more rows and I don't know how to connect it to my PX30.Here's how I tried.Thanks!
Look at SOM board picture in topic https://forum.xda-developers.com/an...px3-5-headunit-mod-recover-flash-som-t3766892
In the third picture you can see that there is "two pins missing" at the left end of the socket... And if I remember right, in my PX30 SOM, there was socket all the way, like you wrote. So, you must take those missing pins into account, or start to calculate right pins starting from the pin 5...
Edit. Pin no. 1 is in top row/ left one pin. Pin. no 2 is in bottom row/ left one pin. And so on..
Timpuli said:
Look at SOM board picture in topic https://forum.xda-developers.com/an...px3-5-headunit-mod-recover-flash-som-t3766892
In the third picture you can see that there is "two pins missing" at the left end of the socket... And if I remember right, in my PX30 SOM, there was socket all the way, like you wrote. So, you must take those missing pins into account, or start to calculate right pins starting from the pin 5...
Edit. Pin no. 1 is in top row/ left one pin. Pin. no 2 is in bottom row/ left one pin. And so on..
Click to expand...
Click to collapse
So, they are like that?
PIN1 | PIN3 |
PIN2 | PIN4 |
And so on? On my SOM. Also, can you take a look at my cable, is it okay? Here is how I tried, I also tried to move all connections two rows to the right, still nothing.Also when I connect the orange leads to the SOM voltage goes from 3.14 to 1.7V. Is this normal? Thanks a lot for the fast reply, gotta get you a beer!
Yes, pins goes like that.
And if you make connection like in the picture it is wrong. You have to move pins two rows to the right, thats correct.
Your cable looks fine to me. I can't remember voltage values anymore, sorry.
I have some difficulties also and that's why I have to change resistor values from 12k and 22k to 6k and 11k. Also it might take couple of tries to enable to maskrom-mode.
Look at thread
https://forum.xda-developers.com/an...px3-5-headunit-mod-recover-flash-som-t3766892
again. So, there is said that voltage should be between 1.8 to 3.3V to 'tell' the SOM to go into OTG recovery mode. So, maybe 1.7V is too low...
Timpuli said:
Look at thread
https://forum.xda-developers.com/an...px3-5-headunit-mod-recover-flash-som-t3766892
again. So, there is said that voltage should be between 1.8 to 3.3V to 'tell' the SOM to go into OTG recovery mode. So, maybe 1.7V is too low...
Click to expand...
Click to collapse
It is 3,14V when it is not plugged to the SOM. when I plugged in it drops.Anyway, I am gonna try again! Thanks, if I have more questions I will ask you! I really appreciate that you helped and replied really fast.
Ok, I hope for the success. I assume that you have installed drivers already? Sequence to enter masrom-mode is:
1. Short maskrom mode pads and keep those shorted.
2. Plug in OTG-cable to usb-port...
3. When windows detects SOM-board remove shorting from the pads.
It might take several tries to have success to enter maskrom-mode. Have you checked is SOM-board detected in Windows device manager?
Yes I did. I will try again with MASKROM and check voltages on orange leads.I will keep you updated.
@Timpuli, I got it in MaskROM mode!Successfully connected, now I am searching for a rom with a .img. Once I find I will flash it and see if it works!Thanks so much!
Question. On the core board does anyone know what pins are for UART? slightly off topic but I've managed to boot a Ubuntu kernel on my px30 but it's a bit glitchy so would like to work out what pins are for serial console
Does anyone know what's happening here?.
So I've tried to flash a custom OS using maskrom, but the device keeps cutting the connection anywhere from 40% to 60% complete - it's driving me insane having tried about 15 times now to get it to flash.
Attached is my current maskrom setup....I'm trying to flash a Ubuntu based OS based on the Firefly px30 system.
Should all that fail, does anyone have the necessary files to maskrom my way back to android?
UKSFM99 said:
Does anyone know what's happening here?.
So I've tried to flash a custom OS using maskrom, but the device keeps cutting the connection anywhere from 40% to 60% complete - it's driving me insane having tried about 15 times now to get it to flash.
Attached is my current maskrom setup....I'm trying to flash a Ubuntu based OS based on the Firefly px30 system.
Should all that fail, does anyone have the necessary files to maskrom my way back to android?
Click to expand...
Click to collapse
MCU cuts power after a period.
Remove board from mainboard, use jig instead.
marchnz said:
MCU cuts power after a period.
Remove board from mainboard, use jig instead.
Click to expand...
Click to collapse
Ok will try.
I can't get it to work though, what pins should I use for the JIG.
Currently I have the following:
1 - 5V
3 - GND
20,28 - 15k resistor (1.2V)
29,30 - USB Rx, Tx
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!