yashsingh1/xdaforums huggingface dataset:
[Xperia Z1 Q&A, Help & Troubleshooting] gaboh24:
Always press the red button, i call it emergency button or redboot, whatever...when it comes to that matter.haha! B1nny is right maybe it's about the firmware...firmware mulfunction sometimes..

sent from future!
[Xperia Z1 Q&A, Help & Troubleshooting] gregbradley:
Volume up and power does the same thing without the need for a paperclip to be on hand
[Xperia Z1 Q&A, Help & Troubleshooting] bogdan wst:
I know Sony's international policy states that they could replace your phone under warranty with a refurbished one or that they could use second hand materials to repair your phone, but in my country that kind of policy is forbidden. The law in my country says that all the repairs must be done using new materials or the device must be replaced with a brand new one.

p.s. - also, the legal warranty term in my country is 2 years, though Sony's policy states 1 year warranty.
[Xperia Z1 Q&A, Help & Troubleshooting] Haleem98:
Thanks for the advice. And thanks to everyone else too. 4.3 should bre released this month, if everything goes well, for the Z, Z ULTRA and Z1. Not sure about other devices, however in January we should see the release of KitKat, which I'm looking forward to seeing.#

PS. With the Red Button, I pressed it but nothing happened. I probably didn't push it all the way, or didn't hold it down long enough. I just pressed it once, and then left it.

That's good to know! Here, I'm not sure what materials they use to fix the phone, however I do know for sure they don't give you a brand new phone. :( That sucks. Where you from btw?
[Xperia Z1 Q&A, Help & Troubleshooting] gregbradley:
What makes you say January for kit kat, Sony have said no such thing, just that kit kat had been promised with no eta
[Xperia Z1 Q&A, Help & Troubleshooting] drsoran2:
Yeah, it wouldn't make much sense at all to release kitkat in January and 4.3 in December. It's just 4 weeks in between and if everybody knew that 4.4 is coming so soon, hardly anyone would go through the hassle of updating and then again. At least I wouldn't and wait until 4.4.

Therefore, Sony will either release 4.4. straight away or later and skip 4.3 or release 4.3 in December and 4.4. in March or something. I assume the latter will be the case.
[Xperia Z1 Q&A, Help & Troubleshooting] bogdan wst:
I live in Romania (Eastern Europe).
[Samsung Galaxy Nexus] atishey23:
I got this phone form my brother, but camera is not working, when I asked him how did it happened he said either upgrading from 4.0 to 4.1 or 4.1 to 4.2 camera always have error, it said 'unfortunately gallery has stopped '. After the 4.3 OTA the camera remains faulty. When I got this phone I thought to flash it with factory one of 4.3 using fast boot, I did... But no user, camera still not fixed. So I thought to return to 4.0 or 4.1, so I downloaded both from Google site.

1- I flashed 4.0 (imm76i) image, when the phone booted, it was running 4.2.2 :o :o....Idk how. so I fastbooted again and flashed 4.0.4 again when phone booted version was 4.2.2. (This time noticed that when the phone booted it showed splash screen 'Google', then boot animation 'nexus cross' then immediately phone switches off and boot up again with splash screen.)

2- I flashed 4.1, again same headache... It booted to 4.2.2.....same story....

3- I flashed 4.3...then it booted to 4.3 only. why is this happening.

Plz help me to downgrade the phone.

_______________________________________________

-----------------------------------------------------------------------------

Different issue than above- Right now I'm running slim rom build 2.2.

And yeah one more thing, on slim rom I get all calls normal, and when I flashed PAC or Carbon or crDroid rom...I get no calls. Can't place any calls and can't pick any calls. Always 'com.android.phone stopped'...

sent from a phone running on SLIM ROM
[Samsung Galaxy Nexus] dwoods1983:
Re: I need some help to fix my Galaxy Nexus

