Nexus 6 MRA58K gets stuck on Google screen - Nexus 6 Q&A, Help & Troubleshooting

Hello XDA,
I'm using WUG toolkit.
I'm having an issue that after I upgrade to MRA58K. I'm unable to flash custom roms or make changes (remove google apps) to the stock rom. I'm able to root and flash twrp. Once I reboot it get's stuck on the google boot screen if remove the stock apps. It also gets stuck if I reboot to recovery and flash one of the custom MRA58K roms.
Any suggestions are appreciated.

sawyer815 said:
Hello XDA,
I'm using WUG toolkit.
I'm having an issue that after I upgrade to MRA58K. I'm unable to flash custom roms or make changes (remove google apps) to the stock rom. I'm able to root and flash twrp. Once I reboot it get's stuck on the google boot screen if remove the stock apps. It also gets stuck if I reboot to recovery and flash one of the custom MRA58K roms.
Any suggestions are appreciated.
Click to expand...
Click to collapse
do you remember to wipe data beforw flashing ghe custom rom?

simms22 said:
do you remember to wipe data beforw flashing ghe custom rom?
Click to expand...
Click to collapse
Yup. I was able to get things working after flashing chainfire's modified boot.img after flashing the rom.
http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344

Related

[Q] Cant install 4.19.401.11 stock recovery.

Hello guys, I need an help! I have reinstalled a 4.4.2 stock ROM on my phone, because I had some problems with ARHD 53.0, and decided to return stock waiting for 63.0. Anyways, I am curious about a thing. I have TWRP 2.6.3.3 installed on my phone, last firmware (4.19.401.11), stock kernel, rooted, last hboot, no fastboot option activated and, when I try to flash the stock recovery of 4.19.401.11, it always fails; it doesnt open but shows the warning red sign screen. Instead, I can install TWRP recovery without any problems. What is the reason for this? I always erase cache from fastboot before and after recovery flashing. thanks to everyone!
diego9416 said:
Hello guys, I need an help! I have reinstalled a 4.4.2 stock ROM on my phone, because I had some problems with ARHD 53.0, and decided to return stock waiting for 63.0. Anyways, I am curious about a thing. I have TWRP 2.6.3.3 installed on my phone, last firmware (4.19.401.11), stock kernel, rooted, last hboot, no fastboot option activated and, when I try to flash the stock recovery of 4.19.401.11, it always fails; it doesnt open but shows the warning red sign screen. Instead, I can install TWRP recovery without any problems. What is the reason for this? I always erase cache from fastboot before and after recovery flashing. thanks to everyone!
Click to expand...
Click to collapse
The red warning triangle is stock
mb_guy said:
The red warning triangle is stock
Click to expand...
Click to collapse
So the normal HTC stock recovery cant be used for flashing, etc? just for the OTA? Was just curious about, dont want to keep stock recovery but wondered about it
You need a custom recovery to flash any roms. Stock recovery is for OTA's. If you aren't worried about them I'd leave the custom recovery on
Sent from my HTC One using XDA Premium 4 mobile app
5 29865659
nateboi81 said:
You need a custom recovery to flash any roms. Stock recovery is for OTA's. If you aren't worried about them I'd leave the custom recovery on
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Perfect, was just curious to know about stock recovery functions thank you all
diego9416 said:
Hello guys, I need an help! I have reinstalled a 4.4.2 stock ROM on my phone, because I had some problems with ARHD 53.0, and decided to return stock waiting for 63.0. Anyways, I am curious about a thing. I have TWRP 2.6.3.3 installed on my phone, last firmware (4.19.401.11), stock kernel, rooted, last hboot, no fastboot option activated and, when I try to flash the stock recovery of 4.19.401.11, it always fails; it doesnt open but shows the warning red sign screen. Instead, I can install TWRP recovery without any problems. What is the reason for this? I always erase cache from fastboot before and after recovery flashing. thanks to everyone!
Click to expand...
Click to collapse
i also need 4.19.401.11 stock recovery but can not find it. can you share it with me? its important, i have no recovery now and i must install sense 6 update
erhangulsum said:
i also need 4.19.401.11 stock recovery but can not find it. can you share it with me? its important, i have no recovery now and i must install sense 6 update
Click to expand...
Click to collapse
You always have a recovery.. that would be ODD to not have one.. Here is it http://d-h.st/Igg Thanks to @Guich

