if someone has the same problem, tell me if you could recovery your cell phone, i have HTC S411 and now is bricked.
had this problem a while ago: just switch to bootloader mode, connecth the device to laptop via USB, wait until it's written USB on the screen of the mobile, find the orignial shipped rom (try //wiki.xda-developers.com), run the update, that's all.
Samer.
Related
I am trying to flash from the bootloader to recover from an installation error on my Fuze. I've entered into the tricolor bootloader screen by holding down Vol.down and reset. Now, when I plug the phone into the computer, the computer recognize the phone as a Qaulcomm CDMA Technologies MSM, and is trying to install a driver for it (which it cannot find.) When I run the Custom_RUU, it does not find my Fuze and is showing a ERROR[260]: Connection.
What am I doing wrong? Do I need to find a driver for Qualcomm first? I searched, and it seemed that when you enter bootloader to flash, it is suppose to say USB at the bottom. Mine says Serial. Does that matter?
If more information is needed to troubleshoot:
SPL is SPL-1.90.OliNex
Phone is unlocked by using Olinex's unlocker
Rom was EnergyRom 3.0 Phoenix 51909
Problem was caused because I tried to install Studio Kuma Traditional Chinese Fonts on it. That program works flawlessly on a WM6.1. Of course, Energy 3.0 are WM6.5, hence causing the problem.
Any assistance is very appreciated.
Try sd card flashing
You have connect your device to your USB port and let it find the drivers. In order for it to download the drivers, you must have Activesync or Windows Mobile Device Center.
Once you have one of those downloaded, launch it and connect the device while it is running normally. Opt to connect via Activesync on your phone. You don't have to have these running in the future but you need it to find the drivers and install them. Leave the Activesync connection intact while you run the Flash program.
Once the phone reboots in bootloader mode, the PC will probably download some more drivers. The Flasher will probably time out while the drivers are being downloaded and installed. Keep trying.
Once the bootloader drivers are downloaded and installed, try to run the Flasher program again. Sometimes you'll need a reboot if something is hung up.
You SHOULD be able to reboot, put the phone in bootloader mode (Down + Power + Reset) and it should change "SERIAL" into "USB". Once it displays "USB" you are good to go. Load up the Flasher program and it should go all the way through without the assistance of ActiveSync or Mobile Device Center.
I always flash in bootloader mode, I just know the initial pairing is rough.
Well, I flashed from sd card, and the phone is working now. Thanks for everyone's replies.
I tried flashing CWM recovery onto my AT&T Galaxy S4 and because my phone does not connect to my computer via USB for some reason (the phone charges and my computer recognizes that there's a device in, but I cannot actually do anything with it) I flashed it with Flashify. I rebooted into recovery mode, and I got slapped with the "Unauthorized software has been detected on your phone!" message. So I tried rebooting, and I got stuck in a recovery mode bootloop with the same message. Eventually, I realized if I just go into download mode and reboot by pressing the volume down key, it doesn't try to go into recovery mode. I have already endlessly researched my USB problem, and yes, I DO have USB debugging on. ODIN recognizes that I have an external device in as well, but I haven't tried flashing anything onto my phone with it because I don't want to brick my phone because the connection to my PC is faulty. I'm using the charger that came with the device as my USB drive, so that's not faulty either. I know rooting my phone did this, and I'm pretty sure it's because I missed a step. I used this tutorial to root my phone:
[droid views dot com] /root-att-galaxy-s4-sgh-i337-android-4-4-4-kitkat-firmware-i337ucufnj4/ (I'm not allowed to post links yet, so fix the URL if you're gonna have a look)
When I flashed the I337_NC1_Stock_Kernel, my phone refused to go into download mode and I couldn't flash the I337_NJ4_Stock_Kernel as a result. I'm pretty sure that's what caused it, but I have no idea how to fix it. I'm not an expert with my phone and, despite almost soft-bricking my phone via a corrupt CWM .zip, I'm not a newbie at this either. If I could figure out how to fix this problem, I wouldn't have to worry about throwing myself into a bootloop because I can just use ODIN. I was a sitting duck before download mode rescued me, so I'd like some help as to how I can accomplish this. Any and all help is appreciated. I am 100% certain my device is the right version for that tutorial, I wouldn't try to root my phone without checking all of the simple things first.
Hi guys, I recently purchased a Homtom HT3 for my mother, when it arrived to me I charged it and checked it out a bit just to make sure everything was fine which it was.
She collected it from me the next day and told me she'd start to use it the day after, she calls me up the next day and tells me there's some problems with it and a few people at her workplace tried to fix it for her to no avail. I pick the phone back up and I notice that everytime I power it on, it gets stuck on the "homtom" logo.
As I don't know too much about fixing phones I only took the following steps before asking for advice here; I went into recovery mode by holding up volume and power button, the android guy with the red triangle appeared so I tapped up + power button to get into the recovery(?) menu. I wiped the phone to factory settings and deleted the cache in there but it hasn't fixed the problem.
I assume I need to flash a firmware or something to potentially fix this, but I'm unable to find an official firmware from doogee/homtom's site for the HT3. I've found a firmware that I downloaded from "chinagadgetsreviews" but I'm a bit weary to try and flash with that rom because it isn't from the manufacturer. (even if I knew how to - the only experience I have is rooting my own phone but that's when I actually had access to a working phone, not one thats stuck on a boot logo).
Sorry for the long post but could anyone guide me in the right direction here? TIA
I'm not opposed to not using official firmware, I think I use cyanogen mod(?) on my own phone. I'd just like the problem fixed in the easiest way possible.
Trying to fix it myself by flashing a rom via SP flash tools but I've ran into another problem which is stopping any kind of progress - the phone isn't detected in Windows, I can't enable usb debugging because I can't get passed the boot loop, I've tried installing the ADB driver manually which didn't seem to work (just said it didn't install correctly and left me with a yellow exclamation mark) and I tried to install it automatically via ADB driver installer but it just throws up an error that the device isn't detected.
Any help would be greatly appreciated.
Hello. I bought a Homtom HT3 and next day a done an update with sp flash tool. all gone ok, but phone now wont to turn on. I contact homtom and got all drivers and room to fix it. Now i have a problem , i hit download on flash tool , take off battery + pres volume down + conect phone on usb cable. My computer detect it as USB MTK PORT sp flash tool load only the first red line but not detecting phone info, then after 1 minute i get
s_ft_da_no_response(4001) da didn't send response data to flash tool.
I changed drivers port even to MTK preloader, but i get same error.
NOTE....... All drivers and rom i got original from HOMTOM.
Thanks to all who can help me.
I can show a screenshot if need.
Same here - any solution for this problem?
Kleos89 said:
Hello. I bought a Homtom HT3 and next day a done an update with sp flash tool. all gone ok, but phone now wont to turn on. I contact homtom and got all drivers and room to fix it. Now i have a problem , i hit download on flash tool , take off battery + pres volume down + conect phone on usb cable. My computer detect it as USB MTK PORT sp flash tool load only the first red line but not detecting phone info, then after 1 minute i get
s_ft_da_no_response(4001) da didn't send response data to flash tool.
I changed drivers port even to MTK preloader, but i get same error.
NOTE....... All drivers and rom i got original from HOMTOM.
Thanks to all who can help me.
I can show a screenshot if need.
Click to expand...
Click to collapse
Hi everyone,
My dad's friend has a problem with his phone and dad asked me if I can help him. Right now I only know that he had "LG Security Error". However when I got the phone it didn't react on anything, so I'm unable to turn it on or charge a battery (I have also a second battery, neither of them works). When I plugged it to a PC it showed "OMAP4430". I've never had experience with LG before (only Xperia phones), but after searching I found this (2n option), which didn't work with my device, but this (1st option) worked flawlessly. I managed to get into FASTBOOT mode (phone is listed with "fastboot devices", ADB not) - OMAP FASTBOOT DEVICE. I noticed that it disconnects itself after 1-2 minutes and the proccess needs to be repeated. The phone still isn't showing anything on screen. After few hours of searching I didn't find anything, except that after doing procedure with Vol+ button entered, Windows recognized my phone (I could get only twice and the screen was still blank):
Code:
LGE Mobile Composite USB Device
LGE Mobile USB Serial Port (COM9)
LGE Mobile USB Modem
LGMobile Support Tool was doing something, but in the end it didn't detect anything, also I checked out LG Flash Tool 2014, phone information showed that it was in emergency mode. Screenshots
At this point I'm guessing that the phone is hard bricked as it couldn't go to S/W mode, download mode or show anything on screen etc. I haven't found any tut about unbricking in fastboot. Is there anything I can to at this stage?
Thank you in advance!
The com port driver is the only one needed for unbricking. Provided, that the phone is already in D/L mode, otherwise communication will first be done with the ADB driver.
I had the situation, that the phone wasn't recognized by the ADB and Fastboot drivers(with a custom rom installed), and under Win8.1 and Ten Fastboot generally doesn't work. But only the L9 is affected by this.
But if someone managed to clear the whole internal flash, with bootloader and baseband, the phone is economical junk now. Though re-flashing via JTAG is possible. While some geeks may own one of these Octopus adapters privately, even if you know such a person, he should be an LG user, too, as support for each brand or individual model has to be bought separately. Or simply invest around 100€ or $100. That is the price of a brand new phone with the L9s capabilities and a stable(!) Lollipop or Marshmallow installed.
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.