yashsingh1/xdaforums huggingface dataset:
[Wing, P4350 Accessories] guro:
sorry to push that older thread, but i also have a cracked TFT-screen. does anybody know where to get a replacement TFT with touchscreen in germany?

or europe with less shipping costs?

thanks in advance!
[Wing, P4350 Accessories] moSess:
www.blackberry8100parts.com

these guys are good but i noticed the screen they sent me has developed a dent in the middle where i guess the screen is used the most. like a contour in the middle.

the reason i think its the "type" of screen they sent me is because i haven't had this problem with any other screens that I've had for longer.
[Wing, P4350 Accessories] aj255:
i cracked my wing's screen and when it cracked it also cracked the touch screen part does anyone know a good site with reasonable prices?...i was gonna send it to HTC but they asked 150 nd thats way too much
[Wing, P4350 Accessories] boogiewoogie:
my touchscreen got cracked, i ordered a new digitizer for 12 euros, this was including shipping.

does anyone have experience with replacin the digitizer apart from taking the complete lcd out?
[Wing, P4350 Accessories] fishwiz45:
you tube link

i followed this tutorial and it went very easy... http://www.youtube.com/watch?v=aN6cKRM2F1M
[Wing, P4350 Accessories] boogiewoogie:
ty, thats the one i used

unfortunately it only replaces the lcd screen and not remove the digitizer from it. But it helped me almost all the way:)

now that i have my lcdscreen seperated from my digitizer i found out the connector is different so im stuck anyway..
[Wing, P4350 Accessories] rpp293:
Is there a document tutorial of some kind?
[Wing, P4350 Accessories] arucard98:
Found a screen 11 bucks. free shipping.

http://cgi.ebay.com/ws/eBayISAPI.dl...ksid=p3907.m29&_trkparms=algo=LVI&its=I&otn=2
[Wing, P4350 Accessories] poibowl:
That is just for the digitizer part, not for the whole screen, like how they worded the listing, you can tell because you can see through the screen. most times the digitizer is fine but the lcd below is cracked and has to be replaced
[Xposed General] brute-coder:
Using Yureka CM12 rooted. Installed Xposed successfully, but modules not working no Module.list being formed. Want to make it manually please help.
[Optimus L3, L5, L7 Q&A, Help & Troubleshooting] alpengandalf:
Ok, I'll make this quick.

I've installed CWW touch, v20a, tried to root it, it kinda failed.

Now i can only go into CWM, it can't be detected by my PC and I can't install an other .kdz over CWM, I have all drivers and now i'm seriously starting to panic.

Heres the kdz log:

[R&D Test Tools Log File]

20:36:46 : Launching SW update

20:36:46 : Unpacking KDZ

20:36:56 : KDZ file extraced

20:37:08 : Files were extracted.

20:37:08 : LGMobileDL Load.

20:37:08 : Port = -1

20:37:08 : Connecting to phone

20:37:08 : PHONE WAS NOT FOUND!

20:37:10 : ===FINISHED===

I fixed it, thread can be closed now
[Android Apps and Games] Vahe114:
Polygon

View attachment 3328046

This game is created by 16 years old students . Please review the game and leave comments . They named their team Marimba Games.

Thank You!!!
[XDA Assist] smb.computers:
wana root my moto e gen I, i have upgraded to lollipop,

the device space is too low,

i have tried it to root via twrp recovery v 2.7, 2.8 &2.10

all gives error, mismatched partition size,

guide
[XDA Assist] jd1639:
I thank you for using XDA Assist. Please only post your question in one thread per XDA rules. It gets too confusing if it's in multiple places. I see you've posted here also, http://xdaforums.com/moto-e/help/how-to-root-moto-e-lollipop-t3028902. I'll close this thread.
[Galaxy S6 Q&A, Help & Troubleshooting] shiningarmor:
1 : when flashing a new rom, do i have to reflash cfroot and then twrp all over and then only flash the designated rom? Im currently on xtreolite