Have you been clean or dirty flashing?? It sounds like you need to completely wipe your phone (factory restore) and start over from scratch. I'd download the latest SlimBean 4.3 build 2.2 Official (based on Android 4.3.1) and the associated GAPPS (AIO). Boot into recovery, wipe data, cache, dalvik cache, and then flash SlimBean. You can go to the Slimroms website to download these.

This is what i'm running and having no issues...very stable.

Let me know if this works.
[Samsung Galaxy Nexus] atishey23:
Yes I have clean flashed 4.0.4 & 4.1... Formatted sdcard too.Then also I get 4.2.2 when I flash 4.0 & 4.1

And I never said I have problems with slim rom. It works fine for me.This is a different thing not related to stock image issue. That I can make calls in slim rom but can't make any calls in PAC or Carbon or crDroid rom.

sent from a phone running on SLIM ROM
[Samsung Galaxy Nexus] atishey23:
#delete# wrong post
[General Questions and Answers] Anonymuszymus:
I dissambled my HTC Evo 3D because my display is not working correctly,the screen goes black randomly and if I press hard the left corner where is the home soft button the screen is working again.The trouble is with the conector between the motherboard and LCD diplay.I don't know how to reach this because my touchscreen is work perfectly and i don't want to remove it and melt the glue.is other way to reach it from the other side?.my question is how to fix it,I need a new display or I can change only the conector?

the contact problem is where the conector connects to the diplay :D
[General Questions and Answers] z0rin:
http://www.youtube.com/watch?v=o56O0_xIv6c try to open it up and clean the connector and put it back
[8125, K-JAM, P4300, MDA Vario General] DICE02:
HI there,

I have installed TOM TOM 5.1 on my XDA Mini S by copying the cab files to the SD card theninstalled it to the phone memory, next i created the voice folder and put the voice i chose in. After this i copy the Folder of all the GB maps onto my SD card.

When i they open the TOM TOM software it just freezes! if i start tom tom up with out the sd card it loads straight away but i just get my no maps message! Does any1 know why it is freezing?

Thanks in advance.
[8125, K-JAM, P4300, MDA Vario General] woggle eye:
Hi,

I had the same problem what i had to do is using the built in file explorer goto My Device/My documents/

and make a folder named TomTom once made put a image file in there any type .gif .jpg anything.

tomtom should then work if you manage to get it working let me know as im having real trouble seeing my leadtek gps.

Cheers

Dean
[Nexus 7 Q&A, Help & Troubleshooting] pmgreen:
After flashing a number of ROMs over the past year and a half or so, storage has been used up though the values don't add up to 16GB. Think that there are partitions consuming storage. Is there a way to safely clean this up?

Noob here trying to understand and appreciate your help
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] hammer007:
I am currently using a another custom rom on S4 SGH-I337M.

I would like to install the Slim Bean 2 stable rom on to it.

I am very new the installing roms etc,. Just rooted and installed CWM on my phone last week.

My question is do I doing the following procedure to install

5.Now, perform data wiping task. To do so, select wipe data/factory reset, then select Yes on next screen to confirm your action. Wait few minutes till the data wipe is complete. Now come back to CWM recovery main menu. Select wipe cache partition and after wiping process done, select Wipe Dalvik Cache under advance option to perform Dalvik cache wiping.

Or follow the guide on Slim Bean sire:-

SlimBean 4.3 installation instructions

After there is a some confusion about how to install 4.3, here is a list of what's absolutely necessary

■full wipe (means: wipe data / factory reset and format /system)

■install Slim 4.3 ROM

■install Slim 4.3 gapps

■Reboot

What is the difference between the two guides.

As I mentione I have been doing quite a bit of reading and I was able to following the instruction when i first rooted to install custom Rom my phone. But is a little confusing with so much out there to read.

Thanks in advance for any help and suggestions.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] zee24:
Okay dude I was a noob too just a few weeks ago and I was staying over the little things too. Basically the only things you need to wipe are cache and dalvik cache and format/data but beware you should always have a backup of your current Rom because wiping data will make your phone unable to boot incase the zip file you downloaded doesn't install. In that case you can simply restore your rom download anther and try again so yeah
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] bcflyfisher:
There's no real difference between those 2 guides.

