Develop Bugs

[Q] Stuck at google logo WHILE USING

Well, something strange happened and i have no idea what the prob is
yesterday i installed a new kernel for my gnex and made a backup (using CWM) before flashing. Today i decided to go back to the previous kernel so i just went to recovery and restored from the backup. It installed successfully and then i rebooted my phone twice just to be sure everything was working and it was untill 4-5 hours later, I was playing a game (temple run) when suddenly the phone turned off and restarted by itself, i though maybe the game crashed and its restarting but i kept waiting for an hour but the phone was just stuck at the google logo. After waiting, i decided to go to recovery and flash a new kernal or restore but when i went to the bootloader and selected recovery, the phone didnt go into recovery but its stuck in google loop again. so somehow i think the recovery has been deleted of something like that because it gets stuck in loop if i go to recovery :/
i am on 4.0.3 codenamed android rom
Thanks
EDIT: I have already tried removing the battery for some time but still i am not able to enter recovery. i thought recovery was to prevent such things :$

You should probably use search next time. It's happened to quite a few people (myself included).
Use fastboot/ODIN to flash stock rom again.

case0 said:
You should probably use search next time. It's happened to quite a few people (myself included).
Use fastboot/ODIN to flash stock rom again.
Click to expand...
Click to collapse
Thanks but i wont be able to recover my data using this right?:/

No I don't think so, it sucks. I thought they had fixed this bug in 4.0.3 though which is strange. I lost my data twice within a month because of this, when I was on 4.0.2 (or maybe 4.01). Haven't had it since I rooted and updated.

Try flashing the recovery again. Maybe it will work.

case0 said:
No I don't think so, it sucks. I thought they had fixed this bug in 4.0.3 though which is strange. I lost my data twice within a month because of this, when I was on 4.0.2 (or maybe 4.01). Haven't had it since I rooted and updated.
Click to expand...
Click to collapse
can you tell me which tut to follow? i searched and found ODIN files for 4.0.4 and 4.0.2 but i'm on 4.0.3
sry but this is my first android phone and i have no previous knowledge
efrant said:
Try flashing the recovery again. Maybe it will work.
Click to expand...
Click to collapse
already tried that. manually and also using toolkit but i get the same error something like "recovery status read failed too many links"
Thanks for replies btw

rollerdyke44 said:
can you tell me which tut to follow? i searched and found ODIN files for 4.0.4 and 4.0.2 but i'm on 4.0.3
sry but this is my first android phone and i have no previous knowledge
already tried that. manually and also using toolkit but i get the same error something like "recovery status read failed too many links"
Thanks for replies btw
Click to expand...
Click to collapse
Use the Odin files for 4.0.4. Why are you looking for 4.0.3?
Sent from my Galaxy Nexus using Tapatalk 2

efrant said:
Use the Odin files for 4.0.4. Why are you looking for 4.0.3?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
well i am on codenamed android based on 4.0.3 so i was looking for 4.0.3 files for ODIN. this will flash my firmware to stock 4.0.4 right?
And do you know of ANY WAY i can fix my phone so that i can recover my data? I have tried everything but to no avail. i have tried flashing recovery, booting recovery (not flashing) using different usb ports and cables, flashing boot.img from codename android and everything i read online :/

rollerdyke44 said:
this will flash my firmware to stock 4.0.4 right?
Click to expand...
Click to collapse
Yes.
rollerdyke44 said:
And do you know of ANY WAY i can fix my phone so that i can recover my data? I have tried everything but to no avail. i have tried flashing recovery, booting recovery (not flashing) using different usb ports and cables, flashing boot.img from codename android and everything i read online :/
Click to expand...
Click to collapse
What happens when you boot CWM?
In order to recover anything, you need to be booted either into Android or CWM.
Maybe try using the "no-wipe" odin files, which may allow you to either boot into the ROM or allow you to boot CWM, and then you can retrieve your data. However, if this does work, I would recommend you wipe right after you retrieve your data, then restore your files, as you may have issues later on running with that data on your device.

efrant said:
Yes.
What happens when you boot CWM?
In order to recover anything, you need to be booted either into Android or CWM.
Maybe try using the "no-wipe" odin files, which may allow you to either boot into the ROM or allow you to boot CWM, and then you can retrieve your data. However, if this does work, I would recommend you wipe right after you retrieve your data, then restore your files, as you may have issues later on running with that data on your device.
Click to expand...
Click to collapse
thanks for your quick reply mate
I am not able to boot into recovery. When i select enter recovery from bootloader then it just loops on the google logo. When i try to reinstall cwm then it fails everytime with the error i mentioned above
ohh and btw, sometimes when the cwm installation fails then the bootloader gets stuck and the screen becomes kind of blurry and i have to take out the battery...... is that normal?
And i'll first try the no wipe files (from here http://forum.xda-developers.com/showthread.php?t=1586807&highlight=odin) and see if that works