2: how do i check what modem/bootloader/etc version am i on?
[Galaxy S6 General] DevonSloan:
SAMPLE POST - Follow this Format

Snack Challenge

DonutMan Fresh Strawberry Donut

Stock camera

Auto, HDR-ON

Snapseed

Donutman, Glendora, CA, USA
[Galaxy S6 General] DevonSloan:
Completed challenges:

WEEK 1: SUNSET CHALLENGE - Open to interpretation. This can be a literal beautiful sunset, or it can be an abstract concept displaying the end of something.

WEEK 2: ARCHITECTURE - This can be a full building or just an architectural detail.

WEEK 3: RUST - Beautiful decaying metal... or anything else that makes you think "rust".

WEEK 4: REFLECTIONS
[Galaxy S6 General] DevonSloan:
reserved for whatever
[Galaxy S6 General] sdfsdfsfs:
Clear Skies

Snap camera

Auto, Hdr

Snap Gallery

Aridaia, Greece
[Galaxy S6 General] MM.626:
http://postimg.org/image/nwdu4md45/

Sunset Challenge

Sun outside my school

Google camera

No HDR

Stulang, Johor, Malaysia

I use xiaomi 3w

Can I participate in the next one!!?

Sorry I can't find my phone's challenge
[Galaxy S6 General] NIK516:
https://docs.google.com/file/d/0B2MI2302SlWdbjlSZHh1RnlzSDQ/edit?usp=docslist_api

Don't know if this will work but here it goes.

Well galaxy s6 edge

Don't remember settings but it was in auto .

Then snapseed with some focus repair on the shell to get more detail and then some warmth and saturation.
[Galaxy S6 General] udaan:
Suggestion and a question

Question first, since this is a challenge, do you select winner/winners and give them prizes?

A Suggestion, make a Q&A section on this thread so that we can ask questions and discuss thread related matters without breaking posted entries in the main section.
[Galaxy S6 General] DevonSloan:
We are off to a rocky start. Two of these posts are directly addressed in the top post with the challenge guidelines - if I have been unclear, let me know; I have tried to be as clear as possible about this challenge thread.

The challenge is open to all S6 owners and users using photos that have been taken with an S6. I appreciate your enthusiasm, but the Xiaomi 3w does not fit in with this thread.

Great pic! I'd advise to use Flickr, Photobucket, or any of the other free hosting sites that give you code for forum embedded thumbnails. It would just make it easier for readers to see photos without having to click on text links. Picasa is a good host that is owned by Google - maybe they have integration with Google Drive that can be used for thumbnails. (I don't use Google Drive, so I don't know.)

And remember that you can always click "Preview Post" before you post to see if your thumbnail has worked.

From the top post that everyone should read:

There are no winners, losers, or prizes. The point of shooting challenges is that as weeks go on, photographers are stretched and encouraged to shoot subjects that they normally don't and sometimes in ways they've never thought of. It's not a contest, but an exercise to come together as S6 photographers and challenge ourselves to grow and learn - but mostly just have fun and create great images.

Sadly, discussion in this thread will happen. There will be no way around it. We're only 3 photos into the thread and here we have discussion. it's also why I am adamant about having actual PHOTOS in the photo submission posts, and not just links, as it at least gives a visual cue that it's a photo submission and not just chatter.

And as mentioned in the top post, if there are any questions or suggestions, feel free to PM me.
[Galaxy S6 General] vampi369325:
Flower

Link to flickr: https://flic.kr/p/tuaRzR

Sunset Challenge

Flower at Sunset outside my House

Stock Camera

Auto, HDR-on (I think)

Snapseed to increase focus on flower

Hillsborough, NJ, USA
[Galaxy S6 General] Itaintrite:
Great photos, but I'm sure all of them violates:

17) Please only submit photos taken during the week of the challenge.
[Galaxy S6 General] DevonSloan:
Maybe, but I'm not going to check EXIF for photo dates. I think that this first week will have a bit of a learning curve and will take a bit of time before people read the entirety of the top post.

Also, I think what will also take a bit of an understanding curve is that this isn't a "challenge" to find a picture you've already taken that fits in the topic, but a challenge to go shoot something new within the week of the challenge. I have hopes that this will develop as time goes on.
[Galaxy S6 General] Itaintrite:
I agree. Used to do 365 projects until I got too lazy for that and cheated. And that kinda defeated the whole purpose. Anyway, since nobody's posted one yet, here's my panoramic view of the East River.

My sunset. by Linh Nguyen, on Flickr

Panorama mode.

VSCOCam C7 Preset (with minor adjustments)
[Galaxy S6 General] mellomelon45:
Sunset challenge

Stock camera

May 25 2015

No filter

Kentmorr Harbor, Maryland
[Galaxy S6 General] msavic6:
-Auto Mode

-HDR
[Galaxy S6 General] smilingcruel:
Sunset

Galaxy S4
[Galaxy S6 General] Itaintrite:
One more sunset shot. The S6's lens is great at dealing with flares.

Practice will get you somewhere. by Linh Nguyen, on Flickr

Auto mode.

VSCOCam F3.
[Galaxy S6 General] DevonSloan:
The new challenge is up - it's "Architecture".

Thanks for all the submissions this past week, there were some really gorgeous sunset photos. Please remember that photos should be taken the week of the challenge, and only post photos taken with a Samsung Galaxy S6, any variant. Thanks!
[Galaxy S6 General] Itaintrite:
You should edit thread title to reflect challenge change.
[Galaxy S6 General] msavic6:
I figure I'll get the ball rolling for this week. I have plenty more Archetecture shots from today but I guess I'm restricted to only posting one for now.

Auto Mode
[X 2014 General] JulesJam:
EDITED - an XT1095 owner on the 60.16 bootloader from a 5.1 soak bricked when he downgraded to 4.4.4 then took the 5.0 OTA. Several Brazilian XT1097 owners have done the same on the 60.14 or 60.16 bootloader.

THERE IS NO REASON TO DOWNGRADE TO 4.4.4 AFTER TAKING THE 5.1 SOAK IF THE 5.0 STOCK IMAGES ARE AVAILABLE FOR YOUR DEVICE!!!! Just flash the 5.0 stock images instead (system, kernel, modems, baseband, recovery - but not bootloader (motoboot) or partition table (gpt)).

Quite a few posters on the Q&A forum have hard bricked by taking the 5.1 soak, then downgrading to 4.4.4 then taking the 5.0 OTA. And unfortunately, the files that are necessary to restore their bootloaders are not available.

Obviously, taking an OTA after downgrading is dangerous. I would only flash the firmware myself or use Motorola Device Manager to upgrade if you have downgraded in the past.

Update - a poster on reddit is claiming that they did in fact take the brazilian 5.1 soak OTA, then downgraded to the chilean 4.4.4 then took the chilean 5.0 OTA without bricking. If this is true (and I have no way of knowing if it is true or not), what it could mean is that the OTA updater scripts are supposed to have checks in them that when your bootloader is not the right version, they prevent a brick.

From all that is posted on the Q&A forum, it looks like the Brazilian 5.0 OTA updater script did not have adequate checks in it to prevent bricking. IOW, human error in writing the brazilian 5.0 OTA updater script.

None of us can know which OTA updater script will be properly written and which ones will be defective until people start bricking. My advice is that you don't take the chance, because even if the chilean 5.0 OTA updater script was properly written, the brazilian one was not. Who knows what others were defective.

I would not take the chance myself (and I have MotoCare so it would only be $39 for me to get a new device if I brick) and don't see why anyone would. The Brazilians whose devices were bricked by the 5.0 OTA updater script are being denied warranty service for their devices due to having rooted in the past. They can tell they rooted in the past by the qe (root checker).

