Develop Bugs

[RECOVERY] [GN] [maguro] ClockworkMod Recovery 6.0.4.7 + Nightlies [Flashable Zip]

ClockworkMod Recovery -- Latest maguro Official & Nightlies
This thread is for the GSM/HSPA+ (maguro) model, GT-i9250, and its international variants.
"Nightlies" and changelogs are posted in this thread each time a version bump is made in the source with no official update on ROM Manager. Zips for the latest official are also posted until another "nightly" gets made. Links to the latest "nightly" zips will be in this post, as well as links to the latest official fastboot images via ROM Manager.
http://github.com/CyanogenMod/android_bootable_recovery/commits/cm-11.0
Downloads
Current Official: 6.0.4.7 (Jan 29, 2014)
Fastboot links: http://clockworkmod.com/rommanager
Changelog link: http://v.ht/6047mo
Use the appropriate fastboot command to flash on an unlocked bootloader:
Code:
fastboot flash recovery recovery-clockworkmod-touch-6.0.4.7-maguro.img
Or use my Flashlt script or Recovery zip!
Final "Nightly": 6.0.5.1+ (Nov 4, 2014)
Flashable Zip / Changelog link: http://v.ht/6051mf
Zips provided to flash in the custom recovery of your choice.
Credits: I take no credit for any of the fantastic work done on the recovery; I'm just making it easier for the community to follow along by sharing builds from builder.clockworkmod.com (or mirrors.reflected.net for 6.0.4.9+) and packaging them as zips with a changelog summarized from the Github contributions. CWM is open source and features ongoing work by koush, cyanogen, PhilZ and many others.

Official + "Nightly" Build Changelogs
Recent Major Features/Changes:
- End-Of-Life for ClockworkMod Recovery, features reduced to become Cyanogen Recovery. (6.0.5.2+)
- Allow selective restore of multiple partitions. (6.0.5.0+)
- Multi-core support "performance mode" during backup/restore. (6.0.4.7+)
- Add swipe-based controls to non-touch recovery. (6.0.4.5+)
- Remove all extra "No" options, create .many_confirm to restore. (6.0.4.5+)
- Reintroduce "Rainbow Mode" Easter Egg. (6.0.4.0+)
- Add gzip format (tgz) to Default Backup Format Menu, reducing backup size significantly. (6.0.3.8+)
- Save last 6 recovery logs in /cache/recovery/. (6.0.3.6+)
- Remove Fix Permissions option. (6.0.3.5+)
- Add Reboot to Bootloader and Power Off options to Advanced Menu. (6.0.3.5+)
- Add rooting of unrooted devices with koush's Superuser. (6.0.3.2+)
- Remove Wipe Battery Stats option. (6.0.2.2+)
- Enable "adb sideload <zip>" command. (6.0.1.5+)
- Add creating an update zip of /data apps to share with others. (6.0.1.1+)
- Add dedupe format (dup) to Default Backup Format Menu, reducing space required for multiple backups on one device. (6.0.0.0+)
Current Issues / Notes:
- Key test does not have a confirmation, so if triggered by mistake a hard reset is required if no USB connection is available to make it exit.
- SELinux in JB4.3+ changes the permissions of su on every boot, so after any boot back to Android you will get a su warning in CWM; it can be ignored.
- efs (/factory) partition and many other important device partitions may now be accessible in the "mounts and storage" menu, so be careful not to format them.
Changelog History:
- Jan 29, 2014 - Nov 4, 2014 - 6.0.4.7 official to 6.0.5.1+ End-Of-Life "nightly"
- Oct 6, 2013 - Jan 22, 2014 - 6.0.4.3 official to 6.0.4.7 "nightly"
- Oct 1, 2013 - Oct 6, 2013 - 6.0.4.0 official to 6.0.4.2 "nightly"
- Jul 23, 2013 - Oct 1, 2013 - 6.0.3.4 official to 6.0.4.0 official
- Apr 13, 2013 - Jul 1, 2013 - 6.0.3.1 official to 6.0.3.3 "nightly"
- Dev 16, 2012 - Mar 19, 2013 - 6.0.2.3 official to 6.0.3.0 "nightly"
- Nov 16, 2012 - Dev 16, 2012 - 6.0.1.5 official to 6.0.2.3 "nightly"
- Jul 20, 2012 - Oct 14, 2012 - 6.0.1.0 official to 6.0.1.5 "nightly"
- Time immemorial.
Enjoy!

