yashsingh1/xdaforums huggingface dataset:
[Galaxy Y GT-S5360 and Duos 6102 Q&A, Help & Troubl] stratosk21:
The need if a update.zip is to root your phone only and install the superuser app. It is safer to root before u flash because the chances of success are higher. If u got bricked go here to ask.

http://xdaforums.com/showthread.php?t=2063534I

Happy flashing and press thanks !
[Galaxy Y GT-S5360 and Duos 6102 Q&A, Help & Troubl] wazzink:
u mean flash custom rom? it's just fine. almost all of them are pre-rooted.

and in that case, u wont need the update zip for rooting
[AT&T HTC One (M7)] sdla4ever:
Ok, so I went and unlocked my bootloader and was making good pace to root my device. Get into TWRP and it won't mount data or cache. So I then went and tried to follow a guide to rebuild the partition table and my laptop keeps giving adb device not found errors after a few commands and makes it impossible to follow that guide. I still have the stock OS installed and it boots into it just fine, but it won't install SuperSU or backup.

Using a MacBook Pro (10.8)

Newest SDK and tools

TWRP 2.5.0.0

SuperSU

I searched thru quite a few pages and havent found this issue with this specific phone yet. I will be away from the computer for the next 12 hours but after that should be ready to jump back in with you guys help.

EDIT SOLVED: It worked with the clockwork mod. I think the part that made it work was the fastboot being off honestly, all the other guides I saw didn't say anything about turning fastboot off from the power menu.

Thanks
[AT&T HTC One (M7)] ChristopherXDA:
I had this issue too and tried some of the fixes you mentioned with no luck, so I tried out the clockworkmod (http://xdaforums.com/showthread.php?t=2173863) and had zero issues. Not sure what we were doing wrong, but my One is doing great with the latest Revolution Rom.
[AT&T HTC One (M7)] sdla4ever:
Awesome I'll give it a shot when I get home and get back to you

EDIT SOLVED: It worked with the clockwork mod. I think the part that made it work was the fastboot being off honestly, all the other guides I saw didn't say anything about turning fastboot off from the power menu.
[One (M7) Q&A, Help & Troubleshooting] qwertyuiop89:
Hi, this is my second HTC one, and it seems to lag behind my previous one.

For example, when I click on a story in Blinkfeed, the usual animation is for the bottom dock to fly up, and be replaced by the story. On this new handset, the bottom dock freezes in the middle of the screen for a second, and then the story eventually loads.

In another example, the keyboard seems to register touches a few too many split seconds after me typing, so that there's a noticeable lag as I type.

I don't have any power saving features on either!

Is this normal?
[One (M7) Q&A, Help & Troubleshooting] ant78:
The only lag I have come across is while playing Simpsons tap out
[One (M7) Q&A, Help & Troubleshooting] dobknobby:
the only lag i get is playing this game too. . . I think EA needs to optimise it a little better. Even real racing and modern combat it dont lag. Just this one.

Oh, Tapped out is a Battery Killer also .. .lol. When i go into view the Battery Stats tapped out is at top!
[One (M7) Q&A, Help & Troubleshooting] darkgoon3r96:
Maybe what you're having is a hardware issue? You didn't install any Custom ROMs right?
[One (M7) Q&A, Help & Troubleshooting] CheesyNutz:
lag ha .... hahah haha haha
[One (M7) Q&A, Help & Troubleshooting] jlevy73:
I think the OP got the S4 and H1 mixed up :laugh:

In all seriousness, no lag thus far except in crappy non optimized apps.
[One (M7) Q&A, Help & Troubleshooting] jngtt:
I said the same thing, what lag?
[AT&T HTC One (M7)] EnIXmA:
So I was flashing a kernel and the thing rebooted during flash. Now it doesn't go past the HTC boot screen with that development message in red. I can boot into fast boot and recovery, but cannot find a way to go past the boot screen. Even locked and then unlocked the phone, even flashed a rom the phone,.Any way to fix this?

Thnx
[AT&T HTC One (M7)] amit34521:
first flash a stock rom with kernel and then try again
[AT&T HTC One (M7)] joshyy_rey:
1)Word to the wise. You don't have a brick. Bricks are when you can't do anything to the phone

2)what previous posters said. Wipe cache and factory wipe and flash stock rom. If you don't have a nandroid or one on the phone use adb. Push to get it there
[AT&T HTC One (M7)] shook187:
You can get into fastboot and recovery? That's kids play man.
[AT&T HTC One (M7)] EnIXmA:
Yes, I can get into fast boot and recovery. I tried fast boot, adb and nothing seems to work. Ruu for my carrier is not out yet.

