I don't know if I'm missing some vital step but I've successfully bricked my phone consistently when manually updating my CM12.1 nightly.
I try to update to the latest nightly once a week, and for the past couple weeks it ends up bricking the device, causing me to go through unbricking procedure and return to stock, then root and all that other fun ****. That being said I have the whole unbricking down to a science, but that doesn't change the fact that it is getting more and more annoying each and every time I have to do this.
It's not that the ROM I'm flashing is bad, It works perfectly fine if I do a clean flash, but when it comes down to updating it completely ****s the phone. To make it worse, thanks to my phones locked bootloader my recovery method is using safestrap, which of course gets wiped when the phone fails the update, leaving me with fastboot as my lord and savior.
I simply don't understand the issue, I'm willing to adapt to doing a clean flash every time I have to update, but I'd at the very least like to know why the hell it does this, to me it makes little to no sense.
I'm using a stock kernel, and no weird init.d scripts that could cause it to boot funny.
On another note, slightly irrelevant, but if someone could tell me how (if possible at all) I could skip the foreplay of flashing back to stock and just flash a ROM through fastboot, it'd be greatly appreciated.
Are you using some kind of built-in update mechanism in CM 12.1 or just flashing the updates through safestrap? If it is the former, maybe it is messing with the safestrap files in some way, maybe even removing them; they do reside in the /system partition, after all. If you are running it on one of the numbered slots, maybe it is mounting the actual /system partition during some part of the update process and doing something it shouldn't on this phone.
Maybe you should create a rom slot and use it for cm. That way your phone won't be bricked...only that rom slot might get messed up if at all.
I guess safestrap is getting messed up and therefore you have to go back to stock. How are you flashing cm nightly? Are you using install option in safestrap or some other way?
Related
I've been flashing various ROMs, but continuously am running into force close/waits, lag, apps shutting down, but only random reboots on one of the ROM's and it got fixed. I get fc/w's on android.process.acore, calendar storage, alarm clock, you name it, I've probably had it error out on me.
I'm wondering how I can clean up my phone entirely.
I don't know what a ROM writes, or doesn't, but I think I've got something in there that escapes a wipe and a flash that seems to be interfering with the system.
I'm not the only one in the Cyanogen's Experimental thread, nor the lastest stable thread that has had this issue. I haven't been keeping up on the other ROM threads, so I can't say if anyone has had these issues with other ROMs or not.
The Mod on Cyanogen's thread has recently threatened bans for non-ROM -related posts, and to be honest, I don't think this is the ROM because it happens to few, but not all. I'ts not a ROM related question, since it shouldn't matter what ROM I'm using, if I'm rooted, I just want to clean off my phone entirely.
I'm also wondering f these issues could be hardware related, perhaps a different manufacturer of a chip or something.
So, how do I really scrub the thing?
From what I understand, going back to a stock, unrooted phone and going through the rerooting process should "unclutter" things.
I followed this how to
http://forum.xda-developers.com/showthread.php?t=491350
I think I solved my issue
Going back to an unrooted phone doesn't deal with anything on the apps2sd partition that might be messing things up if I go back to it.
I ended up deleting the ext4 partition on my card and recreating it. The last time I cleaned up, which didn't do the trick, I just deleted everything I saw. I don't know if there was something left in lost&found or something hidden, but that's what I did.
I also flashed from RC29 instead of JF1.5.1. The first time I thought it would be easier to flash to a ROM I had on my PC that already had Terminal Emulator and Telnet already on it than to download the two apps. I don't think anything would get left in place from that, and I think people have had success with flashing CM's from JF, so I doubt it was that, but who knows. I did both just to be sure.
I also didn't enable any swapping, but i can't imagine that swapping would create acore force closes. ???
So, flashing from RC29 and starting from a freshly created ext4 did it for me.
I recently received a Nexus One from a friend. The bootloader is unlocked and I believe it is rooted. When I got it it kept generating some sort of process error and the phone randomly rebooted. I tried reinstalling a ROM and then the phone just sat with the "X" boot screen. 3 days later and I managed to find a ROM that makes the phone usable (22607-ERD79-update-nexusone-stock-signed). The phone ran fine with that but it is now 2 generations old and I want to update to Gingerbread. Every attempt I have made has ended with the phone just sitting there with the "X" screen after 20 mins. Clearly the updates aren't working. I'm completely confused by all of this.
I'm coming from an iPhone that I was able to jailbreak and hack with no problems. I also have experience with WinMo phones. Never had these issues.
Most of the updates seemed to install correctly. The log screen completes all the steps and ends with "Install from sdcard complete."
Running RA-nexus-v1.5.3
Please help me with this. I want Gingerbread!
First, what versions of Radio and HBoot you use?
How would I tell? Where would I find this info?
Sounds like you are not wiping data.
Whenever you change to a different rom (other than upgrading the same rom) you need to wipe the data partition, otherwise you could get bootloops, stuck at X, unstable systems, etc.
Sometimes not wiping works out okay, but in this case it sounds like it didn't.
I have tried the wiping. As I understand it, I should wipe before flashing the new ROM?
THe baseband is 32.41.00.32U_5.08.00.04
Found them!
HBOOT = 0.35.0017
radio = 5.08.00.04
so I've now upgrade to recovery-RA-supersonic-v2.3.img
supersonic is the wrong phone.....
OK. What is the correct one?
So apparently I was provided the wrong recovery. I did a little research and believe I have the correct one now. recovery-RA-passion-v2.2.1.img
Now should it work...
Still not working. I have no idea what I'm doing wrong. This is really getting under my skin.
Can anyone offer any more info on this? Maybe walk me through it. I have to believe that I am doing something wrong as the phone seems to work otherwise.
Return to a completely stock image. Follow the unroot/restore method from the wiki, using passimg and the FRG33 image...
http://forum.xda-developers.com/wiki/index.php?title=Nexus_One/Guides_%26_Tutorials#Unroot_.2F_Restore_your_Nexus
Sent from my Nexus One using XDA App
OP I had a similar issue. Wiped, installed, wiped, installed. No ROM was stable. It constantly rebooted.
Luckily it was under warranty and HTC replaced it. The new device is rock solid but has burn-in (Pandora buttons always visible and I don't even have Pandora installed).
They are replacing this one as well.
Hope it's under warranty. If so, HTC is great, even with an unlocked bootloader.
Phone: HTC Hero, CDMA
Carrier: Sprint
While others have reported of this problem, the solutions that worked for them dont work for me. Im really stuck.
I know, its an old and slow phone, but I was hoping to go to CM7 to get better performance out of it. Well, I must have done something wrong in the process. My current android version is 2.1-update1. I used z4root to root it and used the clockworkmod ROM manager to install a recent nightly after backing-up my current ROM. Installing the nightly failed, something to do with the zip, but my phone had already been wiped and rebooted in default factory mode. I tried doing the install again with the same nightly and a more recent one, but it kept failing due to a problem with the zips. After one of the reboots, the OS just wouldnt load; seems to be looping on the 'HTC quietly brilliant' screen. I am able to boot in recovery mode, but cant figure out how to get past this looping issue.
Ive tried booting using the back-up I created with no luck. Ive even tried going through the RUU process (cant post a link cause Im a new member here), which results in an error message stating that theres an incorrect bootloader.
I did figure out that I was trying to install CM7 using the wrong zip; had the GSM version. Ive tried installing CM7 with the correct zip, but, after reboot, it loops at the animation with the android on the skateboard and the blue arrow around it. Not sure what it means that the two different OSs loop at, what looks like, the same points.
I probably did something wrong, but Im hoping somebody with a better understanding of all thats involved can let me know if there is any way for me to fix this. Thanks in advance for the help.
grins1 said:
Phone: HTC Hero, CDMA
Carrier: Sprint
While others have reported of this problem, the solutions that worked for them dont work for me. Im really stuck.
I know, its an old and slow phone, but I was hoping to go to CM7 to get better performance out of it. Well, I must have done something wrong in the process. My current android version is 2.1-update1. I used z4root to root it and used the clockworkmod ROM manager to install a recent nightly after backing-up my current ROM. Installing the nightly failed, something to do with the zip, but my phone had already been wiped and rebooted in default factory mode. I tried doing the install again with the same nightly and a more recent one, but it kept failing due to a problem with the zips. After one of the reboots, the OS just wouldnt load; seems to be looping on the 'HTC quietly brilliant' screen. I am able to boot in recovery mode, but cant figure out how to get past this looping issue.
Ive tried booting using the back-up I created with no luck. Ive even tried going through the RUU process (cant post a link cause Im a new member here), which results in an error message stating that theres an incorrect bootloader.
I did figure out that I was trying to install CM7 using the wrong zip; had the GSM version. Ive tried installing CM7 with the correct zip, but, after reboot, it loops at the animation with the android on the skateboard and the blue arrow around it. Not sure what it means that the two different OSs loop at, what looks like, the same points.
I probably did something wrong, but Im hoping somebody with a better understanding of all thats involved can let me know if there is any way for me to fix this. Thanks in advance for the help.
Click to expand...
Click to collapse
I *think* your error, in general, was using a bunch of "easy" one click methods and not properly learning (READING) about what the proper steps are. Here is my advice (assuming you are still rooted) -
1.boot into recovery (power off phone, hold home button, press power)
2.wipe data/factory reset
3.mounts/storage - wipe system and boot
4.restore nand backup OR flash ROM/gapps (from the same thread)
5.reboot, and be patient, bootup could take 5-10 minutes.
Good Luck.
You are the man (or woman)! I believe the formatting of system and boot is what did it. Really appreciate the help.
grins1 said:
You are the man (or woman)! I believe the formatting of system and boot is what did it. Really appreciate the help.
Click to expand...
Click to collapse
It is important, as Il Duce said, that you definitely do a good amount of reading when you want to get involved in rooting your phone. You are opening yourself up to some great innovation and fun, but you can also cause yourself a lot of headaches.
Recovery is your friend. If you can get into that, at least you know things are ok. I like to wipe (or format) system, data, cache, and boot 3x just to make sure that clockwork recovery cleaned everything and there are no dingleberries from the last rom I was using.
Flashing the correct type of rom is even more important. Don't flash a gsm rom to a cdma phone and NEVER flash a gsm radio to a cdma phone. Once you delve into the reading aspect of XDA, you will see that is the sure way to brick your phone.
Some roms take longer than others to boot up. Let it run its course. Sometimes it will reboot right after installing. At some point, you might want to make a nandroid of the new rom you are running and go back to your stock (2.1 update 1) and update your PRL, baseband, etc. (if you haven't done an update in a while).
Have fun, that is the most important part and we seem to have a lot of it here in HeroC XDA land.
You know, I put in a fair share of reading about how to update the ROM on my phone and I was under the impression that it would be fairly simple. I figured that since this has been done for quite a while and all these tools have been developed, I wouldnt need to know what happens on the back end during a root or ROM install.
But I did get myself into a bind that I wasnt able to figure out on my own. And with the help of this forum, I was able to get past my problem. Im glad to say I now have a phone that is functioning very smoothly with CM7 and the apps I need.
Next step for me is figuring out how to save my apps to the SD card so that I can install from there if/when I update my ROM in the future.
Thanks again for the help!
Get titanium backup FTW.
BANG! from my shooter...
ive had the phone since at&t had it on display. rooted it and had various roms for the last couple years and never had any serious issues. last night i flashed jellycream v2 and then did a factory reset inside the rom. the phone prompted that it would reboot twice and that it was normal. it rebooted into twrp and did nothing afterwards. i rebooted it from the recovery and all it did was reboot back into recovery. i decided to flash a different version of twrp and still the same. then flashed clockwork and still got the same result. i wiped the bootloader and basically went through the rooting process again. flashed the latest version of twrp and the phone is still only booting into recovery.
i am at a loss because this is as far as my knowledge goes. its like the phone is stuck still trying to wait for that factory reset from the jellycream rom or something and it wont do anything else but load TWRP.
If factory hard reset will not work (with phone off, press power and volume up together for some seconds. You might want to try also holding home on the touch screen.) flashing firmware will fix it unless you have hardware failure, which I doubt.
http://forum.xda-developers.com/showthread.php?p=39269819
Part 1 can be tricky, so take your time and get that right before proceeding.
drastic00 said:
If factory hard reset will not work (with phone off, press power and volume up together for some seconds. You might want to try also holding home on the touch screen.) flashing firmware will fix it unless you have hardware failure, which I doubt.
http://forum.xda-developers.com/showthread.php?p=39269819
Part 1 can be tricky, so take your time and get that right before proceeding.
Click to expand...
Click to collapse
so far i get the grey LG screen with 'booti mmc_read xxxx' at the upper left with the hard reset. it only takes 2 seconds to show up but the phone shuts off if i continue to hold the power and volume buttons. ill read up on that link here.
I missed that you wiped bootloader. You need that . So you could maybe just install the wkpark bootloader in recovery. You would do 1 and 3 here (1.25a file is down the page)
http://forum.xda-developers.com/showthread.php?p=39130435
I think Jellycream actually requires you have it, if I remember correctly.
Not sure why factory reset would cause that issue, but it will definitely not start without bootloader.
Flashing firmware will also write the (stock) bootloader if that does not do it. It will also reinstall the OS if system is corrupt or missing.
I can't find the thread for Jellycream2. Would you post a link? Are you sure it is for P920/P925 (same device, one is AT&T branded. I have the Thrill P925). If it is not for those device numbers, you may need xbsall's unbrick guide.
Also, if Jellycream2 is based on ICS and you were on a GB ROM, you would likely have needed to first upgrade to ICS and then install the ROM.
I'm just trying to understand why a factory reset could brick your phone...
drastic00 said:
I can't find the thread for Jellycream2. Would you post a link? Are you sure it is for P920/P925 (same device, one is AT&T branded. I have the Thrill P925). If it is not for those device numbers, you may need xbsall's unbrick guide.
Also, if Jellycream2 is based on ICS and you were on a GB ROM, you would likely have needed to first upgrade to ICS and then install the ROM.
I'm just trying to understand why a factory reset could brick your phone...
Click to expand...
Click to collapse
ok basic rundown of what i did in the last year;
when first played around with rooted it about a year ago i used all-in-one to do it. i had already upgraded to ics using the lg mobile support tool prior to rooting. rooting went off fine until i installed a Beats Audio app from the play store. when the phone rebooted after it would be stuck at the grey LG logo. i didnt know what to do so i used twrp and wiped the whole phone. then i used all-in-one and flashed the ICS bootloader and did the flash kernel 4 fix or something its one of the last options to do. then using twrp i flashed ICS_V20_P20, Stock_V20P_Rooted, and a Thrill Update, the phone rebooted fine in an ICS rom but it ran like complete ****, so i tried various roms and the one i settled with was called OptimusRS V1. i used that up until 2 days ago when i flashed the jellycream rom.
after i factory reset that i tried to flash the different wkpark bootloader and twrp that came with the megatron tool hoping that would fix the issue. but it did so i reflashed the original twrp and ics bootloader from all-in-one.
failed to mention this before but i tried 3 different recovery files in between each attempt and it would flash and reboot fine but the phone would still do the same thing and just load recovery.
ill find links when i get off work today. thats the basic history of the phone though.
Hmm. Stil not sure then . Maybe a corrupt zip or you wiped something important. Flashing with LG Flashtool should recover it. And always make a Nandroid backup before installing anything from recovery.
http://forum.xda-developers.com/showthread.php?t=2392309
thats the jellycream rom.
im downloading the files for your xbsa rom at the moment. i do remember yesterday when i used the megatron tool i saw an option to flash the stock bootloader and recovery. i tried it but all i got was the pink LG logo then a security error message below it and the phone shut off.
Oh, ok, OptimusRS's ROM.
Hmm, I thought v20 was GB or something... If it is not ICS then that would be the problem. Also it does say there you need wkpark bootloader for that ROM.
Also, xbsall's v28B includes recovery but it is in system partition. I don't know if that ROM requires you install it from recovery partition or not.
If you still want Jellycream you should be able to flash xbsall's ICS v28B (the normal partitions one, not large partitions), then install wkpark bootloader 1.25a in recovery, then the ROM.
drastic00 said:
Oh, ok, OptimusRS's ROM.
Hmm, I thought v20 was GB or something... If it is not ICS then that would be the problem. Also it does say there you need wkpark bootloader for that ROM.
Also, xbsall's v28B includes recovery but it is in system partition. I don't know if that ROM requires you install it from recovery partition or not.
If you still want Jellycream you should be able to flash xbsall's ICS v28B (the normal partitions one, not large partitions), then install wkpark bootloader 1.25a in recovery, then the ROM.
Click to expand...
Click to collapse
well that breaks down that a bit better. my progress at the moment is step f6. when i connect the phone nothing installs though. it just reconnects and disconnects every second or so. im guessing its because i already have those files. dunno though. i cant get my pc to install the adb drivers for the life of me when the phone is connected in recovery mode.it sees the new hardware just cant find the files.
actually i got it. for some reason the phone wouldnt install anything until i put the battery back in at that step. i continued successfully to step M. the phone is setting up my google account at the moment.
will flashing the baseband be necessary if my apn and sim work like the phone is now? my provider is h20(canadian i heard) but im the usa.
HUGE thanks regardless
Cool :thumbup::beer:
The no battery part is just for driver install, which is fiddly for this phone. Sometimes trial and error is a factor.
The baseband you have now would be the one you had previously. If it works, no problem. The one in the v28B pack is supposed to be optimized for the v28B .bin file, but hey, whatever works.
drastic00 said:
Cool :thumbup::beer:
The no battery part is just for driver install, which is fiddly for this phone. Sometimes trial and error is a factor.
The baseband you have now would be the one you had previously. If it works, no problem. The one in the v28B pack is supposed to be optimized for the v28B .bin file, but hey, whatever works.
Click to expand...
Click to collapse
im only getting E for data. i tried to flash a baseband meant for at&t but it says failed after about 90 seconds. still no 4g though. i did flash the xbsav8 before i set my apn up. i might just go with an optimusRS rom again though. i was happy with it. probably not jellycream this time.
Baseband fail after 80 or so sec is normal. It means it worked. Check your baseband in android settings/about phone.
You might try speed test app to compare actual speed. ATT 4G icon is a lie on this phone IMO.
Now that your pc is set up you can flash any P925/920 bin. Kdz files (combo of bin and fls, there is another tool for flashing those files) can be extracted into separate bin and fls, but I have not done it. The advantage is you can flash baseband separately.
Xbsalls vX3D (see his page) with the P925G fls file gives me 4G icon on Straight Talk in the US, but I like his vR3D better, and I can't tell a speed difference, honestly.
I have not actually measured the speed in either, however.
And for either of those ROMs, you must flash his large partition version of v28B first...very important.
oh its definitely like 2g speeds. its pretty slow. i tried using my providers app and website and its saying the phone i have isnt registered to them anymore so it might be just that. if thats the case ill just bring it in so they can do that for me. when i rooted it the first time i wasnt getting any data and they had to re-register the phone to get it to work right.
my baseband says OMAPP4430/XMM6260. for comparison and/or confirm differences. i have no idea lol.
side question though; my sdcard still has recovery files for the optimusRS v1 rom i had on it. i really liked the setup i had when i made the recovery for it. Im tempted to reinstall it but im really not too sure if itll work or worse harm my phone again.
Lots of variables, but you must remember that xbsall's P940 recovery app he he uses has recovery in system partition. The recovery you had before was probably in recovery partition. They write restores from two different places. Probably you would get an error, but not positive. Understanding that may take some Googling...
If you try it, back up before trying to restore the old backup. Then you could hopefully restore if the restore fails, know what I mean?
Probably the safest thing is to use the all in one tool to install recovery in recovery partition and use that one to restore backup.
I do know when I have restored backups, I have wiped Dalvik, Cache, and Factory Reset (in recovery) and then restore. Then it works. Some people wipe system too.
You can usually flash to recover from a problem, but then you have to set your phone up again
Well I recovered everything. All settings and personalized stuff. Just everything. Everything is running normal again. Just now my data is saying im using an h20 microcell instead of just H20 with a 4g connection. This 2g stuff is for the birds. I'm almost thinking the firmware we flashed has something to do with it. The phone is functional though. Just slow and no mms. I haven't been able to find much on the forums about it. I'll poke around more tomorrow.
Sent from my LG-P920 using xda app-developers app
I'd try another baseband.
Quick question. Is there any reason flashing cm13 on a 20p phone would cause issues? I had to get a refurb due to boot loop and tried to load cm13 on it but ended up with no sound card. I got that fixed by kdz to 20o and then updated to 20p but I don't really like the stock ROM much and am wary about flashing CM again because the back order on this phone is ridiculous.
forvrknight said:
Quick question. Is there any reason flashing cm13 on a 20p phone would cause issues? I had to get a refurb due to boot loop and tried to load cm13 on it but ended up with no sound card. I got that fixed by kdz to 20o and then updated to 20p but I don't really like the stock ROM much and am wary about flashing CM again because the back order on this phone is ridiculous.
Click to expand...
Click to collapse
What do you mean "because the back order on this phone is ridiculous"
OK let me revise
First, you unlock bootloader, and "unlocked bootloader" appear when you turn on your device.
Next, you installed TWRP custom recovery.
Then you boot into recovery (TWRP)
Before installing (flashing) CM you first wipe your previous OS. In TWRP you Advance wipe (delvak,system,data,cach) and internal if you already backed up your data.
After completely wiping. Now you install (flash) latest CM13.
Then, after flashing complete reboot system. Don't install Gapps yet. Every thing should be working fine.
Last but not least, Gapps you install, it might be tricky because if you try to install an app that has an alternative pre installed. some problems could appear. For me Camera and keyboard the stop working.
I'm a noob myself. But if there would be a problem between a software and a hardware. I would blame it on the kernel.
Or the CM file you downloaded is corrupted.
Re download it and check the md5.
Please keep me updated. And any further Q.
Give me a like if this was helpful.
Wolf2231 said:
What do you mean "because the back order on this phone is ridiculous"
OK let me revise
First, you unlock bootloader, and "unlocked bootloader" appear when you turn on your device.
Next, you installed TWRP custom recovery.
Then you boot into recovery (TWRP)
Before installing (flashing) CM you first wipe your previous OS. In TWRP you Advance wipe (delvak,system,data,cach) and internal if you already backed up your data.
After completely wiping. Now you install (flash) latest CM13.
Then, after flashing complete reboot system. Don't install Gapps yet. Every thing should be working fine.
Last but not least, Gapps you install, it might be tricky because if you try to install an app that has an alternative pre installed. some problems could appear. For me Camera and keyboard the stop working.
I'm a noob myself. But if there would be a problem between a software and a hardware. I would blame it on the kernel.
Or the CM file you downloaded is corrupted.
Re download it and check the md5.
Please keep me updated. And any further Q.
Give me a like if this was helpful.
Click to expand...
Click to collapse
The backorder for a refurbished is about a month. My 1st G4 was rooted and running several roms but mostly cm13. It randomly boot looped after a flash and in an attempt to fix it used the LG flash utility and a 20n kdz. When it would boot it would be so laggy that it was unusable. Managed to look at logcat and saw errors related to asound device missing. Turned that phone on for a replacement at a t-mobile store and it just arrived.
The new phone came on 20n I think and I unlocked, rooted, and flashed cm13 again. After about a day I rebooted for something and got the exact same problem. After some searching I managed to find that kdz to 20o would fix it and it did. Not really sure but was thinking that maybe some filesystem change or something might have happened between versions that didn't play nice with cm13.
Not really sure this isn't my area of expertise or anything so just guessing. I'd rather not go through all this again so figured I'd ask if anyone knew any reason that cm13 could have caused it or if I'm just unlucky.
Thanks for the response though I'll make sure to double check the md5 I'm really bad about that lol
forvrknight said:
The backorder for a refurbished is about a month. My 1st G4 was rooted and running several roms but mostly cm13. It randomly boot looped after a flash and in an attempt to fix it used the LG flash utility and a 20n kdz. When it would boot it would be so laggy that it was unusable. Managed to look at logcat and saw errors related to asound device missing. Turned that phone on for a replacement at a t-mobile store and it just arrived.
The new phone came on 20n I think and I unlocked, rooted, and flashed cm13 again. After about a day I rebooted for something and got the exact same problem. After some searching I managed to find that kdz to 20o would fix it and it did. Not really sure but was thinking that maybe some filesystem change or something might have happened between versions that didn't play nice with cm13.
Not really sure this isn't my area of expertise or anything so just guessing. I'd rather not go through all this again so figured I'd ask if anyone knew any reason that cm13 could have caused it or if I'm just unlucky.
Thanks for the response though I'll make sure to double check the md5 I'm really bad about that lol
Click to expand...
Click to collapse
I see you went through a lot. Well the possibility of one of us getting this problem is low, under same consequences. Anyways, on this page, we just try to share info between each other to find the best solution. That's what its about.
Hey, thanks for sharing your experience you just added a possible problem and solution. This will be helpful for the community. About md5 google how to check it. There are really easy ways. Checking the md5 is worth it, that's for CM ROM. I believe LGUP does check for kdz automatically, since the kdz are stock.
Good luck, and don't stop sharing.