Luns 5 is the main one and I had that backed up before I started this adventure.You can still write Luns 6 from another back up device and it doesn't make a difference at all.Well,at least so far I don't see any issues on my end.But,thank you for clarifying the 6-8 of what you was describing.My model is a TM model,and with AT&T's new 3g shutdown they have something in place to verify which software you're using on the device.If it's not a branded AT&T device they're blocking VoLTE and you can't make or receive calls.Data and text work 100% with no issues at all.And,it's not IMEI related becuase they have the correct IMEI of this V60 I'm using and with it cross flashed with the 20d Luns files it's working like a champ.Oh I understand it's only intended for the 600AM models,but as of now I'm looking for solutions so it will work properly.That was another reason I ask how voice was working on A13 beta?I hope that better explains what I was saying to you.But,thanks for your work.This may be a viable solution for others using their service with different carrier V60's.
Edit:One other thing I wanted to say.The VoLTE issues with this shut down has nothing to do with the modem files either.I have decompressed the AT&T modem file from my device,and tried to write the mbn files back with PDC and even set it active for 5g.Even down to changing all the VoLTE criteria settings in the hidden menu to match perfect and it won't work for voice calls with a different branded firmware.I wanted to sling that out there too.I have been stabbing hard to see what they have done to keep calls from being used...lol..
Oh! Well I'd be happy to talk about a13 but first of all I'd like to clear something up. When posting here about kernel panic it would be preferable for you to be a little more specific about what you're trying to do, and specifically what model v60 doing it on. Other people are reading this and they see kernel failure and don't know you're testing outside of the scope of this restore. They think it just plain doesn't work. This process has been successfully used by many many people but most importantly, I freaking use it!
Now I'm not sure why you would use a TM model on AT&T when Tmob has some very good and inexpensive 5g prepay plans. They also have by far the best 5g network in the US, at least right now. With that being said, I use google fi which is actually the tmob network and I've had no problem with making calls but am presently only able to get LTE and no volte. I put up with this for now because I have a large credit with Fi stemming from a previous phone deal. When that done I'll most likely move to another carrier and maybe another phone.
Ok, so here's the deal with a13 dp2 (developer preview). I'm using a pixel 5a a13 dp2 rom that has been converted to a gsi rom using Erfan's GSIs tool. Also, I manage to load and boot the pixels 6 pro convert a13 dp2 rom but couldn't get any audio on a call so I had to fall back to the 5a rom. Everything is copacetic except for a few things. I had to use the app hd camera and google assistant is presently not working with error message: :google assistant not available on this device", which I think had to do with permissions. a13 is a totally different animal when it comes to security. Now on the upside, there is not one shred of bloatware on my phone, not from a carrier and not from LG. It's smooth, it's fast, I can make calls and browse and so far no failures what so ever.
Now last but not least, you will totally loose all test menu ability. That means no *"568346'*600#. This almost made me turn back but since I just use this phone for testing and LTE is very fast in Sofla it works for me.
