yashsingh1/xdaforums huggingface dataset:
[LG Optimus L9 P760, P765, P768, P769] xdrc45:
Yes I know that the P760/P765/P768 are basically the same and the P769 and MS769 variant are slightly different... But that video should give you a very good idea and should be almost the exact same process in replacing the digitizer and screen.
[LG Optimus L9 P760, P765, P768, P769] reggiexp:
Repaired

Just repaired it.

13euro lol

But thr touchscreen is already broking. LoL its really a fragile phonr but i sold it to my friend for 15euro and yeah for 15euro you won't get a working phone lol so hr js happy even if the screen is already broken. It works okay the phone.

So voila it's finally repaired.
[Samsung Galaxy Gear] BuLLitz:
This is a generic question to Galaxy Gear users...

I have an app on my phone called 'Sleep as Android' that measures my sleep. It currently integrates with Pebble for better accuracy than laying your phone near you while you sleep.

A user posed a question to the developer of 'Sleep as Android' about developing the app to work with Galaxy Gear.

The response from the developer was that perhaps 'Sleep as Android' could be side loaded onto Galaxy Gear directly.

Has anyone here used 'Sleep as Android'?

Has anyone attempted to load this app directly to their Galaxy Gear?

Does it even sound doable???

I am not really interested in a Pebble watch. Pebble has poor reviews and does not appear to be even remotely appealing to me.

On the other hand, Galaxy Gear is something that I could see my self wearing and using.
[Samsung Galaxy Gear] h00rj:
I went ahead and gave it a try just for you!

I wasn't able to install it directly on the gear via the play store. Some error, so I side-loaded it by installing it on my phone first and using titanium backup's "send latest backup" feature. (you'll need titanium on your Gear as well to restore the backup)

Opens right up and appears to be running smoothly. Maybe I'll give it a go for some sleep tracking. Got a 14 day trial.

Oh, I'm using NULL_ ROM.

I guess you could side-load it using one of the other methods if you don't want to flash. (I've no clue about that stuff, however)

--update

The user interface is kinda tight on the tiny screen, but I haven't had any problems clicking on anything yet!
[Samsung Galaxy Gear] BuLLitz:
Dude, you are awesome(x2!).

If you use it during sleep, let me know how it does....

Am sure the sleeping/noise(snoring) graphs and stuff may be hard to read on such a small screen though.

There is an add-on to upload to cloud. I guess I could use THAT to see the graph details, etc..
[Samsung Galaxy Gear] lazer9:
Yea, I would be curious how this works myself. I suppose since the Gear has motion sensor, it should work for tracking sleep. The only concern I would have is battery drain. I know the app even warns of that and when I used to use this on my old Droid Razr Maxx, I would have it connected to the wall and stretched to the bed whilst on charge. Can't really do that with the goofy arse cradle system the gear has and still wear it. :silly:
[Samsung Galaxy Gear] h00rj:
Since it's meant to be ran on a phone laying next to you, you could just leave it cradled up next to you. I couldn't sleep with a watch on, anyway. End up rolling over and smacking my wife with it or something... Speaking of that, I wonder if it accommodates for two people in the same bed. Haven't really had a chance to play with it.
[Samsung Galaxy Gear] lazer9:
Lol! :laugh:True, didn't think of that.
[Samsung Galaxy Gear] ronfurro:
http://m.shutterstock.com/images/131314172/full
[Nexus 7 Q&A, Help & Troubleshooting] nickynooner:
I know. You guys have heard it all before...but

I was using WugFresh to re-flash back to 4.3 from 4.4 and the recovery was taking so long. After an hour of running, I was moving the device to a coffee table when the cable fell out.

Hay, why isn't a message include in WugFresh like the backup process as to approximately how long this process takes? That brings up another issue in general with these old N7s is that these micro-USB female connectors get loose after so many years of use, makes connecting and charging difficult.

But I digress.

I have read often in the XDA forums about a factory reset ‘from bricked feature’ in WugFresh, but I can not find that feature anywhere where ‘bricked’. anything is. If it is there, where is it?

Anyway, how can I recover the bootloader and everything without having to learn doing everything via a cmd line or .bat process?

These are the facts:

Nexus 7 2012, 8g, re-flashing back to 4.3 from 4.4, using Nexus Root Kit

v1.8.2, Flash Stock + Unroot (I had read in XDA Forum somewhere where it was suggested to go back to a factory vs to use this option).

