yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] XQuisite:
Hello everyone...

Just wanted to know if someone's Galaxy Nexus came back from the brink of death after going in the water. I can't say how submerged the phone was and it was a very quick dunking. Long story short as soon as I realized that the phone was dunked and still on, I pulled the battery and let it sit with the cover off of course.

I've gently heated it and it is now sitting in rice to try to dry it out. It's post 5-6 hours from the incident.

What the phone does now when I try to boot up on ParanoidAndroid 4.3 is that the color PA logo boot up screen continues color cycling but the phone never completes the boot.

I can get into recovery with CWM and tried re-flashing the ROM but it does the same thing.

Any other ideas? Or just sit and wait? I'm back on my old Moto Defy for now. Which is a mixed blessing, loved this thing.

TIA
[Samsung Galaxy Nexus] wastedlife:
Did you have the mpokang kernel or any other with dynamic fsync enabled? You may need to wipe your data partition because pulling the battery may have corrupted it. The fact that you can boot into recovery is a good sign though.
[Samsung Galaxy Nexus] XQuisite:
I don't think I had the mpokang kernel installed. I'm not even sure what fsync is, as I'm only as deep as ROMS and GApps in my knowledge. I will try to do a full wipe next as it is the next step. =/ Thanks! I'll keep this updated with what I get.
[Samsung Galaxy Nexus] wastedlife:
You would know if you flashed a kernel or changed that setting. The rom and most kernels shouldn't be set that way by default. To put it simply, fsync is how the filesystem writes to the internal storage. Dynamic fsync gives an increase to performance by writing changes to the storage less often. Mpokang is built to maximize performance, and that is one of the options it enables by default.
[G Pad 8.3 General] mustbepbs:
Just thought I'd create a place to pool our knowledge and try to get a custom recovery going.

So far I've been able to piece together the partition table using an app from the Play Store. I don't know if it's accurate or not since I'm new at this, so if someone else knows that something is wrong please let me know.

BLOCK-	MOUNT-	DEVICE NO-	LABEL-	FILESYSTEM-	SIZE (MB)

MMCBLK0	179/0	15028

MMCBLK0P1 /FIRMWARE	179/1	MODEM	VFAT	13.5 / 64.0

MMCBLK0P2	179/2	SBL1	0.5

MMCBLK0P3	179/3	SBL2	0.5

MMCBLK0P4	179/4	SBL3	2

MMCBLK0P5	179/5	ABOOT	0.5

MMCBLK0P6	179/6	RPM	0.5

MMCBLK0P7	179/7	BOOT	24

MMCBLK0P8	179/8	TZ	0.5

MMCBLK0P9	179/9	PAD	0

MMCBLK0P10	179/10	MODEMST1	3

MMCBLK0P11	179/11	MODEMST2	3

MMCBLK0P12	179/12	M9KEFS1	0.8

MMCBLK0P13	179/13	M9KEFS2	0.8

MMCBLK0P14	179/14	M9KEFS3	0.8

MMCBLK0P15	/PERSIST-LG	179/15	DRM	EXT4	4.3 / 7.9

MMCBLK0P16	/SNS	179/16	SNS	EXT4	4.1 / 7.9

MMCBLK0P17	179/17	SSD	0

MMCBLK0P18	179/18	MISC	16

MMCBLK0P19	/FACTORY	179/19	FACTORY	EXT4	4.1 / 15.8

MMCBLK0P20	179/20	BNR	EXT4	8

MMCBLK0P21	179/21	ENCRYPT 0.5

MMCBLK0P22	179/22	EKSST	0.5

MMCBLK0P23	/SYSTEM	179/23	SYSTEM	EXT4	1853.8 / 2113.8

MMCBLK0P24	/CACHE	179/24	CACHE	EXT4	14.4 / 788.4

MMCBLK0P25	/PERSIST	179/25	PERSIST	EXT4	4.1 / 7.9

MMCBLK0P26	179/26	TOMBSTONES	256

MMCBLK0P27	179/27	RECOVERY	24

MMCBLK0P28	179/28	FSG	3

MMCBLK0P29	179/29	DDR	0

MMCBLK0P30	179/30	FOTA	32

MMCBLK0P31	/MPT	179/31	MPT	EXT4	11.5 / 31.5

