yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy Note II] mid_life_crisis:
It's 3.7
[AT&T Samsung Galaxy Note II] vebulous:
That's good and weird at the same time.

Its good because its what we expected AND that the Samsung person fixed your phone even though you tripped the KNOX bit.

Its weird because the Samsung person fixed your phone even though you tripped the KNOX bit.
[T-Mobile, Samsung Galaxy SIII] carter444:
Hi Guys,

A month or so ago my mom dropped her S3 into the toilet. I told her to put it in rice ASAP and I believe a day or so later she did (but perhaps later that night). When I turn the phone on, the blue SAMSUNG (or maybe it says Galaxy) logo comes on and shows up completely fine, but nothing else after that works.

The lights around the phone work as well, including when I hit the menu and back buttons on the bottom part of the phone. It vibrates properly when it should and I also get sound, no problem.

I've tried connecting the phone to my computer to salvage pictures and data but it doesn't recognize the device for some reason.

Is the phone completely toast or is there a way for me to fix it? It was in very good condition before this and had only been used for a year.

Thanks a lot for the help. Any advice is greatly appreciated.
[T-Mobile, Samsung Galaxy SIII] carter444:
Update: I just turned it on again and I could see the FAINTEST traces of the home screen. I pulled the settings down and turned the screen brightness up all the way and I can make out everything. The phone seems to be fully functional, but the screen is still incredibly dark. Any ideas on what is broken and what I need to fix?

Once every while it flickers to the full brightness for a split second and then goes back to dull.
[T-Mobile, Samsung Galaxy SIII] Perseus:
Digitizer may have water. See if someone can take it out and wipe it down. Otherwise its a insurance call.
[T-Mobile, Samsung Galaxy SIII] carter444:
Thanks for the reply. I have no insurance on the phone so that's not an option. Would it be ultra difficult for me to try and take out the digitizer and wipe it down? Is it far too late to try and dry it out more with rice or silicate packs?
[T-Mobile, Samsung Galaxy SIII] Perseus:
Please see this thread. Perhaps you can compare notes.
[T-Mobile, Samsung Galaxy SIII] carter444:
Is there a way to confirm it's the digitizer before I pay $120 to try and transplant a new one into the old phone? I am also not very savvy at phone repair, although I could probably hire someone locally to do it.

Would like to make sure it's the digitizer first though.

I've also heard that re-dropping it in distilled water and then drying it with silicate gel packs might help clear whatever issues it's experiencing now. That seems crazy to me. Thoughts?

Thanks!
[T-Mobile, Samsung Galaxy SIII] Perseus:
I wouldn't drop it again in water. If you are not sure you can do it, then better send it for Out-Of-Warranty Repair. I can't tell you of a way to determine if its the Digitizer or not.

I "think" its your LCD having some dampness.
[T-Mobile, Samsung Galaxy SIII] carter444:
Okay, thank you. So assuming it's the LCD being damp, is it far too late to use silicate packs to bring out the moisture? Or is it time to pull it apart and wipe it down?

Also the videos I see online kind of make it seem like you can't remove the screen without breaking it.
[T-Mobile, Samsung Galaxy SIII] Perseus:
Yes give it a try. A friend of mine, tried that successfully. Your mileage may vary.
[T-Mobile, Samsung Galaxy SIII] carter444:
I followed a video tutorial online and took it apart and brushed it with a toothbrush dipped in 99% isopropyl alcohol. I let it dry for a bit and retried it and the screen was still very dark. :-/ I guess I'll try it again later.
[JAM, MDA Compact, S100 General] NashXDA:
From:	"O2 Support" <support@seeo2.com>

To:	Coolthomas_83@yahoo.com

Subject:	Mini - TT1 - General Enquiries

Date:	Thu, 4 May 2006 17:24:27 +0800

Dear Nash,

Thank you for contacting O2 Asia Technical Support.

With regards to your query below, O2 Asia has not released a camera

patch

for

the XDA II Mini. Our engineers are currently looking into the

possibility

of releasing

a Windows Mobile 5.0 upgrade for the Mini (No further news at the

moment).

Thank you.

Warmest Regards,

Mark Njo

O2 Technical Support (Email)

Asia Pacific Region

For full listing of retail outlets and information on the latest

products

information, please visit

http://www.seeo2.com

PRAISE DA LORD
[JAM, MDA Compact, S100 General] Chatty:
Dude, you're 33 days late. I doubt Mark Njo said that. And who wants that slow WM5 anyways? I'd rather have 128MB or more RAM.
[JAM, MDA Compact, S100 General] NashXDA:
Wat did u mean that i am 33 days late???

