Database Develop

[Q] Problem with Root after Stock ICS RUU update

I'm having issues getting the Superuser app to grant root to root apps.
The superuser apk is installed but isn't functioning.
Here's what I did. I was coming from pirateghost's CWM root ROM which was built off the stock developer's ICS OTA update (see my signature). I decided to start over since the sync icon would not go away from the notification tab. I know this is a minor issue but it was very annoying staring at it every time I used the phone.
I did the following:
1) Installed Wildchild's recovery using fastboot
2) Wiped all the data from the phone using wildchild's recovery
3) Locked the bootloader
4) Installed the ATT Stock RUU
5) Unlocked the bootloader
6) Reinstalled wildchild's recovery using fastboot
7) Installed the Superuser apk using wildchild's recovery
Everything is working fine and I don't have the sync icon stuck in the notification tab, but now I can't get any root application to be granted root access. The system just times out when the app is requesting root.
I'm guessing that Wildchild's recovery root is not compatible with the stock ICS release, but is this true? I haven't used the vivid all in one kit because it appears to be using the same method to install root. Everytime you install root it blows away all the data on the phone and makes you start from fresh, so I'm reluctant to try anything unless I'm certain it will work.
Any suggestions from the experts?

Did you look at the last post in the superguide? WC made a post to make rooting easier. Also a video in there as well.
Sent from my HTC PH39100 using XDA

megatronisabeast said:
Did you look at the last post in the superguide? WC made a post to make rooting easier. Also a video in there as well.
Sent from my HTC PH39100 using XDA
Click to expand...
Click to collapse
Yes, this is exactly what I did to the "T", just as in his video. SU is installed on my device but it doesn't grant any privileges to any root apps. I've been digging around searching for answers for about 3 hours and have found many people posting about the same issue but no fix.

3.07 is the latest version of su...redo it with unguarded version see if that works...the rom i used was unrooted and all stock

Wild Child said:
3.07 is the latest version of su...redo it with unguarded version see if that works...the rom i used was unrooted and all stock
Click to expand...
Click to collapse
I saw that and was wondering what "engineering Unguarded superuser" was but didn't know. I guess it's worth a try at this point.

FYI, I used the "Install eng (unguarded) su" and all it did was uninstall the Superuser apk.
Now the root apps respond with a different message when they request root. They don't see the SU app and reply with this statement, before they would hang while they requested SU access.
I'll wait until WC figures out what is going on or just download his ROM.
Are there any known bugs with his ROM?

[email protected] rooting....if going through trouble of unlocking bootloader and flashing a recovery....why not just flash a stock custom rom?....This make no [email protected] do this....Im the first to like completely stock builds,as thats what i use personally...but i cannot stand the at&t bloatware....Main problem with trying to root a stock build is the root access to kernel config....ill upload a stock rooted kernel, if having issues with root after using the recovery you need to install busybox from provided link below.
or flash the boot.img provided.
From original [email protected] guide
- ONCE BOOTED, if you have titanium backup installed but it says there isn't root or busybox isn't installed, download a free app from the market called BUSYBOX INSTALLER. Run this program and proceed in installing busybox. After that, try titanium backup again and it should work.
https://play.google.com/store/apps/...DMsImNvbS5qcnVtbXkuYnVzeWJveC5pbnN0YWxsZXIiXQ..

I had pirateghost's rooted ICS ROM installed but had the sync notification issue. That's why I decided to go back to the stock RUU. I've always been a stock kind of person. I don't know why, but I've always gone back to stock with my phones then rooted it and debloated it myself.
I'm downloading your ROM right now! Since I already have your recovery installed I'm sure this will be a breeze. Thanks!

megatronisabeast said:
Did you look at the last post in the superguide? WC made a post to make rooting easier. Also a video in there as well.
Sent from my HTC PH39100 using XDA
Click to expand...
Click to collapse
I tried using the WCX recovery to install su and I now have super user as one of the apps but Titanium backup could not acquire root privileges.
What am I doing wrong?

