Database Info

Assistance with Flashing roms please.

My boot loader and phone is rooted.
AT&T Htc one X
I have tried to flash a couple roms + the boot.img but the device pauses at HTC splash screen (I DID clear caches)
but its constant and I have to go into Fastboot-Usb and reinstall the RUU in order to try again.
Does anyone have any ideas?

viprk24 said:
My boot loader and phone is rooted.
AT&T Htc one X
I have tried to flash a couple roms + the boot.img but the device pauses at HTC splash screen (I DID clear caches)
but its constant and I have to go into Fastboot-Usb and reinstall the RUU in order to try again.
Does anyone have any ideas?
Click to expand...
Click to collapse
why don't you start by reading this http://forum.xda-developers.com/showthread.php?t=1957193
If you have ruu'ed you have to root again and unlock your bootloader again.
What recovery did you install ?

My bootloader is unlocked and my phone is rooted*
And I used TWRP or what ever its called. I can root fine and ez from it Trying to get Viperxl

viprk24 said:
My bootloader is unlocked and my phone is rooted*
And I used TWRP or what ever its called. I can root fine and ez from it Trying to get Viperxl
Click to expand...
Click to collapse
did you flash a recovery yet and if so which one ? if you want help you need to give us some details ?
What rom did you try to flash ? How did you go about it ?

Thank the android gods it wasn't an international ROM.
Did you flash superuser or supersu. We will need a little more information in the steps you've taken. Can you make a list of the steps for us?
The link crappyvate sent is a great tool for help.
Sent from my One X using xda premium

viprk24 said:
My bootloader is unlocked and my phone is rooted*
And I used TWRP or what ever its called. I can root fine and ez from it Trying to get Viperxl
Click to expand...
Click to collapse
Crappyvate said:
did you flash a recovery yet and if so which one ? if you want help you need to give us some details ?
What rom did you try to flash ? How did you go about it ?
Click to expand...
Click to collapse
apparently he did and some did not read the information

I have flashed TWRP recovery or what ever I have installed Supersu successfuly and full root. I restarted booted into recovery now and wiped system cleared cache now I'm going to attempt to flash it one more time.

CheesyNutz said:
apparently he did and some did not read the information
Click to expand...
Click to collapse
surprise...that would be a first
---------- Post added at 11:07 PM ---------- Previous post was at 11:05 PM ----------
subarudroid said:
Thank the android gods it wasn't an international ROM.
Did you flash superuser or supersu. We will need a little more information in the steps you've taken. Can you make a list of the steps for us?
The link crappyvate sent is a great tool for help.
Sent from my One X using xda premium
Click to expand...
Click to collapse
don't think so since apparently he still gets the htc splash screen but need more info.

viprk24 said:
I have flashed TWRP recovery or what ever I have installed Supersu successfuly and full root. I restarted booted into recovery now and wiped system cleared cache now I'm going to attempt to flash it one more time.
Click to expand...
Click to collapse
what exactly is it doing im not understanding is it freezing ? just not installing what error code is it giving

Are you flashing the boot image for your ROM in adb?
Sent from my One X using xda premium

viprk24 said:
I have flashed TWRP recovery or what ever I have installed Supersu successfuly and full root. I restarted booted into recovery now and wiped system cleared cache now I'm going to attempt to flash it one more time.
Click to expand...
Click to collapse
ok. i'm not gonna beg if you want help I need DETAILS not vague s***t like "TWRP or whatever".. So evidently you can boot into recovery with no problem. What rom are you trying to flash ? You need to extract the boot.img from the rom.zip and flash that in fastboot and then flash the rom.zip in recovery.
If you're not booting it's most likely because your phone is not finding a kernel (boot.img)
So more details or more reading
Good luck to you