rollerdyke44 said:
thanks for your quick reply mate
I am not able to boot into recovery. When i select enter recovery from bootloader then it just loops on the google logo. When i try to reinstall cwm then it fails everytime with the error i mentioned above
ohh and btw, sometimes when the cwm installation fails then the bootloader gets stuck and the screen becomes kind of blurry and i have to take out the battery...... is that normal?
And i'll first try the no wipe files (from here http://forum.xda-developers.com/showthread.php?t=1586807&highlight=odin) and see if that works
Click to expand...
Click to collapse
What happens when you boot CWM via fastboot?
fastboot boot cwm.img

efrant said:
What happens when you boot CWM via fastboot?
fastboot boot cwm.img
Click to expand...
Click to collapse
i get a blurry recovery mode picture (that hat kind of thing) for a couple of secs and then the phone reboots and again in boot loop[

rollerdyke44 said:
i get a blurry recovery mode picture (that hat kind of thing) for a couple of secs and then the phone reboots and again in boot loop[
Click to expand...
Click to collapse
Oou, that doesn't sound good. Not sure you'd be able to save your data.

efrant said:
Oou, that doesn't sound good. Not sure you'd be able to save your data.
Click to expand...
Click to collapse
well lets hope for the best
And i was on codenamed 4.0.3 so if i use the "no-wipe" files for 4.0.4 it should not cause anymore problems right?
I'll first use ODIN with no wipe files and if that doesnt work then i guess i'll say bye bye to my data and do a full wipe.
Thanks for you help mate and i will reply with the result in an hour or so (dinner time now )
Thanks again
EDIT:
so i ran ODIN but now its stuck. the start button has been greyed out with the following message
"<ID:0/011> Added!!
<ID:0/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
"
and the phone is on the ODIN download mode screen :/
EDIT 2:
when i use the full image, then the ODIN downloading screen on my nexus becomes blurry when ODIN on pc shows "<ID:0/011> NAND Write Start!! "
PLease help as i really dont know what else can i do

Fu*kkkkk
i think its bricked now i cant even access the bootloader the phone doesnt even turn on now i cant even get the google logo just a black screen

rollerdyke44 said:
Fu*kkkkk
i think its bricked now i cant even access the bootloader the phone doesnt even turn on now i cant even get the google logo just a black screen
Click to expand...
Click to collapse
It may not be bricked. Not being able to get into the bootloader can happen when you flash via odin.
Can you not boot into download mode (hold volume down and then press and hold power)? If you can, then you can still flash via odin.
I haven't really used odin too much, so I won't be able to help you troubleshoot too much (maybe ask in Chainfire's thread), but: if you can boot into download mode, do it, and re-follow the instructions in this post to-the-letter. Use the full odin image, not the no-wipe one.

efrant said:
It may not be bricked. Not being able to get into the bootloader can happen when you flash via odin.
Can you not boot into download mode (hold volume down and then press and hold power)? If you can, then you can still flash via odin.
I haven't really used odin too much, so I won't be able to help you troubleshoot too much (maybe ask in Chainfire's thread), but: if you can boot into download mode, do it, and re-follow the instructions in this post to-the-letter. Use the full odin image, not the no-wipe one.
Click to expand...
Click to collapse
noooooo
i cant even get the fone in download mode. the phone screen is completely black!!!! Wont even vibrate which shows its starting up
pleaaassseeee heeelppp
now i am getting scared for my nexus

rollerdyke44 said:
noooooo
i cant even get the fone in download mode. the phone screen is completely black!!!! Wont even vibrate which shows its starting up
pleaaassseeee heeelppp
now i am getting scared for my nexus
Click to expand...
Click to collapse
Take a slow deep breath and exhale. Take out the battery. Wait for a while. Put the battery back in.
Hold down the volume down button (not the volume up) and then press and hold power for 15 secs. See if that gets you into download mode. Even if nothing shows up on the screen, try following the steps in the odin thread.
You did make sure only the checkmarks that needed to be there were there in odin, correct?

efrant said:
Take a slow deep breath and exhale. Take out the battery. Wait for a while. Put the battery back in.
Hold down the volume down button (not the volume up) and then press and hold power for 15 secs. See if that gets you into download mode. Even if nothing shows up on the screen, try following the steps in the odin thread.
You did make sure only the checkmarks that needed to be there were there in odin, correct?
Click to expand...
Click to collapse
Which checkmarks should be used?

TwinkyOfHope said:
Which checkmarks should be used?
Click to expand...
Click to collapse
Why don't you take a look at the linked (a few posts up) odin thread and see for yourself?

AOKP to STOCK BIG PROBLEMS

i need some help here guys. i was running AOKP for the longest time and loving it. then today i tried to update to the latest version. i downloaded the rom and went to flash the .zip in CWM. i've done this dozens of times. this time things were completely different. i kept getting FCs over and over. so i booted into recovery again to reflash. for whatever reason, it seemed like my file system was corrupted. folders i had never seen were all over the place. it was a big mess. i decided to flash back to stock. i booted into DL mode and did this with odin successfully. then upon reboot, the phone was stuck at the Samsung logo. looking into this i saw that i needed to boot into recovery, wipe data/factory reset, wipe cache, and wipe dalvik cache. i tried doing this but no matter what, my phone will not boot into recovery. i have even used odin to flash CF-SGS3-CWM-v5.5-v1.0.tar. when i press volume up+home+power i get the first samsung logo with the tiny blue text up at the top saying "recovery booting" but then nothing happens and the phone just goes to a normal boot attempt, which stalls at the samsung logo. please help guys. just for a quick overview. was on [ROM] AOKP(Jellybean 4.2.1 )Task & Ktoonsez (12/23) (AT&T/Rogers), potential file system corruption during a routine upgrade, flashed back to stock with odin (meaning i can still boot into DL mode), but CANNOT boot into RECOVERY mode. i'm freaking out

jamesquags said:
i need some help here guys. i was running AOKP for the longest time and loving it. then today i tried to update to the latest version. i downloaded the rom and went to flash the .zip in CWM. i've done this dozens of times. this time things were completely different. i kept getting FCs over and over. so i booted into recovery again to reflash. for whatever reason, it seemed like my file system was corrupted. folders i had never seen were all over the place. it was a big mess.
i decided to flash back to stock. i booted into DL mode and did this with odin successfully. then upon reboot, the phone was stuck at the Samsung logo. looking into this i saw that i needed to boot into recovery, wipe data/factory reset, wipe cache, and wipe dalvik cache. i tried doing this but no matter what, my phone will not boot into recovery.
i have even used odin to flash CF-SGS3-CWM-v5.5-v1.0.tar. when i press volume up+home+power i get the first samsung logo with the tiny blue text up at the top saying "recovery booting" but then nothing happens and the phone just goes to a normal boot attempt, which stalls at the samsung logo. please help guys.
just for a quick overview. was on [ROM] AOKP(Jellybean 4.2.1 )Task & Ktoonsez (12/23) (AT&T/Rogers), potential file system corruption during a routine upgrade, flashed back to stock with odin (meaning i can still boot into DL mode), but CANNOT boot into RECOVERY mode. i'm freaking out
Click to expand...
Click to collapse
First of all, good job on searching before posting! :good:
Second, if you want help, try using capital letters at the start of a sentence and using paragraphs. It makes it sooo much easier to read that way.
Third, just keep trying. But from what you're saying about a file-system issue, that could be bad? It's not familiar to me anyways. Hope it didn't damage the internal SD.
If nothing else works, then try the USB-JIG to access Recovery mode. They're like $5 on eBay.
Okay, try these things.
1) Odin a non-rooted, stock ROM that comes with a 3E recovery and try to access that recovery.
If that doesn't work, move onto this step:
2) Odin a different recovery. I attached one to this post. Just unzip it and then odin it. :CWM-Recovery-LTE-SGS3-v5.tar:
Try to get recovery again after a battery pull.

If that doesn't do it, then try this next:
1) Odin a rooted ROM onto the phone.
2) Download the attached "openrecovery-twrp-2.3.1.0-d2att" and unzip it.
3) Download this ADB & Fastboot tool and extract it to your C:/ drive with subfolders using this path: "C:/Android/platform-tools/".
Here is the file to download:
http://www.androidfilehost.com/?fid=9390135922294523275
4) Rename the openrecovery-twrp-2.3.1.0-d2att to "recovery" and place it into the Platform-tools folder.
5) Open the JPEG and follow the EXACT same commands in the pic. This will install TWRP recovery for you.
Then try once again to get into recovery.
If it still doesn't work, then buy a USB Jig.

