yashsingh1/xdaforums huggingface dataset:
[LG Optimus G Pro] jesi.james:
Not trying to be that guy here but this shouldn't be in the dev section. Either q&a or general. Please ask a mod to move this thread.
[T-Mobile, Samsung Galaxy SIII] Mnguyen:
So I decided to unroot my phone via flashing the stock firmware T999UVDMD5_T999TMBDMD5_T999UVDMD5_HOME.tar.md5 for my T-Mobile Samsung Galaxy S3 through Odin. Then, once it rebooted, it was stuck on the flashing Samsung logo. I took out the battery and tried accessing recovery mode, but all it did was just showed turned itself off. I was still able to access download mode, so I tried flashing the stock firmware again, still didn't work. Then, I tried flashing CWM to see if it would open up access to my recovery mode. Nothing changed, so then I tried to root it again by flashing CF-Auto-Root-d2tmo-d2tmo-sght999.tar.md5. Nothing changed, so I tried to flash the stock firmware one last time. Even through all the efforts I still was stuck on the flashing Samsung logo and still was able to have access to download mode. I looked at what it said on the Downloading... screen and this is what it said:

ODIN MODE

PRODUCT NAME: SGH-T999

CUSTOM BINARY DOWNLOAD: Yes (4 counts)

CURRENT BINARY: Samsung Official

SYSTEM STATUS: Official

QUALCOMM SECUREBOOT: ENABLE

Is my phone as good as gone? Or is there some sort of hope that I just haven't looked into yet?

Thank you so much for your help!

Yours truly,

Mnguyen
[T-Mobile, Samsung Galaxy SIII] Aerowinder:
Take out the battery and tell us what the sticker underneath it says.
[T-Mobile, Samsung Galaxy SIII] Mnguyen:
model: Sgh-t999

fcc id: A3lsght999

rated: 3.8v
[T-Mobile, Samsung Galaxy SIII] Aerowinder:
Link to the recovery file you downloaded?
[T-Mobile, Samsung Galaxy SIII] Mnguyen:
ixcluth 82

I went to samsung updates . com and I selected SGH - T999 (Samsung S 3 (T-Mobile)) and the first download link.
[T-Mobile, Samsung Galaxy SIII] Aerowinder:
What happened when you tried to get into recovery? It shut off?
[T-Mobile, Samsung Galaxy SIII] Mnguyen:
Yes
[T-Mobile, Samsung Galaxy SIII] Aerowinder:
Are you holding power+vol up+home until the phone vibrates (turning on), then releasing the power button?
[T-Mobile, Samsung Galaxy SIII] Mnguyen:
Omg! I've been doing the opposite, where I release vol up and home! Now I have access to my recovery mode woohoo! Thank you!

From here do I just do a factory wipe and wipe cache partition correct?
[T-Mobile, Samsung Galaxy SIII] Da Kine:
Yes, do a factory reset and reboot device.
[C++ or Other Android Development Languages] lkd85:
I'm fairly new to Android (or any) development in general, I've currently made a camera app for more functionality for filmmakers. My question lies in accessing the raw frame stream from the level that the media recorder/omx native source uses to compress video? Reason being, this is the only sure way to grab the frames at a locked frame rate and without going through Java's bottlenecks in grabbing consecutive frames at a high frame rate. I'm searching through the OPPO FIND CM 10 device and kernel sources to find where the magic happens so to speak. Just locating the binder interfaces for IPC at the moment. Is V4L at work here?
[C++ or Other Android Development Languages] ScatteredHell:
Ehm ....which one you use, Mono Android?
[C++ or Other Android Development Languages] const_char:
You mean an external camera? Like a USB camera? Or an internal camera? Internal cameras may be different, USB cameras might use different drivers. Anyway V4L is available on Android from the NDK, yes. But there are difficulties you'll have to work on.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pre4speed:
Just a few questions

Is the service a mvno? How is the service in southern Cali (north of Los Angeles here)? Do you get 3g/lte? Is so, did you use one of the mods and if so which? Most importantly, can you use YouTube and any streaming services without problem? Tia for any answers.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jpcdeux:
Family mobile is T-Mobile. Might be better off asking there
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pre4speed:
I'm asking here because I want to know if anyone with the i747 is using the service.
[Nexus 4 Q&A, Help & Troubleshooting] john5220:
I wanna get that $199 N4 its a real steal

I am going bank tomorrow to put in some cash in my account so I can transfer it to my friend who has a credit card with a US billing address.

