Develop Bugs

[Q] Has Android Revolution HD install bricked my phone? [Solved]

Hello All.
This is the first time I have tried to put a custom ROM on an HTC so I am still learning the ropes.
I tried to follow the instructions in the first post. So... In sequence, this is what I did...
HTC One X unlocked with htcdev.com (S-ON) or S-OFF (coming soon)
This seemed to go without a hitch. On the HBoot screen (I think that is what it is called) it tells me I am now unlocked.
ClockworkMod Recovery or 4EXT Touch Recovery (coming soon)
I installed the official version as per the instructions here.
The last instruction that seemed to work successfully was this:
Code:
fastboot flash boot recovery-clockwork-touch-5.8.2.4-endeavouru.img
Then I tried
Code:
fastboot reboot
which put me into recovery mode.
<EDIT> The instructions here have now been corrected to:
Code:
fastboot flash recovery recovery-clockwork-touch-5.8.2.4-endeavouru.img
</EDIT>
Choosing the reboot option from recovery just bounces me back into recovery mode but I understand from the instructions I should be able to boot into a working phone!
Has something gone wrong?
If I use the volume down + power button I can enter HBoot mode. From here I can select Fastboot. Connecting via USB to my computer seems to work fine, as I see Fastboot USB on my phone, and I when I execute this...
Code:
fastboot devices
I get something like this
Code:
List of devices attached
HTXXXXXXXXXX device
I am now unsure how to continue because I think something has gone wrong and I should have a working phone at this point.
Do I press ahead and try to install the Firmware package from here? Unless this lets me boot into a working phone (which I don’t believe it will), it still leaves me with the problem that for a One X, without a removable SD card I don’t know how to transfer and run the "Super Wipe" script, nor transfer and flash Android Revolution ROM via recovery.
Do I need to do something with
Code:
fastboot flash
?
Please help as she is threatening to dump me for destroying her 2-day-old phone.

It's
Code:
fastboot flash [B]recovery[/B] recovery-clockwork-touch-5.8.2.4-endeavouru.img
not boot..
Solution for you is to go into bootloader, flash recovery with the command i gave you and then reboot into recovery and install the rom..
After that everything should be ok and your phone will boot into ARHD without any problem.

delete please

anko184 said:
It's
Code:
fastboot flash [B]recovery[/B] recovery-clockwork-touch-5.8.2.4-endeavouru.img
not boot..
Solution for you is to go into bootloader, flash recovery with the command i gave you and then reboot into recovery and install the rom..
After that everything should be ok and your phone will boot into ARHD without any problem.
Click to expand...
Click to collapse
Thanks
It looks like the instructions I followed previously had an error then.
<EDIT> The instructions were incorrect, but have now been corrected </EDIT>
I will follow your instructions. But what about the RUU that is mentioned in the instructions? It is not clear how or when I should flash it. Presumably I flash the RUU before I do the ARHD flash... ???

mwhincup said:
Thanks
It looks like the instructions I followed previously had an error then.
I will follow your instructions. But what about the RUU that is mentioned in the instructions? It is not clear how or when I should flash it. Presumably I flash the RUU before I do the ARHD flash... ???
Click to expand...
Click to collapse
You don't need to flash any RUU or firmware unless your phone wasn't shipped with 1.26, which i don't think it was.
Just try flashing the recovery with the correct command and then the rom. If your phone doesn't boot after that then you may try the firmware but i'm sure you won't need it.

anko184 said:
You don't need to flash any RUU or firmware unless your phone wasn't shipped with 1.26, which i don't think it was.
Just try flashing the recovery with the correct command and then the rom. If your phone doesn't boot after that then you may try the firmware but i'm sure you won't need it.
Click to expand...
Click to collapse
So, I understand that you are telling me:
Flashing CWM recovery will rectify my current problem and restore my phone to a workable state.
Booted normally, I can copy the ARHD ROM to the internal SD (not sure what the location for this will be).
I then reboot into recovery and 'Install Zip from SD card'.
Click to expand...
Click to collapse
Is this correct?

mwhincup said:
So, I understand that you are telling me:
Is this correct?
Click to expand...
Click to collapse
Wait before you flash anything, if you don'talready have arhd on your internal sd you may be in trouble if you do superwipe
Sent from my HTC One X using XDA

mwhincup said:
So, I understand that you are telling me:
Is this correct?
Click to expand...
Click to collapse
Without trying to sound like a ****, if you don't understand what you are doing you should read more to understand the whole process before attempting it.

bagofcrap24 said:
Wait before you flash anything, if you don'talready have arhd on your internal sd you may be in trouble if you do superwipe
Click to expand...
Click to collapse
Good advice, I am sure. However my problem now is getting into a working phone so that I can transfer the ROM onto the internal SD.
Can't wait to get home and try it!

