Hi all,
I need of some assistance, I've got 2 Xperia L1's in front of me that will not boot.
Plug in to PC, and the device is picked up as a USB Serial Port.
I can still get into flash mode, but even here I'm having issues.
I am unable to flash any stock ROM. The process simply stops and gives up with no errors at "Opening TA Partition 2".
I've got a backup of the TA partition, but I can't flash using dd / adb, as the phone does not boot.
Any recommendations? I've tried updating PC drivers, using old versions of flash tool and different cables with no luck..
Related
My milestone 2 is completed bricked and can't be recognized by PC. But I can log in the official recovery screen. I have downloaded a update.zip file from a link （not sure if it is an official link, as I can't find it through Motorola website). It prompted "signature error" when installed. Not sure anyone can provide an update.zip file, so that I can try if I can save my Milestone2. Thanks in advance!
as long as you can enter the stock recovery. your device isn't bricked. did you try to do a full wipe in stock recovery? did you try to use another usb port in bootloader mode? sometimes you get a black screen in bootloader mode, but you pc recognizese your device very well. did you install all drivers on your pc?
lulli1 said:
as long as you can enter the stock recovery. your device isn't bricked. did you try to do a full wipe in stock recovery? did you try to use another usb port in bootloader mode? sometimes you get a black screen in bootloader mode, but you pc recognizese your device very well. did you install all drivers on your pc?
Click to expand...
Click to collapse
1. I have tried full wipe, but didn't work. The machine reboot again and again;
2. I have tried another usb port, another PC and even another operating system (win7 and winXP), also didn't work.
3. I am sure I have installed the drivers, as PC can recognize my phone when it is OK before;
As I can only entered the official recovery screen, I think I can try if it worked when I update with an official update file. Anyway, thanks for your suggestions and reply!
hi,guy.i think you should do the curect usb driver for your pc recongnizing first. than choose a ringt bootlaoder offical ROM. curse your phone can login the rockrecovery screen means its ok! isn't?
I think the only way for you to get an update.zip is with another milestone 2 running froyo, that way you can update it via OTA, and before the phone reboots, take the update.zip from the /cache partition.
Sent from the U
Hello,
I have installed a custom rom (Marshmallow) for my SM-A500FU through the adb. Now when I want to install a different rom I have to either boot into TWRP and I can't do that because booting into recovery simply restarts a phone, or I have to boot into Download mode and install it with the adb. The problem is that when the system is running, the phone simply charges, no Windows notifications or devices appear and when the phone is in Download mode Windows detects that a device is plugged in but can't recognize it. I have all the adb drivers, KIES and all that so it's not a problem. Can I somehow boot into TWRP or make Windows recognize my phone so I can use adb?
Thanks.
before installing a rom, have you wiped system, cache, dalvik and data? If yes try with a hard reset and if it doesn't work, too flash stock firmware
Hey,
yes, I wiped everything, I have flashed many roms earlier and I believe I have flashed it properly. I have managed to get into TWRP so I can actually flash FWs. I have only updated my rom to the newest CW13 build there is for my A5. Is there any way to flash a stock FW (for example a XEO KitKat) without ODIN? I can only use ADB through TCPIP and TWRP, so there is no way for me to flash it through ODIN.
Thanks.
so, if you press power+home+vol- it doesn't reboot in download mode, right?
It does boot into the Download mode. The problem is that when I plug the phone into my PC in Download mode it says that the USB Device is not recognized in Windows with 'A request for the USB device descriptor failed' error. When I plug it in when the phone is booted normally into android, it just charges, Windows doesn't see it at all.
whzq said:
It does boot into the Download mode. The problem is that when I plug the phone into my PC in Download mode it says that the USB Device is not recognized in Windows with 'A request for the USB device descriptor failed' error. When I plug it in when the phone is booted normally into android, it just charges, Windows doesn't see it at all.
Click to expand...
Click to collapse
Well, you can't flash samsung firmwares with twrp. Try flashing another rom through twrp
Alright, I have tried to flash multiple ROMs. Currently sitting on a Lollipop. Nothing changed, though. On every single ROM the problem still persists. It's not a problem with the PC as I've tried to connect my A5 to a laptop with freshly installed Windows and KIES and it behaved the same way as on my PC. The cable is fine as well, I have tested it with my old SGS3, it worked just fine on both my PC and laptop. Frankly, I have no idea what to do next, I'm starting to think that the port is physically broken. It's weird though, as I can still charge my phone and there is a response when the phone is in Download mode, just that Windows can't recognize it.
Try with adb command "adb reboot recovery" if it doesn't work you can downlaod odin mobile from play store and flash stock firmware!
Do you have odin for windows ?
zyxw-androidiani said:
Try with adb command "adb reboot recovery" if it doesn't work you can downlaod odin mobile from play store and flash stock firmware!
Do you have odin for windows ?
Click to expand...
Click to collapse
Yes, ihlf his device can boot he can use mobile odin. Have you tried with other PCs, just to see it isn't a problem of your pc?
In my experience usb device descriptor errors are related to the specific PC the error occurs on due to device driver conflicts, but if you get the same error on another pc then it could be the hardware.
I'd certainly be trying another cable first on a fresh PC.
Anyway regardless of all that you can flash the stock firmware with FLASHFIRE available on play as long as you have root.
Sent from my SM-T280 using XDA-Developers mobile app
First, apologize for poor English.
Does anyone have full system backup as single img or bin file? Accidentally flash ZUK Z1 rom when porting MIUI8 and now my device is bricked, and partitions is a mess. QFIL doesn't allow me flash because detect ZUK device. Is anyone kind enough to make backup with EMMCRAW_1.4.0.0 or something similar? It's important to be a software without model check, just simple raw copy as single file.
update: Things goes worst. Tried to save it with Qfil but it fail, Miflash fail too and ruined my partitions. Long story short, now my device doesn't boot, blank screen, windows XP,7 and 10 recognize Qualcomm 9008 mode if i power it on without battery. With plugged battery recognized as Linux CD...something, without partitions. ADB and Fastboot doesn't work on any case. On many tries, Qfil accept only ZUK Z1 rom, flashing fine but doesn't boot off course. If i start QPST Configuration tool, it detects port but progress bar loading and never goes full, EMMC Software Download tool fail too. So, i'm asking for advice.
I found a friend with the same phone and make raw system dump, but result is same, only Qualcomm 9008 mode. Is my mainboard broken?
Did you try with older qfil? QPST ver2.7.422?
maybe this help
Krasimir said:
First, apologize for poor English.
Does anyone have full system backup as single img or bin file? Accidentally flash ZUK Z1 rom when porting MIUI8 and now my device is bricked, and partitions is a mess. QFIL doesn't allow me flash because detect ZUK device. Is anyone kind enough to make backup with EMMCRAW_1.4.0.0 or something similar? It's important to be a software without model check, just simple raw copy as single file.
update: Things goes worst. Tried to save it with Qfil but it fail, Miflash fail too and ruined my partitions. Long story short, now my device doesn't boot, blank screen, windows XP,7 and 10 recognize Qualcomm 9008 mode if i power it on without battery. With plugged battery recognized as Linux CD...something, without partitions. ADB and Fastboot doesn't work on any case. On many tries, Qfil accept only ZUK Z1 rom, flashing fine but doesn't boot off course. If i start QPST Configuration tool, it detects port but progress bar loading and never goes full, EMMC Software Download tool fail too. So, i'm asking for advice.
Click to expand...
Click to collapse
try volume down + power and try formating everything fro that menu
K920
Hi,
I have exactly the same problem. Did you resolve it?
Dear members, this is my first post and the problem is very complicted, so please bear with the long post
Device details:
LeEco Le1s (x500)
MTK6795 chipset
3 GB + 32 GB (Everybody knows )
Background:
I downgraded my ROM from 19s to 14s with SP Flash tool and the phone booted normally. I went through the initial setup, unlocked Developer mode and USB debugging. Then I opened the adb toolkit on Win 7 x86 machine to unlock bootloader and install twrp custom recovery at single go (instead of letting phone rebot after bootloader unlock and then proceeding with recovery flashing).
Now phone went to soft brick, to overcome which I needed to flash userdata with sp flash tool (I have done this in past also following a tutorial, the same files were used this time). But flashing process resulted in BROM error and I was not successful.
So, I re-flashed the original 14s rom via SP flash tool to get the things back to working, but phone didn't boot properly and bootloop situation was still there. I again reflashed the same ROM and this timephone entered red light of death mode, and didn't boot up after flashing original rom.
Now, I again googled this problem and found that we need to format flash with bootloader. Here the problem complicated further.
As soon as I formatted the flash and the bootloader, laptop stopped detecting the phone via usb cable. Now I can't flash any rom using SP flash tool as the phone is not detectable.
I have reinstalled my windows 7 32 bit operating system and reinstalled all the drivers for MTK smartphone. I have another Le1s phone running on 19s version of EUI marshmallow with stock recovery and locked bootloader which is detecting fine without problems.
Please guide me how can I resolve the problem.
Also guide if the other phone can anyhow help in this matter in terms of software backup for SP flash tool (I couldn't find a way of backing stock rom using SP flash tools.
Problem summary:
1) Flash with bootloader formatted
2) Phone is not detectable on Windows 7 32 bit OS and latest SP flash tools
3) Red LED turns on when phone connected to charger or laptop via usb cable,nothing on LCD display
4) Can't reach bootloader or recovery either
Help will be really appreciated. You all know the value of data stored on smartphones.
Thanks in advance!!
can explain how you were able to solve it?
facing a similar issue would ne helpful.
thanks.
I don't know how to leave well enough alone, and I've been working on the Onn 8" Pro (100003561) tablet trying to at least get root. I managed to unlock the bootloader, but was unable to use SP Flash Tool to dump my own boot.img, so I picked up one I found online that I'm pretty sure is from an older firmware version (https://forum.xda-developers.com/t/stock-stock-backups-images-otas.3998227/page-9#post-82619259) and now it keeps giving me errors, bluetooth crashing, etc, even after a factory restore from the recovery.
I CANNOT get SP Flash Tool to load the scatter file that deadman was using in his comment (https://forum.xda-developers.com/t/stock-stock-backups-images-otas.3998227/page-9#post-82619259) it just gives me an invalid scatter file error. I just want it back to factory, start all over, but no matter what I do I can't figure out how to flash deadman's firmware file, or ANY firmware backup for that matter. I keep getting scatter file errors, and SP Flash doesn't even wanna find my device. I've got the drivers installed properly, it shows up as "MediaTek PreLoader USB VCOM (Android) (COM3)" in my device manager. I've tried changing the COM port, running the flash tool in compatibility mode for Windows 7 (I'm on Windows 11 btw) running it as admin, and nothing. I can get an empty scatter file from WWR 2.51 to load in flash tool, but when I plug my device in it just does nothing. If I unplug my device, it gives an error that says "BROM ERROR: S_BROM_CMD_STARTCMD_FAIL (2005)".
I can get into fastboot mode, but I can't open the settings in the normal boot because it instantly crashes to the ONN boot logo whenever I open anything. I'm at a complete loss here.
sethfoxen said:
I don't know how to leave well enough alone, and I've been working on the Onn 8" Pro (100003561) tablet trying to at least get root. I managed to unlock the bootloader, but was unable to use SP Flash Tool to dump my own boot.img, so I picked up one I found online that I'm pretty sure is from an older firmware version (https://forum.xda-developers.com/t/stock-stock-backups-images-otas.3998227/page-9#post-82619259) and now it keeps giving me errors, bluetooth crashing, etc, even after a factory restore from the recovery.
I CANNOT get SP Flash Tool to load the scatter file that deadman was using in his comment (https://forum.xda-developers.com/t/stock-stock-backups-images-otas.3998227/page-9#post-82619259) it just gives me an invalid scatter file error. I just want it back to factory, start all over, but no matter what I do I can't figure out how to flash deadman's firmware file, or ANY firmware backup for that matter. I keep getting scatter file errors, and SP Flash doesn't even wanna find my device. I've got the drivers installed properly, it shows up as "MediaTek PreLoader USB VCOM (Android) (COM3)" in my device manager. I've tried changing the COM port, running the flash tool in compatibility mode for Windows 7 (I'm on Windows 11 btw) running it as admin, and nothing. I can get an empty scatter file from WWR 2.51 to load in flash tool, but when I plug my device in it just does nothing. If I unplug my device, it gives an error that says "BROM ERROR: S_BROM_CMD_STARTCMD_FAIL (2005)".
I can get into fastboot mode, but I can't open the settings in the normal boot because it instantly crashes to the ONN boot logo whenever I open anything. I'm at a complete loss here.
Click to expand...
Click to collapse
Ugh, I feel so stupid. I FINALLY got SP Flash to recognise my device, by FOLLOWING THE DIRECTIONS :eyeroll:
So yes, you DO have to tear the back off of the tablet, and unhook the battery before you can do anything.