Hopefully they don't sell out by tomorrow. This kind of price it sounds like they must be selling thousands per day and right now I sold my trash S3 mini and am using a $10 nokia black and white phone to make calls and use alarm app.

But I don't know which color to buy. Generally I HATE AND I MEAN I HATE White Galaxy S3 and S4

BUT thats Mostly because its plastic and the front of the phone is also white. The N4 is like the Galaxy Ace. The front is all black but back and sides alone are white.

But I hear the N4 sides can get discolored and dirty if its white

please help me decide I am so excited. So glad I didnt waste money on a S4 or Xperia Z

I should probably buy black since its always my favorite color in electronics
[Nexus 4 Q&A, Help & Troubleshooting] taodan:
How about this, buy both phones, black and white, then try it out for a few days and then decide which one you like. Keep one and return the other :) Personally, I prefer black color.
[Nexus 4 Q&A, Help & Troubleshooting] john5220:
No apart from not having the money to buy both

I live in the Caribbean so it cannot be returned and also getting one device alone into the country means I have to pay around $100 USD in TAX

So that would be $100 US wasted plus the shipping fee international.

i think its best be safe and go with black
[Nexus 4 Q&A, Help & Troubleshooting] xxxMADxxx:
Choose black one
[Nexus 4 Q&A, Help & Troubleshooting] john5220:
ok I will choose the black

thanks

Better safe than sorry :)
[Nexus 4 Q&A, Help & Troubleshooting] uploder:
no no wait!!!!! choose white!!!!!!!!!!!!!!!!!!!!!!!!1
[Nexus 4 Q&A, Help & Troubleshooting] NardVa:
Chicks get white phones.
[Nexus 4 Q&A, Help & Troubleshooting] kangerX:
Not offensive at all ^

sent from the state where marijuana is NOT illegal !!
[Nexus 4 Q&A, Help & Troubleshooting] failly:
I would personally choose the black one, much more classy and sleek look.

Also, you notice dirt more on white phones.

Your choice man!
[Nexus 4 Q&A, Help & Troubleshooting] john5220:
yeah that dirt on the white will be an issue

white looks like a girly phone.

Black always seem to look a lot more exotic
[Nexus 4 Q&A, Help & Troubleshooting] obtained:
Here
[Nexus 4 Q&A, Help & Troubleshooting] mascolel:
I am using PA 3.99 and i am having a problem with the volume of the notifications.

First i vhoose the volume panel style: expanded.

Then i choose the volumes: Music and ringtone with high volumes and notification with the minimum volume (after choosing the volume for each item, you can hear the sound as it should be.)

Then i uncheck all boxes, except the "silent mode affects notification.

When a notification comes, the volume is high. Then, if i go to Volume again, the notification volume is the same as the rongtone one.

I have tried all possible ways to make it work properly (choosing every kind of volume panel, check and uncheck all items, etc), but nothing seemed to work.

Is there any way to fix it? Everyone faces the same problem? I hate this high volume notification :rolleyes:
[Nexus 4 Q&A, Help & Troubleshooting] danielms22:
Well, I think this is the first time I see someone complain about too high volume levels on the N4 :D Usually it's the other way around.

I can't really help you with PA, but I can recommend the Volume control of Android Assistant, which I run on stock/unrooted, and it worked fine so far.
[Nexus 4 Q&A, Help & Troubleshooting] unubtanium:
This is a bug in PA. loot at bugreport 211 and 222 here http://bugtracker.androidninjas.com:8282/projects/framework/issues?page=1&tracker_id=1
[Samsung Galaxy Nexus] GiZiM:
Anybody else had this issue? I tried it on Shiny Rom and now CM 10.2 nightly. Get in one time with no issues, if I reboot I get stuck at the Google screen. The one way to get the phone usable is to do a completely factory data wipe and start all over.

I'm using TWRP, I've flashed tons of roms and I'm doing it no different than any of them. I do a complete wipe, install CM, GApps, reboot I get in one time. Do a reboot and then get stuck at Google screen.

This happened with both ShinyROM and 10.2 both are 4.3. They both had a valid MD5.

I have flashed PRIMEMD04_Bootloader-signed - One that came from Shiny ROM bootloader-toro-primelc03 - Stock (I believe)

Nothing worked, got the same issue.
[Samsung Galaxy Nexus] desktopfusion:
The only time I get persistent Google screen is when I have a corrupt /userdata partition.

Try running e2fsck on mmcblk0p12 if you have one of those devices that get emmc corruption by changes in sdcard free space.

In case you need more information on this :

1. In TWRP Mount options, unmount Data. The command won't work on mounted partition.

2. In Advanced > Terminal Command, select the /dev/block folder. Then type in

