yashsingh1/xdaforums huggingface dataset:
[Nexus 6 Q&A, Help & Troubleshooting] jonzey231:
Alright, so I had M Preview 1 and used the rooting procedure from this thread: http://xdaforums.com/nexus-6/general/root-nexus-6-android-m-dev-preview-t3123285 and it worked flawlessly with no booting errors or anything.

Now that I've upgraded to Preview 2 on the day it was released I can't get it to root. I've tried the methods in that post, I've tried some other methods that I've picked up over the years of doing this kind of stuff and no matter what I end up in a boot loop or a boot validation error that just shuts the phone down. So I just end up re-flashing the system and boot partitions to get it back up again while I look for more solutions.

I've looked all over XDA and some other forums thinking that maybe I need a different kernel, or Super SU package but I can't find anything. If someone can explain to me or at least reply with a link to a thread that will help me out I'd really appreciate it.

Thanks in advance!
[Nexus 6 Q&A, Help & Troubleshooting] simms22:
flash any m based custom kernel, i generally use despair or elementalx, and then flash the latest supersu, when you boot, youll have root. the latest supersu is version 2.49 btw. and if you want to yse the kernel in that thread, elite kernel, grab the latest m version, not the one in that thread, its old.
[Nexus 6 Q&A, Help & Troubleshooting] jonzey231:
Yeah I tried using the latest M version of that kernel and yes, I used Super SU 2.49. Thanks though, I'll try the latest elementalx kernel.
[Nexus 6 Q&A, Help & Troubleshooting] simms22:
well, then its odd, you should have gotten root after flashing both in recovery.
[Nexus 6 Q&A, Help & Troubleshooting] jonzey231:
I know, right? I'll give it another shot. I'm getting ready to do it now. I'll update in a few minutes when I've finished up.

Edit: Grabbed Elemental from here: http://xdaforums.com/showpost.php?p=61931417&postcount=3921&nocache=1

Updated last night so it should be the absolute latest version. So I'll flash twrp in fastboot, then boot into twrp and flash the kernel first, and then supersu and I should be good to go.
[Nexus 6 Q&A, Help & Troubleshooting] jonzey231:
The Elemental Installation is freaking awesome! I've never installed it before. That's so cool how it brings up it's own interface for the install to customize your setup.

And the phone just booted up after flashing both the kernel and supersu.

The boot animation (spinning colored dots) is glitching out though. Can't tell if it's a "setting up" type of thing or not. It's optimizing app 1 of 1 right now.
[Nexus 6 Q&A, Help & Troubleshooting] simms22:
yea, elementalx uses the aroma installer, whete you can pick and chose what you wnt in the kernel. sounds like its booting, hopefully youll have root.
[Nexus 6 Q&A, Help & Troubleshooting] jonzey231:
It's been in a bootloop for like 5 minutes. It would get the the Android is Starting screen and loan for about 30-40 seconds, then reboot.

Then it would hit the validation screen and reboot.

Then it would boot back to Android is Starting, freeze, and reboot lol

It is very erratic, all of this has been going on without any interference from me. Just letting it sit there trying to work through it's issues.

Then all of a sudden as I was typing "adb reboot-bootloader" the thing boots right into my existing lockscreen haha. So I guess I'll just do my best to not have to reboot this thing in case it wants to have a seizure like that again lol.
[Nexus 6 Q&A, Help & Troubleshooting] jonzey231:
It's finally up and loaded and yes, I've got root now. Thanks for your help today.
[Nexus 6 Q&A, Help & Troubleshooting] jonzey231:
One final question.

Is there any way to get system write access? If so, what did you use? I tried the fix_rw_boot.img that I used for preview 1 and it just put me in a boot loop lol.
[Nexus 6 Q&A, Help & Troubleshooting] simms22:
sure. i just flashed an m compatible kernel(despair), and supersu 2.49. bow ive root with full access, write as well.
[Nexus 6 Q&A, Help & Troubleshooting] jonzey231:
Hmmm...I flashed Elite with SuperSU and ElementalX with SuperSU. Wasn't able to get root with either one. Clean flashes (coming from formatted partitions) each time too.

