yashsingh1/xdaforums huggingface dataset:
[G3 Android Development] hokiealumnus:
OK, so bear with me here. Maybe [MENTION=2486198]itskapil[/MENTION] isn't part of the team and was guessing, but it seemed like he was speaking from a place of authority. So, he said this:

...but you say this:

So I'm totally confused. Is it stock based or AOSP based? If the latter, again I'd ask how you managed to get the LG camera working on it? That would be great info that could be used with existing LP ROMs too.

I want to give you the benefit of the doubt, and indeed I also really want to play with M -and am very grateful for your efforts- but hopefully you can see how this is all very confusing.
[G3 Android Development] Felipe_Salves:
i'm still having binary errors on d855.
[G3 Android Development] tallman43:
You and everybody else it's not been fixed yet i'm sure the op will post when i'ts fixed.
[G3 Android Development] manups4e:
they have ported the nexus 6 developer preview 3 using stock lollipop rom... that's why you can see the lg apps... that's because it's the most stable way
[G3 Android Development] empulse92:
instead of bashing and blaming the op you guys could try to help building or fixing errors and providing logs, or maybe port a rom by yourself if you already want to talk like smart people, you shall prove your knowledge
[G3 Android Development] manups4e:
I totally agree
[G3 Android Development] hokiealumnus:
Thing is, I'm not trying to bash or blame. I'm trying to verify. Those are very different things. Let's look at the information available so far - and again, [MENTION=5348372]jeddahboy23[/MENTION] , please don't take offense, this entire thread just doesn't make any sense to me, and it could very well be my own fault. I'd love nothing more than to be wrong here!

-OP makes a thread asking how to install Xposed.

-A week later, OP makes a thread purporting to have somehow meshed a Nexus 6 Marshmallow build with an LG Stock build, claiming it's a Marshmallow ROM with LG Lollipop apps. Again, none of the stellar devs working on our device has been able to do that; not on KK, not on LP...nobody has a working stock camera on an AOSP ROM, at least that I've seen.

-Screenshots posted, which are generally used to give examples of what the ROM look like, were pointed out as being suspiciously similar to a stock LG build + xposed + a G3TWB theme (not just by me, but others too). Considering the thread from Nov. 7, that makes more sense than this thread in its entirety does.

-Screenshots are subsequently dismissed as being not from the Marshmallow build...so why post them? ...and why do they show Android 6.0?

Also, who is TeamJB? Can anybody find any references to that anywhere else on XDA...or anywhere? Contrast this OP with the Candy5 thread's OP, or the Team-Exodus OP, which are put together by real teams with real G+ pages and real websites. The 'professionalism', for lack of a better word, of those OPs is very evident.