samsat said:
I tried using the WCX recovery to install su and I now have super user as one of the apps but Titanium backup could not acquire root privileges.
What am I doing wrong?
Click to expand...
Click to collapse
Look at wild Childs post a couple above this.
Sent from my HTC PH39100 using XDA

Thanks for helping Mega.
I tied installing busybox installer but it says no root access.
Is the stock rooted kernel being referred to boot.zip?
What's the safest way to flash this?

The fastboot flash boot boot.img command is the safest.
samsat said:
Thanks for helping Mega.
I tied installing busybox installer but it says no root access.
Is the stock rooted kernel being referred to boot.zip?
What's the safest way to flash this?
Click to expand...
Click to collapse

Wild Child said:
The fastboot flash boot boot.img command is the safest.
Click to expand...
Click to collapse
I successfully flashed the boot.img file above.
Titanium backup and busybox installer both say no root access.
No apps in superuser.
I really want to get your ROM installed, just this root issue which is stopping me!

Something else is going on then, my rom has nothing to do with this....the roms i release are already rooted and debloated stock builds
samsat said:
I successfully flashed the boot.img file above.
Titanium backup and busybox installer both say no root access.
No apps in superuser.
I really want to get your ROM installed, just this root issue which is stopping me!
Click to expand...
Click to collapse

Samsat, so let's see what you have done so far:
flashed boot.img
flashed recovery
what about the rom? What did you do with that? Was it a zip file from WC's site?

megatronisabeast said:
Samsat, so let's see what you have done so far:
flashed boot.img
flashed recovery
what about the rom? What did you do with that? Was it a zip file from WC's site?
Click to expand...
Click to collapse
Yes done the above but still running RUU ICS stock rom.

samsat said:
Yes done the above but still running RUU ICS stock rom.
Click to expand...
Click to collapse
I would say if you want root, the best thing to do is install one of Wild Child's roms. Once you install it, you will have root. He has an att build just like the att ruu but without the bloat.
http://www.wcxxperia-nce.com/index.php
This is his site. You have to register to see the vivid forum. Also, make sure to read the rules before installing his rom.

Exact process i did and it is rooted with titanium back up working...so flashing from wcxrecovery does work.
Testing procedure:
1 Flashed fastboot oem relock...success
2 Flashed PH39IMG.zip
3 Said Update was complete
4 Phone rebooted
5 My custom ROM was still present
6 Flashed PH39IMG.zip again
7 My custom ROM was still present
8 Attempted running RUU,Failed
9 Entered fastboot via Hboot menu
10 Re ran ruu,ROM updated completely.
11 Ran bootloader unlock command
12 Flashed wcx recovery (provided)
13 Flashed rooted kernel (provided)
14 Booted ROM,fully loaded
15 Rebooted into recovery
16 Installed superuser and su
17 Signed into Market
18 installed stericson Busybox
19 Installed titanium Backup
20 Succesfully rooted with stock att rom
21 Reboot phone after doing said process above Perm root achieved

Thanks WC. I must have been doing the same while you were posting this!
All went according to plan. I now have a rooted phone with unbloated ICS kernel, WCX recovery etc. etc.

Thanks WC, This is great

[Q] Flashing a Custom Kernel

Hi guys.
I'm attempting to flash the ElementalX-m7-5.2 on my phone which is currently running ARHD 21.0 Sense 5. My base is 3.17.xxx therefore I think everything should be fine. I just wondering what my Kernel version should read after I finish flashing it. From what I can see, it kernel hasn't been successfully flashed. Are there any prerequisites that I have to fulfill before flashing a custom rom?
Cheers.

