[Q] Found phone stuck at recovery - Droid Eris Q&A, Help & Troubleshooting

A friend found a Droid Eris on the side of the road. It would only boot to HBOOT. I am trying to fix the phone.
When I started working on it the bootloader was 1.47.0000 S-ON
I followed this Q and A thread to flash 1.29.2000 S-OFF
I can not get it to boot Amon's recovery. It freezes at the three skateboarding androids. It always boot to fastboot even if I have other buttons held down.
I have tried fastboot erase, flash, and boot.
I know how to use adb and fastboot.
In summary I have never been able to get the phone to boot fully but was able to flash the root rom with S-OFF. Now I need help booting to recovery.
Thanks in advance

This post has both a version of Amon_RA Recovery that can work with a broken trackball, plus instructions on how to flash with fastboot with the S-OFF bootloader (see scenario 4 toward the bottom): http://androidforums.com/eris-all-t...2-custom-recovery-trackball-not-required.html

Related

[Q] HTC unlock method don't work?

hi all,
I just soft bricked my evo 3d, who will kindly help me?
My new htc evo 3d just go in trouble: when I rebooted yesterday it just boot loop, then I googled and tried my methods to make it boot, all failed!
My evo 3d is hboot 1.5, and I followed htc method to unlocked it, and tried ruu from goo-inside.me/shooter/ruu ( md5sum checked), but failed to boot up.
Then, I tried:
fastboot erase boot
give thus result:
erasing 'boot'...
FAILED<remote:not allowed>
But It seemed that the command "fastboot flash boot boot.img" successful:
sending 'boot' < 3604 KB>...
OKAY [1.016s]
writing 'boot' ...
OKAY [ 8.468s]
finished..
But, I unlocked with htc method, and I can see ***UNLOCKED*** when get into fastboot, why I can not erase boot and any other partitions? So I guess flash boot successful just a fake?
Am I right? What should I do next?
Thanks in advance!
I'm sorry for my English!
I mean, my evo 3d has HBOOT 1.5, and now go in trouble of boot loop.I have followed htcdev.com to unlocked the bootloader, and have tried:
* after unlocked the bootloader,tried twrp-1.0.3, cwm-4.1.0.4 recovery, but all failed to boot into, just stop @ splash screen.
* then I relock with 'fastboot oem lock', and flash with ruu 2.08.651.2, but still failed to escape from boot loop.
* then I unlock it again, and tried 'fastboot erase boot' and want to reinstall boot partition, but failed when running 'fastboot erase boot', please refer to #1 post.
So I think HTC unlock method maybe a suck? if I can not erase the old boot partion, how can i write to boot partion? Am I right?
Thank for any help!
EDIT: I found that after boot loop some times(maybe 10 times), the phone will become very hot, especially around the camera, I don't know why.
Go y htcevohacks.com and follow the really easy steps there to do unlock, get recovery, and super user to all work well. I used these steps and had no problem. I running clean ROM and a custom kernel.
---------- Post added at 03:05 PM ---------- Previous post was at 02:59 PM ----------
There are only 2 recoveries working for the HTC way they have been modified to work with the hboot 1.5 the htcevohacks.com way has a zip file that has everything you need to do the recovery and superuser. Just read the threads and you can find more detailed instructions....
jamesjeter1 said:
Go y htcevohacks.com and follow the really easy steps there to do unlock, get recovery, and super user to all work well. I used these steps and had no problem. I running clean ROM and a custom kernel.
---------- Post added at 03:05 PM ---------- Previous post was at 02:59 PM ----------
There are only 2 recoveries working for the HTC way they have been modified to work with the hboot 1.5 the htcevohacks.com way has a zip file that has everything you need to do the recovery and superuser. Just read the threads and you can find more detailed instructions....
Click to expand...
Click to collapse
Thanks jamesjeter!
I have followed htcevohacks' method, but can not enter into recovery, everytime when I select recovery from fastboot, it just boot into normal mode and stuck at the splash screen with HTC logo and then boot loop.
I have tried fastboot boot cwm-4.0.1.4-shooter.img or fastboot flash recovery cwm-4.0.1.4-shooter.img, all failed.
I just can not enter into recovery.
I don't know it is a software brick or a hardware brick? and anyway I can break the boot loop?
Thanks in advance!
do you ever get everything working. Im still stuck trying to get into recovery
MWaV said:
do you ever get everything working. Im still stuck trying to get into recovery
Click to expand...
Click to collapse
You also posted this question in my Flash Image GUI thread. I'll provide you the same answer here:
Steps 1 - 3 will work having used AlphaRevX's revolutionary method. Steps 1 & 3 will work having used HTC's unlock method. The two methods unlock the internal memory write protection differently, hence the difference in steps for flash a custom recovery on the EVO 3D.
1) Flash from normal android mode: My application works well for this, Flash Image GUI, as well as flashing kernels, especially when being away from or not having a computer available.
2) Flash through the bootloader by putting a PG86IMG.zip file on the root of your sdcard. This file with the recovery.img loaded inside is available at the TWRP site.
3) Flash through fastboot by using the following command: fastboot flash recovery c:\downloads\twrp-recovery.img
Hope that helps!
thanks bro, sorry about the double post
subaochen said:
Thanks jamesjeter!
I have followed htcevohacks' method, but can not enter into recovery, everytime when I select recovery from fastboot, it just boot into normal mode and stuck at the splash screen with HTC logo and then boot loop.
I have tried fastboot boot cwm-4.0.1.4-shooter.img or fastboot flash recovery cwm-4.0.1.4-shooter.img, all failed.
I just can not enter into recovery.
I don't know it is a software brick or a hardware brick? and anyway I can break the boot loop?
Thanks in advance!
Click to expand...
Click to collapse
i used the TWRP recovery for Hboot 1.50 http://www.mediafire.com/?n72emuv5a1c00sd Put the recovery.img on the root of sd card.
type:fastboot boot recovery.img
Hope that helps
I think I got your answer. Relock phone with HTC method and then reflash ruu complety and reroot with HTC method.
Sent from my Nocturnal 3D using xda premium

