yashsingh1/xdaforums huggingface dataset:
[XDA Assist] priyankmehta:
Hey guys my device is xperia sola mt27i. Its stuck in bootloop/bricked and i really need help. I had rooted the device and had intentions to install cyanogen mod. So first i unlocked the bootloader. Then i flashed the boot.img file using flashtool. after that i rebooted the device into sytem using flashtool again but the screen showed the sony logo and didnt go beyond that. After that i get a blank screen and nothing else. it does not even connect in fastboot mode.

it just remains stuck on the blank screen. i did not have clockworkmod recovery/ rom manager installed on my phone at the time of flashing which i am considering as the reason for the problem. Please help me. i cant figure this out. :(
[XDA Assist] It_ler:
Please check this thread: Xperia Sola [MT27i] Official Thread ROOT, ROMS, MODS, HELP & Guides [All In One].

Maybe this can already help.

If not, please ask in the [FAQs][Q/A][Xperia P,U,Sola & Go]Help Thread, Newbies post here first thread.
[Galaxy S3 Neo Q&A, Help & Troubleshooting] moro89:
Hello!

Today I had a really weird situation with my Samsung Galaxy S3 Neo !

I put the phone on the charger as usual, then went to sleep.... Only to wake up on the boot intro sound of my device several times!

The only obvious reason for this situation is probably just putting my phone on the charger!

I tried to reboot several times, removed the battery and waited for a while, but in vain! Sometimes I had the logo screen, very slow one with a stuttering audio, sometimes not.

I tried to flash stock Kitkat firmware 4.4.4 (the same Hong Kong one I was using already)... No change!

I couldn't boot properly into recovery till I decided to flash TWRP and do a full erase of just about everything that could be erased!

The result?? You guessed it... NO CHANGE! Still the same bootloop, while sometimes I could see the launcher before the reboot!

I decided to try to flash the previous firmware that was before the update (4.3 Jellybean, UAE) and send it to the service center, and I just removed everything from the phone: The battery, and all the cards were removed and put aside! However, I found that this will trigger the Knox Warranty flag to 0x1, definitely not the best shape for visiting the service center! :\

After all, I decided to give it one last try to boot before I send it to be serviced just the way it became. To my surprise, I managed to boot successfully and restore almost everything. The only noticeable loss was the Samsung "Over The Horizon" soundtrack! (Got links for this one, please??)

However, all that flashing wasn't for free! I had a change of both firmware statuses to "Custom" after I had a once "Official" firmware tag! To my chances, I didn't trip the Knox Warranty Flag, and I had my device rooted using CF-AutoRoot with Odin!

A few questions here:

1. What the heck is going on?! What caused all of this from the beginning??!! The phone was rooted and working great before that! I even managed to resolve the battery drain and the camera issues for good! (I'll describe my method later ;) )

2. After all that play, how come I didn't trip the Knox flag?! Was it just... luck???!!!!

3. Can I change to the UAE firmware from the Hong Kong one without tripping the Knox flag???!!! I have little problems with the Hong Kong one, despite the fact that I had some crashes and minimal glitches before! As you all know, Android is a glitchy OS, but this one has much less glitches than before.

Thank you for your time. Hope to see your thoughts asap :)
[Galaxy S3 Neo Q&A, Help & Troubleshooting] bongski55:
Question 1: I read similar problem on samsung phone somewhere caused by defective or dirty microUSB connector. Perhaps your several flashing resulted on dislodging of the dirt from the connector thus your reboot problem was resolved.

Question 2: I also flashed 4.3 over kitkat from hongkong rom and the knox was not tripped. Perhaps only rom 4.2 and below will trip the knox?

Question 3. I have done flashing from Hongkong to UAE to Russia no problem with knox.

Good luck!
[Galaxy S3 Neo Q&A, Help & Troubleshooting] moro89:
Thanks a lot!

BTW, which one is better to use of the three firmwares you flashed already?? I have the I9300I with the 1.4 GHz Quadcore CPU and I know that some firmwares are made for the 1.2 GHz edition...
[Galaxy S3 Neo Q&A, Help & Troubleshooting] bongski55:
You may have read my experiences with kitkat on a separate post? I am back to 4.3 now.

Anyway the most stable among the 3 is the latest Hongkong kitkat. Some users here suggest Kazak rom but I has heating problems with that...
[Motorola Droid 4] QA Bot:
Q&A for [ROM][4.4.4] ParanoidAndroid

Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.

Before posting, please use the forum search and read through the discussion thread for [ROM][4.4.4] ParanoidAndroid. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.

Thanks for understanding and for helping to keep XDA neat and tidy! :)
[Motorola Droid 4] aczlan:
No sound in call on pa_maserati-4.6-BETA5-20141022