s3330987 said:
Hi guys.
I'm attempting to flash the ElementalX-m7-5.2 on my phone which is currently running ARHD 21.0 Sense 5. My base is 3.17.xxx therefore I think everything should be fine. I just wondering what my Kernel version should read after I finish flashing it. From what I can see, it kernel hasn't been successfully flashed. Are there any prerequisites that I have to fulfill before flashing a custom rom?
Cheers.
Click to expand...
Click to collapse
Why not?
What's the error? You get it in recovery when you flashed?
Or are you talking about what you can see into settings?

Guich said:
Why not?
What's the error? You get it in recovery when you flashed?
Or are you talking about what you can see into settings?
Click to expand...
Click to collapse
Well it's beyond me really. Well, I have to get into recovery to flash it, so yeah.
Flashing seems to work as there is no error. I restart it twice, just as it requires. I go into my system info to check my kernel version, but nothing seems to have changed. Note, I've attempted to flash this twice now. Maybe, I'll just have to keep trying.

s3330987 said:
Well it's beyond me really. Well, I have to get into recovery to flash it, so yeah.
Flashing seems to work as there is no error. I restart it twice, just as it requires. I go into my system info to check my kernel version, but nothing seems to have changed. Note, I've attempted to flash this twice now. Maybe, I'll just have to keep trying.
Click to expand...
Click to collapse
ElementalX is "[email protected]" under kernel. If it shows that, then you're good.
Sent from my HTC One using xda app-developers app

ilal2ielli said:
ElementalX is "[email protected]" under kernel. If it shows that, then you're good.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Ahhhhh. Super! I guess it worked then. Brilliant. :good:

URGENT: New ota released (1.54.651.10) how do I take it if I'm root?

I'm root/soff. a new ota just came out that will fix my unusable phone. how do I take it if im root, do I have to fully unroot? or can I take it as is?
Sent from my SM-T217S using XDA Free mobile app

looks like it needs stock recovery to flash, it's not hboot format and twrp won't take it. will report back if I am able to do it
Sent from my SM-T217S using XDA Free mobile app

One of the benefits to being s-off is you don't have to take the OTA...you just flash the firmware and done.

BD619 said:
One of the benefits to being s-off is you don't have to take the OTA...you just flash the firmware and done.
Click to expand...
Click to collapse
i did that and then i was unable to take profile or prl updates :crying: it also didnt apear to have fixed the signal issue... i might not have waited enough... or it could have something to do with the unability to take prl and profile updates... anyhow ill try again from a diferent download see what happens

Did your baseband change? last four should be .0610.
If it did change then it's most likely a network issue.

BD619 said:
Did your baseband change? last four should be .0610.
If it did change then it's most likely a network issue.
Click to expand...
Click to collapse
Yes the baseband did change but the signal problem persists. i need to take the FULL ota to fix my phone (or install something else that will) regardless the radios alone aren't fixing the issue.

i tried flashing the rafios by themselves and it wouldnt update prl or profile; it also had the same signal issue. i tried the radios AND the new stock rom for it and same thing. i tried going back to stock and taking the ota and the ota wouldnt install.
Thoughs?

I'm the same root/s-off. I flash the h/k sound file did you find a way to install the latest ota update?

I cant figure out how to get the OTA either
I have S-Off im also rooted, and i have TWRP recovery, i can't get the zip to flash. I was thinking about doing a stock root recovery using the RUU, but then i thought if i do that, would i still be able to reroot using the same method? so my question is, how can i flash this zip and keep my root? or should do a stock recovery from the RUU and update and wait for another root? if any devs read this, i'd really like your help please and thank you. I currently have the stock rom with just root access and S-Off.no custom roms on here.

man.. i have the same problem bro.. smh.. hey man keep me posted if something comes up

Working via fastboot: http://forum.xda-developers.com/showthread.php?t=2759908&page=8

I am S-Off and had no issues, took 2 minutes, I followed the MikMik link

the 1.54.651.10 update.
If I'm rooted and have S on, how do i take the update?

