yashsingh1/xdaforums huggingface dataset:
[Verizon LG G3] manaox2:
I wasn't trying to insinuate xposed as the cause, but the trial and error process might go faster if we could find out certain common factors. It could just be noise injection from power adapters or a system process timing out on shut down or memory handling error, tens of things that are low level and hard to test. Logcats would be a good idea.
[Verizon LG G3] PiousInquisitor:
And I'm not defending xposed. I personally don't like it or what it has done to development. So my comment was made for the same reason yours was: to rule out what is causing the issue.
[Verizon LG G3] roirraW "edor" ehT:
I'm much better at (and very thorough if I may say so myself) process of elimination. First in larger groups and then whittling down to the culprit(s).

Again, just information, not refuting the usefulness of logs.

[VK810.4G] [altev] [ViKtory810ROM] official LG G Pad 8.3 Lollipop 36B_00 5.0.2

[VK810.4G] [altev] official LG G Pad 8.3 Lollipop 36B_00 5.0.2

DEBLOAT SCRIPTS

and copies of all the files they remove

[VK810.4G] [altev] OTAs, .IMGs and KDZs, oh my
[Verizon LG G3] roirraW "edor" ehT:
There's hope. I may finally be on the track to finding out what's causing this to happen more often. Unfortunately for me, it may require another whole level of tediousness, but with this hope, maybe I'm encouraged enough to do what I need to do. I won't elaborate until I'm 99% sure. Rumors and snake oil suspects are spread around enough as it is.
[Verizon LG G3] davidstjohn1:
Your the man that's a lot of hard work and I'm sure me and everyone else included will be very appreciative, I would like to donate a six pack...
[Verizon LG G3] roirraW "edor" ehT:
Thanks, I appreciate the sentiment!

Argh. Frustrated again. Might have been a fluke or just the typical random occurrence of this problem such as what's happened on this phone from the beginning. Sigh...

We'll see.
[Verizon LG G3] davidstjohn1:
Just a thought but with the age of the phones and multiple people having this problem could it be either a the contact for the battery or the battery age themselves? I'm just mentioning it because I put a brand new battery in haven't had the problem since
[Verizon LG G3] roirraW "edor" ehT:
The first two times I had this problem were when I had the phone probably three or four months. I didn't have the problem again until the last month or so, after the 35B update came out, and that's when it started happening a lot more often, unless I used the ROM's built-in reboot menu - then I didn't have the problem at all.

I was able to reproduce the problem predictably 20% of the time during 30 reboots when I first started doing tests two days ago. Then I started with a clean install and worked my way up from there to where I am now, and I couldn't get it have the problem once until just this morning when I was able to get it to do it exactly once.

So far, given my inability to reproduce the problem again, there isn't enough evidence to suggest anything - only, in my mind, eliminating what I listed earlier as things some people had speculated were the cause.

---------- Post added at 10:39 AM ---------- Previous post was at 10:01 AM ----------

We're back to having hope again.
[Verizon LG G3] roirraW "edor" ehT:
I'm done testing for now, probably permanently.

Link to my documentation of my process and test results: http://xdaforums.com/verizon-lg-g3/general/rebooted-140-times-attempt-to-narrow-t3251949

I've rebooted 140 times documented and probably at least another 20 or 40 or so undocumented. I give up narrowing it down for now.
[Verizon LG G3] dirtfoot:
I appreciate your attempts and I apologize for sharing my experience so late. I had the reboot problem quite a bit previously. I was running skydragon 602 and flashed the 35b bootstack to get hd calling which I had never activated previously. Something apparently is removed from sd6 because it wouldn't let me activate hd calling after the bootchain. (Yes I clean flash and yes I activated it on my account). My wife's phone on sd5 was able to activate HD calling on her phone after I activated the feature on my account so I clean flashed back to sd5, flashed the 24 bootstack and activated HD calling. Then I clean flashed back to sd602 and flashed the 35b bootstack. About 25 percent of the time my phone wouldn't reboot. No LED light either. So I kdz back to 10b,(because no amount of clean flashing seemed to end the issue) now I'm on sd6 again but no 35b bootstack and also no reboot issues. I'm using a few exposed mods as well.

If the people having issues have gone between 35b and other bootstacks, then something must be getting left behind and causing problems. I don't recall having the problem before going back to sd5 and the previous bootstack.

I'm not complaining here. I very much appreciate all the work put in and generally speaking everybody is enjoying the ROM.