MMCBLK0P32	259/0	TZBAK	0.5

MMCBLK0P33	259/1	RPMBAK	0.5

MMCBLK0P34	259/2	RCT	0

MMCBLK0P35	259/3	RESERVED	16

MMCBLK0P36	/DATA	259/4	USERDATA EXT4	2260.3 / 11304.5

MMCBLK0P37	259/5	GROW	4

/DEV/FUSE	/STORAGE/EMULATED/LEGACY	NA/NA	EMULATED STORAGE AT /DATA/MEDIA ?	FUSE	2260.3 / 11304.5

/DEV/FUSE	/STORAGE/EMULATED/0	NA/NA	EMULATED STORAGE AT /DATA/MEDIA ?	FUSE	2260.3 / 11304.5

/DEV/FUSE	/STORAGE/EMULATED/0/ANDROID/OBB	NA/NA	EMULATED STORAGE AT /DATA/MEDIA ?	FUSE	2260.3 / 11304.5

/DEV/FUSE	/STORAGE/EMULATED/LEGACY	NA/NA	EMULATED STORAGE AT /DATA/MEDIA ?	FUSE	2260.3 / 11304.5

/DEV/FUSE	/STORAGE/EMULATED/LEGACY/ANDROID/OBB	NA/NA	EMULATED STORAGE AT /DATA/MEDIA ?	FUSE	2260.3 / 11304.5

The last bit there is a bit of a head scratcher to me.

I've also extracted the recovery.img from the mmcblk0p27.

https://www.dropbox.com/s/4u9v9dqfzrj5100/recovery.img
[G Pad 8.3 General] Endlessillusion:
Thanks for your effort man, i wouldn't know where to begin with something like this.
[G Pad 8.3 General] mustbepbs:
Trust me, I didn't either. Just taking it one step at a time. We've got a way to restore to stock, so it's relatively safe if you're patient and don't rush.
[G Pad 8.3 General] Endlessillusion:
I don't have my pad yet shipment was delayed until tomorrow. I am going to wait around, will take it nice and slow just happy to see some progress.
[G Pad 8.3 General] Alexey71:
This is the working recovery?, you can get root access?
[G Pad 8.3 General] Palux:
hello e thanks [MENTION=4346245]mustbepbs[/MENTION]

can you use this site to create a recovery cwm? builder(dot)clockworkmod(dot)com <--upload recovery image & build the recovery.. we can try to obtain the recovery without attend the job of "team CWM"

edit:

I apologize, I missed the link reading the first post..I saw now.

I now see what we get by loading the recovery image on the site.
[G Pad 8.3 General] mustbepbs:
Yeah it doesn't work. A lot of builds are failing on there so I don't know if it's the IMG or their build server.

I synced the CM10.2 repo last night so I'm gonna get started on trying to build from scratch today. Can't make any promises.
[G Pad 8.3 General] mustbepbs:
Okay, so I got CWM to build and I think I've gotten it right. Basically at this point I've got an update.zip for future reference and a recovery.img from the build. I've got to work in LOKI and see what happens.
[G Pad 8.3 General] mustbepbs:
Okay, so I patched LOKI and flashed it successfully.

When I adb reboot recovery, I get:

https://www.dropbox.com/s/591cd1a349nqfq0/bootingimage.jpg

It just boots normally after that. I suppose it's progress.
[G Pad 8.3 General] Palux:
yeah ... thanks for the tests and the work you're doing :highfive:
[G Pad 8.3 General] Alexey71:
It remains to unlock the tablet?
[G Pad 8.3 General] mustbepbs:
Not really sure what went wrong.

CWM built, so I think if there was a problem it wouldn't have built. Loki patched and flashed successfully because of that error message I got.

If something flashed to the wrong place, I wouldn't think I'd be able to boot like I can.

I guess I don't fully understand LOKI. Trying to do as much digging around as I can.
[G Pad 8.3 General] obiwan86300:
Hi,