Added to all of that, it seems nobody can successfully install the ROM (each one of those words is a separate link to someone that can't install it).

You don't consider this healthy skepticism, but rather bashing and blaming? Am I too much of a cynic for my own good? Look, I want this to be real as much as the next person, but everything presented so far looks like it's just plain not. You are very correct though, I cannot develop a ROM. But I certainly can install Xposed, and figured out all by my lonesome how to do it; it's not that hard, especially compared to developing a ROM as complicated as some amalgamation of a brand-new Marshmallow pull from a Nexus 6 and a Lollipop stock LG build.

Again, no offense is intended to the OP. This is just intended to be a post pointing out facts. Maybe there are excellent explanations for all of this, and they'll come out with an awesome Marshmallow ROM - the first on our device when no other developer has done so. That would be great! So far, however, things aren't adding up to me. :confused:
[G3 Android Development] kingracer:
You should read previous pages - it's still in development and can't be installed for now. OP is working on this issue.
[G3 Android Development] :
It's not bashing or blaming when the checksum of every file matches that of LG's 20U firmware, and none of them match a file from DP3. It's called skepticism, which is perfectly fine when OP ignores every question posed by skeptics and the mods allow him to continue to do so under the assumption that this ROM is not harmful. I could fix this ROM in five seconds, considering I've ported 20U already and could upload it with the same changes as OP under the same guise.
[G3 Android Development] bajasur:
Thread Closure

Thread closed until further notice. Thank you for your understanding.
[Galaxy Note5 Accessories] felloffthetruck:
Installed the Zagg Glass today on my black Note 5 and I'm happy to report that I have no halos at all. I did have some stubborn bubbles that took a while to press out but everything came out prefect (except my sore thumbs). The is the Zagg Glass I purchased from Verizon and is the Full Screen Coverage Version. :)

Here are a few pictures.
[Galaxy Note5 Accessories] Carsus55:
Does it look blue in the sun when applied?
[Galaxy Note5 Accessories] felloffthetruck:
No, the one that Best Buy is selling has that blue tint to it. This one is clear.
[Galaxy Note5 Accessories] awtryau89:
I have the same one and it does not look blue. I think there is a different version that adds the tint.
[Galaxy Note5 Accessories] Carsus55:
Wish I'd known that. Oh well.
[Galaxy Note5 Accessories] felloffthetruck:
I just worry about cases messing with it as it's so close to the edge. :p
[Galaxy Note5 Accessories] tonys.94:
I got halo's on mine even after pressing and holding the edges for a very long time :(
[Galaxy Note5 Accessories] felloffthetruck:
Zagg Glass UPDATE: The Otterbox commuter case causes the Zagg glass to peel up in certain areas when you put on the outer shell. :(

I guess this glass is not "Case Friendly" like past Zagg glass offerings. :(

I have a UAG case coming but until then I can't use the commuter.

Just a heads up as I don't know if this glass "Full Screen Coverage" will play nice with any case.

This sucks. :(
[Galaxy Note5 Accessories] sweteg:
If it hasn't been set for a while, you will need to re align it. It's probably happening on only one side (likely top or bottom)? That tiny bit is hanging off the end of the flat area on the screen.
[XDA Assist] mustafaalweshahi:
i was flash new firmware using sp flash tool and the laptop stopped at the process of flashing and now the tab wont power or recognized by windows and nothing happen when press power and volume down what is the solution i tried to reinstall all vcom mtk drivers and use another laptop and cant make windows recognize the tap>> sorry of my bad English "ps non removable battery"
[Upgrading, Modifying and Unlocking] blackdin:
can anyone help me? Im new with PDA. What happen was i tried to upgrade my PDA, and i manage to install the satin black. after trying another os my pda doesn't want to reboot when the installation was succesful. tried hard reboot and it goes to the red green yellow and white screen. now everytime i get the spl 1.40 to install it works till 100% but after that it won't reboot. what can i do? thx. please help
[Upgrading, Modifying and Unlocking] wi_lee:
you should hard spl your x01ht first before upgrading your pda.

did you do hard spl first?

what is your radio rom, SPL??
[Nexus 7 (2013) Q&A] a4abbas:
I just bought this device a week and I haven't even rooted I wanted to install Cyanogenmode and follow through the instructions and flashed TWRP through fastboot commands from Windows7 using Minimal ADB and Fastboot [8-28-15].

I got the TWRP recovery but I am not sure what have I done wrong, when I am in the TWRP recovery, it does not show any partitions so I am unable to install any ROM on it.

I have also tried to use this thread: http://xdaforums.com/nexus-7-2013/nexus-7-2013-qa/mount-recovery-t3064562 when I flash the given recovery from fastboot commands from this thread, the recovery get stuck with bootloop. So then I restored it back to the original TWRP 2.8.7.0.

So at this point now I can only access bootloader and the recovery which does not show partitions.

At this point Is it possible for me to go back to the stock ROM somehow? Please advice. Otherwise I might be able to return it because I have only bought it few days ago.

SOLVED: To get TWRP to work, I flashed the original stock ROM from here https://developers.google.com/androi...s/images?hl=en using adb. I then flashed this TWRP multirom https://s.basketbuild.com/filedl/dev...o_20150630.img

This allowed TWRP to work.

Thanks to Batfink33 and lynnux
[Nexus 7 (2013) Q&A] elonus:
You can follow this guide to flash the newest factory image: http://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/. You should just download the latest factory image from: https://developers.google.com/android/nexus/images?hl=en the one in the guide is outdated.
[Nexus 7 (2013) Q&A] lynnux:
Join the club, I did the same thing you did with the same results(even flashing the multirom twrp after flashing the regular one, and getting the recovery bootloop). I happened to find the same instructions theminikiller posted above after pulling my hair out trying to figure out what went wrong.

This post http://xdaforums.com/showpost.php?p=62275723&postcount=558 explains what's going on. If you do the above and then flash the multirom twrp it should work fine, it did for me. I also reformatted system in adb after erasing everything, not sure if that was necessary or not.
[Nexus 7 (2013) Q&A] Batfink33:
Did the multirom TWRP work for you? I get a bootloop in TWRP when I flash that multirom TWRP posted.
[Nexus 7 (2013) Q&A] lynnux:
It worked for me, but only after erasing everything via adb and reflashing all the stock images. I got the bootloop when I flashed the regular twrp first, then the multirom twrp. Also, I'm using the most recent multirom twrp from June (I believe).
[Nexus 7 (2013) Q&A] Batfink33:
Yay, it works for me now. I had to install the stock ROM using adb then flash the multirom TWRP. Thanks!
[Nexus 7 (2013) Q&A] a4abbas:
Thanks for your replies here. Could you please give me the link to the multiroom Recovery that had worked for you? Also did you installed Cynageon mode after getting the mutliroom TWRP working? Please advice
[Nexus 7 (2013) Q&A] Batfink33:
To get TWRP to work, I flashed the original stock ROM from here https://developers.google.com/android/nexus/images?hl=en using adb. I then flashed this TWRP multirom https://s.basketbuild.com/filedl/de...//multirom/flo/TWRP_multirom_flo_20150630.img

This allowed TWRP to work.
[Nexus 7 (2013) Q&A] a4abbas:
Is it required to enable Developer options at some point of flashing it successfully? I am in China and here the google is blocked i bought this tablet and I can not get through the first screen that ask me to connect the wifi (no option to skip it unless i connect to wifi) then after loading it gets error message that it is failed to connect to internet. So just understand that I can not goto the device options right now. So is it possible to flash cynagonmode rom without enabling developer option. Please advice
[Nexus 7 (2013) Q&A] elonus:
No, it's not required. Just turn off your device. Then to boot into the bootloader hold volume down + power button until it's done booting. From there you can follow other guides to unlock the bootloader and installing custom recovery and Rom's.
[Nexus 7 (2013) Q&A] a4abbas:
I have tried to do it. But the device is not being recognized with the ADB tools on my PC. Any ideas? Could it be because of the USB debugging option?
[Nexus 7 (2013) Q&A] elonus:
When you are in the bootloader it doesn't matter if you have USB debugging enabled or not. It could be a problem with your driver's.
[Nexus 7 (2013) Q&A] a4abbas:
You must be right, it make sense.
[Android Q&A, Help & Troubleshooting] LiteGaming:
Well i rooted and flashed a System.img with FastBoot and i want to know how can i unroot because i want to try out the 1 click method then upgrade to the latest version V2.20.40.90 i dont have a linux computer so i got the system.img online also i am planning to unlock the bootloader so i can use twrp

My ZenFone 2 ZE551ML (CN)

1080p Screen

32GB of Internal Memory

4GB of RAM

1.8GHz Intel Atom CPU

I Flashed it with Fastboot with the WorldWide ROM to get it to work for me in Canada and it works but i want to update since there is alot of issues that the new update will fix but i still use alot of root since i use root uninstaller and Titanium Backup and alot of Root Benifit like moving the app to system apps and freezing and my favourite remove the Bloatware

If you guys need the System.img to check it out if its broken or something tell me and i will upload it to my MEGA Account or DropBox or OneDrive or Google Drive if any of these are blocked in you country but this is only for look at and i dont know if i am going to break the rules but sorry if i did but i am really in need since my phone i am doing new stuff and the OS is starting to get buggy and also the flash look horrible and the update fixs it

Also if anybody can make me a PreRooted System.img for (ZE551ML WW 2.20.40.90)

Well i can make it but i dont know how to and its too hard but i do have Ubuntu but the stuff

i been trying 7Hours
[Xiaomi Mi 4i] wyemarn:
Based on official spec mi4i has MU-MIMO but I'm getting only 433Mbps. My others phones and tablets can get up to 866Mbps. I wonder what speeds are you guys getting?
[Xperia Z1 Q&A, Help & Troubleshooting] Desd1nova:
Is this an easy fix, or just ignore it?

Thanks
[Xperia Z1 Q&A, Help & Troubleshooting] mo120697:
you can ignore this, it says nothing:)

but maybe delete this numbers in build.prop
[Xperia Z1 Q&A, Help & Troubleshooting] Desd1nova:
Sorted!

Turns out I'd forgotten I'd had a replacement sim and they hadnt done it their end. Asked EE for a network refresh and now its back;)

Thanks!
[Sony Ericsson Xperia Neo, Pro] goriath:
Hi everybody

I own an

Xperia Pro MK16i

. The phone is still on stock ROM (4.0.2.A.0.58 GB 2.3.4) and the bootloader is still locked. The only thing I did recently is root the phone successfully with eRoot.

Now, the phone still gets the OTA updates, right now it does notify me that the "new" update 4.0.2.A.0.62 (the latest GB release available for my phone) is ready to download. I would like to install this update in order to try it and only after eventually switch for ICS 4.0.4 (4.1.B.0.587 is the latest).

I was wondering myself:

1) Is there any way to backup the OTA update in order to save and store it for the future? I red that OTA update files end up in the /cache folder and thank to root access I managed to open that folder and see that as soon as I download the OTA update a download_package.bin is created inside the folder; the problem is that the file is less than 8MB and it's a BIN file. What this file is for and is there any way to make use of it? The only thing I know is that it's too small to be the real firmware/rom...right?

2) Is there any chance for me to get somewhere the 4.0.2.A.0.62 stock rom with the proper customization number? My phone is unbranded and purchased in

