yashsingh1/xdaforums huggingface dataset:
[Remix OS for PC] D2Dchris:
No support for third party launcher

I tried this method. I succeeded to disable/freeze the Launcher3 app (succeeded both ways: by root terminal or by SD maid).

When selecting the home button, or entering the "am start -a..." command as described, I get a toast notification "no support for third party launcher". None of the launchers will launch, only Launcher3. Any suggestions to bypass this error? I get the notification when selecting any third party launcher (Nova, Apex, Action or Evie).

After freezing Launcher3 and the file manager, i succeeded to run Apex Launcher.
[OnePlus X Themes and Apps] Morphine1:
For those who miss OxygenOs stock bootanimation on custom roms,

I've made a flashable zip file for easy installing via recovery.

Download OxygenOsBootanimation-flashable.zip

UPDATE:

For those who were asking for the flashable version from OOS 3 Bootanimation:

Download OxygenOs 3 Bootanimation-flashable.zip
[OnePlus X Themes and Apps] IchBinNoob:
Thanks, but I'm unable to download it :/

(Error 403)
[OnePlus X Themes and Apps] Morphine1:
Thanks for informing.

Link has been fixed.

Enviado desde mi ONE E1003 mediante Tapatalk
[OnePlus X Themes and Apps] Aphex13:
Here's one I edited to fade to red. I made it to match my Dbrand skin...
[OnePlus X Themes and Apps] Morphine1:
Just noticed this post. Good job.
[OnePlus X Themes and Apps] Aphex13:
Thanks, here's a couple more. The first one is the stock mm bootanimation from oneplus, and the second is my edit of the animation to remove the oneplus branding so I can use it on my Nexus. Enjoy.
[OnePlus X Themes and Apps] Tiongkia:
All working. Thanks much
[OnePlus X Themes and Apps] Morphine1:
Good job once again.

Enviado desde mi ONE E1003 mediante Tapatalk
[OnePlus X Themes and Apps] Morphine1:
UPDATE:

For those who were asking for the flashable version from OOS 3 Bootanimation:

Enjoy!

Download OxygenOs 3 Bootanimation-flashable.zip
[OnePlus X Themes and Apps] Exodusche:
Does anyone have the boot animation from the first community build of mm?
[Nexus 6P General] joooe:
I was trying to get rid of the Facebook app because it's so batery hungry and use chrome facebook notifications instead. But I wanted to mute the sound of the notification. So:

Install https://play.google.com/store/apps/details?id=ws.stefma.soundcontroll

Then by having root, choose a notification file you don't use and create an empty file with the same name (I choose Europa.ogg). Copy the file over the original in system/media/audio/notifications. As the file is empty, It won't play any sound.

Open the MegaSound app and configure the Chrome app notification to the empty file.

It's still vibrates though.
[Nexus 6P General] biggyt:
I set my phone constantly on do not disturb as the vibration when I got a Facebook notification through Chrome annoyed me. I have a pebble time watch and I still get notifications on that but my 6p is totally silent
[T-Mobile, Samsung Galaxy SIII] ihavecrashed:
I was trying to flash a new ROM so i tried to wipe data and cache and delvik cache but each time i try to wipe the phone i says E:Can't mount '/preload'

but i didn't notice the error and installed custom ROM anyway.and now i am stuck at boot screen. :(

i can still access TWRP manager and download mode but still can't mount '/preload'. I have searched a lot online but no satisfactory thread found.

Detailed help on this topic will be much appreciated.:good:

thanks
[T-Mobile, Samsung Galaxy SIII] audit13:
I am not sure what would cause the error but the simplest solution may be to flash back to stock, flash TWRP, and re-flash the custom ROM.
[Verizon LG G3] MISAH08B:
I really need some help. Please please help. :( I have my LG G3 VS985 and it was on stock verizon firmware. I had lollipop and android 5.1.1. I rooted it using Kingroot and it was working fine. I used an app called Autorec and i tried flashing twrp using it and all it did was make my phone not turn on. It keeps vibrating and i really need your help or anyone. I'm very worried.﻿
[Verizon LG G3] Slorsx89:
I have this same exact problem... anyone have a solution?
[Verizon LG G3] roirraW "edor" ehT:
I haven't looked in [MENTION=3279781]bender_007[/MENTION] 's autorec thread in a while but last I looked he didn't provide a version for 35B, only 23C and 24B.

Even if the screen stays black, go through the motions of putting the phone in Download mode. Does your phone show up in Windows' Device Manager in the modem section? If so, flash the 10B TOT using the .DLL that's extracted from the 35B KDZ to start fresh. Re-root with the Stump app and use TWRP Manager from the Play Store to put TWRP back on.

Rooting gets more complicated after 10B and putting TWRP on gets more complicated after 12B. For what it's worth, I stick to stock but modified/heavily debloated Verizon/LG ROMs.

Always flash the 10B TOT to root and to put TWRP on, it just saves a lot of headache. Kingroot installs a bunch of stuff behind the scenes (not just apps), so it's very shady. [MENTION=2941286]xdabbeb[/MENTION] experienced just how much Kingroot modifies the ROM under the hood.
[Verizon LG G3] Specter597:
I was completely stupid and have soft bricked my phone tonight.

I had a small issue with xdabbeb's 47A and went to restore a prior nandroid. Now the phone turns on, (I can hear it) but the screen is black. I'm sure it's a bootstack 35B issue.

I'm in a panic and am having trouble finding all the correct files to TOT or KDZ back and fix my phone.

Can you please walk me through the steps?

I feel so stupid and this couldn't have happened at a worse time.
[Verizon LG G3] roirraW "edor" ehT:
For KDZ, [MENTION=4795150]annoyingduck[/MENTION] 's stickied return to stock thread in the General section.

For TOT, just Google for:

TOT method

and just use the VS985 TOT and .DLL. The method is the same on all LG devices, just use the VS985 files instead of whatever the directions you find specify. You can still get the 10B TOT and the .DLL that's necessary at my Android File Host section which is linked to from the bottom of the first post of the return to stock thread I referenced. There's also a link to his thread in my signature below.

As you found out, when restoring TWRP back ups or flashing a new ROM, always flash the corresponding appropriate Bootstack after the restore or flash. 12B Bootstack for KitKat, 24B Bootstack for Lollipop 5.0.x and 35B Bootstack for Lollipop 5.1.x and Marshmallow 6.0.
[Verizon LG G3] Specter597:
Yes, I see the link in your sig now. Thanks for responding. The 10b download is not working from that link but 12b KDZ is downloading. Should that be a problem? I can still bump and stump 12b right? Also I think 12b was what shipped with my phone.
[Verizon LG G3] roirraW "edor" ehT:
You're welcome!

You're looking at the direct links to those KDZs, right, like the following?

I have an Android File Host link below those that points to a folder that has all the KDZs and TOTs in one place. 10B, whether TOT or KDZ, is recommended because you can root 10B the easiest - by using the Stump app found on XDA. You can't use Stump after 10B, or at least definitely not on 12B (not 100% positive about 11C that came between). Put TWRP on after rooting with TWRP Manager from the Play Store. Installing TWRP is possible that easily on 12B if you root it using a different method. Putting TWRP on becomes more complicated after 12B, FYI.

What your phone came with doesn't affect things.

Even though your screen may stay blank, if you go through the motions of putting it in Download mode, then it will be in Download mode. Pull the battery first then put it in Download mode using the original USB cable that came with the phone, connected preferably to a USB 2.0 port that comes directly off of your PC motherboard - not through a USB hub. You can check it by looking in Windows' Device Manager to see if the "LGE..." device is listed under the Modem section.

The symptom you're having is common and isn't actually caused by a Bootstack, but by a lack of one, or probably more accurately, a catastrophic mix of conflicting partitions caused by, in this case, having one Bootstack on the device - probably 35B, and then restoring a backup that might've included only some of the partitions necessary for the Bootstack. TWRP backups don't back up the entire Bootstack, so you end up with some partitions from one, and other partitions from another, and they don't play well together.

JasmineROM and SkyDragon in particular play havok, so even if you dirty flashed either ROM after restoring a TWRP backup of either, if you had the 35B Bootstack flashed previously and didn't flash any Bootstack after dirty flashing either ROM, you'd have a mix of 24B and 35B partitions because even though the latest versions of both of those ROMs are based on 35B, they include part of the 24B Bootstack, but not even the whole thing at that. The reason they did that is because they couldn't figure out how to get the 35B modem working, and it wasn't until [MENTION=2941286]xdabbeb[/MENTION] packaged the proper Bootstacks we needed that it was realized that the 35B sbl1 - which those two ROMs don't include any kind of sbl1 partition - is necessary for the modem to work with it, so they included some 24B partitions because that modem worked fine with the older sbl1 which was still on the device from the last time the phone was flashed to stock unrooted.

We have a similar situation with 47A except in this case, besides needing the 47A sbl1 for the 47A modem to work, the 47A sbl1, in combination with the 12B aboot (bootloader) causes a QHSUSB_BULK 9008 mode type of brick, which requires different instructions for recovering than the normal KDZ or TOT methods, although it does use the TOT as part of the recovery, and then you flash the entire TOT method afterwards.

Sorry if this is TL;DR. :)
[Verizon LG G3] Specter597:
I followed to your Android Host link and was getting errors on primary DL and mirrors for 10b KDZ and 10b TOT. That is why I started DLing the 12b