REPLY
Thanks so much for the advice.
Regarding the TWRP installation, is the phone connected to the computer in DL mode for this?
I am currently downloading a rooted stock ROM. This might help shed light on what is going on here.... I unzipped the .tar you attached to your first post and stuck it in the PDA slot with the phone connected and in DL mode. ODIN did nothing and the returned a FAIL message saying that it "Failed to Open Serial [COM] Port". Hmmmm. Anyways I am going to try to install the TWRP recovery. If not I will buy the USB jig. Thanks again for you help. -jim

jamesquags said:
"Failed to Open Serial [COM] Port".
Click to expand...
Click to collapse
Have you installed the phone drivers? They're linked from the Odin thread.

smelenchuk said:
Have you installed the phone drivers? They're linked from the Odin thread.
Click to expand...
Click to collapse
Yes i have installed the drivers. I have flashed multiple .tar files today.

jamesquags said:
Thanks so much for the advice.
Regarding the TWRP installation, is the phone connected to the computer in DL mode for this?
I am currently downloading a rooted stock ROM. This might help shed light on what is going on here.... I unzipped the .tar you attached to your first post and stuck it in the PDA slot with the phone connected and in DL mode. ODIN did nothing and the returned a FAIL message saying that it "Failed to Open Serial [COM] Port". Hmmmm. Anyways I am going to try to install the TWRP recovery. If not I will buy the USB jig. Thanks again for you help. -jim
Click to expand...
Click to collapse
The TWRP doesn't use Odin. You have to use ADB/FastBoot like I show in the picture attached with it.
I have yet to find an Odin flashable TWRP.

CZ Eddie said:
The TWRP doesn't use Odin. You have to use ADB/FastBoot like I show in the picture attached with it.
I have yet to find an Odin flashable TWRP.
Click to expand...
Click to collapse
After flashing the ROOTED STOCK ROM, I tried about 7 times to boot into recovery. It finally did!!! I then was able to do a wipe data and cache and I'm all set.
Thanks so much for helping me out. -jim

