yashsingh1/xdaforums huggingface dataset:
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] koftheworld:
Why not apply yourself to figuring out how to root 5.1, maintain root upgrading to 5.1, or how to use mofo to flash 5.1? I think people care more about that then anything else.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] SaschaElble:
Because I've spent countless days on 4.4, I know how it works. Its actually pretty simple, way less complicated than when I first started with it. And I rather help those that were smart enough to stay on the 4.4 bootloader and waited for the mofo flashable 5.1 rom. Because anyone who cared or even had the fainted idea about exploits knew better than to upgrade, when they could STILL get 5.1, but would have to wait... like what less than a week before the first flashable image appeared?

5.1:

How it works: Nobody has a clue because the 4.4 loophole is patched.

4.4

How it works: (I'm just making an example don't pick apart my math or partition sizes)

system.img = 3.5gb

cache partition = 1.5gb

So with a modified fastboot, you will write to the cache partition, but send more than 1.5gb of data, since the /system partition is next in order anything you send now will actually write to /system and not the /cache partition.

There are a few quirks I've seen, fastboot sends the "download" command 2x back to back, while the first "download" command hardly sends anything. This has something I assume to be "fake writing" Not quite sure. Its like it writes a tiny amount of data to /cache, sends the second "download" command to now write to /system. I've noticed that the data sent to /cache is actually a clone of a portion of the data sent to /system. Also there is 3gb of ram on the device, so after that gets filled up, the flash command is sent, then it goes back to download commands.

At the end it erases /cache because its full of garbage.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] koftheworld:
Fair enough that is exactly why I stayed on kk.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] SaschaElble:
I still have not had anyone help out. If done right, nothing will be wiped or corrupted. Just need someone who has flashed a modded /system using mofo and still have that .img file. Flashing the same file again wont harm anything and will get me the info needed.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] Michaelmansour1997:
Does anyone have any info on the lolipop .img s
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] TheSt33v:
I'm interested in helping, but I'm not interested in giving you remote access to my computer. No offense, I just don't know you and really have no reason to trust you. If you give me instructions on how to generate the log file that you want, I'll be happy to do it. I'm tech savvy enough to modify system images, so you shouldn't have to dumb it down too much for me.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] Michaelmansour1997:
just use a vm...
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] TheSt33v:
Good idea. I'd be willing to do that.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] SaschaElble:
Okay,

Download USBlyzer

Turn on device in fastboot mode

Open USBlyzer

On the left hand side of USBlyzer, watch, while you plug in the device

checkmark the new device in USBlyzer in the left hand side (should say xt1254 or turbo or fastboot or anything that indicates the turbo)

click "start capture" in USBlyzer

Open mofo and flash your rom as usual.

When mofo is done, go back to USBlyzer and save the capture log where you will remember.

That log data contains your device serial and UID for your turbo... Thanks for helping the turbo community!
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] SaschaElble:
That should work
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] TheSt33v:
I think I can handle that. Unless you were planning on coming to my house with a flash drive, I'm pretty sure a large file transfer was inevitable, so I'm okay with uploading it somewhere. Thanks for the info about the sensitive information though. If I can figure out how to remove that from the log, I will do so before sending it to you. If I can't, I'll consider sending it to you anyway. If I can't do any of that (because, you know, apparently I'm a moron for not immediately realizing that I could use a VM to have you do this exact same thing), then sorry for bugging you.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] SaschaElble:
Open the log (ends in .ulz) in a hex editor such as HxD, and you can zero out your serial and UID, I apologise for the rude response. I've surprisingly had lots of resistance getting everyone on the same page here on xda. I did screw up by posting a modded mofo package, but that needs to be water under the bridge. I'm working on making a legit version.

The part that was surprising is how a few people had the knowledge on how to make a clean and 100% original version but refused to share it or gave vague hints.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] TheSt33v:
No worries. I've been following your posts. I don't really care about who you piss off. You seem to be knowledgeable/talented enough to recreate and improve upon mofo, and that's good enough for me. Just promise me that you'll send me a copy of whatever you come up with if you get yourself banned again :).