what you have done is replaced your boot sector with a recovery image, that is the reason why you cant boot your phone as normal so even flashing the recovery correctly will not allow your phone to boot up.
as your phone cannot boot up you cannot transfer any files to the internal memory of your phone in order to flash ARHD
at present there is a problem with the official version of ClockworkMod Recovery so i personally would reccommend using the interim version HERE
and flash with fastboot flash recovery r1-modaco-recovery-clockwork-touch-endeavoru.img
As you have [email protected]$ked your boot partition up you will also want to download THIS
this is an insecure boot image (thanks to paul from modaco) I have just extracted the part you will need from his package
with this you will need to be in fastboot again and type fastboot flash boot boot.img
obviously you will need to copy both of the files to the same directory as fastboot is on your PC in order to send them
by flashing the boot section with the insecure boot here it will allow your phone to boot up normally again, once it has booted normally you can then copy the ARHD and superwipe to your internal SD card
to access recovery
power off phone by holding power button for 10seconds
power on with power+voldown
select recovery from hboot screen with voldown then power to select
your phone will reboot and then you will be in recovery
do a nandroid backup incase anything goes wrong
then flash the superwipe script
then flash ARHD 1.2.2
all is good

animaleyes76 said:
Without trying to sound like a ****, if you don't understand what you are doing you should read more to understand the whole process before attempting it.
Click to expand...
Click to collapse
You are correct of course, however, there comes a point where the only way to learn is to actually do something. I have flashed numerous ROMS on my Galaxy S, and before doing this I have read numerous guides trying to better understand the procedures for HTC devices.
I have tried to follow what appeared to be a step-by-step guide, however, either there has been a malfunction, or it appears there may be two important bits of information missing from that guide:
Flashing CWM recovery leaves the phone in a state that it won't boot normally, and consequently...
The ARHD ROM should be loaded onto the internal SD at the very beginning of the procedure
Click to expand...
Click to collapse

Thanks all of you so much for your effort. It's much appreciated.
bagofcrap24 said:
what you have done is replaced your boot sector with a recovery image, that is the reason why you cant boot your phone as normal so even flashing the recovery correctly will not allow your phone to boot up.
Click to expand...
Click to collapse
@bagofcrap24 I may have misled you with a typo in the first post. (See my edit)
d'oh

edit : just read updated info
so what happens when you choose recovery and press power from the hboot screen
i'm understanding that when doing a normal reboot it just sends you straight into hboot?
power on with voldown
press voldown to select recovery
press power to select recovery
you should either see CWM or the stock recovery
again looking at what you have written, if you just do a normal reboot and its putting you straight into recovery then you probably have flashed recovery onto the boot partition

bagofcrap24 said:
edit : just read updated info
so what happens when you choose recovery and press power from the hboot screen
i'm understanding that when doing a normal reboot it just sends you straight into hboot?
power on with voldown
press voldown to select recovery
press power to select recovery
you should either see CWM or the stock recovery
again looking at what you have written, if you just do a normal reboot and its putting you straight into recovery then you probably have flashed recovery onto the boot partition
Click to expand...
Click to collapse
I'll get back to you with some definitive answers in 3 hours or so. Sorry, I'm at work now.

bagofcrap24 said:
so what happens when you choose recovery and press power from the hboot screen
Click to expand...
Click to collapse
power on with voldown
press voldown to select recovery
press power to select recovery
Click to expand...
Click to collapse
I get a circular yellow 'recycling' symbol, followed a few seconds later by a magenta triangle with an exclamation mark. (Is this the stock recovery?). Then the phone restarts and I end up back in the Clockworkmod recovery.
i'm understanding that when doing a normal reboot it just sends you straight into hboot?
Click to expand...
Click to collapse
No. A normal reboot (without holding the Vol down key) sends me straight to clockworkmod recovery.
I can get to HBoot with Vol down+Power on startup.

mwhincup said:
I get a circular yellow 'recycling' symbol, followed a few seconds later by a magenta triangle with an exclamation mark. (Is this the stock recovery?). Then the phone restarts and I end up back in the Clockworkmod recovery.
No. A normal reboot (without holding the Vol down key) sends me straight to clockworkmod recovery.
I can get to HBoot with Vol down+Power on startup.
Click to expand...
Click to collapse
Right this means you did mess up the boot and recovery partitions, the one where you have the exclamation mark is the stock recovery which means you didn't flash cwm to the recovery partition.
the fact that you get to recovery on a normal boot also suggests as I suspected that you have flashed recovery on to the boot partition, follow the instructions I put up earlier about flashing the boot.IMG and redo the recovery.IMG and you should be fine
Sent from my HTC One X using XDA