So frustrated, haven't slept all of yesterday night
[One (M7) Q&A, Help & Troubleshooting] DesirableDesire:
I can't work out how to turn off the camera shutter sound. On my old One X I think that when it was on silent mode the camera shutter sound didn't go off, but in this phone even on silent it does and I can't find any option to turn it off. Does anybody know if it's possible?

Sent from my HTC One
[One (M7) Q&A, Help & Troubleshooting] xXxG0dzRAgexXx:
It goes off for me when I'm in silent. Don't see why it wouldnt work the same for you. You sure it's on silent?
[One (M7) Q&A, Help & Troubleshooting] omar302:
In camera, tap menu (3 dot icon), go to "Shutter options" (towards the bottom) > Shutter sound > un-tick.
[One (M7) Q&A, Help & Troubleshooting] the_scotsman:
The shutter sound is a legal requirement in some countries (so you can't take sneaky photos). Some carriers remove the sound option from the camera settings.
[One (M7) Q&A, Help & Troubleshooting] Terra1:
You have to be kidding.......... What's the world coming to.........
[One (M7) Q&A, Help & Troubleshooting] the_scotsman:
Only noticed the OP is an Aussie. Then I confirm this is the case. In Australia, phones MUST have a shutter sound. Silly I know....but Telstra, Optus etc branded phones don't let you remove shutter sound. This is for most of their phones.
[One (M7) Q&A, Help & Troubleshooting] zolseb:
I'm in Australia on Optus and can confirm that in silent mode the shutter does not make a noise. My phone is stock, unrooted and obtained from Optus.

Furthermore I have also unticked the 'shutter sound on ' in the settings as it has been suggested already and that works also, no sound from the camera when the volume is on.
[One (M7) Q&A, Help & Troubleshooting] DesirableDesire:
Yeah I thought this might have been the case. I have a Telstra One.. it's strange that the Optus version doesn't have it but Telstra does. Oh well just giving me more reason to root.

Under shutter options for me the only setting is touch to capture :/

Sent from my HTC One
[One (M7) Q&A, Help & Troubleshooting] mercury670:
Also on Telstra.

One XL on Telstra had shutter sound with ICS. After the OTA JB update, camera had no shutter sound in silent mode, without changing any settings.

One on Telstra definitely has shutter sound on all sound 'profiles', and the shutter sound option has been removed.

Maybe we'll be lucky and receive the silent shutter when we get the KLP update :D
[One (M7) Q&A, Help & Troubleshooting] hughboat:
ATT allows for shutter sound to be turned off.
[One (M7) Q&A, Help & Troubleshooting] nobnut:
This may well be ROM dependent, but I'm using TrickDroid 5.2.1 and when I put my phone on silent (toggle the sound through EQS) I get no shutter sound.
[Galaxy S III Q&A, Help & Troubleshooting] YesEvil:
Hi all,

Just wondering g if anyone can help.

For some reason yesterday my gallery started showing all homescreen apps as folders in the gallery. They all appear as single folders with 1 image, the app icon image. So now instead of the 2 or 3 folders I used to have I know have about 80!

Does anyone know how to fix this or what's caused it?

I'm using nova launcher pro if that makes a difference.
[Galaxy S III Q&A, Help & Troubleshooting] elspanish88:
Its not really a fix but more a work around:

Download quickpic from the market and highlight the folders and select "hide" then they won't be visible in the normal gallery I think you can uninstall quickpic once they're hidden
[Galaxy S III Q&A, Help & Troubleshooting] dxppxd:
Does it happen only with homescreen apps? I don't know nova launcher, maybe it keeps a cache with the images of homescreen apps.

Otherwise, do as indicated in the previous post, i've yet to find a better gallery than quickpick.
[HTC One X+] progy26:
My CID num is - HTC__038, version-main: 1.17.707.1, version-baseband: 3.1204.168.32, version-bootloader: 1.35.0000.

I have unlocked the bootloader and flashed CWM and the device is rooted!

Can i install custom roms like Elegancia, Insertcoin etc... ???

And I installed CWM, I want to replace it with TWRP, What is the proper method of flashing TWRP, by completely replacing CWM ?
[Defy Q&A, Help & Troubleshooting] bibihub:
Hi !

Here is my problem: Android doesn't allow to send very long sms. But I found this : http://xdaforums.com/showthread.php?t=1113854 .

According to the dev I just need to:

Change the AutoConverting:

In /res/xml/mms_config.xml change the following values at line 19:

Code:

<int name="smsToMmsTextThreshold">4</int>

to:

Code:

<int name="smsToMmsTextThreshold">200</int>

The problem is that I'm on wiui and I can't find this mms_config file ! In fact I don't even find the res repertory but I did a reaserch and I only found mms_preferences but there is nothing to change sms size in it.

Ps: I'm using root browser for it (don't want to pay an app like root explorer)