I've got it up and rooted and restored but don't have access to write to the system partition at all no matter what I try.
[Nexus 6 Q&A, Help & Troubleshooting] simms22:
yea, it seems as a few are having this same issue, while most have no issue http://xdaforums.com/nexus-6/general/root-nexus-6-android-m-dev-preview-t3123285/page18
[Nexus 6 Q&A, Help & Troubleshooting] jonzey231:
Yeah I just flashed Despair and SuperSU to replicate what you've done and still nothing.

This is pretty irritating.
[Nexus 6 Q&A, Help & Troubleshooting] simms22:
ok, i think i have a solution for you. its a little dirty, but its a solution i think. im running it right now, so its safe. its a basic m version 2 rom. it doesnt have many additions to it, its very basic. but i think youll get root. make a backup, i think that you could dirty flash it. or, to be safe, id wipe data. flash supersu 2.49 as well. heres the rom http://xdaforums.com/nexus-6/development/rom-jdx-1-0-t3121053
[Nexus 6 Q&A, Help & Troubleshooting] jonzey231:
Awesome, I didn't really he'd made a ROM for Preview 2 yet. I'll make a backup and give it a shot, thanks for pointing this out to me.

I'll let you know how it goes as well!

Update: it worked!!! I wiped the system partition and flashed the ROM. It failed the first time so I tried again after mounting the system and now I've got too with system write access!! Spread the word my friend.
[P3600 Accessories] kimusan:
I just saw that HTC is releasing a stereo headset with audio control called E100

http://www.expansys.com/htc/p_htc_item.aspx?i=150191

bit I simply cant see where it differs from the W100.

Does anyone know this?
[P3600 Accessories] Azamat:
I guess it's the same, but the E100 has a headset with it, the W100 does not
[One (M7) Q&A, Help & Troubleshooting] QA Bot:
Q&A for [KERNEL][21. Aug][GoogleEdition][Android 4.3] JMB-M7-GE r2.0

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 [KERNEL][21. Aug][GoogleEdition][Android 4.3] JMB-M7-GE r2.0. 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! :)
[One (M7) Q&A, Help & Troubleshooting] SUPAXOR:
dead link

Can you send me this kernel please ?

Your link doesn't work...
[G3 Q&A, Help & Troubleshooting] bitpie:
Hi.

So today i have small problem with TB. Picture and Title can say everything.

And can be like that all the time. yesterday i left backup accidentally for all night and in the morning i had 99%. So it looks like still backing but need few days lol. Or i wrong - idk.

First time i see something like this, Where is the problem and how to resolve it ? I need backup bcs i want to change kernel for Gabriel for my 5.7.11 miui
[G3 Q&A, Help & Troubleshooting] Vivek_Vivek:
TB has issues when it comes to backing up system apps. Try it again, unticking the erratic app
[Xperia Z4/Z3+ Q&A, Help & Troubleshooting] T.ghouas:
Hello xda's!

I unlocked the bootloader on my Sony Xperia z3+. It worked just fine, but after a sertain time (I think it was after I rebooted the phone first time after unlocking) it now says under "Service info->Configuration" the following:

Rooting status: Unknown

HW Config rev.: Unknown

Remote Lock State: Not Lockable

Security Configuration: Test

