yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Q&A, Help & Troubleshooting] LuisinhoUlisses:
OK. Thanks man!

Just to be clear, when you say let it discharge, you mean discharge until it die? There is no problem in doing that?

Thanks and sorry for my noob questions.
[Nexus 4 Q&A, Help & Troubleshooting] AlmogK:
Yes, dischrage till the phone is dead (the extremist even turn it on few times till even the boot logo isn't show anymore) and then fully charge to 100% +2 hours.

don't forget to clean battery logs before! :]
[Nexus 4 Q&A, Help & Troubleshooting] failly:
You can do both, either let it die or charge it when around 2%.

You can also wipe battery stats but that won't have any effect on the type of battery we got!
[Android Q&A, Help & Troubleshooting] Metalface91:
Hi I've tried many cm9 rom on my phone and the UI always freezes randomly eg. listen to music the music countinues playing but the UI conpetly freezes there's only one solutiin if i replace the battery or reboot my phone through adb are there any fixes for this issue?
[Android Q&A, Help & Troubleshooting] utanamun:
Turn on screen rotation in setting. If you dont like rotation you can set 0 degress

WeChat ID: Utanamun
[Android Q&A, Help & Troubleshooting] Metalface91:
Thanks, it's now working fine.
[G2 General] BlueHarford:
Anyone have success charging with a case on?

I got the incipio feather woke up this morning phone was warm and only at 50%
[G2 General] AmbroseAI:
Which charger are you using? Did you hit the "sweet spot" for charging (if there is one on your charger)?

I have the TYLT VU and have had no issues with it, although I have a "skin" on my phone instead of a case.

PS I've been waiting for the incipio cases to come out but their website says they aren't available yet. Where did you get yours?
[G2 General] BlueHarford:
LG WCP-300 the one verizon sells. like a disc.

i got my from verizonwireless.com they only have the feather.. fits nice. 25 bucks. guess the magnet isnt strong enough or case it too dense, even tho its pretty thin
[G2 General] godsfshrmn:
Should work fine. I charge my nexus 7 through a thick rubber case. I have the Nokia qi
[G2 General] joshuadjohnson22:
same here I charge my active through *most* cases there are some that do not work. The case itself gets hot but charges fine, slow but fine
[G2 General] eth3rton:
I came from a Nokia Lumia 928 and had the wireless Nokia charger. Works fine on the G2 in the folio case. Every once in awhile I have to re-position it or it acts a little wonky - charge, no charge, charge, no charge... other than that it charges quickly.
[G2 General] truckroot:
I have the same charger and works fine with Verizon TPU and LG Quickwindow cases.

From a Verizon logo plastered G2 bastard
[G2 General] JTNiggle:
Like was mentioned earlier, there's a sweet spot for charging. I almost think that LG and other phone makers should have some sort of label/insignia for the center of the charging coil so we would know. But they don't, so lets look on the inside.

You can see that the center of the coil is below the center of the phone. So, if you're using one of those small round LG chargers, you wont be centering the phone on the charger. And if you're using the Nokia 900 oval charger, you want the bottom of the phone to line up with the bottom of the charging pad, where the indicator light is. I have messed with this quite a bit and have found this placement to be ideal for consistent charging. If you are a little off, it may charge, but it may also go in and out. Each time it goes in and out, it wakes the phone and draws power, thereby reducing the effective charge.

I have no trouble charging my G2 with a heavy Ballistic case on it, on either the Nokia 900 or 910 chargers with the above method.
[AT&T, Rogers HTC One X, Telstra One XL] Sonone:
My apologies if this has been repeated before but i would like to just clear some things i have in my mind?

it may have been repeated but i would sincerely appreciate if someone just elaborates!

My understanding at present is:- i know root gives you more access,bootloader is a script or a code to load up os and kernel,s off gives us extended rights to some partitions,supercid makes it possible to flash any ROM irrespective of carrier and region,the firmware essentially contains the bootloader (hboot) and radio and lastly RUU is a utitlity to upgrade rom which can be region and carrier specific.

PLS correct me if m wrong?

So RUU+Supercid+SOFF can cause bricks?:eek:

which implies if at all RUU is used we need to be be on SON and CID should be 0000000?

also if i have OTA updates for a ROM that is from some other Service Provider and I am on SOFF and SUPERCID it still will brick my phone?

and lastly i have S0FF SUPERCID and Unlocked Bootloader and obvioulsy rooted:o

so what all on earth i should avoid doing? :confused::confused::)
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
You've got it the wrong way around. It goes like this: SuperCID + s-on + jb RUU = brick. Having s-off means you can run any RUU (Evita) without bricking. Other things that can cause a brick are flashing software not intended for our device (ROM/kernel/radio etc), running an RUU not intended for our device, in some cases altering the hboot has caused bricks. In some other cases running an Evita RUU has caused bricks if something goes wrong during the process. You shouldn't take an OTA unless you have the correct preceding ROM/firmware already on the device, plus you need stock recovery and I believe (not 100% sure) the correct CID. Personally, I wouldn't take an OTA on a modified device.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] Sonone:
Given this background if something happens and I need to go back entirely to a factory configuration what can be done?