[Q] Hboot 1.57 OS 5.11.401.10 reboot loop

Hi,
I just got a brand new HTC One 7 (WWE, CID E_11) after my last one died. Im trying to root it and install a custom recovery to install arhd or insertcoin. I used htc one toolkit for this. Everything seemed to work ok, but after booting the installed rom (ARHD or insertcoin) the phone reboots after i see the login screen. I somehow managed to reinstall my phone again yesterday, as it was a complete (soft) brick.
I used this to return to stock:
http://forum.xda-developers.com/showthread.php?t=2759000
Now does anyone know why I get a reboot loop? Does anyone know if i installed this stock rom if I get the normal OTA updates again? And do i need to relock the bootloader for this? I would really like to install stock roms again but I'm a little anxious after yesterday. (I've installed custom roms since the old HD2/HTC desire, and also on my old HTC One M7, never had any problems, I think it has to do with the Hboot).
Hoping to hear from you guys,
best wishes,
Olaf
Agil1ty said:
Hi,
I just got a brand new HTC One 7 (WWE, CID E_11) after my last one died. Im trying to root it and install a custom recovery to install arhd or insertcoin. I used htc one toolkit for this. Everything seemed to work ok, but after booting the installed rom (ARHD or insertcoin) the phone reboots after i see the login screen. I somehow managed to reinstall my phone again yesterday, as it was a complete (soft) brick.
I used this to return to stock:
http://forum.xda-developers.com/showthread.php?t=2759000
Now does anyone know why I get a reboot loop? Does anyone know if i installed this stock rom if I get the normal OTA updates again? And do i need to relock the bootloader for this? I would really like to install stock roms again but I'm a little anxious after yesterday. (I've installed custom roms since the old HD2/HTC desire, and also on my old HTC One M7, never had any problems, I think it has to do with the Hboot).
Hoping to hear from you guys,
best wishes,
Olaf
Click to expand...
Click to collapse
Flash the stock firmware 5.11.401.10! I think your firmware is mismatched.
By flashing the firmware after installing the Rom I might fix the bootloop? Or is the stock firmware necesarry to go back to stock? Sorry bit confused, thanks for your response btw
Sent from my HTC One using XDA Free mobile app
Agil1ty said:
By flashing the firmware after installing the Rom I might fix the bootloop? Or is the stock firmware necesarry to go back to stock? Sorry bit confused, thanks for your response btw
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
Flashing the firmware might fix the boot-loop, since you flashed the stock rom! If it does stop the boot-loops, you can re-install TWRP or CWM to get the custom recovery.
Agil1ty said:
By flashing the firmware after installing the Rom I might fix the bootloop? Or is the stock firmware necesarry to go back to stock? Sorry bit confused, thanks for your response btw
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
when using a sense custom rom you need to make sure you use twrp 2.6.3.3 recovery, do not use the toolkits, most of the time they are out of date and not updated, this would explain the bootloops, take the time to learn how to use adb and fastboot, you'll never look back.
nothing to do with the firmware and no need to flash it, if your firmware was knackered, you would have a hard brick.
Seanie280672 said:
when using a sense custom rom you need to make sure you use twrp 2.6.3.3 recovery, do not use the toolkits, most of the time they are out of date and not updated, this would explain the bootloops, take the time to learn how to use adb and fastboot, you'll never look back.
nothing to do with the firmware and no need to flash it, if your firmware was knackered, you would have a hard brick.
Click to expand...
Click to collapse
First of all thanks for the quick response. I know how to use adb and fastboot (at least I think).
If i would (in this order) do the following, would that be correct?:
unlock using htdev
Flash twrp 2.6.3.3 using fastboot command: "fastboot flash recovery recovery.img" (naming twrp 2.6.3.3.img = recovery.img)
reboot bootloader
Flash SuperSU.zip in TWRP
reboot twrp
flash custom rom (ARHD).
The thing is it isn't a normal bootloop (which normally would come with the HTC logo all the time)
It reboots when I try to setup the phone (in the setup menu). Restoring the phone with the link in the OP, ive recoverd my phone, but I would still love to use custom roms again.
Agil1ty said:
First of all thanks for the quick response. I know how to use adb and fastboot (at least I think).
If i would (in this order) do the following, would that be correct?:
unlock using htdev
Flash twrp 2.6.3.3 using fastboot command: "fastboot flash recovery recovery.img" (naming twrp 2.6.3.3.img = recovery.img)
reboot bootloader
Flash SuperSU.zip in TWRP
reboot twrp
flash custom rom (ARHD)
Click to expand...
Click to collapse
unlock using HTC Dev
flash TWRP 2.6.3.3
fastboot erase cache
fastboot reboot-bootloader
enter recovery
no need to flash super user it will be included in the rom you flash
flash custom rom, or stock reset rom, if its not rooted, twrp will ask you if you would like to root upon exit.
Seanie280672 said:
unlock using HTC Dev
flash TWRP 2.6.3.3
fastboot erase cache
fastboot reboot-bootloader
enter recovery
no need to flash super user it will be included in the rom you flash
flash custom rom, or stock reset rom, if its not rooted, twrp will ask you if you would like to root upon exit.
Click to expand...
Click to collapse
It seems that insertcoin had a problem in it's installer:
http://insertcoin-roms.org/category/devices/one_m7/one_sense6/
the changelog says: Fixed SuperSU install (might solve the sudden reboot issue in SetupWizard)
It left me without any rom to install, so i had to sideload ARHD, which it didnt want to install via sideload... The next step I isntalled stock again, which I'm using right now.. but I miss xposed framework and other tweaks too much..
I'm gonna try to unlock it again this afternoon and install insertcoin again, but this time ill make a backup first. Does installing the recovery wipe anything?
Agil1ty said:
It seems that insertcoin had a problem in it's installer:
http://insertcoin-roms.org/category/devices/one_m7/one_sense6/
the changelog says: Fixed SuperSU install (might solve the sudden reboot issue in SetupWizard)
It left me without any rom to install, so i had to sideload ARHD, which it didnt want to install via sideload... The next step I isntalled stock again, which I'm using right now.. but I miss xposed framework and other tweaks too much..
I'm gonna try to unlock it again this afternoon and install insertcoin again, but this time ill make a backup first. Does installing the recovery wipe anything?
Click to expand...
Click to collapse
no it doesn't wipe anything, but you can use xposed and its tweaks on stock rom, you just need to root first, just install TWRP, enter recovery and again upon exit it will offer to root stock rom for you.