e2fsck -n mmcblk0p12

("-n" option will cause no changes to your filesystem, it just shows a simulation of the file system correction tool's result.) If the result says the filesystem is "clean", then you have something else to worry about and its not corrupted /userdata.

3. If it starts checking for errors (there's a KILL button while running the command), your filesystem has errors. You can kill it, and then run

e2fsck -f -C 0 -y mmcblk0p12

(-f is for forced run, -C 0 will give you progress of completion of task, -y will say yes to all prompts (necessary), and mmcblk0p12 is the /userdata partition)

4. Let the command run until you don't see the KILL button (shouldn't be more than a couple of minutes). On running

e2fsck -n mmcblk0p12

again, it must show you a "clean" filesystem.

5. Just reboot to System. If your /userdata was corrupt, running this will mostly solve your problem.

Damn, I wish I had found such instructions to get over my horrendous time with corrupt partitions over six months from November 2012-April 2013.
[Samsung Galaxy Nexus] GiZiM:
Thank you! I will look into this but I would love to fix the cause.

I'm sure this is the issue because I cannot get the phone back into a working state until after doing a full factory wipe.

What would be causing 4.3 roms to corrupt my /userdata? Whatever it is it is happening after the first reboot after I get into the rom.
[Samsung Galaxy Nexus] desktopfusion:
Whatever my phone faces is not limited to 4.3. It has been happening since 4.1. Something to do with the eMMC of the phone itself. Gets corrupt too easily when the decreasing free sdcard space approaches 3 GB. Sometimes a battery pull can also cause it, sometimes a random reboot can cause it. Technically, 4.3 is supposed to solve this issue with TRIM execution in the background, but it hasn't helped me definitively yet.

It has been documented on these forums for this to happen to phones produced in August, September, October 2012.

In my case, I am quite sure that adding and/or deleting files larger than say 500 MB (for example Nandroid backups) causes this problem to happen at any time afterwards without notice (preceded by random reboot straight into stuck Google screen). I guess new ROMs can cause such issues if there is a large amount of app data deleted everytime, but this is just uninformed speculation.

I've setup Tasker profiles to autorun e2fsck through TWRP every morning before I wake up so I don't have these issues while awake. And one more profile to tell me every 8 hours if my sdcard has changed by a lot. :cowboy:

I hope this is all there is to your phone's problem!
[Samsung Galaxy Nexus] GiZiM:
Thanks this is very helpful, I will work on this tonight after work and see what I can come up with.

Right now it is showing as CLEAN but i'm running 4.2.2. Is there anything special to go from 4.2.2 to 4.3?
[Samsung Galaxy Nexus] desktopfusion:
Nothing special really.

Was the result Clean after a stuck Google logo?

You could pull battery at the stuck logo and go to TWRP and then check if it is clean. If it is indeed clean, then there's something else wrong that is completely different!
[Samsung Galaxy Nexus] GiZiM:
I'm going to give it a go tonight when I get home.

1. So pretty much backup everything, do a complete factory wipe of all data.

2. I'll do a adb push of the .zip for the rom and everything.

3. Flash rom and any other packages needed

4. Run that command see if it comes back clean

5. Reboot go into the rom

6. Reboot, if i get stuck at the Google screen run that script if it's not clean just keep running it?
[Samsung Galaxy Nexus] GiZiM:
It's running, it says "clone multiply-claimed blocks? <yes>"

How long does this normally run?

Edit: Running now for 4hrs
[Samsung Galaxy Nexus] desktopfusion:
Hey, sorry.

4 hours?! I've not had it run for more than 2 minutes, ever!

Did you run the -n option and let it say whether there is a corrupt partition? If yes then there may be a problem with the eMMC since its taking so long.

As a last resort, you could go completely stock via fastboot. [Formats /userdata partition, erases SDcard as well - take backup]
[Samsung Galaxy Nexus] TwebStab:
Lifesaving string of code.

Holy mother of god.

This was a lifesaving string of code. I was convinced that I was going to have to buy a brand new phone. Kudos to you DesktopFusion. Thanks a lot!
[Samsung Galaxy Nexus] TwebStab:
Explanation as to why a corrupt userdata partition causes this issue

So, in case anybody was wondering, I would like to explain how I see the issue at hand (corrupt userdata partition).

Upon first boot, the ROM is getting set up and doesn't have any orders to check /userdata because well, there is none on the device. So why waste precious time being redundant (smart coders, right?). So the userdata partition is not checked.

However, now that the second boot is being performed, there is, by default in the system's repertoir, data put in by the user, so the bootloader is told to check the partition containing user data. Since the partition is corrupt, and the free space is technically "modified", it errors up and gets stuck.

I could be wrong, I'm not a developer of any sorts. Just a dude giving my point of view.
[Samsung Galaxy Nexus] bimasakti85:
I got this trouble too last night. I'm flashing elia's 4.3 custom rom with under 5 gb free space. Got it boot twice,then got stuck at google's logo after trying flashing slim bean gapps. Flashing whole 4.3 stock firmware finally solve this. Maybe there is correlation between upgrading from 4.2.2 without upgrading the bootloader with this problem.
[Samsung Galaxy Nexus] GiZiM:
It ended up running for 6hrs and never finished, I did do the -n and it said it was CLEAN but still could not boot into the 4.3 ROM.

So ran it any way for 6hrs and no change as of right now I am unable to boot into ANY 4.3 ROM.

If eMMC was screwed up why can 4.2.2 roms work fine but not 4.3 roms? what's the difference?
[Samsung Galaxy Nexus] GiZiM:
BUMP still no 4.3 love
[Samsung Galaxy Nexus] desktopfusion:
Still not resolved?

Have you tried flashing completely stock factory image via fastboot?

Consider checking your flash memory with this app, "eMMC Brickbug Check"

Could you also put in here what Type and Date the eMMC chip was made as per the application?
[Samsung Galaxy Nexus] GiZiM:
Sane chip

Ran memory check no issues

Type: SEM32G

Date: 10/2011

FW: 0x90
[Samsung Galaxy Nexus] desktopfusion:
Rats. Falling short of ideas.

I might have missed your answer on whether you've tried flashing a stock Nexus image through fastboot, though.
[Samsung Galaxy Nexus] 7175:
I had basically the same problem coming from 4.2.2 to 4.3. I'm not sure if it was the bootloader upgrade, 4.3 CM alpha from early August, or the small amount of free space under 5GB, but it was definitely userdata corruption like desktopfusion is saying. I was finally able to fix the problem after a "fastboot -w" userdata and cache*format. This has to be done in fastboot, so hook your computer to your phone in twrp, run "adb pull /sdcard "drive:\pc_backup_location"" to backup your sdcard data (grab what you can if errors come up from badly named or corrupted files). Make sure you got md5verified recovery & bootloader images renamed to recovery.img & bootloader.img, and a rom.zip in your adb folder on the computer. Reboot to bootloader, still connected. **And make sure you're not forgetting any sdcard backup, or twrp backup if still functional, before this erase and format. Run "fastboot -w". Then "fastboot flash recovery recovery.img" and you should be good to reboot, adb transfer ROM.zip and other files to fresh sdcard, etc. There's info on this around to double check, and I just posted a little more detailed walkthrough on this a couple days ago. This definitely saved me though with an identical problem, so if the emmc error check doesn't pan out, I would give this a try. May the fastboot gods be with you.

[MENTION=4760010]desktopfusion[/MENTION] -Thanks for your post on the previous page! Copied and saved to mygiant android useful infos text file ;)... which will one day end up corrupting my userdata partition with my luck.
[Samsung Galaxy Nexus] chafedbm:
7175 nailed it. I tried flashing all sorts of different ROMs/gapps/Super SU combinations and tried different wipes/formats to no avail. I wish I would have found the instructions to "fastboot cleanse" the phone 4 or 5 hours ago. I have been reading through forums for several hours today and every suggested fix failed. 7175's fix was spot on for me. My phone was locking up at the Google screen with the lock every time I rebooted after installing a 4.3 ROM.

