Related
Hi all, after some modding it seems that my nexus 7 2013 lte custom recovery is vanished. I've tried to flash it via adb, I've flashed the new 5.1 official image, but nothing happen. Every time I try to boot into recovery mode, via adb or power+volume up, all I get is a dead android robot logo with no options.
And, btw, my N7 works perfectly
What can I do?
Thanks
When you flash a new android version you lose root and custom recovery, you need to root and flash custom recovery again as your currently on stock, when that robot is on his back you also have hold down a button combo to access the fastboot / bootloader or recovery, unless you send it the command via adb.
My advice is re-root using cfautoroot and flash custom recovery with flashify.
Ok, thanks! I've flashed twrp (I'm still no-root) and it works fine. Now is there any possibility to come back on stock recovery?
Flashify premium allows you to download and flash stock recovery or bootloader,
if you can't afford it or there not available for dl yet you can alternatively extract the .img files
from the factory image and flash them instead.
Q8-V08 said:
Flashify premium allows you to download and flash stock recovery or bootloader,
if you can't afford it or there not available for dl yet you can alternatively extract the .img files
from the factory image and flash them instead.
Click to expand...
Click to collapse
Nothing to do. I've extracted the img file from the factory image and flashed it via fastboot but, when I restart the device in recovery mode, it still shows the green half dead androidbot
^Thats normal. When you get to that screen you have to press volume up, down and power all at the same time, all three buttons. Just keep pressing them all at once a few times and it'll let you into stock recovery. It took me about 10 minutes to get in the first time. Don't hold the buttons, a quick press.
yosmokinman said:
^Thats normal. When you get to that screen you have to press volume up, down and power all at the same time, all three buttons. Just keep pressing them all at once a few times and it'll let you into stock recovery. It took me about 10 minutes to get in the first time. Don't hold the buttons, a quick press.
Click to expand...
Click to collapse
So you're saying that normally, on a Nexus 7 with no root and with stock recovery, the combination key to enter in the recovery isn't power+volume up ? Sorry for repeating, but I'm new at modding
I'm saying when you boot into recovery and it gives you the dead android (on it's back I think?) do what I said above.
yosmokinman said:
I'm saying when you boot into recovery and it gives you the dead android (on it's back I think?) do what I said above.
Click to expand...
Click to collapse
Done Thank you all!
Yeah it's pita to press, it's why I prefer to launch recovery from flashify or quick boot it's so much easier.
Android seems to love doing things arsed about faced / over complicated it should just be an option in settings, power off like
custom roms along with wireless adb.
So I just unboxed my new Pixel XL. First thing I did was to fastboot oem unlock with no issues. I downloaded systemless root from chainfire and ran fastboot boot boot-to-root.img and have been stuck at the boot animation screen for over 15 minutes. Any ideas what I did wrong and how to get it working?
Thanks for any input
Shawn haz root said:
So I just unboxed my new Pixel XL. First thing I did was to fastboot oem unlock with no issues. I downloaded systemless root from chainfire and ran fastboot boot boot-to-root.img and have been stuck at the boot animation screen for over 15 minutes. Any ideas what I did wrong and how to get it working?
Thanks for any input
Click to expand...
Click to collapse
You're using boot-to-root which was outdated many weeks ago.
Here are some avenues you can take to achieve root: (hint: go with the last option)
If TWRP RC1 + SU 2.78 SR4, must delete fstab before flashing SU.
If insist on SU 2.78, then use TWRP Alpha2, not RC1.
If TWRP RC1 + 2.79 SR2, no need to delete fstab.
quangtran1 said:
You're using boot-to-root which was outdated many weeks ago.
Here are some avenues you can take to achieve root: (hint: go with the last option)
If TWRP RC1 + SU 2.78 SR4, must delete fstab before flashing SU.
If insist on SU 2.78, then use TWRP Alpha2, not RC1.
If TWRP RC1 + 2.79 SR2, no need to delete fstab.
Click to expand...
Click to collapse
Ouch, wish I caught that before I pushed it. I downloaded TWRP RC1. I can't get into fastboot now though, the commands in cmd don't work as it doesn't see the phone and holding the power button and volume down isn't working. Do I need to reinstall the stock binaries and start over? I don't care about any data loss.
Shawn haz root said:
Ouch, wish I caught that before I pushed it. I downloaded TWRP RC1. I can't get into fastboot now though, the commands in cmd don't work as it doesn't see the phone and holding the power button and volume down isn't working. Do I need to reinstall the stock binaries and start over? I don't care about any data loss.
Click to expand...
Click to collapse
You don't need to go to stock yet. How long did you hold vol - and power? Keep holding until bootloader comes up.
quangtran1 said:
You don't need to go to stock yet. How long did you hold vol - and power? Keep holding until bootloader comes up.
Click to expand...
Click to collapse
So when the phone is stuck in the boot animation, I hold down Vol down plus power and the phone shuts off but then immediately goes to "Your device software cannot be checked...etc" Press power to pause. I can pause it but still can't run any commands and if I press power to continue, it then takes me back to boot which obviously hangs there.
EDIT: I just wasn't patient enough. I was successful in getting to the boot loader, thank you.
Shawn haz root said:
So when the phone is stuck in the boot animation, I hold down Vol down plus power and the phone shuts off but then immediately goes to "Your device software cannot be checked...etc" Press power to pause. I can pause it but still can't run any commands and if I press power to continue, it then takes me back to boot which obviously hangs there.
EDIT: I just wasn't patient enough. I was successful in getting to the boot loader, thank you.
Click to expand...
Click to collapse
Now you would go back into twrp rc1, install su 2.79 sr2 in the slot you want and live happily ever after.
quangtran1 said:
Now you would go back into twrp rc1, install su 2.79 sr2 in the slot you want and live happily ever after.
Click to expand...
Click to collapse
great, I just booted into twrp, flashed the .zip and am now waiting for it to boot into the OS. Do you think it's ok that this was done after the boot-to-root.img caused me to be stuck at the boot animation?
Shawn haz root said:
great, I just booted into twrp, flashed the .zip and am now waiting for it to boot into the OS. Do you think it's ok that this was done after the boot-to-root.img caused me to be stuck at the boot animation?
Click to expand...
Click to collapse
Yes, you should be ok.
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.
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
I got a brand new A2 Lite, unlocked the bootloader and flashed TWRP recovery to install Magisk.
It all seemed well, but then it automatically downloaded a system update overnight, and upon restarting it just shows the loading (white screen with a line) animation. I left it like that for an hour to no avail.
So in summary, I now have three options: getting to the white loading screen (power button), the fastboot screen (power + vol down), or the "no command" robot and menu (power + vol up).
I spent quite a lot of time to set up applications and authenticator programs, so I would prefer not to hard reset, but if that's that's the only way I'll do it.
Any suggestions?
If I were you I would try and fastboot boot patched_boot.img for the latest 10.0.4
Can be found in this thread
https://forum.xda-developers.com/mi...v10-30-0-january-update-t3891331/post78959192
Or direct link to his patched_boot
https://1drv.ms/u/s!AqlJY73bUA7rhpcsCiBBksxTPauDvg
If you do get it to boot, you will need to open magisk and install> direct install
Then make sure to go into Dev options and turn off automatic updates.
Aside from that you may need to flash factory firmware with miflash... Wiping your data
hossman said:
If I were you I would try and fastboot boot patched_boot.img for the latest 10.0.4
Can be found in this thread
https://forum.xda-developers.com/mi...v10-30-0-january-update-t3891331/post78959192
Or direct link to his patched_boot
https://1drv.ms/u/s!AqlJY73bUA7rhpcsCiBBksxTPauDvg
If you do get it to boot, you will need to open magisk and install> direct install
Then make sure to go into Dev options and turn off automatic updates.
Aside from that you may need to flash factory firmware with miflash... Wiping your data
Click to expand...
Click to collapse
Thank you. The patched boot image didn't work so I flashed a factory rom. It works now.
neptun123 said:
Thank you. The patched boot image didn't work so I flashed a factory rom. It works now.
Click to expand...
Click to collapse
Be sure to turn off auto update if you root again.
hossman said:
Be sure to turn off auto update if you root again.
Click to expand...
Click to collapse
Already did.