Sent from my VS985 4G
[Verizon LG G3] davidstjohn1:
So my question is how do I get back to the regular 24b modem without this bootstack is it possible or do I have to tot or kdz? Could I essentially just flash the 24b modem?
[Verizon LG G3] blueis300:
I have been using this Rom since the day it came out and all of a sudden getting random freezing. I havent really changes anything so unsure what to look at.
[Verizon LG G3] PiousInquisitor:
Take a look at the initial posts of the Jasmine ROM thread.
[Verizon LG G3] roirraW "edor" ehT:
You're welcome for my part, but:

1. Why not post in the SkyDragon thread?

2. People have flashed the 35B bootstack over SkyDragon 6 and have been able to use HD calling.

[MENTION=4132606]bweN diorD[/MENTION] 's stickied thread in the General section.

[VK810.4G] [altev] [ViKtory810ROM] official LG G Pad 8.3 Lollipop 36B_00 5.0.2

[VK810.4G] [altev] official LG G Pad 8.3 Lollipop 36B_00 5.0.2

DEBLOAT SCRIPTS

and copies of all the files they remove

[VK810.4G] [altev] OTAs, .IMGs and KDZs, oh my
[Verizon LG G3] davidstjohn1:
I already have the 24b baseband zip. I was just asking to get out or off of the 35b boot stack in back to the way it was before I flashed that what would I have to do what I just have to flash that 24b boot stack or just the 24b modem? Right now I'm on XDA bbebs rom, and of course I'm on the 35 b boot stack.
[Verizon LG G3] dirtfoot:
I understand my post was a bit long to digest but my point wasn't referring to HD calling. It was referring to the rebooting issue that you apparently were trying to figure out. I have no problems with my ROM currently, but I had reboot problems after going between different bootstacks in order to go back and forth from sd5 and 6.

It could be something else but I haven't messed with the bootstack since i kdzd back and haven't had any reboot issues

Sent from my VS985 4G
[Verizon LG G3] roirraW "edor" ehT:
Flash the 24B bootstack.

Did you read my thread I linked to? It has nothing to do with the bootstack.

[VK810.4G] [altev] [ViKtory810ROM] official LG G Pad 8.3 Lollipop 36B_00 5.0.2

[VK810.4G] [altev] official LG G Pad 8.3 Lollipop 36B_00 5.0.2

DEBLOAT SCRIPTS

and copies of all the files they remove

[VK810.4G] [altev] OTAs, .IMGs and KDZs, oh my
[Verizon LG G3] davidstjohn1:
I'm going to read the link but I have to wait till I'm done work sorry I'm just a little busy but I definitely am very interested in reading it
[Verizon LG G3] dirtfoot:
I read your link. I said thanks for trying, but you admit you don't have the answer. I just shared what i did that caused my problem and how I don't have it anymore. It may not be the bootstack but your testing didn't appear to try switching ROMs and bootstacks like I did.

Edit: what would be the correct way to go back to a previous bootstack ROM if the mistake was mine

Sent from my VS985 4G
[Verizon LG G3] roirraW "edor" ehT:
I asked because I was on the 35B bootstack for 70 consecutive reboots with no reboot failures and I thought you were indicating you still thought it might be the 35B bootstack that's the problem.

The rest isn't aimed specifically at you and I'm sorry but I'm going to rant because all of the questions regarding the bootstacks have been answered so many times, mostly in this thread but they've also been addressed some in the other two stock ROM threads.

If you're going to a KitKat ROM, flash the 12B bootstack. If you're going to a 5.0.1-based ROM like CM12 or Stock LG 23C or 24B, flash the 24B bootstack.

People, there's nothing magical or mysterious about these bootstacks. Other than the bootloader (aboot.img) and the download (laf.img) partitions, all the other partitions are exactly what the respective official stock ROM from LG/Verizon have. The aboot and laf in all three bootstacks are exactly the same, in order to, as [MENTION=2941286]xdabbeb[/MENTION] has explained, keep being able to get into TWRP, and also to be able to downgrade or flash whatever TOT or KDZ you want to via Download mode.

5.0.1 stock international-based ROMs should work with the 24B bootstack, because 24B was 5.0.1. CM11 would work with the 12B bootloader.