The N7 is currently has one of 4 states available: Bootloader screen (with below stated status), Google initial screen (with "Start" Showing and "Booting failed" in the upper right corner), or it can Power off. Recovery Mode is an option, but does nothing but cycles to the Google initial screen.

In Fastboot mode the status says this:

FASTBOOT MODE

Product name - grouper (it got that far)

Variant - grouper

HU version - E3

LOCK STATE - UNLOCKED

Bootloader Version - N/A

Serial Number - 015d2109ab281807

SIGNING - not defined yet

Of course I can't get an MTP connection to Microsoft XP, but an "Unknown

device" error shows up under USB when I connect the cable. No drivers from WMSDK kit or any from WugFresh worked.

Oh, and by the way, the WugFresh backup didn't work for me. It saved next to nothing, but I have another type of backup that works, so no worry.

GOT ANY SUGGESTIONS?
[Nexus 7 Q&A, Help & Troubleshooting] Captain Sweatpants:
Looks like it will be fine follow the sticky for reflashing a factory image.

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

[GUIDE] Flashing a Factory Image with fastboot / return to stock

Don't use toolkits for flashing devices just learn the adb commands its much safer. The reason there is no time for completing a flash if it varies with devices.

FYI the wugfresh option you are looking for is return to stock/unroot with soft bricked checked

Programming is a race between engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.
[Nexus 7 Q&A, Help & Troubleshooting] nickynooner:
{Q} Thanks Captain, I have been following the Guide instruction, but I have some other questions before I proceed.

In your Quote above you said “follow the sticky for reflashing”, I don’t know what you mean by a “sticky” and I have looked though a lot of the pages after the "[GUIDE] Flashing a Factory Image with fastboot / return to stock" and I can not find “reflashing” mentioned yet. Did you mean to go directly to the "Flashing the Factory Image" section in the Guide and follow that?

Since I didn't know that answer, I went a head and read the whole Guide and other questions popped up: If I have to download Java SE JDK will the Version 6 I already have work? The Oracle website you directed me to won’t let me download Version 8; however, Android SDK did accept Version 6 to install.

I did re-download all the drivers as instructed and put the JWR66V bootloader into the place of the JWR66Y one and then inserted bootloader-grouper-4.23.img, image-nakasi-jwr66y.zip, flash-all.sh, and flash-base.sh all into <my sdk directory>\platform-tools as the Guide says.

Now that I think I have it all ready to go, will I still have to run the Adb cmds to install Drivers?
[Nexus 7 Q&A, Help & Troubleshooting] Captain Sweatpants:
A sticky is a thread that a mod has "stickied" meaning that it won't move down the forum but stays at the top.

Yes that's what I meant.

Just follow the whole guide and take it slow if you have been relying on toolkits like wugfresh this will be a not of a learning curve

Yes you still have to install drivers you shouldn't need adb to do that just make sure windows has the correct adb and fastboot drivers installed. If you have been using wugfresh NRT the drivers should be OK.

As your device is soft bricked where the guide says use the command adb reboot bootloader you will need to manually enter the bootloader by pressing power & vol +
[Nexus 7 Q&A, Help & Troubleshooting] nickynooner:
Now its Driver installation issues

{Q} Installing the driver now seems to be the issue. I tried a couple of things:

1.	I know this was not exactly appropriate, but I went into Device Manager, located the USB “Unknown Device”, tried to update

the Driver after selecting it, directed the screens to both the ‘supposed’ drivers in WugFresh and Adb subdir’s. None took.

2.	Then I forced a new device though the Control Panel’s, Add New Hardware, navigated to “Add a new hardware device” and

selected “Google Nexus 7 ADB interface”, and it created the new device. The Device Manager showed and error on the

device, so I refreshed it with the Adb driver, with no different results.

3.	I then added the device driver “Google Nexus Bootloader Interface” via Add New Hardware

4.	I rebooted the computer. After it came back up…

5.	I looked at the Device Manager with no change in the status of any of the Android or the Unknown USB Device.

6.	I insured the N7 was in bootloader mode by rebooting with volume keys/on key.

7.	I went ahead and ran “adb drivers” cmd after entering the “cd’ cmd. I got the following:

Bear with me as I have no screen printing capability at this time.

>Command Prompt screen:

>C:\<adb dir>\platform-tools> adb devices

>List of devices attached