To get into recovery hold the power+volume up+ home key when you see the blue text at the top of the screen let go if the power button but still press the home + volume up
Sent from my SGH-I747 using Tapatalk 2

jerrycoffman45 said:
To get into recovery hold the power+volume up+ home key when you see the blue text at the top of the screen let go of the power button but still press the home + volume up
Click to expand...
Click to collapse
Why do you continue to hold the home + volume up? I release all three as soon as I see the blue text and it goes into Recovery just fine for me.

CZ Eddie said:
Why do you continue to hold the home + volume up? I release all three as soon as I see the blue text and it goes into Recovery just fine for me.
Click to expand...
Click to collapse
i dont know i have always done it that way well learned something new just tried it your way thanks

Soft bricked

Hello everyone, today I installed TWRP recovery, it went fine and I am not new to install custom roms, custom recoveries, etc. but this got my phone messed up. It was working perfectly fine and then I turned it off in the night and in the morning, it just got stuck in a bootloop, and knowing me of course, I forgot to create a backup as I installed TWRp. So, is there any kind fellow out there that has a TWRP backup at hand for the ZE551ML?

Just to get the order correct...
Flashed TWRP - No problem
Rebooted to system - No problem
System worked?
Turned off phone
Bootloop on power on?
Is this a bootloop, or does it just sit on the Asus screen? Does it get to the actual boot animation, or are you on the splash screen?

Harfainx said:
Just to get the order correct...
Flashed TWRP - No problem
Rebooted to system - No problem
System worked?
Turned off phone
Bootloop on power on?
Is this a bootloop, or does it just sit on the Asus screen? Does it get to the actual boot animation, or are you on the splash screen?
Click to expand...
Click to collapse
I am getting to the boot animation with the gears turning and then error comes up and boots me into TWRP. The problem is, the Bootloader will not come up so I can do the fastboot flashing, TWRP comes up instead. It comes up and I didn't overwrite the bootloader with TWRP. Problem is I can't access fastboot commands.

Lurkingintheshadows said:
I am getting to the boot animation with the gears turning and then error comes up and boots me into TWRP. The problem is, the Bootloader will not come up so I can do the fastboot flashing, TWRP comes up instead. It comes up and I didn't overwrite the bootloader with TWRP. Problem is I can't access fastboot commands.
Click to expand...
Click to collapse
Give me a few minutes. I'll get you a TWRP flashable boot.img zip.

Try flashing this in TWRP. You might need to sideload it onto your phone if you can't boot into system.

Harfainx said:
Try flashing this in TWRP. You might need to sideload it onto your phone if you can't boot into system.
Click to expand...
Click to collapse
Thank you. But, it won't flash, I've tried about every option now. I think I'm just going to see if I can get a replacement. 2.19 was always causing me problems to install and then now that I finally got it on my phone, I couldn't install another 2.19 on top of it or downgrade. Guess this phone is done for until CM12 gets released. Thanks for the help but it seems it can't be recovered at this point.

Lurkingintheshadows said:
Thank you. But, it won't flash, I've tried about every option now. I think I'm just going to see if I can get a replacement. 2.19 was always causing me problems to install and then now that I finally got it on my phone, I couldn't install another 2.19 on top of it or downgrade. Guess this phone is done for until CM12 gets released. Thanks for the help but it seems it can't be recovered at this point.
Click to expand...
Click to collapse
If you lurk on these forums, there are some Intel flashing tools I've seen that can help you recover from a soft brick.

I am stuck too!
I was in stock recovery and did a cache wipe. It took forever and wouldn't come out of it so i powered it off and tried booting. It got stuck on bootloop. phone is asus zenfone 2 Z00A. It is intel chipset. please help me out.
the worst part is that i cant get into fastboot or recovery modes so i am completely stuck! please help me out.
when i try to get into fastboot mode with vol up+ power key it vibrates but nothing is displayed.
if i just power it on its stuck on bootloop.
i can't get into recovery and fastboot bcoz its at the same place.
can i use adb commands or fastboot commands somehow?
i can maybe use adb reboot recovery to get into recovery and then i can do a wipe and flash new stuff.
please help me out.
UPDATE: I found out u can use adb reboot recovery while on the asus bootanimation.
i tried adb reboot recovery and now getting a flashing android sleeping bot with error!
can't use adb or fastboot commands now though
now in even bigger mess. after using adb reboot recovery, i can't get to bootanimation either.
just stuck at flashing android sleeping bot with error.
can't get to bootloader or fastboot or anything!
Please any suggestions. I'm dying here to fix it.
I have a adb backup.
i couldn't take a nandroid backup. i just entred recovery and wiped cache first. after doing that i was going to flash twrp and then using twrp take a nandroid backup and flash a custom rom. but it got stuck at cache wipe and i powered it off and the whole mess.:
Finally entered bootloader with fastboot now working!
Content and satisfied

