Hey Guys,
I unlocked my Xperia L C2105 successfully using the official Sony instructions, but after a reboot it gets stuck in the animation splash screen.
I can't go anywhere from here, can't get CWM or SuperSU installed too.
Tried everything around here but nothing seems to work:
-Installed PC-companion and installed Flashtool's drivers afterwards > device gets recognized and connected successfully in both programs.
-Installed flashtool, tried flashing the stock Rom > get an error 'processing of loader.sin finished with error'
-Flashmode and fastboot mode are working OK though.
-Tried unlocking/re-locking using flashtool > get an error 'your phone bootloader cannot be officially unlocked'
-There's no way I can get into recovery mode, neither by removing the battery and boot with volume down held down.
What options do I have left?
I have exactly the same problem on my SP but on a locked bootloader. Tried everything, nothing works. Read somewhere that the phone is locked in a read only state. While flashing with flashtool it gets stuck on READING DEVICE INFO and then gives me Processing of loader.sin finished with errors. I guess taking it to the service center is the only option. It gets stuck on a screen with spanner and a screwdriver and a progress bar below that and its been in this state from last 4 days.
Related
I have looked at multiple guides on this and other sites, googled and tried stuff and I cannot resolve this problem. Hopefully I am posting in the right place.
I took the jump and unlocked the bootloader on my Moto G first generation, XT1034 successfully. I flashed TWRP 2.8.60.xt1034.zip with adb and this was successful. Then I flashed Super SU 4.6 Update and that was successful. I got into trouble I guess when I tried to flash Cyanogenmod 12.1 nightly. I used TWRP to flash via install. The flash had an error, which unfortunately I didn't write down. I believe it was something to do with a partition. However, it looked like the flash failed. At this point and for hours I have been trying to fix the "Warning Bootloader Unlocked Loop I am stuck in.
I have been able to get into the phone and flash via adb commands. I've tried several commands suggest to fix this that I have found in forums. I have tried flashing several recoveries including an older TWRP per the method in this thread, a clockworkmod - and the original 2.8.6.0.xt1034. When I get into the phone bootloader which is available, I have not been able to access any options in recovery. Pushing the power button on recovery leads to a blank screen sometimes followed by a recovery starting or a Motorola Logo starting up and a couple times a recovery. TWRP has started a couple times, but never gets past the intro screen, where it locks up. clockworkmod (clockworkmod-6.0.4.7-falcon.img started once after flashing through adb and gave me flash options. I tried to sideload, didn't understand, went back and the recovery locked up. These recoveries no longer load at all.
Through all of this the "Warning Bootloader Unlocked" logo screen comes up after plugging into the computer (Windows 8.1).
Example, I open the phone bootloader by waiting for the phone screen to go from the "Warning Bootloader Unlocked" screen to blank - it cycles from logo to blank. If I'm quick the phone and hard boot the phone will boot into bootloader. I connect to the laptop through USB. When I toggle to recovery and hit the power button the screen goes blank, the Motorola Logo pops up, goes blank and then the "Warning Bootloader Unlocked" appears. The Laptop then seems to connect and disconnect as the Warning screen comes on and turns off.
The factory selection just goes to a blank screen.
I would really appreciate some advice on how to get the phone back to a state in which I can work with it and try again. It is very difficult wading through all of the information out there. I've learned a lot through this issue, but can't take it any further.
Thanks, Jeff
Solved - Stuck in "Warning Bootloader Is Unlocked" Loop
This resolution took many hours to figure out, but I finally got there with this guide - http://forum.xda-developers.com/showthread.php?t=2542219, this thread - http://forum.xda-developers.com/showthread.php?p=54855457#post54855457 and this thread - http://forum.xda-developers.com/gen...e-firmware-t3042687/post59139823#post59139823.
I tried RSD Lite on different computers and USB cables I could not get the device recognized. So I ended up with the MfastbootV2 method to reload stock firmware, which I found on the firmware thread above - this was big, as my phone is with Wind Mobile in Canada and the link is the right one. The only thing I picked up from a different website was to use a computer with USB 2 ports. This is what I did, but I don't know one way or the other if USB 2 was needed. .
Can't thank you hard working guys enough for the time you take to put these threads together. I'm back up and running. As a bonus, after a big clean up in the process, my phone is running fast again.
Thanks everyone.
Hi,
My phone is/was rooted with an unlocked bootloader and I have attempted to flash using flashtool, something I've done loads of time beforehand without issue.
However, it crashed and my phone won't go past 'the udpate failed' black screen when turning on.
It appears to go into both flash and fastboot modes.
Have run on flashtool again, downloaded firmware etc...but when i got to flash, it doesn't recognise the firmware so cannot prepare it, or the phone model.
Why won't it load up the firmware so i can create/prepare to flash, and how do i fix this issue so I can use my phone again? Sending me mad...any help greatly appreciated!! Just cannot get rid of this update failed problem.
Stuck on "Your device is corrupt. It can't be trusted and will not boot" start screen
Hi,
(I already posted this as a comment on the thread - GUIDE: How to unbrick your Zenfone 6 (ZS630KL) - but am looking for anyone who can help with this issue)
I did a series of steps over the past 48 hours that have ended with my phone now displaying the message, "Your device is corrupt. It can't be trusted and will not boot." It stays like that for about twenty seconds, and then reboots. At the time it is rebooting, I'm able to press the volume up + power keys together and get it into the Fastboot Mode - and then it shows up in the Fastboot menu of an attached computer, but that's it - from there, I'm unable to reboot into Recovery / System, as both attempts end with the above stated message. I AM able to power off the device from the Fastboot Mode, but the device powers on automatically (and displays that message onscreen).
I downloaded the Qualcomm drivers as suggested in this article, and was able to convert the phone from an "unknown android" to a "Asus android" device in Windows Device Manager - but no further progress; after running the .bat and the script, this message still appears onscreen, when attempting to login to the Recovery from the Fastboot Mode.
Any guidance would be appreciated. I am briefly outlining the glorious-many (mis-)steps that led to this current situation:
- Installed LineageOS 17.1
- Realised that Google Pay (Indian version) and a banking app don't work
- Tried multiple options to resolve that issue, such as installing (and uninstalling) TWRP, Magisk, Xposed framework, etc.
- finally gave up and was looking to get back everything to stock - ROM, Recovery and boot loader. Stumbled on the "fastboot oem asus-back" command, which now in retrospect, I shouldn't have used with custom recovery + ROM on the device, but yeah, that's what led to this issue.
cutesocks7583 said:
Hi,
(I already posted this as a comment on the thread - GUIDE: How to unbrick your Zenfone 6 (ZS630KL) - but am looking for anyone who can help with this issue)
I did a series of steps over the past 48 hours that have ended with my phone now displaying the message, "Your device is corrupt. It can't be trusted and will not boot." It stays like that for about twenty seconds, and then reboots. At the time it is rebooting, I'm able to press the volume up + power keys together and get it into the Fastboot Mode - and then it shows up in the Fastboot menu of an attached computer, but that's it - from there, I'm unable to reboot into Recovery / System, as both attempts end with the above stated message. I AM able to power off the device from the Fastboot Mode, but the device powers on automatically (and displays that message onscreen).
I downloaded the Qualcomm drivers as suggested in this article, and was able to convert the phone from an "unknown android" to a "Asus android" device in Windows Device Manager - but no further progress; after running the .bat and the script, this message still appears onscreen, when attempting to login to the Recovery from the Fastboot Mode.
Any guidance would be appreciated. I am briefly outlining the glorious-many (mis-)steps that led to this current situation:
- Installed LineageOS 17.1
- Realised that Google Pay (Indian version) and a banking app don't work
- Tried multiple options to resolve that issue, such as installing (and uninstalling) TWRP, Magisk, Xposed framework, etc.
- finally gave up and was looking to get back everything to stock - ROM, Recovery and boot loader. Stumbled on the "fastboot oem asus-back" command, which now in retrospect, I shouldn't have used with custom recovery + ROM on the device, but yeah, that's what led to this issue.
Click to expand...
Click to collapse
This issue is kinda resolved now - it took more than 24 hours of looking through various solutions on the internet.
In the interests of anyone who happens on my comment/post and would like to know how I resolved it, I can't give you exact steps - sorry, but there was just way too much fiddling. But these two posts were invaluable in helping me understand the issue:
a) XDA post: [Guide]Remove "your device is corrupted and can not be trusted" issue
b) XDA post (and the first few replies): Phone keeps booting into csc fastboot mode
and this post was invaluable in actually finally resolving the issue (it resolved only after I ran through the steps a second time, after trying the steps from the above two links a few times, and trying other steps from other forums on the internet)
c) [GUIDE] QDLoader 9008 fix | EDL Mode fix
I didn't complete ALL steps in that last post, since my ROM had already been flashed in my previous steps; I just had to get past that locked/unlocked Bootloader, and things are fine now.
I'm trying to update to firmware version UL-ASUS_I01WD-ASUS-17.1810.2008.171-1.1.1-user now, after which I'm going to attempt flashing the stock ROM from the ASUS website. Hopefully, it all works out fine - but right now, I'm just glad that the phone isn't bricked, and that I don't need to visit an Asus service centre.
Hello everyone,
I have a European H870 and unlocked the bootloader, used ADB/FASTBOOT to install TWRP but could never get to start in recovery because of a warning screen that shows up because it is unlocked.
Couldn't get into recovery from both ADB or by utilizing the keypress method. Vol-down+power --> logo --> release power for 1 sec then back on it. I even tried with other variants of that but could never get into recovery or DL mode. What's the point of unlocking the bootloader if you can't do anything afterwards because of a stoopid warning screen?
I never had that issue with my Samsung Mini S3. But with the LG's that I have, since the bootloaders were locked, the phones display this warning screen upon powering up. I can't be the only one with this issue unless I was doing it wrong. But I wasn't. So...anyway.
So with my G5 H850 I got around this problem by using FASTBOOT FLASH RECOVERY TWRP*.IMG and then FASTBOOT REBOOT before using ADB REBOOT RECOVERY during the boot process to get into recovery before the phone had fully booted.
So I tried the same with the G6 H870, of which I also cannot get into DL mode or recovery because of this screen. The only difference was that there is something different about how the H870 loads the system so that I could not run ADB commands until the phone was already 100% booted and thus rendering my recovery flash useless.
I ended up doing something that caused my phone to always boot into fastboot so I downloaded what I thought at the time was the correct boot.img and flashed it. And now I'm at the current situation where the phone boots past the warning screen and into the logo screen but then stops for a few minutes before rebooting. This process endlessly repeating. It is obvious to me that the boot.img was incorrect.
So what I have done so far is loading all Qualcomm drivers, LG drivers, QFIL and QPST (drivers being installed or uninstalled for each instance that requires them). The problem now is that the phone shows up on a COM port but is is unrecognized to all the different software and thus can I not communicate or flash anything to it.
A couple of unbricking procedures that I tried are:
https://forum.xda-developers.com/lg-g6/how-to/lg-g6-unbrick-method-t3935924
https://androidmtk.com/use-qpst-flash-tool
There were more but I cleared my browser's memory.
So, do I need to invest in an Octoplus device to get past this or is there another way?
Thank you.
hello,
Some time ago my phone started to lag spontaneously. I had to force boot it in order to get it back working. After few days it repeated, then again, then again. Last time force boot didn't work - got stuck at "samsung welcome screen" All i could do is to enter recovery and download mode. Tried to do everything in recovery didn't work. Tried to flash rom via odin, but after 20mins of flashing stuck at one point i aborted it (stupid af idea) Phone went into screen i enclosed. smart switch doesn't see phone at the same time pc detects it (sound when connecting) odin does too yet still can't flash official rom.