Boot Logo Loop? - X Style (Pure) Q&A, Help & Troubleshooting

Hi,
I'm having a huge problem with my Moto X Pure Edition. After I tried to push the SuperSU.zip and went to reboot, my phone went to reboot but stayed on the logo screen. I'm still able to shut it off, and go to into fastboot and bootloader, but it's just stuck on the logo screen. I'm going to feel dumb if it's permanently bricked, since I was so close to getting this thing rooted.... FYI, I was using TWRP and running android MM 6.0
Thank you very much for anyone that can help!
UPDATE: Fixed, wiped cache/ other temps files and flashed the initial SuperSu.zip and booted up perfectly.

motouser32 said:
Hi, I was using TWRP and running android MM 6.0
Click to expand...
Click to collapse
@motouser32 ... You say you are using TWRP. From power off reboot directly into TWRP, restore your latest TWRP backup and go through the recommended method to install SuperSU again.
You use the word "push" I presume you mean flashing the SuperSU zip file in twrp recovery and that you are not trying to use the ADB command "push".

Use 2.62-3

metpolds said:
@motouser32 ... You say you are using TWRP. From power off reboot directly into TWRP, restore your latest TWRP backup and go through the recommended method to install SuperSU again.
You use the word "push" I presume you mean flashing the SuperSU zip file in twrp recovery and that you are not trying to use the ADB command "push".
Click to expand...
Click to collapse
Thank you for your response! Unfortunately, I'm new to rooting and the several guides I referenced said nothing about making a backup in the first place, therefore I never made a backup for me to restore to. And yes, when I say "push" I do mean flashing SuperSU zip in twrp recovery by first using step 3 on WinDroid and then manually clicking install on my phone etc.

motouser32 said:
Thank you for your response! Unfortunately, I'm new to rooting and the several guides I referenced said nothing about making a backup in the first place, therefore I never made a backup for me to restore to. And yes, when I say "push" I do mean flashing SuperSU zip in twrp recovery by first using step 3 on WinDroid and then manually clicking install on my phone etc.
Click to expand...
Click to collapse
I had the same problem. thankfully i live close to dottat and he put the "systemless_root.zip" on my sd. we flashed it with twrp and it fired right up. might be worth a shot.

UPDATE: So there is a little bit of progress. Instead of rebooting and freezing at the initial logo, the logo is now stuck in that buffering like Motorola logo (with the hand stitched by message at the bottom). I've noticed also that when I try flashing anything, it says that there is no MD5 file found and so it skips that check. I feel like this is important?

Did you try 2.62-3 yet?

lafester said:
Did you try 2.62-3 yet?
Click to expand...
Click to collapse
I'm not entirely sure what version i'm running now, I'm just happy it works lol.

motouser32 said:
Hi,
I'm having a huge problem with my Moto X Pure Edition. After I tried to push the SuperSU.zip and went to reboot, my phone went to reboot but stayed on the logo screen. I'm still able to shut it off, and go to into fastboot and bootloader, but it's just stuck on the logo screen. I'm going to feel dumb if it's permanently bricked, since I was so close to getting this thing rooted.... FYI, I was using TWRP and running android MM 6.0
Thank you very much for anyone that can help!
UPDATE: Fixed, wiped cache/ other temps files and flashed the initial SuperSu.zip and booted up perfectly.
Click to expand...
Click to collapse
Hi,
I'm also stuck in the same boat as you were. I followed your advice & wiped cache/delvik & now the phone goes ahead of Moto Logo but freezes with black screen (side lights on). I'd really appreciate any help.

With twrp-2.8.7.1-clark and SuperSU-v2.66 worked
lafester said:
Did you try 2.62-3 yet?
Click to expand...
Click to collapse
Thanks!!!!
I was in boot loop with twrp-3.0.0.0 and SuperSU-v2.67, flash with twrp-2.8.7.1 and SuperSU-v2.66 worked! Thank you!
PT-BR: Eu estava em boot loop com twrp-3.0.0.0 e SuperSU-v2.67, instalei twrp-2.8.7.1 e SuperSU-v2.66 e funcionou! Obrigado!
Moto X Style Android 6.0 XT1572

