Database Info

Google Nexus 5 Flashing

Hi Guys.
I am a bit out of date. Haven't done something here for about 2 years, and can't even remeber how I did my last flash of the rooted stock rom on my device.
Is there any way I can see, if my phone is already prepared for any flash method? Or are there no more different options out there these days?
If it doesn't matter, which one you would advise me to use? I am interessted to flash the CM (hammerheadcaf).
Thank you for any help. Cheers

s0urce said:
Hi Guys.
I am a bit out of date. Haven't done something here for about 2 years, and can't even remeber how I did my last flash of the rooted stock rom on my device.
Is there any way I can see, if my phone is already prepared for any flash method? Or are there no more different options out there these days?
If it doesn't matter, which one you would advise me to use? I am interessted to flash the CM (hammerheadcaf).
Thank you for any help. Cheers
Click to expand...
Click to collapse
Fist the bootloader must be unlocked.Then you need to flash a custom recovery ("normal" TWRP for stock/aosp based roms or CAF TWRP for CM 12.1 CAF).
Also check which bootloader version is required for the rom you are planning to flash.
Of course this is a quick overview of the requirements, but you will find plenty of detailed information about every step here in the Nexus5 forum. Good luck!

Pretoriano80 said:
Fist the bootloader must be unlocked.Then you need to flash a custom recovery ("normal" TWRP for stock/aosp based roms or CAF TWRP for CM 12.1 CAF).
Also check which bootloader version is required for the rom you are planning to flash.
Of course this is a quick overview of the requirements, but you will find plenty of detailed information about every step here in the Nexus5 forum. Good luck!
Click to expand...
Click to collapse
Hi, thank you for ur answer. My problem is not to find details about flashing a specific ROM. My question was more about, how to find out, which kind of flashing I have done the last time on my phone? So I would know, if I can skip a big part of the tutorials or if I need to do everything from scratch.

Well, those steps are meant for flashing in general not only a specific rom and from my point of you it doesn't matter how you used to flash in the past (but maybe i'm missing something here or didn't understood your question).
Basically flashing the Nexus5 two years ago was same as now (but might different than other devices) but most likely you will need a newer revision of your recovery, a bootloader upgrade (and if necessary unlock your bootloader if you locked it in the past). So just check this information against your current configuration and you will find out if you can skip a step or not (and also different roms could come with different requirements, like the CAF buils).

Any updates on TWRP?

Seems like development in general has really dropped off over the past year or two. Used to be TWRP would be out within 1-2 weeks, now it's almost 3 months and nothing. Makes me sad to see us going the direction of accepting factory builds

in_dmand said:
Seems like development in general has really dropped off over the past year or two. Used to be TWRP would be out within 1-2 weeks, now it's almost 3 months and nothing. Makes me sad to see us going the direction of accepting factory builds
Click to expand...
Click to collapse
I was just thinking this the other day. The whole scene of Rooting and flashing ROMs seems to be coming to a dead end. Kinda sucks, I've always enjoyed tweaking my phone in my spare time..

in_dmand said:
Seems like development in general has really dropped off over the past year or two. Used to be TWRP would be out within 1-2 weeks, now it's almost 3 months and nothing. Makes me sad to see us going the direction of accepting factory builds
Click to expand...
Click to collapse
Used to take 1-2 weeks when things were simple and easier.
Your comment about factory builds doesn't make sense considering you don't need TWRP to flash custom ROMs etc

Mackay53 said:
Used to take 1-2 weeks when things were simple and easier.
Your comment about factory builds doesn't make sense considering you don't need TWRP to flash custom ROMs etc
Click to expand...
Click to collapse
True, but it does seem like it has greatly hindered rom development... It wasn't until very recently there were any roms even available.

in_dmand said:
True, but it does seem like it has greatly hindered rom development... It wasn't until very recently there were any roms even available.
Click to expand...
Click to collapse
More cheaper phones will have a higher user base so more development activity.
I think Pixels already has solid software so not much to add and the high price point will hold it back a little

in_dmand said:
Seems like development in general has really dropped off over the past year or two. Used to be TWRP would be out within 1-2 weeks, now it's almost 3 months and nothing. Makes me sad to see us going the direction of accepting factory builds
Click to expand...
Click to collapse
https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html