I just installed Paranoid Android 4.6-BETA5-20141022 (from aospal.com/roms/maserati/ on my Droid 4 via Safe Strap.

I wiped the cache and dalvik partitions with Safe Strap before installing, the install went well and almost everything seems to work except that I have no sound in a phone call unless I turn on the speaker phone or use bluetooth.

It doesn't seem to matter if I call through Verizon or through Google Voice and yes, I have tried turning the volume up while in the call.

Any suggestions on where I should look first?

Thanks

Aaron Z
[Motorola Droid 4] sd_shadow:
Just install pa_maserati-4.6-BETA5-20141022.zip with pa_gapps-modular-nano-4.4.4-20141025-signed.zip

on stock rom slot, volume is working fine

did you verify md5 checksums with a md5 utility? https://sites.google.com/site/sdshadowscollection/home/hash-checksums

---------- Post added at 05:29 PM ---------- Previous post was at 05:26 PM ----------

also should be wiping data/ factory reset unless you are installing over a older version of the same rom.

then if you have problems, should factory reset, and reinstall rom and gapps
[Motorola Droid 4] aczlan:
Ah, it looks like I used the pa_gapps-stock-4.4.4-20141110-signed gapps.

The MD5 checksums match with the ones on the download sites.

I will try re-installing with the newer gapps, will it cause problems to use a slot other than the stock slot?

Any problems with using pa_gapps-modular-nano-4.4.4-20141103-signed.zip?

I did a factory reset (then a factory reinstall using RSD Lite), rooted (with razr_blade), installed safestrap and then installed PA.

Aaron Z
[Motorola Droid 4] sd_shadow:
ROM slot should not matter, but never know, stock slot more likely to cause problems

Older gapps should be fine

Did you try rebooting to stock rom and checking if volume worked still?
[Motorola Droid 4] aczlan:
Stock rom has working sound.

I downloaded pa_gapps-modular-pico-4.4.4-20141110-signed.zip, the MD5 checksum matched.

I did a "Factory Reset" on slot 1, then loaded pa_maserati-4.6-BETA5-20141022.zip and pa_gapps-modular-pico-4.4.4-20141110-signed.zip

It loaded and in call volume worked, but it popped up an alert every 30 seconds saying that Google keyboard has stopped. That seemed to have also disabled the physical keyboard.

I tried reloading that (same factory reset, etc as before) and got the same results.

I then downloaded pa_gapps-modular-nano-4.4.4-20141110-signed.zip, the MD5 checksum matched.

I did another factory reset on slot 1, then loaded pa_maserati-4.6-BETA5-20141022.zip and pa_gapps-modular-nano-4.4.4-20141110-signed.zip and so far so good. The keyboard works and so does volume in the calls.

Aaron Z
[Motorola Droid 4] sd_shadow:
Sometimes files just don't install correctly
[Motorola Droid 4] aczlan:
Yep. Apparently my phone doesnt like that Pico gapp file.

Aaron Z
[Xolo Q700, Q700i] QA Bot:
Q&A for || Android L/Lollipop ROM || XOLO Q700/Q700i ||

Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.

Before posting, please use the forum search and read through the discussion thread for || Android L/Lollipop ROM || XOLO Q700/Q700i ||. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.

Thanks for understanding and for helping to keep XDA neat and tidy! :)
[Xolo Q700, Q700i] sharoid:
good work Suraj Lulla

no network .....net problem plz fix it.....thanks in advance
[Xolo Q700, Q700i] srjlulla:
Trying

Trying my best.

Thanx for ur review
[Xolo Q700, Q700i] faiztipu:
plz fix camera and network, the rest of the rom is awsm....

nice work
[Xolo Q700, Q700i] srjlulla:
I think reliance works in it
[Xolo Q700, Q700i] verma_ayush:
Can i use this rom on Xolo Q500?? I am asking this because there is no custom rom available for xolo q500 and i have used both q700 and q500....they r almost same irrespective of the kernals etc. So should i try flashing this rom on my xolo q500?
[Xolo Q700, Q700i] shashu_rony:
Hi,

I flashed the Lollipop rom which was posted in ur thread..

Had 2 problems:

1. Mobile signal is very weak almost 0