ErivandoXP said:
Thanks!!!!
I was in boot loop with twrp-3.0.0.0 and SuperSU-v2.67, flash with twrp-2.8.7.1 and SuperSU-v2.66 worked! Thank you!
PT-BR: Eu estava em boot loop com twrp-3.0.0.0 e SuperSU-v2.67, instalei twrp-2.8.7.1 e SuperSU-v2.66 e funcionou! Obrigado!
Moto X Style Android 6.0 XT1572
Click to expand...
Click to collapse
Use twrp 3.0.0.2 and super su 2.62-3. It will flash in systemless mode.

Today I updated OTA and stayed with Loop in TWRP ...
I fixed doing wipe cache and wipe dalvik.
I have root on android 6.0, I will update no more OTA, learned the lesson.
PT-BR:
Hoje eu atualizei OTA e fiquei com Loop no TWRP...
Eu consertei fazendo wipe cache e wipe dalvik.
Tenho root no android 6.0, eu não atualizarei mais por OTA, aprendi a lição

Related

Nexus 10 does not boot after Update

After attempt at installing software update to Nexus 10 tablet will not boot. Have wiped Cache and even then did a factory reset. Nothing. Google appears and then twirling colorful dots and nothing. For hours just twirling dots., Samsung and Google and Best Buy geeks says nothing they can do. No longer under warranty but very upset since tablet was working great until update. I am not very tech savvy but can anyone help or do I just have a new paperweight? Thanks for any advice.
I have not made any modifications to the tablet.
Just flash the newest factory image. Get it and the instructions to flash it from here:
https://developers.google.com/android/nexus/images
yes flash the newest image
After getting a notification of the latest update I went and rebooted for the update to install but it went to the twrp recovery and nothing happens, is there a way to install the update?
VivaErBetis said:
Just flash the newest factory image. Get it and the instructions to flash it from here:
https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
Gibbothegreat said:
After getting a notification of the latest update I went and rebooted for the update to install but it went to the twrp recovery and nothing happens, is there a way to install the update?
Click to expand...
Click to collapse
Still having proble? what is your recovery ? stock? did you update the bootloader? depending on your answer I should be able to help you out, thx
Khaon said:
Still having proble? what is your recovery ? stock? did you update the bootloader? depending on your answer I should be able to help you out, thx
Click to expand...
Click to collapse
Hi Khaon, I have stock lollipop version 5.1.1 . (LMY47V) and latest twrp version. When upgrading it restarts and goes to recoverys main screen.
BTW how can I check which version my bootloader is?
same problem
VivaErBetis said:
Just flash the newest factory image. Get it and the instructions to flash it from here:
as a newbie .I'm not allowed to reference your link !!
I rooted my nexus 10 using xda instructions., installed CWM. All good. I tried backup and recovery and screwed something up in recovery. Got stuck in recovery mode reboot loop. Many gyrations, no fix, so I tried factory reset. Still no fix.
I decided to install a new version of the OS using the Mantaray tar you reference above. UBS connecting and fastboot. All messages look good. Now I have the problem reported in this thread. Stuck with flying balls and no boot. Very interested in any suggestions you may have.
Click to expand...
Click to collapse
Gibbothegreat said:
Hi Khaon, I have stock lollipop version 5.1.1 . (LMY47V) and latest twrp version. When upgrading it restarts and goes to recoverys main screen.
BTW how can I check which version my bootloader is?
Click to expand...
Click to collapse
So you keep just boot looping into twrp, right ?
Did you try installing a custom ROM through adb or just connecting your device?
If it keeps boot looping you gotta to wipe the full storage.
Khaon said:
So you keep just boot looping into twrp, right ?
Did you try installing a custom ROM through adb or just connecting your device?
If it keeps boot looping you gotta to wipe the full storage.
Click to expand...
Click to collapse
No, on a normal reboot or a shutdown/restart it's fine no problems there but when I try to install the update via system update it reboots into twrp. I attach a pic of my system.
Gibbothegreat said:
No, on a normal reboot or a shutdown/restart it's fine no problems there but when I try to install the update via system update it reboots into twrp. I attach a pic of my system.
Click to expand...
Click to collapse
Oh I see, well, you should just flash a custom ROM or if you want to stay with official factory images, you should just follow instruction there:
https://developers.google.com/android/nexus/images
What you do need is just have fastboot executable once you are into the bootloader.
You can easily access the bootloader from twrp : shutdown > reboot into booatloader
Cool thx for your continued help :good:
The problem is due to your attempting an OTA update with a custom recovery (TWRP). You can only do OTA with stock recovery. Once you are in this situation, your easiest way out of it is to simply apply the latest factory image using "fastboot", but this will also wipe your user data so backup any photos, music, etc. before you start. You will also have to reload programs from Playstore once the new image is installed.