I_am_sid said:
I was in stock recovery and did a cache wipe. It took forever and wouldn't come out of it so i powered it off and tried booting. It got stuck on bootloop. phone is asus zenfone 2 Z00A. It is intel chipset. please help me out.
the worst part is that i cant get into fastboot or recovery modes so i am completely stuck! please help me out.
when i try to get into fastboot mode with vol up+ power key it vibrates but nothing is displayed.
if i just power it on its stuck on bootloop.
i can't get into recovery and fastboot bcoz its at the same place.
can i use adb commands or fastboot commands somehow?
i can maybe use adb reboot recovery to get into recovery and then i can do a wipe and flash new stuff.
please help me out.
UPDATE: I found out u can use adb reboot recovery while on the asus bootanimation.
i tried adb reboot recovery and now getting a flashing android sleeping bot with error!
can't use adb or fastboot commands now though
now in even bigger mess. after using adb reboot recovery, i can't get to bootanimation either.
just stuck at flashing android sleeping bot with error.
can't get to bootloader or fastboot or anything!
Please any suggestions. I'm dying here to fix it.
I have a adb backup.
i couldn't take a nandroid backup. i just entred recovery and wiped cache first. after doing that i was going to flash twrp and then using twrp take a nandroid backup and flash a custom rom. but it got stuck at cache wipe and i powered it off and the whole mess.:
Finally entered bootloader with fastboot now working!
Content and satisfied
Click to expand...
Click to collapse
how did you get fastboot working? I can get into bootloader, but cant get my pc to connect with my zenfone2. can't use any adb cmd it would just say "error: can't find devices"

I_am_sid said:
I was in stock recovery and did a cache wipe. It took forever and wouldn't come out of it so i powered it off and tried booting.
Click to expand...
Click to collapse
Just a reminder to everyone, never force shutdown the Phone during a cache wipe procedure, it takes a long time but it finishes.
When I did it on my ZF2, I thought it was taking too long, but I did a search here and found out about it taking long before it was too late.
I'm glad you could recover yours. :good:

I shut mine down because it took too long. Wouldn't start up again. Had to send it in for RMA. Asus Canada reset the OS. I'll never do that again.
Sent from my ASUS_Z00AD using XDA-Developers mobile app

ikkuy said:
how did you get fastboot working? I can get into bootloader, but cant get my pc to connect with my zenfone2. can't use any adb cmd it would just say "error: can't find devices"
Click to expand...
Click to collapse
Dude you can never use adb when in bootloader.
That's why you have fastboot.
just type
fastboot devices
you will get your device.
if you don't then download intel drivers. You will get them in asus website.
if you are stuck without custom recovery i would suggest you to download system image (~1.5Gb) from asus website.
just search for asus zenfone 2 and go to official asus site. in downloads tab you should find both drivers and system image.
download the latest one.
See if you can get into stock recovery.
when in bootloader press vol down and go to recovery mode.
you will see a sleeping android bot with error.
press power key + vol down you will get a list.
choose factory reset and then after wipe is complete choose sideload from adb.
connect your phone and then in adb type
adb sideload filename.zip
obviously place file in your platform-tools folder and replace filename with whatever its name is.
it will take a while and you will get back your system.
---------- Post added at 07:37 PM ---------- Previous post was at 07:21 PM ----------
Marteicos said:
Just a reminder to everyone, never force shutdown the Phone during a cache wipe procedure, it takes a long time but it finishes.
When I did it on my ZF2, I thought it was taking too long, but I did a search here and found out about it taking long before it was too late.
I'm glad you could recover yours. :good:
Click to expand...
Click to collapse
Thanks!
It took a lot of time though.
For anyone stuck,
I first got fastboot working. and then i flashed stock recovery and boot.
got into stock recovery and sideloaded system img into it.
After it booted back into asus stock rom i unlocked bootloader, placed twrp in sdcard and got straight into fastboot again installed twrp and then did a wipe and went ahead and flashed ROM and Gapps. Working fine.
Update:
To get to bootloader:
i was stuck in a bootloop.
When at asus boot animation i connected USB cable and quickly typed
adb reboot bootloader
which seemed to work for me. Though i couldn't get into recovery.
So i had to flash stock recovery again.

Recovery gone / corrupted.

I am no longer able to boot into my recovery. TWRP nor stock / default. I am on a custom ROM. I am on 7.1.2 root with magisk 12. I have tried all the fastboot commands to live boot into recovery. I have tried TWRP official app. I have tried FlashFire. Everytime I try to boot into my recovery my phone just reboots back into the OS.

Wrong section

Hacker101 said:
I am no longer able to boot into my recovery. TWRP nor stock / default. I am on a custom ROM. I am on 7.1.2 root with magisk 12. I have tried all the fastboot commands to live boot into recovery. I have tried TWRP official app. I have tried FlashFire. Everytime I try to boot into my recovery my phone just reboots back into the OS.
Click to expand...
Click to collapse
So you have tried booting into the bootloader and entered "fastboot boot twrp.img" in adb?

