Flashed the wrong recovery - Nexus 10 Q&A, Help & Troubleshooting

I followed this guide to root my Nexus 10, did the oem unlock, downloaded the linked version of TWRP and flashed it via fastboot, now it won't boot and I can't get into recovery mode, because the version of TWRP was apparently meant for the Nexus 7 aka Flo.
It starts booting normally, but the boot animation just seems to go on forever, I waited around 30 minutes for it to finish but it didn't.
I can get into fastboot mode, but can't change the boot option and I haven't been able to flash anything (doesn't show up with fastboot devices), Windows recognizes the device as "Gadget Serial".
Is there anything I can do?

codfreak said:
I followed this guide to root my Nexus 10, did the oem unlock, downloaded the linked version of TWRP and flashed it via fastboot, now it won't boot and I can't get into recovery mode, because the version of TWRP was apparently meant for the Nexus 7 aka Flo.
It starts booting normally, but the boot animation just seems to go on forever, I waited around 30 minutes for it to finish but it didn't.
I can get into fastboot mode, but can't change the boot option and I haven't been able to flash anything (doesn't show up with fastboot devices), Windows recognizes the device as "Gadget Serial".
Is there anything I can do?
Click to expand...
Click to collapse
Install the ADB drivers on your PC, and then use the command prompt to boot into recovery : adb reboot recovery
http://lifehacker.com/the-most-useful-things-you-can-do-with-adb-and-fastboot-1590337225

What? I can't boot into recovery mode because I flashed a recovery for the Nexus 7. And I can't use ADB because I can't boot into Android either.

Use WugFresh Nexus Root Toolkit. It's worked for me on tablets that could not get past the bootloader on their own.
http://www.wugfresh.com/nrt/

1) Press power + volup + voldown and enter bootloader
2) Flash recovery with command:
fastboot flash recovery recovery.img
done

Related

Able to boot to Recovery from Bootloader?

I am not able to.
I can boot into recovery from the system menu, and I can boot into it from within apps...but not from within the bootloader.
In order to get to the recovery if I'm stuck i need to reflash (and boot) the recovery from fastboot
fastboot flash recovery ****.img
fastboot boot ****.img
I don't know about recovery by boot loader, but I believe the command to get into recovery is adb reboot recovery. You might have to use it from fast boot too
Sent from my Nexus 7 using xda app-developers app
plug in via usb while in the bootloader, then press recovery. you should be able to get in then. its a bug that some are experiencing.
If you are not near a computer... there's an app for that.
https://play.google.com/store/apps/details?id=com.siriusapplications.quickboot
allows you to boot directly to Recovery, bootloader etc... without an attached computer.
You can also use a terminal and do it from within the device, but this is just a simple button that works.
bongostl said:
I am not able to.
I can boot into recovery from the system menu, and I can boot into it from within apps...but not from within the bootloader.
In order to get to the recovery if I'm stuck i need to reflash (and boot) the recovery from fastboot
fastboot flash recovery ****.img
fastboot boot ****.img
Click to expand...
Click to collapse
I had the same issue with my recovery. Everytime I tried to get into recovery via fastboot it was just showing the nexus logo and then freezing on that. I flashed CWM and now that was the only way I could get into it.
there are too many apps that do it. plus you can type reboot recovery in the terminal emulator.
simms22 said:
there are too many apps that do it. plus you can type reboot recovery in the terminal emulator.
Click to expand...
Click to collapse
Yes--thank you everyone...I am already aware of the many ways to get into recovery.
The issue is getting into recovery in a situation where you can't fully boot into android (boot loop, etc...)
In such cases, it is really nice to be able to select recovery from the bootloader.
However, right now I need to be near a computer so I can flash the recovery all over again

Tried going back to Stock