Slim ROMs

always recommend manually formatting system (as well as wiping cache / dalvik / data) but in theory it shouldn't be necessary. As you flash a ROM if you watch all the text on your screen you'll see that it formats the system itself. When you do a data wipe / factory reset you'll notice that it also wipes the cache at the same time. There's no harm doing it twice and I usually end up doing more than necessary.

As the previous poster said, ALWAYS make a backup before you do anything serious. My backups consist of:

- nandroid backup (with CWM or TWRP)

- back up all user apps and data (never system apps/data) with Titanium Backup Pro (I actually do these 3x/wk on a schedule)

- backup Calls and Messages to xml with TiBu Pro

Whenever I change from

one custom ROM to another

(say, Cyanogenmod to Slim) or one Android version to another (4.3 to 4.4) I do all of the following...

- wipe data / factory reset

- wipe cache

- wipe dalvik

- mount system

- format system

- flash ROM

- flash GAPPS

- with Kit Kat (Android 4.4) I've also been flashing SuperSU1.69.zip since some of the early Kit Kat ROMs were breaking Superuser.

- reboot

- follow the basic setup procedures to get your main Google account going

- open Play Store and get TiBu and Pro Key again

- open TiBu and do a batch action: "restore missing apps with data", then restore calls and messages from xml

- go into settings and tweak away......

When I update to a

new version of my current ROM

(like a new nightly or weekly or new stable version) I do the following...

- wipe cache

- wipe dalvik

- flash ROM

- flash GAPPs

- reboot

This is a "dirty flash" and can cause problems so do it at your own risk. Worst case scenario is that you might have to restore your backup or do a proper full wipe and try again...

---------- Post added 12th December 2013 at 12:04 AM ---------- Previous post was 11th December 2013 at 11:56 PM ----------

I should also mention, if you've already taken a stock phone and followed instructions to root and get a ROM going then what you're trying to do now is even easier. As long as you have CWM and make a backup you don't need to worry. Just make sure you always download the

correct version

of the ROM for your phone as well as the correct GAPPS package for the Android version you're flashing.
[Xperia Z1 Q&A, Help & Troubleshooting] gaboh24:
Guys need your help about this matter, I just bought my xperia z1 a week ago and i already rooted it... So my question is can i still back up my TA? I did not tamper my bootloader..how will i know if my bootloader is unlocked?

My process in rooting my xperia z1 is:

1st I downgrade my xperia z1 in 14.1.G.1.534 firmware and rooted it using vroot then upgrade it to the latest firmware which is 14.1.G.2.257... BTW I uninstall the vroot superuser because it's in chinese language and I can't understand it, but I replaced it Superuser in playstore and it works fine!...Thanks~

from Philippines :D
[Xperia Z1 Q&A, Help & Troubleshooting] chewdaniel:
unless u visited the bootloader unlock website and requested for a key which involved keying in your imei number and then using fastboot to unlock bootloader, it's fine...

u can verify by checking if bravie engine works... or dial *#*#7378423#*#* and going to service info > config > rooting status
[Xperia Z1 Q&A, Help & Troubleshooting] gaboh24:
It says bootloader unlocked allowed: yes.. Does it mean my xperia z1 bootloader is already unlocked? But i did not attempt to unlock my bootloader...

sent from future!
[Xperia Z1 Q&A, Help & Troubleshooting] gregbradley:
No, it means you are allowed to unlock it, but you have not done it yet otherwise it would say

bootloader unlocked: yes
[Xperia Z1 Q&A, Help & Troubleshooting] gaboh24:
Hooooo! Great answer.. I thought i acidentally unlocked my bootloader, so it means i can backup my TA.. I can sleep now peacefully!