:highfive:
[Samsung Galaxy Nexus] 0rigin:
Thanks for this...

First thought it was an issue with SlimRom, tried different kernels, problem wouldn't go away, then realised it was happening with every rom I flashed...
[Samsung Galaxy Nexus] GiZiM:
RESOLVED!

Okay guys and gals got this taken care of

Had to flash stock back to the phone then I could then flash TWRP and install my ROM without issue.
[Samsung Galaxy Nexus] zoso59brst:
I had this happen as well and was able to resolve the same way, but not without some addition difficulty that I've yet to solve... My phone will no longer connect with adb. Hard to explain.. If I plug in the phone via USB to my pc, my phone does not prompt me to authenticate the PC, nor is it visible to adb. It will however connect and be accessible in PTP mode, but not in MTP mode. I am able to push commands in fast boot and that's it. It's completely bizarre and I can't fix it. This is only since it soft-bricked after going to 4.3. I was ready to chalk it up to a hardware issue but I have no idea.

Edit : Also, PDA net won't install - can't handshake with device
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] sincity:
I'd like to wipe the Delvik cache... Is there any way to do this in ODIN? I DO NOT HAVE RECOVERY.

I've been doing some research and if I can wipe the cache, the boot load would have to rebuild. Killing the apk that is freezing my S4.