jchtcusre1 said:
If I'm rooted and have S on, how do i take the update?
Click to expand...
Click to collapse
Settings>System Updates>HTC Software Update

BD619 said:
Settings>System Updates>HTC Software Update
Click to expand...
Click to collapse
I tried that and failed, I returned to a completely stock rooted backup from the day I rooted, downloaded the update, chose install, it rebooted to recovery, saw no stock recovery, so it brought up TWRP and thats it.........

scott_0 said:
I tried that and failed, I returned to a completely stock rooted backup from the day I rooted, downloaded the update, chose install, it rebooted to recovery, saw no stock recovery, so it brought up TWRP and thats it.........
Click to expand...
Click to collapse
I never OTA so not really sure of the process.

scott_0 said:
I tried that and failed, I returned to a completely stock rooted backup from the day I rooted, downloaded the update, chose install, it rebooted to recovery, saw no stock recovery, so it brought up TWRP and thats it.........
Click to expand...
Click to collapse
You have to have stock recovery to take the update, which means you have to flash stock recovery first and then take the update, then repeat the rooting process.

scott_0 said:
I tried that and failed, I returned to a completely stock rooted backup from the day I rooted, downloaded the update, chose install, it rebooted to recovery, saw no stock recovery, so it brought up TWRP and thats it.........
Click to expand...
Click to collapse
you should at least have seen a green arrow circle and/or a red triangle with a "!" in the middle. if you saw the triangle that is recovery trying and failing to update. at this point if you press and releast volumeup+power it should bring up the text of what it did.

rhe12 said:
You have to have stock recovery to take the update, which means you have to flash stock recovery first and then take the update, then repeat the rooting process.
Click to expand...
Click to collapse
I am dev unlocked, rooted, s-on with twrp. If I revert to stock recovery would I be able to take the OTA then reinstall twrp?
Many thanks!
Swyped mobile from HTC One M8.

drich66 said:
I am S-Off and had no issues, took 2 minutes, I followed the MikMik link
Click to expand...
Click to collapse
I'm looking at the MikMik one, and I am just not sure if this will erase all my apps and settings. Do I need to use a backup app or should I be ok flashing this and keeping all my apps and settings?

CWM Recovery problem

Hi, I followed the guide to install CWM and it seemed to go fine, but when I power on the phone and tap the vol-down key nothing happens, I do get the vibrations as I'm doing it though. Is CWM really necessary to install a custom rom? Cos I might just skip it.

You can't flash a custom rom without cwm recovery.
Sent from my C2104 using XDA Free mobile app

karthikys1 said:
You can't flash a custom rom without cwm recovery.
Sent from my C2104 using XDA Free mobile app
Click to expand...
Click to collapse
O lol, I guess I need to solve this then. I thought I just used FlashTool to flash the rom and viola, rom is on.
Does anyone have any ideas what I might be able to try to figure out why CWM isn't working? Any way to see if CWM is actually on my phone? (Maybe it's just not there, rather then not working).
Edit: Rom Manager seems to think I have CWM installed, also I did a Nandroid Backup which seemed to be configured to use CWM so I don't know if it's there or not, or working or not

Which guide did you follow? And how did you make a Nandroid Backup?

I followed this guide.
I downloaded Nandroid Backup Root, it created the backup without rebooting the phone, so it never needed to boot into CWM.

Astralogic said:
I followed this guide.
I downloaded Nandroid Backup Root, it created the backup without rebooting the phone, so it never needed to boot into CWM.
Click to expand...
Click to collapse
That's what I thought. The fact that it can create a backup doesn't mean it has a recovery installed, it doesn't use a recovery to create it. If the LED is lighting up at boot, and it is vibrating, and it doesn't get back in, I don't know what the problem would be. I'd try reinstalling CWM, and FYI, you should use V8; V9 has issues.
At the very least, if it really is installed, you should have a "recovery.tar" and "chargemon" file in /system/bin/.

