Hi everybody !
I have messed up my phone while installing and removing different progs like twrp and magisk. Now i'm stuck in a loop and can't figure out how to get out of it,despite having read many posts here and there. Here is what i have done:
- My phone is a Mi A2
- When i push the power button, i see briefly the android one logo, then a first message saying "your device can't be checked for corruption, please lock the bootloader", followed by a second message saying "your device has loaded a different operating system". Then it boot again with same messages infinitely.
- So i opened the phone, shorted the test points and flashed the "jasmine_global_images_V10.0.13.0.PDIMIXM_9.0" with miflash tool, apparently successfully. (By the way, i have never been able to boot in edl mode when the battery was disconnected) But alas, when rebooting after successful flashing, the phone did nothing more or less than before flashing: still stuck in the same loop.
- Pushing power and volume up does nothing else than bringing the loop mentioned above.
- Pushing power and volume down bring up fastboot, but then the device is not recognized in device manager, and i can't figure out why, as i already used adb and fastboot commands sometime ago before i messed up the phone.
Thank you in advance for any advice, and keep care of yourself and everyone around you all over the world !
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.
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.
Was attempting to flash Android 11 to my 4a since I couldn't stand 12's UI, and in the middle of the process, accidentally hit the power button and now my phone says it's corrupted, any attempt to boot it results in it being stuck on the Google logo screen, and my PC won't detect it anymore. Am I screwed or is there a solution to this?
EDIT: I've made it into fastboot, unsure of what I should do from here, enter reason says "no valid slot to boot".
EDIT2: Attempted recovery mode, screen says No command, and my PC now detects it, however it says it's unauthorized.
NEVERMIND, lots of reboots and eventually getting my PC and Android Flash Tool to recognize the phone let me force flash it and it's fixed now.
Hello, I've been using this phone for more than a few years now. Reflashed the system a few times over the years and was currently on Ivan_Meler's amazing LineageOS 18.
I saw that a bug on his 19.1 version I was experiencing was potentially fixed, so I started preparing to switch to that.
First order of business was going to recovery and doing a full backup, I had gone into recovery not too long ago.
Except I got boot looped instantly.
The current situation is:
- Model is SM-G930F
- The device is rooted
- Device will not stay turned off, if I force turn off with volume down + power it reboots instead
- Device is able to get into download mode and it seems to work normally
- Device will always boot to recovery, except when I ask to boot to download mode by volume down + power + home (not sure if there is a button combination for specifically booting to system, lmk If there is)
Things I already tried:
- Letting the battery run out completely to hopefully clear some cache -> Device tries to boot to recovery as soon as I plug the charger in
- Using ADB during the stuck splash screen -> Device eventually gets recognized by windows but it throws the generic "Your USB device malfunctioned" error, ADB doesn`t recognize it.
- Rebooting by launching a harmless command in Heimdell -> Device reboots but nothing else changes, still stuck.
- Letting battery run out at different stages, like in the stuck teamwin splashscreen, in the warning message before download mode and in download mode -> nothing changes
Additional information from the moment I tried to get to recovery and got stuck:
- I fat fingered "reboot" instead of turning off the phone, so I just held down volume up + home to get into recovery (I had already done this successfully before).
- My phone has USB debugging turned on
- My phone was plugged to my PC in USB Tethering mode when I tried to get to recovery
- My phone was set to use USB Tethering mode by default when plugged via USB, because I use that function a lot.
- My PC had the ADB server running, but was not actively running anything on device at the time.
I remember having been stuck in this same situation before and being able to recover it without losing data. But I have no recollection of how I did it.
If there was a way to make my phone stop trying to reboot and just turn off, im sure that
I would be able to boot into system, because i dont see how anything could've gotten messed up there since the phone rebooted normally and wasn`t reflashed or anythng
I really didn't want to have to wipe it, since my last full backup was a few months ago.
Do you guys have any suggestions? I was thinking of trying to flash back the exact same TWRP version through Odin, without flashing anything else. And seeing if that fixes it since the version is shown in the teamwin loading screen, would that be safe?
Hi, any progress ? I'm in the very similar situation, but flashing the same TWRP with Odin didn't help and I'm still stuck on TWRP logo. And adb doesn't see the device (neither when I'm in download mode nor when I'm on TWRP logo)
Is the device softbricked?
Try Frp HiJacker
All Samsung Frp HiJacker by Hagard (2017)
All Samsung FRP HiJacker 2017 latest updated tool.This tool 100% working and tested. FRP HiJacker V1.0 Features: * Remove Samsung FRP 2017 in Download Mode (No More Combination Files and No more tricks) * Softbrick fixer *Phone...
forum.xda-developers.com
Had similar problems myself