[Q] unable to run any recovery

hi guys iive unlocked my evo with the htcdev mod and no problem has come out , bun i'm unable to run any recovery.
iìve tryed all cwm twrp and any i found on the site.
i try with fastboot method and abd, all say that the recovery vas written , no error but when i try to lunch recovery the phone show the htc logo stay 10/15 second then reboot the phone.
pls help me
Have you tried downloading the twrp pg86img.zip & make sure it's named PG86IMG.zip then put it on the root of you're sdcard, boot into bootloader and update that way?
CM powered EVO 3D, enough said.
luca73n said:
hi guys iive unlocked my evo with the htcdev mod and no problem has come out , bun i'm unable to run any recovery.
iìve tryed all cwm twrp and any i found on the site.
i try with fastboot method and abd, all say that the recovery vas written , no error but when i try to lunch recovery the phone show the htc logo stay 10/15 second then reboot the phone.
pls help me
Click to expand...
Click to collapse
when the device either hangs on the htc logo or reboots while on the htc logo, it means there is an issue with the actual kernel/ramdisk.
when dealing with a custom recovery, they should always boot without any issues. the best suggestion off the top of my head is to make sure if you're on the CDMA version, use the shooter recovery and if you're on the GSM version, use the shooteru version of the custom recovery.
otherwise, as suggested above, reflash the confirmed correct custom recovery for your device. there are a few ways to flash the custom recovery although, being you used the htc unlock method, regular custom recovery mode will not have write access to the boot/kernel partition.
if you're interested in loading any ROMs which come with kernels or separately flashing a custom kernel, there are essentially two complete methods:
1) use my Flash Image GUI app from normal android mode to flash the kernel. then flash the ROM from custom recovery.
2) use fastboot boot c:\android\cwm-recovery.img . this will temporarily boot the custom recovery and htc unlock will grant it write access to the kernel/boot partition. this command is different than fastboot flash recovery c:\android\cwm-recovery.img. the fastboot boot will temporarily boot into the custom recovery while fastboot flash will permanently write it into the recovery partition.
hope all the extra details make sense and helps!
Ummm.....Just my 2 cents, but it sounds as though the most basic possible problem has been overlooked here. You need to go into menu>settings>power and uncheck the "fast boot" box or do a battery pull, then try to boot into your bootloader to access recovery. With your phone completely powered down (fast boot unchecked or after battery pull), hold volume down and press power. That will put you in your bootloader with an option to boot recovery from there.
ok i'm a noob i've used thr shooter and not the shooteru cwm img, now all works
ty guys