i have always wondered does EVITA have any Application Utility (with a user friendly GUI ,terminals and prompts scare me)?

i have the all in one tool kit!! besides that?

and can flashing ROMS cause brick cause in The OP's of various ROM release threads i have read something like "brick fixed"?

and is it appropriate to use Goo Manager and the ROMS listed there?

btw after my epic failure of flashing a kernel ( now u see m really a noob) i accidentally happened to wipe my entire phone through TWRP and by mounting it i was able to get it back again that time i observed that the phone still has the bootloader but not the OS so which led to another question that is the boot loader a part of the firmware?

I know m wrong but somehow i just cant connect the dots!

excuse me for my bad English!

I really wonder at times why people like me total newbies take the risk.. but then i realize when u just have that little more control of your device and it stands out in the crowd its worth the effort and the calculated risk!

Cheers to all the developers!! :good::laugh:
[AT&T, Rogers HTC One X, Telstra One XL] Sonone:
you know what.... you are a savior and a hope for many! :good:

thanks!

so Supercid + SOFF + JB Ruu is not bricking your device (exceptional failures and human error in the process not considered)
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Absolutely correct, sir.

Sent from my Evita

---------- Post added at 10:45 AM ---------- Previous post was at 10:35 AM ----------

If you want to go back to a factory configuration all you need to do is run an RUU.

I think the ROM threads with the "brick fixed" would be the cm threads. There were a few builds a couple of months ago which had caused bricks but they've been fixed now.

I personally don't like or encourage the use of any automated flashing tools like Goo Manager, I simply don't trust them. Many users do use it with success though.

The bootloader/hboot is part of the firmware, this partition is unable to be wiped through recovery. So even if you do accidentally wipe everything in recovery you can always get to your bootloader and recovery.

To be honest I think it's totally worth the calculated risk. You have so much more freedom with your device, the ability to flash pretty much any ROM you want is awesome, plus you're able to access features that a stock configuration can't provide. In saying that, there is obviously a certain level of knowledge required to do this. Without that level of knowledge the risk is far higher, this is why we see many people bricking their device, because they've rushed into modifying it without doing the appropriate research first. It takes some work to learn it all, but the information is freely available and easy to access. We have a great community here, some great people with a combined pool of knowledge that can be called upon if someone gets into trouble with their phone.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] spyrobiskinis:
Why s-on is brick friendly since it's a safety measure?
[AT&T, Rogers HTC One X, Telstra One XL] twistedddx:
For the "what exactly causes the brick" my theory goes like this:

AT&T yelled at HTC that devices were ending up unlocked.

In that yelling someone decided the best way forwards was to block AT&T users using supercid 11111111 to get unlocked on HTCDev. This meant that even if a new root method was found a user with supercid still could not unlock. As a side thing it looks like they attempted to block supercid users getting future updates also.

We saw on HTCDev that they blocked supercid 11111111 for AT&T devices. It looks like as a simple oversight either by HTC or because AT&T only requested 11111111 be blocked that all other supercid variations still work. The oversight is likely because whoever decided on the block did not realize that 11111111 is only one of many supercid strings.

So now back to the side effect of attempting to block supercid users getting updates causing bricks. This issue is maybe deliberate or more likely accidental, it appears the block was not well thought through or tested before being implemented as seen by the HTCDev oversight.

I believe somewhere in the update the software checks that it is being installed on a device with the correct CID and in this portion of code ALL supercids were removed from being allowed.

