Anyone know how to kick this tablet out of limbo and get it to boot at all? I accidentally flashed a different preloader on my LeapFrog Epic and while I am still able to get it detected and thus flash firmware images to it using SP Flash Tool v5.1532.00, it is basically unable to switch back to normal mode and kick in the preloader whenever I plug it in whilst the device is off. Tried flashing a known clean backup - still no dice. I know there's a thread about unbricking MTK devices and it does mention the USB COM port issue, but said thread is locked and thus I am forced to make a new one about it. Short of shorting testpoints and such (pun intended ), is there anything else I can do at this point?
Can anyone help?
Related
Hi all,
I have a Star/Bluebo B6000 phone which I believe is based on the MediaTek 6589T.
I followed the procedure here: http://forum.xda-developers.com/showthread.php?t=2206421
to set up a new ROM for the phone.
I seemed to have gotten it all done properly, but the phone only stays connected for about 2 seconds. The SP Flash tool moves into the red progress bar and then just fails.
Luckily, there isn't any software damage on the phone (from the look of it).
I'm trying to put in a new ROM to actually fix a previous issue where my phone remains on but when I press the home button or the power button the screen stays blank. Think a new ROM/fresh start may solve this.
But the core issue is that I am unable to put in a new ROM because the phone doesn't remain connected long enough.
Is there a solution to this? Or is there another way to install ROMS?
Thanks.
There are several things the issue could be.
Try running SP Flash Tools as Admin.
Try a different USB cable.
Try uninstalling current drivers and using PDANet VCOM USB drivers
Try a different PC
Try MTK Flash Tool as opposed to SP Flash Tool.
Make sure the scatter is correct. Create a new scatter with MTK Droid Tools
None of them work.
I've tried 4 different cables. MTK and SP tools.
It seems as though something is wrong with my preloader. When I try to 'restore factory settings' or even try to restart in recovery mode, the phone doesn't do anything. It's almost as though these modes don't exist or are bugged/busted.
EDIT: Yes, it seems to be some kind of preloader issue. When the phone is OFF, I connect the USB (which the computer recognises) and the within 2 seconds the 'disconnect' sound comes up. Within 2 seconds after that the battery charging shows up on the phone.
I say this because when the phone is ON, I am able to transfer files onto the phone and treat the phone as a normal connection. Something within the phone's software is causing SP Tools/MTK Tools/Other drivers not connect to it. I have a feeling I may have a corrupt/broken preloader/recovery system.
Thanks for the help. Please do advise as to what I can do.
Anyone?
Really could use some help.
vika09 said:
Anyone?
Really could use some help.
Click to expand...
Click to collapse
Hi, did you manage to get this sorted?
Some wanker had posted wrong images for boot and recovery for S6000L. And since I'm a moron, i didn't take the files apart to check them.
Installing them bricked my tablet. So essentially I have no boot or recovery images on the device and was wondering if there's any way to revive it.
Tablet freezes if i start it in normal, fastboot or recovery modes, so that's out of the picture.
However, i think that "meta mode" still works (if indication of it working is displaying lenovo logo and having "meta mode" written on the bottom of the screen)
It's getting detected on "mediatek preloader usb vcom port" for a couple of seconds when connected to the PC, which means that i might be able to use adb to push a backup into the tablet (?)
Been scouring the internet for a while with no results. Is there, by any chance, anyone who can help me out?
Hello,
I recently found my old Droid Razr Maxx again and wanted to know if any of you know a way to restore it to its former glory, so to say.
I jumped into a lake with it after forgetting that it was in my pocket a few years ago and ever since, the data parts of USB have been dead. I continued to use it for some time after the accident, but unfortunately I managed to soft-brick it with no way to re-flash the firmware with RSD Lite.
Connecting a regular USB cable to the device with the battery removed just lights up the white LED, which indicates that it receives power over USB, but not enough to boot. When I use a factory cable, the device boots, which leads me to the conclusion that pin 1 and 4 still work like they should.
The device then gets stuck on the Motorola bootsplash, but I'm able to get into the bootloader, fastboot mode, and stock recovery with the key combos. I already tried to place a few signed .zip's (OTAs) on the SD card and flash them through the stock recovery, but all .zip's I've tried so far fail as they check system files of the current ROM that are supposed to be in place. They just include the incremental update parts anyway, so I don't know if they would help, even if I could install them.
I wrote a small script that executes "fastboot devices" every second, booted into fastboot and tried to connect the USB data pins directly to the lines that go into the motherboard (in case just the port is corroded), but I've had no luck so far, as it doesn't get recognized. I tried to connect to the Test Points near the microUSB port in various combinations, hoping that they are connected to the data pins, but my Razr just reboots in most cases, or does nothing. It still doesn't get recognized.
Does anybody know how I could get a working firmware on the device? :silly:
Here are some images: https://imgur.com/a/oz3bo
Hi,
I've got a Nubia N1 Lite (NX597J) to mess around with, and wanted to try modifying the ROM. I can enter developer mode and allow bootloader unlocking, adb also works. What I can't do is use USB while booting, or in the recovery menu. No fastboot or sending ROM images via adb to the recovery software. The phone doesn't connect to the computer at all (I'm using Linux, it should at least show up in dmesg). Recovery log says
Code:
musb_pullup 2498: no USB cable, don't need to turn on USB
A couple times, even though the cable is connected and works in Android proper. I've tried USB2 and 3 ports, on a hub and directly on the motherboard. It shows up as 0e8d:2000 MediaTek preloader when turned off and, very briefly, as 0e8d:2008 when booting into recovery.
Am I missing something, or is the recovery image just broken on this phone? I've tried both the EU and US firmware, which is a bit more recent.
Do I need some tool that interacts with the preloader, maybe? I have found this guy who's been messing with a phone that has the same SoC.
Have you managed to get it into recovery mode? I just get a dead android picture :/
I've accidentally broken it by flashing the US ROM but my phone is the EU version. Boots up okay but has lost the IMEI and once the screen turns off won't turn on again - unless I reboot it.
Have so far failed to re-flash with the correct EU ROM - it just fails half-way through.
No, and I'm in the same situation with the firmware.
I have a thl knight 2, I tried to flash twrp and it's stuck in a bootloop. I can't connect trough adb, fastboot but I saw some ports in device manager. I downloaded mediatek drivers. As far as I know when I connect the phone it should be detected by the droid tools or sp flash tool but it isn't. All the drivers pop up, I tried setting them to mediatek DA USB VCOM (Android), Mediatek USB VCOM (android) and Mediatek PreLoader USB VCOM (Android) but still it doesn't find the phone. I can't use recovery and can't enter fastboot. My volume up key used to lower the volume instead so maybe they are both mapped to volume down? I have a orange state message on the android logo about not trusting my phone. It would have been better to just let the chinese government get my personal information than trying to mess with forces I don't comprehend! If anyone reads this and is willing to help me I will be forever in your debt.
Maybe if I brick it altogether I will have more chance than it just getting to the android logo.
maduri said:
Maybe if I brick it altogether I will have more chance than it just getting to the android logo.
Click to expand...
Click to collapse
Where did you get the mentioned twrp recovery?