There is nothing to be gained by doing this and clearly at least one 5.0 OTA updater script does not prevent bricks if you have previously updated to the 5.1 soak.
[X 2014 General] eqjunkie829:
I've flashed the the soak and down graded twice in the past couple of months. What is happening to cause hard bricks?
[X 2014 General] AGISCI:
The bricks are caused when doing OTA after a downgrade. Not when flashing.

Sent from my XT1095
[X 2014 General] JulesJam:
It happens when they downgrade to 4.4.4 then take the 5.0 OTA as stated in the OP.
[X 2014 General] JulesJam:
Right, so I would never take an OTA after downgrading - I would only flash the firmware or use MDM (which is the same as flashing but has checks in it).
[X 2014 General] JulesJam:
I responded in the other thread.

The issue is with taking the 5.1 soak, downgrading to 4.4.4 then taking the 5.0 OTA. The OTAs are supposed to fail if your system and recovery are not stock. I am sure the issue is taking the 5.0 update with the 5.1 bootloader and partition table - the OTA updater script does not adequately protect you from a hard brick when you have a higher version BL and PT than the system/recovery version you are running.

You simply cannot downgrade the bootloader despite what some people are saying here - it doesn't happen. Neither fastboot nor mfastboot will downgrade your bootloader. If people were on 5.0 system and then went back to 4.4.4 system and they are still on the 4.4.4 bootloader, then it is because they never successfully flashed the 5.0 bootloader. If they had successfully flashed the 5.0 bootloader, their bootloader would not flash back to the 4.4.4 bootloader using either fastboot or mfastboot.

What is going on with the OTAs that I have seen is that once you upgrade to 5.1 via the soak OTA, you flash back to 4.4.4, which will flash your system/kernel/ramdisk/modems/baseband/recovery back to 4.4.4 but not your bootloader or partition table. Then when they take the 5.0 OTA, which is a patch, the OTA updater script is trying to patch the 5.1 bootloader and partition table as if they were the 4.4.4. This should never happen - it is totally a Motorola mistake. The 5.0 updater script should detect that the person is on a different version bootloader and partition table than 4.4.4 and it should fail rather than hard brick the phone. But it doesn't.

It is infuriating that these people are hard bricking due to Motorola's bad coding and they are being denied warranty service due to having rooted. Root has nothing to do with it - the OTA updater scripts should be coded to fail if the person is on the wrong bootloader and partition table.

Your qe however will show you have rooted in the past if you have ever rooted before.
[X 2014 General] JulesJam:
Not the bootloader and partition table. I explained that in my other thread.
[X 2014 General] JulesJam:
Yeah, it does - I answered your question in my other thread multiple times. Just read the thread.
[X 2014 General] wolfu11:
Actually you didn't nor did anyone else, I'll just downgrade again and see what that Motorola firmware thing is all about.

No big deal since my phone doesn't seem to brick anyway.
[X 2014 General] JulesJam:
Yeah I did, but I am not repeating it b/c I am tired of spoonfeeding people who don't know basic things yet want to argue with me. You can read the thread or don't. No sweat off of my back either way.

Because you aren't downgrading your BL or PT, lol!

Anyhow, please stop cluttering this thread. I suggest you read and learn what you are flashing then you will know. And please don't encourage other people to do dangerous things with their device when you don't even know what it is that you did with yours.
[X 2014 General] JulesJam:
Why would I do something stupid?

OK, you don't know what hearsay is. It is a rule of evidence. It has nothing at all to do with anything other than what is admissible evidence in a court of law. Completely irrelevant to anything being discussed here.

But if what you are trying to say is that I haven't done it myself so how could I possibly know - well I haven't thrown my body in front of a speeding train before but I know if I do, the chances are high I will die, lol! No, I don't have to brick my phone myself to know what could cause a brick.