2. Camera does not work - crashes upon opening

Rom is very good i liked this, just these 2 bug fixes is all it needs..

Can somebody pls offer solution to these bugs..?

Thank You.
[Xolo Q700, Q700i] Mehandi:
LOLLIPOP

Dear Respected Members

I used the Rom Problems

1. Week Network

2. Consume Heavy Battery

3. Can't identify the device properly (USED XOLO Q700i identify as LAVA IRIS458q

4. And many other problems too like Camera e.t.c

http://cdn4.xda-developers.com/images/icons/icon9.gif
[Xolo Q700, Q700i] imcheenu:
Interface

Could you Add Tamil Interface??
[One (M8) Q&A, Help & Troubleshooting] Critias:
Good evening guys, Im really new to Root etc andI've been trying this for a bit now and I just cant seem to find a solution for this. A few months ago I rooted my M8 and flashed the GPE on it, I tried to get back to stock and somehow managed (with TWRP) to get it back to Stock with the Firmware 3.28.401.7 but my problem is I cant turn on WIFI, the button is just gray and stay like this and I want to sell my phone so I want that to be fixed if possible. My M8 is S-ON. I read everywhere I could and it seems I forgot to flash the boot.img so I did that but nothing changed. Also when I try to boot into recovery now it just shows a warning sign with a "!" in the middle. If I'm missing any info just tell me and thanks for your help!
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
You need to go back to an older stock ROM that matches you firmware (hboot, radio, etc.).

You somehow also reverted to stock recovery (red exclamation point). Just install TWRP again.
[One (M8) Q&A, Help & Troubleshooting] opticus44:
Just find an old backup which matches your device, where are you from?
[One (M8) Q&A, Help & Troubleshooting] Critias:
Im from austria I have the CID HTC__102

I'll try that out when Im back at home :)
[Nexus 5 Q&A, Help & Troubleshooting] duarian:
I wasn't sure where to ask this, and since all of my devices are Android I figured i'd post it here.

I was given the Poweradd 6 port charger as a gift. I am a little hesitant to use it for my devices simply because the Volt/Amperage is off. Will this harm my devices if I use it? I tried it and I had to plug my wireless charger into the very top port for it to get the required power (red light).

Devices and charger used:

Nexus 5: Wireless Charger (2.5A / 125v, or 1.25v, font is small)

Nexus 10: Pogo charger (2.5A / 125v, or 1.25v, again font is small)

Samsung Galaxy S3 on my N5 Stock charger: (1.2A, 5V)

Not sure which ports I should even use for what, but this would free up a lot of plugs on my surge protector..

Thank you!

The ports are as follows:

USB1: 5V/2.4A

USB2: 5V/2.4A

USB3: 5V/2.1A

USB4: 5V/2.1A

USB5: 5V/1A

USB6: 5V/1A

Sorry if this isn't the forum for this, not sure where else to turn to for my N5's charging needs.
[Nexus 5 Q&A, Help & Troubleshooting] danarama:
Devices have there limits to what they can draw. A charger will only feed what the device draws. Nexus 5 I *believe * draws 1.5A through USB maximum, but in short - it doesn't matter which port you use on an Amps basis.
[8125, K-JAM, P4300, MDA Vario General] grivad:
So, I've got this issue and I can't figure it out.

My Messaging app (default one, ie: MMS/Text/Email.. Pocket Outlook is it?) keeps opening up on its own, constantly.

I close it, and half a second later, it opens up again. I force close using InClose, and it opens up again. It's very annoying.

Anyone know what could cause this? Please help!

TIA!

-Gonzo
[8125, K-JAM, P4300, MDA Vario General] anothertmobilemda:
Did you configure a pop3 acct recently ?

have you done a soft reset yet ?
[8125, K-JAM, P4300, MDA Vario General] grivad:
POP3, no.. but I'll double check the settings to make sure one hasn't snuck in there somehow.