[FIX] & [DOWNGRADE HBOOT] - Stupid Bootloop with HBOOT 1.58 EVO 3D - UPDATED 1-7-13

[FIX] & [DOWNGRADE HBOOT] - Stupid Bootloop with HBOOT 1.58 EVO 3D - UPDATED 1-7-13
My friend's phone had the annoying bootloop problem. I'm posting this because after a lot of searching, I found nothing to fix the bootloop, just people asking about it. Here's a simply fix.
BOOTLOOP FIX:
If you already tried unlocking/ and you're still S-On, then set everything back to stock:
Flash the attached stock recovery,
fastboot oem lock to be locked again.
Use the latest RUU to update the phone.
At this point the stock, locked phone should function normally.
I have busted this phone a ton of times trying to get different recoveries and roms to work, and this method has always fixed the bootloop.
At this point you can try whatever tutorial you like to downgrade or customize the phone...and if it breaks, hopefully this method will still work for you. If it doesn't work the first time, try running the RUU a second time. Or third.
CUSTOM RECOVERY:
If you want to unlock and install custom stuff:
Use the HTC Dev unlock method.
Fastboot install CWM Recovery v5.8.0.1 from their website -
The ONLY recovery that I've found to be compatible with HBOOT 1.58 is CWM v5.8.0.1. Everything else leaves the phone in an infinite bootloop. Maybe others have had different experiences.
To fastboot install the CWM recovery, rename the file to recovery.img (for simplicity) and type in a command prompt (same directory as fastboot and recovery.img):
fastboot flash recovery recovery.img
Then, to enter into recovery, either pull the battery and enter recovery through the bootloader menu, or type in:
fastboot boot recovery.img
This should get you into the working CWM recovery. If it doesn't, it's because HTC hates people that buy their phones.
If you feel like giving up and running stock, all you need to do is reflash the stock recovery, and relock the phone using fastboot oem lock - and now it should run the stock rom...and if it doesn't, then rerun the RUU. Tedious.
HBOOT Downgrade & S-Off:
If you have: Stock 2.89 RUU / Locked / S-On
Unlocked with HTC Dev method
Flash CWM 5.8.0.1 from the CWM website:
fastboot flash recovery recovery.img - then
fastboot boot recovery.img (to enter recovery)
Flash the SetMainVersionLOW.zip file attached (thanks ramjet73)
Relock the phone with: fastboot oem lock
Use the Unknownforce/closeone hboot downgrade with live CD using the 2.89 RUU's rom.zip (from windows temp folder) renamed to PG86IMG.zip - go to the Unknownforce/closeone thread for this part: http://forum.xda-developers.com/showthread.php?t=1563342
Then flash the standard 1.13 RUU on your windows system (may also work with the PG86IMG.zip method, have not tested)
Then use revolutionary 0.4pre4 to S-Off
Finally, you need to flash a custom recovery which you can do from revolutionary, or from fastboot as listed above. Once the recovery is installed, you should be able to install a compatible custom rom and kernel.
You bootloader screen should now say REVOLUTIONARY on top instead of UNLOCKED or RELOCKED etc... and show HBOOT 1.40.1100.
Thanks to Unkownforce, closeone, and ramjet73 for making this possible.
PS. Screw up your phone at your own risk.
In case anybody was wondering, the RUU I've been using is the latest one at the time of this post: RUU_Shooter_ICS_35_S_Sprint_WWE_2.89.651.2_Radio_1.09.00.0706__NV_NV_SPCS_1.43_release_271101_signed.exe
If by "reset s-on" you mean to switch s-off to s-on using the "write secureflag 3" command, then there is no need to do that., you can directly run RUU.exe on S-OFF and any recovery (hboot needs to be one of the stock versions I guess, I dont know for sure).
And I dont know if theres any relation with hboot version and recovery but TWRP and 4ext recovery works for every hboot. And if you are s-on, you dont always have to flash boot.img seperately using fastboot if you turn smartflash on.
mnomaanw said:
If by "reset s-on" you mean to switch s-off to s-on using the "write secureflag 3" command, then there is no need to do that., you can directly run RUU.exe on S-OFF and any recovery (hboot needs to one of the stock versions, I dont know for sure).
And I dont know if theres any relation with hboot version and recovery but TWRP and 4ext recovery works for every hboot. And if you are s-on, you dont always have to flash boot.img seperately using fastboot if you turn smartflash on.
Click to expand...
Click to collapse
Yeah, don't ever do the write secure flag command. That's bad news. Running a ruu will not s- on, and you're better staying s-off
Sent from my PG86100 using xda app-developers app
Reset s-on, and
fastboot oem lock to be locked again.
Click to expand...
Click to collapse
As others have mentioned, this is completely unnecessary. Once you're s-off htc's unlock is a non-issue and you can run any RUU you wish to at any time.
I know of no reason whatsoever where someone would need to set S-ON once it's off.
xHausx said:
As others have mentioned, this is completely unnecessary. Once you're s-off htc's unlock is a non-issue and you can run any RUU you wish to at any time.
I know of no reason whatsoever where someone would need to set S-ON once it's off.
Click to expand...
Click to collapse
@xHausX
Totally agree. The only reason to set S-ON once S-OFF is achieved is to return to 100% stock for warranty service or to sell the phone.
Nice to see you in these parts again and Happy New Year!
@joshdv
The CWM recovery version (6.0.1.4) you attached to the OP gives an error about accessing mmcblk0p34 when used with the engineering (ENG) bootloader, which a lot of Evo 3D users have installed to run GB or AOSP based ROM's. The current version of TWRP2 (2.3.3.0) has a similar error about the misc partition and I don't know if those errors will affect anything else or not. Apparently those errors are caused by variations in the emmc partition layouts with different bootloaders.
I prefer to use 4EXT which doesn't show any errors once cache+dalvik are formatted.
ramjet73
I updated the OP. I read somewhere else that it was necessary, this phone was never S-Off, so I wasn't sure.
Thanks
Everytime i run the ruu for my 3d it will finish as it has completed and boot. But whenever i remove my battery to switch it with a secondary, i used to do this before bed every night, i get a bootloop and cant boot untill i boot into bootloader and select the recovery option which wipes the phone and boots untill then next time i remove the battery. Why wont the RUU fix this? ive ran it multiple times. And also whenever im in the stock recovery and i select factory reset or any of the options i get "invalid option" "sucess rebooting by reason oem-00" what does this mean!?! can this be my sd? cause i cant mount cache recovery command or mount anything in recovery for that matter. if i need an sd ill buy one. just dont wanna find out its not my sd. and ive run the RUU about 7 times in total and nothing helps. thanks
ramjet73 said:
@joshdv
The CWM recovery version (6.0.1.4) you attached to the OP gives an error about accessing mmcblk0p34 when used with the engineering (ENG) bootloader, which a lot of Evo 3D users have installed to run GB or AOSP based ROM's. The current version of TWRP2 (2.3.3.0) has a similar error about the misc partition and I don't know if those errors will affect anything else or not. Apparently those errors are caused by variations in the emmc partition layouts with different bootloaders.
I prefer to use 4EXT which doesn't show any errors once cache+dalvik are formatted.
ramjet73
Click to expand...
Click to collapse
Yeah, I put WIP because it still never worked right, it was just the only one that ever actually loaded. I still hate this phone, I wish HTC was as nice as Samsung. It's so easy to work with Samsung, I always get mad trying to work around HTC's crippling B.S. Still better than Motorola though.
bootloop in my Htc Evo 3D hboot 1.53.007
How do you flash the stock recovery?
jcthelight said:
How do you flash the stock recovery?
Click to expand...
Click to collapse
put your phone into the bootloader by holding the volume down key while turning it on.
Assuming you have the sdk tools, or some basic set like QADERSO.zip:
select fastboot from the bootloader menu, then connect it to your computer with a usb cable (should change to fastboot usb)
in a command prompt (or terminal window, depending on your OS)
Go into the folder containing both fastboot and the recovery.
Type in: fastboot flash recovery recovery.img (rename the stock recovery included in the OP to just recovery.img)
Once that is complete, you will have the stock recovery.
joshdv said:
put your phone into the bootloader by holding the volume down key while turning it on.
Assuming you have the sdk tools, or some basic set like QADERSO.zip:
select fastboot from the bootloader menu, then connect it to your computer with a usb cable (should change to fastboot usb)
in a command prompt (or terminal window, depending on your OS)
Go into the folder containing both fastboot and the recovery.
Type in: fastboot flash recovery recovery.img (rename the stock recovery included in the OP to just recovery.img)
Once that is complete, you will have the stock recovery.
Click to expand...
Click to collapse
i have hboot 1.53 with s-on stuck on bootloop and i did as u said i flashed stocked recovery from temp folder from ruu-ics-35-ara.exe still my phone is in boot loop. Even i tried oem lock and run ruu.exe file upto 65% process goes fine then suddenly shows 100% process complete and reboot device(still stuck on bootloop).... plz give me suggestion to get rid of this thing.....
"RUU_SHOOTER_U_ICS_35_S_HTC_ARA_3.28.415.2_Radio_11.77.3504.00U_11.25.3504.06_M_release_264795_signed.exe"
joshdv said:
put your phone into the bootloader by holding the volume down key while turning it on.
Assuming you have the sdk tools, or some basic set like QADERSO.zip:
select fastboot from the bootloader menu, then connect it to your computer with a usb cable (should change to fastboot usb)
in a command prompt (or terminal window, depending on your OS)
Go into the folder containing both fastboot and the recovery.
Type in: fastboot flash recovery recovery.img (rename the stock recovery included in the OP to just recovery.img)
Once that is complete, you will have the stock recovery.
Click to expand...
Click to collapse
I'm a little confused. I've never rooted this phone so it's completely stock. My phone keeps powercycling. When I type in "fastboot flash recovery recovery.img" my cmd prompt tells me FAILED (remote: signature verify fail).
Any suggestions?
Re: [FIX] & [DOWNGRADE HBOOT] - Stupid Bootloop with HBOOT 1.58 EVO 3D - UPDATED 1-7-
Dang it! Why does it seem like developers have quit developing fully functioning roms for this phone? I live in a good 4g area so those roms without it are out of the question for me. And the others are having major issues with cameras, video playing, text messaging that keep it from being a daily....
And after using jellybean these ICS roms feel very incomplete even though they're more functional. I know you developers are busy people but please, can ICS get freshened up. Or just ignore me if y'all think the camera/text thing will be resolved very soon.
Sent from my PG86100 using xda premium