I think the most recent version of Stump could brute force 12b. I never TOT'd back to 10b when I bought my phone so it may have worked a year or so ago. But I will try downloading 10b KDZ and 10b TOT/.DLL in a few minutes and see if the Android Host File DL's are working again.

Is there any problem with KDZ'ing now and TOT'ing later? I understand the limitation on KDZ and Updates. But KDZ doesn't prevent a future TOT does it?

About the TL;DR - I read it. You describe EXACTLY what I did. I was on Jasmine 9.1; I successfully installed 47A but TWRP borked my MMS/SMS backups so I thought, "I'll restore my TWRP nandroid AND (because I thought I was clever) I'll dirty flash the ROM and Update over the Nandroid so that the partitions are correct!"

... and here we are.:crying:
[Verizon LG G3] roirraW "edor" ehT:
Weird, I just checked and all the servers aren't working for me either. I might have to put all the files up somewhere else as a backup. AFH is so convenient though since developers can upload via FTP.

No, Stump won't work on 12B. You have to brute force on 10B, but it just won't work on 12B. A new root method had to be found, and they're available, some scripts in some threads in the non-Verizon G3 General section, but it requires a connection to the computer and USB Debugging mode and is less reliable than Stump.

I'll upload the 10B stuff and the .DLL elsewhere and I'll let you know if/when it's up - might take a while to upload though.

No, you can always TOT - just TOTing from stock unrooted 35B and higher requires the .DLL I have a copy of (it's extracted from the 35B KDZ). There was an older .DLL that worked fine coming from 24B and lower, but the new .DLL should work for coming from both new and old builds. And as I think you're saying you already know, if you're on stock unrooted 35B or higher you can only flash the 35B or higher KDZs, which is one of the reasons it's always suggested nowadays to flash the 10B TOT in order to root and put TWRP on.

Whether TOTing or KDZing, if you're rooted and have flashed any of [MENTION=2941286]xdabbeb[/MENTION] 's Bootstacks, then you should be able to flash the TOT with either the old or new .DLL, and you can flash any KDZ.
[Verizon LG G3] Specter597:
Thank you, thank you. I DID manage to download the special 10b .DLL from your Android Host File location. I think I've found the 10b_3 TOT on a different site and I'll try using it with your DLL - but if I doesn't work I'll try getting yours as well when you tell me its working.
[Verizon LG G3] roirraW "edor" ehT:
You're welcome. That's good. I'm uploading the TOT and KDZ elsewhere but looks like it'll take three or more hours to finish.

Good luck!

---------- Post added at 10:03 AM ---------- Previous post was at 09:27 AM ----------

@Specter597 I had put in a ticket to Android File Host and it appears the problem was caused by me. They told me there were illegal characters in the filename and said he'd contact the uploader, not realizing the uploader was me, so he didn't mention which characters are illegal - I asked so hopefully he'll reply soon and I don't have to experiment to find the right combination.

For what it's worth, thanks for helping me to find out there was a problem with some of my filenames on AFH. Doh me!

Edit 2: Turns out it was the comma I had put in the filename. I removed the comma from that one and the 10B KDZ and now they download fine. Sigh!
[Verizon LG G3] Specter597:
This time I was successfully able to start the 10b TOT download from your AHF.

Thank you so much.

I'm going to take the time and download YOUR file out of sheer paranoia, even though the other file has finished.
[Verizon LG G3] roirraW "edor" ehT:
If the MD5 hash of the TOT you had downloaded is F22CD79F6C4924A0FE4429A8C4BABE9A, then it's the same as the TOT I have inside the 7-Zip archive you're currently downloading. That's the easiest and quickest way of checking to see if you have the right thing.
[Verizon LG G3] Specter597:
I've gotten everything installed and setup, but for whatever reason Windows 7 is not showing the LGE Modem at all in COM Ports.

Do you think I should just try different Phone drivers?

Edit: Maybe I have the drivers right now.

Edit 2: The Drivers' installation seem to be spotty.

Sometimes The LGE Android MTP Device install Fails

Sometimes the LGE Mobile for VZW USB Modem fails.

But I'm having a hell of a time figuring out if I'm in Download Mode or not.

How long, [MENTION=2560614]roirraW "edor" ehT[/MENTION] after I plug in the USB cable should I continue to hold "Up"?
[Verizon LG G3] roirraW "edor" ehT:
You would only have to hold the Up volume button for at the very most 10 seconds, and that's probably extreme. If the Modem and Port sections list the LGE device now, you can be reasonably sure it's in Download mode. For TOT, change the port of the LGE device that's in the Port section (not Modem section) to 41.

I always use the latest drivers either from LG's or Verizon's website. 4.0.4 was the latest last I looked. I always reboot the PC (with the phone disconnected) after installing drivers. I don't bother updating the drivers to the latest if I already have working ones installed. With new drivers, it can take Windows up to 10 minutes to actually finish loading the drivers the first time you plug a new device into a new/different USB port. That's the way all USB devices work. In other words, if you plug the phone into port "A" in Download mode and you wait anywhere from seconds to minutes until it loads the drivers, and then unplug it and replug it into port "B", then it'll load the driver again. If you switch back to "A" it won't have to load the driver again, though.

They'll all load them from the same driver installation you did once.

Are you using the original USB cable that came with the phone? Letting the phone sit while plugged in, and not moving it around? Sometimes just rebooting the PC or trying different USB 2.0 ports help. In the end, sometimes trying a different PC helps.
[Verizon LG G3] Specter597:
Update: Success.

Successfully TOT'd back to 10b.

I decided (after installing/reinstalling the drivers 6 times) that even though it had said that some of the drivers failed to install, I would just say "F* it." Try it anyway. Despite the Windows installer saying that two elements of the DL Mode Driver package didn't install - it worked anyway. The other part that got me was that after clicking the Yellow arrow you have to unplug/plug the phone back in. What a way to spend 12 hours of my life.

Thanks for all your support [MENTION=2560614]roirraW "edor" ehT[/MENTION]

Now I just have to decide if I want to bother rooting again, install xdabbeb's 47A or just play it safe ...
[Verizon LG G3] roirraW "edor" ehT:
Great! You're welcome! Glad things didn't get worse from installing drivers so many times. :) F* it. Root it, it's so easy. Just always remember to flash the right Bootstack after flashing any ROM, even if you think you're already on the right Bootstack - doesn't matter, just flash it, there's no reason not to. You know you can't stand it without the features you get from rooting! ;)