Soft reset, yes.. many times.. still keeps happening :(
[8125, K-JAM, P4300, MDA Vario General] tikkel:
Having the same problem. Is it a virus? Is there any solution yet?
[8125, K-JAM, P4300, MDA Vario General] ricardomacedo:
I have a similar problem. But in my device is not only with the Messaging app, all the programs keep opening like if someone was controlling the device very quickly and sometimes I can't get control of it. When I let the device in standby mode for a while the problem ends. I guess it's a virus, but I can't find anything in the internet to help me. I've tried to change the pressure thereshold of the device, but no success.

If someone has a solution for that, please letme know.

Bye,

Ricardo Macedo
[XDA Assist] XDA Visitor:
Sorry if this is a dumb question, I'm new to android (note 4). I was messing around with some lockscreens (go locker, kk locker, echo, my locker) I ended up uninstalling all of them and I still have a second lock screen on top of the default touchwiz one. I ran clean master to remove the junk files and it didn't work. Any ideas on how to remove it?
[XDA Assist] It_ler:
There are no dumb questions.

I would say, uninstall all lockscreen apps should do the job.

If not, you may have to flash a stock firmware (kernel/ROM) or do a factory reset.

If you have further questions, please ask in the Samsung Galaxy Note 4 > Galaxy Note 4 Q&A, Help & Troubleshooting > [NOOB FRIENDLY] Ask the question! thread.
[Wear OS Q&A, Help & Troubleshooting] Alexthekiller1993:
Hello everyone ,

I recently bought the LG G Watch and i think is pretty cool . But I am annoyed because everytime i move my hand the screen turns on for a few seconds !

The screen turns on about 40-50 times during workout , also when i move my hands while eating , even when i am driving which is a big distraction and the battery is draining fast because of that useless feauture . I know if i mute it , it will not turn on but i cannot get any notification which is the reason of LG G Watch existence .

How can i disable it ?
[Wear OS Q&A, Help & Troubleshooting] siraltus:
Just got the LG G Watch R and want to disable this as well. It annoys me to no end. I want the screen to only turn on when I tap it or press the side button.
[Wear OS Q&A, Help & Troubleshooting] MabeeDev:
This is not possible. The feature itself is built into Android Wear, and cannot be disabled.
[Wear OS Q&A, Help & Troubleshooting] siraltus:
Then someone needs to make a custom ROM that allows us to disable it. :)
[Wear OS Q&A, Help & Troubleshooting] imminentwill:
Found this link doing a similar search:

http://www.reddit.com/r/AndroidWear/comments/2h5gb1/howto_disable_tilt_to_wake_without_muting/

You need to be rooted though.
[Wear OS Q&A, Help & Troubleshooting] AstroDigital:
I thought Google was going to update Android Wear?

Be nice to disable this feature
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] systemglytch:
Hellos! I've successfully downloaded and installed Safestrap and tried to install Cyanogenmod 11 for jftlte but after I installed it and try to boot it up, the screen stays black. I am positive I'm using the right ROM for my device. How can I get it up and running?
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] jd1639:
You can't. You can only install touch wiz based roms. No cm.
[Nexus 7 (2013) Q&A] tungdil:
Root not working

Hello!

First of all :good: :good: :good: I am using your kernel more or less since I own the Nexus 7 (2013) in combination with Multirom and some custom ROMs, installed as secondary. It is working like a charm and I never saw any problems on "KK".

With "L" root is not (yet?) working for me. This might however been caused by the way of using it. I have two scenarios: 1.) "L" as secondary ROM and 2.) "L" as primary ROM. For both cases I used Tassadar's build. For the latter I copied the installed secondary ROM to the primary slot. With Tassadar's kernel I have root. When installing GlitchKernel root is gone. By flashing Tassadar's boot.img I regain root. As far as I can say right now this -- regaining root -- does not work for the secondary ROM.

To have it said: I also tried flashing GlitchKernel and Chainfire's SuperSU directly afterwards before rebooting with no effect. One thing I haven't tried is to NOT inject Multirom after flashing your kernel.

It would be great if you could help. If there is anything I could/should test, let me know!

Finally, my prayers are also with you!!!

Best Regards,

tungdil
[Nexus 7 (2013) Q&A] Tk-Glitch:
[MENTION=5098312]tungdil[/MENTION]

Hello tungdil,

I'll start by asking what revision of Glitch are you running ?

r300 didn't come with root support out of the box, and it is required to flash a root-enabled boot.img (the ramdisk in it to be exact) prior to flashing r300 to enable the rooting technique of your choice (SELinux Permissive (potentially with system R/W access) or just Chainfire's partial root "trick"). Lollipop's security enhancements are modifying how root works for us (users), so until some kind of standard takes place I did want to wait and see.

However, considering many users didn't find that easy (either to understand or to find what boot.img to get for what result), I did release r303. This new revision comes with various ramdisk patches you can enable through Aroma to get anything from Chainfire's partial root to full root with SELinux Permissive, system partition R/W access and PIE bypassing (it will obviously lower Lollipop security though).