Italy

where I live, customization version is: 1249-7782_R12D

3) What does this customization mean? Is it about language? About preinstalled apps? Or what? Someone could clear me the whole thing please?

Many thanks
[Sony Ericsson Xperia Neo, Pro] goriath:
OK, I digged around about this point and just for reference I share what I found.

The main problem with OTA updates is these packages are binary DELTA packages; they are not the full ROM/FW release, but they contain only the differences between the source ROM (the firmware installed in the phone) and the target ROM (the updated firmware you want to install in the phone).

I took a look inside the BIN file with an HEX editor and what I found confirm the dependance between the update and the stock ROM:

<?xml version="1.0" encoding="ISO-8859-1"?>

<metadata version="3.2">

<product>

<manufacturer>SonyEricsson</manufacturer>

<model>MK16i</model>

<hwplatform>MSM7x30/8x55</hwplatform>

</product>

<update>

<generation>

<version>2.0.0.24</version>

<date>2012-02-01T11:01:38+01:00</date>

<rb_version>6.2.29.19</rb_version>

<rb_ua_version>6.2.29.19</rb_ua_version>

</generation>

<source>

<software>

<revision>4.0.2.A.0.58</revision>

</software>

<customization>

<variant>1249-7782</variant>

<revision>R12D</revision>