Hope you didn't lose anything you don't mind losing.
[Verizon LG G3] Specter597:
No. I don't think there was anything that I don't have backed up. (I'm a nut about cloud/sdcard/etc.) Just some SMS/MMS. Maybe a save'd game. Who cares! I still have a phone!! :laugh:

But I'm definitely deleting those Jasmine 9.1 backups. I don't even want to risk that again. Aside from Skydragon/JasmineROM are there any of the other ROM's floating in the DEV forum that will Bork my phone this badly?

And after I Root and TWRP is there any reason I can't go straight from 10b to xdabbeb's 47A?
[Verizon LG G3] jurington:
Yes you can go straight to 47A from 10B, I've done it a few times before with no problems. Also you can try out xdabbeb's 2.0 which is lollipop not marshmallow. Very slimmed down, not a whole lot of grill to it, but very smooth and reliable. I keep going back and forth between the two myself.
[Verizon LG G3] roirraW "edor" ehT:
Not that I'm aware of. And either ROM is just fine as long as you flash the Bootstack after, and you should do that no matter what TWRP backup or ROM you flash.
[Verizon LG G3] Specter597:
Hmm...

I tired 47A. (Again)

And I found that I did not love it.

I am getting ready to flash restore my Jasmine 9.1 TWRP

Can you please, before I reboot confirm the bootstack I should be on?

I thought I had it right, but the posts online seem to indicate 35B but I had saved in my folder 24B

I don't want to reboot until I have flashed the correct bootstack.

Stomach doing flips.
[Verizon LG G3] roirraW "edor" ehT:
Either Bootstack is fine. No Bootstack will be catastrophic, anyway, just as long as you flash some Bootstack after, the worst that would happen is just no signal (I have no idea if the 12B modem, etc, gets a signal on 35B). 35B is technically the correct one, but as I said, just as long as you flash *some* Bootstack AFTER the ROM, you're fine. The whole problem stems from JasmineROM 9.x's and SkyDragon 6.x's partial 24B Bootstack.

If you want device encryption and Advanced/HD Calling to work, you must use the 35B Bootstack with a 35B-based ROM.

Have you tried [MENTION=2941286]xdabbeb[/MENTION] 's VS985 v2.0.0 35B-based ROM? It's awesome. If I wasn't happy with 47A I'd be back on it.

Reference:

35B Bootstack for Lollipop 5.1.x and Marshmallow 6.x ROMs

24B Bootstack for Lollipop 5.0.x

12B Bootstack for KitKat 4.4.2

ALWAYS flash an appropriate Bootstack AFTER either flashing any ROM or restoring a TWRP backup. Every time. No matter what Bootstack you think you currently have flashed.

The only time the order of flashing the Bootstack matters is with SkyDragon 6.x and JasmineROM 9.x, and that's because of their partial 24B Bootstack. i.e. if you flash the 35B Bootstack before flashing the ROM, key partitions (but not the entire Bootstack) will get overwritten by the 24B parts in either of those two ROMs, and having the conflicting 24B/35B partitions causes a brick. Those are the only ROMs (that I'm aware of) that contain any part of the Bootstack. That's why I always tell people to flash the Bootstack after any ROM or restoring a TWRP Backup. If you just do it after flashing the ROM, then you'll never be wrong.

