yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ejatds:
thanks! made the logcat file too large accidentally (didn't know i had to manually exit the cmd window lol) the file got to 600+kb,

however, i did get multiple (read: hundreds)

W/wpa_supplicant( 3101): wlan0: Failed to initiate AP scan

then couple tens of lines down, after disconnecting and reenabling wifi

I/wpa_supplicant( 4136): wlan0: Associated with 00:26:44:8d:fd:55

I/wpa_supplicant( 4136): wlan0: CTRL-EVENT-CONNECTED - Connection to 00:26:44:8d:fd:55 completed (auth) [id=0 id_str=]

D/DhcpInfoInternal( 727): makeLinkProperties with empty dns2!

D/DhcpInfoInternal( 727): makeLinkProperties with empty dns2!

D/ConnectivityService( 727): ConnectivityChange for WIFI: CONNECTED/CONNECTED

D/ConnectivityService( 727): ConnectivityChange for WIFI: CONNECTED/CONNECTED

okay, thanks, i'll try this!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zimlokks:
let me get a full logcat plz post on pastebin i wanna see if anything else changes at the same time
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mohankm:
I faced similar issue with some other android tablet and the only solution I could do was to disable all security in Wi-Fi router and make it open. This was stable. I made my ssid hidden at that time.

Frankly speaking this can be a work around if you are desperate, try..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ejatds:
don't want to risk that :/

also, i need to access the wifi at school and other places as well.. :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ejatds:
ok, the file was too large i guess ill have to make another one :P
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ejatds:
trying to create a logcat but it always ends up being over 500kb, the max file size :/

but i see messages such as:

I/wpa_supplicant( 3161): rfkill: Cannot open RFKILL control device
W/wpa_supplicant( 3161): wlan0: Failed to initiate AP scan

is there a specific part of the logcat i should be focusing on to paste to pastebin??
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zimlokks:
ok umm that should be enough info. nandroid then do this... 1) back up 2) take the wap_supplicant from the stock rom 3)move it to where it is on the current custom rom u have set proper permissions and reboot 4) profit?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ejatds:
i just cut out most of the beginning of the logcat and pasted it to pastebin, didn't see your reply haha

here it is anyway. http://pastebin.com/976unUv8

so i'll try overwriting the wpa supplicant with the one from touchwiz 4.0.4. doesn't matter if the version is different (cm10 jellybean 4.1.2, tw 4.0.4) right?

thanks for the help!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zimlokks:
Thanks will look at nd i dont believe so :) your welcome hope it works
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] peneoark:
Did you uncheck the "avoid weak signal" in the wifi settings?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ejatds:
yep, that was one of the first things i tried. i unchecked avoid poor signals, and i set wifi to always be awake.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ejatds:
so there were 2 wpa supplicant files

(system/bin and system/etc/wifi)

the one in bin was stated as a 'file', and the one in the wifi folder was stated as 'CONF file) and ended with a .conf.

should i be overwriting both these files, by just copy-pasting using a file manager, or using adb?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zimlokks:
hmm replace them one at a time to see if it may work if they dont then replace both. use which ever is easier for you :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ejatds:
i think i'll just try replacing both, and ill keep the old files handy.

just finished restoring the nandroid, hope this works!! :laugh:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zimlokks:
lets hope. im going blind since i dont own this phone (bad idea on my part)

Sent from my rooted GameBoy Color
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ejatds:
so i was having problems with which file to replace, but i think it works when i ONLY replaced the .conf file with the one from touchwiz.

i guess i'll wait a day and see how it goes :)

thanks!

edit:

didn't work :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zimlokks:
im stumped im sorry i cant help...not owning a devices is pretty hard to diagnose a problem...umm try to get help from a dev :)

Sent from my rooted GameBoy Color
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Threezees:
I've had that problem before, what always worked for me was changing the region code to the correct region and rebooting. It was always set as Europe for some reason.
[HTC One X] jabr0ni:
Hi Everyone,

I'm new to the forums and Android in General.

After the Jelly Bean update, I noticed a bigger drain on my battery. On ICS I usually have an average of 24 hours on my normal usage of my HOX, but after the update, the average for the same usage just takes ~12 hours.