There is at least one check right at the start(the update-script) that still includes the supercids as being allowed, which is why the updates starts, but later on another check in a different piece of code has had the supercids removed as valid cids. Because of this the device gets half way through the update and stops, leaving the device in a brick state.

I think whoever "designed"/made the change to remove supercids may not have understood that they had not removed the supercids from all required places to prevent bricks as we have seen. But at least they understood that there is many supercid strings and managed to block/remove them all.

Having s-off is allowing the check half way through to pass successfully. Likely because the update code doesn't bother checking CIDs if you have s-off and s-off checks were not what HTC/AT&T were looking to block at the time(s-off came later).

Why they wanted to block supercid users updating might be related to AT&T saying users that had not purchased their device from AT&T were being able to use AT&T propriety code without paying them to do so.

Silly argument but something large corp execs would get insane and illogical about.

I doubt the bricks were intentionally designed by HTC or AT&T. It is a side effect of poorly thought out blocks requested by AT&T related to blocking unlocks and blocking non AT&T users using AT&T software..
[AT&T, Rogers HTC One X, Telstra One XL] Sonone:
So in a way they were trying to avoid HTC devices being used on the other carrier networks and hence resorted to block such devices getting official software updates but the check for supercid occurred at a later stage of the procedure and it abruptly discontinued the entire upgrade causing bricks!

it seems reasonable although but rendering the device completely useless seems a bit harsh!:(

so users with supercid should stay away from RUU?

and Soff doesn't have any effect on the procedure it seems?

and u also mentioned Sir that there are multiple CID thread would you please elaborate!:angel:
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
The unlocking process he's talking about is the bootloader unlock, which is entirely separate from a SIM unlock. A bootloader unlock doesn't allow a non at&t SIM to be used. Basically, at&t didn't and don't want their phones to be able to have their bootloader unlocked and have custom software installed.

Users with SuperCID are totally fine to use an RUU, but they MUST have s-off first. Having s-off makes the RUU process safe.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] twistedddx:
Supercid + s-off is fine.

Being s-off turns off the current check for CID that is bricking devices.

11111111, 22222222, 33333333, 44444444, 55555555, 66666666, 77777777. 88888888. 99999999 are all valid supercids. But shhhh don't tell AT&T, as I'm sure in the next update 22222222 will get blocked and we will all move to 33333333. :)

This isnt about a user that bought an AT&T phone and wants to use it on Sprint USA etc. It is about a user buying a phone from Canada(or Hong Kong, Singapore, Australia etc) and importing it to USA and then switching it over to AT&T software. Or pretend for a minute AT&T made some amazing image editing app that they dont want to give out for free, but Australians users are getting it for free because they have supercid. It all seems like a knee jerk reaction to understanding supercid, how it was allowing their devices to be unlocked and a realization that overseas users might have supercid also and have AT&T software(and therefore potentially access to servers) for free.

"You told us the bootloader was locked, why are users still unlocking?!!"

It appears AT&T have told HTC to block supercid(in particular 11111111) for their devices. Exactly where blocking supercid translated to only 11111111 on HTCDev is unclear, it is likely AT&T's fault for not understanding the technical details of what exactly they were requesting.

"Well if they will likely be able to find a root exploit just block supercid 11111111(that they keep using) from HTCDev for our devices, then the problem is fixed!!!!"

And in my fictional version of the story the programmer that was told to block supercid 11111111 from being able to receive updates managed to correctly translates that request back to any supercid, but stuffed up by blocking the update too late in the update process.

Things get very pedantic in these types of cases. AT&T might have said "our propriety software must not be installed on supercid devices", so the non AT&T code starts installing but at the moment AT&T code is about to be transferred the update stops or something.
[AT&T, Rogers HTC One X, Telstra One XL] Sonone:
LOL like that!!

Big corporations and their big plans!

but again we cant blame them!

so having S-OFF actually has given the users a lot of freedom!

it is an important thing!

(just realized it now)

explained really well btw!
[Galaxy Ace II Q&A, Help & Troubleshooting] HalmyAK:
sorry for disturbing everyone i have big problem about my phone samsung galaxy ace 2 (rooted) if i know this can be i wouldnt never root again its because im newbie im just want my phone unroot and reset binary counter to become original again but...

story