JasmineROM 9.x and SkyDragon 6.x contain *some*, but not all of the same partitions as these bootstacks, which is why if anyone had previously flashed the 35B bootstack and then you flash SkyDragon 6.x or JasmineROM 9.x after, you'll be soft bricked with a black screen and blinking LED even when you go into Download mode - because the combination of partitions from different official releases of the various partitions, other than the aboot and laf, don't work together. Everything seems to behave correctly you just can't see the screen but Download mode works as normal so you can flash a KDZ (recommend 10B for ease of root and installing TWRP). I did the very same thing by accident and recovered exactly the same way others did, by flashing a KDZ with LG Flash Tool 2014.

This is why the 24B bootstack would have to be flashed prior to flashing JasmineROM 9.x, SkyDragon 6.x, or any 5.0.1 stock international-based ROM.
[Verizon LG G3] dirtfoot:
So what we've learned today is don't offer the road warrior any feedback.

I didn't ask for any help. I didn't complain about anything. My phone works just as i want it with thanks to xdabbeb and others, yourself included perhaps. You've been talking on every vs985 forum about researching the reboot problem. That's all I posted for. I had the problem and posted what I did that might have caused it in case you wanted to continue testing, as you can't seem to replicate the problem.

I don't care what caused the problem as my phone is fine now but you seemed interested yesterday.

Sent from my VS985 4G
[Verizon LG G3] nagi_007pk:
Well....

My Imei is showing up as 00000000

Network reception is disabled in our area by the operator. Does that anything to do with the imei going 0000?

Help anyone?
[Verizon LG G3] xdabbeb:
As it seems unlikely that people will reference the post I mentioned in the VS980 dev section, I added a FAQ to the 2nd post that should answer most of the questions that keep coming up.

You won't notice a huge difference with f2fs, but write-intensive operations will certainly be sped up. At this point it's a pretty mature fs.

Yes, this has a custom (and gutted) kernel, but you've got some of your terms mixed up :) While you're correct that your custom recovery is/needs to be bumped in order to pass the bootloader check, I have not "bumped" anything in the bootstack zips...nor does anything need to be. As stated, they're just the necessary version-specific partitions along with the last exploitable 12b aboot/laf pair.

Correcto...they're doing an assert check of the baseband/modem, but you can just modify the updater-script with the 35b baseband version (35B:MPSS.DI.2.0.1.c1.13.4-00005-M8974AAAAANPZM-1) and you'll be good to go.

No need to wipe system as the firmware zip contains the full ext4 system image.
[Verizon LG G3] roirraW "edor" ehT:
I don't know if not flashing the bootstack might cause that. Does the ROM list a baseband? If so, you'll have to search for threads for that problem. I've read about some people using QPST to manually re-enter their IMEI. Once you restore it, this time make and keep multiple copies of a backup of it.
[Verizon LG G3] nagi_007pk:
I have an efs backup

the baseband is listed

So should I try and nandroiding back or?
[Verizon LG G3] roirraW "edor" ehT:
Although I'm aware that TWRP does list the EFS as something it can backup/restore, I'm inexperienced with using it for that as far as researching if it does work reliably and is a recommended way of restoring it. Definitely do your research and find out hopefully from someone who's done it before trying it, just in case it could muck things up worse.
[Verizon LG G3] davidstjohn1:
Thank you for clearing this up i was wondering if i could just restore my 9.1 Jasmine nandroid without flashing any other boot stack. Thanks so much.
[Verizon LG G3] roirraW "edor" ehT:
You're welcome! May work even better than JasmineROM 9.1 does already.
[Verizon LG G3] davidstjohn1:
Could this be the result of wiping internals, as said in the op, not to wipe the internals...
[Verizon LG G3] xdabbeb:
Neither the bootstack nor the firmware zips even reference let alone touch your efs1/2 partitions, so I can't say why that happened to you. I suppose it could be related to your regional network as you mentioned, but I can't say I've ever heard of Verizon doing anything like that. Where are you located? Since you (wisely) have a backup of those partitions you should be fine, however.
[Verizon LG G3] bloodstorm666:
So, if i wanna use the 35B Bootstack on Skydragon, i flash the bootstack (has the modem included, correct?) and if i wanna go back to cloudy 2.5 based off 24b i just flash the 24B Bootstack after i restore nandroid?
[Verizon LG G3] roirraW "edor" ehT:
No, that would be just paranoia. Different partition.