So I've decided to flash my HOX for a custom ROM. I really a noob in terms of rooting/flashing custom ROMs so I would like your assistance with this. I've read all the tutorials and manuals for doing things but still kinda unsure on the specific steps that I would take. Please let me know the step by step procedure that I would take in rooting/flashing a custom ROM in my HOX.

Here are the things that I've downloaded:

1. CWM Recovery 5.8.4.0

2. Fastboot

3. Firmware for CID__044 with Hboot

4. Android Revolution HD 16.0

I reckon that this would be the steps but I would like to be sure:

Preparing Your One X for Custom Roms (For Dummies)

[ROM] Android Revolution HD 16.0 | High Quality & Performance | Sense 4+ | BEST STOCK

Please let me know step by step on what I should do because I don't know specifically. Your assistance is very much appreciated. :good:

Thank you!
[HTC One X] mihirengg19:
yes the first link is correct for you...just follow those steps carefully and everything will be fine...:)
[HTC One X] jabr0ni:
Thank you for the help! Just finished unlocking my bootloader and installed CWM. Currently doing a Nandroid backup.

I'll be installing Android Revolution HD 16.0 ROM and there's a couple of things that I do not understand.

How do I do these steps? (From the ARHD ROM thread):

Proper HBOOT version for Jelly Bean based ROM (don't know how to do this. I'm already in Jelly Bean, what do I do with the Hboot?)

Flash boot.img from the downloads section (where do I get the boot.img file?)

Thanks!
[HTC One X] aman360elite:
These steps

When u go to ur bootloader ur hboot version version will be given.

If its 1.31/33/36 ur good to go :)

I am assuming u already have the right hboot as ur on JB.

The Boot.img is given in the ARHD thread itself see properly.

Now to the flashing part.

Download the boot image and keep it in ur FAstboot folder.

Go into bootloader mode.

Select fastboot

Connect phone to pc using usb cable.

In fastboot give command fastboot flash boot boot.img

and then Fastboot erase cache

Now go to ur recovery and install the ROM.

Done :)
[HTC One X] jabr0ni:
Thanks for the help!

I've run in to another problem again.

I've installed ARHD 16.0 custom ROM and I've already booted.

Upon checking the settings, Airplane Mode is stuck at "turning off", WiFi "error", there is no IMEI.

Hope you can help me out with this as well.

Thanks heaps!
[HTC One X] Goku80:
all i can i say if you have installed the rom and it has already booted is to do a clean wipe again and start over....make sure you do a backup first and do a full wipe and flash the rom again my friend and see what happens..normally a full wipe would fix the problem....check also in the ARHD thread and search if anyone had the same issues as you
[HTC One X] aman360elite:
Reflash!

Some Other users have also faced the problem.U should have MD5 of the downloaded file but no prob.Just flash the ROM again problems will be gone :)

CHeers

And yeah full wipe + Dalvik Cache too!
[HTC One X] mihirengg19:
1. go into fastboot mode from bootloader

2. flash boot.img

3. go into recovery from bootloader

4. FULL WIPE-factory reset, wipe cache partition, wipe dalvik cache..

5. reflash rom from recovery.

now there should not be any problem...;)

and u have done a good thing making a backup:good:

the boot.img can be found inside the rom zip file....or a specific compatible kernel(boot.img) prescribed by the dev can be flashed...
[HTC One X] jabr0ni:
Thank you

Hi All!

Thanks for your replies! My phone is now working with the ARHD ROM!

I re-flashed the boot.img file included in the ROM and erased the cache and everything is working now!