i have install avg virus to ignore threat root because i dont know how to unroot then i install supersu to unroot but its temporary not permanent and i have installed otarootkeeper to check root then just 1 system root protection is checklist other not checklist and then i have try to update new os to jelly bean 4.1.2 then my phone is still custom os i want make original again and i try check internet is need too install triangleaway root for reseting binary counter but i open app and say need super user access but my phone access is gone or uninstalled (should i root phone again to become original but i dont know how to root ) my phone rooted by brother friends

what should i do please help :(:(:(
[Galaxy Ace II Q&A, Help & Troubleshooting] so1000:
try this

try this http://xdaforums.com/showthread.php?t=2025096
[Galaxy Ace II Q&A, Help & Troubleshooting] HalmyAK:
thank you but should i must update my jelly bean back to ginggerbread ?

Im just want reset binary counter to back original not custom os
[Galaxy Ace II Q&A, Help & Troubleshooting] tofueatsbread:
root phone (dont worry, ive done it maybe more than 40 times already(i like to change roms once in awhile) its perfectly safe,for now) and give triangle away root access, reset flash counter and unroot, done

EDIT: and you dont have to flash stock jb again, resetting flash counter and unrooting is enough
[Galaxy Ace II Q&A, Help & Troubleshooting] HalmyAK:
Thanks but i have unroot phone but its still custom os then i try open triangleway root needed superuser acces but my superuser has uninstalled then need su binary. What shiuld i do ? Must i root device to get su binary then reset binary counter ?
[Galaxy Ace II Q&A, Help & Troubleshooting] tofueatsbread:
root device again, give triangle away root access and reset flash counter, then unroot(and delete root apps as well)
[Galaxy Ace II Q&A, Help & Troubleshooting] HalmyAK:
Thank you but how to add su binary to access superuser i dont hve it and my brother cant help me its because just my brother friend know it, or show me tutorial thread and unroot because im unroot using supersu ?thx
[Galaxy Ace II Q&A, Help & Troubleshooting] tofueatsbread:
what? root using the zip from [MENTION=4060849]Shaaan[/MENTION]. supersu will be included just give triangle away root acces reset counter and unroot
[Galaxy Ace II Q&A, Help & Troubleshooting] HalmyAK:
I hve download root zip for jelly bean by shaaan and where i can place root zip file i hve following tutorial by shaaan but not working say recovery mode but just showing volume up continue volume down cancel no install root ?
[Galaxy Ace II Q&A, Help & Troubleshooting] tofueatsbread:
locate zip, select and press power button- yes. then reboot
[Galaxy Ace II Q&A, Help & Troubleshooting] HalmyAK:
Im very sorry im still not understand i save file root.zip in external sd card i dont know wehre locate zip file then i have following your instruction but still not have su binary for superuser or rooted please step by step thx
[Galaxy Ace II Q&A, Help & Troubleshooting] tofueatsbread:
1. put root.zip in /sdcard

2. reboot to stock recovery

3. select apply update

4. you should see root.zip select it

5. select yes

6. it will say installing temperory busybox and then is will uninstall(something like that)

7. reboot to system

note: to select press power* button
[Galaxy Ace II Q&A, Help & Troubleshooting] HalmyAK:
K thx i have reset binary counter but why my phone still custom os ( i hve install new firmware from sammobile )
[Xperia Z1 General] sj8023ld:
Original post can be found here http://www.digi-wo.com/thread-8924-1-1.html

Firmware Info:

Firmware Version

14.1.G.534

Brand

Commercial&Journalist

CDA

1277-1398

Download Link：

http://pan.baidu.com/share/link?shareid=861120694&uk=286154023

http://sdrv.ms/1dALjJy
[Xperia Z1 General] Geoffxx:
If anyone can get their hands on an ftf for HK please post here

and on the above firmware what is Commercial&Journalist
[Xperia Z1 General] iSaaa3d:
Does it have Arabic Language ?
[Xperia Z1 General] auchengyu:
any chance to get for 6902??~~
[Xperia Z1 General] DooMLoRD:
yes please get this for C6902!
[Xperia Z1 General] auchengyu:
this is for 6903 right?... 6902 cant use it.,...safely right?
[Xperia Z1 General] yeeson:
6902 no flash！
[Xperia Z1 General] auchengyu:
6902?

Anyone can upload a 6902 version? if it exists~~~?
[Xperia Z1 General] Beards:
Anyone in the UK with SIM free received this update?

Thanks

Beards
[Xperia Z1 General] Apoxx:
Still on .518 with unlocked phone. No OTA updates so far.

Did anyone try this update; if so, is the camera just as crappy as before?
[Xperia Z1 General] SirRobin78:
Update for .534 is started in germany, updated my Z1 a few minutes ago :)
[Xperia Z1 General] m3dd0g:
Can you post your CDA number?
[Xperia Z1 General] Sean473:
That's good to hear.. Hopefully reaches UK soon!
[Xperia Z1 General] SirRobin78:
My device is 1277-0154_R7A
[Xperia Z1 General] freestaler:
Its same in Switzerland for my unbranded one. Update done. :)

I think camera is now littlebit better. Not so "noisy". Still like a cam with a small lens, but better as .518. but i had to test more.
[Xperia Z1 General] Sean473:
The actual camera firmware update isn't till next month... Still seeing no update here in the UK.. Hopefully here by tonight :)
[Xperia Z1 General] gibbo82:
Still no uk update. Im using a sim free Z1, unbranded.
[Xperia Z1 General] devmc:
Sony uk sucks, no updates at all so far!
[Xperia Z1 General] ~ emad ~:
Does it have Arabic Language ?
[Xperia Z1 General] Sean473:
Guys, to both of you, I suggest you flash the central europe firmware .534... Its perfect and hell my device doesn't even heat up as much as it used to. Its pretty simple to flash it and there is even a guide on the forum! Do this only if you have an unlocked UK LTE model....and not any carrier model!
[Xperia Z1 General] coolhand83:
I'm using a UK Z1 (O2) and I've got the update...
[Xperia Z1 General] Sean473:
Yes only O2 is updating them! No one else has!
[Xperia Z1 General] gibbo82:
What's the difference. Between the European version and the uk?.

Is it in English?

Sent using my Sony Xperia Z1
[Xperia Z1 General] veletron:
I just popped into the local EE store, and their demo Z1 is running .534 while my Z1 locked to EE is running .218 and no updates are available. WTF?!

Noted that theirs says 'LTE' next to the signal icon while mine says '4G' that was the only thing instantly noticeable. Guy in the shop did not have a clue.

Nigel
[Xperia Z1 General] K3yMaster:
Just received the update here in Denmark :cyclops:
[Xperia Z1 General] daleski75:
Just got the update here in the UK and installing it now.
[Xperia Z1 General] ascariss:
Yup this just seeded to me here in Poland,
[Xperia Z1 General] mas5acre:
C6903 white unlocked UK model imported to USA, just got the .534 update notification on the device. First firmware update since stock .18
[Xperia Z1 General] Feyris:
Same here with white UK unlocked model imported to France
[Xperia Z1 General] thepanttherlady:
Just got mine via OTA a couple of minutes ago.
[Xperia Z1 General] MobileBritain:
UK unbranded 534 update OTA available now.
[Xperia Z1 General] kingsizeriz:
Anyone got the ftf for UK unbranded?
[Xperia Z1 General] krazeyivan:
Finally got an OTA update! - hurrah!

Quick question - got this phone from CPW - on an EE contract - will it be carrier locked?
[Xperia Z1 General] Feyris:
Yes, I got the .534 update on my UK unbranded Z1 througt the PC software.
[Xperia Z1 General] kingsizeriz:
I mean to upload for other users
[Xperia Z1 General] ianford10:
I have created the ftf and it is posted in the general section :)
[Xperia Z1 General] Sean473:
CPW android phones are all unlocked!
[Xperia Z1 General] veletron:
Nothing for an EE Z1 yet. Probably need to flash it manually. Anyone flashed a locked EE Z1 with the generic UK Rom?

Nigel
[Xperia Z1 General] ianford10:
I haven't but it won't hurt it ;)
[Xperia Z1 General] wezzel98765:
Mine and my girlfriends are EE Z1S from,P4U. Both updated OTA today
[Xperia Z1 General] gibbo82:
anyone know whats actually new with the latest update??
[Xperia Z1 General] GeorgeCm:
Just received the update in Greece.
[Xperia Z1 General] tyw87:
Hello, may i know which version should i use for Asia version? Mainly for Malaysia.

Thanks.