I've read about multiple instances (I'd say maybe a dozen, maybe half a dozen) of Verizon G3 users flashing ROMs and/or at least when flashing a KDZ (I don't recall if it happened with TOTs) and losing their IMEI. There doesn't appear to be any way of predicting when or if it'll happen. Glad it hasn't happened to me...yet.
[Verizon LG G3] davidstjohn1:
The DPI is lower i believe? Definitely not 640 ?
[Verizon LG G3] roirraW "edor" ehT:
Yes. Yes.
[Verizon LG G3] bloodstorm666:
Awesome! Guess ill give it a try. Any noticable improvements as far as signal and things like that?
[Verizon LG G3] roirraW "edor" ehT:
It's much too early to tell. I mentioned earlier, I'm at work and they have weak Verizon around here (they use Sprint) plus I'm doing lots of backing up/shuffling things around so it'll take days to find out about anything else. I just actually got on the ROM within the past 15 minutes. :) Was previously just on the 35B bootstack flashed over another ROM.
[Verizon LG G3] bloodstorm666:
Lol. :) Im gonna flash the 35B Bootstack on top of my SD 6.0. Hope all goes well!
[Verizon LG G3] halcut:
I just installed the ROM. It feels very smooth and responsive.. also its only got 124 apps so its very lean..

Question - LG file manager is removed in this ROM and I need to get to the titanium backup apk (stored on external SD) to restore all my saved apps. Wonder what option do I have? I cannot even sign into Google Play to install tibu as I need Google Authentication which needs to be restored using tibu.
[Verizon LG G3] roirraW "edor" ehT:
Why do you have to restore Google authentication with TB? Why not just enter your account info the normal way? I've signed in and installed apps...
[Verizon LG G3] halcut:
I have 2 step authentication turned on for my account which requires a code generated by the Google Authenticator.
[Verizon LG G3] roirraW "edor" ehT:
Ah! I see. Thanks. I would say ADB via USB/network is going to be the only way then. Of course if you had access to a PC you'd probably have other options available, I'm guessing?

Edit: I might be able to make a flashable zip of the stock file manager for you or others in your situation. If you can find any other flashable zip of a file manager on XDA you might be able to use one.
[Verizon LG G3] mopartonyg:
Really? Your post is pretty disrespectful to a guy that helps everyone and takes on the research and development problems to help everyone.
[Verizon LG G3] roirraW "edor" ehT:
I know you didn't ask for help. In your first post in this series, I saw a couple of things which you mentioned which you did have issues with (even if they were resolved now) which is why I volunteered the information that I did. If you don't want someone to address an issue, don't mention it.

You apparently didn't read my thread correctly because I did replicate the problem, so that had nothing to do with why I stopped testing.

Also, there are so many variables already just with staying with the same stock ROM, I am not about to add all the additional variables of flashing different ROMs. I've so far replicated the problem enough sticking to one stock ROM. Thank you anyway.
[Verizon LG G3] blueis300:
So people have time to argue but not give possible suggestions about my issue? Just kidding not a big deal.
[Verizon LG G3] roirraW "edor" ehT:
:) Sorry man. I haven't encountered this issue on this ROM or previous stock ROMs for the G3. If it happened to me, I would do the following, testing to see if you can reproduce the freezing issue after each one:

1. Delete the Android folders in the root of your internal storage, and also in the root of your MicroSD card.

2. Eject the MicroSD card and leave it out.

3. Copy everything you want to keep from the internal storage and wipe it from TWRP.

4. Do a backup of all your apps with LG Backup, do a complete wipe and fresh flash of the bootstack and ROM. Once you confirm the fresh flash of the ROM isn't freezing, make a new TWRP backup and then only restore some of your apps at a time with LG Backup. What I do is split the apps I have backed up in half alphabetically (since that's how they're listed anyway), so restore half your apps, test to see if you can reproduce the problem. If not, make another backup in TWRP and then use LG Backup to restore half of the apps you hadn't restored yet. Keep repeating until you can reproduce the issue, doing a fresh TWRP backup each time the issue doesn't present itself. Since only you know how often the problem would happen you'll have to be the judge of when to be secure that the problem doesn't exist. If you do reproduce the issue, you should suspect one of the apps you had most recently restored. Restore your most recent TWRP backup, then restore the apps you had previously most recently restored, but this time one by one until the issue comes back.

Good luck! Let us know if you figure it out.
[Verizon LG G3] blueis300:
Thanks will give it a try. My phone has other issues lol. Not really sure if part is the Rom or the phone is just messed up. When making calls I cant always hear the person or they cut in and out.
[Verizon LG G3] roirraW "edor" ehT:
Are you using Advanced (HD) Calling or regular? If you don't know, or you never enabled it on your Verizon account, then it's regular. Have you checked the Call settings (in the dialer) like "Voice enhancement" or, well, I thought there was another option but I can't find it...
[Verizon LG G3] blueis300:
Yeah both hd voice and video calling are enabled but never did anything with my account so just uncehck those?
[Verizon LG G3] roirraW "edor" ehT:
Worth a try, not sure if it'll solve it but won't hurt.
[Verizon LG G3] Bramton1:
So love this ROM. It's been lightning fast since I flashed it, and it still is.