Wifi Doesn't Turn on

My wifi won't stay on. It just keeps switching off. Here's what happened:
Non root. OTA update to 6.0 Marshmallow.
Unlocked bootloader.
Flashed TWRP. - Stuck on bootloop, then blank screen.
Went on Recovery and did factory reset. No change.
Flashed stock firmware for 5.1.1
Now wifi won't switch on. This is my 2nd phone now it happened to. Both Moto X Pure.
How can I get this fixed? I've done a lot of research and nothing worked.
I think that your Wi.fi is not working at all, You just need to flash the file Non.Bin modem from Lollipop file again.
Glsoto said:
I think that your Wi.fi is not working at all, You just need to flash the file Non.Bin modem from Lollipop file again.
Click to expand...
Click to collapse
So do I copy NON-HLOS.bin to the Fastboot, then flash it as an image?
southpaw311 said:
So do I copy NON-HLOS.bin to the Fastboot, then flash it as an image?
Click to expand...
Click to collapse
Yes
Brilliant! Thanks very much! Now how can I flash TWRP on Marshmallow without bootloop?
I can install TWRP fine with Marshmallow. Now my issue and concern is that when I flash SuperSU (Either TWRP prompts me for install, or flash it manually), I lose everything. Stays on the logo screen, then eventually to a blank screen. How can I get SuperSU on with Marshmallow?
southpaw311 said:
I can install TWRP fine with Marshmallow. Now my issue and concern is that when I flash SuperSU (Either TWRP prompts me for install, or flash it manually), I lose everything. Stays on the logo screen, then eventually to a blank screen. How can I get SuperSU on with Marshmallow?
Click to expand...
Click to collapse
try this, http://forum.xda-developers.com/moto-x-style/development/wip-systemless-root-t3263405 - DO NOT let TWRP install SU !!!
You can use systemless root by chain fire, just flash supersu 2.62-3 version, not 2.64. Flash this file with TWRP, and keep the system partition read only, when TWRP ask it. Try this link,to download suppers file at the bottom of the page.
http://forum.xda-developers.com/app...arshmellow-t3219344/post63197935#post63197935
That worked. Thank you very much to all!

broke root?

So i just flashed android N and i think i broke root. Whne i try to boot into recovery it just hangs at the TWRP logo and i flashed su before and it doesnt appear to be on my page. Do i just revert stock or what do i do thanks. I was on pure rom and just flashed N over . Bootloader system and radio.
You have to decrypt the phone for Twrp to work on N Preview, it was like that since the first preview released.
Techno Peter said:
You have to decrypt the phone for Twrp to work on N Preview, it was like that since the first preview released.
Click to expand...
Click to collapse
how would i be able to do that
havy15 said:
how would i be able to do that
Click to expand...
Click to collapse
You need to fastboot modified boot img
Easy way out: Use TWRP 3.0.0.0 and adb sideload the SuperSU zipfile.

Bricked, bootloop tried all I can think of