It seems we have got the same error. Being new to compiling android i can't be sure my initial configuration (recovery.fstab BoardConfig.mk) were correct. The problem could also be that LG has changed its bootloader and Loki doesn't work anymore as i haven't seen anybody having succesfully tested it on the G Pad.
[G Pad 8.3 General] mustbepbs:
From what I've read, getting that error means that LOKI is working. I pulled the recovery.fstab from the stock img so I know that's correct. I may have mucked up a few things in the BoardConfig.mk, I fixed them but was so tired last night that I couldn't focus. Gonna try again today and tomorrow.
[G Pad 8.3 General] joshuadjohnson22:
has anyone tried this http://www.xda-developers.com/android/compile-twrp-for-your-device/
[G Pad 8.3 General] mustbepbs:
I haven't tried TWRP yet.
[G Pad 8.3 General] joshuadjohnson22:
I don;t know much about development but it looks like they made it easier?
[G Pad 8.3 General] mustbepbs:
I'll take a look if my revised CWM build doesn't work.
[G Pad 8.3 General] Alexey71:
Hi, how's it going?. Recently brought a tablet, I would like to recovery
[G Pad 8.3 General] Drgravy:
well we should have something soon

just need some time to test
[G Pad 8.3 General] dmnq:
wow, looks good. but it is not fully working yet?
[G Pad 8.3 General] Palux:
really good, there is something specific that does not work as expected?
[G Pad 8.3 General] katsika:
wow good job! if cwm makes its way to gpad then we can have cyanogen or some other custom rom!
[G Pad 8.3 General] Drgravy:
well good news I have twrp built and I should be releasing it later today
[G Pad 8.3 General] naruto.ninjakid:
Thanks

YES!!!!!!!!!! :laugh::laugh: Was hesitating to get this tablet for fear of customization and ROMS. But is seems that Root and others will be possible. Even though I prefer PAC Man ROM, CyanogenMod will do just fine. Even though stock LG is not that bad.

Drgravy, Good Sir you know what you are doing. Thank you I appreciate all your work. You are giving LG some sales lol.
[G Pad 8.3 General] Palux:
[MENTION=4557482]Drgravy[/MENTION]

hi man, any bugs or problem? all right? :o:o
[G Pad 8.3 General] Drgravy:
no problems all seems good;)
[G Pad 8.3 General] woody1:
So, do we need to have root before we can install TWRP, or will your recovery include a root method?
[G Pad 8.3 General] mustbepbs:
It's the loki exploit, so you'll need root in order to flash it.
[G Pad 8.3 General] woody1:
And currently, Kingo is the only method to root, I guess? I would really like to have a method that I felt more confident about.
[G Pad 8.3 General] andrea210701:
There is oneclickroot metod

http://www.oneclickroot.com/phone/lg-g-pad-8-3/
[G Pad 8.3 General] naruto.ninjakid:
Is this safe ? I don't trust that Chinese Root Method lol I was waiting for a safer option. Im not sure about this one click root method.
[G Pad 8.3 General] andrea210701:
I was used it for my LG p500 and it is safe...
[G Pad 8.3 General] naruto.ninjakid:
Have you tried it on LG gpad 8.3?
[G Pad 8.3 General] andrea210701:
Not,i'm going to buy it,but the software for rooting is safe

Edit:can anyone test this in g pad? http://xdaforums.com/showthread.php?t=2130276

It works on my phone(huawei ascend g330)

It seems that work in the LG optimus g(if we have the q8064 we have the same canche of it)

Please test it

Sorry for my bad english
[G Pad 8.3 General] jesterhead82:
Had no luck with it on mine ?
[G Pad 8.3 General] woody1:
How do you know it's safe?
[G Pad 8.3 General] andrea210701:
Search any notice that he is not safe....
[G Pad 8.3 General] Paul^^:
Couldn't respond in regular thread (10 posts limit :( ). I'd like to report, that I've just installed your custom recovery, and everything works great - thanks ! :)
[Samsung Galaxy Mega] m4f1050:
Is there a specific recovery for the Samsung Galaxy Mega SPH-L600 (Sprint)?

I would like to do a nandroid backup before I start playing with it.. :)
[Samsung Galaxy Mega] Silesh.Nair:
If you send me your stock recovery.img, i can try making one for you.
[Samsung Galaxy Mega] jsimonson0:
Check this thread for recovery deets:

http://xdaforums.com/showthread.php?t=2527473
[Samsung Galaxy Mega] m4f1050:
I managed to backup 6 partitions: BOOT, CACHE, DATA, EFS, RECOVERY, SYSTEM. Does that sound right?
[Samsung Galaxy Mega] vwbug2007:
Clap clap! Hooray! I was planning on nandroid backing up stock rom after getting the replacenent mga this friday
[Samsung Galaxy Mega] ashikrobi:
Pls upload your efs or qcn backup

I need factory efs backup or qcn backup for SPH-L600. Please upload those. Few days ago I programmed this phone with dfs cdma. It was working. I was trying to read nv with this tool. Pressed read range and then write. Now efs is corrupted. Not shows sid nid and channels. I tried many ways but failed. Please help me.
[Samsung Galaxy Mega] m4f1050:
What range did you write to? Have you tried to ODIN it with stock ROM?
[Samsung Galaxy Mega] ashikrobi:
I did what you said

Thanks for your reply. I am in a horrible situation. No one is helping in xda. I wrote from 0 to 65535 range. I tried oding with stock rom several times with no luck. At last i did with tick in nand erase all and clear efs. When i press *#06# in phone, it shows only meid. Please help me.
[Samsung Galaxy Mega] m4f1050:
Wow, that IS bad. Problem is some NVItems can't be read so when you try to write those it will write blanks (0's) or not write them at all. If you already wrote from a phone that does read them you might have corrupted your NVitems. Is insurance an option?
[Samsung Galaxy Mega] ashikrobi:
I don't have insurance

Friend i don't have any insurance options. I am from outside USA. I am from Bangladesh. If you can, please upload qcn file or send it by e-mail personally in this address ashikrobi@gmail.com. Do not worry i have my imei i do not want to steal anything that is yours. I have installed part detection patch and now all my nv items are readable. I will be able to write qcn file with qpst. Please help.
[Samsung Galaxy Mega] m4f1050:
You keep mentioning IMEI, us Sprint users have CDMA which uses MEID/pESN, is yours GSM or Sprint CDMA?
[Samsung Galaxy Mega] ashikrobi:
Its sprint cdma

Mine is sprint cdma SPH-L600. Its from USA. My cousin send it.
[Samsung Galaxy Mega] m4f1050:
So if I give you my qpst file you can change the imei? I don't use the GSM part so I don't care, but very interested in knowing if I can change the imei to match my meid.
[Samsung Galaxy Mega] ashikrobi:
I don't know if imei can be changed

I don't know if imei can be changed. I also don't care about that now. I just want to fix radio information to original setting so i could use this phone again. If you have backup of qpst please post it. It seems you are not going to upload the file.
[Samsung Galaxy Mega] m4f1050:
Im asking a few questions first, no need for attitude. And NO, I am not posting it here publicly, I am sending you a PM with a download link. So once I take out my personal info, create the qnc (sp?) file I will upload and send you a PM.

EDIT: PM sent.

For the record, I'm not the one who messed up the phone, you are asking me to send you my QCN file which contains all my info and that requires me to zero out the phone first THEN reprogram my phone, doing it as a favor, no need to get cocky.
[T-Mobile Samsung Galaxy Note 3] zmore:
Hey all,

Just curious how many of you received your Note 3's (or older phones) and noticed any OLED display defects? Specifically, if you see any "stuck" red/green/blue pixels? My last two OLED phones (SGS1, and SGS3) were perfect ('cept for SGS1 burn-in), but I just noticed that my Note3 has tiny red pixel splotches all over.

When I first got my Note3 about a month ago, the first thing I did before I even turned it on the first time was slap on a cheap (Spigen) screen protector. I was wearing a red long-sleeve shirt at the time, so when I powered on the phone I was pissed to see what I thought were pieces of red lint from my shirt under the protector. I didn't care that much because I was planning on replacing the plastic protector with tempered glass anyway, annnndddd, I finally got around to doing that tonight, which is when I discovered that the red lint were actually display defects. :(

On a 100% white background image I can see one somewhat noticeable 0.5mm red splotch in the lower right corner, and then 8 other much smaller red dots spread out elsewhere. On most other backgrounds, it's barely noticeable, unless you know what to look for or have OCD.

I'm not anal enough to do a warranty return over this (though I know many of you out there are); I was just curious how common this minor problem might be? I know that the original Note had a problem with "crushed blacks", which was thankfully fixed, and that the Note 2 wasn't that bright compared to the Note 3, yada yada. Chasing perfection.