I'll start the process as soon as I'm near my PC, and I'll pm you a link as soon as the upload is complete.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] SaschaElble:
lol. I will for sure! But I won't get banned again. Not if everyone plays by the same rules they expect me to.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] SaschaElble:
Anyone is free to contact me at (Edit: I was such an idiot. 5 years later... wow. ) If you want an easy two click way to get onto my channel on IRC follow the link in my signature.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] Michaelmansour1997:
if i was rooted id help, but i have one turbo on lolipop and one bricked which is supposed to be on lolipop
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] SaschaElble:
I would buy the bricked one, or you can let me see if I can fix it remotely.

NEW:

My vouching thread for those who I request access to their device remotely or gain knowledge of sensitive information:

http://xdaforums.com/general/off-topic/saschaelble-vouching-thread-want-help-t3150299
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] Michaelmansour1997:
Do you have a hangouts
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] TheSt33v:
Sorry for the delay. Installing USBlyzer on my Windows 8.1 Pro x64 machine results in a BSOD on reboot. I'm in the process of setting up a Win7 VM to see if I have better luck with that. If you have any alternatives to USBlyzer (windows or linux is fine), please let me know.

EDIT: The VM is working fine. I'm doing the flash and generating the log with USBlyzer now.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] TheSt33v:
Uhhhggg. USBlyzer stopped the capture because it ran out of buffer space. I have the buffer set to the maximum (1 GB). How can I remove this limit? I need to go to bed. I'll mess with this more tomorrow.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] SaschaElble:
Weird, it should just keep flushing to the file. Also I don't see a 1gb limit anywhere,

under capture settings :64kb max

under options preferences : capture : Temporary Capture File I have set to 256mb
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] TheSt33v:
I was referring to the size slider of the temporary capture file. It won't go higher than about 1 GB. I'm trying again with the settings that you mentioned now.

EDIT: I got the same message, except much sooner this time (probably due to the decreased temporary capture file size). It says "Capture buffer full. Capturing stopped." I think I remember you mentioning before that you only needed to see the last part of the flash. Do you want me to crank the temporary file size back up to 1 GB, wait until the flash is at about 50% and start capturing from there?
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] SaschaElble:
The temporary file size maxes out at 256mb. I'm on win 8.1 x64 with 12gb ram. I have no problem.

You're VM is the cause of the problem. Feed it more memory
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] TheSt33v:
Are we using different versions of USBlyzer? I'm on 2.1 b 39. See attached screenshot. This was taken after I upped the VM ram from 8 GB to 14 GB (I have 16 GB in my host system). Doing this did not change the maximum temporary file size, which is 1024 MB. I'm not sure why this size would be related to the amount of available RAM since the temporary file is stored on the hard drive.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] SaschaElble:
Using 2.0 Build 25

Weird, I get 800+mb files with only "256mb" temp capture.... (and I only get 256mb max)
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] TheSt33v:
Okay, after a lot of frustration, this is what I managed to do:

1. I retried the process on my Surface Pro 2 (yes, I'm one of the two people in the world that bought one). USBlyzer installed fine on this machine.

2. I started the capture, then started the mofo flash. I let the capture go until it reached 1024 MB, where it gave me the error message and force stopped the capture.

3. I saved the file as quickly as I could, and I restarted the capture. Mofo finished, and then I saved this log.

4. The two logs end up being about 1.5 GB unzipped, which is significantly smaller than I think you were expecting.

You can download the logs here: https://drive.google.com/file/d/0Bz1f5-grRw5BYlhHQTRDWnp5Sk0/view?usp=sharing

Please let me know if they contain the info you need. If not, I'll try to find the version of USBlyzer that you are using and I'll take another crack at it.

The log files are named 1-64 and 68-100. The numbers represent the percentage that mofo indicated when the logs were started/stopped. 65-67% was lost due to the time it took to save the first log.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] SaschaElble:
I know how to get it all, open the filter and check mark everything like this: (you won't see a lot of activity. But I have enough plus this last complete run to make it happen.)

THANK YOU FOR YOUR TIME. You get the first copy of anything I ever make for the Turbo.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] TheSt33v:
You're welcome! Good luck.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] wrecklesswun:
I'd be willing to try. I am setup. We can use team viewer if you'd like.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] SaschaElble:
close. jcase for the win. Congrats.
[AT&T Samsung Galaxy Note 4] privatewarrior1:
Besides the regular internet speed tests, is there a definitive website and/or app that allows you to say for sure that your device is being throttled.? I've been working on this for a week now but cannot find a good and specific answer online.