SOLVED [Q] shooteru - cant get into bootloader after flash attempt

SOLVED
Hey, I have htc evo 3d gsm (shooteru). I unlocked the bootloader using htcdev.com and installed clockworkmod recovery. Then I changed cid to HTC__001 and tried to flash a gingerbread ROM in preparation for using the flashmaniac tool to downgrade my hboot (1.53.0007 -> 1.49.0007).
But when I tried to flash the gb rom the recovery said that installation finished but the phone did nothing after reboot. So I took out the battery and went into bootloader and everything looked the same as before the flash attempt. So I tried once again with same result. Then I powered off the phone and now when I turned it on again it only shows the HTC logo for a few seconds and then nothing (the buttons at the bottom have their lights turned on though).
Any ideas?
Yes, hboot version not compatible with gb rom, and or boot partition didn't get flashed. Unlocked but s-on doesn't let boot partition have write if booted into recovery in a normal way.
So yoy can get boot.img from install zip and flash with fastboot
fastboot flash boot boot.img
Or you can reinstall from recovery if booted from fastboot command.
fastboot boot recovery.img
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
jcfunk said:
Yes, hboot version not compatible with gb rom, and or boot partition didn't get flashed. Unlocked but s-on doesn't let boot partition have write if booted into recovery in a normal way.
So yoy can get boot.img from install zip and flash with fastboot
fastboot flash boot boot.img
Or you can reinstall from recovery if booted from fastboot command.
fastboot boot recovery.img
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
Click to expand...
Click to collapse
Somehow got it at least to bootloader, no idea how, just tried taking out battery a few times and charging it a bit and it worked.
Thanks for the advice, didn't realize there was a difference between these flashing methods.
randomguyhtc said:
Somehow got it at least to bootloader, no idea how, just tried taking out battery a few times and charging it a bit and it worked.
Thanks for the advice, didn't realize there was a difference between these flashing methods.
Click to expand...
Click to collapse
Power + volume down when turning on will get you into bootloader
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
jcfunk said:
Power + volume down when turning on will get you into bootloader
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
Click to expand...
Click to collapse
I know , it just didn't work for some reason before.
So I flashed the boot.img and now it's stuck in a boot loop. Tried going to cwm recovery and wiping various caches etc and flashing again, and flashing boot.img again but it still goes into boot loop.
I would just use the flashmaniac's tool anyway because I don't care about any data on the phone or anything, but it seems that it requires the phone to be booted before it can start the downgrade.
What should I do? Try to flash other roms maybe? The one that I have now is EU_Shooter_U-1.20.401.8_ROOTED.
So I extracted a rom.zip from a RUU but it won't flash from cwm "Can't open /sdcard/rom.zip (bad)", should I try to flash it with adb/fastboot? I'm worried that the zip may be broken (even though archive manager integrity check says its fine).
Would this work with shooteru/GSM?
[TOOL] Ultimate Recovery Tool 3.1 (Unbrick, Downgrade, VM Radio Fix/Reset)
I'm thinking it might be a way to sidestep the boot loop problem that I have now, just relock the bootloader and follow the instructions until I get HBoot 1.40.something like the guy in the video?
Do I need some special drivers when using the RUU executables on Windows?
So I've got it to work. The problem was what jcfunk said (both of the things he mentioned, actually), I was trying to flash a GB rom when I should have tried an ICS rom instead (lol). After going to ICS RUU, I did the wire trick (unlimited.io) and now everything works nicely and I can get the latest roms.
Glad to hear.