Ps2: I don't want to use a third party app
[Xoom Q&A, Help & Troubleshooting] ktang88:
Hi Guys,

Can I get some help with the following please:

Issues: When power on my Xoom(MZ601), I get the following error "Tablet is not provisioned. Please insert valid SIM card and reboot"

Steps taken to troubleshoot

1. Restore to factory settings and when reboot, I will get the above error. I wont be able to get into the tablet with that error.

2. Install custom rom - Will be able to get into the device but does not have any signal be it 2G/3G. Only can use wifi. When try to set the APN, nothing will happen.

I am suspecting I messed with the baseband version and causes this issue. I am currently on baseband 07P. I am trying to a way to fully restore back the device to factory settings include the baseband itself to see if this will fix the issue.

Is there anyway I can get a copy of the baseband N_01.100.05P file so I can try?

Thank you very much for any form of help.
[Xoom Q&A, Help & Troubleshooting] XxLordxX:
Hi,

I never saw such a problem, but if the problem is really the baseband I think you can try restoring to 100% stock (find how to do it on our FAQ), then you update until the latest version in your country, then you root again (you can find it on the FAQ again), and then give me a shout to know what happens ;)

Good luck!

"This Story Ends Where It Began" - Octavarium (Dream Theater)
[Xoom Q&A, Help & Troubleshooting] ktang88:
Thanks for your reply!.

I have tried what you've suggested where I restore it to full stock but end up just getting the same error message. I'm using this package (MZ601_H.6.1-38-9_Other_International_Retail)

I even tried to restore it to (MZ601_H.6.1-38-1_Retail_Europe) whereby it actually allows me to setup my tablet and I'm able to get into the device finally which was a good sign BUT, I guess Europe spec's doesn't support my telco's :eek:, therefore again, I did not manage to fix the issue.

The same sim, if it were to insert to any of my other devices, it will just work fine.

And when I was doing the europe package, the baseband change to some older ones at first, then as I upgrade it with the stock patches, in the end it went back to 07P again!!!!

Is there any way I can find the baseband 05P files so I can try to flash it back and see if it works? I strongly believe I've messed up with the baseband file whereby now my device cannot find signal.

If there's anymore posibble area that you think I've posibbly messed up, please let me know. I have played with the device long enough but this time I'm really stucked. :D.

Appreciate your big help!
[MDA II, XDA II, 2060 ROM Development] ID64:
ok, now I am totaly screwed.... imate stuck in loading screen with version numbers etc... Not going further and bootloader not available.... Is there any way to communicate with unit while it's in this mode?
[MDA II, XDA II, 2060 ROM Development] Victor:
what you are saying is unclear. Does your device say "Serial" (or "USB") on top with "V 1.06" on the bottom?

If so, you ARE in bootloader mode. If not, then please specify what it actually says on the screen
[MDA II, XDA II, 2060 ROM Development] ID64:
no, it's not in bootlader mode. it's in Tmobile screen at the bottom it says R 1.12.00

G blah

D blah

it stuck there. and I can't enter bootloader mode. looks like it's totaly dead
[MDA II, XDA II, 2060 ROM Development] Victor:
What happens when you try to enter bootloader (Power - Action - stylus)?

What happens when you try to press (Camera - Record - Stylus)?
[MDA II, XDA II, 2060 ROM Development] Ivan_R:
GO TO HELL ROM 1.72.104

F%@#&!?G FREAK ROM!! :evil:
[MDA II, XDA II, 2060 ROM Development] Victor:
Please calm down... in a day or two, this problem will be solved and everyone will probably be back to where they were