>C:\<adb dir>>\platform-tools>

And as you can see, NO listing showed.

So what’s next? I have another XP computer I can try this on, but I will have to get all the Abd stuff over to it 1st. While you answer I will try that.
[Nexus 7 Q&A, Help & Troubleshooting] Captain Sweatpants:
Your Nexus in fastboot mode is not an adb device so it won't show up. Change your command to fastboot devices and it should work.

If you are still having driver issues download USB deveiw and remove anything that looks like a Nexus bootloader interface or adb device

Programming is a race between engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.
[Nexus 7 Q&A, Help & Troubleshooting] nickynooner:
OK, I have tried what you said with no results. If you would be willing to work with my computer directly, I have a method of allowing you to see what I see. The 2nd computer I have the N7 on right now have very little personal stuff on it, and I would be willing to let you access it. I have set up a temporary e-mail address sparemull@att.net you can send an e-mail to with your e-mail address, and we can correspond directly, thus I can give you the access you need. I know you are else where in the world, so I would be willing to leave my computer up for you to see it all when you like. What do you think?

Tell me the final score of Zebre and your teem, what date it occurred, and what the sport is so I know it is you. Send the answer to the e-mail above, so I know it is you. I’ll only give you a short time to respond.
[Nexus 7 Q&A, Help & Troubleshooting] Captain Sweatpants:
It wouldn't work as I would need to be able to press buttons on the nexus.

If none of this is working then try wugfresh NRT again make sure you have the most up-to-date version from www.wugfresh.com its 1.8.2

The option you are looking for is unroot/back to stock there is an option for soft bricked make sure that is ticked

Sent from my Nexus 7

Hit thanks if I've helped
[Nexus 7 Q&A, Help & Troubleshooting] nickynooner:
The Fat Lady Just Sang an Unhappy Song!

Hi Captain,

Thank you for all of your help and patience with me. I have read a lot more about the status of my device through looking at the XDA forum about other devices that have the kind of issue I do, and I have concluded mine is HARDbricked. I went ahead and ordered another motherboard off of eBay. My device was an 8G and I got a 32G replacement, making sure it was for my age of my N7. XDA forum and other websites say the boards are interchangeable. I was thinking about buying a new device anyway and this way I can upgrade and still have the same familiar device with no learning curve of a new one.
[Galaxy S 4 Themes and Apps] peppe130:
Hi guys.. Is there an app that make permanent my icon pack? For example: my icon pack includes the Facebook icon; when I flash my icon pack, the Facebook stock icon will be replaced by the mine but if I do any update of the Facebook's app, my modified icon will be replaced by the stock one. What should I do to make my icon pack permanent even if I do updates? Thanks :)
[Galaxy S 4 Themes and Apps] derWolf_:
I can't understand what exactly do you want, but try Unicon from the store. It changes permanently the icon of any app
[Galaxy S 4 Themes and Apps] peppe130:
I meant: if I change the stock Facebook app icon with an another icon made by me, then, when I'll do an update of the Facebook app, my custom icon will be replaced by the Facebook's original one. Now, to use unicon I have to create an app. How can I create an app with my custom icons inside?
[Galaxy S 4 Themes and Apps] Sammydaskroko:
not possible because an custom rom can include facebook app .. the app then is stored in system/apps by the rom cook.. if a update occurs the update replaces the app and stores it to /data/app .. if you replace an icon in data/apps the app will be removed and renamed .. for example to data/app/com-facebook~.apk so any icon in it is stock ...
[Galaxy S 4 Themes and Apps] peppe130:
Ok thanks!
[Upgrading, Modifying and Unlocking] shooteruk88:
Hi I'm not sure if I'm poasting I'm right place. I'm a new member to xda.

I have allot of experience in installing custom roms and rooting all my phones. I have recently bought a symphony explorer w92

And have accomplished rooting my device but now when i comes to installing cwm i cant install cwmr or twrp and I can't find any custom rom's online:confused:. my question is is there any custom roms out there or could anyone point me to the right direction for help building a rom for it from scratch so i can build one and add it for other users:highfive:. all in all the phone was a good bye duel cim card quad core prosesser and expandable 32 gb storage:fingers-crossed: thanks for taking time to read this post and i look forward to being part of the team and helping out if possible thank you:victory:.
[Upgrading, Modifying and Unlocking] Tiash420:
Nah man. Couldn't find any custom rom or custom recovery for w92. You should just stick to stock with Xposed. :P Development dekhe next time phone kinio. :P