Antiga Prime said:
That's what I thought. The fact that it can create a backup doesn't mean it has a recovery installed, it doesn't use a recovery to create it. If the LED is lighting up at boot, and it is vibrating, and it doesn't get back in, I don't know what the problem would be. I'd try reinstalling CWM, and FYI, you should use V8; V9 has issues.
At the very least, if it really is installed, you should have a "recovery.tar" and "chargemon" file in /system/bin/.
Click to expand...
Click to collapse
I don't have those files so CWM is not installed. I can't find v8 of CWM for Xperia T but I found this file "CWM4XperiaT_v8i_JB.zip", is that it?

Astralogic said:
I don't have those files so CWM is not installed. I can't find v8 of CWM for Xperia T but I found this file "CWM4XperiaT_v8i_JB.zip", is that it?
Click to expand...
Click to collapse
It clearly says "Xperia T" in the name of that file... yes, that's it. Now I'm wondering what you installed, if you didn't install that one, or V9.

Antiga Prime said:
It clearly says "Xperia T" in the name of that file... yes, that's it. Now I'm wondering what you installed, if you didn't install that one, or V9.
Click to expand...
Click to collapse
V8 works perfectly, it's installed fine.
I am going to follow this guide to install cyanogenmod, do I need to obtain a bootloader unlock code? Or should I just skip right to installing the ROM?
Edit: Oops forgot the link: http://wiki.cyanogenmod.org/w/Install_CM_for_mint

Astralogic said:
V8 works perfectly, it's installed fine.
I am going to follow this guide to install cyanogenmod, do I need to obtain a bootloader unlock code? Or should I just skip right to installing the ROM?
Edit: Oops forgot the link: http://wiki.cyanogenmod.org/w/Install_CM_for_mint
Click to expand...
Click to collapse
First of all, yes, you need an unlocked bootloader. You can't flash custom kernels on a locked bootloader. Secondly, I've never tried that tutorial (I have a TX), but I'm assuming it should work fine, but, personally I'd either go with FXP, or one of the OMNI builds here in XDA, since, as far as I know, developers here have more fixes than what I've seen on FXP and/or CM.
Also, there are a easier ways to flash your ROM, since you already have a custom ROM. I don't think it's necessary to have to fastboot the kernel first.
Edit: The Carbon ROM I'm on also has a T version. The reason I'm on this ROM (and previously OMNI) was because FXP/CM roms have/had a battery drain that was never fixed, something that was fixed here on XDA.

Antiga Prime said:
First of all, yes, you need an unlocked bootloader. You can't flash custom kernels on a locked bootloader. Secondly, I've never tried that tutorial (I have a TX), but I'm assuming it should work fine, but, personally I'd either go with FXP, or one of the OMNI builds here in XDA, since, as far as I know, developers here have more fixes than what I've seen on FXP and/or CM.
Also, there are a easier ways to flash your ROM, since you already have a custom ROM. I don't think it's necessary to have to fastboot the kernel first.
Edit: The Carbon ROM I'm on also has a T version. The reason I'm on this ROM (and previously OMNI) was because FXP/CM roms have/had a battery drain that was never fixed, something that was fixed here on XDA.
Click to expand...
Click to collapse
There's a problem My bootloader is not unlockable... does this mean I've been wasting my time?
Edit: There is this guide, it makes no mention of unlocking the bootloader so it might work?

Astralogic said:
There's a problem My bootloader is not unlockable... does this mean I've been wasting my time?
Edit: There is this guide, it makes no mention of unlocking the bootloader so it might work?
Click to expand...
Click to collapse
No, that tutorial won't work. Never follow a guide for flashing ROMs that wasn't meant for your phone. Your phone didn't even exist yet when that guide was written.
If you can't unlock your bootloader then there is no way you'll ever be able to flash a custom ROM, because, like I mentioned earlier, custom ROMs have custom kernels, and custom kernels need an unlocked bootloader.
I wouldn't consider it a waste, it's always useful to have a recovery installed; with it you can at the very least backup and restore, flash deodexed/zipaligned stock ROMs, such as this one, flash files, and even have access to ADB if your phone doesn't boot up, which can save you from having to wipe everything, etc., so not a complete waste of time.