Thank you
[AT&T Samsung Galaxy Note 4] privatewarrior1:
Another difficult question
[AT&T Samsung Galaxy Note 4] NickOlsen8390:
No, There isn't a way to definitively say you are throttled or not.

There are many more larger questions here.

For instance, Define throttled. Are you referring to a specific rate limit set on your device? Rate limit as in, Traffic exceeding the rate limit are either queued, And sent at a lower rate period (Packet Scheduling). Or dropped (Rate Limiting).

I doubt ATT has placed a rate limit on your connection. They are in the business of having happy customers. Specifically making your connection slow is bad business to them. Now, Placing limits

Now, Another form of limiting could be construed into how their gear is setup. Let's say they are running a 5Mhz LTE channel. Which is capable of 20Mb/s up/down. But the gear technically can run a 40Mhz LTE channel giving you 400Mb/s up/down. Are they "Throttling" you because they choose not to run the gear at it's highest operating spec? You could say that. But it's a horrible way of looking at it.

Finally, the better question is what does it matter? In my youth I spent many a day trying to find data like this. If your service is working poorly. And your expectation is to provide proof of throttling in some attempt to change your service. I can tell you. Don't waste your time. Even if you had proof. No one at ATT cares that you found out you were throttled. Or care to do anything about it.
[G4 Q&A, Help & Troubleshooting] Joeful:
Will the color sensor still work correctly if it's scratched?
[General Topics] NASA1970:
I was hoping someone could start a device tread for the Lenovo TAB 2 A10 Tablet. I'd like to see if it can run stock Android Lollipop (like a Nexus 6 or Nexus 9) and learn any developing tricks. Excited about rooting, developing and all that is involved.

Thanks.

Frank
[General Topics] Magnum_Enforcer:
You can make your request in the thread linked below.

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

Thread closed.
[T-Mobile, Samsung Galaxy SIII] Lt1streconbn:
You can't... It has to be extracted from the ROM as far as I know. Anyway, there isn't much need to upgrade a boitloader, and its by far the most dangerous item in the firmware to disturb. Unless you have a reason requiring it to be upgraded, its best left alone, or just go up to the next full stock ROM with a new bootloader included.
[G4 Q&A, Help & Troubleshooting] rzkman:
Hi all,

I have had my H815 (Taiwanese version) for over a month now with no issues. Starting last night whenever I take a photo with the rear camera a green spot appears in the viewfinder. This green spot is also captured in the photo as per this sample

http://imgur.com/QGE1X0C

When I pan the camera the green spot disappears, but as soon as I hold it still, it appears again. No issues with the front camera. Any ideas what might be causing this? I updated to V10b last night, but I am not sure if it is related since I haven't seen any other reports of camera issues.

Hardware fault? Would appreciate your input.

Thanks,

Ray
[G4 Q&A, Help & Troubleshooting] shook187:
Did you remove the protective film that was on the lens?
[G4 Q&A, Help & Troubleshooting] Arctic Prodigy:
Some cases have been proven to interfere with either the laser or the flash.
[G4 Q&A, Help & Troubleshooting] rzkman:
No not a protective film, has been working without issues for the past month .

Not the case either as it has been the same case and I tested taking off the case and cover too.
[G4 Q&A, Help & Troubleshooting] Rapazzo:
Have you tried covering up the ir sensor to see if that makes a difference?
[G4 Q&A, Help & Troubleshooting] siraltus:
The spot is in the shape of the autofocus laser window. It's probably something to do with that.
[G4 Q&A, Help & Troubleshooting] stuarty211:
i have noticed the same thing but have noticed that there has been a recent update to the software. dont know if that is causing the problem
[G4 Q&A, Help & Troubleshooting] J1mmyCrackCorn:
I've been experiencing the same thing just this past week now. It seems to come and go depending on how the lighting is. I thought it had something to do with the laser autofocus because it seems to be in the same area of the screen. It's kind of annoying trying to take photos with its awesome camera and have them ruined by this strange green dot. Hopefully it can be fixed. You're the only other person I know of that has had the same issue as me so far.
[G4 Q&A, Help & Troubleshooting] nicolas_s:
I have received my G4 one week ago (Switzerland) and I have this green spot that appears sometimes since today but I have not played a lot with the camera this week.