Root-Maniac said:
I was just thinking this the other day. The whole scene of Rooting and flashing ROMs seems to be coming to a dead end. Kinda sucks, I've always enjoyed tweaking my phone in my spare time..
Click to expand...
Click to collapse
No we all just have to move on to next generation rooting an modding. Magisk can be flashed, or the Manager App is used to patch the boot.img manually and flash it afterwards. GSIs ROMs can be flashed via fastboot from fastboot mode as well. So in my opinion it is fastboot flashing an GSI.img, Custom (optionally Magisk patched) boot, or Stock Magisk patched boot. That's it. It's even more, as it's back to the roots of adb and fastboot. TWRP has been there on U12+ for as long as the device exists, bit I never used it, as I switched to GSIs instead, and of on Stock the Magisk ROMs of LeeDrOiD and Team Viper could be easily installed through Magisk Manager. We should all have taken a look at phhussons work much earlier to accommodate to the things that got moving by Googles change in architecture when they introduced treble. We've only been to lazy, and many of today's users on this board, hardly know anything in-depth about adb and fastboot, but only scratch the three or four superficial standard commands. Technical affinity is more in demand again, and our good old adaptability.
Sent from my Pixel 4 XL using XDA Labs

uicnren said:
https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html
Click to expand...
Click to collapse
Oh wow, thanks for posting that! I certainly don't expect dees Troy to handle that difficult of a problem by himself with his wife pregnant and everything. Thanks again

5m4r7ph0n36uru said:
No we all just have to move on to next generation rooting an modding. Magisk can be flashed, or the Manager App is used to patch the boot.img manually and flash it afterwards. GSIs ROMs can be flashed via fastboot from fastboot mode as well. So in my opinion it is fastboot flashing an GSI.img, Custom (optionally Magisk patched) boot, or Stock Magisk patched boot. That's it. It's even more, as it's back to the roots of adb and fastboot. TWRP has been there on U12+ for as long as the device exists, bit I never used it, as I switched to GSIs instead, and of on Stock the Magisk ROMs of LeeDrOiD and Team Viper could be easily installed through Magisk Manager. We should all have taken a look at phhussons work much earlier to accommodate to the things that got moving by Googles change in architecture when they introduced treble. We've only been to lazy, and many of today's users on this board, hardly know anything in-depth about adb and fastboot, but only scratch the three or four superficial standard commands. Technical affinity is more in demand again, and our good old adaptability.
Click to expand...
Click to collapse
I agree on most points of you. GSIs are wonderful especially for phones at release start when there are no custom roms available yet.
And luckily device specific custom roms can be flashed over fastboot, too.
But for one reason i want a twrp for our device:
I find data backups with twrp much more easier as without. At least on my pixel 4 xl i miss a twrp somehow because Titanium Backup doesn't work on the gsi which i'm using.
I must create all my app folders again on my phone when i update it and backup all my stuff manually on my pc in extra folders and files.
I could spare me all that with twrp.
(I know there is the Google Cloud too as possibility but i refuse to use it)

dhacke said:
I agree on most points of you. GSIs are wonderful especially for phones at release start when there are no custom roms available yet.
And luckily device specific custom roms can be flashed over fastboot, too.
But for one reason i want a twrp for our device:
I find data backups with twrp much more easier as without. At least on my pixel 4 xl i miss a twrp somehow because Titanium Backup doesn't work on the gsi which i'm using.
I must create all my app folders again on my phone when i update it and backup all my stuff manually on my pc in extra folders and files.
I could spare me all that with twrp.
(I know there is the Google Cloud too as possibility but i refuse to use it)
Click to expand...
Click to collapse
Why do you refuse to use Google cloud

ceelos218 said:
Why do you refuse to use Google cloud
Click to expand...
Click to collapse
Because i don't want to feed Big G with my data.
And GSIs give me the possibilty to use my pixel without all the Gapps and the Google Play Service. That's a reason too why i like GSIs.

dhacke said:
Because i don't want to feed Big G with my data.
And GSIs give me the possibilty to use my pixel without all the Gapps and the Google Play Service. That's a reason too why i like GSIs.
Click to expand...
Click to collapse
Privacy is an illusion unless you go completely offline.