Crappyvate said:
ok. i'm not gonna beg if you want help I need DETAILS not vague s***t like "TWRP or whatever".. So evidently you can boot into recovery with no problem. What rom are you trying to flash ? You need to extract the boot.img from the rom.zip and flash that in fastboot and then flash the rom.zip in recovery.
If you're not booting it's most likely because your phone is not finding a kernel (boot.img)
So more details or more reading
Good luck to you
Click to expand...
Click to collapse
from what i can make out
hes flashed the boot.img
installed twrp
superSU
but with no details on what ERROR its giving we as a help teams are FUBARD

CheesyNutz said:
from what i can make out
hes flashed the boot.img
installed twrp
superSU
but with no details on what ERROR its giving we as a help teams are FUBARD
Click to expand...
Click to collapse
not sure the boot.img was flashed the right way...or in the right place

Calm down trolls I simply said
I flashed TRWP
Flashed Supersu
Flashboot oem unlock (Successful)
Relaunched back into bootloader
I fastboot boot.img
Then to Recovery where I Cleared cache and wiped System.
I then reflashed recovery because i wiped system.
I relaunched back into recovery and flashed rom

viprk24 said:
Calm down trolls I simply said
I flashed TRWP
Flashed Supersu
Flashboot oem unlock (Successful)
Relaunched back into bootloader
I fastboot boot.img
Then to Recovery where I Cleared cache and wiped System.
I then reflashed recovery because i wiped system.
I relaunched back into recovery and flashed rom
Click to expand...
Click to collapse
Its not a good idea to ask for help and then flame. Honestly what was hard about posting this the first time? I thought maybe English wasn't your language or something. How could you flash a recovery before unlocking???
If you wiped everything, you should reflash bootimage in adb. Then flash your ROM. Please be nice.
Sent from my One X using xda premium

viprk24 said:
Calm down trolls I simply said
I flashed TRWP
Flashed Supersu
Flashboot oem unlock (Successful)
Relaunched back into bootloader
I fastboot boot.img
Then to Recovery where I Cleared cache and wiped System.
I then reflashed recovery because i wiped system.
I relaunched back into recovery and flashed rom
Click to expand...
Click to collapse
yea bash the folks attempting to help you ... thats like biting the hand that feeds you .. im out have fun

CheesyNutz said:
yea bash the folks attempting to help you ... thats like biting the hand that feeds you .. im out have fun
Click to expand...
Click to collapse
likewise. Over and out.

[SCH-I705] Help can I unbrick my tablet

I have a Galaxy Tab 2 VZW and was trying to install the ClearRom, but I guess I forgot to unlock bootloader, so now everytime I turn the tab on I get message statitng " System Software not authorized by Verizon Wireless has been found on your phone."
I have a backup from before I tried installing the ROM but don't know what to do with it
Any help will be appreciated

melog69 said:
I have a Galaxy Tab 2 VZW and was trying to install the ClearRom, but I guess I forgot to unlock bootloader, so now everytime I turn the tab on I get message statitng " System Software not authorized by Verizon Wireless has been found on your phone."
I have a backup from before I tried installing the ROM but don't know what to do with it
Any help will be appreciated
Click to expand...
Click to collapse
HOw did you make the backup? CWM? If so, then install CMW recovery and do a restore.

DigitalMD said:
HOw did you make the backup? CWM? If so, then install CMW recovery and do a restore.
Click to expand...
Click to collapse
I tried getting into recovery mode, but I get the following screen everytime, I think I need the Stock Firmware to flash with ODIN but I don't know where to find it.
<iframe src="https://skydrive.live.com/embed?cid=47A1A726F16BDCFD&resid=47A1A726F16BDCFD%212570&authkey=AE3MPZ8PewFeQos" width="180" height="320" frameborder="0" scrolling="no"></iframe>