Hit thanks please! I'm working hard helping.
[Samsung Galaxy Nexus] aatif69:
hiii there...i m suffering from unique weird problem in my gnex.....

everytime when i remove my battery or battery % is less than 10...

my phones main speaker and earpiece stopped working...it all goes on silent mode...

i have to wipe cache partition in cwm to fix it everytime it happen...

tried different roms and kernels but nothing happened.......

plz guys help me in understanding nd solving the problem....

is it a software problem or a hardware problem......

its very frustrating.....

plz help me...
[Samsung Galaxy Nexus] mrgnex:
Flash the factory image via fastboot.
[Nexus 5 Themes and Apps] jd1639:
For those who remember, I'm showing my age, and those who don't, here is the opening theme from Woody the Woodpecker.

1. rename bootanimation.zip to bootanimation.zip.bak in /system/media

2. copy http://d-h.st/Hyj to /system/media

MOVED, PLEASE SEE THIS http://xdaforums.com/showthread.php?p=52394427

MODS, THIS CAN BE CLOSED
[Nexus 5 Themes and Apps] CRIME INC.:
Oh what memories this has brought back lol

sent from my HAMMERHEAD
[Nexus 5 Themes and Apps] josemedina:
That is just awesome.

Thanks for your effort.
[Nexus 5 Themes and Apps] DaveinSoCal:
Keep getting ad pop ups when I try to DL

---------- Post added at 11:06 AM ---------- Previous post was at 10:58 AM ----------

Is there any flashing involved? I renamed and rebooted and just got a metallic android boot screen.
[Nexus 5 Themes and Apps] Tylog:
That's great :) so long time ago :) thank you

Tapatalk Team SlimRoms
[Nexus 5 Themes and Apps] jd1639:
Try changing the bootanimation.zip permissions to rw-r-r

Sent from my Nexus 5
[Nexus 5 Themes and Apps] DaveinSoCal:
Thanks for the response, will try right now.

---------- Post added at 11:45 AM ---------- Previous post was at 11:43 AM ----------

Still no dice, same metallic android boot screen
[Nexus 5 Themes and Apps] jd1639:
Maybe a bad download. Why don't you download it again and try

Sent from my Nexus 5
[Nexus 5 Themes and Apps] DaveinSoCal:
In the process of a re DL

---------- Post added at 11:55 AM ---------- Previous post was at 11:50 AM ----------

No dice, same bootscreen
[Nexus 5 Themes and Apps] jd1639:
Sorry not sure what else to tell you. It works for me and appears to have worked for others. You are using it on an nexus 5

Sent from my Nexus 5
[Nexus 5 Themes and Apps] mauslbr:
Nice to remember Woody the Wookpecker ;)
[Nexus 5 Themes and Apps] DaveinSoCal:
After a couple of re-boots the damn thing booted with the Boot Screen, very nice btw.

Woody Woodpecker was one of my favorite cartoons growing up (also showing age). All I would need is a Wile E Coyote and Road Runner, or Foghorn Leghorn and that dog he always messed with.

Thanks again man.
[Nexus 5 Themes and Apps] jd1639:
Glad you got it to work. I got a road runner, mighty mouse and Bullwinkle I'm going to try and put up this weekend

Edit, road runner. http://d-h.st/AG9. A sneek peek
[Nexus 5 Themes and Apps] DigitalUnderground:
[MENTION=3200478]Woody[/MENTION] this is perfect for you!!!
[Nexus 5 Themes and Apps] Woody:
Haha, indeed it is.

Thread Closed per OP request, but please feel free to visit the current thread here.
[JAMin, XDA Neo, S200 General] ingenious:
Hello,

I have an XDA Neo from O2 Germany and I have problems with the hardware buttons. The soft key button doesn't work anymore, the start button activates the start menu only after a few pushes. The problem appeared a week ago. The funny thing is, I had similar problems with my XDA Mini S 4 months ago. I'm using the Dopod WWE ROM from the crossvendor thread below. I reinstalled it but nothing helps. And when I was having the problems with the Mini S, I hadn't changed the OS. Is there anything that can be done? Is it indoubtedly a hardware problem?
[JAMin, XDA Neo, S200 General] ingenious:
Hm... it seems that it's because of some dust underneath. If I push the buttons stronger, they work. Is there an easy way to open the device and clean it?