This happens to me all the time. Using the advanced reboot menu on my ROM or "adb reboot recovery" while connected to my PC just results in the phone booting back into the OS. Pretty annoying. It has to have something to do with the Slots.
Anyways, to get around this, disconnect the phone from any power source, turn the phone completely off, wait 5-10 seconds, then press and hold Vol Down + Power to get to the bootloader. Then use the volume keys to select Recovery Mode and press power to boot into recovery. This method works every time for me. If this does not work for you or results in some other screen/error/whatever other than booting into TWRP, then you must live boot (as suggested in the above post) into TWRP and flash TWRP RC2.

Alcolawl said:
This happens to me all the time. Using the advanced reboot menu on my ROM or "adb reboot recovery" while connected to my PC just results in the phone booting back into the OS. Pretty annoying. It has to have something to do with the Slots.
Anyways, to get around this, disconnect the phone from any power source, turn the phone completely off, wait 5-10 seconds, then press and hold Vol Down + Power to get to the bootloader. Then use the volume keys to select Recovery Mode and press power to boot into recovery. This method works every time for me. If this does not work for you or results in some other screen/error/whatever other than booting into TWRP, then you must live boot (as suggested in the above post) into TWRP and flash TWRP RC2.
Click to expand...
Click to collapse
I have done this 100+ times. Booting into recovery using any method does not work. Including live booting.

Hacker101 said:
I have done this 100+ times. Booting into recovery using any method does not work. Including live booting.
Click to expand...
Click to collapse
If you are still able to access the bootloader, I would suggest flashing a factory image (removing -w if you want to keep your data) with the flash-all.bat. It sounds as if your recovery partition has been removed somehow making it unable to be booted into. Perhaps flashing the factory image will fix your partitions and solve the problem. It's worth a shot I guess if you can't access it at all. Good luck to you!

TheBobMiller said:
If you are still able to access the bootloader, I would suggest flashing a factory image (removing -w if you want to keep your data) with the flash-all.bat. It sounds as if your recovery partition has been removed somehow making it unable to be booted into. Perhaps flashing the factory image will fix your partitions and solve the problem. It's worth a shot I guess if you can't access it at all. Good luck to you!
Click to expand...
Click to collapse
How am I supposed to flash a factory image if I can't flash anything? Plus I am on a Linux computer not windows. Isn't .bat windows? Would I need a .sh type of command?

Hacker101 said:
How am I supposed to flash a factory image if I can't flash anything? Plus I am on a Linux computer not windows. Isn't .bat windows? Would I need a .sh type of command?
Click to expand...
Click to collapse
The factory image flashes in bootloader mode and should correct any issue you have. You have to install the Android SDK platform on your Linux machine. Go to this link https://developer.android.com/studio/index.html#tos-header and scroll down to almost the bottom for just the command line tools and follow the instructions to install. Then go to https://developers.google.com/android/images and download the factory image you want to flash and follow the instructions in that link to flash. I don't have a Linux machine myself, but I believe the process is fairly similar and it should work just fine.

TheBobMiller said:
The factory image flashes in bootloader mode and should correct any issue you have. You have to install the Android SDK platform on your Linux machine. Go to this link https://developer.android.com/studio/index.html#tos-header and scroll down to almost the bottom for just the command line tools and follow the instructions to install. Then go to https://developers.google.com/android/images and download the factory image you want to flash and follow the instructions in that link to flash. I don't have a Linux machine myself, but I believe the process is fairly similar and it should work just fine.
Click to expand...
Click to collapse
Sweet I'll give it a try when I get home later. We got a nasty storm blowing in so I may not get to it today. Also I'll remember to Thank that post tomorrow lol limited to eight a day. When you have 100+ people helping you out at once it's hard to thank each one.

Hacker101 said:
Sweet I'll give it a try when I get home later. We got a nasty storm blowing in so I may not get to it today. Also I'll remember to Thank that post tomorrow lol limited to eight a day. When you have 100+ people helping you out at once it's hard to thank each one.
Click to expand...
Click to collapse
Don't worry about the Thanks, cause I'm sure others have contributed more. Sorry I'm not more familiar with the Linux instructions!

Ok having the same issue as OP. A and B slots do not allow me to boot into recovery mode. It just immediately restarts as soon as the white Google splash screen appears. I have just done a factory reset with N2G47O. After complete, the stock default recovery works fine. I booted TWRP from fast boot to install the latest, issue came again. Trying to get into recovery mode just causes it to bootloop until you hold the volume down button to get bootloader up to boot to system instead. I am downloading and will flash NOF27D (last 7.1.1) to see if I can reinstall twrp from that. I can confirm that installing twrp when on that image worked. Will report back...

Hacker101 said:
Sweet I'll give it a try when I get home later. We got a nasty storm blowing in so I may not get to it today. Also I'll remember to Thank that post tomorrow lol limited to eight a day. When you have 100+ people helping you out at once it's hard to thank each one.
Click to expand...
Click to collapse
jkashuba07 said:
Ok having the same issue as OP. A and B slots do not allow me to boot into recovery mode. It just immediately restarts as soon as the white Google splash screen appears. I have just done a factory reset with N2G47O. After complete, the stock default recovery works fine. I booted TWRP from fast boot to install the latest, issue came again. Trying to get into recovery mode just causes it to bootloop until you hold the volume down button to get bootloader up to boot to system instead. I am downloading and will flash NOF27D (last 7.1.1) to see if I can reinstall twrp from that. I can confirm that installing twrp when on that image worked. Will report back...
Click to expand...
Click to collapse
I forgot to ask if you were on the latest May security update. If you were on that version then you need to use the Android Verified Signer.zip from chainfire after you flash twrp. What version are you running?