((and a lot smarter than they were too))
[MDA II, XDA II, 2060 ROM Development] ID64:
It both cases it still sits in this screen :(
[MDA II, XDA II, 2060 ROM Development] Victor:
Try removing the battery and waiting for a period of time (20 Mins ??)

Then try the two things again (first without the battery -- for the heck of it -- and then replace the battery and try them)

...obviously, you need to remove it from the charger too :wink:
[MDA II, XDA II, 2060 ROM Development] Victor:
to be clear... nothing is expected to happen when you try to do these without the battery in, except perhaps (??) clear out any remaining charge held in capacitance, if any.

Kinda like removing the batteries in the remote control of a TV and then pushing a button on it (there is always enough charge in the capacitors for a single push/command to the TV
[MDA II, XDA II, 2060 ROM Development] Rudegar:
that once happent to me

and softreset dident help

so i did a hardreset and that fixed it

fixed my data too though :/
[MDA II, XDA II, 2060 ROM Development] ID64:
nothing happenes :( Sent email to imate tech support. I am not sure if they going to warranty unit with Tmobile betta screen stuck on IMATE. looks like i am short 700 USD........ :( :( :( :( :(
[MDA II, XDA II, 2060 ROM Development] ID64:
Is there any way to communicate with XDA2 when it stuck in this loading screen? Terminal via serial cable doesn't work. anyother low level programs are out there? please, help.
[MDA II, XDA II, 2060 ROM Development] Victor:
Have figured out that the problem is in the Bootloader. If there is a way to (and I know there is) revert to an older Bootloader version, then the problems will all be solved.
[MDA II, XDA II, 2060 ROM Development] ID64:
That's great, but unfortunately my device is one step more screwed that others - no bootloader :( not even working Windows now.

Is there any way to boot directly from SD card?
[MDA II, XDA II, 2060 ROM Development] vwonges:
victor,

can you upgrade or downgrade the bootloader ? If you can, HOW? please post the way to upgrade or to downgrade the bootloader. :shock:
[MDA II, XDA II, 2060 ROM Development] ranger:
ID64,

I had an XDA I and wiped the bootloader by accident. As far as I know, you have only two options. The first one is JTAG [http://www.xda-developers.com/jtag/] but I don't think the boards have been documented yet for XDA II. The other option is to bring it back to where you bought it from. Tell them there's something wrong with it and play dumb. If you're lucky they might replace it for you, if they assume that you are still within warranty.
[MDA II, XDA II, 2060 ROM Development] Victor:
Yes, there is a way to upgrade/downgrade the Bootloader. I just don't know how.

The bootloader is locked, that is the problem you have (except for those who cannot access the bootloader).

If you know the right syntax and use the password to the bootloader (it is BOOTLOADER), you can load the proper ROM back using the "LNB" command. However, they have changed the syntax since ITSME's doc on the subject, or he mis-documented the syntax to the bootloader. Or at least his syntax was wrong with 1.06 version.

I got mine fixed, but I have means available that 99.9% of the people out there do not have. If I knew more, I would tell you about the percise syntax in the bootloader -- but alas, I am not a developer.
[MDA II, XDA II, 2060 ROM Development] ID64:
Thanks for the reply, Victor. When you talking about commands for bootloder what connection to PC you are talking about? Serial or jtag?
[MDA II, XDA II, 2060 ROM Development] Victor:
I am referring to the device in the cradle, in bootloader mode. The screen in this mode should read "USB" on top and "V.1.06" (or whatever version) on the bottom. Very hard to read, as there is no backlight.

Anyhow, just for fun.... why don't you try the following:

Uncheck the USB option in Active Sync Connection Settings

Cold boot your system (hard reset)

place the device in the cradle

run the communications software (found on this forum)

When asked which COM port to use, click on the down arrow and see if there is a USB port listed (should be top entry in list).

If so... click it. (if not, you are basically done)

After clicked, then hit return (enter) on the pc a few times.

Anything happen?
[MDA II, XDA II, 2060 ROM Development] ID64:
My bootlader is dead, so I can do the first thing.

To what communitcation software you are reffering to? My device wont even recognized by hyperterminal connected by a serial cable
[MDA II, XDA II, 2060 ROM Development] :
I am referring to the mtty tool found here

http://wiki.xda-developers.com/wiki/HimalayaBootloader

Try to connect through the USB Port to the device using this tool and see what happens .. but do it with Active Sync USB disabled and after a Hard Reset (without waiting too long)
[MDA II, XDA II, 2060 ROM Development] ID64:
Thanks, Victor. But nothing happenes, I even used serial cable and nada...

It's time to send my imate for service. But where? Carrier Devices tech support is abit mmm.... slow.
[MDA II, XDA II, 2060 ROM Development] ID64:
Well, my iMATE is on it's way to Dubai service centre. I have to tell you, that I am very happy with imate tech support. Response wast fast and I got RMA in one day. Wonder, how long it will take to get it back...
[MDA II, XDA II, 2060 ROM Development] fedup:
I had the same problem several time

I had the same problem several time and the only way trying to solving it it is putting the battery out. It is really deceiving that a device like this simply goes stuck for unknown reason, you cannot rely on it. I've lost several times all data. See "unknonw sim status causes several serious crashes" under "Using it" section
[MDA II, XDA II, 2060 ROM Development] ID64:
Actually, I was very happy with the device in genreal before this unfortunate upgrade. It was very reliable and stable, as well as my first iMATE I've had 4 monhts ago.
[General Questions and Answers] jaybrohn:
I want to theme my AOSP Jelly Bean 4.2 contacts app to look like the attached image. I want to change the blue banner and blue text to the grey color (#222222).

I have tried creating my own tmobile engine theme but always run into APK compile errors. I have used APK Multitool to decompile Annex's CM10.1 Theme Template apk, then immediately tried to recompile (without editing anything yet) and get the included screenshot error.

I've also thought about replacing the images in Contacts.apk file with my modified ones but that still will not solve the font color issue. Plus not sure if it will even work?

Any help to my compile error?

Not expecting this by any means, but if anyone has alot of theming knowledge or is a themer, I wouldn't assume it would take long to make those slight changes if someone wouldn't mind. But I'm not hoping to be able to do it all myself if I can figure out why I can not compile apks.
[Nexus 7 Q&A, Help & Troubleshooting] Ninja_Fox:
So, just yesterday, I purchased my new Nexus 7 from a Gamestop. Brought it home, started loading all my apps, things went smoothly, everything was great, more importantly, my WiFi signal was strong, even on the second floor of the house. Fast forward to today, I see I can update to Android 4.2.2, so i go ahead an load it up, it updates quick and easy. However I am noticing that the signal strength is abysmal. I can barely connect, even from right in front of where the router is located. However, any other devices are connecting just fine, such as my HTC One S running Android 4.0.4

I've searched around, but I haven't seen any fix for it. I've turned NFC off but that seems to have no effect. My sister has a Nexus 7 Android 4.2.2 and hasn't complained about this issues, so I assume not every tablet is affected

SO my question is:

What is my best course of action?

Do I factory reset it, reload all my apps, start over, and just not update to android 4.2.2?

Return it to GameStop, replace it with another unit, and hope it doesn't have the same problem?

Or do you have another suggestion?

Any help would be much appreciated! Thanks
[Nexus 7 Q&A, Help & Troubleshooting] bftb0:
Exchange it for a new replacement after doing a factory reset.

(You might want to first check signal strength side-by-side with the other N7 to verify it's not just a reception dead spot issue in your home)

First, the stock upgrade should not cause any problem.

Second, if something were to go wrong with the software upgrade in a way that affected WiFi, the most likely trouble would be complete failure (or perhaps intermittent signals) - not a signal strength change.

It sounds like an "infant mortality" issue - a hardware failure that occurs shortly after you put hardware in service. It could be something stupid like a loose antenna connector, but you don't want to invalidate the warranty trying to diagnose the trouble in case the trouble is elsewhere (same thing goes for unlocking the boot loader in order to re-flash stock). If it is a new device, use your warranty privileges to let somebody else figure out what the problem is.

good luck

PS it is apparent that you might be a little new to android - a "factory reset" does not really return the device to as it was when you first pulled it out of the box. It probably should have been called "Erase all user data and settings changes". When you do the factory reset, it will still be on the *new* OS - 4.2.2 - not whatever was on it to begin with. (For pure-stock, non-rooted devices, upgrades are not reversible using a "factory reset" procedure)
[Sony Xperia P, U, Sola, Go] werty100:
Here I posted a EXCEL with the bugs of JB it you find another ones said to my and I modificate it.

https://docs.google.com/spreadsheet/ccc?key=0AiPIXbJ_ZVFMdDFsZHpvT1ZCRks1UTFRLU1rMEZ1Vnc&usp=sharing

Please report the bugs
[Sony Xperia P, U, Sola, Go] Elwino2.3:
No need make a new thread like this on dev section
[Sony Xperia P, U, Sola, Go] werty100:
But they were talikgn about this EXCEL and here all people have control of bugs
[Optimus One, P500, V Q&A, Help & Troubleshooting] Shraven:
I just installed CyanogenMod 10/ Jelly Bean 4.1 on my LG Optimus One P500.

Everything seems to be working except the incoming calls. Incoming calls are getting listed in call log but i don't get any notification of it when i get the call. Outgoing calls are working fine and Messaging is also working fine.

i am confused if this is related to baseband thing (old / new). If someone could advise on what could be the issue and how to rectify this problem, it would be great.

Thanks in advance!!
[Optimus One, P500, V Q&A, Help & Troubleshooting] pmvyas:
Since you are getting network, and can receive calls, baseband is not the problem. It could be a bad flash or maybe not enough space (more likely) in / system. Trim the rom more and reflash. Use shinobisoft's tool to trim the rom.

Sent from my LG-P500