When I check status either using "Emma" (Sony's own flashtool) or Flashtool, they both indicate that the phones bootloader is locked. I tried running the same prosedure using the Sony Android SDK to unlock it "again", but the command return a fault indicating it has already been run succesfully once and of course can't do it again. I have tested the "Remote Lock State", and it works (unlike what the Service info. reports). I can't seem to find anyone that have similar problem. Suggestions for a solution?
[Xperia Z4/Z3+ Q&A, Help & Troubleshooting] hush66:
How did you unlock your Z3+ bootloader in the 1st place? The official site (http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/) does not even list the Z3+ as one of the supported devices for unlocking.
[Xperia Z4/Z3+ Q&A, Help & Troubleshooting] T.ghouas:
Found partly answers to my questions.

Before I unlocked the bootloader I forgot to deactivate the "My Xperia" (Xperia Theft Protection = MXTP). It is all explained at "developer.sonymobile.com/unlockbootloader : After unlocking your device, you should not enable My Xperia (found in the settings menu under security on some devices running Android 5.0) as this might cause the device to malfunction". As mentioned, "My Xperia" was already active before I unlocked the bootloader. It was probably not the wisest thing of me not reading the instructions thoroughly anough. But at the same time can a serious company offer unlocking the bootloader and at the same time having one of their own proprietary programs causing the phone to malfunction? Then I think they should not offer that kind of service at all.

I was wrong when I said that I was able to remotely lock the phone in that satus. If u remove your google account on the phone under "accounts", you can just restart the phone after locked state shows up and the phone will work normaly. But, you will not be able to remove/deactivate the "My Experia" and the bootloader seems to be in a locked state (even if Flashtool reports it as unlocked in flashmode).
[Xperia Z4/Z3+ Q&A, Help & Troubleshooting] T.ghouas:
Hello Hush!

...the Z3+ is just not yet officially suported. If u trough the " developer.sonymobile.com/unlockbootloader " site, choose for example the Z3 together with the IMEI code and u will be provided with a bootloader code.
[Xperia Z4/Z3+ Q&A, Help & Troubleshooting] Rookie123:
Hi T.ghouas,

I am facing same exact problem as you. Did exactly what you did. Unlocked bootloader, rooted and then activated myXperia. :(

And I am stuck with locked bootloader and it cannot be unlocked now!!

Were you able to find a solution to unlock the bootloader again?
[Xperia Z4/Z3+ Q&A, Help & Troubleshooting] T.ghouas:
No change in staus.

Hello Rookie!

Sorry, no change in status. I guess we have 2 wait for the more experinced ones 2 come up with a solution, if there ever will be. Another downside to this is that the DRM keys are also lost. You will notice that on the cameras problem 2 autofocus, especially on close up objects. Apart from that, the phone is working just fine. "MyXperia" is not someting I will miss, apart from being that tiny safety.
[Xperia Z4/Z3+ Q&A, Help & Troubleshooting] DHGE:
you are lucky the device is still working

[MENTION=6834029]T.ghouas[/MENTION]

From what I read here (maybe a bit sensational journalism) and these guys know what they are writing about:

http://fxpblog.co/2015/07/03/dont-destroy-your-unlocked-device.html

They have bricked their devices beyon soft repair so they need to send them in.
[Xperia Z4/Z3+ Q&A, Help & Troubleshooting] T.ghouas:
Hello DHGE!

Thx for the info. I'm not sure how they managed to brick their devices the way they did? Cause it seemed to me they did pretty much the same mistakes I did. My phone as resaulted more in the way that the MXTP is not working, lost DRM keys and an uknown status of the bootloader. Phone is working just fine, apart from that.
[Xperia Z4/Z3+ Q&A, Help & Troubleshooting] dl12345:
It's amazing that Sony is embracing the open devices meme but does such a bone-headed thing as to allow one of their own apps to permanently lock down a device if inadvertently activated. These Xperia's have really nice hardware design but they're a real challenge on the software side of things.

The first thing I did after rooting my device was to delete the MyXperia app from the phone thanks to the public reports from those unfortunate enough to have fallen victim to Sony's apparent obsession with locking down phones. Having owned only Samsung devices for the last 4 years or so, I complained bitterly about Knox. However, they're neophytes when stacked up against Sony's shenanigans.

I wish these manufacturers would get it. I don't give a sh1t about their software. I just want a device with cool design and decent hardware. I'll put my own software on it thank you very much. And the degree to which they lock it down is inversely proportional to the phones desirability to me as a customer.

Ha, rant over. Sorry for running off on a tangent.
[Xperia Z4/Z3+ Q&A, Help & Troubleshooting] mohinipollob:
Hi ,

At first take my thanks .your answer is very informative.Go ahead
[Xperia Z4/Z3+ Q&A, Help & Troubleshooting] seriousstas:
The same problem does not yet have a solution?
[Xperia Z4/Z3+ Q&A, Help & Troubleshooting] T.ghouas:
Hello Seriousstas!

Most likely it will never be solved, according to Sonys respond to my question on this matter. You can send it in for repair, which means replacing the motherboard. That will be approx half/60% of the price of a new phone. Don't want to sound to negative, but for me there is no more Sony on the basis of:

1. Unlocking boot loader vs MXTP prob.

2. Unlocking boot loader and loss of DRM keys and the effect that has, especially on the camera.

3. Z3+ has the same rear glass probl. has the Z3, it breakes easily. This has happened to boths phones (Z3+) where I work, incl. my own. 1000 of ppl reported this on the Z3. Sony would not admit that this was a serious production error, which ended up in ppl having to pay for the repair them self. Of all the ppl I have talked to, that encounterd that problem say they will never buy Sony again.

4. There are always some annoying prod. errors with their phones, which at least I always think is either that they don't care about or that they are not checking the product thoroughly before it is released.

(5). Bloatware.

Sony phones usually come have really nice feauters, like good camera, IP67 certificated and nice design. But, as mentioned there are to many repeating draw backs. Sony has been asked a few times why their phone sale does not "take off" and that they are considering stopping the phone prod. I think a good deal of it comes from to many dissatisified customers that easly find comfort in other brands, and stay with them. Its hard to clear a bad reputation. Yes, I think they should stop selling phones.

I'm sorry for the offload here, and its questionable if some of my views belongs to this tread. I just say this so that you and others in same position should not have to high hopes solving the "main issue", cause there will be no help from Sony.
[Xperia Z4/Z3+ Q&A, Help & Troubleshooting] artsfreaky:
i unlocked bootloader using flashtools

Rooting status: unknown

HW Config rev: HWC_Kitakami_Com_009

Remote Lock State: Unlocked

Security Configuration:

Live

return to relock

Rooting status: Bootloader unlocked:Yes

HW Config rev: HWC_Kitakami_Com_009

Remote Lock State: Unlocked

Security Configuration:

Live

there is any sulotion for this issue pls help me guys..........................................
[Xperia Z4/Z3+ Q&A, Help & Troubleshooting] artsfreaky:
nothing happen never buy sony mobile ever.....
[Microsoft Surface] DEV_AKA:
Hi

I'm using Surface RT 8.1 I'm trying to edit an application.

This is what I done so far:

*Took full ownership and control of the folder

*created a folder in Windows apps renamed and cut files of the application into that

*I was able to edit this file now

However in order for the application to run I need to add the unknown account into security permission, how can I do this?

it turns out the unknown account is not necessary it only requires "ALL APPLICATIONS PACKAGES" but when I try running the app it still fails
[Verizon LG G3] 2ndAmendNut:
Everything looked good but it's been in this state for 45 minutes. Did I just brick my phone?
[Verizon LG G3] RMarkwald:
Are you trying to do this on 24B? I'm pretty sure one click root doesn't work on 24B....
[Verizon LG G3] 2ndAmendNut:
23C
[Verizon LG G3] 2ndAmendNut:
So I uninstalled/reinstalled everything (or so I thought) and now I'm getting this error message.
[Verizon LG G3] NBreunig3:
Google newest LG root method I have a one click script that roots 24B.
[Verizon LG G3] thegracerandall:
Currently experiencing the same issue. Was your phone bricked? If not, how did you fix the issue?
[Verizon LG G3] mopartonyg:
Try this method instead of one click http://xdaforums.com/showthread.php?t=3129197
[Android Q&A, Help & Troubleshooting] QA Bot:
Q&A for Asus me175cg (single sim) return to KitKat

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 Asus me175cg (single sim) return to KitKat. 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! :)
[Android Q&A, Help & Troubleshooting] zyyraf:
I have this model too.

Update from KitKat to Lolipop on this is like... like migration from XP to Vista few years ago on PC.

Anyone know how to downgrade to KitKat on Asus K00Z?

Or may, whether Asus will give us next update?
[G2 Q&A, Help & Troubleshooting] doxiarski:
Hello guys

My Lg G2 have cracked screen and display doesn't work so i can't do factory reset by the settings. I also can't turn off my phone to do Hard Reset.

Can anyone tell me please how can i do factory reset by the computer? Or is there any other method to do this?
[G2 Q&A, Help & Troubleshooting] MilanStojkovic:
You can't turn off your phone? That means your back physical buttons are not working also, right?
[Testing] plamencoapps:
[how to] Acquiring API keys

Go to the Google Developers Console.

Select a project, or create a new one.

In the sidebar on the left, expand APIs & auth. Next, click APIs. Select the Enabled APIs link in the API section to see a list of all your enabled APIs. Make sure that the API is on the list of enabled APIs. If you have not enabled it, select the API from the list of APIs, then select the Enable API button for the API.

In the sidebar on the left, select Credentials.

Click Create new Key and select the appropriate key type:

Server keys

Create and use a server key if your application runs on a server. Do not use this key outside of your server code. For example, do not embed it in a web page. To prevent quota theft, restrict your key so that requests are only allowed from your servers' source IP addresses.

Browser keys

Create and use a browser key if your application runs on a client, such as a web browser. To prevent your key from being used on unauthorized sites, only allow referrals from domains you administer.

iOS keys

Create and use an iOS key if your application runs on iOS devices. Google verifies that each request originates from an iOS application that matches one of the bundle identifiers you specify. An app's .plist file contains its bundle identifier. Example: com.example.MyApp

Android key

Create and use an Android key if your application runs on Android devices. To do so, you need to specify the SHA1 fingerprints and package names of the application using that key.
[Xperia Z3 Q&A, Help & Troubleshooting] OnSugarHill:
Hi guys,

I cracked my screen two days ago and took it to a repair shop. They replaced the screen, and it looks great, but I am unable to make calls/texts on the phone. Most of the time, there is a triangle up top in the notification bar indicating that I don't have service. The SIM card is working fine. I tried using it on a different phone and it still works great, but it is not working on the Xperia Z3. It did work very briefly for about 20 seconds and I was able to make one call, but then it went back to no service. Do you think they messed something up when they fixed the phone?

For what it's worth, the SIM card was working fine after the drop. I was still seeing texts/calls coming in, but I couldn't answer them since my touch screen was unresponsive.
[Xperia Z3 Q&A, Help & Troubleshooting] AlvinZahran98:
Claim more and claim hard about it. Sony service centre all over the world sometimes (well, most of the times) did some crap things like that and other craps. Contact them again and ask them for replacement or just fix your phone.

Just sue 'em if they charge you a crazy price
[Android Studio] plamencoapps:
Creating a Run Configuration

The run configuration specifies the module to run, package to deploy, Activity to start, target device, emulator settings, and Logcat options. Run configuration can be set at the project, default, and module levels. When you first run a module as an Android Application, Android Studio will automatically create a run configuration. The default run configuration will launch the default project Activity and use automatic target mode for device selection (with no preferred AVD). If the default settings don't suit your project or module, you can customize the run configuration or even create a new one.

To create or modify a run configuration, see the IntelliJ documentation on Run/Debug configurations.

The following steps highlight the important things you need to do for an Android project:

Open Edit Configurations from the Run Menu.

Expand the Android Application item and create a new configuration or open an existing one.

With the Run Configuration selected, adjust your desired run configuration settings:

In the General tab, specify the Module settings to launch. In Target tab, consider whether you'd like to use Manual or Automatic mode when selecting an AVD to run your application. See the following section on Automatic and manual target modes).

In the Emulator tab, specify any emulator options to the Additional Emulator Command Line Options field. For example, you could add -scale 96dpi to scale the AVD's screen to an accurate size, based on the dpi of your computer monitor. For a full list of emulator options, see the Android Emulator document.

In the Logcat tab, set the LogCat options for the application.
[General Topics] dieterpapa:
Hello all,

has anybody already got Pylon Pro (5.41 build 138) running under WM 6 ? I need a confirmation before upgrading my Ameo...

Dieter
[One (M8) Q&A, Help & Troubleshooting] JimmyKane9:
Hi there all.

I am on gpe lollipop h6 patch .

I have the following problem. I can write on the sd card and delete files via es explorer but not via some apps.

Example if i delete a photo via the new Google photos app or htc gallery , the image is removed from the app but when I naviagte there its still there.

Another wierd thing is that these apps have write access on the card so eg if I trim a video the new trimmed version is saved on the external sd folder.

Also the htc gallery app when I try to copy an image complains as it cannot access the sd card while it can.

I am rooted and have applied also the sd card permission patch via the twrp manager app and all went ok.

All apps have access on the sd card but I am bothered by this strange behavior.
[One (M8) Q&A, Help & Troubleshooting] WingZer0n:
Use the stock htc file manager
[One (M8) Q&A, Help & Troubleshooting] jball:
"Root Explorer" usually does the job
[Android Q&A, Help & Troubleshooting] aadeezboy:
Is there any way to install bootloader because i just bricked my bootloader of asus zenfone 4 a400cg.I can't go in to fastboot .....plz help me or is there any way to perform fastboot cmd without going into bootloader..help me plz