yashsingh1/xdaforums huggingface dataset:
[G3 Q&A, Help & Troubleshooting] jamesrfraser:
Hmmm.really im not crazy lollike i said before.it happened on my lg g2 when i flashed any g3 ported rom.and it happens so fast most dont notice it.my friend said i was crazy until she really watched her screen and confirmed i was right.im guessing it might have something to do in developer options.on some ported g3 roms to my old g2 that if you ticked hardware over ride option i would go into gallery to look at a pic and all my pics were distorted.i actually narrowed it down to that one developer option.so what im guessing is when i set up my g3 for the first time i have ticked an option somewhere and thats what is causing my problem.maybe some people dont use all the same options as me and thats why it isnt happening to everyone.just a thought
[G3 Q&A, Help & Troubleshooting] cpg1987:
Mins started doing the same thing a few days ago out of the blue and nothing seems to get it to stop. The phone is not hot or anything, but when i turn the brightness up the screen dims a tad. Pretty annoying, but at least I know I'm not the only one. I am still on version VS98510B with Verizon.
[G3 Q&A, Help & Troubleshooting] vdubjim:
anyone find a solution?

Is there an app that slows cpu a bit to make screen stay at least HALF bright? After playing a game 5 min mine dims to unusable.
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] JosePabon:
Hello community yesterday (september 30,2014) I Rooted my Galaxy S4 Mini GT-i9195L on Android 4.2.2 using:

-recovery-clockwork-6.0.5.0-serranoltexx.tar.md5

-S4Mini_RootKit_v2.zip

-UPDATE-SuperSU-v2.02.zip

-Odin_v3.09

I did every step to root just fine, using your guides, everything went fine it get rooted, I even make sure it was rooted using Root Checker app from PlayStore.

Then I Upgraded my phone from Android 4.2.2 to Android 4.4.2 using:

-cm-11-20140930-NIGHTLY-serranoltexx

-pa_gapps-stock-4.4.4-20140930-signed

Now in this OS (Android 4.4.2) everything works fine except for the original Settings app that come on the OS, I even downloaded apps from PlayStore and they work just fine and every other apps are working 100%.

As soon as I tap the Settings app it Stops working, it never opens, not even for a second. I even made a factory reset and unrooted and installed the factory OS and made all the root process again and upgraded to 4.4.2 again and the same problem is present with the Settings app. I'll be very happy if anyone can help me resolve this problem. :)
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] Razvan:
Its a known bug of that nightly. You must wait next release for fix.

> CyanogenMod 11 - GT-I9195 and GT-l9190 - Nightlies - Bug Reports & Discussion

Cheers
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] JosePabon:
OK! Thanks Man, I really appreciate your help! :)
[One (M7) Q&A, Help & Troubleshooting] MrLizm:
You can get to recovery from fastboot?
[One (M7) Q&A, Help & Troubleshooting] Deleted member 5444902:
Did you hold a bright light into the camera? Helps sometimes.
[One (M7) Q&A, Help & Troubleshooting] MrLizm:
I had thought the bright light should be shined into the light sensor on front top left, maybe the camera... Don't think so, however.
[General Questions and Answers] cleinadz:
Hello i'm new in here and i think this is an awesome forum :)

Anyway, i'm willing to root my phone but i just don't want to reach the point where my phone got Hard Brick or useless. So how long does rooted phone live? Would it only take a months? because i can read some topics in other forums that their phone got bricked. Why is that happening? Is that normal? And how to avoid soft brick or hard brick? I will not be downloading some Rooted Apps if i root my phone. I just want to use this Wifikill app, dsploit and etc. but i will not be flashing customized ROM or themes. So would it still "soft brick or hard brick" my phone?

Thanks !!!!
[General Questions and Answers] Khatarian:
Rooting isn't dangerous if you're careful

Hi there, I'm not sure what you mean by "how long does a rooted phone live", but I'll try to answer as best as I can.

Rooted phones 'live' as long as a non-rooted phone, the only risk of rooting a phone is the flashing part. For todays rooting methodes it's actually hard to hardbrick a phone, espescially when you just follow the steps provided by the rooting process.

Hardbricking a phone means that you messed up the flashing soo badly that there is no way to recover the phone. I actually tried on purpose to hardbrick an old SGS3 and even when I removed the USB cable while flashing the recovery, I was still able to revive the phone.

Softbricking however is much more common, but actually quite easy to revive from. All you need to un-brick the device includes having ADB/FastBoot on your PC or access to the recovery.