Kudos to all of you and once again thank you for the help!
[HTC One X] mihirengg19:
no problem...always happy to help...:D:)
[Galaxy Note II Q&A, Help & Troubleshooting] w7y7a7t7t:
Hey, i'm getting a note 2, should be here tomorrow (yay!) I have a question about playback that maybe someone who has one could answer, i did some googling but sadly found nothing. How is the playback when your playing 720p and 1080p .mkv? Can the stock player do it? and if it can't how is it on 3rd party players? Does it jump or stutter at all? Thanks
[Galaxy Note II Q&A, Help & Troubleshooting] IamPro:
I use MXPlayer for almost everything
[Galaxy Note II Q&A, Help & Troubleshooting] gandalf21502:
MXplayer is the way to go!
[Galaxy Note II Q&A, Help & Troubleshooting] foxmeister:
The Note II is the first Android device I've owned where I've felt no need to use anything other than the stock player (and I've had many, going back to the G1).

Regards,

Dave
[Galaxy Note II Q&A, Help & Troubleshooting] gandalf21502:
For the most part the stock player will play well, but some 1080p videos it will play choppy a bit. MXPlayer plays them ssmmmoottthhhh!
[Android Q&A, Help & Troubleshooting] metalhawj:
is there any way to reconfigure the gamepad settings for GTA3?

i know you can change the touchscreen controls but is there a way in game to change for the gamepad. i am using a ps3 remote through the sixaxis app and using native gamepad settings.

I am aware that you can create touch settings but i can not find any premade settings that will work with my S3. since the app supports native gamepad, i havent found any updated touch profiles on XDA or google. i tried making it myself also, not working out too great.

im asking because the right analog stick for native gamepad sucks. you cant control the orientation of the screen. it changes you to first person and is useless.

does anyone have a solution to this or an updated touch profile fixing this.
[Android Q&A, Help & Troubleshooting] mista.maja:
wow, finally found someone with the exact same issue. any news on this?
[Samsung Galaxy Nexus] speedyink:
I'm a hobbyist photographer, so while I was looking through wallpapers on my Gnex I got a sudden idea.

Making a wallpaper I got here fullscreen (from a HD wallpaper pack in the app section), I ran to my bathroom, propped up my phone on my granite counter top, and took this picture. Obviously the Nexus is the top set of apples and the reflection is off the counter top.

Did I say I love my SAMOLED Nexus?

Edit: I had to retake the photo, the over exposure was killing me =P
[Samsung Galaxy Nexus] speedyink:
Appreciate the thanks guys :good:
[HTC One X] heber_cc:
After an update unsuccessful, my phone displays a list of problems:

1 - After upgrading unsuccessful. I tried to go back to Original ROM (STOCK), then came the first problem, the screen hangs after a few minutes, generating duplicate images or shuts off completely, but with some precionadas the power button, alloy display.

2 - When I turn on the computer, device is not accepted,adb not recognizing.

2.1 - I tried other machines, already reinstalled the drivers from htc, but the computer only recognizes the device as MY HTC or fastboot.

3 - The Cellular carries not more than 10%, it is restarting the 5 in 5 minutes.

4 - some times he connects with the lcd working, and I see that it goes up to the htc logo and hangs.

Well, these are the problems. If someone managed to revive your device, please help me.:crying::crying::crying::crying:
[HTC One X] heber_cc:
could someone help?
[HTC One X] Vcek:
What is your Hboot version, and what is your base version ? Don't panic, HTC One X is currently unbrickable.
[HTC One X] heber_cc:
Official ICS rom 2.17.707.3 Asia WWE

after giving the above mentioned error, I tried to reinstall the official rom and could not longer access my mobile device: kernel, recovery, hboot and boot belong to this rom.
[HTC One X] yode:
not the same but STILL PROBLEM

stock rom , relocked bootloader , voodo ota rootkeeper , BUT WONT UPDATE ( it starts good and at 1/3 stops with red triangle)

PPPPLLLLEEEAAASSSEEE!!!!!!!!!!!!!!:crying:
[HTC One X] heber_cc:
help!

will be having someone who knows how I can solve the problem, or part of it?
[HTC One X] ckpv5:
When you said "reinstall the official rom" can you tell us how did you do that.

Was it you reflash your device with a RUU ? Or a nandroid backup ?

Please also tell us what is your hboot no. written on the bootloader.
[HTC One X] Vcek:
Install the official rom without any modding. Then you can update.

Sent from my EndeavorU
[HTC One X] heber_cc:
how can I update if the battery does not want to carry more than 10%, as pointed out just above.
[Verizon Samsung Galaxy S III] 8ttype4:
Whether it's stock, free, or paid, what text message app do you recommend? I'm tired of losing my messages after I change roms..
[Verizon Samsung Galaxy S III] kintwofan:
Download super backup. You can backup your texts and call logs between flashing. I use the stock app

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] 8ttype4:
Thanks