jkashuba07 said:
Ok having the same issue as OP. A and B slots do not allow me to boot into recovery mode. It just immediately restarts as soon as the white Google splash screen appears. I have just done a factory reset with N2G47O. After complete, the stock default recovery works fine. I booted TWRP from fast boot to install the latest, issue came again. Trying to get into recovery mode just causes it to bootloop until you hold the volume down button to get bootloader up to boot to system instead. I am downloading and will flash NOF27D (last 7.1.1) to see if I can reinstall twrp from that. I can confirm that installing twrp when on that image worked. Will report back...
Click to expand...
Click to collapse
Ok, I can confirm after doing factory reset to NOF27D I was able to reinstall TWRP and boot to it successfully
---------- Post added at 04:57 PM ---------- Previous post was at 04:56 PM ----------
TheBobMiller said:
I forgot to ask if you were on the latest May security update. If you were on that version then you need to use the Android Verified Signer.zip from chainfire after you flash twrp. What version are you running?
Click to expand...
Click to collapse
Yes I was on May.. Do you have link to Verified Signer?

jkashuba07 said:
Ok, I can confirm after doing factory reset to NOF27D I was able to reinstall TWRP and boot to it successfully
---------- Post added at 04:57 PM ---------- Previous post was at 04:56 PM ----------
Yes I was on May.. Do you have link to Verified Signer?
Click to expand...
Click to collapse
Here is the link to the verifiedbootsigner.zip from Chainfire: https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
Make sure you give him some Thanks and Donate if possible! He has earned plenty of both from all of us Android users!
Instructions: Anytime you flash anything that affects the boot partition (ie. twrp, rom, kernel, etc), make sure to flash the boot signer zip at the end of the flashing before a reboot.

TheBobMiller said:
Here is the link to the verifiedbootsigner.zip from Chainfire: https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
Make sure you give him some Thanks and Donate if possible! He has earned plenty of both from all of us Android users!
Instructions: Anytime you flash anything that affects the boot partition (ie. twrp, rom, kernel, etc), make sure to flash the boot signer zip at the end of the flashing before a reboot.
Click to expand...
Click to collapse
Thank you, and will do.. yes chainfire has done a lot of good work, definitely have appreciated him over the years

TheBobMiller said:
Here is the link to the verifiedbootsigner.zip from Chainfire: https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
Make sure you give him some Thanks and Donate if possible! He has earned plenty of both from all of us Android users!
Instructions: Anytime you flash anything that affects the boot partition (ie. twrp, rom, kernel, etc), make sure to flash the boot signer zip at the end of the flashing before a reboot.
Click to expand...
Click to collapse
That's only for May and so on correct? I am on April. Heard nasty things form root uses about root screwing up, bootloader problems, etc. So I stayed away from May and stayed on April.

Hacker101 said:
That's only for May and so on correct? I am on April. Heard nasty things form root uses about root screwing up, bootloader problems, etc. So I stayed away from May and stayed on April.
Click to expand...
Click to collapse
Correct. Only the may bootloader requires the extra zip file to be flashed. I am still on April but I have heard people not having any problems and some having nothing but problems from May. I think I'm going to give it a try tomorrow and see how it goes.
Edit: Tried the May bootloader and couldn't get it to boot a custom rom or TWRP, so I went back to April after flashing the Android O Beta and playing with it for a couple of hours. I feel that the Beta is still too early for a daily driver, but it was nice to mess around with some of the features we will have once this OS is released.

Pixel 2 xl stuck on white screen with G on it and status bar underneath

Phone is stuck on this white screen with the G on it and the status bar scrolling over and over. Phone is unlocked and rooted and i was having trouble installing a recovery onto it. I just spent 3 hours setting everything up. Do i have to wipe and start again?

equlizer said:
Phone is stuck on this white screen with the G on it and the status bar scrolling over and over. Phone is unlocked and rooted and i was having trouble installing a recovery onto it. I just spent 3 hours setting everything up. Do i have to wipe and start again?
Click to expand...
Click to collapse
What did you flash to cause this?? Did you try a hard restart by holding the power button down until it starts rebooting?

Tried a hard restart and same thing happens. I was trying to install TWRP using skipsoft toolkit #6 option.

equlizer said:
Tried a hard restart and same thing happens. I was trying to install TWRP using skipsoft toolkit #6 option.
Click to expand...
Click to collapse
Since I'm not familiar with toolkits, or their interface, I'll let someone else take over. Have you considered using adb and fastboot commands to accomplish your task?

I would if i knew what i was doing I just tried the wipe everything option and now it says "cant load android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory reset and erase all user data stored on this device"
Well i did that and i get that same message over and over again. How do i start fresh? I have the image on my computer