sent from future!
[Xperia Z1 Q&A, Help & Troubleshooting] gregbradley:
trust me, you cannot accidentally unlock it... ;)
[Xperia Z1 Q&A, Help & Troubleshooting] gaboh24:
Hahaha chewdaniel says to look at sevices menu if it's unlocked and i saw the word "yes" i thought i accidentally unlock it when performing to root it..i feel nervous when i saw it haha!

sent from future!
[Xperia Z1 Q&A, Help & Troubleshooting] chewdaniel:
1. visit bootloader unlock website

2. key in your imei number

3. receive an email with unlock code

4. FINDING & INSTALLING FASTBOOT DRIVERS, while phone is in Fastboot state

5. entering bootloader unlock command with a very long and complicated unlock code

so yea... like Greg said... there's no way u can "accidentally unlock" it :p
[Xperia Play Q&A, Help & Troubleshooting] ChunkFlip:
Hello,

I'm trying to compile a 3.4 kernel for Xperia Play(zeus) and i have a problem with the compiling, i managed to compile with clean sources,but they have a bug (not working touchscreen) . I tried to mix some of the code from DoomLord's 3.4 kernel ( not finished yet, but in git it says that the touchscreen is fixed) with mike's sources (my base sources ).

Here is what i get in terminal:

scripts/kconfig/conf --silentoldconfig Kconfig
GEN /home/filip/android/system/out/target/product/zeus/obj/KERNEL_OBJ/Makefile
CHK include/linux/version.h
Using /home/filip/android/system/kernel/semc/msm7x30 as source for kernel
CHK include/generated/utsrelease.h
make[3]: `include/generated/mach-types.h' is up to date.
CALL /home/filip/android/system/kernel/semc/msm7x30/scripts/checksyscalls.sh
CHK include/generated/compile.h
GZIP kernel/config_data.gz
CHK kernel/config_data.h
UPD kernel/config_data.h
CC kernel/configs.o
CC drivers/input/touchscreen/cy8ctma300_touch.o
LD kernel/built-in.o
/home/filip/android/system/kernel/semc/msm7x30/drivers/input/touchscreen/cy8ctma300_touch.c:185:28: error: expected ')' before 'int'
/home/filip/android/system/kernel/semc/msm7x30/drivers/input/touchscreen/cy8ctma300_touch.c:186:32: error: expected ')' before string constant
/home/filip/android/system/kernel/semc/msm7x30/drivers/input/touchscreen/cy8ctma300_touch.c: In function 'perform_reset':
/home/filip/android/system/kernel/semc/msm7x30/drivers/input/touchscreen/cy8ctma300_touch.c:488:2: error: implicit declaration of function 'gpio_set_value' [-Werror=implicit-function-declaration]
/home/filip/android/system/kernel/semc/msm7x30/drivers/input/touchscreen/cy8ctma300_touch.c:492:2: error: implicit declaration of function 'gpio_get_value' [-Werror=implicit-function-declaration]
/home/filip/android/system/kernel/semc/msm7x30/drivers/input/touchscreen/cy8ctma300_touch.c: At top level:
/home/filip/android/system/kernel/semc/msm7x30/drivers/input/touchscreen/cy8ctma300_touch.c:1104:13: error: 'THIS_MODULE' undeclared here (not in a function)
/home/filip/android/system/kernel/semc/msm7x30/drivers/input/touchscreen/cy8ctma300_touch.c:1106:2: error: unknown field 'ioctl' specified in initializer
/home/filip/android/system/kernel/semc/msm7x30/drivers/input/touchscreen/cy8ctma300_touch.c:1106:2: warning: initialization from incompatible pointer type [enabled by default]
error, forbidden warning: cy8ctma300_touch.c:1106
make[5]: *** [drivers/input/touchscreen/cy8ctma300_touch.o] Error 1
make[4]: *** [drivers/input/touchscreen] Error 2
make[3]: *** [drivers/input] Error 2
make[2]: *** [drivers] Error 2
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [sub-make] Error 2
make[1]: Leaving directory `/home/filip/android/system/kernel/semc/msm7x30'
make: *** [TARGET_KERNEL_BINARIES] Error 2