[Q] Decrypt if I'm already rooted with unlocked boot loader??

So I have a T-mo rooted Nexus 6 running stock rom and kernel presently. I would like to decrypt the phone as I've heard/read I will see an improvement in both performance and battery life. So first question is what would be the best/easiest method to do this and second will I lose root and have to re-root after decrypting. Thanks in advance for any help.
Basically you will have to flash a different boot image that disable the encryption flag.
This will require you to completely wipe your device and start over. Yes, you would have to re-root but if you know how to flash a stock no-encrypt image then rooting is easy and simply requires you to flash the current SuperSU zip from recovery once you are all set up.
Basically follow the long version of this guide. Technically you don't need to flash completely stock and couold just follow the guide in the next section but if you have to factory reset anyway I would want to start fresh:http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
But use this no-encrypt boot image instead that matches the stock google rom you flash:http://forum.xda-developers.com/nexus-6/development/disable-forced-encryption-gain-root-t2946715
Once that is done you can flash recovery (or simply boot into TWRP temporarily if you want to keep the stock recovery) and flash Supersu.zip from here and then you're rooted again. I think you could also flash TWRP in the first step above when you are going back to stock but I usually do it at the end for some reason:http://forum.xda-developers.com/showthread.php?t=1538053
Thank you so much

Downgrading from Marshmallow if I have custom recovery

