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
Related
Here's a video tutorial on how to root your Nexus 10 for noobs!
Windows video tutorial:
Mac video tutorial:
Linux video tutorial:
All the files you need in one zip (adb+SuperSU+fastboot+Windows drivers):
http://downloadandroidrom.com/file/Nexus10/Nexus10RootNew.zip
Step-by-Step tutorial with photos here:
http://nexus10root.com/nexus-10-root/how-to-root-nexus-10-easiest-method/
Also, if you get stuck on bootloop after unlocking bootloader (This happened to me couple times), do a factory reset in stock recovery to fix:
Thanks to shimp208 for the sideload method and working CWM, ChainFire for awesome SuperSU and to all the developers who are worked on CWM recovery!
So the CWM that was just updated by Koushik on CWM does not work properly or does it work? Was asking based on this
While CWM Recovery is still being fixed
Click to expand...
Click to collapse
Edit: There's no driver issue if it were on a Mac right? Especially adb sideloading the CWM SuperSu zip?
How do I flash the stock recovery? CWM isn't working and I tried to update the driver like in the video but couldn't find the "manta" that I needed to update. I'm just stuck in bootloop animation now. I'm downloading the stock image right now to try and flash it back to stock..
johno86 said:
How do I flash the stock recovery? CWM isn't working and I tried to update the driver like in the video but couldn't find the "manta" that I needed to update. I'm just stuck in bootloop animation now. I'm downloading the stock image right now to try and flash it back to stock..
Click to expand...
Click to collapse
If you go into fastboot mode then choose recovery to get to the screen with the red triangle, keep pressing the power button and volume buttons randomly until the stock recovery pops up. From there do a factory reset and it'll work, I just did it to mine!
I flashed the CWM recovery img so when I do what you say it takes me to the bootloader screen and says Downloading. No red triangle. It boots into CWM and then after 20 seconds restarts itself and hits the bootanimation loop. Any clue what to do next? Trying to flash the stock image but having issues using cmds in windows cmd
*edit
I cleared cache through cmd and i got to the red triangle...thank ****ing the lord. DTWAZERE, I will remember tonight. Thank you for your help.
johno86 said:
I flashed the CWM recovery img so when I do what you say it takes me to the bootloader screen and says Downloading. Any clue what to do next? Trying to flash the stock image but having issues getting it into fastboot now...
Click to expand...
Click to collapse
Thing is it will delete the CWM recovery when you leave it so you'll have to reflash it, which is why this is so unstable!
I had the exact same thing as you and this is what I did:
Press the power button to turn it off while it says downloading
Hold both volume buttons down and power on to get into fastboot
Choose recovery
Press power and volume buttons randomly when the red triangle appears until you get stock recovery
Choose Factory Reset
Reboot
You should be able to get back into the rom that way,
to root it you need to boot into fastboot again, reflash the recovery, and sideload the superuser apk
dtwazere said:
Thing is it will delete the CWM recovery when you leave it so you'll have to reflash it, which is why this is so unstable!
I had the exact same thing as you and this is what I did:
Press the power button to turn it off while it says downloading
Hold both volume buttons down and power on to get into fastboot
Choose recovery
Press power and volume buttons randomly when the red triangle appears until you get stock recovery
Choose Factory Reset
Reboot
You should be able to get back into the rom that way,
to root it you need to boot into fastboot again, reflash the recovery, and sideload the superuser apk
Click to expand...
Click to collapse
Yeah this is exactly what I did and it worked. I'll wait on flashing anything until there's a stable recovery. I was fairly confident in what I was doing until that happened. Not being able to input commands from cmd prompt made me sick so I'll wait for a dev to release something that works without having to quickly install the drivers again within a 15-20 second timeframe. Too much stress.
cant boot
I got a huge problem.
I follow the step and going on. Ive seen the done in CWMR. But the tablet cant boot.
It stops in the second animation( X mark) cant boot in os.
Anyone can help me?
lc684760 said:
I got a huge problem.
I follow the step and going on. Ive seen the done in CWMR. But the tablet cant boot.
It stops in the second animation( X mark) cant boot in os.
Anyone can help me?
Click to expand...
Click to collapse
Heh im having the same issue.
lc684760 said:
I got a huge problem.
I follow the step and going on. Ive seen the done in CWMR. But the tablet cant boot.
It stops in the second animation( X mark) cant boot in os.
Anyone can help me?
Click to expand...
Click to collapse
I'm having the same issue. Stuck on the 2nd splash screen with the Nexus Logo.
I received successful messages after every entry.
deevooneh said:
I'm having the same issue. Stuck on the 2nd splash screen with the Nexus Logo.
I received successful messages after every entry.
Click to expand...
Click to collapse
sucks. But we can boot in fastboot and downloading . I think we may have some tricks to fix.
i did everything, and it all went successfully after a few tried. Now i am stuck with the JB X load screen.
How do i get the stock google rom and how do i flash it?
lc684760 said:
sucks. But we can boot in fastboot and downloading . I think we may have some tricks to fix.
Click to expand...
Click to collapse
Ok. Let me know if you figure something out. Hopefully we didnt brick it.
deevooneh said:
Ok. Let me know if you figure something out. Hopefully we didnt brick it.
Click to expand...
Click to collapse
I just called service phone. But goole play agent told me that they didnt know how to deal with that. Its the new device. They dont know much. Damn it!
lc684760 said:
I just called service phone. But goole play agent told me that they didnt know how to deal with that. Its the new device. They dont know much. Damn it!
Click to expand...
Click to collapse
How do we get back to stock? Might need to reattempt this.
If you are stuck on the boot animation (X) screen... power off your device and enter fastboot mode and then type fastboot -w... I has this problem and this fixed it!
NOTE: fastboot -w will wipe your internal storage completely
dtwazere said:
If you go into fastboot mode then choose recovery to get to the screen with the red triangle, keep pressing the power button and volume buttons randomly until the stock recovery pops up. From there do a factory reset and it'll work, I just did it to mine!
Click to expand...
Click to collapse
deevooneh said:
How do we get back to stock? Might need to reattempt this.
Click to expand...
Click to collapse
Stock is here
https://developers.google.com/android/nexus/images#mantarayjop40c
Still need a way to get CWM stable, so we have time to copy to sd
craigacgomez said:
If you are stuck on the boot animation (X) screen... power off you devices and enter fastboot mode and then type fastboot -w... I has this problem and this fixed it!
NOTE: fastboot -w will wipe your internal storage completely
Click to expand...
Click to collapse
THIS WORKED!!
Youre a genius. thanks!
When I try to install the manta drivers manually and tell it to search the same area that it searched and found the android bootloader drivers for fastboot mode it says that the drivers couldn't be found and installed. Am I missing something? Also if i try to do fastboot flash recovery it gives me an error message stating that it cannot determine the image filename for the recovery image.
Well i guess i did it the long way around.
Went to https://developers.google.com/android/nexus/images#mantarayjop40c
and downloaded the Nexus 10 file. extracted, and the actual files in the Nexus10Root folder.
Opened the flash-all.sh and entered each command manually because it was erroring out running the script.
After the 3rd command it booted right into android!
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.
I have flashed many phones before my G4 and this is the first time I'm having to ask for help.
The firmware installed was AICP CM13, then the screen went green with a DemiGod message. I held the vol down button to reboot and it came back up. After a few restarts and green screens i figured I needed to reflash the firmware. I booted into Recovery and while wiping the device to flash a new firmware, TWRP crashed. After leaving it for half hour or so, I took the battery out to enter into TWRP so I can flash the new firmware. TWRP is no there to be seen. I hold down the vol down and power button, releasing power for second or two and choose to go into recovery. Every time the phone just gets stuck on the LG screen displaying "Bootloader state :Bootlader unlocked!".
In short, I have no firmware, the device has been wiped and TWRP doesn't seem to be working.
I have tried to flash a KDZ file (H81520A_00.kdz) using the flash guide here. This comes back as unsuccessful saying "connection to server failed". As shown below.
View attachment 3605673
The method to flash an .img file using cmd on the pc includes moving the 4gb .img file to the parent folder of the phone storage. I can't get to move any files whatsoever to my device so figured this method would not work.
Seems if I can somehow flash TWRP, then I should be able to install a new firmware.
Any help much appreciated.
Hi, Can you get an ADB connection to your phone, or get your phone into bootloader somehow. From there you could try 'fastboot boot recovery.img'?
If so, then from within TWRP you can flash twrp recovery so the recovery is then sorted. Then you could flash click here (the full version). This will then allow LG UP to find a connection. From there if you really wanted to can flash any KDZ as a proper reset. Hope it works buddy!!
rav101 said:
Hi, Can you get an ADB connection to your phone, or get your phone into bootloader somehow. From there you could try 'fastboot boot recovery.img'?
If so, then from within TWRP you can flash twrp recovery so the recovery is then sorted. Then you could flash click here (the full version). This will then allow LG UP to find a connection. From there if you really wanted to can flash any KDZ as a proper reset. Hope it works buddy!!
Click to expand...
Click to collapse
I can get into recovery but I am unsure as to how I could try 'fastboot boot recovery.img'. Would that be the same as flashing an img when the root method first came out?
AndHD2 said:
I can get into recovery but I am unsure as to how I could try 'fastboot boot recovery.img'. Would that be the same as flashing an img when the root method first came out?
Click to expand...
Click to collapse
Just to make sure you know. TWRP is your recovery. Your last message said you did not have TWRP?
When I first rooted my phone (and subsequently when I install a .kdz), I have to go into the bootloader and install TWRP. I personally do this by using the above command "fastboot boot recovery.img" with the recovery.img being placed on my computer in the same location as my adb installation. This command only boots up TWRP but does not flash it. I then flash twrp by having a copy of it on my external sd card. Within twrp you can select to flash zip, or there is an option to flash an image. I use this to flash twrp (from twrp... its a little inception like but it works). Once you have twrp up and running, you can install a rom. If you want to do flash a .kdz, I have found you need to be on a stock based rom in the first place hence why i referenced the v20a full system zip.
Hope that made sense.
Regards,
Ravi
It is late here and with me being tired I said recovery instead of download. I can boot into download mode but when I try to boot into recovery then it just goes straight to the LG splash screen and it will either remain in that screen or the green Demigod screen would come up.
I'm off to sleep and away from my laptop as I have to be up in 5 hours. Luckily I still have my Note 4 so at least I'm not without a phone in the morning. I will try the steps what you have suggested just as soon as I get back from work.
Many thanks
rav101 said:
Just to make sure you know. TWRP is your recovery. Your last message said you did not have TWRP?
When I first rooted my phone (and subsequently when I install a .kdz), I have to go into the bootloader and install TWRP. I personally do this by using the above command "fastboot boot recovery.img" with the recovery.img being placed on my computer in the same location as my adb installation. This command only boots up TWRP but does not flash it. I then flash twrp by having a copy of it on my external sd card. Within twrp you can select to flash zip, or there is an option to flash an image. I use this to flash twrp (from twrp... its a little inception like but it works). Once you have twrp up and running, you can install a rom. If you want to do flash a .kdz, I have found you need to be on a stock based rom in the first place hence why i referenced the v20a full system zip.
Hope that made sense.
Regards,
Ravi
Click to expand...
Click to collapse
I have finally got chance to sit down and have a go at performing the procedure listed above. I downloaded the adb and fastboot installation as outline here. It is the minimum to what this thread says I will need for my device. I moved the recovery.img to the installation location which were in Windows/programs files (x86)/Minimal adb and fastboot. I launched the program and typed in 'fastboot boot recovery.img'. I tried this in download mode, charging mode (phone off) and while on the LG flash screen where TWRP didnt load but in all cases I have had no response at all.
If someone can help the much appreciated.
AndHD2 said:
I have finally got chance to sit down and have a go at performing the procedure listed above. I downloaded the adb and fastboot installation as outline here. It is the minimum to what this thread says I will need for my device. I moved the recovery.img to the installation location which were in Windows/programs files (x86)/Minimal adb and fastboot. I launched the program and typed in 'fastboot boot recovery.img'. I tried this in download mode, charging mode (phone off) and while on the LG flash screen where TWRP didnt load but in all cases I have had no response at all.
If someone can help the much appreciated.
Click to expand...
Click to collapse
Hi @AndHD2, I'm sorry but I can't think of anything else
rav101 said:
Hi @AndHD2, I'm sorry but I can't think of anything else
Click to expand...
Click to collapse
I had another demigod type screen but this was grey and not green with less detail. However it did say it were a kernel error.
Is the handset still under warrenty with the bootloader unlocked. I have a feeling its not
Here are the steps that got me to where I am.
1. Stock Pixel XL March 2017
2. Installed TWRP
3. Installed SU
4. All worked correctly for the last month
5. Saw that there was a new April release
a. It would not install as I was rooted
b. I installed the April OTA using TWRP
c. Rebooted
6. Saw that I was no longer rooted
7. Tried to go to Bootloader
8. Got dead droid with no command error
9. Went to recovery (Power + up vol) to enter sideload
10. Sideloaded the April updated
11. Rebooted
a. Same no command error
b. Went to recovery (Power + up vol) to enter factory restore
c. Rebooted
12. Tried to go into boot loader
a. Same no command error
13. Problem is that twrp was not asking for pattern And would not install correctly with image file. Solution was to keep loading the twrp image file until it asks for pattern. Then follow standard twrp /su instructions.
Thanks.
Power device off, use key combo (power+voldown) to boot bootloader. Fastboot flash stock boot.img to both slot a and b. Then reboot, take the OTA, or sideload it. Reboot. Now reboot to bootloader, fastboot boot TWRP, then reboot to twrp. Now you can flash TWRP to keep it as the recovery, or just su then reboot. Should be good.
Sent from my Pixel XL using Tapatalk
This should be posted under Q&A not development
wyrdtrtle said:
Power device off, use key combo (power+voldown) to boot bootloader. Fastboot flash stock boot.img to both slot a and b. Then reboot, take the OTA, or sideload it. Reboot. Now reboot to bootloader, fastboot boot TWRP, then reboot to twrp. Now you can flash TWRP to keep it as the recovery, or just su then reboot. Should be good.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Bootloader does not load.
When you get the dead Droid just hit vol up, no power button.
Sent from my Pixel XL using Tapatalk
Then what?
bschatzow said:
Then what?
Click to expand...
Click to collapse
I think I know where you went wrong you installed an incremental OTA with TW RP. If I'm not mistaken that new firmware had an updated bootloader and I believe that's dangerous to do. You may be out of luck
Why would the built in factory restore fix it?
bschatzow said:
Why would the built in factory restore fix it?
Click to expand...
Click to collapse
Can you get into fastboot?
So no bootloader.
Just my thoughts. I don't know if that's even possible.
Isn't it possible to edit the ota script to flash a bootloader?
Or even make a full factory update like this?
To use fastboot you need to be in bootloader mode.
mikaole said:
So no bootloader.
Just my thoughts. I don't know if that's even possible.
Isn't it possible to edit the ota script to flash a bootloader?
Or even make a full factory update like this?
Click to expand...
Click to collapse
If it is, I don't know how. I would need it to be able to load from Sideload.
Does phone boot at all? To OS?
Yes it does. Only thing not working is bootloader. Without out this I can't root.
bschatzow said:
Yes it does. Only thing not working is bootloader. Without out this I can't root.
Click to expand...
Click to collapse
Ok..if phone boots ur bootloader is still there. Phone wouldnt boot without it. You on stock rom? Hit me up on hangouts and I will try to help you if you want. For the sake of time. Im sure you wanna get this resolved ASAP.
Sent you a pm requesting contact info.
Moderator Close
Worked for a long time with BDogg718. He generously spent a great deal of his time with me and opened several Chats with Developers and No one had a solution. He is very knowledgeable and really did not want to give up. For now the solutions seems to be send it back to Google and get a replacement. It would be nice if someone could talk to Google, as a phone that has a recovery built in firmware should be able to restore itself. The dual slots seems to be a problem for them as well.
I think I had the same thing happen with me! I installed the update via TWRP. The update installation seemed to crash at the end, resulting in a reboot. The phone did install 7.1.2 successfully, but I lost root and the ability to successfully boot into any recovery. I tried flashing TWRP again, but it failed "FAILED (remote: partition recovery doesn't exist). It appeared to attempt to flash it into slot "_b", if that means anything.
TWRP will not boot on 7.1.2. At least that's the conclusion formed last night in #twrp while the devs were working with someone else with this issue. I don't think they know why yet, but I doubt it will be overly long til they figure it out.
Sent from my Pixel XL using Tapatalk
Glad to hear someone is on the case. I will be sure to send a few shekels their way for my clumsiness.
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.