This way you can allways reflash the recovery or ROM if this gets corrupted.

You'll need a custom recovery to root your phone. You can brick your device if you pick the wrong recovery, but this is easy to check. Always match up the modelnumer of your phone with the one for the recovery.

After the rom has been installed, you'll need to flash the SuperSU zip to succesfully root your device and after that, you're all set.

So, bottomline is: as long as you make sure your phone is fully charged, and your PC won't randomly shutdown (that's why I always flash from a laptop). There is no way you can mess up.

For the lifetime of your phone: If you aren't planning on overclocking, you don't have to worry about shortening the lifetime of the device.

If you're going to root, always make a backup of your data, just in case something does go wrong!

For the apps you're mentioning: Just make sure you use those apps on your own network!
[General Questions and Answers] cleinadz:
Flashing

So you mean flashing is the most common reason that bricks your phone? What if i want to play games, listens to music, texting or calling, does it brick your phone(soft or hard?)? And is it possible for the unrooted phone to be brick bit by bit if you keep on flashing wrong recovery file? I hope you can answer all my questions :)
[General Questions and Answers] Khatarian:
No it's not possible to brick your phone by playing games, music ect. Flashing (Writing another recovery or updating your ROM) is the one and only way to brick your device.

If you flash the wrong recovery image to your device, it will be bricked. It 'should' be fixable in most cases.

The question about unrooted phones... Well, you can flash an custom recovery on your phone and get it bricked that way, but there is no need to flash another recovery if you're not going to root the device afterwards.

So just to clarify, you're not going to brick your device by normal use, rooted or not. The bricking part is when you're installing the recovery and root. When you succesfully rooted your device, there is no way you can brick it, until you're going to install another ROM on your device.

The worst thing that could happen with installing another ROM is getting stuck in a bootloop, but that can be fixed by going into the recovery and reflash(or install, if you prefer that term) the ROM. Unless it's the first time you're installing a custom ROM, in that case you will be stuck in a bootloop because you'll need to wipe the data, system and cache partition before installing a ROM. This prevents getting in a bootloop after installing a new ROM ;)
[General Questions and Answers] cleinadz:
Thanks !

Ok so i think i will root my phone tomorrow :) Im not in a purpose of installing custom ROM or kernel. I just want to use apps like dsploit or wifikill and it needs a proper root access. So its all clear and now i understand how bricky part happen. THANKS !
[8525, TyTN, MDA Vario II, JasJam General] mightyeric:
HOW DO I: Delete _all_ SIM contacts -- without -- erasing any 'Contacts' contacts?
[8525, TyTN, MDA Vario II, JasJam General] Elwyn M3100:
My Orange SPV M3100 has the same application. However, it only allows deleting of one entry at a time.

Although to be honest it's something you can do rather than playing Solitare :D :D :D
[8525, TyTN, MDA Vario II, JasJam General] mightyeric:
I've looked into this, but it's not obvious which ones are SIM contacts and which ones aren't. Any other ideas out there?
[8525, TyTN, MDA Vario II, JasJam General] Elwyn M3100:
MightyEric.

If you scroll to the bottom of the list in you contacts you will see some have got a small symbol to the right of the entry, that look suspiciously like a sim card.

It'll be them ;)

I've tried to delete them one-by-one too, but it's taken a while. I have usually found better things to do in my breaks. Like sleep :D

If you are still unsure then post again with your query ;)
[8525, TyTN, MDA Vario II, JasJam General] mightyeric:
I ended up putting my sim card into a different, empty phone and then deleting everything. Annoying, but it worked.
[8525, TyTN, MDA Vario II, JasJam General] dXsL:
start SIM manager, select menu/select all, press screen for 2 seconds or so, and select Delete in the popup window.

do NOT: start SIM manager, select menu/select all, select menu/delete contacts

Last one is almost the same, but does something totally different :D
[8525, TyTN, MDA Vario II, JasJam General] ultramag69:
Mate, check the date on this thread, It was over 2 years ago....
[8525, TyTN, MDA Vario II, JasJam General] dXsL:
true... hadn't seen that :eek:

anyway, solution is still valid, just now for WM 6.5.3 :)