TWRP doesn't back up the entire Bootstack, only partial. That's why you need to flash whatever the appropriate Bootstack is for whatever TWRP backup you restore AFTER you restore it and before exiting TWRP.

The only parts of either ROM that make them unique are the system partition and at least in the case of SkyDragon, the kernel. Bootstacks don't contain either of those.
[Verizon LG G3] Specter597:
Okay, that makes sense.

So I flashed 24B > Wiped > Restored my TWRP

Do I need to re-flash a bootstack BEFORE rebooting?

I'll need to take a closer look at VS985 v2.0.0 35B. - I think I've already even downloaded it - just haven't pulled the trigger.

The thing that always trips me up is the order of flash. And worrying about if the 35B provided with JasmineROM is the same as the one provided by xdabbebs
[Verizon LG G3] roirraW "edor" ehT:
I edited my post with three key things:

If you want device encryption and Advanced/HD Calling to work, you must use the 35B Bootstack with a 35B-based ROM.

ALWAYS flash an appropriate Bootstack AFTER either flashing any ROM or restoring a TWRP backup. Every time. No matter what Bootstack you think you currently have flashed.

The only time the order of flashing the Bootstack matters is with SkyDragon 6.x and JasmineROM 9.x, and that's because of their partial 24B Bootstack. i.e. if you flash the 35B Bootstack before flashing the ROM, key partitions (but not the entire Bootstack) will get overwritten by the 24B parts in either of those two ROMs, and having the conflicting 24B/35B partitions causes a brick. Those are the only ROMs (that I'm aware of) that contain any part of the Bootstack. That's why I always tell people to flash the Bootstack after any ROM or restoring a TWRP Backup. If you just do it after flashing the ROM, then you'll never be wrong.
[Verizon LG G3] Specter597:
But if JasmineROM / SkyDragon both write over portions of the bootstack then won't flashing the 35B bootstack AFTER restoring cause portions of their ROM to be overwritten? I'm missing something.
[Verizon LG G3] roirraW "edor" ehT:
It doesn't matter what's same/different as long as you flash the Bootstack after.

---------- Post added at 11:59 AM ---------- Previous post was at 11:57 AM ----------

You're not missing anything, you're just overthinking. I wouldn't have said it if you shouldn't do it.

TWRP doesn't back up the entire Bootstack, only partial. That's why you need to flash whatever the appropriate Bootstack is for whatever TWRP backup you restore AFTER you restore it and before exiting TWRP.

The only parts of either ROM that make them unique are the system partition and at least in the case of SkyDragon, the kernel. Bootstacks don't contain either of those.
[Verizon LG G3] Specter597:
I've been accused of that before.

Thanks for your patience.

I'm going to give 2.0.0 a try before I go back to JasmineRom I think.

Thanks for all the advice around the forums.
[Verizon LG G3] roirraW "edor" ehT:
:)

You're welcome! Hope you like it. It's the most modified stock VS985 ROM there is.
[Verizon LG G3] minhas729:
Hey bro.. Trying to send you PM .. But can't reach you.. Wanna discuss something
[G 2014 Q&A, Help & Troubleshooting] fidorulz:
I just updated to 6.0 via official OTA on my XT1064

Bootloader is locked currently and everything is stock

I know I have to unlock the boostloader first but has anyone found clear instructions that they tested on the XT1064 to get root with the 6.0 update?

I found plenty of threads but they mix instructions for various models and versions of android

Im looking specifically for XT1064 and stock 6.0

I bricked my device already once previously and another time the rooting via boot.img caused wifi to stop working

I am not willing to use my device as a test subject anymore.

Anyone who has been able to root stock 6.0 on the XT1064 please help and simply point me to what worked for you

Thank you