zetsumeikuro said:
Privacy is an illusion unless you go completely offline.
Click to expand...
Click to collapse
So we should stop fighting for this? Sry but that isn't a option for me.
Yes complete privacy isn't possible mostly but there are ways to improve it. With privacy friendly services, FOSS Apps such as AfWall, AdAway and Ad and Tracking Blockers in Browsers, Linux instead if Windows and no use of Gapps etc.
I know that my comment is probably off topic so sry.

dhacke said:
So we should stop fighting for this? Sry but that isn't a option for me.
Yes complete privacy isn't possible mostly but there are ways to improve it. With privacy friendly services, FOSS Apps such as AfWall, AdAway and Ad and Tracking Blockers in Browsers, Linux instead if Windows and no use of Gapps etc.
I know that my comment is probably off topic so sry.
Click to expand...
Click to collapse
No worries man my comment was also off topic. I too used to a lot of what you currently do. Even using the magisk script Energized which does blocking of ads,trackers etc. But when I saw the sheer amount of information Google has collected even when I opted out of it, just made me realize how futile it almost all is. These companies will never be 100% transparent and honest with us since they're making money off selling our information.

zetsumeikuro said:
No worries man my comment was also off topic. I too used to a lot of what you currently do. Even using the magisk script Energized which does blocking of ads,trackers etc. But when I saw the sheer amount of information Google has collected even when I opted out of it, just made me realize how futile it almost all is. These companies will never be 100% transparent and honest with us since they're making money off selling our information.
Click to expand...
Click to collapse
I have a hobby of reversing stuff, Ive given up trying to go private. With gms code I've seen, they check for so much it's ridiculous. I think a better method for the future is us (the custom rom community) coming together to find a way to block outgoing traffic via an open source app

Surge1223 said:
I think a better method for the future is us (the custom rom community) coming together to find a way to block outgoing traffic via an open source app
Click to expand...
Click to collapse
I think we already have this with AfWall+.

I just wanted to chime in here with a tip to help fill the TWRP void that many are facing right now, especially with Android 10. You can use a manual file flashing app to do most of the same things that TWRP allows you to do, minus the recovery part, of course. You can flash all the TWRP mods you want using this method without needing a custom recovery. Just in case some people didn't know.
You can even install image files too, which means you don't need to be tethered to a computer once you get all set up. This guide should help you understand the power of manual file flashers without having to rely on TWRP for installing certain mod files.

StrifeSoldierVII said:
I just wanted to chime in here with a tip to help fill the TWRP void that many are facing right now, especially with Android 10. You can use a manual file flashing app to do most of the same things that TWRP allows you to do. You can flash all the TWRP mods you want using this method without needing a custom recovery. You can even install image files too, which means you don't need to be tethered to a computer once you get all set up. This guide should help you understand the power of manual file flashers without having to rely on TWRP.
Click to expand...
Click to collapse
It's not Just about flashing. It's about recovery. You can't use a flashing app if you are in a bootloop.

Tulsadiver said:
It's not Just about flashing. It's about recovery. You can't use a flashing app if you are in a bootloop.
Click to expand...
Click to collapse
Oh definitely! Nothing worse than a bootloop. I was just specifically talking about the flashing part. I know a lot of people have been lost without TWRP, so they aren't installing certain mods as much right now since it takes more steps without it. But you can at least do the installing part without TWRP using a file flasher. I don't think as many people are aware of this. It's handy to know. You can use it as a stop-gap until TWRP arrives for any device you want.

the backup and restore functionality of twrp is what i am missing most. just in case something goes wrong with a flash.
is there a way to backup/restore without a custom recovery?

Custom recovery anytime soon?

Any word on whether custom recovery can be available anytime soon for the 4a? Mine arrives in 2 weeks or so and I hope it's available by then.

Crickets... Is this because the device is shipping globally pretty slowly? I figured with a Pixel we'd see this sooner.

With the new security enhancements of android there isnt a custom recovery for android 10 so I doubt there will be one going forward.

It's really unnecessary these days anyhow

Still seems to me like there is a role for custom recovery to play. If the phone won't boot, it's a way to get in and unscrew it or at least do a full backup before any sort of full reset. I do see Pixel 4 has an experimental version for Android 10.