Do you use this alongside titanium backup?
[Verizon Samsung Galaxy S III] Hypera:
SMS backup & store is good, but slow at restoring. I think Handcent subscription portion has a backup service.
[Verizon Samsung Galaxy S III] kintwofan:
That one works good too, but is slow. However super backup saves to your SD card so if the phone is destroyed they're gone. I use both. Super backup for flashing and SMS backup to keep a more secure backup in case my phone is destroyed.

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] 8ttype4:
2

I need
[HTC Rezound] texascfdad:
Maybe this question belongs in the general android dev section, if so then sorry. What makes a phone "brick". I know what it means, but why can't we in brick them. If everything is wiped, what keeps us from accessing the wiped partition with a pc and doing what we want to with it. We do it with computers all the time. I know its not exactly the same, but its very similar isn't it? Is it like the BIOS going bad on a pc that causes them to brick?
[HTC Rezound] Max725:
From what I have heard, at least on the Rezound, bricks are generally caused by bad hboots. People do often compare hboots to BIOSs, but when they do, they always qualify their statements, adding that the two actually have little in common, but it's the best comparison between Android and PC. I'm sure someone else can explain that a lot better than I can. I believe a brick can also, theoretically, be caused by a bad kernel/boot partition, since it is what tells the phone where to get the information needed to boot (or something like that).

People also sometimes call it bricking when they just mess up the hardware in some way, like while replacing the digitizer.

Their are methods to unbrick from an hboot related brick, but they do not always work.
[HTC Rezound] SteveG12543:
What Max said.

Just wanted to say you did indeed post this in the correct section. Even if it's a development related question, questions belong in the questions section :)
[HTC Rezound] ryanshew:
I always thought the same thing why can't you just wipe everything and reinstall if the brick is caused by a software issue then what's the stop you from removing that software and putting working stuff on.

The only thing I can think of to answer my own question would be, for example, you know how you can adjust the voltages to the CPU, well lets say you install some bad or damaged software which controls the Hardware say you send too much voltage to a component such as the CPU and you fry the component by sending too much voltage or maybe its even possible by sending not enough voltage.

Just a thought anyways . I could be way off I have no idea really.
[HTC Rezound] Squirrel1620:
Bad hboot brick is the most common common and it is irreversible because you need a functional hboot to flash anything. So a corrupted hboot leaves you with a catch 22. Your hboot is bad, you want to flash a working hboot but your bad hboot can't flash anything so your stuck.

A kernel or bootlooping brick is a soft brick because you can still boot to hboot or recovery and flash a working kernel
[HTC Rezound] texascfdad:
Can't a bad radio brick it too? I know on a pc you can start with nothing, no boot partition or mbr, and the kernel is flashed with the os (windows, linux), and you boot from a cd or floppy. The only thong you start with is BIOS. Is being incapable of booting from another source like USB or sd card the main reason we can't unbrick most phones? I guess I'm just looking for deeper detailed nerd answers for a better understanding. I'm a nerd as most of you would probably claim to be too lol and I just want to get a better understanding of how it all works.
[HTC Rezound] V0latyle:
There are three main parts to phone firmware. You have the boot loader, which handles very low level stuff and generally doesn't touch partitions, but provides a boot environment for other software such as recovery and system...which is why, in Broad com routers, it is called the CFE or Common Firmware Environment. Think of it as the BIOS of the phone. If the boot loader is corrupt or damaged, chances are there will be no way to recover the phone via normal methods; JTAG must be used to directly interface with the hardware and force reflash of the boot loader.

Recovery is in a way like DOS. It has the ability to create, mount, change, and delete partitions, but can't touch low level stuff like the radio or bootloader. It can modify and remove files on partitions and change specific things such as the kernel. A damaged recovery can usually be fixed without any special tools as the phone will boot but won't go into recovery mode. In the case of the Rezound, a PH98IMG flash would fix it.