bagofcrap24 said:
what you have done is replaced your boot sector with a recovery image, that is the reason why you cant boot your phone as normal so even flashing the recovery correctly will not allow your phone to boot up.
as your phone cannot boot up you cannot transfer any files to the internal memory of your phone in order to flash ARHD
at present there is a problem with the official version of ClockworkMod Recovery so i personally would reccommend using the interim version HERE
and flash with fastboot flash recovery r1-modaco-recovery-clockwork-touch-endeavoru.img
As you have [email protected]$ked your boot partition up you will also want to download THIS
this is an insecure boot image (thanks to paul from modaco) I have just extracted the part you will need from his package
with this you will need to be in fastboot again and type fastboot flash boot boot.img
obviously you will need to copy both of the files to the same directory as fastboot is on your PC in order to send them
by flashing the boot section with the insecure boot here it will allow your phone to boot up normally again, once it has booted normally you can then copy the ARHD and superwipe to your internal SD card
to access recovery
power off phone by holding power button for 10seconds
power on with power+voldown
select recovery from hboot screen with voldown then power to select
your phone will reboot and then you will be in recovery
do a nandroid backup incase anything goes wrong
then flash the superwipe script
then flash ARHD 1.2.2
all is good
Click to expand...
Click to collapse
Your analysis is quite correct. All is indeed good! Thanks very much. The boot image worked as described. I will now transfer Superwipe and the ROM.

Make sure you do a nandroid backup first, it was lucky this time but if you mess up your system partition you may find yourself with no way of putting files on without unrooting and restoring the ruu
Sent from my HTC One X using XDA

bagofcrap24 said:
Make sure you do a nandroid backup first, it was lucky this time but if you mess up your system partition you may find yourself with no way of putting files on without unrooting and restoring the ruu
Sent from my HTC One X using XDA
Click to expand...
Click to collapse
Done!
Everything worked as you said it would.
I now have ARHD installed and running brilliantly.
Thanks again

mwhincup said:
Done!
Everything worked as you said it would.
I now have ARHD installed and running brilliantly.
Thanks again
Click to expand...
Click to collapse
Glad you fixed it and sorry for being a bit harsh earlier.. was having a bad day

Cannot access flashboot / recovery - RESOLVED