I simply do not believe that all of the people on the Q&A forum who are begging for the blankflash files to be released are liars and/or making up false bricking stories out of boredom. I believe them when they say they bricked their devices and are desperate for some help.

Thanks.
[X 2014 General] wolfu11:
That clears up a lot .

Thanks
[X 2014 General] JulesJam:
FYI - a poster on reddit is claiming that they did in fact take the brazilian 5.1 soak OTA, then downgraded to the chilean 4.4.4 then took the chilean 5.0 OTA without bricking. If this is true (and I have no way of knowing if it is true or not), what it could mean is that the OTA updater scripts are supposed to have checks in them that when your bootloader is not the right version, they prevent a brick.

From all that is posted on the Q&A forum, it looks like the Brazilian 5.0 OTA updater script did not have adequate checks in it to prevent bricking. IOW, human error in writing the brazilian 5.0 OTA updater script.

None of us can know which OTA updater script will be properly written and which ones will be defective until people start bricking. My advice is that you don't take the chance, because even if the chilean 5.0 OTA updater script was properly written, the brazilian one was not. Who knows what others were defective.

I am not taking the chance myself (and I have MotoCare so it would only be $39 for me to get a new device if I brick) and don't see why anyone would. The Brazilians whose devices were bricked by the 5.0 OTA updater script are being denied warranty service for their devices due to having rooted in the past. They can tell they rooted in the past by the qe (root checker).

There is nothing to be gained by doing this and clearly at least one 5.0 OTA updater script does not prevent bricks if you have previously updated to the 5.1 soak.
[X 2014 General] JulesJam:
Heads up peeps - the XT1095 5.1 soak OTA updater script does not have adequate checks in it to prevent a hard brick if you have downgraded and then attempt to upgrade again.

http://xdaforums.com/showpost.php?p=60941697&postcount=132

So this is just like the Brazilian XT1097 5.0 OTA.
[X 2014 General] JulesJam:
Please read the edit to the OP!!!
[X 2014 General] Xdevillived666:
This happened to me and I'm so frocking pissed I didn't see this thread beforehand!! Does anyone know if a JTAG service could fix this or how Mich Motorola would charge to repair?
[X 2014 General] ajanu:
Just to be clear on this issue. I can't find a 5.1 RETCA image, and MDM only gives me " No Update available" I have been on 5.0 pure edition with 4.4.4 RETCA modems for a long time. Can't OTA a phone that is 1097 but thinks it's 1095. The filefactory link has broken modems, just like the OTA that bricked phones in Canada so I was still on 5.0 with 4.4.4 modems.

I downgraded to 4.4.4 RETCA with fastboot, the partition failed but everything else flashed. Since I have not gone to the 5.1 partition or bootloader flashing 5.0 through an OTA should not cause issues correct?
[X 2014 General] JulesJam:
If you are back to stock 4.4.4 - the correct version for your device - everything stock (no root, no custom recovery etc.) and take the 5.0 OTA for your device, you will not brick.
[X 2014 General] adm1jtg:
I have posted before but will re-post.... to get to 5.1 you dont need to use the OTA you certainly can but you can also just fastboot flash the system.img and boot.img

I have used this method to go to 444 and to 5.1 and back and forth successfully. This way you dont change the bootloader and eliminate the chance to perma-brick. Notice i said perma-brick as you can easily still soft brick but not formatting or clearing cache but I have gone back and forth enough times that I think is pretty safe to say if you dont mess with the bootloader or gpt files at all and you never take an ota you will not perma-brick
[X 2014 General] JulesJam:
He can't find those for 5.1 for his device.
[X 2014 General] adm1jtg:
Could someone not help him out and either make a dd dump or twrp backup of those partitions and post them for him? I guess not or he wouldnt be in this mess
[X 2014 General] JulesJam:
As long as he is 100% stock on 4.4.4 he can just take the OTA.
[X 2014 General] FiyreWyrkz:
So - I pulled a dipsh*t move... I had sort of recalled reading about bricks after downgrading/upgrading, but stupid me was trying to go back to the RETCA version of the phone from the TMO 5.1 and I've ended up bricking my phone after taking the OTA from the 4.4.4. RETCA that I downgraded to.