(On a good note, though, I did manage to apply my iloom tempered glass screen protector almost perfectly straight, and without any lint this time, thanks to the steamy shower room. LOVE the glass; never going back to tackier-feeling and greasier-looking plastic protectors, even though they're much cheaper)
[T-Mobile Samsung Galaxy Note 3] atn0716:
Mine suffer from mura effect. It only show in compete dark room though.
[T-Mobile Samsung Galaxy Note 3] 01010001:
Same here, my old SGSII had the same defect (even after several exchanges). I think all Samsung OLED displays have the mura defect except possibly for those few lucky lottery winners. I've learned to live with it, but I cringe every night I use it with the lights off. I hope they fix it at some point, I thought they would've by now.
[Galaxy S Advance I9070 General] Ankurzl:
Hello guys & Gals

In this tutorial we will be learning how to change deep sleep state in STOCK ROMS/STOCK based ROMS in Samsung galaxy S Advance. ;)

First of all What is deepest sleep State?:confused:

"CPU on the Mobiles have variable speeds, like CPUs on laptops. We can work at 200, 500, 800, 1000, 1200 and 1400 MHz, depending on what application we're running.

When there's nothing to do, the CPU should go into "deep sleep" state, which means basically stopped, so it consumes very little power."

By default, Deep sleep state will be 3 in STOCK JB and can be increased till maximum 5.

Now lets start with it.

Requirements:

Samsung galaxy S advance running any STOCK based ROM

Rooted

Root explorer

Terminal emulator

Kernel having init.d support (CoCore-E/EP 6.0 or above)

Instructions

First Download the deepsleep.zip

Extract the zip and you will be getting a file

Copy the file to your phone in Internal storage/Memory card.

Open root explorer and give it root permissions.

Now navigate to System/etc and make a folder named"init.d" if it is not there.

Long press the folder and some options will pop out.

Click on permissions and tick the first 9 brackets(i.e change the permission to 0777)

Now Change Ownership to root root 0:0

Next move the file "deepsleep" from the Storage to the init.d folder.

Change the permissions and the ownership same as you did for the init.d folder.

Reboot your phone.

How do I know That my Deep sleep state has been changed to 4?

Open Terminal Emulator and type the following commands & you should be getting your answer.

You can change deep sleep state to 5 by editing the deepsleep file in init.d and replacing 4 by 5. (similar to make it 3)

NOTE: Don't Use Deep Sleep State 5 on pegasusq(sio governors), It may cause system instability. Instead use indemand+cfq in deep sleep state 5. (but still you may encounter random reboots)

Enjoy better battery backup in standby mode.

If you are using CM10.1/10.2 there is a option to change deep sleep state in settings>advance>deep sleep. You will not be needing any script in CM.

init.d script by anantttt

This is my first post on XDA, So do thank me if you like it & sorry for any typos.

:fingers-crossed:

#PEACE
[Galaxy S Advance I9070 General] FabioSan:
Thanks man ;)

I'm using the valor 4 with the init.d script :)

So, i must think that the pegasusq + sio or noop or row scheduler and deep at 4 work normal? i'm using in this moment ondemandq + noop as test :)
[Galaxy S Advance I9070 General] shut_down:
I am using Deepsleep 4 with PegasusQ + SIO on CM 10.1. Without problems. Deepsleep 5 makes reboot, but 4 is working good.
[Galaxy S Advance I9070 General] FabioSan:
I'm using Ondemandq + noop + deep at 4 :) no problems :) But i'm not sure if it's better pegasusq, ondemandq or hotplug xD

Off Topic closed :)
[Galaxy S Advance I9070 General] anantttt:
You are using my script. Dah anyways, why did you open another thread when I already explained in a tutorial to make init.d scripts. See this

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

But still good work
[Galaxy S Advance I9070 General] Ankurzl:
Sorry dude i too got that script from another person and really didn't know who made it.

Right now i am online from my cell so will edit your name in document afterwards when i will be on my pc.
[Galaxy S Advance I9070 General] Ankurzl:
Try using pegasusq instead of ondemand.
[Galaxy S Advance I9070 General] FabioSan:
I'm using Pegasusq + noop from some days :) but sincerly i don't see sensible differences ._.