cmstlist said:
Still seems to me like there is a role for custom recovery to play. If the phone won't boot, it's a way to get in and unscrew it or at least do a full backup before any sort of full reset. I do see Pixel 4 has an experimental version for Android 10.
Click to expand...
Click to collapse
Agree - the ability to do a full backup on the device and restore it is a nice-to-have, and an unofficial version does exist for A10 Pixel 4.
That said, the September update is probably the last update of A10 for this device.

That backup is fully available function of adb
https://9to5google.com/2017/11/04/how-to-backup-restore-android-device-data-android-basics/
But based on this I will admit, when it's not creating problems twrp can be quite convenient and simplify many processes. I'm building it now, will post soon™

It's going to be an adjustment having to flash ROMs through ADB/fastboot. I've kept my 2xl up to date solely through TWRP for months.
Gonna have to dust off my computer!

EDIT: oops double posted

xstefen said:
That backup is fully available function of adb
https://9to5google.com/2017/11/04/how-to-backup-restore-android-device-data-android-basics/
But based on this I will admit, when it's not creating problems twrp can be quite convenient and simplify many processes. I'm building it now, will post soon™
Click to expand...
Click to collapse
In my experience, adb backup can have unpredictable results. Plus if I need to unscrew a non booting device, I can't get into adb without a recovery. Glad to hear you are working on a build! My 4a should arrive in a week or two and I can test it eventually.

xstefen said:
That backup is fully available function of adb
https://9to5google.com/2017/11/04/how-to-backup-restore-android-device-data-android-basics/
But based on this I will admit, when it's not creating problems twrp can be quite convenient and simplify many processes. I'm building it now, will post soon™
Click to expand...
Click to collapse
Any luck? ?

Well my Pixel arrived (Canada). I guess no recovery available for now. Hoping that with increased global distribution of the 4a as of this month, we'll see dev interest pick up.

Flashing through ADB isn't so bad. Just got DU flashed without a hitch

For me the primary benefit of a recovery is ability to extract data from a non bootable device. Gives the ability to recover from a flashing disaster.

xstefen said:
I will admit, when it's not creating problems twrp can be quite convenient and simplify many processes. I'm building it now, will post soon™
Click to expand...
Click to collapse
Any updates? ?

As mentioned previously, the unofficial TWRP does work in fact for Android 10 because I tested it with a backup from one device and then did a restore to another device and they were both identical:
TWRP 3.7.0-12 for Sunfish[Testing]
[RECOVERY] TWRP 3.7.0-12 - TeamWin Recovery Project Introduction: Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and...
forum.xda-developers.com
*You just need to flash it with a compatible kernel - this guide is a very good how to:
[GUIDE] UNLOCKING, DOWNGRADING TO A10, TWRP, ROOT
Hello, I'm posting this guide for those (like me) who can't do without TWRP on their device. I'm providing only a step-by-step explanation. Credits to @nikamura for his kernel and TWRP...
forum.xda-developers.com

Questions About Bootloader, Root and Roms

Looks like I'm gonna get a free P2 from my son. It maybe has 1 update left before Google abandons it. When I get it I want to root and put Lineage on it, or maybe a different rom based on opinions provided.
I have some questions:
1- I'm looking for the simplest method to unlock the bootloader and root, as I am not the most knowledgable Android/Linux user. I'm familiar with adb, although best if I can follow a written script. I would appreciate a recommendation on which method posted on XDA. I've seen Deuces and Nathanchance's methods. They seem easy enough to follow along with.
2- I'm a little confused about the Pixel factory images that folks mention in their posts. I see that Google has images catalogued on their site for downloading. How do you choose which one to flash to the phone after bootloader/root process? Does it matter? I'm located in Canada if that makes a difference.
3- I have used TWRP and never used Magisk for loading roms. I also see from one of the bootloader unlock/root methods that TWRP may not be all that reliable. Would TWRP be good enough to flash the factory image with, or should I get familiar with Magisk?
4- Am I correct in thinking that the Google image is flashed first to get the phone up and running, followed by Lineage (and gapps), or an different rom that would be flashed thereafter with TWRP/Magisk?
5- If I screw up during the unlock/root is there a recovery method available?
Thanks for any help provided.