Thank you man. Would give it a try.
Sent from my Galaxy Nexus using XDA Premium HD app

Your touchrecovery link isn't right.
http://download.clockworkmod.com/test/maguro-touch-test-recovery.img
this is the one for the people interested.
Edit;
Tried making a backup, but d*mn this is really fast!
And the size of the backup too, this is gonna be my daily recovery now.

br13an said:
Your touchrecovery link isn't right.
http://download.clockworkmod.com/test/maguro-touch-test-recovery.img
this is the one for the people interested.
Click to expand...
Click to collapse
Fixed it .. Thanks

since i haven't tried it myself, perhaps someone else in here can answer this:
i read on a german forum, that backups made with 6.0.0.0 result in a bootloop when restoring. anyone REALLY tried to backup and restore a rom?

horst0815 said:
since i haven't tried it myself, perhaps someone else in here can answer this:
i read on a german forum, that backups made with 6.0.0.0 result in a bootloop when restoring. anyone REALLY tried to backup and restore a rom?
Click to expand...
Click to collapse
i did tried it .. i did jelly bean backup then installed aokp b40 to try and see if the files intact then restored then wiped data and cache and restored the jelly bean rom and that is the one i'm using right now

If it's Alpha... it's expected to give a fatal error once in a while that corrupts the bootloader?

can someone make a flashable.zip plze

pa.pn2 said:
can someone make a flashable.zip plze
Click to expand...
Click to collapse
Fail.
Sent from my Galaxy Nexus using Tapatalk 2

Made a backup, its 20.7 MB very impressed.
Sent from my Galaxy Nexus using xda premium

Tikerz said:
Fail.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
No, you failed.
http://forum.xda-developers.com/showthread.php?p=28363171
Sent from my Galaxy Nexus using xda premium

mrasquinho said:
No, you failed.
http://forum.xda-developers.com/showthread.php?p=28363171
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Haha
Sent from my Galaxy Nexus using xda premium

It also made a 727mb folder in the backup folder called boop

arifqur said:
It also made a 727mb folder in the backup folder called boop
Click to expand...
Click to collapse
blobs yes .. i just found out .. i guess the whole idea is same files shared with different backups so no new files no extra space which means same files serve diffrent backups

D3VI0US said:
blobs yes .. i just found out .. i guess the whole idea is same files shared with different backups so no new files no extra space which means same files serve diffrent backups
Click to expand...
Click to collapse
Yup. Seems logical

Just used this toolkit
http://forum.xda-developers.com/showthread.php?t=1392310
very easy to flash

love it so much faster backup and restore!

works fine as intended, very nice nandroid speed! making nandroid backup/restores relevant once again.

Can this be downloaded directly through clockworkmod ROM manager? If so, I don't see an option for it.

[Multiboot][Recovery] Boot Multiple Roms v2.2 - (twrp2.8.3.0)