I was on the last beta n4f26t, and flash TWRP successfully, then went to flash superSU from twrp, this when wrong and everything goes downhill from here. I tried flashing back the last update, in it's entirety following the Heisenberg guide for returning to stock didn't work, tried flashing twrp again still can't get into recovery (just boot loops) I tried a previous update NMF26F and got to the dead android recovery screen but when I tried to flash back the OTA nothing happened and went back to bootloop on reboot. I've used the nexus root kit and still nothing. What can I do to fix this? I've honestly looked up every resource I could think of before posting this here. really hoping I didn't perma brick my 6P
maddmarkk said:
I was on the last beta n4f26t, and flash TWRP successfully, then went to flash superSU from twrp, this when wrong and everything goes downhill from here. I tried flashing back the last update, in it's entirety following the Heisenberg guide for returning to stock didn't work, tried flashing twrp again still can't get into recovery (just boot loops) I tried a previous update NMF26F and got to the dead android recovery screen but when I tried to flash back the OTA nothing happened and went back to bootloop on reboot. I've used the nexus root kit and still nothing. What can I do to fix this? I've honestly looked up every resource I could think of before posting this here. really hoping I didn't perma brick my 6P
Click to expand...
Click to collapse
Edit I was on NPG47I the lastest beta update not n4f26t
Hello... So now you only have access to the bootloader Or bootloader and stock recovery?
If your bootloader is unlocked, you can try:
fastboot erase cache
fastboot format userdata
Of course it will wipe your internal storage...
maddmarkk said:
Edit I was on NPG47I the lastest beta update not n4f26t
Click to expand...
Click to collapse
I would concentrate on trying to get a working recovery first. Almost everyone who lost recovery mode never got their phone back- classic BLOD. First try fastboot FORMATTING recovery and then both fastboot flash twrp, and then fastboot boot twrp. If you can get a working recovery there may be hope. If you can never boot to recovery mode, I think you are done. From your bootloader screen, what is your bl version?
v12xke said:
I would concentrate on trying to get a working recovery first. Almost everyone who lost recovery mode never got their phone back- classic BLOD. First try fastboot FORMATTING recovery and then both fastboot flash twrp, and then fastboot boot twrp. If you can get a working recovery there may be hope. If you can never boot to recovery mode, I think you are done. From your bootloader screen, what is your bl version?
Click to expand...
Click to collapse
just updated it to 3.67 from the 7.1.2 beta image
maddmarkk said:
just updated it to 3.67 from the 7.1.2 beta image
Click to expand...
Click to collapse
Yes, but is that what is shown on your bootloader screen? How did you flash it? With flash-all.bat? Which 7.1.2 image did you flash and how did you do it?
v12xke said:
Yes, but is that what is shown on your bootloader screen? How did you flash it? With flash-all.bat? Which 7.1.2 image did you flash and how did you do it?
Click to expand...
Click to collapse
BL: angler-03.6.7
Baseband: angler-3.81
I see all normal BL options and I flashed it with the nexus root kit and used https://developer.android.com/preview/download-712.html this image
I know with older versions of TWRP there was a problem with the EFS partition that contains the IMEI info. What version of twrp are you using??? I thought I bricked my Nexus 6p after restoring a backup but it was actually just me screwing up my EFS partition. The newer versions of twrp (i think 3.0.3 and up) fixed this problem. Still though, if it is that, and you flash a new twrp version it won't fix your problem. If you have the time search through the forum for the EFS partition fix. I don't know the commands off the top of my head but I know this helped a lot of people. Worth a shot.
maddmarkk said:
BL: angler-03.6.7
Baseband: angler-3.81
I see all normal BL options and I flashed it with the nexus root kit and used https://developer.android.com/preview/download-712.html this image
Click to expand...
Click to collapse
OK, but when you try to boot to recovery, it bootloops? Never goes to recovery? Try the steps above to successfully flash the recovery partition using fastboot. I suppose you can use NRT, but download the latest version of TWRP and try both flashing and booting the twrp.img.
same boat
anxious to hear results: I can't get to recovery and am bootlooping - tried a bunch of things using Nexus Root Toolkit . Curiously enough earlier when I was trying to flash an older version or ressurection remix, even my TWRP would bootloop so I couldn't flash anything without it quitting - anyone ever hear of that happening?
mikeygeer said:
anxious to hear results: I can't get to recovery and am bootlooping - tried a bunch of things using Nexus Root Toolkit . Curiously enough earlier when I was trying to flash an older version or ressurection remix, even my TWRP would bootloop so I couldn't flash anything without it quitting - anyone ever hear of that happening?
Click to expand...
Click to collapse
Hello... Try looking here: https://forum.xda-developers.com/nexus-6p/help/boot-loop-death-nexus-6p-t3533528
v12xke said:
OK, but when you try to boot to recovery, it bootloops? Never goes to recovery? Try the steps above to successfully flash the recovery partition using fastboot. I suppose you can use NRT, but download the latest version of TWRP and try both flashing and booting the twrp.img.
Click to expand...
Click to collapse
I have flashed TWRP 3.1 and I can not boot into recovery, I flashed it manually with fastboot flash recovery "image"
maddmarkk said:
I have flashed TWRP 3.1 and I can not boot into recovery, I flashed it manually with fastboot flash recovery "image"
Click to expand...
Click to collapse
Hey... Did you try to boot TWRP?
From bootloader: fastboot boot twrp.img
If this fails and you only have access to the bootloader, i think you are SOL.
Good luck...
5.1 said:
Hey... Did you try to boot TWRP?
From bootloader: fastboot boot twrp.img
If this fails and you only have access to the bootloader, i think you are SOL.
Good luck...
Click to expand...
Click to collapse
you meant do this in the fastboot CMD right? if so then it just boot loops :'C
maddmarkk said:
you meant do this in the fastboot CMD right? if so then it just boot loops :'C
Click to expand...
Click to collapse
Yep from bootloader:
fastboot boot TWRP.img
I don't have any other idea sorry...
You can try to contact Google or Huawei. Even being out of warranty, some people have had their device replaced.
Good luck...
maddmarkk said:
you meant do this in the fastboot CMD right? if so then it just boot loops :'C
Click to expand...
Click to collapse
Are you able to get into recovery and adb sideload a stock OTA from the google developer website? That's always saved me when I've had problems.
DEVILOPS 007 said:
Are you able to get into recovery and adb sideload a stock OTA from the google developer website? That's always saved me when I've had problems.
Click to expand...
Click to collapse
Guess you didn't read the rest of the the thread...
We don't need more posts about bootloop. There is a main topic that has been discussed for multiple pages:
https://forum.xda-developers.com/nexus-6p/help/boot-loop-death-nexus-6p-t3533528
I personally had the issue and had to RMA the phone. I suggest you do the same.
5.1 said:
Guess you didn't read the rest of the the thread...
Click to expand...
Click to collapse
Yeah honestly I couldn't be bothered to be perfectly truthful
so i'm going thru the same thing as OP.
I need help.

