Moto G7 Power XT1955-5: Stuck in BootLoop at "Unlocked and Can't Be Trusted"
I made several attempts to install twrp-3.4.0-0-ocean to this new Moto G7 Power. I was able to Unlock the Bootloader, and even had TWRP running twice., but after it was rebooted it would never go back to TRWP, it would reboot to the Stock ROM. Then, runnng adb reboot bootloader would bring me back to the stock bootloader page.
Each time it boots, it has displayed the "Your Device Has Been Unlocked and Can't Be Trusted." page, and then would eventually boot. Annoying, but ok. It is what it is.
However, this last attempt to reboot from the stock bootloader has created an endless bootloop to that "Cant Be Trusted" page.
No combos of holding down the down volume for 3 seconds with the power key.. or holding down the power key for 15 or 20 seconds.. nothing works. All it does it turn the screen off for a couple of seconds and then goes back to the "Can't Be Trusted" warning page.
Well.. turns out it does work, it's just finnicky. This video showed me how to do it.. https://www.youtube.com/watch?v=fA0DHvbIlWY
Holding down the Down Volume and Power for several seconds until the screen goes black, release the buttons, then waiting a moment will allow the bootloader to appear.
1- Should I replace the stock rom? If so, how? I can't boot far enough along to run adb push.. and TWRP will not run.
What I cant do now is factory restore the device. Where can I get a stock rom, or any suggestions? I am pretty sure that's what I get for trying to use the xt1955_5.img file from Minimal+adb_fastboot_platform-tools_r29.0.6_2020 on unofficialtwrp.com's how to page, right?
Thanks in advance..
bryangrant4 said:
I made several attempts to install twrp-3.4.0-0-ocean to this new Moto G7 Power. I was able to Unlock the Bootloader, and even had TWRP running twice., but after it was rebooted it would never go back to TRWP, it would reboot to the Stock ROM. Then, runnng adb reboot bootloader would bring me back to the stock bootloader page.
Each time it boots, it has displayed the "Your Device Has Been Unlocked and Can't Be Trusted." page, and then would eventually boot. Annoying, but ok. It is what it is.
However, this last attempt to reboot from the stock bootloader has created an endless bootloop to that "Cant Be Trusted" page.
No combos of holding down the down volume for 3 seconds with the power key.. or holding down the power key for 15 or 20 seconds.. nothing works. All it does it turn the screen off for a couple of seconds and then goes back to the "Can't Be Trusted" warning page.
Well.. turns out it does work, it's just finnicky. This video showed me how to do it.. https://www.youtube.com/watch?v=fA0DHvbIlWY
Holding down the Down Volume and Power for several seconds until the screen goes black, release the buttons, then waiting a moment will allow the bootloader to appear.
1- Should I replace the stock rom? If so, how? I can't boot far enough along to run adb push.. and TWRP will not run.
What I cant do now is factory restore the device. Where can I get a stock rom, or any suggestions? I am pretty sure that's what I get for trying to use the xt1955_5.img file from Minimal+adb_fastboot_platform-tools_r29.0.6_2020 on unofficialtwrp.com's how to page, right?
Thanks in advance..
Click to expand...
Click to collapse
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my Moto E (4) using Tapatalk
Glad you're out of boot loop.
Recovered from bootloop and "dead" bootloader screen! Tips to recovery
I was able to Rescue the device from periodic BootLoops and a dead end Bootloader screen.
I referenced the information on this thread in the XDA forums, specifically the “Motorala Unbricking Tools” section.
I then tried the "LMSA: Lenovo's Motorola Smart Assistant" thread to find the link to the Lenovo / Motorola download page.
The Rescue software is a bit clunky. Powerful, but clunky.
There are also some cool tools such as Clipboard Copy Text between Device and PC, a Gif Maker, a Ringtone Maker, and a SCREEN RECORDER!!
Back on Track with the Rescue:
-Linux or Mac versions are NOT available; Windoze only.
-You will need at least 2gb of ram in your virtual Windoze7 machine to run it or it will not run in a useful manner.
- Parallels16/Windoze7-64bit worked fine.
-WINE based installs will NOT work.
To run, you will need to enable USB Debugging, although there are two other ways to connect the phone I did not also try. There even appears to be a way to rescue even a truly bricked dead device.
To Rescue your device:
Download, Install, and Run Rescue and Smart Assistant.
The Rescue process will NOT relock your bootloader.
Select the Rescue tab, then select Rescue Now. If you need to backup the device, try the Backup button right next to the Rescue Now button.
The application has some bugs, shortcomings.. here's some heads up to reduce Stress caused by those bugs..
The software will ask you to select the phone you own. The slider dialogue UI is badly done, so you will go back and forth a dozen times before learning how to navigate the menu. It might auto-recognize, but it did not on mine. Good luck!
Next, download the ROM.. the progress bar does not reflect what is actually going on. Once the 2bg down is 100% complete, it will sit there for a LONG TIME doing nothing. Dont kill the app and restart. It's actually busy unpacking the .zip Rom file into a directory tree on your harddrive. Just go eat some lunch, and come back.
Then, a similar issue occurs when you install the ROM. The progress bar is pretty much done, it just sits there doing nothing.. Let it go for a long time.. it's actually doing it's job, and the progress bar is just badly done.
If you are going to use the backup.. TURN OFF YOUR POWERSAVING stuff on both ends. If it is interupted by Power Saving/Sleep mode, the software will start at the beginning. The backup process takes hours, not minutes, so this is not a good result.
Once backed up, if you are moving to a new phone, there is a couple of ways to do that. I am going to perform these functions today or tomorrow, and will update with the results of those efforts.
Related
Moto G not boot, it just gets in the bootloader screen warning
I'm having the exact same issue, just flashed the latest stable version of CM11 (with gapps obviously) from dhacker's thread in CWM.
Coming from 4.3 with the US version t-mobile moto g.
Stuck on the bootloader unlocked screen.
I thought for a while it was just that the first loadup takes awhile but has been 10 minutes now and am figuring something bad happened.
ignore all the italics, I'm an idiot
Edit: 25 minutes in, have tried connecting the phone to computer and running command prompts to it like I did to get into recovery, device not recognized under cmd "adb devices" or "fastboot devices" when connected to computer
Phone screen goes black for about 0.8 seconds when power button is held down and immediately pops back up into warning bootloader unlocked screen, trying to go into fastboot or anything like with volume down and power button achieves the exact same effect.
Any help would be greatly appreciated.
Edit2: If I hold the power button and down volume for 20 seconds (just ignore when the screen goes black and hold it for 20 seconds) it will boot into fastboot mode
Recovery seems to do nothing but the device is now recognized by the mototool all in one, I will report back if I figure out anything more useful, I am hoping the mototool will save me
Edit3: tried flashing stock recovery, my phone now says in pink "hab check failed for recovery", tried flashing CWM recovery, it seemed to work. I then clicked "fix boot logo" it worked. The phone is now showing the motorola logo but doesn't seem to be doing much else, I'll let it sit for a couple minutes.
Edit4: If none of this works at least you'll have an interesting read about how to further destroy your phone
Tried rebooting to recovery, the mototool thinks it did it but my phone stays stuck at the motorola logo. I then told it to check connection and it now thinks there is no longer a device connected. Tried turning the phone off again, went immediately back to the motorola screen. I seem to be in the same situation except the bootlogo is no longer that ugly text. Back into fastboot mode, lets see what else we can do.
I checked to see if it was recognized by command prompts now and it IS, if you go back under like you were unlocking the bootloader and open up a cmd prompt and type "fastboot devices" it's recognized in this fastboot mode. This has given me new optimism, I'm feeling hopeful that my device is not destroyed, hopeful and very hungry, I will report back in after getting food.
Edit5: I've realized that I have no idea where to go from here, while I can access command prompts I have no idea what commands to put in, I tried hitting "factory" under the fastboot in hopes that it would flash my factory recovery, no such luck, I'm back to the same situation, tried hitting BP tools next because I didn't know what it was and thought it would be helpful, no such luck, back to the same screen, my quickly inflated confidence is now waning, I do have hope that someone can fix this issue but I am thinking that someone is not me.
I hit the recovery button, I'm sure I had done this before but this time it worked, went to restore from sd card, and restored my backup I made right before all these issues, it recovered my device, I then restarted it and everything is good now.
Apparently I am an idiot, but that's okay because my phone is working again now, after only about an hour or something.
TO FIX YOUR ISSUE HOLD DOWN VOLUME AND POWER AT THE SAME TIME FOR 20 SECONDS, IGNORE WHEN THE SCREEN GOES BLACK, KEEP HOLDING FOR ALL 20 SECONDS, CHOOSE RECOVERY, THEN GO BACK TO YOUR BACKUP THAT YOU SAVED BEFORE FLASHING A NEW ROM, RESTART THE DEVICE AND NOW THE DAY IS SAVED
My phone seems to be stuck in download mode. I'm trying to get it to recovery, all attempts result in it going back to download.
I just don't know how to get something else showing on here.
Background: Phone was rooted on Kitkat but I lost the root when I upgraded to Lollipop.
Was trying to root the phone with via the one click (http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951) which seems simple enough. However, my phone would not enter into download mode so I couldn't continue the steps. I found someone with my exact problem right here on XDA (http://forum.xda-developers.com/showpost.php?p=57125760&postcount=9) and in doing what he did, my phone DID enter into download mode, just got stuck in it.
Edit: In pressing Volume Down and Power off and on (press them, release them, press them, release them, etc) an unknown white screen that reads "Factory Data Reset" and a "yes" and "no" has came up. I don't know if I replaced my CWM recovery with this weird thing, in doing what the XDA poster said?? Even if I press "yes", the download mode screen comes back upon restart.
2nd edit: I did get it working. Left the phone connected to the LGMobile Support Tool while I tried the "Upgrade Recovery" again and after a few tries of that it turned on all by itself. Will try rooting again, hopefully succesfully this time
Hey guys - I hope you're doing well.
I recently got an HTC U12+, but wanted to try using a custom ROM due to all of the bloatware . Unfortunately I think I've ended up bricking my device. Here are some things I've since tried:
- Restoring to the backup I made beforehand in TWRP - restore works without any errors, but then just hangs at the boot screen
- Method 1 from this thread (https://forum.xda-developers.com/u12-plus/how-to/collection-htcu-u12-ruu-firmware-t3794664) - TWRP always says the zip files are corrupted for some reason
- Method 3 from that same thread - this actually worked before, but I tried installing a custom ROM again, somehow messed up again, and now this method no longer works as it just hangs at the "HTC" boot screen for eternity
- Both methods in this thread (https://www.theandroidsoul.com/how-to-install-htc-firmware-ruu-and-zip/) - the first one leads to a "failed remote 99 ru unknown fail terrible mishap" error, and for some reason my PC doesn't see my phone when I try the second despite being able to see it in file manager
- Probably many other methods that I've now forgotten
I know this is a whole lot of information, but I'm in desperate need of some help. I typically like to troubleshoot things myself, but I've been trying to fix this for quite some time now and could definitely use another set of (much more experienced) eyes. I greatly appreciate any help you guys can provide.
Thanks.
Flash RUU with SD card method
Download RUU from here(important:check your CID): https://docs.google.com/spreadsheets/d/1wIRrVQawd5rD-t9VKPQ-SdRK20RcJVZhwD7lhmPIK8w/edit#gid=0
1. rename RUU to 2Q55IMG.zip
2. copy zip in the root of your sd card. - external card / not internal - it will not work
3. reboot to download mode,
4. your device will pick up the zip file and flash it.
5.follow on screen instructions and enjoy your RUU(this method erase all your data)
I'm having an issue with my u12+ where it just continually reboots to a message saying "The boot loader is unlocked and the software integrity cannot be guaranteed. Any data stored on the device maybe available to attackers, do not store sensitive data on this device" and then it shows the white HTC logo that says Powered by Android down the bottom of the screen, it stays like that for about 5 minutes and then reboots and does the same thing over again.
Holding the power down button does nothing, it will not turn off the phone. Holding power and volume down does nothing either. The phone just does this every 6 minutes and reboots and cycle and that's it.
I've tried putting the file 2Q55IMG_IMAGINE_DUGL_O80_SENSE10GP_hTC_Asia_TW_1.53.709.1_Radio_sdm845-000201b-1807311356_release_531499_signed_2_4.zip (renamed to 2Q55IMG.zip) on the root of a 8gb Fat32 formatted SD card, but I just can't get into recovery or download mode.
I've tried holding down all 3 side buttons for minutes, or just the power button, or combination of buttons, they all do nothing to the phone. (it's as tho they are disabled, but sometimes holding a combination of the 3 will make the phone vibrate a little bit, but in no particular time or order)
When the phone is in either state (locked bootloader message or white HTC logo) my Windows 10 PC sees the phone plugged in as a "USB Input Device", not an Android Phone or Android Device. So using ADB or Fastboot commands do not work to it. I've tried to force the driver to the HTC driver but that does not work.
I also tried using the RUU_IMAGINE_UHL_O80_SENSE10GP_NA_Gen_Unlock_1.30.617.2.exe file, but once again it doesn't detect my phone.
Any help would be kindly appreciated.
Cheers!
EDIT: So I was finally able to get into download mode by waiting until the phone done its 6 minute reboot and then holding power down until it vibrated once, then held volume up until it vibrated again, then let go of the power button, I was then able to choose recovery, download etc.
So I managed to get the file 2Q55IMG.zip to install, it said it installed 100% okay. The phone rebooted and now I'm stuck again just at the white HTC logo and Power by Android down the bottom of the screen.
This time the phone is not automatically rebooting itself and no key combinations will make it reboot. I've tried holding them all in certain combinations for periods of time, the phone will not reboot or turn off.
EDIT 2: So maybe I didn't wait long enough after installing the 2Q55IMG.zip file, I finally got the phone to reboot and now I've got a working phone again. happy days :laugh:
whowhatwhen said:
I'm having an issue with my u12+ where it just continually reboots to a message saying "The boot loader is unlocked and the software integrity cannot be guaranteed. Any data stored on the device maybe available to attackers, do not store sensitive data on this device" and then it shows the white HTC logo that says Powered by Android down the bottom of the screen, it stays like that for about 5 minutes and then reboots and does the same thing over again.
Holding the power down button does nothing, it will not turn off the phone. Holding power and volume down does nothing either. The phone just does this every 6 minutes and reboots and cycle and that's it.
I've tried putting the file 2Q55IMG_IMAGINE_DUGL_O80_SENSE10GP_hTC_Asia_TW_1.53.709.1_Radio_sdm845-000201b-1807311356_release_531499_signed_2_4.zip (renamed to 2Q55IMG.zip) on the root of a 8gb Fat32 formatted SD card, but I just can't get into recovery or download mode.
I've tried holding down all 3 side buttons for minutes, or just the power button, or combination of buttons, they all do nothing to the phone. (it's as tho they are disabled, but sometimes holding a combination of the 3 will make the phone vibrate a little bit, but in no particular time or order)
When the phone is in either state (locked bootloader message or white HTC logo) my Windows 10 PC sees the phone plugged in as a "USB Input Device", not an Android Phone or Android Device. So using ADB or Fastboot commands do not work to it. I've tried to force the driver to the HTC driver but that does not work.
I also tried using the RUU_IMAGINE_UHL_O80_SENSE10GP_NA_Gen_Unlock_1.30.617.2.exe file, but once again it doesn't detect my phone.
Any help would be kindly appreciated.
Cheers!
Click to expand...
Click to collapse
with the phone off, turn it on,when you feel first vibration
quick release power key and keep push volume down.
Smartphone should boot in bootloader mode.
can you get into this mode with this guide?
fabrizio b92 said:
with the phone off, turn it on,when you feel first vibration
quick release power key and keep push volume down.
Smartphone should boot in bootloader mode.
can you get into this mode with this guide?
Click to expand...
Click to collapse
Cheer mates, issue sorted. I just updated my comment in my post.
Not sure if I'm game enough again now to try and put LeeDrOiD and Magisk on it.
I use this forums a lot for info but in this case i can't find any leads of whee to go with this, so wondering if someone can chip in some ideas?
I flashed a ROM via flashtool but wasn't happy with it, so i thought i'd just go back to stock and so used flash tool AKA emma to flash one of the options given there.
First attempt to flash it said "flash failed" or something like that and had the "flashing failed, connect to computer" note in the phone when booting it. (I'm sort of making up the terms, not that much into the tech ). Anyway, i tried flashing the same FW again and this time it went through really quick being 'completed' in a few seconds.
Now when i try to boot it gets stuck in the 'Sony' logo. Can go into Fastboot but no Flash Mode (nothing happens using the vol down key), and USB debugging seems to be off now as well.
Emma only works in Flashmode so can't do anything with that. Flashtool doesn't offer anything useful in Fastboot and Xperia Companion recognises the phone when in Fastboot but asks that i unlock the screen and enter MTP...
Any help of where i can go with this?
Thanks
P.s. While keeping buttons pressed randomly it went once into flash mode, but trying to flash a ROM with flashtool it got stuck at "reding device data" and i haven't been able to enter the mode again. Is there an alternative key press combination that i stumbled on by chance? I think i just kept vol up and power held for a while and let go at a random number of phone vibrations
Just tried: Flashed twrp via fastboot and then rebooted into recovery. Same thing. It still opens to Sony splash screen and stays there
Ok, i'm kind of talking to myself here, but mild success and something that might help someone.
Managed to get back in flash mode. Don't know if it's a fluke, unique to this phone, or how it's actually meant to work, but the sequence is:
From the freezed up splash screen, and the USB connected, press and keep pressed power+vol up (hard restart/shutdown)
You get a single vibration, if you let go here it restarts. Keep pressing
You get a triple vibration, if you let go here it shuts down. Keep pressing
You get a single vibration, if you let go here it starts in fastboot. Keep pressing
You get a second single vibration, if you let go here it starts in flash mode.
Possibly a fluke but don't want to have to try again!
Anyway, i managed to flash the last working firmware and it's all good, yet this is the unwanted one. So issue is i still need to downgrade the phone to 7.1.1
Ok Guys So I Shouldn't Have Done This But I Used Fastboot To Flash Recovery And I think I Did It Wrong. It Said "ok" And Finished And I Rebooted Phone It Resetted And Then Stuck On The Orange State Bootloader Message. I Do The Recovery Mode And Goes Black And Nothing Is Responsive For a While, Sometimes Longer Than Others. This Happens If I Start Phone Normal Or Try Fastboot Or Download.
Because Of My Mistake I Cannot Connect To Pc Software And Im Not Sure Of What I Can Do. I Feel Like Im Not Going To Like The Answer For This But I Got To Take The Blame For This.
Btw i Have A Samsung galaxy Note 20 Ultra Sm-N986u
I think your phone is hard bricked
so you can't get fastboot using volume up+power or via adb?
rescue from manufacturer site pos or just device not being recognised?
It isn't hard bricked it's just way of Samsung trying to make life of simple people more difficult, people who paid for Samsung phones lots of money.
To sort that screen issues what you can surely do is,
Simply press volup + voldown buttons at the same time, no matter if you're on that orange screen or whatever just press those those two buttons at the same time and keep pressing them while you connect your phone to pc. you will boot into download mode. Then flash stock firmware for your phone. After stock of flashed Reboot and start your phone, go to developer options see if oem unlock option is there if it is then oem unlock it if it is not then go back to settings manually change date to year ago, then go to updates disable auto update, connect to WiFi, and press on update several times untill window shows up saying no updates, then go to developer options you should see oem unlock, unlock it.
Then boot into download mode and make sure you have working copy of recovery.
And make sure you follow instructions of whoever recovery you installed on how to boot into recovery. I have S20 plus and too had troubles with it, and the only working recovery for my phone is twrp customised. To boot into it after flashing recovery from odin auto reboot disabled I pressed voldown and power, USB cable connected, then after screen goes off I changed from voldown to volup while kept pressing power button and cable connected. Orange screen with warning showed up for 5 sec I kept pressing and it bottled to twrp and then I was able to install custom rom beyond rom and while installing in aroma I was able ti choose option to remove orange screen.
That's it.
I ran into the same error. I mistakenly loaded twrp's recovery into userdata instead of ap section. The phone was stuck at the orange screen and nothing was happening whatever i pressed. I waited till the battery to dry out and with 0% battery, i directly connected to pc and was able to get into download mode. Then i flashed stock and everything is now back to normal.
Carl Johnson (Cj) said:
I think your phone is hard bricked
Click to expand...
Click to collapse
Absolutely not