I've tried searching through this thread and googling all over the place. I'm stuck with the "QHSUSB_DLOAD" which I've been able to install drivers for and have the "Qualcomm HS-USB QDLoader 9008" COM port functioning. I'm hoping someone might be able to point me in the right direction for the proper bootloader files to flash for the Moto X 2014?

*EDIT* Not holding my breath right now given the info in these threads.

MPRG8974.hex and 8974_msimage.bin (MSM8974_bootloader_singleimage.bin) for MotoX 2014

[Q] How do unbrick in Moto x 2014 (snapdragon 801 MSM8974AC)?
[X 2014 General] JulesJam:
What bootloader are you on? Are you on the 4.4.4 bootloader or the 5.0 bootloader? And if you are on the 5.0 bootloader, is it the correct bootloader for your device?
[X 2014 General] JulesJam:
To clarify - 100% stock means the 4.4.4 bootloader and partition table too. If everything is 4.4.4 for your device - bootloader, partition table, logo, kernel, system, recovery, modems, basebands - then you can take the 5.0 OTA.
[X 2014 General] JulesJam:
Again stock 4.4.4 means you are running the 4.4.4 bootloader and partition table.
[X 2014 General] JulesJam:
Just to clarify, you have a RETCA XT1097 and upgraded to the XT1095 5.1 including the bootloader and partition table, then downgraded to the RETCA XT1097 4.4.4 and took the 5.0 OTA?
[X 2014 General] JulesJam:
The files haven't been released by Motorola. Can you make a warranty claim? The OTA files should have checks in them to prevent bricking so this is Motorola's fault.
[X 2014 General] FiyreWyrkz:
Yeah, that would be an accurate supposition. When I went back to RETCA XT1097, I'm pretty sure the motoboot.img (bootloader) wouldn't flash through fastboot, nor would the patrition table (gpt.bin)... Can't quite recall.

I don't think I have warranty anymore. Might just get sold for parts at this point. Looks like I'm going to have to find a digitizer/lcd formy old Nexus 4. ='(
[X 2014 General] JulesJam:
Right, since you had upgraded to the 5.1 bootloader and partition table (which btw you didn't have to do since the 4.4.4 bootloader and partition table work fine with 5.1 system, kernel, radios), when you tried to downgrade them it failed. With very few exceptions, you can't downgrade motorola bootloaders and partition tables. It will fail or you will brick. In your case it failed.

Then you took the 5.0 OTA and it applied the patches as if the bootloader and partition table were still 4.4.4, but they weren't, they were 5.1. That caused the brick. The 5.0 OTA should have checks in it to prevent that, but it doesn't. Bad coding on Motorola's part.
[X 2014 General] JulesJam:
Idk about Canada, but in the US you have a 1 year warranty and the phone hasn't been out for a full year yet. At least on the US site we can check our warranty status online.
[X 2014 General] ajanu:
I was on the 4.4.4 bootloader but the 5.0 partition table. For some reason the bootloader downgraded but the partition failed. I took all OTAs and I am now running 5.1 with no issues.

All of this could be solved if Motorola would just release every firmware version as soon as OTAs start rolling out and allow anything to be downgraded.
[X 2014 General] JulesJam:
IMO they are never going to allow the bootloader to be downgraded because the bootloader is responsible for enforcing security issues. When they find a flaw in the bootloader that makes it less secure, they patch it and don't want you to downgrade to a less secure version.

What needs to happen to stop this is for Motorola to code the OTAs so that they do a check for bootloader version number and fail if the bootloader is not the correct version number. I IF-THEN statement in the code would fix the issue.