jjcdennis said:
Looks like I'm gonna get a free P2 from my son. It maybe has 1 update left before Google abandons it. When I get it I want to root and put Lineage on it, or maybe a different rom based on opinions provided.
I have some questions:
1- I'm looking for the simplest method to unlock the bootloader and root, as I am not the most knowledgable Android/Linux user. I'm familiar with adb, although best if I can follow a written script. I would appreciate a recommendation on which method posted on XDA. I've seen Deuces and Nathanchance's methods. They seem easy enough to follow along with.
2- I'm a little confused about the Pixel factory images that folks mention in their posts. I see that Google has images catalogued on their site for downloading. How do you choose which one to flash to the phone after bootloader/root process? Does it matter? I'm located in Canada if that makes a difference.
3- I have used TWRP and never used Magisk for loading roms. I also see from one of the bootloader unlock/root methods that TWRP may not be all that reliable. Would TWRP be good enough to flash the factory image with, or should I get familiar with Magisk?
4- Am I correct in thinking that the Google image is flashed first to get the phone up and running, followed by Lineage (and gapps), or an different rom that would be flashed thereafter with TWRP/Magisk?
5- If I screw up during the unlock/root is there a recovery method available?
Thanks for any help provided.
Click to expand...
Click to collapse
Would appreciate some help...

Pixel 2 was updated to android 11, and will likely continue to to get monthly security updates until the release of android 12, so you should have about another year if staying stock.
As far as rooting, the xda guides as you mentioned are pretty straightforward and comprehensive.
Pixel factory images are the stock system images that are provided by google. They are what you would flash if you wanted to run a stock system, and also the means for 'resetting' the phone back to a factory state in the event of a screwup. On the site, you'll notice that google has each of the images organized by phone type (the Pixel 2 is walleye) and within each phone type is operating system version going from oldest at the top to newest at the bottom. Typically you'd want to flash the newest os version unless you have a special use case. There are also cases where a particular version is only for a particular carrier, in which case google will note it under the version number.
As far as flashing lineage, I'm not too sure. I run stock (rooted) on my P2, but lineage is it's own rom so would be flashed directly via twrp. I would image the lineage thread would have install instructions and q/a.

clcdev said:
Pixel 2 was updated to android 11, and will likely continue to to get monthly security updates until the release of android 12, so you should have about another year if staying stock.
As far as rooting, the xda guides as you mentioned are pretty straightforward and comprehensive.
Pixel factory images are the stock system images that are provided by google. They are what you would flash if you wanted to run a stock system, and also the means for 'resetting' the phone back to a factory state in the event of a screwup. On the site, you'll notice that google has each of the images organized by phone type (the Pixel 2 is walleye) and within each phone type is operating system version going from oldest at the top to newest at the bottom. Typically you'd want to flash the newest os version unless you have a special use case. There are also cases where a particular version is only for a particular carrier, in which case google will note it under the version number.
As far as flashing lineage, I'm not too sure. I run stock (rooted) on my P2, but lineage is it's own rom so would be flashed directly via twrp. I would image the lineage thread would have install instructions and q/a.
Click to expand...
Click to collapse
Thanks very much for the help.

Is there a SUPER NOOB thread anywhere to help me with my 7 Pro??

Hello Everyone.
Been rooting since my first HTC Hero- never thought of myself as a noob until this One Plus 7 Pro! Its the US/Global unlocked model. This thing is KILLING ME!
I've followed about 5 different "rooting for beginners" threads from different sites and I still cannot get a basic, working root. I have unlocked bootloader with no issue.
I've had fastboot bootloops, lineage OS bootloops, stock Rom bootloops, stock rom booting up but wifi did not work. I've tried everything on Oxygen 9 and 10 (using the respective TWRP). I've used official and unofficial TWRPs, different versions of Magisk.
I've used the msm tool to reset this thing about 7 times! So as you can see, I'm at a loss.
The only thing I can think of is that I'm screwing something up as it relates to TWRP and Magisk and my flashing/booting process with the A/B slot stuff. Read threads on the benefits of A/B phones...but since I'm having so much trouble, I hate it!
Overall my goal is to get a stock rom rooted; but I couldn't resolve the no wifi toggle issue. I read on one thread that I just needed to flash a custom kernel. If that is the only actual fix, then I should be good to go, but I'm skeptical and figured I messed something up.
So like my title says - Is there any thread out there that someone can refer me to?
Thanks in advance.