twrp gets erased

Hello guys i need an urgent help yesterday i unlocked bootloader on my g5 plus which was running Android 8.1 everything was ok i installed twrp latest version it got installed but when i reeboted to system the twrp gets erased idk how whenever i try to boot into recovery it shows no command sign and then after pressing power button it boots into stock recovery ! Guys can anyone mention me a solution thread or just explain me what to do ! Thank you
Reinstall it, and then boot right into recovery. If I remember, there is a pop up when you go to close twrp and boot to system to keep twrp, or some such nag.
As far as i remember there were 2 files. dm-verity and forced encryption. I never needed them but if you stay on stock you will have to flash those so that twrp doesn't get replaced by stock recovery everytime you reboot. Check the how to root forum you should find more information there about this.
Or you can just root it and twrp won't erase with stock recover.
naikxda18 said:
Hello guys i need an urgent help yesterday i unlocked bootloader on my g5 plus which was running Android 8.1 everything was ok i installed twrp latest version it got installed but when i reeboted to system the twrp gets erased idk how whenever i try to boot into recovery it shows no command sign and then after pressing power button it boots into stock recovery ! Guys can anyone mention me a solution thread or just explain me what to do ! Thank you
Click to expand...
Click to collapse
Do this:
[email protected] said:
Reinstall it, and then boot right into recovery. If I remember, there is a pop up when you go to close twrp and boot to system to keep twrp, or some such nag.
Click to expand...
Click to collapse
and flash Disable_Dm-Verity_ForceEncrypt_02.04.2019:
https://yadi.sk/d/HLr5vjnkA8gaqw
Wolfcity said:
Do this:
and flash Disable_Dm-Verity_ForceEncrypt_02.04.2019:
https://yadi.sk/d/HLr5vjnkA8gaqw
Click to expand...
Click to collapse
hmmm, that's strange. I've never flashed that and never lost twrp on any of the phones I've unlocked. Is that new with unlocking Oreo?
Wolfcity said:
Do this:
and flash Disable_Dm-Verity_ForceEncrypt_02.04.2019:
https://yadi.sk/d/HLr5vjnkA8gaqw
Click to expand...
Click to collapse
Thanks but i flashed RR pie soon after flashing twrp now its working fine
[email protected] said:
hmmm, that's strange. I've never flashed that and never lost twrp on any of the phones I've unlocked. Is that new with unlocking Oreo?
Click to expand...
Click to collapse
I didn't either, as you wrote if you boot into TWRP before going to system it should stick or also if you flash magisk before booting the OS.
But there are some devices/ROMs that need the no verity flag to be disabled so flashing this file might help if TWRP won't stick (even when DM verity looks for a tampered system partition in the first case). There are also some terminal commands to do that but I forgot them at the moment.
I mainly used the zip to keep my /data partition decrypted after reformating it. When flashing Nougat magisk did the job for me but when I upgraded to Oreo /data was reencrypted again after flashing magisk and booting into system.
The above zip prevents /data from being encrypted again and may make sure that TWRP sticks.
ahhh, ok I see. Thanks for the explanation.

Categories

Resources