yashsingh1/xdaforums huggingface dataset:
[M.O.J.O. Android Development] PHYSC-1:
On recently updating the mad catz m.o.j.o to the 202 firmware which thanks to users here i managed to read about in a forum post and update it,i have stumbled on something intersting wether or not it is simply a screensaver is unknown or does it maybe hold a way to go up to another firmware with key presses?

Here it is:Go to settings then to about m.o.j.o then hang over the android version 4.2.2 words with the mouse cursor and press on it repeatedly until a jelly bean appears,then hold click on the jelly bean and voila a screensaver appears full of floating jelly beans all over the screen which you can interact with tossing them around and off screen,they will reappear,i haven't looked at this firmware yet so maybe it is just the standard screensaver they might have aded in sleep mode?

But it's interesting it is there via using the method mentioned above,i assume it is something i have found? :D
[M.O.J.O. Android Development] gwaldo:
Interesting, nearly the same as:

<Mojo> Settings -> About M.O.J.O. --> Build number ==> click 8 times, Developer options will appear in Settings

I don't think there's much there, I think it's just androids secret shortcuts.. but nothing really important would be there.
[M.O.J.O. Android Development] PHYSC-1:
It does beg the question though can anyone find any more of these secret shortcuts and do any of them do anything special? eg.unlock a backup/restore/zip loading menu for the recovery menu i found prior,or anything in regards to secret menus within the os it self?

I mean if it can ota update the firmware i wonder if there is a hidden firmware mnu shortcut key combination inside the os?
[M.O.J.O. Android Development] zektor:
Nice Easter Eggs! I recall the Developer egg...but forgot about that. Thanks for the memory refresh. The Jellybean screensaver is really cool!
[M.O.J.O. Android Development] PHYSC-1:
Your more than welcome mate.
[M.O.J.O. Android Development] Aerofreak360:
these are fairly standard android tricks guys, sorry
[HTC Droid DNA] dubsx:
So I RUU'd back to stock JB so that I could upgrade my firmware with the Kit Kat update. Yes, I decided to go that route because I heard there were issues doing it otherwise. So I updated and used Firewater, no problem. I then flashed the ENG hboot so that I could flash a custom splash screen. I flashed a custom splash and now this is what i have....not matter how many times or what I flash, I'm stuck with this. I'm afraid to try to RUU again because custom splashes are supposed to be removed and reverted back to stock. I'm stupified by this and this splash is awful. Anybody else experienced this or have any thoughts as to how to correct it?
[HTC Droid DNA] dubsx:
UPDATE: RUU'd again without any issues, other than the bootloader says "tampered" now.
[Samsung Galaxy Nexus] benkxda:
Thread link

Sometimes you just want to quickly grab the right files and you don't have time, your battery is almost empty or you're missing the matching network coverage to download the full firmware, extract it and pick out your needed files.

Below you find extracted files from the official firmwares for the Maguro "yakju" aka. Galaxy Nexus (GSM/HSPA+) by Google.

If you need more, other or less files, let me know. I want to offer the right stuff, this should be helpful.

Android 4.3 (JWR66Y) (download full image - 281 MiB)

Extracted file yakju-jwr66y-factory-09207065.tgz

boot.img 4.3MB - MD5: d1254addf766a9a1688c1a4cd72925b9

bootloader-maguro-primelc03.img 2.3MB - MD5: 35c167479ae7e277730722b659a8a6c4

radio-maguro-i9250xxlf1.img 12MB - MD5: a51c8b814b996ecf120e1af1fe2c6870

Android 4.2.2 (JDQ39) (download full image - 253 MiB)

Extracted file yakju-jdq39-factory-b2ebb5f3.tgz

boot.img 4.3MB - MD5: a92de971738281ac42dc86fc8e828a93

bootloader-maguro-primemd04.img 2.3MB - MD5: 8d8438f9b84210278e719d010d9ec32e

radio-maguro-i9250xxlj1.img 12MB - MD5: 32905a190fb4f5a53c4a5606aa722a96

Android 4.1.2 (JZO54K) (download full image - 235 MiB)

Extracted file yakju-jzo54k-factory-92ff9457.tgz

boot.img 4.3MB - MD5: a71821f220015ffe16d90bc0be2bba00

bootloader-maguro-primelc03.img 2.3MB - MD5: 35c167479ae7e277730722b659a8a6c4

radio-maguro-i9250xxlj1.img 12MB - MD5: 32905a190fb4f5a53c4a5606aa722a96