Stuck Rooting and Flashing Custom ROM

Hi, I oem unlocked my Nexus 9, installed TWRP and SuperSU, but I think I missed a step before I can go to custom ROMs and all. I've looked for instructions but I'm just getting confused. I firstly cannot reboot into TWRP unless I fastboot boot recovery from my PC every time. If I don't do that, it just boots into the Flounder PVT Ship white screen with Fastboot USB in red and below that HBOOT, REBOOT, REBOOT FASTBOOT, and POWER DOWN.
What step am I missing in this process? Do I need some sort of custom image or what am I doing wrong?
Thanks,
Chris
Hello,
It can get a bit confusing sometimes and people generally expect you to just know lol.
You've not missed a step. Getting into recovery is irritating lol. For as long as I've had it if booted into recovery from the power menu lol xD.
Reboot the Google Nexus 9 by holding the Power and the Volume Down buttons at the same time and wait until the tablet display shows a Google splash screen before releasing the buttons.
If you get a android with an exclamation mark then you've made a boo boo. Dw, even us pros muck up ;]
Go back to your fastboot. Flash twrp like you do. But this time once you've flashed it type
Code:
fastboot boot recovery twrp.img
That should boot your device into recovery after flashing it.
There it should be stuck on there nicely of it takes a while Dw. That's just the fun of owning a N9 lol. That should Do it .
Happy Flashing.
Give us a Thanka if I helped
ChrispyChris said:
Hi, I oem unlocked my Nexus 9, installed TWRP and SuperSU, but I think I missed a step before I can go to custom ROMs and all. I've looked for instructions but I'm just getting confused. I firstly cannot reboot into TWRP unless I fastboot boot recovery from my PC every time. If I don't do that, it just boots into the Flounder PVT Ship white screen with Fastboot USB in red and below that HBOOT, REBOOT, REBOOT FASTBOOT, and POWER DOWN.
What step am I missing in this process? Do I need some sort of custom image or what am I doing wrong?
Thanks,
Chris
Click to expand...
Click to collapse
If you installed TWRP using
Code:
fastboot flash recovery twrp.img
The only ways I know to get into recovery are to reboot to recovery from the Power menu of your ROM
OR
Boot to fastboot, select HBOOT, then select Recovery. If TWRP is installed as your recovery this will boot TWRP. If it goes to the dead droid screen then you need to install TWRP properly, using the fastboot flash command above.
I can't get my nexus 9 to run twrp as well.
I go to fastboo, select Hboot, then I get the android with exclamation, volume up and power brings up the original android recovery menu, not twrp. I've unlocked the bootloader, wiped everything and tried again, no luck. Always the same result
Mephisto_POA said:
I can't get my nexus 9 to run twrp as well.
I go to fastboo, select Hboot, then I get the android with exclamation, volume up and power brings up the original android recovery menu, not twrp. I've unlocked the bootloader, wiped everything and tried again, no luck. Always the same result
Click to expand...
Click to collapse
Are you using the newest TWRP? 3.1.0.0? It's not working for me either, can't boot to recovery. Use 3.0.2.2 or whatever the last version was
I used the 3.1.0.0
the trick was, after installing it, reboot straight back into recovery, so it doesn't get overwritten

Categories

Resources