I have not the spot at the same place. Mine is near the flash.

w w w.dropbox.com/s/hg1ie6rm0kmviwc/20150719_145148_HDR.jpg

Sorry for the link but I'm not authorized to share a link..

Envoyé de mon LG-H815 en utilisant Tapatalk
[G4 Q&A, Help & Troubleshooting] phineous:
I saw the green spot for the first time yesterday. Mine was very faint, and it didn't show up in the photo, only in the preview screen.
[G4 Q&A, Help & Troubleshooting] NocturnalDroid:
It's a ghost.
[G4 Q&A, Help & Troubleshooting] RedOCtobyr:
- Do other camera apps show the same green spot?

- Is it only in certain modes, like Manual, vs Auto?

- Does it appear in videos?

- Someone asked about the laser. You could try covering the laser's window, to see if anything changes.
[G4 Q&A, Help & Troubleshooting] nicolas_s:
- I have the same green spot with other camera apps

- I'm able to reproduce in all modes

- Same spot in videos

- I have removed the battery cover and I have covered the laser but no change.

The spot seems to appear depending the luminosity.

Envoyé de mon LG-H815 en utilisant Tapatalk
[G4 Q&A, Help & Troubleshooting] J1mmyCrackCorn:
So after chatting with LG support they told me to do a hard reset. After I did that the camera still had the same green spot. Definitely a hardware issue. Took it back into Sprint and they gave me a replacement phone. The guy there told me that it's a manufacturer defect on the first batch of phones that is becoming more common. Got a new G4 today. Camera looks fine now. We'll see how it holds up.
[G4 Q&A, Help & Troubleshooting] alain57:
now imagine you had unlocked the bootloader and removed the warranty ....
[G4 Q&A, Help & Troubleshooting] stuarty211:
green dot

its really annoying this issue. i have contacted lg and they have send my phone away to repair the camera. i thought it was a software issue tho, because it happened just after and update. but lets hope this replacement camera fixes it. i have not seen this issue reported anywhere else than here.
[G4 Q&A, Help & Troubleshooting] stuarty211:
Lg has got back to me and said that my phone needs a new main board.
[G4 Q&A, Help & Troubleshooting] SchootyBoo:
Green blob

I've been dealing with this for about 2 weeks. First noticed it while taking a picture of the sunset (right around when I got the new update). Showed up again today when the I was trying to take another picture outside. Seems to only do it when the sun is around and my phone is running a little warm. So annoying. Definitely ordering a replacement, because this should be covered under warranty.
[G4 Q&A, Help & Troubleshooting] :
I didn't have any issues with this green got untill I flashed the PR verison of the ATT's rom. I'm hoping this is an easy fix of just replacing the camera. I have an LG g4 coming work for a replacement and I can harvest the camera out of the device and replace mine.
[G4 Q&A, Help & Troubleshooting] :
Replaced out the physical camera with another from another device and the issue was was resolved.
[G4 Q&A, Help & Troubleshooting] RedOCtobyr:
Interesting. How hard was it to replace the camera?

It looks like a replacement camera is about $25 on eBay, if another user had to replace their camera.

http://www.ebay.com/itm/Original-OEM-Rear-Back-Main-Camera-MODULE-FIX-For-LG-G4-F500-H815-VS986-H810-/121695589354?pt=LH_DefaultDomain_0&hash=item1c559f53ea
[G4 Q&A, Help & Troubleshooting] :
Pretty easy, then again I am a phone repair tech lol. Remove the back, detach mother board then just remove camera and replace.

The phone still does the weird vibrating thing even after I replaced the camera, so i'm not sure if its still a software bug that cause it to it. It sounds like buzz/hum so I think it may be burning out the cameras like what the HTC ones did with their "purple" images issue.
[G4 Q&A, Help & Troubleshooting] :
Seems to be the when using the flash/flashlight it makes the vibrating/humming noise.
[G4 Q&A, Help & Troubleshooting] RedOCtobyr:
In some earlier testing, I can make my phone make a "clack" sound if I move the phone around quickly while in the camera app. But I cannot cause this noise with the camera inactive.