Android 4.0.4 (IMM76I) (download full image - 187 MiB)

Extracted file yakju-imm76i-factory-8001e72f.tgz

boot.img 4.1MB - MD5: fdabcc10437b6c54adfef97f4f31df08

bootloader-maguro-primela03.img 2.3MB - MD5: 5195f55cbb63c06a97639d1e56893336

radio-maguro-i9250xxla02.img 12MB - MD5: d27b18407ef7d74cc899c37a1a75ee72

23 Feb 2015

Reopened the thread, many thanks to AndroidFileHost

18 May 2014

Added all files. If you find any errors, let me know. This is "handmade" without automation scripts, so errors might be possible.

10 May 2014

Started work, uploaded files. Many thanks to Ian from Battledroid.org for hosting all these files. So again, fast downloads and no ads. Good work.

.
[Samsung Galaxy Nexus] benkxda:
Post #2

Reserved
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] iFlasher:
Since I bought the mobile I have experienced problems with the touch (the touch is not responding properly, or ghost touchs happen). Change my phone and the same problem happens, try the phone from my cousin and brother, and the same problem happens. In normal use (navigation, internet, music, reading) is not annoying, but in the games it hurts much experience, because the touch stops responding indefinitely and acts on his own for a few seconds so I have to lock the mobile for the touch working again until the problem happens again. I've noticed that the problem occurs more frequently when the mobile is hot. Definitely not if the problem is software or hardware, because the problem happens on all phones I've tried. Maybe someone can help me, because I find no solution so far.

Also all phones I tried was : i9192

Thanks :)
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] chemicalrage:
This used to happen on my Galaxy S Advance when it was hot. Maybe it happens with all phones which are hot.
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] iFlasher:
Ummm, so there is not a way to fix o reduce this problem?
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] iFlasher:
Bump! No more people have this problem? :/
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] Aronuser:
maybe keeping the display clean helps
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] iFlasher:
Maybe a Screen Protector?. I noticed that when I have moisure in the fingers the problem occurs umm....
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] Aronuser:
maybe :rolleyes:
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] iFlasher:
Ok, now I tried the screen protector and the problem persist. No more people have touch problems and possible fixs?

I don't think that I and my brother and cousin are the only with this problem.

Greetings!
[Galaxy Tab 3 Q&A, Help & Troubleshooting] brumlondon:
So, I don't know what it is, The touchscreen works, and so does the actual screen itself, but everything is discolored. Does anyone know why or what I need to buy to fix this?

so i can't post a video due to xda forums but i have a video on youtube to show, so if you want to see my problem please pm me.

*edit*so when i turn down the brightness to the bottom it almost looks fine, but when i pull it back up in brightness, it becomes a mess.

i am really unsure if this is a hour job or a replacement.
[Galaxy Tab 3 Q&A, Help & Troubleshooting] thanitos:
Im going to assume you mean it looks washed out? Try getting a gamma adjusting app
[Galaxy Tab 3 Q&A, Help & Troubleshooting] brumlondon:
I've tried, not really effecting it. it seems to be like white=red and everything is a bit mad, if you can PM me i can send you a link, it wont let me till 10 posts.
[Galaxy Tab 3 Q&A, Help & Troubleshooting] thanitos:
I emailed Samsung because my T110 looks the same no real answer though
[Verizon HTC One (M8)] roadblock217:
I'm fairly new to the modding area, I'm familiar with the VZW S3 and S4, but upgraded to an M8...I rooted, got S OFF with firewater, and booted into twrp...BUT somehow the main factory image was deleted, and I can only boot into twrp..it stays at the HTC logo if I just let it boot...help!!

Is there something similar to Samsung's ODIN mode that I can just reflash a factory image?
[Verizon HTC One (M8)] Dragbike Racer:
I'm not sure if this will help but try reading this thread, http://xdaforums.com/showthread.php?t=2718562

Hope this will help.
[Verizon HTC One (M8)] roadblock217:
Tried..doesnt work for me

I can get it to boot past the recovery area, but only stays on the white screen with the green HTC logo...

EDIT:::

I want to try it again, but now somehow I have S ON....and it says TAMPERED, below that UNLOCKED in fastboot..

Really frustrated..
[Verizon HTC One (M8)] roadblock217:
When I try this again, it keeps telling me it cannot open the file...i copy the fastboot text so that it is correct...