Please help me.

Or if you want , you could try to make a kernel with working touchscreen for zeus and i will test it,here is the link for the sources : https://github.com/LegacyXperia also from the sources i tried to mix : https://github.com/DooMLoRD/CAF_msm7x30-3.4.x;
[Xperia Play Q&A, Help & Troubleshooting] saqibkhan:
I was planning to ask Devs here to help us for Play Touchscreen problem.. until I saw your post trying to find a fix for touchscreen problems.. don't worry. we might get help soon.
[Xperia Play Q&A, Help & Troubleshooting] ChunkFlip:
Actully I managed to compile but it didn't work. I hope someone will help us get the touchscreen driver working.
[Xperia Play Q&A, Help & Troubleshooting] saqibkhan:
hi.. can you please guide me in building kernel.. I am a little confused.. I have installed Ubuntu for the same reason.. I want to help and experiment so that maybe we could find a way out. any guide you could refer me to.. I am a little noobish (my first attempt) so if you could please help me to build a cm 10.1 kernel.. (I also want to take half from doom lords sources and half from mikes:) .. but how.. am clueless after reading almost 10 guides.
[Xperia Play Q&A, Help & Troubleshooting] pedyvirus:
well changes that doom did on touchscreen files wont solve the touchscreen issue

doomlord updated the driver in his source