</customization>

</source>

<target>

<software>

<revision>4.0.2.A.0.62</revision>

</software>

<customization>

<variant>1249-7782</variant>

<revision>R12D</revision>

</customization>

</target>

</update>

</metadata>

This explains why my download_package.bin is large only 7.55MB; it does update (add/replace files to) the actual ROM. And this is the reason why updates through OTA are sequentials; I cannot install latest GB OTA update w/o go through every previous update first.

So this binary package alone is not useful to create a full ROM of any sort, cannot be flashed as is and cannot be extracted/unpacked/decrypted unless to be a developer and doing reverse engineering.
[Shield Tablet Themes and Apps] maze02:
Hi. I'm on 5.0.1 stock/root.

I'm on a free WiFi hotspot in Amsterdam. I use freedom VPN to bypass torrents download restrictions on that network. I used to do this no p.b for a long time.

But now, I cannot open torrents files with a torrent pro anymore. I tried all others torrents apps but it wont work.

I use solid explorer app with sdcard fixed and adaway (disabled for this). And to get freedom working with torrents download I just launch torrent app, pause download, erase feedom vpn data and restart it.

All that process worked fine on my previous tab, with latest ota (da one with the kill switch).

Here on my new tab (ota is the one right before the kill switch one) not working.

This cannot come from the ota I gess/hope

Any help if possible, would be great. Thanks

Here is a sceenshot of the error notification > /!\ttp://imgur.com/vI9FLSr (replace/!\ with h)

Edit: I found those 2 weird freedom services with disable service app. Any ideas on wait this is ?

/!\ttp://imgur.com/Dtzm8UP ( replace/!\ with h )
[Shield Tablet Themes and Apps] NinjaPerv:
Try using an app called 'flud'
[Shield Tablet Themes and Apps] maze02:
NinjaPerv [xD name]

Thanks NinjaPerv. I didnt knew that app. Will try that out later.
[Shield Tablet Themes and Apps] maze02:
Solved.

Thanks again mate. I somehow fixed all that.
[Onetouch Idol 3 Q&A, Help & Troubleshooting] STcraft:
hello, i got this phone and i love it, though its my first phone with nfc and i want to play around with some tags, which tags are nfc compatible on this phone?

Thanks. -STcraft.
[Onetouch Idol 3 Q&A, Help & Troubleshooting] kirplunk:
:good:

i use ( whiztags ) they are very universal tags and will work probably with any phone, they have all kinds of shapes, colors, key tag, stick-ons, water proof. google them.
[X 2014 Q&A, Help & Troubleshooting] skuratowsky:
Hello!

Can somebody tell me, is there some way to downgrade my XT1097 AT&T (locked) to 4.4.4 from 5.1?