The operating system of the phone is as Windows or Linux GUI is to a computer. It provides the user with an easy to use environment as well as tools and software to help the user do what he wants to do. A damaged OS may boot, and problems may be limited to a few specific apps, or the problem may be system wide to the point of unusability...or if there is something wrong with the kernel, the OS will not start at all, and will be stuck in a boot loop. Easily fixable via recovery.
[HTC Rezound] feralicious:
What's JTAG?
[HTC Rezound] GrayBoltWolf:
A lot of devices have JTAG ports that allow us to use another piece of hardware to access the deeper levels of the hardware and software.

This makes it possible to unbrick by fixing those deep files that are required for the device to work.

Also, Wikipedia is your friend. :)
[HTC Rezound] GetRipped:
Here's the nerdiest answer you're going to get. Your phone is ultimately just a large hunk of copper and silicon. It contains all sorts of microchips and connections and are necessary for literally every function of the phone. Literally... From the LEDs to the audio components. Everything. If youve heard of a schematic that's what I, talking about. Each one of these microchips must be programmed form its specific function. Were literally talking hardware level here. No Android OS no hboot etc.

Point of explaining all of that being that there are all sorts of programmable parts of the phone that you will never modify, access, or even think about. If you manage to access and screw up the wrong thing.. You can quickly go from functioning phone to just a hunk of copper and silicon. Hboot is the lowest layer software that devs will modify. If you screw up the hboot.... You are left with a brick. Is it ultimately possible to unbrick in any situation? Yeah of course. How else would HTC have made the phone in the first place. But if you screw up the hboot... You're gonna need an engineering degree to fix that thing. And at the cost/effort that that would take.. You'd be better off buying a new phone. Thus your phone is totaled and its best use just because a paperweight.
[HTC Rezound] CharliesTheMan:
I think it's important to note that most of the phones people post about being "bricked" aren't actually bricked. A lot of times people panic and if they can't fix their phone, they call it a brick. It's kind of a common, often used slang term. Now there's terms like hardware brick, hard brick, software brick, and soft brick and probably some more.

But if it's fixable in my opinion using a computer and commands, or if you can see it's getting power, it's usually not really bricked.

For example, when the s off process came out the forums were over run by people who "bricked" their phones while trying to attain s off. What actually happened in a big number of these cases was that the windows script replaced the boot.img that was on their phone with a custom boot.img for the service mode. When there was a windows error with the software which was newly developed and released, and the windows app hung up or the computer went weird mid process, they had a black screen with a funny image, like a disk and arrow maybe, and when they turned the phone on it only went to that screen. In fact it happened to me which is why I figured out how to fix it and what caused the problem.

Now all they would have had to do is run a fastboot command from their computer, "fastboot flash boot boot.img" to flash the boot.img that matched whatever rom was installed on their phone, and they would be back up and running. But for a large number of users, when they phone was unresponsive and turning it on took them straight to the black screen, they considered it "bricked."

When in fact the phone was doing exactly what it had been commanded to do, and it was the person who was expecting something unreasonable, when you think of it in 1's and 0's, or black and white. Of course this isn't always the case, there are some real bricks, just not as many as one would first believe if they scanned through forum topics for the word bricked in the title.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tony_YYZ:
So I upgraded to Jelly Bean using the OTA on Rogers. I used Voodoo to maintain my root access but it only seemed to preserve it for the apps that already had access. I was trying to flash CWM on the phone today only to find out root is broken.

What is the easiest way for me to regain root access? I uninstalled SuperUser and reinstalled it without any luck. Now the root apps like TiBu that were working before are no longer working.

I need some guidance on how I should proceed to get it back. I really don't want to have to wipe all my data if that can be avoided. I was able to install CWM using ADB. But I'd rather have my root functionality restored in my TW ROM so that I can make a proper backup before beginning to flash custom ROMs.

My details are in my sig. Thank you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CZ Eddie:
Just re-root it. You don't uninstall and re-install Superuser.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tony_YYZ:
Would you think the best course of action is to flash the SuperSu.zip via CWM or reload the OS on top using Odin/MrRobinson's method and have it repair what's broken?

I noticed my flash counter is now showing 1, don't know how that happened.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pizzlewizzle:
Did you try updating the superuser binarys first?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tony_YYZ:
How would I go about doing this?

I currently have Superuser installed, not SuperSU(Although it looks like more people are using this now)