nick did this in his first zimage but touchscreen was not working :(
[Xperia Play Q&A, Help & Troubleshooting] saqibkhan:
hi.. I found something really useful here.. can you try this..

https://groups.google.com/forum/#!topic/android-porting/Rmvqi8fPYCg

and maybe this http://xdaforums.com/showthread.php?t=1328515

and this too.. we all should go through these links.. gives us a little extra knowledge. http://stackoverflow.com/questions/7425303/replacing-touchscreen-driver-in-android-kernel
[Xperia Play Q&A, Help & Troubleshooting] pedyvirus:
this thread was very useful

http://xdaforums.com/showthread.php?t=1328515
[Xperia Play Q&A, Help & Troubleshooting] saqibkhan:
nick corrected your error in the main thread.. did you correct it and compile ?? waiting for your or nick's test kernel.. plz make sure to make a boot.img .. as I don't even know how to convert zlimage to boot.img.. if you are compiling that is..

FYI : its night time again at my place.. looks like its time to start researching again for new solutions.. haha.. I do this everynight.
[Xperia Play Q&A, Help & Troubleshooting] pedyvirus:
i tryed to compile again but gived me that ***** error again

i even tried compiling with another toolchain instaed of doomlord ones but gived me another error :(

---------- Post added at 08:44 AM ---------- Previous post was at 08:31 AM ----------

i was checking the file that you attached (doomlord one)

i did a diffcheck and i can say it wont solve the problem

differences were only related to some lines that doomlord one were all outdated

in the header 3.4 kernel needed things weren't included

we still had old int err = 0; instead of long err = 0; and ....

and your error was probably caused by one of that things

---------- Post added at 08:53 AM ---------- Previous post was at 08:44 AM ----------

please try what is explained in this thread

im 50% sure it will work

http://xdaforums.com/showthread.php?t=1328515
[Xperia Play Q&A, Help & Troubleshooting] saqibkhan:
can you please make a Noob Guide about compiling a 3.x Kernel for Xperia Play. so that noobs like me can experiment themselves.. and more chances of getting it working.. every person tries something different.. maybe we end up their.
[Xperia Play Q&A, Help & Troubleshooting] ChunkFlip:
ok , i reinstalled ubuntu (had a problem with the hdd :( ) , now i'm syncing the repo again to try the tj_style fix, thanks for the tip pedyvirus.

[MENTION=4862673]saqibkhan[/MENTION]

How i did,I don't know if this is the right way but.. :

1.Install Windows 8(if not already installed) but leave some free space on the hdd , don't partition it completly.

2.Install Ubuntu 13.10 with a partition ext 4 and mount point "/" and a swap partition . ps: install it on the ext 4 partition.

3.Follow this guide : http://wiki.cyanogenmod.org/w/Build_for_zeus until "Initialize the CyanogenMod source repository"

4.Follow this guide but change smultron with zeus in the code lines http://xdaforums.com/showthread.php?t=2164696

EDIT 1:@pedyvirus can you provide me the files that you have changed, but doesn't compile , i want to try it too . I saw the tj_style post but i couldn't find these lines in our code maybe i'm too noob or too blind.
[Xperia Play Q&A, Help & Troubleshooting] ChunkFlip:
--- delete post please
[Xperia Play Q&A, Help & Troubleshooting] saqibkhan:
for 1. i always had windows 8. on a 350gb HDD

for 2. i installed with Partition Boot 250mb.. Root partition 30gb.. Home partition 60GB .. Swap Partition 8GB.. Bootloader installed in Boot Partition.. this way.. windows loads always.. unless i select Ubuntu before 10 SEconds.. (i get the option for both)

for 3. i will start following and let u knw of any help needed. (until means not including that step right.. or until completion of Initialise the CYMOD source repo)

for 4. same like 3.
[Xperia Play Q&A, Help & Troubleshooting] pedyvirus:
our driver is not completely the same :(

im too noob about this too
[Xperia Play Q&A, Help & Troubleshooting] ChunkFlip:
Not including. It says that in mike's guide too
[Xperia Play Q&A, Help & Troubleshooting] saqibkhan:
if i want to build only the kernel.. do i have to follow all the steps.. cuz the steps are not clearly mentioned.. like what to follow only for kernel.. i followed till repo sync.. but the next three steps take me towards building the ROM.. but i want to build only the kernel. ?? i am talking about Mike's Guide.
[Xperia Play Q&A, Help & Troubleshooting] ChunkFlip:
See down the post , he explained already.
[Galaxy Note 3 General] cellrama:
It's been awhile since I was on the forum but thought I would create a quick post for those who wish to enable LTE on the Samsung Galaxy Note 3 (model: SM-N900W8) where LTE has been crippled. I have compiled the following steps and this should get you up and running without having to ROOT your device, install RECOVERY software or FLASH a new modem.

1) Obtain the device IMEI by pressing *#06# on your dial pad and record this number to reference later.

2) Type in *#272*[IMEI Number]# Where [IMEI Number] is the number you recorded in the step above.

3) You will be prompted with a 3 letter "Regional Settings" menu. Cross reference the 3 letter code with the carrier list at the following link: http://www.samsungis.com/Firmwares/SM-N900W8.html. You do so by hovering over the 3 letter code under the "Region" column. If the SIM you wish to use is from one of these carriers and the carrier supports LTE, we're on our way! The above steps are confirmation, do not modify anything yet!

4) Unlock your device using a preferred unlocking method. Myself, I use http://www.cellunlocker.net which charges $32.99 US for a Samsung Galaxy Note 3 unlock code. It's a reliable site with quick turn-around.

5) Once you receive your unlock code, put in the SIM from the carrier you wish to use and enter the unlock code when prompted.

6) Once unlocked, it may reboot and when at the main menu, follow step 2 and 3 above but this time, select your 3 letter carrier code for the carrier SIM you just inserted then click on OK or INSTALL.

The device will go through a boot up sequence but once complete, you will have LTE enabled. If you do not see this, go into your network settings and you should have the option to select GSM/WCDMA/LTE (auto connect).

Hope this helps those of you wishing to enable the crippled LTE band but do not wish to delve into all the technical jargon related to ROOTING, RECOVERY and FLASHING.
[Galaxy Note 3 General] Dylan66:
Thanks for this.
[Galaxy Note 3 General] chnoor:
Thanks

Thank you for sharing this wonderful trick. I was looking for something like this for a long time.