How can I get S OFF back if I can't boot to any rom??
[Verizon HTC One (M8)] Tigerstown:
You can get into recovery...it won't let you restore a back up or nothing ?

---------- Post added at 12:22 AM ---------- Previous post was at 12:17 AM ----------

Maybe sonic can get you s-off if all else fails with his java card. I'm not sure in your situation but I know he can do it as I used it. But I would use that as last resort
[Verizon HTC One (M8)] andybones:
So you were S-OFF and you somehow got turned to S-ON...??

I would say flash the RUU and call it a day, but we don't have one and the one we do have you need S-OFF..

best bet?

get into fastboot/bootloader, and put on a custom recovery.

then, get the TWRP nandroid of the OTA, restore to that.

then, weaksauce/S-OFF

and then you should be back to normal.

If adb/fastboot is not working, I suggest you re-install your drivers, worked for me when I didn't think it would.

opion 2

get TWRP on with fastboot

then

adb sideload any ROM to it and then get back to S-OFF

since you are unlocked you should be ok to do this without being htc dev unlocked.

you could also try htc dev, but i think that is locked.

sorry trying to think of anything else.
[Verizon HTC One (M8)] roadblock217:
I got TWRP back on, but where can I find a nandroid of the OTA? I tried doing a regular backup before things got weird but would not let me...Now I see the bug that doesnt allow to mount system...
[Verizon HTC One (M8)] andybones:
http://xdaforums.com/showthread.php?t=2725001
[Verizon HTC One (M8)] roadblock217:
Thanks...just downloaded and am going to try...

What I'm concerned about is not being able to mount /system now...this is so weird
[Verizon HTC One (M8)] andybones:
because of this, it most likely will not flash the nandroid then as system is a big part of the ROM and needs to be mounted.

you may have to do what was explained earlier and wipe the Internal, and then you may be able to re-do these steps.

so first try it out.

if it doesnt work, I would then wipe the 5 things instead of the 4

1) data

2) cache

3) dalvik cache

4) system

5) Internal storage (this will remove all your internal storage!)

then reboot from recovery into bootloader, then back into recovery and see if system is mounted, if it is, you can go ahead and either do the nandroid backup or an adb sideload. -- your choice

now,

if NONE of that works,

download the "RUU" that was put together and that *should* fix you right up.
[Verizon HTC One (M8)] roadblock217:
Nope won't work. I think it's because there is no marker folder for the m8 in my SD card where I store my backups. I tried making one, and it won't register that there is a folder there...
[Verizon HTC One (M8)] andybones:
yes.. yes it most certainly will work as my ROM is based off that precise nandroid backup...

this is something you should have had backed up..

but, make yourself a dummy nand backup to create the folder..