I'm using this new revision on primary and secondary roms using MultiROM with no rooting issue.

If you're running r300, get the r303 update. If you're already on r303, what apps are you running that won't get root access ? You may want to use more patches to "open the can".

Have a nice day !
[Nexus 7 (2013) Q&A] tungdil:
Hello Tk-Glitch!

Thanks a lot for your feedback! My feeling is I am doing something wrong :confused: because you wrote you don't have problems using it with MultiROM. But let me answer your questions:

Actually I tried both r300 and r303 using the following sequence:

"install" with TWRP (or delete and inject if it is the secondary ROM) the boot.img which is packaged with Tassadar's lrx21p_flo.zip. Note: I do have root afterwards

Flash GlitchKernel, reconfigure everything in the Aroma installer. Usually I don't use permissive mode or PIE Patch but have tried it as well with no success

Reboot, which results in not having root.

For the primary ROM: Re-install the Tassadasr's boot.img; which results in having root again.

That means, I start with a situation where root is working (btw. Kernel: 3.4.0-g0356b90-00001-gd0e79e3 tassadar@nymeria #240)! Yesterday I have also updated the bootloader to 04.04 with no effect. Just right now I tried it again and after flashing Glitch-N7-r303.zip (leaving all options as is but selecting PIE patch and permissive mode) the Kernel is: 3.4.0-Glitch-N7-AOSP-r303 tk@ubuntu #1, dated 16.11.14 08:08:49 PST but I don't have root.

The following "apps" are not working AFWall+, MultiROM Manager, Reboot Menu Widget, and su itself if directly "called" from within Terminal Emulator. Just to have it said: ES File Explorer also won't work, but that's because it needs at least the PIE patch. The log of SuperSU tells, for example for AFWall+:

iptables v1.4.20: can't initialize iptables table ... : Permission denied

When I try launching su from the Terminal, SuperSU will ask to confirm root access even if I previously allowed root acces permanently. If I allow root nothing happens and the Terminal is "dead". The same applies for the other apps. I also tried this via an adb shell with the same effect, i.e. from the adb shell with root I'll see:

shell@flo:/ $ whoami
whoami: unknown uid 2000
1|shell@flo:/ $ su
root@flo:/ #

and without

shell@flo:/ $ whoami
whoami: unknown uid 2000
1|shell@flo:/ $ su

i.e. the shell will not return.

Anything else I could test or check?

Best regards,

tungdil
[Nexus 7 (2013) Q&A] tungdil:
Solved

Hello Tk-Glitch,

I "just" saw that Chainfire released an update to SuperSU (Beta 2.23) and ... that did it for both, primary and secondary ROM. I was on SuperSU Beta 2.19 before. My installation procedure for 2.23 was as follows:

Start with root NOT working for the primary ROM and working for the secondary ROM

For primary ROM use a TWRP queue for flashing GlitchKernel r303 and SuperSU Beta 2.23, and for the secondary ROM first flash GlitchKernel and then SuperSU

reboot and ... :) :cool: :good:

Notes:

currently not using the PIE patch when installing Glitch kernel, i.e. no root for ES File Explorer. All other apps I mentioned above do have root!

the same installation procedure did not work with SuperSU 2.19

Best regards!

tungdil
[Nexus 7 (2013) Q&A] Tk-Glitch:
[MENTION=5098312]tungdil[/MENTION]

Hi again tungdil,

It's nice you got it sorted, though it convinces me something must be wrong with your installation process. Latest SuperSU is able to mod the ramdisk to enable root support (pretty similar to what Glitch r303 is supposed to do), so yes it works, though the question is why didn't it work with r303 for you ?

It may very well be an error on my side (I'll verify that), though it worked for me and most it seems, as you're the only one to encounter the issue since r303 release, or at least to talk about it. I checked my secondary ROM to be sure, but I'm indeed running SuperSU 2.19 on it.

By the way, injecting multirom shouldn't be required with Glitch, and leaving it checked will only lead to multirom detecting it's not needed and skip the injection (so basically you don't have to worry about it).

If you're okay, let me ask a few questions :

- Do you have screen timeout disabled in TWRP ? And if you don't, are you able to hit the reboot button after Glitch install ?

- What ROM are you running ?

- Could you please install r303 and save the installation log for me ?

- Could you please copy the /fstab.flo content from a ROM you got Glitch installed to for me?

- Why to use "delete and inject" for secondary ROM instead of "classic" install ?

Thank you !