(especially the "do NOT" part)
[One (M8) Q&A, Help & Troubleshooting] JJGLive:
Ok, so I have recently switched to a HTC One M8 and I am puzzled by a few things regarding unlocking the bootloader and flashing ROMs. Coming from a Samsung Galaxy s4 I have never really needed to worry about unlocking my bootloader. I have looked up on the subject and have found that with unlocking the bootloader using HTCdev you have to flash boot.img everytime after flasing a ROM on the HTC One. Does this also apply to the HTC One m8 ? If so does anybody have a better means of unlocking the bootloader without needing to do this after every ROM flash.
[One (M8) Q&A, Help & Troubleshooting] jshamlet:
You don't have to replace hboot unless you want to get rid of certain firmware messages, like the tampered flag. Unless you are sending your phone in for warranty work, you won't likely care about it, since you only see it in fastboot/hboot mode. The only thing the token does, besides unlock the boot loader, is remove certain preloaded apps, like the flashlight, which will screw up further OTA updates.

However, I would suggest you look into going S-off, as it makes locking/unlocking the boot loader possible without contacting HTC at all, and without messing up OTA updates. You also gain the freedom to change your CID (if you ever want to convert to stock Developer Edition), SIM unlock, and revert to older firmware if necessary (such as restoring an older RUU to go back to stock) However, S-off is "security off", so there is an increased chance of bricking the phone if you aren't careful.
[One (M8) Q&A, Help & Troubleshooting] JJGLive:
Ok so what i understand is: To install a custom rom I first have to get s-off, then unlock bootloader, root and install custom recovery and I am good to go? Please help me if I have missed anything.

I am used to flashing a rom every week on my Samsung. This is why I am so worried that I might do something wrong.

Edit: I have also found this link: http://xdaforums.com/showthread.php?t=2265618 please tell me if it is the correct way to do it.
[One (M8) Q&A, Help & Troubleshooting] jkolner:
I would suggest you use this guide.

Im going to use it this friday to root my phone.
[One (M8) Q&A, Help & Troubleshooting] JJGLive:
Ok so if I understand correctly now...using that guide I will not need to use htcdev and it will not be neccesary for me to flash boot.img after every rom flash?
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
Not quite. To flash a custom ROM, all you need to do is unlock the bootloader, install custom recovery, and flash a ROM. In addition, I highly recommend you make a nandroid backup before flashing anything

S-off is only needed if you want to avoid the bootloader unlocking method via HTCDev.com (and HTC therefore having a record of you unlocking by IMEI); or to flash hboot, radio, firmware, or a few other things (such as SIM unlock). S-off is not needed to flash a ROM.

One caveat, if your phone presently has older firmware, you will experience some severe bugs on any Sense 2.x based ROM (long boot times, broken WiFi or Bluetooth) and having S-off is required to manually update the firmware. So, while in literal terms, S-off is not needed to flash a ROM. But if the above applies to you, you need s-off to manually update the firmware and get the ROM to work correctly. Alternately, you can OTA to the latest firmware before modding the phone. You will need to list your phone's hboot and present software version for us to tell you what firmware you are on.

Also, its not necessary to root before flashing a custom ROM. You will be rooted after you flash a custom ROM.

Definitely not correct. That guide is for the M7. Be careful what device forum section you are in, and stay in the M8 section.
[One (M8) Q&A, Help & Troubleshooting] JJGLive:
Hell, I feel like a noob again. Ok so no boot.img flash after flashing a rom is needed.
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
Nope, not needed. Boot.img will flash automatically along with the ROM. Don't assume that anything on the M7 applies to the M8. These things change as the hardware changes, and every device has its own subtle differences.
[One (M8) Q&A, Help & Troubleshooting] JJGLive:
Thank you so much...this also applies if I use the htcdev unlock. Still no boot.img then?
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
Correct, no need to flash boot.img separately when flashing ROMs, if you unlock the bootloader via HTCDev.com (or by the S-off way).
[One (M8) Q&A, Help & Troubleshooting] JJGLive:
Thank you very much...I feel much more welcome in the htc one m8 thread than I did when I first started on the samsung s4 thread. You have made me feel very welcome!
[One (M8) Q&A, Help & Troubleshooting] mudassirrashid:
Thankfully we have freegee for LG OG. Bootloader is really dangerous please keep in mind before you go for any tutorials
[Samsung Galaxy Alpha] engid87:
hi all!

I've been reading various reviews of the Alpha, but I can't understand if the Alpha supports USB OTG, as some say it does while others say the opposite. Does anyone know?

The 32gb of memory would be perfectly fine for me if the phone supports USB OTG, so that I can keep videos and other stuff on the usb key I have in my keychain

thanks in advance!
[Samsung Galaxy Alpha] Winstrol:
Alpha has fully support USB-OTG - you can use USB-flash, TV-tuners e.t.c.
[Samsung Galaxy Alpha] robertkoa:
USB OTG ALPHA= Good