just don't backup anything except.. data or cache, just pick one thing. and it'll create the folder for you (tip: backup EVERYTHING (Internal., SD-Card, anything important, etc) when playing with beta ROMs. ESP AOSP beta ROMs..

the folder that gets created will be the same throughout your entire stay on the M8 using TWRP, it will never change (well that phone anyway, if you get a refurb or w.e. obv it will be different, but that phones folder markers will never change within TWRP, so it's to your benefit to have this backed up and ready to go...)
[Verizon HTC One (M8)] roadblock217:
Tried it again and again...used a different computer and it WORKED...Thank you so much for your help andybones!
[Verizon HTC One (M8)] andybones:
Awesome! :)

Very welcome.

So what was the result fix?

Did you have to wipe Internal from system not mounting?

Or did the adb sideload work?

Also once it flashed it loaded up if you did not have to wipe Internal, was your storage still there?

Glad that your back up and running.
[Verizon HTC One (M8)] roadblock217:
I had to flash the RUU but it finally worked and was applied..I'm honestly thinking of holding off on doing more to it until I learn more!

Had to wipe pretty much all except my sd card, rebooted to bootloader and back to twrp and it allowed me to write to system. BUT I couldnt get any rom to flash (when I did, it hung on the HTC logo as usual, but the aroma installer said that it was successful..so I gave up on that and did the RUU on a different computer and its back to normal.
[Verizon HTC One (M8)] andybones:
It's possible after so long you didn't give the ROM long enough to boot up?

Sounds like RUU might be a cause from flashing AOSP, threads like this are good to warn people, and for when it happens to others, they can read this and know what to do. Maybe think of a new title that could help those in a search to find this thread?
[Samsung Galaxy Gear] TyGeR_STD:
So I picked up a Gear about a week ago to pair with my HTC One. I thought if I couldn't get it to work I could give it to my wife to use with her S4 or I would pick up a Samsung phone. I would like to say I am very new with flashing roms or doing anything of the sort. So I started with doing a lot of searching on this site and reading up with how to flash the rom on the Gear to something that I could pair with the HTC One. I installed TWRP and got that working correctly when I boot the Gear into Recovery mode. What took awhile was getting the Null_23 Rom onto the Gear where I could install it. After trying to do it with ABD (and failing) I found a video that used Wonder Share. I went with this system. I paired the device with my wife's Samsung so I could enable Debugging mode, was able to pair the Gear with WonderShare and push the Null 23 Rom to it.

Went into recover, did a full wipe, then installed the Null 23 rom, rebooted unit, it ask if I want to use Apex Launcher, Nova Launcher, and a 3rd option that I can not remember at the moment. But The Apex Launcher and Nova Launcher icons are in the programs menu, I can use them at any time and change the layout of the home screen.

So after installing this Rom I am able to pair the Gear with my HTC One. Now on the Gear, I can answer a phone call, the caller ID works, I can sent the call to my phone to answer but I can not dial out to make a call from the Gear,Contact do not show up, Notifications do not work for text messaging, The seconds on the clock are correct but it will not link up in the correct time zone for the hours. Calender does not work. I can connect the Gear to the internet with pdaNET and the web browser will work. The Google Play Store ask me to log into or make a new account, but when I try to do either it stops working.

I have starting working on the notifications first, but haven't been able to get them to work correctly.

A short list of what works

Answering Calls

Clock keeps times, but has wrong hour, this is probably something simple but I haven't looked into it yet

Camera takes Pictures

pdaNET

Web Browser

Items I would like to work

Notifications,

Calender sync

Contact sync

Dial out to make call

I think if I can get these few functions to work that more will fall in line.

Thank you for any help

TyGeR
[Samsung Galaxy Gear] mr8th:
For notifications you should go with ATN Notifier, there are many threads on this issue.

For dialing out, it worked for me after syncing my Google contacts. Have you logged into your Google account? That should help, I guess. Same with Calendar sync, but this will use Internet access to be up to date and therefore drains your battery pretty quick.

I would also recommend to install Gear Manager (1.6XX) to use gear apps like runtastic, turn by turn navigation and so on. Check out Brendans Folder!

Good luck!
[General Questions and Answers] Maxie divine:
i have tried the tlctactoe aroma rom v2.5 for a500s ips and in both the cases i got a boot loop. Followed every process mentioned but still no luck..... can sum1 plz assist me.....
[General Questions and Answers] TheArc:
Did you wipe data before installing?
[General Questions and Answers] Maxie divine:
yup! did wipe data, cache partition, dalvik cache, battery stats and format system from mount and storage....
[General Questions and Answers] TheArc:
And there is still a bootloop?

---------- Post added at 11:05 PM ---------- Previous post was at 11:05 PM ----------

Just restore your backup and ask the dev and actually make sure its for you're device.
[General Questions and Answers] Maxie divine:
yup! my device is a500s ips and he also specifically mentioned "for a500s ips only"....... anyway thanx! I'l msg hom directly.....
[T-Mobile Samsung Galaxy S 4] Mr_Jay_jay:
I have been buying Skinomi Screen Protectors for little over a year now and I have enjoyed them, they protect my screen and have life time warranty plus they have a new tech glass which looks amazing almost as if u didnt have anything on ur screen . Anyway, I been getting every now and then 60% off coupon on everything you buy which is a amazing deal, I hope some else finds this as Useful as I did.

also If someone find this somewhat useful I will keep this post alive by updating every time I get a new

NO TAKERS?? SO SAD.. I MEANT WELL!!
[T-Mobile Samsung Galaxy S 4] Mr_Jay_jay:
I guess nobody likes skinomi? or none needs a screen protector.. ohh well I meant well!
[T-Mobile Samsung Galaxy S 4] Android_Monsters:
This type of post belongs in member found deals.

I'll send a screen shot. It's in the marketplace:
[T-Mobile Samsung Galaxy S 4] Mr_Jay_jay:
Thank you!!!

Damn I didn't know xda had that!! thank you so much... too bad that the coupon already expired...
[T-Mobile Samsung Galaxy S 4] johnny crapple:
Yeah too bad I was gonna check it out but forgot about it. Thanks for offering the coupon code.
[JASJAR, XDA Exec, MDA Pro General] jvoelcker:
Hi,

I am still trying to resolve an on going screen problem.:-((

When I have my Universal opened up on my desk the volume and phone dialogs and occasionally the anolog/digital clock dialog keep on appearing and disappearing.

Some times it hardly happens at all and other times it is contant, to the point that the touchscreen won't respond to other input.

When in PDA mode I get a similar situation from the same edge of the screen, but this time the scroll bars go mad.

Previous posts here have suggested either grit in the edge of the screen or dirty contacts. I have pulled the screen apart and cleaned all the contacts as well as cleaned the edge of the screen and the case around the 'affected' area.

Since the problem seems to be down to one particular area of the screen - is it more likely to be pressure from the case or a connection issue.

I'm inclined to think it is pressure from the case, but don't know much about how the touch screen matrix works.

Any help with this would be appreciated - at the moment the screen problems are rending the device pretty unusable.
[JASJAR, XDA Exec, MDA Pro General] jvoelcker:
Surely someone here mush have some ideas, this is driving me mad.

Currently running with the back of the screen off and prodding and pocking at connections to see if it makes any difference, but doesn't seem to.

Next stop is to strip down the base to see if there are any issues with the connection of the screen cable on the main board.

The frustrating thing is that the problem seem to appear and disappear - sometimes it if fine and then other times the dialogs are appearing.

When I have the dialogs appearing I try opening and flipping the phone back and forth and sometimes it goes back to normal but more often than not it doesn't.

The first thing that I want to establish is what is likely to be causing the icon area screen to appear as though it is being pressed?

Cheers,

Julian
[JASJAR, XDA Exec, MDA Pro General] oxident:
I'm definitely no hardware expert but my Universal showed a similar behaviour a few days ago and I'm quite sure it has something to do with the case and/or the cable(s) between the screen part and the main body of the device.

In my case, only a small part of the touchscreen (lower left corner) remains working and the speaker on the display side also refused to work anymore. I've applied some pressure on the edges of the display and the speaker "slowly" began to work again... and so the touchscreen did.

Good luck :?

.ox
[JASJAR, XDA Exec, MDA Pro General] jvoelcker:
Is your phone now working properly?

I have had the screen apart, but do major change. Next stop strip the whole thing down.

I'm starting to suspect the cable, but cannot see any obvious problem with it.
[JASJAR, XDA Exec, MDA Pro General] oxident:
Yes, currently my phone works perfectly.

Did you check the connectors "inside" the display part of the phone (e.g. receiver, ...)?

.ox
[JASJAR, XDA Exec, MDA Pro General] jvoelcker:
Hi,

I have opened up the back of the screen and checked the connections of the ribon cable to either side of the screen and also checked the connection of the actual screen to the circuit board.

It would be useful to know a bit more about how the touch screen side of things work bearing in mind that only one corner of the touch screen is being affected.

I'm going to try to strip down the whole phone and check the connections on both ends of the cable between the screen and the main unit to see if that makes any difference.
[JASJAR, XDA Exec, MDA Pro General] jvoelcker:
Well, I have stripped down the phone and cleaned the connections on both ends of the cable between the screen and the main board and at first for a day or so the problem appeared to have gone away, but now it is back.

I am starting to suspect that it is a problem with the actual cable, possibly a loose connection in the wires - the connectors appear OK and problem appears and disappears when the screen is flipped.

I read here that you cannot buy the cables seperately - is this true?

The next option is to take the cable out and either check all the connections and repair it, however it is a random fault so difficult the trace.

The other option I have considered is to bind the cable tightly with PTFE pumbers tape which is thin enough not to cause any problems, the PTFE will bit will help when flipping the screen and binding it might (hopefully) ensure any loose connections don't remain loose.

Any other ideas from here?
[Samsung Galaxy S (4G Model)] lyyesol:
And I searched all over. And I mean all over and could not find one. So then a stock signed GB for sgh-t959v/sgs4g that is recovery flashable and will pass signature verification, please.
[Samsung Galaxy S (4G Model)] inimeg81:
Do one click back to stock install. Search for lumin30 the link is in his signature
[Samsung Galaxy S (4G Model)] lumin30:
It is better to put all info in your post because those using the app cannot see the thread title when reading the post and often open threads without reading the full thread title.

If you do not have a workable USB port on your phone, you will likely have a problem recovering from a soft brick. Give us more detailed information if you would like to see if we can help (i.e. what ROM/kernel you were using before your issues, how you managed to soft brick, etc.).