i unrooted my nexus 7 and now it is stuck at boot loop i just stuck at the boot logo.. the unooting method had to be success cause it said and it re booted it just stuck at boot logo
Ok so Power off your device, or whilst its rebooting hold the Volume Down button.
You should get back to your BootLoader
Plug it into PC and then do fastboot devices.
Your device should be listed.
I would re-unlock your bootloader.
Then Download TWRP - http://techerrata.com/file/twrp2/grouper/openrecovery-twrp-2.6.3.0-grouper.img
Put that in your Fastboot folder on your PC and type: fastboot flash boot openrecovery-twrp-2.6.3.0-grouper.img
That should flash TWRP. Then push volume up in your bootloader menu, until you see "Recovery".
Open the Recovery and TWRP should load.
Then go to : https://developers.google.com/android/nexus/images#nakasi
Download the correct stock image depending on your version you were at before you tried doing what you did.
Then, depending on the version you downloaded do this (I'll use the 4.2.2 one as example).
On TWRP, go to "Advanced"
Then you should see "Sideload"
Choose sideload and swipe accross, it should now say something like "Waiting for sideload".
Go back to your PC And open another CMD as you would for fastboot.
Type adb sideload nameofyourdownloadedimage.img
Wait for sideload and whalla
(I may have missed something, if so when you get stuck let me know and I'll help further".
wilks3y.
Are you stuck at the "Google" splash or the "X" bootanimation?

No fastboot, adb and bootlooping

Hi,
I have multirom installed and tried to install a android 5.0 rom. After installation I had some kind of boot loop: google logo -> restart
After that I rebooted via fastboot to recovery, but after the splash screen it rebootet and I got again the boot loop.
My next step was to try fastboot boot with the multirom recovery image and my default boot.img, but no success...
Then I noticed that I need for this 5.0 rom the 4.23 bootloader, so I upgraded from 4.13 (I think).
Same after that...
Then I tired fastboot boot with a stock TWRP recovery image for nexus 7 (2012) and I got a new kind of bootloop after that: google logo -> TWRP Logo -> restart
And now it tries to boot TWRP every time I turn on the devices and can't boot to fastboot (via vol - button) and adb is not working too...
Any ideas?
Download factory image and do a clean flash with wug tool kit. This will fix it.
To install the factory image, I need fastboot and I can't enter fastboot mode.
ThauExodus said:
Hi,
I have multirom installed and tried to install a android 5.0 rom. After installation I had some kind of boot loop: google logo -> restart
After that I rebooted via fastboot to recovery, but after the splash screen it rebootet and I got again the boot loop.
My next step was to try fastboot boot with the multirom recovery image and my default boot.img, but no success...
Then I noticed that I need for this 5.0 rom the 4.23 bootloader, so I upgraded from 4.13 (I think).
Same after that...
Then I tired fastboot boot with a stock TWRP recovery image for nexus 7 (2012) and I got a new kind of bootloop after that: google logo -> TWRP Logo -> restart
And now it tries to boot TWRP every time I turn on the devices and can't boot to fastboot (via vol - button) and adb is not working too...
Any ideas?
Click to expand...
Click to collapse
I was stuck the same way yesterday. Use the WUGS Nexus Root Toolkit. http://forum.xda-developers.com/showthread.php?t=1766475
I had to fool around with it before it would see the device, but once it did, I flashed the LRX21P and was off and running.
When I want to use in the toolkit "Back to Stock (Soft-Bricked/Bootloop) it asks me to tsrat into fastboot mode... but I can't... but I can get the device into apx mode...
Bump...
ThauExodus said:
When I want to use in the toolkit "Back to Stock (Soft-Bricked/Bootloop) it asks me to tsrat into fastboot mode... but I can't... but I can get the device into apx mode...
Click to expand...
Click to collapse
You mention TWRP - are you able to boot into TWRP, or does it just show the splash and reboot again? If you can get into TWRP, you could conceivably use ADB mode and sideload something...
Splash and reboot... I already tried to get adb access, but no success...

Help please can't see my phone in adb

I've had my Essential two weeks i was on 8.1 beta.Today i unlocked the boot loader.Then installed twrp while in twrp i side loaded magisk.I went back to fastboot then hit start .The phone just went into a bootloop.I Was able to go back to twrp 2 times but now i can't get back to any type of recovery.I Can get back to fastboot mode ishow all the info and secure boot says yes and device state unlocked.My pc see essential phone fastboot in the device manager but i can't get adb to see it .Can anyone help me ?
forgot something
looks like i skipped this part . Once you're in TWRP, install the stock boot image and then the Magisk/SuperSU zip.Is there anything i can do?
videodave1 said:
I've had my Essential two weeks i was on 8.1 beta.Today i unlocked the boot loader.Then installed twrp while in twrp i side loaded magisk.I went back to fastboot then hit start .The phone just went into a bootloop.I Was able to go back to twrp 2 times but now i can't get back to any type of recovery.I Can get back to fastboot mode ishow all the info and secure boot says yes and device state unlocked.My pc see essential phone fastboot in the device manager but i can't get adb to see it .Can anyone help me ?
Click to expand...
Click to collapse
adb only works while phone is booted into system so nothing wrong there. If you're in the bootloader menu where you see that the status of your device is unlocked then you're already in fastboot mode. Just flash twrp again and the sideload stock 8.1 beta boot image (you can probably find it on xda), sideload magisk too. Go into install and press flash image file and find the stock boot image and then go into install again and change to flash .zip and flash magisk. After that, reboot into system.
WOW thank you so much'
Arju said:
adb only works while phone is booted into system so nothing wrong there. If you're in the bootloader menu where you see that the status of your device is unlocked then you're already in fastboot mode. Just flash twrp again and the sideload stock 8.1 beta boot image (you can probably find it on xda), sideload magisk too. Go into install and press flash image file and find the stock boot image and then go into install again and change to flash .zip and flash magisk. After that, reboot into system.
Click to expand...
Click to collapse
I was able to flash twrp i'll try the rest when i get home from work
sideloading stock img
videodave1 said:
I was able to flash twrp i'll try the rest when i get home from work
Click to expand...
Click to collapse
Do i need it to be zipped I've tried it as image that i downloaded from xda and I've tried a zip i got from Essential neither are working?
zip file
videodave1 said:
Do i need it to be zipped I've tried it as image that i downloaded from xda and I've tried a zip i got from Essential neither are working?
Click to expand...
Click to collapse
When i try i get invalid file format. This is using a zip i got from Essential.
Stuck twrp says no os installed . But i did learn how to push files.
just trying to get back to stock now 
videodave1 said:
just trying to get back to stock now 
Click to expand...
Click to collapse
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
thanks been there tried the Oreo beta that is what i was on when i started and tried the 1st build before the betas i get an error on both i'll try to download them on another pc my phone does show up when i type fastboot devices now just need an os now .
Okay got back to 8.1 bootloader still unlocked twrp not install and i don't have root.I may just wait until P comes out.I'll try and learn more about adb. Thanks for your help Arju.
thanks everyone.
videodave1 said:
Okay got back to 8.1 bootloader still unlocked twrp not install and i don't have root.I may just wait until P comes out.I'll try and learn more about adb. Thanks for your help Arju.
Click to expand...
Click to collapse
No problem. Thank you very much for the donation, that was really kind of you. Hey I'm sure you'll get the hang of it before android P drops. you did figure out what went wrong all by yourself so get a hold of the right boot.img and the rest is exactly as how you did it in the first place but flash the boot.img before magisk. Let me know if you want to give it a dive again.
I'm on 8.1 boot loader unlocked and ready to try to root again .Thanks for the help
This is the closest thread i could find to what is happening to my PH-1.
Like videodave1 I 'was' running the latest stock 8.1 and have my bootloader unlocked. In trying to root the phone I did this:
flash boot flash boot twrp.img
adb shell twrp sideload
adb sideload magisk.zip
All installations went well, but when trying to reboot from twrp it forced me to install the app. After that the phone went into boot loop.
* Note how I didn't sideloaded the Oreo 8.1 image before magisk.
By pressing all 3 buttons I can get the phone to reboot and releasing the volume up I can get to Fastboot. Just volume down and power doesn't work.
The problem now is that adb and fastboot no longer recognise the phone. adb devices just gives an empty list and fastboot only shows < waiting for device >
Trying to go into Recovery mode doesn't work either. Power off doesn't work and Restart bootloader, well, restarts the bootloader.
It might be relevant to mention that I'm running adb and fastboot from Terminal in a Mac and that this is my very first and frustrated attempt to root any phone.
For reference this is what the FastBoot Mode brings:
PRODUCT_NAME - Mata
VARIANT - OPENUS
BOOTLOADER VERSION - mata-aad8ac4
BASEBAND VERSION - 2.0.C4-M1.3.1
SECURE BOOT - yes
DEVICE STATE - unlocked
I might have to just resign myself to the ordinary land of unlocked full stock phones
Thanks very much
avocom said:
This is the closest thread i could find to what is happening to my PH-1.
Like videodave1 I 'was' running the latest stock 8.1 and have my bootloader unlocked. In trying to root the phone I did this:
flash boot flash boot twrp.img
adb shell twrp sideload
adb sideload magisk.zip
All installations went well, but when trying to reboot from twrp it forced me to install the app. After that the phone went into boot loop.
* Note how I didn't sideloaded the Oreo 8.1 image before magisk.
By pressing all 3 buttons I can get the phone to reboot and releasing the volume up I can get to Fastboot. Just volume down and power doesn't work.
The problem now is that adb and fastboot no longer recognise the phone. adb devices just gives an empty list and fastboot only shows < waiting for device >
Trying to go into Recovery mode doesn't work either. Power off doesn't work and Restart bootloader, well, restarts the bootloader.
It might be relevant to mention that I'm running adb and fastboot from Terminal in a Mac and that this is my very first and frustrated attempt to root any phone.
For reference this is what the FastBoot Mode brings:
PRODUCT_NAME - Mata
VARIANT - OPENUS
BOOTLOADER VERSION - mata-aad8ac4
BASEBAND VERSION - 2.0.C4-M1.3.1
SECURE BOOT - yes
DEVICE STATE - unlocked
I might have to just resign myself to the ordinary land of unlocked full stock phones
Thanks very much
Click to expand...
Click to collapse
Even though your phone does not show up its there wipe everything.Fallow what Arju said in his post.I got back to stock then took the 8.1 update i'm not rooted but my bootloader is still unlocked.Oh make sure you unlock critical
videodave1 said:
Fallow what Arju said in his post.
Click to expand...
Click to collapse
Thanks for coming back to me. I really appreciate it.
Arju said:
Just flash twrp again and the sideload stock 8.1 beta boot image (you can probably find it on xda), sideload magisk too.
Click to expand...
Click to collapse
I might be missing something hopefully obvious here. How can I flash twrp again if I my computer can't see the phone. With the USB phone plugged in and in the FastBoot screen I enter into Terminal:
fastboot flash boot twrp.img
and I get:
< waiting for any device >
How do I flash it from the FastBoot screen? BTW, going to Recovery mode just hangs at the Essential logo.
Thanks
avocom said:
Thanks for coming back to me. I really appreciate it.
I might be missing something hopefully obvious here. How can I flash twrp again if I my computer can't see the phone. With the USB phone plugged in and in the FastBoot screen I enter into Terminal:
fastboot flash boot twrp.img
and I get:
< waiting for any device >
How do I flash it from the FastBoot screen? BTW, going to Recovery mode just hangs at the Essential logo.
Thanks
Click to expand...
Click to collapse
are you able to get to the bootloader menu? where it says start on the top.
Arju said:
are you able to get to the bootloader menu? where it says start on the top.
Click to expand...
Click to collapse
Thanks Arju. If you are referring to the FastBoot menu where you can use the up and down volume keys to select Start, Restart Bootloader, Recovery mode and Power off Yes, but not much else unfortunately.
If I select Recovery mode I don't go to the screen with the blue buttons from twrp.
Thanks
avocom said:
Thanks Arju. If you are referring to the FastBoot menu where you can use the up and down volume keys to select Start, Restart Bootloader, Recovery mode and Power off Yes, but not much else unfortunately.
If I select Recovery mode I don't go to the screen with the blue buttons from twrp.
Thanks
Click to expand...
Click to collapse
What you need to understand is that twrp will not stick after you flash it. This device does not have a recovery partition and that's why you replace the boot partition with twrp and while you're in twrp you need to flash the boot.img back and whatever mods on top of that such as kernel etc.. If you flash a rom then it will replace the twrp with the boot.img found in the rom zip.
So now we need the computer to recognize you device. Could you unplug the cable and change the usb port on you computer. connect your phone while you're in the bootloader menu where it says start on the top.
The use use fastboot command: fastboot devices
See if the computer recognizes you device.

Oneplus 6T hard brick?

Hello guys
I have a problem, yesterday I was putting the twrp to my one plus 6t via fastboot and as soon as I entered the bootloader I put the command "fastboot boot twrp.img" and it said "fastboot unknow command".
So I searched on google for the commands to start the twrp via the PC terminal and I found this command "fastboot flash recovery twrp.img".
Everything ok, it restarts the screen, 3 minutes then it is turned off and remains in the initial screen where it says that the bootloader is unlocked, it does not go in fastboot mode not in recovery
Tips?
Use the Msm tool to recover if your phone is bricked.
https://forum.xda-developers.com/on...-msmdownloadtool-v4-0-oos-9-0-5-t3867448/amp/
FrancescoPtr said:
Hello guys
I have a problem, yesterday I was putting the twrp to my one plus 6t via fastboot and as soon as I entered the bootloader I put the command "fastboot boot twrp.img" and it said "fastboot unknow command".
So I searched on google for the commands to start the twrp via the PC terminal and I found this command "fastboot flash recovery twrp.img".
Everything ok, it restarts the screen, 3 minutes then it is turned off and remains in the initial screen where it says that the bootloader is unlocked, it does not go in fastboot mode not in recovery
Tips?
Click to expand...
Click to collapse
When it comes to A/B slot phones (Like the OnePlus 6T), you're not suppose to use the fastboot flash recovery twrp.img command. The reason why is because that command doesn't apply to A/B slotted phones, you need to use the fastboot boot twrp.img command to boot into TWRP and then flash the TWRP flasher for OnePlus 6T which can be found here:
https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482
Make sure to download the flasher zip and the latest img for TWRP.
Drag the .img into the fastboot folder and use fastboot boot twrp-3.3.1-8-fajita.img. Then once it boots into TWRP, drag and drop the installer zip onto your phone's storage and flash it. Reboot into recovery and you should have TWRP on your phone.
ImmorTaLGiLL said:
Use the Msm tool to recover if your phone is bricked.
https://forum.xda-developers.com/on...-msmdownloadtool-v4-0-oos-9-0-5-t3867448/amp/
Click to expand...
Click to collapse
I tried but didn't see it
Sadistic_Loser said:
When it comes to A/B slot phones (Like the OnePlus 6T), you're not suppose to use the fastboot flash recovery twrp.img command. The reason why is because that command doesn't apply to A/B slotted phones, you need to use the fastboot boot twrp.img command to boot into TWRP and then flash the TWRP flasher for OnePlus 6T which can be found here:
https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482
Make sure to download the flasher zip and the latest img for TWRP.
Drag the .img into the fastboot folder and use fastboot boot twrp-3.3.1-8-fajita.img. Then once it boots into TWRP, drag and drop the installer zip onto your phone's storage and flash it. Reboot into recovery and you should have TWRP on your phone.
Click to expand...
Click to collapse
ok but it does not go into fastboot mode or in recovery mode
FrancescoPtr said:
I tried but didn't see it
Click to expand...
Click to collapse
Make sure the device is off,Press volume up + volume down button then connect it to the computer.
If your device still doesn't show up,try pressing volume up+volume down+power button and then connect it.
This worked for me in many cases.
When I connect my phone via USB it shows up in the device manager as Qualcomm HS-USB.... But when I try using MSM it shows the phone connected on port 16 and I hit start and it fails after 16 seconds because it can't do a download. My question is is the download external via internet or is it a file in the MSM folder? I might be blocked by firewall at work if external.
EDIT: Looks like I found my issue. I couldn't tell if my phone was on or off since I had no display after trying about 20 more times I guess I got it ON.

Categories

Resources