Because if I get Alpha I could back up photos presentations etc.

I see at Expansys a 2500 Mah battery and back Cover not yet in

stock but if new back plate is flush with Camera could be

cool.

I like the ruggedness and beauty of Alpha over the .. Z3C and

and Camera may have fewer issues also.

Have not seen Z3C in person yet but seems fragile and QC issues with pink spots photos . ., muffled speakers...

Wish the Alpha was more Note 4 like but same form but

10 mm thick , bigger battery , Note Camera etc.

But may take it as is if Z3 C is too quirky.

With USB OTG can Alpha read Media, Photos, etc.

directly from USB Device without loading into internal

memory ?
[Samsung Galaxy Alpha] svmpatel:
Hi,

Yes, the Alpha (at least the International one) does support USB-OTG out of the box. I use it myself on a daily basis with a Meenova USB-OTG MicroSD card reader and a 64GB MicroSD card formatted to exFat under windows so I can watch my movie files that are over 4GB in size.

I am also non-rooted and have no extra software loaded to allow the MicroSD to be read, everything is handled fine by stock ROM.

Hope that answers your question :)
[Samsung Galaxy Alpha] robertkoa:
Not the OP but thanks .

Can you also load Apps and Data on Apps onto USB Memory to use as Backup Storage in addition to

Photos etc. ?

No SD Card is more tolerable if everything can be backed up on USB Media.

Thanks.
[Moto X Android Development] Tqr:
Overview

This is MIUIv5 for Ghost.

Being a Beta, everything is assumed to have full functionality, under windows when drives are mounted they may have strange names like "invalid card", this is purely cosmetic.

Working

- Everything...(?)

Not Working

- ?

Download

MOD EDIT Links removed until the ROM is XDA compliant

F.A.Q
[Moto X Android Development] Megatron007:
OMG 1ST MIUI Rom ..Will Try It :D Thanx For The Rom :good:
[Moto X Android Development] Tqr:
Not just MIUI, you guys have no idea what's coming down the pipe after this lol
[Moto X Android Development] Black_Eyes:
is it with Your Mi Patcher?
[Moto X Android Development] Tqr:
Yes, I created it so I could more easily fork around my own builds. It was never originally intended for other people so I really hope to not see someone release over me using it
[Moto X Android Development] Black_Eyes:
Haha That's Crazy :D
[Moto X Android Development] Megatron007:
Haha !! Waiting For That " BooooM " :p
[Moto X Android Development] imparables:
Wow..MIUI! Awesome, thanks.

Sent from my Unlocked VZW M-O-T-O XxX
[Moto X Android Development] nickdez:
I love you :D
[Moto X Android Development] Tqr:
Uploading now friends~
[Moto X Android Development] Gus194:
Thanks so much! :)
[Moto X Android Development] skulldreamz:
Really appreciate the build. I've never tried miui so I think it's about time and you seem like you got your game on lock so I'm pretty stoked my dude. ?
[Moto X Android Development] Tqr:
Thanks! Everything should be functional beside Bluetooth Share which I've intentionally disabled for the time being in my Alpha runs for right now; all of my firmware shares the same codebase across devices meaning my MIUI for this device has the same ADB as another even across vendors.

More or less I feel being able to fork one code-base to multiple devices has huge advantages because feedback is progress and reaching 'Stable' on the general codebase is the same as having a stable firmware for whatever I can build for, that being said I prefer to not release garbage so even as an Alpha everything beside Bluetooth should function, there will be no nasty surprises like data or wifi not working..

ETA 2 minutes
[Moto X Android Development] Gus194:
One question...I'm guessing this is based on CM11 right? Or is it based on Stock?

Nevermind, just saw that it's unified for all Moto X's lol
[Moto X Android Development] Tqr:
It's based on CM11 but I'd like to make a distinction: I don't use the same codebase and only update MIUI, I also rebuild from source with the newest configs if available alongside MIUI.

A few of my last builds in the 4.2 era had Xiaomi's software camera, with some cooperation from people I could probably bring it to this device so more or less I intend to reach 'Stable' on this device, something with full functionality but feedback is progress~

Edit: I prefer unified builds, it's more productive than a PatchROM on stock
[Moto X Android Development] Musa95:
Downloading and testing..much appreciated!
[Moto X Android Development] Gus194:
Well...it didn't boot for me. Wiped everything and flashed the rom and when I rebooted it got stuck at the "M" bootlogo. I'll download it again to see if I was just a bad download