Antiga Prime said:
No, that tutorial won't work. Never follow a guide for flashing ROMs that wasn't meant for your phone. Your phone didn't even exist yet when that guide was written.
If you can't unlock your bootloader then there is no way you'll ever be able to flash a custom ROM, because, like I mentioned earlier, custom ROMs have custom kernels, and custom kernels need an unlocked bootloader.
I wouldn't consider it a waste, it's always useful to have a recovery installed; with it you can at the very least backup and restore, flash deodexed/zipaligned stock ROMs, such as this one, flash files, and even have access to ADB if your phone doesn't boot up, which can save you from having to wipe everything, etc., so not a complete waste of time.
Click to expand...
Click to collapse
Ok, well, I learned a bit in the process, and I still have an Xperia SP bootloader to unlock, then flash cyanogenmod, so I'm in a better position to handle that now, thanks for all the help guys.

Cannot get M Preview 2 rooted

Alright, so I had M Preview 1 and used the rooting procedure from this thread: http://forum.xda-developers.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!

jonzey231 said:
Alright, so I had M Preview 1 and used the rooting procedure from this thread: http://forum.xda-developers.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!
Click to expand...
Click to collapse
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.

simms22 said:
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.
Click to expand...
Click to collapse
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.

jonzey231 said:
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.
Click to expand...
Click to collapse
well, then its odd, you should have gotten root after flashing both in recovery.

simms22 said:
well, then its odd, you should have gotten root after flashing both in recovery.
Click to expand...
Click to collapse
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://forum.xda-developers.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.

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.

jonzey231 said:
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.
Click to expand...
Click to collapse
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.

simms22 said:
well, then its odd, you should have gotten root after flashing both in recovery.
Click to expand...
Click to collapse
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.

simms22 said:
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.
Click to expand...
Click to collapse
It's finally up and loaded and yes, I've got root now. Thanks for your help today.

jonzey231 said:
It's finally up and loaded and yes, I've got root now. Thanks for your help today.
Click to expand...
Click to collapse

simms22 said:
Click to expand...
Click to collapse
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.

jonzey231 said:
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.
Click to expand...
Click to collapse
sure. i just flashed an m compatible kernel(despair), and supersu 2.49. bow ive root with full access, write as well.

simms22 said:
sure. i just flashed an m compatible kernel(despair), and supersu 2.49. bow ive root with full access, write as well.
Click to expand...
Click to collapse
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.

jonzey231 said:
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.
Click to expand...
Click to collapse
yea, it seems as a few are having this same issue, while most have no issue http://forum.xda-developers.com/nexus-6/general/root-nexus-6-android-m-dev-preview-t3123285/page18

simms22 said:
sure. i just flashed an m compatible kernel(despair), and supersu 2.49. bow ive root with full access, write as well.
Click to expand...
Click to collapse
simms22 said:
yea, it seems as a few are having this same issue, while most have no issue http://forum.xda-developers.com/nexus-6/general/root-nexus-6-android-m-dev-preview-t3123285/page18
Click to expand...
Click to collapse
Yeah I just flashed Despair and SuperSU to replicate what you've done and still nothing.
This is pretty irritating.

jonzey231 said:
Yeah I just flashed Despair and SuperSU to replicate what you've done and still nothing.
This is pretty irritating.
Click to expand...
Click to collapse
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://forum.xda-developers.com/nexus-6/development/rom-jdx-1-0-t3121053

simms22 said:
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://forum.xda-developers.com/nexus-6/development/rom-jdx-1-0-t3121053
Click to expand...
Click to collapse
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.