[updated 20150104]
version v2.2
migration to twrp2.8.3.0
quickfix for lzma initrd roms
fix baseband not recognized on some tw roms
added f2fs feature to multiboot kernel for future versions...
moved qemu tools to sdcard to free space
[updated 20150101]
version v2.13
lollipop support
[updated 20140411]
version v2.11
ubuntu touch support ( http://www.androidfilehost.com/?w=files&flid=13392 )
Important recommandations and details of working features can be found in this thread : http://forum.xda-developers.com/showthread.php?t=2702692
[updated 20140316]
version v2.0
qcow2 support ( https://www.youtube.com/watch?v=LGoTb0u5oX0 )
[updated 20140311]
version v1.2
migration to twrp2.7.0.0
sizing of system/data/cache now possible
real internal/external sd mounted ( respectively in /storage/intsdcard and /storage/extsdcard )
new way to boot roms
new link to download : http://www.androidfilehost.com/?w=files&flid=12801
Hi all,
WARNING : This recovery image has not yet been tested on your device. So be very carefull and wait report of power users
This recovery image is based on twrp with multiboot feature on Galaxy S3.
I did it on my Bell model (d2att) but has ben reporter to work also on Tmobile model (d2tmo).
Original post and recommendations are here : http://forum.xda-developers.com/showthread.php?t=2577211
If you want to test it on your device, please read carefully original post and follow all warnings.
Download link : http://www.androidfilehost.com/?w=files&flid=12801
Thank's for your feedbacks.
Philippe,

Nice...I was actually looking into doing this when I came across it in the m7 forum

didnt have d2spr on filename on xda app. Does on taptalk.

Hi,
Not sure if this multiboot feature is used on your model.
If you want to try new version, it is here : http://www.androidfilehost.com/?w=files&flid=12801. Change log in first message.
Philippe,

Testing now, thanks for the hard work :thumbup:
Been meaning to go back to TWRP and this makes it all that much sweeter :beer:
@Phil_Suz
It seems like you uploaded the wrong file? The d2spr folder contains a zip for the d2tmo, and that file matches the file in the d2tmo folder...
http://www.androidfilehost.com/?fid=23329332407578047

CNexus said:
Testing now, thanks for the hard work :thumbup:
Been meaning to go back to TWRP and this makes it all that much sweeter :beer:
@Phil_Suz
It seems like you uploaded the wrong file? The d2spr folder contains a zip for the d2tmo, and that file matches the file in the d2tmo folder...
http://www.androidfilehost.com/?fid=23329332407578047
Click to expand...
Click to collapse
Hi CNexus, you are wright, wrong file. thank's for the information. Just uploaded the good one.
Philippe,

Thanks for the quick response, downloading now

Working great here. Have 3 roms installed (including internal)

CNexus said:
Working great here. Have 3 roms installed (including internal)
Click to expand...
Click to collapse
Hi CNexus, thank's to give feedback :good:
For All,
Version v2.0 is now ready with qcow2 support.
I opened a dev thread in d2att sub to continue discussion about this projet and to start to speak about how it works and how to use this new feature. If you wish, you can go there now. http://forum.xda-developers.com/showthread.php?t=2684052
Philippe,

@Phil_Suz, you probably already know this, but your modified v2.7.0.0 TWRP for the d2spr fixes the "official" release's problem of not seeing any partitions on some newer S3s.
I was wondering if you would mind if I, or you yourself, whichever you like, post links to here (or you tell me where you'd like the links to point to) in the TWRP and the all recoveries threads since this makes v2.7.0.0 usable for the rest of us who had problems with the official release?
Thank you for this!
Sent from my Sprint Samsung Galaxy SIII with M.O.A.R. v9.0, dkp kernel dated 2/25/2014 and TWRP v2.6.3.0.

roirraW "edor" ehT said:
@Phil_Suz, you probably already know this, but your modified v2.7.0.0 TWRP for the d2spr fixes the "official" release's problem of not seeing any partitions on some newer S3s.
I was wondering if you would mind if I, or you yourself, whichever you like, post links to here (or you tell me where you'd like the links to point to) in the TWRP and the all recoveries threads since this makes v2.7.0.0 usable for the rest of us who had problems with the official release?
Thank you for this!
Sent from my Sprint Samsung Galaxy SIII with M.O.A.R. v9.0, dkp kernel dated 2/25/2014 and TWRP v2.6.3.0.
Click to expand...
Click to collapse
Hi roirraW "edor" ehT,
No I did not know that you had this problem and that this version was working. Yes, you can post link to here but as a temporary solution, I don't manage at all twrp code, my add-on does not touch twrp code so it's a bit weird that this correct a problem on twrp side.
Philippe,

Phil_Suz said:
Hi roirraW "edor" ehT,
No I did not know that you had this problem and that this version was working. Yes, you can post link to here but as a temporary solution, I don't manage at all twrp code, my add-on does not touch twrp code so it's a bit weird that this correct a problem on twrp side.
Philippe,
Click to expand...
Click to collapse
Absolutely, I won't expect you to provide anything and I will explain and encourage others not to either. Thanks again for this. I love the idea of multi-boot although for myself I probably won't be curious enough to try it until a new x.x version of Android drops and won't be provided in a TouchWiz version, so just guessing 4.5 or 5.0 although I hope we get one of those too.
Kudos!
Edit: Do you take donations?

Oh this is funky

Can this be used on the s4?
Sent from my SPH-L720 using xda app-developers app

fabzbear said:
Can this be used on the s4?
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
No. One would need to be built for the s4 specifically.

Hi All,
Multiboot v2.11 is now ready.
This version adds feature to multiboot ubuntu touch 14.04 on galaxy S3 ( img format only, external sdcard strongly recommanded).
I did this ubuntu port on my d2att model but it could possibly work on your device.
If you want to test, I prepared a d2lte test version (0.13) here : http://www.androidfilehost.com/?fid=23329332407583872
Important recommandations and details of working features can be found in this thread : http://forum.xda-developers.com/showthread.php?t=2702692
multiboot v2.11 is at same usual location.
Note : Please let a feedback message in this tread or original one if you tested it. if you report that it is not working, I will remove download link.
Philippe,

As cell features don't seem to work on verizon devices, I removed lte version and created specific versions.
Maybe this will fix cell problems ( because working well on d2att )
Download links are there : http://www.androidfilehost.com/?w=files&flid=13392
Philippe,

S3 TWRP back in business
Thought my new "Best Buy Black Friday" Sprint special was not going to be as cool as it could be since I couldn't get 2.7 TWRP working - but thanks to your modded version I am back in business.

Been running just pac rom for so long forgot there were other sections to this forum. Noticed this today thanks for the work it's nice being able to preview and have multiple roms for ultimate compatibility. Running 5.0 and 4.4 which really helps the transition in my case.

I've been trying this for the past couple days. I can't get it to boot into Ubuntu or any 5.0 ROM. Ubuntu just stays on the boot screen. 5.0 Roms hang while installing.
Sent from my 306SH

[ROM][F220K/F240/E980][jolla-kernel 5.1][Kexec] BlissPop V4.0.3 UNOFFICIAL 5.1.1 [DIS

Hi.
This is United Oxygen team.
We are going to show Official BlissPop for Optimus G Pro with our jolla-kernel ported for G Pro.
This thread is going to be renewed soon.
!NOTICE!
This ROM contains jolla-kernel, which means this ROM supports MultiROM.
RIL is almost FIXED!
When we make a stable ROM, I will re-design our CM thread with PC.
But now, I would just write with mobile, dirty, like this.
And, we'd finally changed our host server, from Innoloud to AchonApp, due to Innoloud's lots of bugs.
What doesn't work:
- T-Money (Korea)
- MMS (Only for F240L - Test with Hangouts, please.)
- Maybe More? You tell me.
You should check:
- Camera (Including 3rd party Camera)
- Installation of Minecraft APK (One Korean said he cannot install it.)
- RIL if it is stable or not now.
ROM Download:
* Optimus G Pro (Korea/Intl)
http://lap.so/krpi
(Download 1021 version.)
(Please select right carrier version for F240. E980 users should download e980 named ROM.)
* Optimus GK
http://lap.so/btme
(Download 1021 version.)
What's Updated:
* 2015.11.11
- Second Release.
- OTA Added - you can download tweaks or kernel updates via OTA app.
- jolla-kernel 5.1 added.

@Genie's, please support Optimus Gx F310!. Thanks in advance.

Can I run any 5.1.1 gapps with this rom

DLM2583 said:
Can I run any 5.1.1 gapps with this rom
Click to expand...
Click to collapse
Yes, you can.

Thanks I'm running the ROM already but can't find APN setting I went into wireless and networks but I don't find mobile data option to add new APN so I don't have mobile data

We are now tring to support E980.
Please download E980 version and test ROM and whether MultiROM is supported or not.
If you install this ROM in Primary Slot, please enter this adb command to know us what E980's kexec code is. :
adb shell
su
dmesg | grep -i hardboot

Hey there I ran the ROM all day today and battery drain is pretty bad and its coming from Google play services...... I'm using Google experience launche.... But i don't think its the Google now cards that are the problem any ideas

We can't solve the probelm associated with Google Play Services... I just recommend you to use Greenify to hibernate some Google Service.

Have been using & pretty good rom.thanks!

Can u only post the kernel so we can use this on any cm based roms and on every new builds.. Is it possible ?

@Genie's, brother, can you share the kernel separately? I love your ROMs, and want also to test other ROMs using OxyGen kernel. Best kernel for F240 so far!

Does it work with E980 yet I am confused by the original post and the one below it?

rjmxtech said:
Does it work with E980 yet I am confused by the original post and the one below it?
Click to expand...
Click to collapse
Oh, I'm sorry. I fixed my first thread. E980 is supported now.
Sent from my Galaxy S4 (SHV-E300S) using XDA Mobile App

DLM2583 said:
Thanks I'm running the ROM already but can't find APN setting I went into wireless and networks but I don't find mobile data option to add new APN so I don't have mobile data
Click to expand...
Click to collapse
Go into settings >data> click 3 dot menu upper right side and you will found the mobile network on last tab. Hope its helpful.
Sent from my LG-F240L using XDA Free mobile app

Yeah thanks it toko me at least two days to figure this one out but thanks

Updated!
Download 0626 Version!
ChangeLog :
- Oxygen Kernel V2.5 Applied! (Which means new ramdisk applied and could be ported to other e980 ROMs!)
- RIL would be go normally when you reboot 5-6 times. It' hard to fix.
- RIL Fix for LG U+

Genie's said:
Updated!
Download 0626 Version!
ChangeLog :
- Oxygen Kernel V2.5 Applied! (Which means new ramdisk applied and could be ported to other e980 ROMs!)
- RIL would be go normally when you reboot 5-6 times. It' hard to fix.
- RIL Fix for LG U+
Click to expand...
Click to collapse
Will this kernel work on stock 5.0.2 lollipop rom E980.? Any ideas

Hamza1010 said:
Will this kernel work on stock 5.0.2 lollipop rom E980.? Any ideas
Click to expand...
Click to collapse
Of course, not.
Kernel used in Stock and CM are each different.
Sent from my LG G3 using XDA Mobile app

Genie's said:
Of course, not.
Kernel used in Stock and CM are each different.
Sent from my LG G3 using XDA Mobile app
Click to expand...
Click to collapse
Thanks for answering.Is there any other featured kernel you know of that I can use on my current rom.??

Hamza1010 said:
Thanks for answering.Is there any other featured kernel you know of that I can use on my current rom.??
Click to expand...
Click to collapse
I don't know well about E980 cuz I'm living in Korea.
Maybe...You should find them in OpGpro Threads.
Sorry.
Sent from my LG G3 using XDA Mobile app

[ROM] [SlimLP] [5.1.1] [CAF] [MOST VARIANTS] [UNOFFICIAL] [STRIX KERNEL]

rom removed! Moving to aospa-l

PATCHES / BASEBANDS
D805/6 Baseband:
This baseband is a version modified from d802 LP, it makes possible to boot on these variants & enable all the 4g bands, that they support.
You can found on my website.
Low Mic FIX:
Here, install it after installing rom. Next build will come with it.

Changelog:
Device Source Changes:
Code:
[B]Device 1.0 Slim Changes:[/B]
-Initial version
-Allow lower brightness for manual and auto mode
-Disable 4k recording (not working as it should)
-Bump
-Disable LCD hack (now, is flashing kernel as stock cm)
Strix Kernel Changes:
Code:
[B]Strix 1.0 Kernel Features:[/B]
-Fastcharge 3.1 (Thx: @Dorimanx)
-No LCD detection hack
-3.4.108 sublevel
-CRC Disable

First here...roms coming fast and thick...thank you for more options

@daniel.stuart14
Judging by the fact the bootstacks are based on your git and not Dr Gravy's or rasheds, you put the bootstacks together yeah? Didn't fork them?

Lawlrus said:
@daniel.stuart14
Judging by the fact the bootstacks are based on your git and not Dr Gravy's or rasheds, you put the bootstacks together yeah? Didn't fork them?
Click to expand...
Click to collapse
Forked, my site just redirects.
I edited all, to work with assert
Here it's

daniel.stuart14 said:
Forked, my site just redirects.
Here it's
Click to expand...
Click to collapse
Well if you used rasheds, you might want to test your download mode as people have reported it being broken.
If you forked them from dr gravy you should be fine, but honestly I'd suggest linking to the official gits as opposed to redirecting them to one of yours.
Will stop possible drama, and if they do update the bootstacks because of something else that might be wrong with them, then its dumbed down, you won't need to keep making sure they're up to date.

Lawlrus said:
Well if you used rasheds, you might want to test your download mode as people have reported it being broken.
If you forked them from dr gravy you should be fine, but honestly I'd suggest linking to the official gits as opposed to redirecting them to one of yours.
Will stop possible drama, and if they do update the bootstacks because of something else that might be wrong with them, then its dumbed down, you won't need to keep making sure they're up to date.
Click to expand...
Click to collapse
All the variants are from Dr Gravy, except d802 (newer aboot) and f320 (I add the bump option). I can't redirect to dr gravy, because his version doesn't has assert. All my bootstacks zip have.

Hey @daniel.stuart14 sorry for the noob question but i always had this doubt, I have a D805, i know that to use the CAF version of the ROMs i need to use the D802 LP bootstacks and a D805 modem but in every CAF ROM i tried i got soft reboots and noticed that is related with modem (3G or 4G) or GPS, and now I'm really confused because of the LP bootstacks update. How should I install the bootstacks in order to be able to install and run your ROM in my D805? (Just asking this here cause you are Brazilian and should have the same device as me). Thanks for the great work

igoorsoouza said:
Hey @daniel.stuart14 sorry for the noob question but i always had this doubt, I have a D805, i know that to use the CAF version of the ROMs i need to use the D802 LP bootstacks and a D805 modem but in every CAF ROM i tried i got soft reboots and noticed that is related with modem (3G or 4G) or GPS, and now I'm really confused because of the LP bootstacks update. How should I install the bootstacks in order to be able to install and run your ROM in my D805? (Just asking this here cause you are Brazilian and should have the same device as me). Thanks for the great work
Click to expand...
Click to collapse
Hey mate!
Here with hybrid bootstacks + my edited baseband (see 2# post), is working flawless.
Just install the bootstacks from my site, and then, the d805 modem.
Give a try, if you still getting issues, just tell me. :highfive:

D802 loops at LG logo. Not booting at all. Obrigado pelo seu trabalho!

dnsp said:
D802 loops at LG logo. Not booting at all. Obrigado pelo seu trabalho!
Click to expand...
Click to collapse
Did you flash my hybrid bootstacks? They are modded to work with my kernel & stock LP.

Yes.

bootlooping here as well on D802.

dnsp said:
Yes.
Click to expand...
Click to collapse
shinaipt99 said:
bootlooping here as well on D802.
Click to expand...
Click to collapse
Guys, can you try this?
I think I found the problem, the new way of flashing kernel was not working as well it should on G2. Fixed in next build.

Still no avail. The LG logo shows up for about 6 seconds following a brief blank screen then it restarts.

dnsp said:
Still no avail. The LG logo shows up for about 6 seconds following a brief blank screen then it restarts.
Click to expand...
Click to collapse
Hmmm, my only guess is the baseband. (This is the only thing diferent between mine and yours).
Try this. and say to me if works. I'll update the bootstacks then.

It's ok now, booted just fine.

dnsp said:
It's ok now, booted just fine.
Click to expand...
Click to collapse
Thank you, I'll update bootstacks modem. (I think I put the d805 version in it, just a mistake )

Mines just got a bootloop too using my the bootstacks+ D805 modem but I couldn't reboot to recovery in the comum way, but I got it thanks to the g2 community in g+ and reflash the older bootstacks from rashed and it worked as before.. Very Strange, can you double check if its really working for D805?

How do I determine if I need to update my vendor and bootloader image?

Due to some negligence and/or, I have a Nexus 5X running Chroma ROM From December 10th, 2015. (December 1st Security Patch Level)
I intend to update to the latest PureNexus ROM as soon as this months ROM is released but I think I have missed some vendor and bootloader updates.
Now I'm not sure if it is completely necessary to update the vendor image, but if so how do we determine if a particular ROM needs a new vendor image or when the old vendor image is safe to use? Is it just good practice to update vendor images with the ROM as necessary?
Thanks in advance.

TechActivist said:
Due to some negligence and/or, I have a Nexus 5X running Chroma ROM From December 10th, 2015. (December 1st Security Patch Level)
I intend to update to the latest PureNexus ROM as soon as this months ROM is released but I think I have missed some vendor and bootloader updates.
Now I'm not sure if it is completely necessary to update the vendor image, but if so how do we determine if a particular ROM needs a new vendor image or when the old vendor image is safe to use? Is it just good practice to update vendor images with the ROM as necessary?
Thanks in advance.
Click to expand...
Click to collapse
The vendor needs to be updated each month.
Being that this is my first Nexus, I don't update my bootloader or radio unless I see the file name has changed between months. There is absolutely nothing scientific about this approach.
Alternatively, I follow a few development threads and I feel like I have little reason to worry about bootloader or radio incompatibilities until a significant update like what we received for March.
Sent from my Nexus 5X using Tapatalk

SlimSnoopOS said:
The vendor needs to be updated each month.
Being that this is my first Nexus, I don't update my bootloader or radio unless I see the file name has changed between months. There is absolutely nothing scientific about this approach.
Alternatively, I follow a few development threads and I feel like I have little reason to worry about bootloader or radio incompatibilities until a significant update like what we received for March.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
So coming from a December 2015 ROM, I'll most likely have to update everything. Cool. Thanks

TechActivist said:
So coming from a December 2015 ROM, I'll most likely have to update everything. Cool. Thanks
Click to expand...
Click to collapse
No, since you are flashing a newer rom. Just update the vendor and bootloader in fastboot then flash your rom.
Sent from my Nexus 5X using Tapatalk