I want to make downgrade because i have clean Google Now launcher, and don't have Moto X launcher after reset.
[X 2014 Q&A, Help & Troubleshooting] AGISCI:
First off it is impossible to downgrade a locked AT&T running 5.1.

Second there is no such thing as moto x launcher. The default launcher that comes on the moto x IS the google launcher.
[X 2014 Q&A, Help & Troubleshooting] skuratowsky:
OK, but it was dark/black on 4.4.4, and now it is white and ugly. And seems there is no way to return dark moto theme except of using some external launcher like nova launcher...
[X 2014 Q&A, Help & Troubleshooting] AGISCI:
Correct kitkat was dark and lollipop is white. You will have to use another launcher such as nova. There is no way currently for you to downgrade.
[X Style (Pure) General] Frank_Murphy:
I posted this in the CM12.1 thread, but I thought it's an issue the devs would be interested in and that deserves its own thread.

I've had my Moto X Pure since Thursday and I've noticed one significant (and annoying) difference between AOSP and stock: there are no heads-up notifications in stock. For some reason, Motorola has disabled them (this is my first Moto phone, so I don't know if that's what they normally do in their version of Lollipop). Normally, that wouldn't be an issue because I could just use Floatify or a similar app, but on certain message notifications, (like notifications from Gmail, Nine, and other email apps) the stock OS seems to be making the body of the message inaccessible to third-party apps. So on my OnePlus One, I could set Floatify up such that tapping a new message notification would expand it and allow me to read almost the entire message within the notification itself. But on my Moto X Pure, the Floatify pop-up only shows the sender and subject. I'm pretty sure the problem isn't with Floatify because I'm using the exact same settings on my OnePlus One. Also, I tried using Tasker and AutoNotification to intercept a Gmail notification and I couldn't capture the message body.

I suspect this has something to do with the way the Moto Display feature is implemented. Though I love Moto Display, I would like to be able to use Floatify the same way I use it on my OnePlus One. That's one reason why I might ditch the stock ROM in favor of CM12.1. Alternatively, if it's possible to cure this issue in an optimized version of the stock ROM, then I would humbly request that the devs keep that in mind as a tweak to include (thanks for all your work, BTW).
[X Style (Pure) General] Rama767:
In Settings > Sound & Notification, the last setting is "Notification access." See if checking "Floatify" works for you? On mine, all of the apps are unchecked by default.
[X Style (Pure) General] Frank_Murphy:
Yes, Floatify is checked.
[X Style (Pure) General] BootloopedMillennials:
Head ups notifications never worked for me with Gmail. Back when I had a Nexus 5 on stock even.
[8125, K-JAM, P4300, MDA Vario ROM Development] fliplyricist1:
How does one go ahead and flash to an updated Radio Rom on a G4 Cingular locked Wizzard? I am currently running NBD 8.0 using 2.25 radio and would like to try out faria's 2.69 radio...and have the nk.nbf file for the radio. Do I just flash it using ShellTool as I have done with all the other full operating systems? Is this even possible to flash the radio on a G4 locked device?
[8125, K-JAM, P4300, MDA Vario ROM Development] mdajunkie:
http://xdaforums.com/showthread.php?t=319751&page=18

im not sure if you read the nbd 8.0 thread lately but you asked this similar question and it was answered for ya :cool: if you still dont understand just mail me
[8125, K-JAM, P4300, MDA Vario ROM Development] fliplyricist1:
oh, sorry man totally missed your response :)

my only last question is, do I still copy over and run the cert and enablerapi cab's on the phone before I use shelltool, or just flash the rom without it?
[8125, K-JAM, P4300, MDA Vario ROM Development] mdajunkie:
no you dont need to run those cabs again. all you have to do is just replace the nk.nbf file and run shell tool and thats it less than five minutes and your working with a new radio. Now if 2.69 dont satisfy you look in the cingular and t-mobile radio threads i have posted a zip file with a variety of radios collected from all over the wizard forums so you can test and try them all if you like. enjoy

edit: the file should be in the first or second page of each thread
[8125, K-JAM, P4300, MDA Vario ROM Development] Azimuth21:
i don't believe that you have to use the shelltool method in order to flash a radio rom. on my first rom flash, i followed the "Faria G4 Step by step installer with instructions" and did use shelltool for the OS part, but i used the regular RUU and flashed the 2.19.11 radio with no problems, without installed the enable rapi and cert cab.
[8125, K-JAM, P4300, MDA Vario ROM Development] fliplyricist1:
thanks a bunch guys...im going to flash it now :)