Always, ALWAYS, follow directions exactly how they're laid out.
What you need to do is download the aboot.img to your sd card. Reboot into recovery, ADB Shell into your device (you may need linux for this part as Windows doesn't recognize the device in recovery mode). Once you ADB into recovery, make sure you are root (noted by # instead of $).
Then:
dd if=/sdcard/aboot.img of=/dev/block/mmcblk0p5
reboot download
This should unlock you bootloader so you can get by verizons pesky warning.
We can't see the picture you tried attaching.

MrHyde03 said:
Always, ALWAYS, follow directions exactly how they're laid out.
What you need to do is download the aboot.img to your sd card. Reboot into recovery, ADB Shell into your device (you may need linux for this part as Windows doesn't recognize the device in recovery mode). Once you ADB into recovery, make sure you are root (noted by # instead of $).
Then:
dd if=/sdcard/aboot.img of=/dev/block/mmcblk0p5
reboot download
This should unlock you bootloader so you can get by verizons pesky warning.
We can't see the picture you tried attaching.
Click to expand...
Click to collapse
I cannot get to recovery mode, only download mode, also ClearRom did not specify that the bootloader, that is why I did not even bother

melog69 said:
I cannot get to recovery mode, only download mode, also ClearRom did not specify that the bootloader, that is why I did not even bother
Click to expand...
Click to collapse
You'll more than likely have to send it back. There has been no official release of stock firmware, unfortunately (none that I have found at least). In the root thread there are steps 1 - 3 for a reason. 1 - Root, 2 - Unlock and Recovery, 3 - Custom ROM. Always follow directions.

MrHyde03 said:
You'll more than likely have to send it back. There has been no official release of stock firmware, unfortunately (none that I have found at least). In the root thread there are steps 1 - 3 for a reason. 1 - Root, 2 - Unlock and Recovery, 3 - Custom ROM. Always follow directions.
Click to expand...
Click to collapse
Well, thanks guys now I know what to do when it's fixed

melog69 said:
Well, thanks guys now I know what to do when it's fixed
Click to expand...
Click to collapse
Maybe try a stock 3100 rom? If the hardware is the same should work, just need to set APN etc.Then reroot, install recovery, install cuztom rom.
---------- Post added at 04:04 PM ---------- Previous post was at 03:54 PM ----------
acefsw said:
Maybe try a stock 3100 rom? If the hardware is the same should work, just need to set APN etc.Then reroot, install recovery, install cuztom rom.
Click to expand...
Click to collapse
Actually, according to here http://forum.xda-developers.com/showthread.php?t=1885558 you just need download mode to install the stock image and then follow the rest of the steps.

acefsw said:
Maybe try a stock 3100 rom? If the hardware is the same should work, just need to set APN etc.Then reroot, install recovery, install cuztom rom.
Click to expand...
Click to collapse
DO NOT INSTALL A P3100 ROM. It's not the same hardware (not really even close), so that would only make it worse.

imnuts said:
DO NOT INSTALL A P3100 ROM. It's not the same hardware (not really even close), so that would only make it worse.
Click to expand...
Click to collapse
I edited the post, read the link, it is for his device

imnuts is correct. These devices are extremely different and really does need it's own subforum so people don't keep getting confused. The i705 is closest to the i535 (s3), nearly identical actually.

MrHyde03 said:
imnuts is correct. These devices are extremely different and really does need it's own subforum so people don't keep getting confused. The i705 is closest to the i535 (s3), nearly identical actually.
Click to expand...
Click to collapse
Then wouldn't it be easier to flash an S Rom?

melog69 said:
Then wouldn't it be easier to flash an S Rom?
Click to expand...
Click to collapse
It still wouldn't work. boot, recovery, and system for the s3 are designed for the s3. The hardware is the same, but the software has it's differences. What differences, though, is beyond me.

I have the same issue, this is the first time I've ever "Bricked" a device. Thought I followed the instructions correctly, I can successfully flash recovery.tar.md5 on Mr.Hydes thread http://forum.xda-developers.com/showthread.php?t=1885558 but when it goes to reboot it gives me the Yellow ExclaTriangle "System software not authorized by Verizion , yadi, yadi ya da".
I can get into Download mode but NO RECOVERY, Tried flashing (With ODIN) CWM 6.0.1.9 located here http://forum.xda-developers.com/showthread.php?t=2044630 but ERROR with NAND WRITE FAIL.
Does anyone have a PIT file? I want give Heimdall a stab at it before I go throw it through Verizon's front window. Appreciate any help, like I said I understand the importance of following Instructions, I've done plenty of Android devices before including The Original GTab7, I dont mind cracking it open either, I've already had it apart to disconnect the battery but that did no help either, BTW it's really easy to open up.

Sounds like you didn't flash the unsecure bootloader
Sent from my SCH-I535 using XDA Premium HD app

MrHyde03 said:
Sounds like you didn't flash the unsecure bootloader
Sent from my SCH-I535 using XDA Premium HD app
Click to expand...
Click to collapse
I couldn't boot into Recovery to Flash, I'm Trying to flash now using Odin but get "Secure Check Fail". Any Ideas?

The bootloader needs to be flashed before the recovery using the dd command. Its listed first under step 2, before the recovery.
Sent from my SCH-I535 using XDA Premium HD app

MrHyde03 said:
The bootloader needs to be flashed before the recovery using the dd command. Its listed first under step 2, before the recovery.
Sent from my SCH-I535 using XDA Premium HD app
Click to expand...
Click to collapse
Yeah that's where I'm confused, I've had it rooted and unlocked since November following your original Development, I was on G3 not J1. Followed the Instructions and then crap.

Unlocked since Nov and it just now crapped? That doesn't make any sense.. When you boot into download mode right now, what orientation is the screen? Portrait or landscape? Landscape would mean a correctly flashed aboot.img (boot loader)
Sent from my SCH-I535 using XDA Premium HD app

iwSachin plain
MrHyde03 said:
Unlocked since Nov and it just now crapped? That doesn't make any sense.. When you boot into download mode right now, what orientation is the screen? Portrait or landscape? Landscape would mean a correctly flashed about.img (boot loader)
Sent from my SCH-I535 using XDA Premium HD app
Click to expand...
Click to collapse
I followed this thread of yours in the beginning of NOV. http://forum.xda-developers.com/showthread.php?t=1942674 I was rooted and unsecured bootloader, had CWM and SuperUser, but there weren't any ROMS out yet. Everything was fine until I went to install CleanRom the other day.
Portrait Orientation in Download mode.

[Q] Flashed wrong Franco Kernel on Nexus 5

I tried flashing the Franco kernel for N4 on my N5 by mistake...now my phone gets stuck on the black reboot screen.
How can I fix this?
Using TWRP.

woowhee said:
I tried flashing the Franco kernel for N4 on my N5 by mistake...now my phone gets stuck on the black reboot screen.
How can I fix this?
Using TWRP.
Click to expand...
Click to collapse
you might not be able to fix it. flashing a kernel meant for a different device can vary easily brick any device.
1. if you can get into your recovery, try flashing the right kernel, even an older version if possible.
2. if that doesnt work, flaah the factory img via fastboot and hope for the best.
3. if still no luck, theres a nexus 4 thread in their general section meant just for accidents like this, find it and try what it says.

simms22 said:
you might not be able to fix it. flashing a kernel meant for a different device can vary easily brick any device.
1. if you can get into your recovery, try flashing the right kernel, even an older version if possible.
2. if that doesnt work, flaah the factory img via fastboot and hope for the best.
3. if still no luck, theres a nexus 4 thread in their general section meant just for accidents like this, find it and try what it says.
Click to expand...
Click to collapse
Is there a way to get the factory img onto the phone via TWRP?

Does the bootloader still work?

BirchBarlow said:
Does the bootloader still work?
Click to expand...
Click to collapse
Yes, I'm able to get into TWRP/recovery mode.

woowhee said:
Yes, I'm able to get into TWRP/recovery mode.
Click to expand...
Click to collapse
Then, you are fine, friend:victory:, just do what the guy upstairs said. (simms22)
wipe system, caches, Flash another Rom/kernel for N5

Fastboot flash /boot boot.img
Sent from my Nexus 5 using XDA Premium 4 mobile app

woowhee said:
Yes, I'm able to get into TWRP/recovery mode.
Click to expand...
Click to collapse
Then what's the problem?

He's safe. He just needs to flash using fastboot.
This is the reason why Nexus devices are awesome.:angel:

woowhee said:
I tried flashing the Franco kernel for N4 on my N5 by mistake...now my phone gets stuck on the black reboot screen.
How can I fix this?
Using TWRP.
Click to expand...
Click to collapse
You can solve flashing a wrong kernel, but don`t ever flash a N4 bootloader or you are definately screwed. Get rid of anything N4 related from your fastboot folder bro..

The point in the bootloader is for this very thing. Just plug it into your pc and fastboot it
Unless you have a kernel/ rom zip or backup already in the memory then just use recovery
Sent from my Nexus 5 using Tapatalk

gee2012 said:
You can solve flashing a wrong kernel, but don`t ever flash a N4 bootloader or you are definately screwed. Get rid of anything N4 related from your fastboot folder bro..
Click to expand...
Click to collapse
Thank you, everyone. Disaster aborted.

[Q] OTA bootloader update when rooted?

Hi guys,
I run rooted unlocked Nexus 5 with CM11. I wanted to update the ROM but it failed - I read a bit and found out that it is due to old bootloader version. I would like to update it but I'm not a friend with ADB and stuff.... It would be great to use the most easiest way. I got OTA update notification but have no idea what it does - will it unroot the phone? will I lose CM11 ROM? Just trying to figure out what backups and steps shall I do to update my ROM. How shall I continue from here?
Thanks a bunch!

devcager said:
Hi guys,
I run rooted unlocked Nexus 5 with CM11. I wanted to update the ROM but it failed - I read a bit and found out that it is due to old bootloader version. I would like to update it but I'm not a friend with ADB and stuff.... It would be great to use the most easiest way. I got OTA update notification but have no idea what it does - will it unroot the phone? will I lose CM11 ROM? Just trying to figure out what backups and steps shall I do to update my ROM. How shall I continue from here?
Thanks a bunch!
Click to expand...
Click to collapse
Attempting to take the OTA will fail.
Download the factory image and extract bootloader-hammerhead-hhz11k.img
Boot your device into bootloader:
fastboot flash bootloader bootloader-hammerhead-hhz11k.img
fastboot reboot-bootloader

You have a custom recovery installed, right? Flash the bootloader zip via recovery. However, you need to get familiar with adb/fastboot as you're gonna need them if you ever find yourself in a tight situation to fix your device.
Open the "must read" thread linked in my signature and find the thread which has all the info about adb and fastboot.

vin4yak said:
You have a custom recovery installed, right? Flash the bootloader zip via recovery. However, you need to get familiar with adb/fastboot as you're gonna need them if you ever find yourself in a tight situation to fix your device.
Open the "must read" thread linked in my signature and find the thread which has all the info about adb and fastboot.
Click to expand...
Click to collapse
Thank you! I get it about ADB, I had to solve one my problem in the past via ADB. Anyway, I just need to find the 4.4.4 bootloader in ZIP (or probalby .img will work too?) and flash it? That's it? Does it wipe my phone or something?

You just need to flash the IMG via fastboot, no wiping required!

EddyOS said:
You just need to flash the IMG via fastboot, no wiping required!
Click to expand...
Click to collapse
Alright. One more thing. Is it possible to convert the IMG file I have into zip to be able to flash it in TWRP?
EDIT: I found that Nexus Toolbox for my 5 has the option to flash the bootloader image so I will try this variant.

devcager said:
Alright. One more thing. Is it possible to convert the IMG file I have into zip to be able to flash it in TWRP?
EDIT: I found that Nexus Toolbox for my 5 has the option to flash the bootloader image so I will try this variant.
Click to expand...
Click to collapse
You don't need to. Just boot into fastboot, connect to PC, fastboot flash bootloader name_of_file.img, reboot, done

it's easy you must become familiar with fastboot and add the second you aren't it will come back to haunt you
Sent from my Nexus 5 using Tapatalk

devcager said:
Alright. One more thing. Is it possible to convert the IMG file I have into zip to be able to flash it in TWRP?
EDIT: I found that Nexus Toolbox for my 5 has the option to flash the bootloader image so I will try this variant.
Click to expand...
Click to collapse
so you learned nothing. awesome.

Zepius said:
so you learned nothing. awesome.
Click to expand...
Click to collapse
Brick waiting to happen.
Add to ignore list
Sent from my Nexus 5 using Tapatalk < Yes, I want you to know that I'm using a mobile client

rootSU said:
Brick waiting to happen.
Add to ignore list
Sent from my Nexus 5 using Tapatalk < Yes, I want you to know that I'm using a mobile client
Click to expand...
Click to collapse
I'm still waiting for someone to make a thread saying their device is "bricked because flashed fastboot to adb using bootloader while in recovery with x toolkit"

[5.0] Nexus 5 Refuses To Flash OTA or Different ROM's

Hello,
So I just discovered this while trying to flash the 5.0.1 OTA from 5.0. I'm rooted on LRX21O via the Nexus Root Toolkit 1.9.9 (which is what I've always used in the past with no issues).
1 Tried flashing the OTA via Google notification push. It reboot, and no changes occur.
2 Fine - I try to use the Root Toolkit again. Boots into bootloader, appears to flash the radio and other necessary components. Reboots - no changes occur.
3 I then tried to just download the 5.0.1 package and flash everything manually via adb. Everything appears to go smoothly, and upon bootup Android updates all of its apps - still nothing. I appear to be completely stuck on LRX21O without any way to reflash stock or OTA's.
Anyone have any clue why this is occurring or have heard of such an issue before?
Thanks all.

Just flash factory images. With fastboot/flash-all script.
https://developers.google.com/android/nexus/images

You flash these in fastboot not adb
Sent from my Nexus 5 using Tapatalk

Did you not understand? I did flash in boot loader USING adb on my computer. All that bat script does is just automate the flashing of each image for you (system, radio, etc) so this is not helpful. I know how to flash, but flashing seems to have no effect despite successfully flashing via manually installing or just using the script

Sane116 said:
Did you not understand? I did flash in boot loader USING adb on my computer.
Click to expand...
Click to collapse
You use fastboot in bootloader, not adb.

I'm not the one asking for help. Anyways, carry on.

Your device's /system partition is tampered (you say you rooted it) and thus the OTA fails. Flash the 5.0 factory image (LRX21O) WITHOUT rooting/flashing kernels/whatever and then use the OTA zip to do adb sideload in the stock recovery to update to 5.0.1 LRX22C.

Manually use fastboot commands to flash system.img and boot.img of the full 5.0.1 factory image (not script). post the output please

I'm not the one asking for help. Anyways, carry on.
Click to expand...
Click to collapse
Sorry about that - didn't mean to come across snippy
It worked this time with fastboot. For future reference can this be done the same way with the OTA update zip instead of reflashing the entire image?

Sane116 said:
Sorry about that - didn't mean to come across snippy
It worked this time with fastboot. For future reference can this be done the same way with the OTA update zip instead of reflashing the entire image?
Click to expand...
Click to collapse
No, but if your phone is setup correctly you can sideload the ota zip in the stock recovery
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
No, but if your phone is setup correctly you can sideload the ota zip in the stock recovery
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Would you mind explaining this? I've used sideload in cwm and twrp before but I'm unsure of how to operate anything within stock recovery. adb won't even connect while in recovery. I would like to just remain on unrooted stock until xposed eventually get's developed for ART and flash zips that way.

Sane116 said:
Would you mind explaining this? I've used sideload in cwm and twrp before but I'm unsure of how to operate anything within stock recovery. adb won't even connect while in recovery. I would like to just remain on unrooted stock until xposed eventually get's developed for ART and flash zips that way.
Click to expand...
Click to collapse
Sideloading in the stock recovery works much the same as in a custom recovery. Boot into the stock recovery and there is an option to sideload. Then on your pc in a command window you type adb sideload update.zip. or whatever the file name is that you're trying to sideload. Obviously, if you can't get adb to recognize your device that's a problem. But that's a separate driver issue.
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
Sideloading in the stock recovery works much the same as in a custom recovery. Boot into the stock recovery and there is an option to sideload. Then on your pc in a command window you type adb sideload update.zip. or whatever the file name is that you're trying to sideload. Obviously, if you can't get adb to recognize your device that's a problem. But that's a separate driver issue.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
How can this be possible though without a custom recovery with the sideload feature? Stock recovery is essentially unusable as it just displays a picture of a dead android on a black screen.
Perhaps we're on different pages, or am I just confused still?

sideloading an OTA update from stock recovery
Hello, to make it work you will need to use the Google USB drivers you downloaded when you go into stock recovery then press the power button and volume up once then you will see a menu option with the "install update from adb option select this and plug in your phone to the computer. After this is done you will need to go to device manager and install the USB drivers from the Google USB drivers you downloaded. at this point after that is done you then go into the folder that has ADB installed and use adb sideload filename.zip
at this point your phone will accept the ota update package and you wont lose any data, I hope this helps..
-cs

Sane116 said:
How can this be possible though without a custom recovery with the sideload feature? Stock recovery is essentially unusable as it just displays a picture of a dead android on a black screen.
Perhaps we're on different pages, or am I just confused still?
Click to expand...
Click to collapse
When you get the dead android you need to press vol up and then press and release power. That'll get you into the stock recovery. It's stupid and I don't know why they made it that way
Sent from my Nexus 9 using XDA Free mobile app

thanks all, can't believe i never knew that volumeup+power got me into stock recovery options.
new issue: sideload works all well and perfect, but how can I bypass the "signature verification failed" flag that kicks me from the zip install every time?

Sane116 said:
thanks all, can't believe i never knew that volumeup+power got me into stock recovery options.
new issue: sideload works all well and perfect, but how can I bypass the "signature verification failed" flag that kicks me from the zip install every time?
Click to expand...
Click to collapse
Well you can't. The limitation of the stock recovery is you can only flash files signed by Google. That's why you need a custom recovery to flash most files
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
Well you can't. The limitation of the stock recovery is you can only flash files signed by Google. That's why you need a custom recovery to flash most files
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
So can I just flash twrp with fastboot and go about that method? I believe it can bypass the signature. I am unlocked without root currently.

Sane116 said:
So can I just flash twrp with fastboot and go about that method? I believe it can bypass the signature. I am unlocked without root currently.
Click to expand...
Click to collapse
If you're trying to flash the update.zip to 5.0.1 you need to do that in the stock recovery. It will not work in twrp or cwm. I'm not sure what you're trying to do right now
Sent from my Nexus 9 using XDA Free mobile app

my apologies.
so originally i wanted to just flash the OTA. ended up performing a fresh install and un-rooted. but there's a few unsigned zips i like to have installed.
So I think I'm going to re-root, flash twrp, install my zips, and leave it at that. i'll just flash stock recovery whenever I need the OTA which should be quick now that I know what to do.
hope that sounds correct. thanks for all the help!