Dude are ya trying to say this is a lie???
[JAM, MDA Compact, S100 General] Chatty:
Which date did we have 33 days ago?

You can tell whether it is a lie or not by reading this thread.
[JAM, MDA Compact, S100 General] NashXDA:
Ppl i just thought u guys wud be happy to find out there was still hope..chatty buddy this was a mail sent to the guys at o2 to get asnwers this is wat i got..try and be nice i was just sharing info..
[JAM, MDA Compact, S100 General] oltp:
Yo Nash,

April fools has been long due, so I guess O2 Asia has fooled you too. I believe you in that you received this answer, problem is that the subject is just a little tensed (you'll be struck be lighting if you even think about posting something optimistic :-( )

For one of the latest camera & album version you can use this ftp://xda:xda@ftp.xda-developers.co...zard_Magician_T-Mobile_WWE_RC28_Customize.CAB

Take care, M
[JAM, MDA Compact, S100 General] NashXDA:
Thanks Buddy i get wat ya sayin
[JAM, MDA Compact, S100 General] Chatty:
Come on... be real about it. The Magician is powerful, nice and small device. But it is dead to HTC and their resellers. Optimism was nice when the device was current. It's like waiting for a new AmigaOS... useless!

The one delivering WM5 to the Magician will be celebrated forever, but I don't see any sense in opening more and more threads: "Pssst... I heard something... believe me... source is absolutely reliable... WM5 goes Magician... next month... if not sooner..."

We'll all be happy if it happens... till then we better be quiet about that.
[JAM, MDA Compact, S100 General] TheBrit:
And....if you're on a contract just upgrade to a Charmer or Prophet when the time comes.
[JAM, MDA Compact, S100 General] NashXDA:
U guys are right they just dnt give a **** abt the Magician anymore..i gonna upgrade to an Prophet soon...unless
[JAM, MDA Compact, S100 General] Lior:
That is the reason they don't (wanna) care much..

i really want a wm5 magician too but gave up long time ago.
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] ahmad5859:
hi

i buy p605 from Dubai , Jamal square last week

i have a problem in notification area , when i slide my finger up to down , nothing happens ...

90 degree turning display also tested , same situation ...

when i long press power button , it shows other page of power off , flight mode and restart that if i want to restart or power off device , i must choose a wrong answer !!!!

sometimes , it is ok and i can access to notification area , some times , no

i change the rom , but problem not solved . now i have xsg p605xxubmj4 rom on my device
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] ahmad5859:
Solved

I call it bag issue .... ;-D
[Android Apps and Games] yossio:
Create Beautiful live wallpaper APKs on the fly!

Just Express your love in words,

and we'll add the effects

App is Completely Free with ads.

You can also create from the website:

http://valentinesdaylwp.com

Have Fun & Happy Valentines!
[Xperia SP Q&A, Help & Troubleshooting] Paranoic1:
after 4.3 update,

When STAMINA is ON - LED notifications are white no matter what kind of colout I selected (missed calls, SMS,..)

When STAMINA in OFF - everything is OK, notifications are flashing in my selected colours..
[Xperia SP Q&A, Help & Troubleshooting] s.bluedreams:
Restart your phone !

i have no problem with colors in 4.3 IN STAMINA MODE !
[Xperia SP Q&A, Help & Troubleshooting] Paranoic1:
I have already restarted it many times...I also did the factory reset but nothing happened... still white colour instead of my selected colours during the Stamina mode.
[Sony Xperia L] fulcrum95:
can any one please give me the original settings.apk... I have lost mine ...and no setting option is coming... :confused:
[Sony Xperia L] exp840513:
this

ui and setting both View attachment 2578598
[Sony Xperia L] fulcrum95:
Thanks Mate :fingers-crossed::fingers-crossed::good:
[Sony Xperia L] MirDanish:
What To Do?

I lost my UI n Setting.apk on Xperia L...and my phone dont show up UI n Setting icon....After that i did factory reset and it didnt help...but when i try to install this ui n setting.apk it didnt install as 3rd party app...also i cant flash as phone is in MTP mode...Tell me what to do plz.:(:(
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] ryanbg:
Hi guys,

I am in desperate need of a raw img of mmcblk0. All I need one of you to do is get an adb shell or in terminal emulator with root type:

dd if=/dev/block/mmcblk0 of=/sdcard/unbrick.img count=524288

This creates a raw image dump I can use to help unbrick my device. It does NOT contain any sensitive data like IMEI or ESN, etc... I need MJE on Verizon Note 3 specifically. Thank you very much in advanced!

EDIT: 2/14 11:15am CST I am still in need of MJE N900V image. Surely would appreciate anyone with the time.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] TechSavvy2:
Dev Edition matter? I can offer one up if that is acceptable :)
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] ryanbg:
It's worth a shot, I sure would appreciate it.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] bftb0:
/dev/mmcblk0 is the entire device - 32 GB