equlizer said:
I would if i knew what i was doing I just tried the wipe everything option and now it says "cant load android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory reset and erase all user data stored on this device"
Well i did that and i get that same message over and over again. How do i start fresh? I have the image on my computer
Click to expand...
Click to collapse
If you want to continue using the toolkit, I would post your problems in that thread. The folks that made it will be more qualified to help you than I could.

i went into bootloader mode and did the flash all. The phone reboots and comes back with the same message "cant load android"
I dont care what i use to get things working again. pls help.

equlizer said:
i went into bootloader mode and did the flash all. The phone reboots and comes back with the same message "cant load android"
I dont care what i use to get things working again. pls help.
Click to expand...
Click to collapse
I will try my best.
1. You have definitely unlocked_critical correct. If you haven't, you need to.
2. Have you downloaded SDK on your pc? You need this as well. You can find a link to it on Google's factory image page.
3. You have downloaded the latest factory image and unzipped it with the 7zip program.
4. Inside the SDK program, look for a file called platform tools.
5. You need to take the contents you extracted from the factory image, and place them in the platform tools folder. That includes: Radio, bootloader, the flash-all.bat file, and another large zip file that contains the boot, system, vendor and about 16 other things.
6. Put your phone into bootloader mode and plug it into the pc. Open a command prompt from the platform tools folder and type "fastboot devices" if your phone ID comes up, your good.
7. Double click the flash-all.bat file, and that should start the installation process. It will take a little while to install the OS, so be patient. If all goes well, your phone should automatically boot up.
8. I will try and find a link for all this installation stuff.
9. Good luck!
---------- Post added at 01:23 PM ---------- Previous post was at 01:16 PM ----------
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
Here is a link to instructions written by one of the best kernel developers out there. Read it carefully if what I gave you doesn't make sense.

Tried it this morning and when i go to root with magisk (followed every step) i get the white screen with the G and the bar scrolling

equlizer said:
Tried it this morning and when i go to root with magisk (followed every step) i get the white screen with the G and the bar scrolling
Click to expand...
Click to collapse
Did you ever get your phone to boot up on stock system?

Badger50 said:
Did you ever get your phone to boot up on stock system?
Click to expand...
Click to collapse
Not sure how i did it but it seems to have reverted back to complete stock. Everything setup after but when it rebooted it said "this device cannot be trusted, hit the power button to continue" so i do and it seems to boot back into the phone. How do i get rid of that message?
Ive never had so many issues with a phone before.

How do i get rid of that message?
once you had the Bootloader unlocked in this phone it will display that message in every boot, there is no way to get rid of it at this moment.

equlizer said:
Not sure how i did it but it seems to have reverted back to complete stock. Everything setup after but when it rebooted it said "this device cannot be trusted, hit the power button to continue" so i do and it seems to boot back into the phone. How do i get rid of that message?
Ive never had so many issues with a phone before.
Click to expand...
Click to collapse
A lot of trouble people have with these phones has to do with the A/B partitions, glitches in cables, sdk, PC's, ghosts in the machine, and users not taking the time to read and learn what to do. Anyway, glad you got it going. Your welcome.

Everything else worked except for the rooting with magisk. when it patches the image using manager 5.4.3 it says its downloading version 14.0 not 14.5. I go to flash the patched boot img then it just reboots to the white screen with the G and it hangs there till i shut it off.

equlizer said:
Everything else worked except for the rooting with magisk. when it patches the image using manager 5.4.3 it says its downloading version 14.0 not 14.5. I go to flash the patched boot img then it just reboots to the white screen with the G and it hangs there till i shut it off.
Click to expand...
Click to collapse
Manually download 14.5 and flash it in twrp. Or, take the stock boot.img, place it on your phones internal storage, open magisk, hit install, and select patch boot (I think) Then take the patched_boot.img and flash that with fastboot. Either way should give you root.

I already said I patched it using the magisk I installed but when I flash it I get the G on the white screen. I can't even get twrp to stick. This was all using 8.1 but now I'm on 8.0. I guess I'll try again?

equlizer said:
I already said I patched it using the magisk I installed but when I flash it I get the G on the white screen. I can't even get twrp to stick. This was all using 8.1 but now I'm on 8.0. I guess I'll try again?
Click to expand...
Click to collapse
What twrp version are you using? So, you can fastboot the twrp-3.1.1-beta2-taimen-img but then are unable to flash the twrp.zip once you enter temporary twrp?

I just downloaded twrp 3.1.1 beta 2 taimen.img and the zip
how do i fastboot the img?
then from there do i flash magisk 14.5.zip then reboot and install magisk manager 5.4.3 then check for root?

equlizer said:
I just downloaded twrp 3.1.1 beta 2 taimen.img and the zip
how do i fastboot the img?
then from there do i flash magisk 14.5.zip then reboot and install magisk manager 5.4.3 then check for root?
Click to expand...
Click to collapse
Go to fastboot and type: fastboot boot twrp-3.1.1-beta2-taimen.img
That should immediately take you temporary twrp where you then flash the twrp.zip, and then flash your magisk zip. That should also install the magisk app as well.

it takes me to the screen where it says "this devices cannot be trusted" so i hit the power button then it just reboots into android 8.0. I appreciate all the help