I do have one question, and I wonder if anyone else has this as well. Sometimes if I go through the power menu and go a restart (not to recovery, but just a normal reboot), the phone will shutdown, vibrate, and then... nothing. Doesn't reboot, and can't use the power button to boot up. Only a battery pull will allow me to boot up the phone again.

UPDATE: OK, just saw the posts regarding this very issue. Glad to know it's not just me. For the record, I get this every 2-3 reboots. Don't recall the problem on previous ROMs.
[Verizon LG G3] roirraW "edor" ehT:
Wasn't sure if you might've gone back far enough (two pages) and seen the link for my thread specifically for this issue: http://xdaforums.com/verizon-lg-g3/general/rebooted-140-times-attempt-to-narrow-t3251949

I did a lot of testing and at least determined what absolutely can't be causing the problem to happen more often.

If you did see this, disregard. :)
[Verizon LG G3] bama17:
Hey guys, I'm not a noob as I've been flashing for several years now, but I've never flashed a ROM quite like this one before. I've been using it and it's great, but I need to go back to Jasmine or SD to test a few things that is removed out of this ROM. But when I tried to recover my backup of SD, I had no data service whatsoever. So I tried a clean wipe and reflashed Jasmine and SD and still no data service. I wouldn't think that you'd have to KDZ back or anything that extreme just to flash another ROM would you? I apologize if this is something simple to correct and makes me look stupid, but I have searched all 3 forums to see if anyone else has had this issue, but came up empty. Does anyone know what I'm doing wrong?? Any help would be very much appreciated.
[Verizon LG G3] roirraW "edor" ehT:
Flash the 24B bootstack. You should've had to flash the 24B bootstack before flashing JasmineROM or SkyDragon - others who hadn't ended up softbricked with no display. They could get into Downloade mode but the screen would be back, and they were able to restore to stock using LG Flash Tool 2014 and a KDZ, like the 10B one.

You *can* flash the 35B bootstack after flashing either of those other two ROMs. That's the only way to get Advanced/HD Calling working on those two, and I think they come enabled by default so if you have it enabled on your Verizon account by going to their website, then calls won't work on those ROMs until you either disable Advanced Calling or flash the 35B bootstack.
[Verizon LG G3] bama17:
Oooh ok. I was kinda thinking of trying that, but didn't wanna try anything like that without being for sure. Thanks so much for the help and the quick response!
[Verizon LG G3] roirraW "edor" ehT:
You're welcome! I hope that solves it because as I said, I'm surprised you didn't end up in the same boat as others if you were on the 35B bootstack when you flashed either of the other two. :) I think it will, though.
[Verizon LG G3] haoleflip:
Anyone having issues with the Facebook app not opening? I have even tried to download older versions of the app, but they all do the same thing for some odd reason. I open the app and it just shows the Facebook icon flashing.
[Verizon LG G3] davidstjohn1:
I'm on this rom Facebook runs perfect! I don't think it's the rom
[Verizon LG G3] haoleflip:
Hmmmm weird, maybe I'll reflash and try again. Thanks.
[Verizon LG G3] takota6:
Just a plug for a new xda app.. Way better than tapatalk (i curse thee)

http://xdaforums.com/showthread.php?t=3241866

.. The only hiccups are when using the dual window ,,it'll lock me up,.

Ps I'm a dip because I dont have logs to testify,, it acts as if its out of ram..4.5 star rom tho

Æaa..\../
[Verizon LG G3] manaox2:
If it wasn't XDA's own app, I wonder how anal they would be over this. No judgment on the app. I suppose tapatalk support will be removed soon (tapatalk is admittedly all over the place for a while now).
[Verizon LG G3] haoleflip:
I reflashed and I'm still having the issue with Facebook. So weird! No one else having an issue with Facebook not opening and just sitting on the loading screen with the F icon blinking?
[Verizon LG G3] roirraW "edor" ehT:
Facebook has worked for me when I use it on this ROM. I usually use it at least several times a week from my phone.
[Verizon LG G3] manaox2:
Are you using an adblocker? I use tinfoil for Facebook instead of the official app, works great and doesn't listen in.