Is that really what you mean?
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] TechSavvy2:
aight, give me a minute

Edit: Sorry give me another minute, had to re-root really quick

Edit: PS, any other dd's you want me to run for you while I'm at it?

---------- Post added 14th February 2014 at 12:12 AM ---------- Previous post was 13th February 2014 at 11:58 PM ----------

This.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] ryanbg:
Cancel that!!! I gave you a bad command. Just delete unbrick.img
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] TechSavvy2:
Already cancelled it out when I realized the size and time it was gonna take. Another memory block you need perhaps?

major minor #blocks name Label

7 0 21861 loop0
7 1 3150 loop1
7 2 26019 loop2
7 3 9387 loop3
7 4 2111 loop4
7 5 4190 loop5
7 6 26019 loop6
179 0 30535680 mmcblk0
179 1 15360 mmcblk0p1	apnhlos
179 2 58816 mmcblk0p2	modem
179 3 512 mmcblk0p3	sbl1
179 4 32 mmcblk0p4	dbi
179 5 32 mmcblk0p5	ddr
179 6 2048 mmcblk0p6	aboot
179 7 512 mmcblk0p7	rpm
179 8 512 mmcblk0p8	tz
179 9 10240 mmcblk0p9	pad
179 10 10240 mmcblk0p10	param
179 11 14336 mmcblk0p11	efs
179 12 3072 mmcblk0p12	modemst1
179 13 3072 mmcblk0p13	modemst2
179 14 11264 mmcblk0p14	boot
179 15 13312 mmcblk0p15	recovery
179 16 13312 mmcblk0p16	fota
179 17 7159 mmcblk0p17	backup
179 18 3072 mmcblk0p18	fsg
179 19 1 mmcblk0p19	fsc
179 20 8 mmcblk0p20	ssd
179 21 8192 mmcblk0p21	persist
179 22 9216 mmcblk0p22	persdata
179 23 2777088 mmcblk0p23	system
179 24 1048576 mmcblk0p24	cache
179 25 26521583 mmcblk0p25	userdata
179 32 512 mmcblk0rpmb
179 64 30702592 mmcblk1
179 65 30701568 mmcblk1p1
254 0 21861 dm-0
254 1 3150 dm-1
254 2 26019 dm-2
254 3 9387 dm-3
254 4 2110 dm-4
254 5 4189 dm-5
254 6 26019 dm-6
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] ryanbg:
Sorry I'm in a bit of a panic. Trying to remember how to piece together a debrick image. Appreciate your patience again.

EDIT: Here we go Link
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] xclub_101:
Actually it DOES contain sensitive data since it contains ALL 32GB of the internal flash :rolleyes:

You need to be rooted and with a decent busybox and do more like:

dd if=/dev/block/mmcblk0 of=/sdcard/unbrick.img count=524288

(this will create a 256MB image).

IMHO you also need to create the debrick image on the same family product - it would be VERY interesting if that would work from a verizon developer edition model (and I would really want to see that tested) but I have some doubts. I would also be interested if any other debrick image would work - I assume you have N900V but IMHO it would be again VERY interesting to try with a N900W8 debrick image (but be very, very careful when you later write stuff with the modem-related stuff, which is very different in N900W8 and you really want to keep your N900V modem and stuff :rolleyes: ).
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] bftb0:
I guess I need to go looking for the right threads, but is it correct to say that the SDcard unbrick method (Qualcomm phone versions) only provides a kind of volatile boot scaffolding so that the device owner can enter Odin/download mode... and that no flashing of the device occurs until the owner actually performs the subsequent flash operation using Odin? (That is, none of the content of the unbrick image is ever written to the device being rescued?)

A second question is whether version locking occurs - I thought I saw someone claiming that a prior release unbrick image, even if taken from the same device (e.g. MI9 or MJ7 prior to a MJE upgrade) will not launch into download mode - is that right?
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] xclub_101:
That is somehow true, but IMHO if all relevant partitions are wiped on the internal flash (from SBL1 to ABOOT) then all those will be read from microSD and have the code and signatures from there, and the "Odin mode" itself will be the version from microSD.