Hi,
I've looked through a lot of threads but can't match the symptoms to mine (this could be a lack of knowledge on my part) so any help is appreciated.
I've previously flashed ARHD a number of times successfully including a new boot image. I flashed 9.2 today with CD Tools Suite and this was fine. I later decided that I wanted to re-flash without the CD Suite Tools and did this by going into recovery and re-flashing the ARHD zip.
The update ran successfully (per CWM) but I can't boot into it. All I get to is the HTC One white screen with a beats audio logo beneath it. I also can't get the phone to reboot into flashboot / recovery so that I can do anything with it (I've tried holding the power button and either vol up or down but this just reboots the phone and it goes back to the white screen again).
I'm sure there is a way out of this. Could anyone please help me?
Many thanks.

Hi, you wrote,
I later decided that I wanted to re-flash without the CD Suite Tools and did this by going into recovery and re-flashing the ARHD zip.
Click to expand...
Click to collapse
Did you use fastboot to flash the correct boot.img file first? It's my understanding that anytime you flash a rom you must flash via fastboot the correct boot.img file for that rom followed by erasing cache before entering recovery and flashing the rom.

Didn't someone say holding volume up & power can brick your phone?
Fastboot is volume down & power.
Press them at the exact same time, keep them held till fastboot loads up (even if it does another reboot)
Sent from my HTC One X using Tapatalk 2

phase sdeyou
Bit Banger said:
Hi, you wrote,
Did you use fastboot to flash the correct boot.img file first? It's my understanding that anytime you flash a rom you must flash via fastboot the correct boot.img file for that rom followed by erasing cache before entering recovery and flashing the rom.
Click to expand...
Click to collapse
They both use the same boot image so no need to re-flash that.

chrisjcks said:
keep them held till fastboot loads up (even if it does another reboot)
Click to expand...
Click to collapse
This was the key for me. It rebooted a couple of times then went into fastboot.
Thank you very much!

Infinite Boot

Hey guys. Got quite the problem here. My Sprint Galaxy Nexus is in an infinite boot. It just stays on the boot animation. I've left it there, at various times, for as long as 90 minutes. It first started after trying to flash the Jellin' 4.1 ROM and continued when I tried three other ROMs (using ADB push to put the ROMs onto my device). I then decided to use Odin, which may have made things worse, as now I do not have any ClockworkMod Recovery. Or any recovery at all, actually.
The only way I can get any data on the phone, at least as far as I can tell, is through Download mode. The leaked Sprint recovery tools also fail as soon as they try to start pushing data to the phone. I do not see my phone on the ADB devices list in either Download mode or the Boot menu. I have also tried to push CWM to my phone using Odin, but that seemed to need to boot into the OS to finish, so that also failed.
If anyone has any suggestions here, I would be incredibly appreciative. I have exhausted my knowledge of flashing and un-bricking devices here. Perhaps there is a different image I should be flashing using Odin? Only the FD02 image in this thread actually completes a load in Odin. The other sits at the "SYSTEM" phase.

you should be able to get into fastboot by holding both volume buttons then holding power, but the fd02 .tar should install stock rom and recovery. perhaps try re-downloading? place the .tar in pda section and only have auto-reboot checked then begin the flash.

apocalyptic0n3 said:
Hey guys. Got quite the problem here. My Sprint Galaxy Nexus is in an infinite boot. It just stays on the boot animation. I've left it there, at various times, for as long as 90 minutes. It first started after trying to flash the Jellin' 4.1 ROM and continued when I tried three other ROMs (using ADB push to put the ROMs onto my device). I then decided to use Odin, which may have made things worse, as now I do not have any ClockworkMod Recovery. Or any recovery at all, actually.
The only way I can get any data on the phone, at least as far as I can tell, is through Download mode. The leaked Sprint recovery tools also fail as soon as they try to start pushing data to the phone. I do not see my phone on the ADB devices list in either Download mode or the Boot menu. I have also tried to push CWM to my phone using Odin, but that seemed to need to boot into the OS to finish, so that also failed.
If anyone has any suggestions here, I would be incredibly appreciative. I have exhausted my knowledge of flashing and un-bricking devices here. Perhaps there is a different image I should be flashing using Odin? Only the FD02 image in this thread actually completes a load in Odin. The other sits at the "SYSTEM" phase.
Click to expand...
Click to collapse
I'd try going completely back to stock using this guide: http://forum.xda-developers.com/showthread.php?t=1626895
If all is well, flash or boot a custom recovery, make a nandroid and then retry a custom ROM.

Petrovski80 said:
I'd try going completely back to stock using this guide: http://forum.xda-developers.com/showthread.php?t=1626895
If all is well, flash or boot a custom recovery, make a nandroid and then retry a custom ROM.
Click to expand...
Click to collapse
To the best of my knowledge their are no official Spring gNex images.

3rdstring said:
To the best of my knowledge their are no official Spring gNex images.
Click to expand...
Click to collapse
Oh yeah, you're right. That's the second time I forgot this.
How about the unofficial factory images WugFresh has packed?

v3rk said:
you should be able to get into fastboot by holding both volume buttons then holding power, but the fd02 .tar should install stock rom and recovery. perhaps try re-downloading? place the .tar in pda section and only have auto-reboot checked then begin the flash.
Click to expand...
Click to collapse
I have done it a dozen times now. It just hits that colorful boot animation and doesn't go any further.
Petrovski80 said:
Oh yeah, you're right. That's the second time I forgot this.
How about the unofficial factory images WugFresh has packed?
Click to expand...
Click to collapse
I have the images you refer to. Would I still follow the guide you provided with these img files?

apocalyptic0n3 said:
I have the images you refer to. Would I still follow the guide you provided with these img files?
Click to expand...
Click to collapse
Yes.

apocalyptic0n3 said:
I have done it a dozen times now. It just hits that colorful boot animation and doesn't go any further.
I have the images you refer to. Would I still follow the guide you provided with these img files?
Click to expand...
Click to collapse
I'm confused here. Can you boot into fastboot mode (turn off, then hold vol up and vol down, and press power)? If so, then you should need to mess around with Odin. Just download a toroplus CWM (or TWRP) recovery and flash it to your device using fastboot: fastboot flash recovery name-of-recovery.img. Then go into recovery, wipe /data and /cache, flash a stock kernel, and it should boot for you.

efrant said:
I'm confused here. Can you boot into fastboot mode (turn off, then hold vol up and vol down, and press power)? If so, then you should need to mess around with Odin. Just download a toroplus CWM (or TWRP) recovery and flash it to your device using fastboot: fastboot flash recovery name-of-recovery.img. Then go into recovery, wipe /data and /cache, flash a stock kernel, and it should boot for you.
Click to expand...
Click to collapse
I wasn't aware you could use fastboot like that. But I did. And I managed to get ClockworkMod reinstalled and used that to wipe all my data and cache, as you suggested, and flash a new ROM. Worked like a charm. Thanks for all the help.

Stock recovery "vanished"

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.

Recovery gone / corrupted.

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

Wrong section

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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