At least the battery is that, and also the phone u.u
[Sony Xperia S, Acro S, Ion] Ferenchop:
Hey,

Sorry if it is a question that had been asked a lot, but I tried couple of jb 4.2based ROMS and the HDMI doesn't seem to work on any of them.

Is it something that sony keeps only for the stock ROM? Or is there some fix to bypass the problem?

And.. If there is no fix right now, is there going to be one?

Thanks in advance.
[Sony Xperia S, Acro S, Ion] Envious_Data:
They dont work on letamas works

Have you tried anything from RaymanFX
[Sony Xperia S, Acro S, Ion] Ferenchop:
apparently no.

i have tried now.

absolutely brilliant.

thanks for giving me the directions. :)
[Sony Xperia S, Acro S, Ion] Ferenchop:
one more direction question...

emm...is there a hdmi friendly 4.2 based rom? or is it just above cm 10.2 that the hdmi comes back to life...
[Sony Xperia S, Acro S, Ion] Envious_Data:
i dont realy know

if you dont see hdmi in the "not working" section of the thread then it may be safe to say Hdmi is working
[Sony Xperia S, Acro S, Ion] Ferenchop:
yeah...:|

well, i still didn't find a rom that isn't based on stock, and actually reacts when i plug the hdmi cable.

the only reaction i got is reboot in some roms.

i did not find one. and i have searched.

now, what i really want, is a rom that is not a stock one, but still hes the hdmi.

does such a thing exist? anyone using one?
[Sony Xperia S, Acro S, Ion] Envious_Data:
im not sure realy

have you looked at miui?
[Sony Xperia S, Acro S, Ion] Ferenchop:
if i am not mistaken, based on 4.1.

its a great rom though :)
[General Topics] crazow:
I need some help, my samsung galaxy s3 I9300 keeps shutting down. I have to do a manual reset about 5 times a day by taking the battery out the phone so it can work again :mad:. This is frustrating me, do you guys have any suggestions?
[General Topics] Xenoxda:
you can elaborate more by explaining about what you did before the condition occurs.

rooted/not, stock/mod, etc.
[General Topics] xsenman:
First you should use the XDA device search engine and post in the S3 Q&A forum meant for your device, after looking at the stickies in that forum.

Basically, this could be due to a battery problem ( sometimes just losing connection - cleaning battery contacts or If battery is bulging - needs to be changed) ) or a ROM problem, could be resolved by a factory reset, when using the S3 stock ROM , but you will lose all your data ( so before attempting to do it save everything in your Phones Internal SD card to your PC ( for salvaging later)

But do look in S3 Forum and post only there when it concerns your S3 device.

Check this out! Links to useful Guides and " Banned " Documentaries ​
[General Topics] hardy174:
Try cleaning up extra cache or data... use recovery mode........might help u
[Nexus 4 Q&A, Help & Troubleshooting] dmkozak:
Just received my download. With the bug reports my gut tells me to wait on installing. I'm happy with jelly bean, and don't want to do a full backup to reload data if there's a problem (all my data is otherwise backed up in various places, but I haven't taken a snapshot of everything). Most of the problems I could probably live with until fixes are released except the dialer bug. Not having a dialer pretty much renders the phone part of the Nexus 4 useless; not something I want going into a holiday weekend.
[Nexus 4 Q&A, Help & Troubleshooting] 1slow4G:
I just installed on mine. All seems fine. For now Lol
[Nexus 4 Q&A, Help & Troubleshooting] dralways:
I absolutely love KitKat, everything is just a hair faster and smoother, battery seems to drain even less with screen off (idle, voice calls) and maybe a hair less with screen on (could be placebo). I haven't noticed any bugs whatsoever and feel like I have a far superior phone over its Jellybean counterpart..................... all except for one INCY BINCY little thing................. THEY STOLE MY MFing TETHER AND NOW I CANT BROWSE MY OTHER DEVICES WITHOUT ROOT.

I'm about to go crazy and may just try another phone when I was planning on waiting another year or so. N4 on JB did everything I needed of it just fine, this single con outweighs the multitude of pros for me. Then again, apparently this is only a Tmo problem so yes, update if you're not on Tmo.
[Nexus 4 Q&A, Help & Troubleshooting] Nate14:
Do you have to pay to tether?