Bruce777 said:
Hello Everyone.
Been rooting since my first HTC Hero- never thought of myself as a noob until this One Plus 7 Pro! Its the US/Global unlocked model. This thing is KILLING ME!
I've followed about 5 different "rooting for beginners" threads from different sites and I still cannot get a basic, working root. I have unlocked bootloader with no issue.
I've had fastboot bootloops, lineage OS bootloops, stock Rom bootloops, stock rom booting up but wifi did not work. I've tried everything on Oxygen 9 and 10 (using the respective TWRP). I've used official and unofficial TWRPs, different versions of Magisk.
I've used the msm tool to reset this thing about 7 times! So as you can see, I'm at a loss.
The only thing I can think of is that I'm screwing something up as it relates to TWRP and Magisk and my flashing/booting process with the A/B slot stuff. Read threads on the benefits of A/B phones...but since I'm having so much trouble, I hate it!
Overall my goal is to get a stock rom rooted; but I couldn't resolve the no wifi toggle issue. I read on one thread that I just needed to flash a custom kernel. If that is the only actual fix, then I should be good to go, but I'm skeptical and figured I messed something up.
So like my title says - Is there any thread out there that someone can refer me to?
Thanks in advance.
Click to expand...
Click to collapse
What version of the is are you on right now

I just reset with the msm tool, so it's back to OOS 9.5.3GM21AA.
It will take OTA updates fine up until before the 11 beta
My model is GM1917 (12GB RAM + 256GB ROM)

Bruce777 said:
Hello Everyone.
Been rooting since my first HTC Hero- never thought of myself as a noob until this One Plus 7 Pro! Its the US/Global unlocked model. This thing is KILLING ME!
I've followed about 5 different "rooting for beginners" threads from different sites and I still cannot get a basic, working root. I have unlocked bootloader with no issue.
I've had fastboot bootloops, lineage OS bootloops, stock Rom bootloops, stock rom booting up but wifi did not work. I've tried everything on Oxygen 9 and 10 (using the respective TWRP). I've used official and unofficial TWRPs, different versions of Magisk.
I've used the msm tool to reset this thing about 7 times! So as you can see, I'm at a loss.
The only thing I can think of is that I'm screwing something up as it relates to TWRP and Magisk and my flashing/booting process with the A/B slot stuff. Read threads on the benefits of A/B phones...but since I'm having so much trouble, I hate it!
Overall my goal is to get a stock rom rooted; but I couldn't resolve the no wifi toggle issue. I read on one thread that I just needed to flash a custom kernel. If that is the only actual fix, then I should be good to go, but I'm skeptical and figured I messed something up.
So like my title says - Is there any thread out there that someone can refer me to?
Thanks in advance.
Click to expand...
Click to collapse
If you are still on Android 10,take a look at the following guide.
[Guide] [Android 9/10] [7/7Pro] Unlock, TWRP, Root, and Update
------------------------------------------ Latest update to guide: Jul. 5, 2020 ------------------------------------------ Hi everyone! Many users browse these forums coming from Google or YouTube and have trouble navigating between many guides...
forum.xda-developers.com

Gr8man001 said:
If you are still on Android 10,take a look at the following guide.
[Guide] [Android 9/10] [7/7Pro] Unlock, TWRP, Root, and Update
------------------------------------------ Latest update to guide: Jul. 5, 2020 ------------------------------------------ Hi everyone! Many users browse these forums coming from Google or YouTube and have trouble navigating between many guides...
forum.xda-developers.com
Click to expand...
Click to collapse
I did that exact one a couple of times and when I get it back booted into stock the Wi-Fi does not work. The toggle stays in the off position.

Gr8man001 said:
If you are still on Android 10,take a look at the following guide.
[Guide] [Android 9/10] [7/7Pro] Unlock, TWRP, Root, and Update
------------------------------------------ Latest update to guide: Jul. 5, 2020 ------------------------------------------ Hi everyone! Many users browse these forums coming from Google or YouTube and have trouble navigating between many guides...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks Gr8man001.
Thought I had done this guide before and done it correctly but I buckled down and tried it once more (slow as molasses) and was able to get twrp and root! Appreciate it.