And here we have a number of interesting paths:

- the signature/hash on SBL1 itself is similar among Note 3 versions - that would result on all steps up to and including ABOOT being valid, so the "special Odin mode" will be entered; if the signature/hash on SBL1 is NOT similar between Note 3 families (or even before and after a major bootloader version) not even the "special Odin mode" will be started;

- if "special Odin mode" is started we can see another fork - if the "downgrade limitations" are part of the microSD code itself then you will be able to write any single firmware you were able to write when the internal SBL1/ABOOT was at the same version as the microSD SBL1/ABOOT - in other words you will be able to downgrade as far back as the microSD SBL1/ABOOT will let you!

- however there are some reports that the "downgrade restrictions" are actually stored in the internal flash in the "invisible/protected" regions there - and can be reset with special JTAG-like hardware:

http://forum.gsmhosting.com/vbb/f672/regarding-knox-s4-1775213/

Even in that last case there would still be a small chance that the "downgrade restrictions" might be skipped when booting from microSD since the internal flash could be considered at that point "less reliable" (or hopefully somebody at Samsung forgot to read that extra info on this special path - we can all hope :rolleyes: )

So yes, I have also seen some people claiming stuff but I would still like to see more detailed tests on it with detailed reports on what is failing at what point! And especially on the microSD with the N900W8 "happy bootloader" or even with some much earlier "early development bootloader" (I have seen something like that mentioned somewhere)!
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] ryanbg:
My theory on this (for public, bftb0 already knows) is you can boot anything that isn't fused to a lower binary counter, and since these values are inconsistent with firmware updates, it gives you a little wiggle room. AKA if A flag in ODIN is A2, you can not use an A1 aboot (MI9), but I (think) could use MJ7 since it's counter value is 2, same as MJE. These values are stored in AP RAW ANTI ROLLBACK in QFPROM. It is my belief that these values are also accessed from the shadow register as opposed to being read every time, since I was able to downgrade and replicate. I'm almost positive it's pulling these flags from RPMB. I'm extremely curious what P is since I may have full control. P1 changed to P0 when I downgraded my SBL1, TZ, and RPM to the testbit bootloader leaked by designgears, which doesn't make much since I believe all three of those have their own counters.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] bftb0:
well ryanbg can summarize when he gets some free time (and I think that there are further experiments in the queue) but an initial attempt at performing a rescue of his bricked retail SM-900V phone (which was on MJE prior to hard bricking by a TZ partition mod) using a 200 MiB dump of mmcblk0 from a MJ7 device resulted in .... nothing.

I haven't seen anything in any of the posts so far about folks talking extra precautions involving repair of the secondary GPT (after doing a raw dump of the unbrick.img to their SDcard media), so I suppose that means that the SDCard unbrick method is - when it works - supposed to be insensitive to the fact that the unbrick SD Card does not have a complete UEFI set of primary & secondary GPTs - and might even have garbage sitting at the secondary GPT offsets.

For the MJ7 trial, we used dd if=/dev/block/mmcblk0 bs=4096 count=50000 (200 MiB) which is sufficiently large to capture everything including some amount of slop at the beginning of /system (p23). I thought I saw a post where someone was using 300 MB unbrick images, making the claim that smaller sizes didn't seem to work. Doesn't make much sense though, as only about ~ 180 MB are needed for everything up to and including p22. (p1 - p22 are ordered contiguously in LBA address space on the SM-900V, and p23 is 2.7GB, so clearly an intact copy of /system can't be needed).

any ideas welcome
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] trevorcobb:
sorry to resurrect this thread, but I can't seem to find a sm-n900v debrick/unbrick img anywhere. i've found the 900T, 900A, 9005 images, but nothing for 900v.

my retail edition n900v is definitely hard bricked and I could use some assistance.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] bossnyce:
Does any one have a note 3 verizon mj7 debrick/unbrick.img
[Moto X Q&A] dys1exic:
Hi XDA Community.

Just recently bought a (Verizon) Moto X DE and am excited to join the XDA forums. This will be my first Android device (coming from iOS) and look forward to diving into rooting etc.. I've been reading and learning a lot on this forum and others since I received the phone a couple of days ago. I plan on spending a decent amount of time tinkering with my new toy and hopefully can add my experiences to the community for other newcomers like myself going forward.

A few of things I'll be starting off with based on the research I've already done:

1. Unlocking the bootloader on my Moto X DE

2. Rooting on 4.4 KitKat

3. Enabling native tethering

4. Installing Xposed and Gravity Box