Can someone confirm this? Or did I just confused myself even more...
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] xBeerdroiDx:
you've given us almost nothing.

are you i337 or i337m? what firmware build? why arent you able to access recovery? are you rooted? what apk did you install?
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] scott14719:
You might be able to use ADB to wipe it, but you will have to do some research to find if it is possible or what the commands would be. And, as always, there is a chance of making things worse. ODIN is a tool for flashing, it is not a recovery substitute. I've never read about anyone ever using ODIN to wipe memory without replacing it with something else (ROM, Kernel, etc...). Maybe someone knows more about it though. So, good luck with your searching and reading. If you decide to check out ADB, you can search for tutorials here at XDA and on Google.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] sincity:
I337 Rooted MF3 --- Chainfire3D
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] sincity:
No luck with ADB because it doesn't full boot. I have trouble with the MTP driver loading... and I don't know if that is the problem either.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] sincity:
At this point maybe flashing anything to clear the cache... LOL!
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] graydiggy:
Impossible to flash anything on MF3. C'mon people, we know this.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] graydiggy:
The phone does not boot. Terminal emulator is a no go.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] sincity:
Yessir...
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] slatesekx:
Terminal emulator is a no go.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] Agent:
When you say you don't have access to recovery....did you try to flash a custom recovery on the MF3 version and lose it that way?

---------- Post added at 05:18 AM ---------- Previous post was at 05:17 AM ----------

How do you suggest pushing an image back to the device on the MF3?
[MDA III, XDA III, PDA2k, 9090 General] stevesm:
Hi Guys,

Is there any way to extend the scanning time on Bluetooth? Seems to be about 10 seconds. I'd really like at least 20 or so.

Thanks,

Steve
[MDA III, XDA III, PDA2k, 9090 General] kimmie:
hmmm good question!

Another case: BT seems to stop scanning after approx. 5 min. Is this correct?
[MDA III, XDA III, PDA2k, 9090 General] Paul_Hammons:
Install this. This sets a new registry key and extends the search time to 25 seconds. It comes from the 2.03 Harrier Extended Rom upgrade.

Or add the registry key manually:

HKLM\Software\Widcomm\BTConfig\General

Key=Dword, InquiryDuration=25

Hope this helps.
[MDA III, XDA III, PDA2k, 9090 General] stevesm:
Hi Paul, Many thanks for that. Works a treat. It scans for 30 secs on my machine which is fine :-) - Cheers
[MDA III, XDA III, PDA2k, 9090 General] pimbo:
Works fine on my Machine

I made the Dword manually in my registry and it seems to be working.

HKLM\Software\Widcomm\BTConfig\General\InquiryDuration=25

Thanx for the free Info :P
[MDA III, XDA III, PDA2k, 9090 General] stevesm:
Thanks, I'll take note of that :-)
[MDA III, XDA III, PDA2k, 9090 General] kimmie:
I have no widcomm installed on my MDA-II. Anyone has an idea how to change the timeout in the registry?
[Sprint Samsung Galaxy Note II] DJMaj07:
So I just have a general question. I sent my phone in for repair. It's been gone for a week so far. When I get my phone back, will all of the texts people have sent me during that time still show up on my phone? Or is there a time limit after which those messages will expire if not delivered by then? Of course, this is all assuming Samsung doesn't wipe my phone clean before sending it back...
[Sprint Samsung Galaxy Note II] patrao_n:
If it hasnt been wiped then they should still all be there. The messages work on a per message basis not time. Say your limit was 200 messages (you can change this in the setting of the messaging app). So when you got message #201 then the oldest message #1 would be deleted. This is also per contact thread.

sent from my Provari with a mini rda!
[HTC Desire X] Len:
Hello,

I want get a new hboot, but... for this I need OTA update.

But can't find nand backup of this cid T-M0B009

Can someone help?
[HTC Desire X] GtrCraft:
There you go: https://www.dropbox.com/s/ibti9pyrzvbjh0k/t-mob009 ICS Nand Backup.zip
[Nexus 4 Q&A, Help & Troubleshooting] kdog1202:
I restored stock and now my messages won't send :( did I do something wrong do I need to flash a radio or?? Please help. Also my phone is at 4.3 and at the top an ota message is there and wont go away but I don't want to loose root