Edit: Yup, just downloaded it again, and the same happened.
[Moto X Android Development] stonesaber:
Same for me as well.
[Moto X Android Development] aarmstrong23:
Yup same for me! Stuck at M bootlogo! I try it second time and same thing happen!
[Moto X Android Development] Tqr:
Hmm, let me re-examine this. that's really unexpected

Edit: I'm an idiot......

In build.prop change:

persist.sys.root_access=1

to

persist.sys.root_access=0

Sorry.. forgot to change that value, updating the build to reflect this change

Edit 2: If that does not work please let me know ASAP for folks who have this and can test
[Moto X Android Development] aarmstrong23:
The build is updated? Can i reflash it?
[Moto X Android Development] Tqr:
it's updating now with what I believe is a fix, but I would be very grateful if someone could change

persist.sys.root_access=1

to

persist.sys.root_access=0

in build.prop and flash.
[Moto X Android Development] Tqr:
In any case bump with a new build that has this value changed; It's a required thing but I forgot it :X I'm sorry
[Moto X Android Development] Tqr:
https://www.dropbox.com/s/zzune5or4rcywiz/cm-11-20141001-UNOFFICIAL-ghost.zip?dl=0

This is the codebase for Ghost, if possible I'd like someone to flash this and confirm the base did not get corrupted during upload.

It's highly irreg for that to not start with proper 0 flag enabled
[Moto X Android Development] stonesaber:
Changed the build prop and it's still a no go for me.
[Moto X Android Development] Musa95:
Nothing changes
[Moto X Android Development] Tqr:
Last question, does the raw CM I posted boot? If not then the base got corrupted from being uploaded
[Moto X Android Development] leonardoafa:
Sorry...but wheres the download link? Am i lost or something??? :} MIUI rox....congrats for your work!!!

---------- Post added at 01:15 AM ---------- Previous post was at 12:55 AM ----------

I flashed it, and can confirm its working!

Pure CM11!

=/

---------- Post added at 01:36 AM ---------- Previous post was at 01:15 AM ----------

Can anyone provide Download link for the rom? I noticed that some issues and strange errors are present, but i want to give it a try anyway!

Thank you
[Moto X Android Development] sorullo_xgrx:
I will go the no booting issue could be related to the kernel since the cm base boots
[Moto X Android Development] Tqr:
Uploading fix now, I believe it's an issue with kernel signing no big deal

Edit: I hope
[Moto X Android Development] mac1996:
Just waiting for download link

..thanks for the new ROM✊✊✊
[Moto X Android Development] Tqr:
It's up, almost positive it didn't boot because of kernel issues but TEST THIS EXPECTING IT NOT TO BOOT. I'm testing this same config as well to confirm if people want to wait on the word before downloading, but if folks want to be active with testing it's up and feedback is surely appreciated
[Moto X Android Development] mac1996:
Downloading right now and will let you know about issues...thnks
[Moto X Android Development] Tqr:
The more I think about it the more I feel splitting the Ramdisk here destroyed the kernel on rebuild especially since this is kind of a newer device.

Anyway, the fact that it didn't even make it to boot feels kernel-related to me so I'm really hoping this one works w/out issue so I can move on to the next device
[Moto X Android Development] leonardoafa:
Downloading it right now for testing!

Ill let you know the results as soon as i get it!

Thank you
[Moto X Android Development] mac1996:
Heres the good news the rom finally boots i was able to play around with itt..

But there is a problem which is wifi doesn't work for me.. I only use wifi on my phone and it keeps saying "Obatining Ip Address & Authenticating"

*****Spoile Images***** Sorry For les resolutions Pics****
[Moto X Android Development] Tqr:
Yep, seems it was the kernel after all LOL.

Ok, can anyone else confirm wifi doesn't work and if so can ADB be provided?
[Moto X Android Development] Megatron007:
Finally :D Downloading Now :D
[Moto X Android Development] leonardoafa:
ROM boots just fine for me, and wifi is working also!

I will test it to see if i find any other bug or issue!

Thanks for your work!!

Will post some screenshots in a few minutes!
[Moto X Android Development] mac1996:
How come wifis not working for me.. i will try to reflash the rom again
[Moto X Android Development] Black_Eyes:
great,

it's booting, just checked on my friend phone...

now which will be your next device :confused:
[Moto X Android Development] Tqr:
Thanks for your patience- I guess the Moto X folks are rare like that lol
[Moto X Android Development] Tqr:
You'll find out in 20 minutes