5. ????

6. Profit

Let me know if you guys have any general tips or noobie advice. I don't have a ton of free time these days, but I look forward to exploring the forums further and adding any useful input where I can.

Respect.
[Moto X Q&A] rstudio:
Well one of the thing's you have to do , to post to development-related forums, is have 10 or more post's.
[Moto X Q&A] NPOA556:
Welcome! I think you will love this phone. I don't know if your list was intended to be in order, but I suggest installing the Moto Tether module in Xposed to very easily get native tethering. It is far simpler than the other methods floating around out there. Only other advice I can give you (and it looks like you are already well on your way toward doing this) is to read a lot before you ask questions. 9 times out of 10 your question has already been answered somewhere, and the old-timers around here don't like answering the same questions over and over. Enjoy your X!
[Moto X Q&A] dray_jr:
its not that we dont like answering the same questions over and over it is just we have taken the time to make these threads with all the answer and get them stickyed and no one reads them before posting lol. one of the reason why i havent created the general questions and answers yet. wait for all this 4.4.2 stuff to get over with and see what error we get before i throw it up.
[Moto X Q&A] vikramkhalsa:
Welcome! I think you'll enjoy yourself here. And the steps you've already done should be enough for a great and interesting experience. You can also try different launchers, like nova, aviate or themer, to customize your experience even more.
[Moto X Q&A] dys1exic:
Thanks all for the welcomes. Personally, I think the search-and-read-before-posting guidelines apply to most all forums and not just XDA.

Anywho, I appreciate the feed back/advice re: the tethering module on Xposed. Will definitely check that out. Also it's prolly worth mentioning that I primarily use a Mac as my main machine. I'll be happy to post any simple advice I can as I go along. I can easily boot up into Windows if I feel that its too much of a hassle on Mac.
[Moto X Q&A] SymbioticGenius:
I'm not much for welcoming, but you made a great decision by going developer edition. I would seriously research using fastboot. There are a lot of other tools here, and they all work well enough, but people left and right are bricking their phones using ez mode toolkits cause they don't know how they work and what they are really doing. Hell I'll admit I don't know how they work because they are unnecessary. I've had 3 different 4.4.2 builds from 3 different countries and never came close to bricking. Last night I finally went T-Mobile 4.4.2 I was fully stock, upgraded and rerooted and flashed recovery in 20 mins while playing video games online. Seriously, learn to use fastboot you'll thank me later.

MotoX Developer Edition went from German 4.4.2 to Great Britain 4.4.2 to T-Mobile 4.4.2 no problem. Fastboot FTW!
[Moto X Q&A] hovax615@hotmail.com:
Dude fastboot is probably the easiest thing to do as long as you have the commands in front of your face your golden.

MOTO X Slapped
[Moto X Q&A] jpd_:
I'm glad that I always use fastboot. This is probably the best advice you will ever get. Don't rely on tool kits.
[Moto X Q&A] dys1exic:
Yeah, I manually rooted using fastboot very easily. However I was slowed down a bit trying to use mfastboot at first, which didn't work. Anyone know the difference between these?

Successfully unlocked bootloader, rooted, installed Xposed/all the modules I felt like I needed including MotoX tether and a couple of other neat ones I came across. Currently trying to find a way to access Google Now commands offline, ie: set alarms/reminders without data connection. Thinking that this method should work: http://xdaforums.com/showthread.php?t=2571466 but I'm trying to figure out if I can accomplish the same thing with a free Tasker-like app.

It seems like Tasker is an absolute buy must for serious Android users. I'm thinking that I'll eventually have to just shell out the $3 for it...
[Moto X Q&A] Cozume:
mfastboot doesn't have the file size limitations that fastboot has. Where did you get your copy of mfastboot from? It is a Motorola utility so it will work fine if you get it from Motorola when you request the factory images.
[Android Q&A, Help & Troubleshooting] dingdongloop:
Ok so i wanted to change a really annoying sound in an app

but when i try the app just does a force close when it needs to load the ogg files

it recompiles, installs and runs fine until it needs to load the sounds

Is there some kind of crc check or some certain way it needs to be done?
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] luzfero:
Hey guys, I'm looking for suggestions for a stable ROM with a good battery life. I'm not too interested in tweaks since it will mainly be for watching videos.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] eushaun99:
If you also don't need much features go for Omni 4.3.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] Glyptho:
Hi, Omnirom(15-Feb-2014) from kasper_h is playing youtube fine.I`ve look transformer transformation without too many lag. Was watchable.

good luck