Hi everyone, this question was asked already but I just want to make sure that it's safe to flash a 5.1 based ROM over a currently active Marshmallow ROM using TWRP using only the usual wipes? I remember that I had to flash a custom boot image with a PC or something like that in order for the custom recovery to work on my K3 Note, which I received with Marshmallow installed, so I'm not sure if I can hop back to 5.1 if phone never even had it installed. Any advice?
livgrave said:
Hi everyone, this question was asked already but I just want to make sure that it's safe to flash a 5.1 based ROM over a currently active Marshmallow ROM using TWRP using only the usual wipes? I remember that I had to flash a custom boot image with a PC or something like that in order for the custom recovery to work on my K3 Note, which I received with Marshmallow installed, so I'm not sure if I can hop back to 5.1 if phone never even had it installed. Any advice?
Click to expand...
Click to collapse
Yes, IT IS SAFE but there are some points to note:
Every Rom Zip contains a boot.img file which is also flashed when the zip is flashed.
You do not need to replace boot.img in order to install TWRP, but you need it to flash SuperSU.zip to your device or install xposed
Remember You need to wipe data partition (No need to wipe Internal) in order to continue.
Thanks for the reply. I don't know why, but I remember when I was installing TWRP I couldn't boot into it until I flashed a new boot image or something like that. All I could boot into was the stock recovery or something like that. I needed to use SP flash tools and flash something in order to get it to work. So it's safe for me to try 5.1 ROMs? They seem to be more stable than custom Marshmallow ROMs....
livgrave said:
Thanks for the reply. I don't know why, but I remember when I was installing TWRP I couldn't boot into it until I flashed a new boot image or something like that. All I could boot into was the stock recovery or something like that. I needed to use SP flash tools and flash something in order to get it to work. So it's safe for me to try 5.1 ROMs? They seem to be more stable than custom Marshmallow ROMs....
Click to expand...
Click to collapse
You must have flashed the recovery.img ( and also the boot.img) because my root methods mention them.

[Q] TWRP lost after flashing 4.1.3

I've recently flashed my OP3T with stock ROM 4.1.3, & do the clean flash with TWRP. After finished, when I went back to the recovery mode, TWRP is lost, and the recovery goes back to stock recovery. Every time I start up/reboot my phone, I always get the DM-Verify warning.
Anyone can point me why after flashed the 4.1.3, my recovery goes back to stock recovery?
Also, which method should I use to change the stock recovery to TWRP & bypass the DM-Verify warning?
Thanks in advance
As for the TWRP, after flashing with TWRP you have to boot into Recovery and root (SuperSu/Magisk).
Only then TWRW sticks.
As for the DM-Verify, there is a thread here how to do.
Honestly, the DM-Verify doesn't bother me, so I don't bother to remove it
Cheers
Tom
tom1807 said:
As for the TWRP, after flashing with TWRP you have to boot into Recovery and root (SuperSu/Magisk).
Only then TWRW sticks.
As for the DM-Verify, there is a thread here how to do.
Honestly, the DM-Verify doesn't bother me, so I don't bother to remove it
Cheers
Tom
Click to expand...
Click to collapse
Thanks for the answer, . Actually when I flashed with 4.1.3, it came from the Experience ROM, ver. 17. After flashed with the stock 4.1.3, when I went back to the recovery, the TWRP is gone, replaced by the stock recovery. I thought that when we flash via custom recovery such as TWRP, it will bypass to flash recovery, CMIIW.
When you flash stock ROM, the image will contain the stock recovery, so you will need to reflash twrp from fast boot
Sent from my ONEPLUS A3003 using Tapatalk
Booting up default ROM, it will make sure recovery is original and if not it will restore it just like it did for you. TWRP rooting will remove the original recovery making it impossible to break TWRP for you.
ben_pyett said:
When you flash stock ROM, the image will contain the stock recovery, so you will need to reflash twrp from fast boot
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
You don't have to. Just flash magisk or SuperSU right after the ROM, you will get both root and twrp

Categories

Resources