No, and I don't think I would try it (unless you have a full nandroid to revert back to). I plan to make one for the Exceed 2, but my time is (and has been) very limited of late. I have about 8 of these that I want to fix up.
The ROMs in OP are all completely unmodified/untouched kernels or bumped now.
How did that happen? I ask cuz your answer may produce different results/suggestions
Never did find a kdz for this device, but I had already installed a cutom recovery *correctly* before bricking mine. The battery pull procedure got me back to TWRP recovery, and I simply restored from a nandroid I had made prior to flashing anything else.
The "Security Error" implies you changed *something* and aboot is kicking you out. *If* in fact you did NOTHING, then it's simply a defective device. Otherwise we need the whole story...
[emoji53]
Maybe a dumb question on my part, but are you rooted? If so, maybe you (or someone else?) can capture the OTA, pull it, and link us to it. Hearing you received an OTA, I ran my IMEI again in hopes the kdz for this may be available now. No such luck tho
Maybe a dumb question on my part, but are you rooted? If so, maybe you (or someone else?) can capture the OTA, pull it, and link us to it. Hearing you received an OTA, I ran my IMEI again in hopes the kdz for this may be available now. No such luck tho
I am assuming that you can get into download mode, correct?
PERFECT
That's recovery, I'm talking about download mode (needed to flash a kdz/TOT [and "just maybe"] a few other tricks)
.That's recovery, I'm talking about download mode (needed to flash a kdz/TOT [and "just maybe"] a few other tricks)
Turn off phone. Hold the Vol+ key and plug in the USB cable from the phone to your computer. I think getting to recovery is nearly the same, only using the Vol- key instead?
OK great! First & foremost, make sure you have the phones drivers, and adb working correctly and can access the device. Easiest installation method for Windows is here. It (optionally) installs drivers for nearly any device, and adb/fastboot is installed system-wide for use in any folder. USB debugging enabled on the device, connect via USB cable, and allow+remember access from the Computer. Open a command prompt in your working folder (ex D:\Realm) and type adb devices. This should present you with the serial number of the device if you have everything setup correctly, and have accepted connections to the phone.
Download the OTA but don't install it yet. With a ROOTED DEVICE, use some root explorer. ES File Explorer File Manager is free and works guite well, but you have to enable root explorer in the settings (SU will prompt you to allow it). Browse to /cache folder inside the root folder of the phone and copy (or move if not going to actually install yet) the downloaded ZIP file to your emulated SD card (or your EXT_Sdcard), then copy it to your PC.
Upload this file somewhere we can grab it (Dropbox, Google drive, whatever) and give us a link. We'll rip it open to see what it contains and maybe come up with a solution. No promises of course, but I'm willing to try. If you don't want your dropbox, google drive (or whatever) getting hammered by the lurkers, start a PM (Conversation) with bcrichster and myself linking us to the file. As bcrichster knows from our other Convo's, I've been working a lot lately, and my time has been quite limited. Collectively, we can share the workload and/or explore different methods once we know what it contains.
Great job! Now need some free time to explore our options. There seem to be a lot of random looking characters preceeding the actual filename, so I'm kind of curious if the update is specific to your particular phone, or common to all of these.
Sweet! Plz be patient w/ @Father Guido as my PC is still down at the moment so he's gonna be your best help. Hope you guys get it squared away, I have faith. [emoji56]
I'm betting your PC is back in service before I have any free time
Same here and Ty- Sir. If/When I get the PC running I'll be be back on & jumping around like a monkey to let everyone know. I still consider myself noob status and you are more knowledgeable on these LG devices at the moment (remember me looking for a "kies" file instead of "kdz"? Lmao).I'm betting your PC is back in service before I have any free time
All I know so far is that the update is a patch of existing files (not a full blown upgrade) . If *anything* has been modified, it will likely fail. Prolly the reason for a boot "security" error in the 1st place.
I'm an amateur compared to most, so here's hoping someone else can grab the ball until I get some time.