My theory is the noise is due to the OIS running. It either actively tries to move the camera too far with the OIS, hitting something. Or it's simply because the lens is "unlocked" from its presumably-secured home position (when it's not active), and is able to kind of bounce around, hitting something.

I can reproduce the noise when using the flashlight. But since flashlight apps need access to the camera in order to activate the flash, my guess is the camera is also active when using the flashlight. And therefore the same OIS-caused noises are possible.

However, I have never noticed any buzzing or humming from my camera, fortunately. It seems strange to me that you still get the noise even with a replaced camera. The noise coming from the camera itself seems reasonable. So you'd figure a replacement wouldn't cause it.

Though on reflection, maybe the OIS is driven/controlled by the phone's gyroscopes & accelerometers, not sensors internal to the camera? Perhaps one or more of the phone's sensors (presumably on the MB) is not functioning correctly, and is giving bad signals to the camera, causing the camera's OIS to freak out?

CPU-Z shows the sensor outputs from the gyros and accelerometers. You might install that to see what they're reporting, to see if there's something weird?
[G4 Q&A, Help & Troubleshooting] :
I had orginally just changed the back out to see if the Green line was caused by a sensor issue, as the flash and color sensor are attached to the back plate on the device. I replaced my orignal back on the device because it shows all the model numbers (thought when I had returend my lg g3 to ATT that sprint model numbers on it they didn't seem to care). Switching out the camera removed the line spot, which I assume gets burned into the device. I'm going to change out the back plate and see if that resolves my humming issues while the flash is active.
[G4 Q&A, Help & Troubleshooting] :
Came back completely again. Meh
[G4 Q&A, Help & Troubleshooting] user787:
My device is the PR version, from carrier Claro. There is not an att PR version, is the same here than the States (as far as I known). Experienced the green spot issue yesterday. I have three weeks with the device. Never happened before. I tought it is related with the digital autofocus vs light exposure. Happens to me in auto mode. It did not happen in Simple mode and Manual mode. Maybe is not hardware related and could be solved with a firmware patch... I mean update.

Regards
[G4 Q&A, Help & Troubleshooting] bobimbap:
There is not an AT&T PR version. It just happen to work for AT&T LG G4. Thanks for clarifying the greenspot on your phone
[G4 Q&A, Help & Troubleshooting] RedOCtobyr:
That is very interesting. I have observed behavior being different in Simple and Auto modes, vs Manual:

http://xdaforums.com/g4/general/pictures-flash-saved-exiting-coamera-t3169818

That thread is about pictures not saving if using the flash in Simple or Auto, then exiting the camera app right after taking the picture. But Manual mode saves the picture correctly under those conditions. It seems to me to be a bug in the Camera app.

If you can eliminate the green spot when using certain camera modes, that would certainly imply a software issue. Does it appear in RAW (DNG) pictures rather than the JPGs, if you can get the green dot in Manual? Do other camera apps show the green dot?
[G4 Q&A, Help & Troubleshooting] faizalotai:
Yeah, after mentioning that..i've checked raw file and guess what..there are NO green spot on it
[G4 Q&A, Help & Troubleshooting] RedOCtobyr:
Wow. So it is presumably being added by the Camera app while processing the image.

Can anyone else with the green spot confirm that the spots are not present in the RAW (DNG) image?

I emailed LG about the apparent bug I found, with a link to the thread I'd made. If this is a software issue, I'd want to make sure they're aware, with as much info on how to reproduce the issue as possible. Especially since it does not affect all phones.
[G4 Q&A, Help & Troubleshooting] nicolas_s:
I have just tested and no green spot on DNG images.
[G4 Q&A, Help & Troubleshooting] kazak1911:
wow your green spots are much worse than mine. However, mine appear everywhere doesnt matter which mode the camera is on. Somehow they disappear when i take pictures indoor. I guess it has something to do with autofocus and exposure
[G4 Q&A, Help & Troubleshooting] :
I get them while he camera is in raw model still :/