P.S. Still, the Green (dial) button doesn't work at all :cry:
[T-Mobile, Samsung Galaxy SIII] zfrangi:
Hello:

Hoping someone here can help me with this frustrating issue. I have a Tmobile GS3 (stock 4.3 rom) which is giving me all kinds of trouble when I try to install custom rom. I inistally started off using the one click windows installer however I ran into trouble. Apparently the knox software was preventing me from rooting and installing CM on the phone. After doing some google seraches on how to remove knox from the phone I came across this post from this site...

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

Following those instructions I was able to root the phone and remove knox from the device and also install TWRP. Tried the one click installer again but still no luck as it would just end up returning me to the stock rom.

At this point I just said ^*&^*& it and I donwloaded the cm 10.2.1 stable d2tmo rom onto my sd card and tried to install it with CWM. I kept getting an error 7 when I do this. A quick google search brings up some pages about what to do with error 7. I tried doing what was listed here....

http://highonandroid.com/android-roms/how-to-fix-status-7-error-with-cwm-recovery-on-rooted-android/

However that still didnt work.

So I take it a step further and replace CWM with TWRP 2.7.0 using Goo Manager. Boot up into TWRP and tried to install the same rom again using TWRP but im still getting an error message TWRP goes so far and gives me the following error...

Error executing updater binary in zip '/external_sd/cm-10.2.1-d2tmo.zip'

Error flashing zip '/external_sd/cm-10.2.1-d2tmo.zip'

Any thoughts/ideas on this? Could this be an issue with CM 10.2.1? Could this have anything to do with how I rooted the phone? Could the fact that I have 2 different recoveries on the phone be causing this now?

Its been a long time since I rooted a phone (Tmobile G1) but damn I dont remember it being this hard.

Thanks in advance...

zack
[T-Mobile, Samsung Galaxy SIII] kunal1540:
This section is for i9300 only... Ask a mod to move this thread to move it in appropriate section by reporting it yourself...

Sent from my GT-I9300
[T-Mobile, Samsung Galaxy SIII] k-semler:
Do the MD5 sums match? You may have a corrupt download.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Where did you download the rom?
[T-Mobile, Samsung Galaxy SIII] zfrangi:
I downloaded the rom from the cyanogen mod download page.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Did you check the md5sum? Looking at the error though its probably because that is an older rom and isnt using the newer updater binary so its not compatible with newer recoveries.

Why not use the latest CM builds? If I remember right CM10 was pretty buggy for a lot of people.

If you want to use the old one though, the best option would be to replace the update binary with one from a newer rom. Or you could try to use a much older recovery.
[T-Mobile, Samsung Galaxy SIII] zfrangi:
Thanks for the quick reply....

I see that there are newer releases for 11.x but I don't see any stable ones. How bad are the milestone snapshots for a day to day use rom? Thats the whole reason I chose 10.2.1 since it was a stable release.

Thanks

zack
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Youd probably be better off skimming over the CM based rom threads for that. I dont use CM so I cant really speak of it either way. Just from random posts it seems to me that cm11 has been better than cm10 on this device though. But I wouldnt only go by that if I were you.
[T-Mobile, Samsung Galaxy SIII] zfrangi:
Would you recommend I flash it with the latest version of CWM?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Again this is personal preference. I personally like twrp. Others like cwm better. Both are good recoveries and should suit most of your needs.
[T-Mobile, Samsung Galaxy SIII] zfrangi:
Ok well I just tried to flash CM-11-20140210-SNAPSHOT-M3-d2TMO using CWM and im getting an error 7 when flashing it. This is the same issue I had before. Something tells me I need to just start from scratch again on the phone. IE: remove the custom recovery stuff, unroot the phone and perhaps reinstall knox?

Is there an easier way to do this...say just install the stock gs3 rom direct from samsung?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
You need to delete the assert lines from the updater script and the signature files.
[T-Mobile, Samsung Galaxy SIII] zfrangi:
I've done this before with the updater script but where do I find the signature files?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
I think they are in the meta-inf folder. Its 3 files. Cert, manifest, and another. Anytime you unzip and rezip a rom or flashable mod, whether you make changes or not, you have to delete these or itll fail at signature verification. (Or you can try turning off sig verification in recovery, but ive seen mixed reports with that.

Many roms and mods may not be signed to begin with. If those files are not there you don't need to worry about them.