Related
Hi All,
S2W is not working on the new version of MIUI ROM V5 [3.8.30]
OK, I tried the new TESCO V2.9++ from the link http://forum.xda-developers.com/showthread.php?t=2385808
Dont know what did i do wrong , I did the same steps as instructed.
Installed the new version 3.8.30, did a clean wipe. didnt install Gapps. booted boot.img from the zip. then flashed the kernel. wiped dalvik+cache(4ext recovery) and restarted. did i do something wrong here ???
mafie said:
Hi All,
S2W is not working on the new version of MIUI ROM V5 [3.8.30]
OK, I tried the new TESCO V2.9++ from the link http://forum.xda-developers.com/showthread.php?t=2385808
Dont know what did i do wrong , I did the same steps as instructed.
Installed the new version 3.8.30, did a clean wipe. didnt install Gapps. booted boot.img from the zip. then flashed the kernel. wiped dalvik+cache(4ext recovery) and restarted. did i do something wrong here ???
Click to expand...
Click to collapse
Whether or not you flashed TESCO kernel isn't the issue. Maybe the developer disabled S2W. Plus are you S-OFF? Because if not, you need to follow S-ON instructions for flashing kernel which can be found in the XS-ICS kernel thread.
I am S-off, but still not able to get through. But, Ya could be as u said that the developer would have disabled it..
Sent from my Incredible S
mafie said:
I am S-off, but still not able to get through. But, Ya could be as u said that the developer would have disabled it..
Sent from my Incredible S
Click to expand...
Click to collapse
You could install trickstermod and enable it...
Sent from one of the few remaining Incredible S'
Thanks, It worked. But the time to wake the device seems to be more than the lock time when i sweep.
So I'm rooted with an unlocked boot loader and a custom ROM installed but when I downloaded some apps it said it can't access root so I checked root checker and it said
My phone isn't rooted even tho I have supersu and a custom ROM on it
Sent from my HTC One using xda app-developers app
Remove the super su and install superSU.zip from recovery.
Sent from my One V using xda app-developers app
Are you sure nothing will happen? Can I just get it from Google play?
Sent from my HTC One using xda app-developers app
Zakdroid said:
Are you sure nothing will happen? Can I just get it from Google play?
Click to expand...
Click to collapse
If you just moved up to 4.3, root implementation has changed, so you need to flash SU from recovery the first time.
iElvis said:
If you just moved up to 4.3, root implementation has changed, so you need to flash SU from recovery the first time.
Click to expand...
Click to collapse
I'm having similar issues with my HTC One, I unlocked and rooted and installed Maximus HD 13 rom - that's when I started getting problems with SuperSu - first the update issue, now it says no binaries.
I tried installing it from recovery, I even tried CWM, then reflashed TWRP. Still nothing, same error. No binaries. Driving me bloody crazy.
ieldra said:
I'm having similar issues with my HTC One, I unlocked and rooted and installed Maximus HD 13 rom - that's when I started getting problems with SuperSu - first the update issue, now it says no binaries.
I tried installing it from recovery, I even tried CWM, then reflashed TWRP. Still nothing, same error. No binaries. Driving me bloody crazy.
Click to expand...
Click to collapse
Do a full wipe and start over, flashing rom and then supersu together.
iElvis said:
Do a full wipe and start over, flashing rom and then supersu together.
Click to expand...
Click to collapse
Yeah it looks like that's what I'm gonna have to do, should I wipe boot as well ? Maximus HD installs the stock kernel as well, wondering if it also installs hboot. Afaik /boot is split into boot and kernel. Wouldn't wanna wipe the entire device, install the ROM, reboot and find myself with no hboot !
ieldra said:
Yeah it looks like that's what I'm gonna have to do, should I wipe boot as well ? Maximus HD installs the stock kernel as well, wondering if it also installs hboot. Afaik /boot is split into boot and kernel. Wouldn't wanna wipe the entire device, install the ROM, reboot and find myself with no hboot !
Click to expand...
Click to collapse
hboot and boot.img are two different things. No rom will touch hboot. Only way to change your hboot is via RUU or OTA, or to s-off and flash in RUU mode.
All roms include a kernel, usually the stock kernel. That will overwrite whatever you had there before but you should still wipe /data.
iElvis said:
hboot and boot.img are two different things. No rom will touch hboot. Only way to change your hboot is via RUU or OTA, or to s-off and flash in RUU mode.
All roms include a kernel, usually the stock kernel. That will overwrite whatever you had there before but you should still wipe /data.
Click to expand...
Click to collapse
Thanks for your replies man! Really helpful ! I installed Maximus HD again, formatted everything I possibly could... it comes preloaded with supersu. Still says no binaries... What the hell should I do
ieldra said:
Thanks for your replies man! Really helpful ! I installed Maximus HD again, formatted everything I possibly could... it comes preloaded with supersu. Still says no binaries... What the hell should I do
Click to expand...
Click to collapse
Did you flash the supersu zip separately in recovery? I've had to do that every time I installed a 4.3 rom.
iElvis said:
Did you flash the supersu zip separately in recovery? I've had to do that every time I installed a 4.3 rom.
Click to expand...
Click to collapse
Alright, basically what I did today is I wiped every single partition I had access to, so everything but boot and recovery. installed maximus HD 13, installed faux kernel, installed faux kernel camera fix. Maximus installs supersu by default, I opened it up and I got the stupid no binary error. So I went back to recovery and attempted SuperSu 1.65 from zip, still the same problem. Please note that I did all this BECAUSE of my issues with root, funny how after nuking the whole phone I still have the same problem. I've google extensively, and pretty much the only advice I've found involves either rooting from recovery or changing something in SuperSu settings, which I CAN'T ACCESS because the app closes right after the error prompt pops up.
I'm a few desperate attempts short of attempting an exorcism...
ieldra said:
Alright, basically what I did today is I wiped every single partition I had access to, so everything but boot and recovery. installed maximus HD 13, installed faux kernel, installed faux kernel camera fix. Maximus installs supersu by default, I opened it up and I got the stupid no binary error. So I went back to recovery and attempted SuperSu 1.65 from zip, still the same problem. Please note that I did all this BECAUSE of my issues with root, funny how after nuking the whole phone I still have the same problem. I've google extensively, and pretty much the only advice I've found involves either rooting from recovery or changing something in SuperSu settings, which I CAN'T ACCESS because the app closes right after the error prompt pops up.
I'm a few desperate attempts short of attempting an exorcism...
Click to expand...
Click to collapse
I have not used Maximus, so maybe you should move over to that thread. I had the same issues with ARHD, but flashing SuperSU in recovery after the rom flash took care of it. In all likelihood, you're not the only Maximus user to deal with this, so the answer may be over there.
iElvis said:
I have not used Maximus, so maybe you should move over to that thread. I had the same issues with ARHD, but flashing SuperSU in recovery after the rom flash took care of it. In all likelihood, you're not the only Maximus user to deal with this, so the answer may be over there.
Click to expand...
Click to collapse
I don't know what changed, but i changed TWRP for CWM, installed the rom, then immediately installed supersu and it worked. I love you. I want you to have my babies.
ieldra said:
I don't know what changed, but i changed TWRP for CWM, installed the rom, then immediately installed supersu and it worked. I love you. I want you to have my babies.
Click to expand...
Click to collapse
I'm lacking the uterus for that, but feel free to hit the Thanks button.
iElvis said:
I'm lacking the uterus for that, but feel free to hit the Thanks button.
Click to expand...
Click to collapse
Alright, so SuperSu WORKED. Until I flashed the faux123 kernel, at which point it stopped working again. Same issue, no binaries. So I reformatted the whole phone, installed Rom, then faux123 kernel, then SuperSu. Same issue. No binaries. I can only conclude that installing the kernel causes the issue. Hope this helps someone who has the same problem. Gonna stick to stock kernel for now
ieldra said:
Alright, so SuperSu WORKED. Until I flashed the faux123 kernel, at which point it stopped working again. Same issue, no binaries. So I reformatted the whole phone, installed Rom, then faux123 kernel, then SuperSu. Same issue. No binaries. I can only conclude that installing the kernel causes the issue. Hope this helps someone who has the same problem. Gonna stick to stock kernel for now
Click to expand...
Click to collapse
That's odd. Are you sure you're flashing the right kernel? I had no such problems with the 4.3 version of ElementalX.
iElvis said:
That's odd. Are you sure you're flashing the right kernel? I had no such problems with the 4.3 version of ElementalX.
Click to expand...
Click to collapse
Pretty sure I am, "m7-faux123-Sense43-007m.zip" and "faux123-jb43-sense-camera-fix.zip". Did you have to root again after installing ElemntalX ? Just finished reinstalling ROM for fourth time today, going to check SuperSu works, go back to recovery, make a nandroid backup and perhaps try ElementalX Is there a kernel control app for it ?
ieldra said:
Pretty sure I am, "m7-faux123-Sense43-007m.zip" and "faux123-jb43-sense-camera-fix.zip". Did you have to root again after installing ElemntalX ? Just finished reinstalling ROM for fourth time today, going to check SuperSu works, go back to recovery, make a nandroid backup and perhaps try ElementalX Is there a kernel control app for it ?
Click to expand...
Click to collapse
I only had to flash SuperSU once. I use TricksterMod.
I've experienced this problem on two different ROMs (different variations of the same problem, actually). In both cases, flashing the same SuperSU .zip fixed it. Link here.
iElvis said:
That's odd. Are you sure you're flashing the right kernel? I had no such problems with the 4.3 version of ElementalX.
Click to expand...
Click to collapse
Dude,
Thank you so much for you post, been wondering is this problem bothering me since i saw you post so i tested it out, end up the rom was fine till i flash the faux123 kernal and camera fix, and binary not install issue come out again.
for people who having same problem, this might be the issue
Cheer
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:
Hi, sorry if this is in the wrong place, XDA won't let me post to the mahdi thread because I'm new.
I clean flashed the 6/28 Mahdi Rom for my Vs980 and audio didn't work whatsoever. Everything else was fine. Here are a couple of examples of what I mean:
Poweramp play button will be clickable but will return an error and revert to the play button
Youtube will constantly prepare to play (load, attemp to play then continue to load again)
Placing phone calls results in a black screen, then call ended screen 20 seconds later
Receiving phone calls don't show up, rings once (on the phone placing the call not my vs980) then goes to voicemail
Volume up and down doesn't give tones.
Apollo player gives "DSP manager crashed" errors
I tried freezing DSP manager, but that didn't work.
I should also mention I didn't restore using titanium, I tried reflashing 3 or 4 times, and I used the PA 4.4.4 gapps.
I can't find anyone else with this issue, hopefully someone knows what's up.
Thanks for helping if you respond!
Have you tried a different rom? One specifically for our service. I know Mahdi is compatible, but just to see.
Sent from my VS980 4G using XDA Premium 4 mobile app
[removed reply, see below]
njstein said:
Have you tried a different rom? One specifically for our service. I know Mahdi is compatible, but just to see.
Click to expand...
Click to collapse
Yes I have, I'm currently running a 4.4.2 build of Mahdi that works fine (2.4-g2-20140211). It's just the 6/25 and 6/28 that have the audio issues for me.
Nextcue said:
Yes I have, I'm currently running a 4.4.2 build of Mahdi that works fine (2.4-g2-20140211). It's just the 6/25 and 6/28 that have the audio issues for me.
Click to expand...
Click to collapse
Huh, that's weird. You probably can't post in that for trouble shooting, so have you tried a different gapps? Maybe PA is doing something? Banks gapps is an excellent package (just keep the convo going so you can hit 10 posts).
Here's a link to Banks:
http://forum.xda-developers.com/showthread.php?t=2012857
Sent from my VS980 4G using XDA Premium 4 mobile app
njstein said:
Huh, that's weird. You probably can't post in that for trouble shooting, so have you tried a different gapps? Maybe PA is doing something? Banks gapps is an excellent package (just keep the convo going so you can hit 10 posts).
Click to expand...
Click to collapse
Hmm, I'll check that out when I get a chance. Thanks so much for replying
Nextcue said:
Hmm, I'll check that out when I get a chance. Thanks so much for replying
Click to expand...
Click to collapse
I guess you are on the stock unmodded Kit Kat modem right?
JRJ442 said:
I guess you are on the stock unmodded Kit Kat modem right?
Click to expand...
Click to collapse
Maybe, how would I find out? When I first rooted I flashed Mahdi over 24a I think.
Nextcue said:
Maybe, how would I find out? When I first rooted I flashed Mahdi over 24a I think.
Click to expand...
Click to collapse
How did you get to 24A? If it was from an OTA its the stock modem. Post a picture of your baseband if you can
JRJ442 said:
How did you get to 24A? If it was from an OTA its the stock modem.
Click to expand...
Click to collapse
It was the OTA, so yes it is the stock modem.
Nextcue said:
It was the OTA, so yes it is the stock modem.
Click to expand...
Click to collapse
The current build you're on where everything works shouldn't even boot if you're on 24A. As old as that build is(2.4), its still using the JB kernel, requiring the 12b radio. I think you should go to the Malladus thread, download his baseband updater, and the ROM. And flash that. It should straighten out whatever happened. Some sound drivers are tied in with the modem/baseband for some reason on KK. That's what makes me think something with the baseband is messed up. I think I have the Malladus stuff in my Dropbox if you want links. After you get a good GPS lock in maps with Malladus. Then flash the newest build of Mahdi, not the 2.4 build you're running.
JRJ442 said:
The current build you're on where everything works shouldn't even boot if you're on 24A. As old as that build is(2.4), its still using the JB kernel, requiring the 12b radio. I think you should go to the Malladus thread, download his baseband updater, and the ROM. And flash that. It should straighten out whatever happened. Some sound drivers are tied in with the modem/baseband for some reason on KK. That's what makes me think something with the baseband is messed up. I think I have the Malladus stuff in my Dropbox if you want links. After you get a good GPS lock in maps with Malladus. Then flash the newest build of Mahdi, not the 2.4 build you're running.
Click to expand...
Click to collapse
Thank you so much, links would be very appreciated.
JRJ442 said:
The current build you're on where everything works shouldn't even boot if you're on 24A. As old as that build is(2.4), its still using the JB kernel, requiring the 12b radio.
Click to expand...
Click to collapse
Also I just checked, definitely still on the 12b radio.
Nextcue said:
Thank you so much, links would be very appreciated.
Click to expand...
Click to collapse
First question, are you using TWRP? The wipe instructions below are for TWRP
Here's the ROM https://copy.com/PDixihCzNxqLSBp
Here's the baseband updater https://copy.com/mVY1Qi2cVg3EgXS and the md5 is 941f657383ab5a6ddc8c6f4c0ee4183c make sure t matches before you flash.
Reboot to recovery and flash the baseband updater. Then hit the back button. Select wipe -> advanced wipe. Select dalvik, cache, system, data. Be absolutely sure you don't select internal. Flash Malladus and whatever gapps you prefer.
JRJ442 said:
First question, are you using TWRP? The wipe instructions below are for TWRP
Reboot to recovery and flash the baseband updater. Then hit the back button. Select wipe -> advanced wipe. Select dalvik, cache, system, data. Be absolutely sure you don't select internal. Flash Malladus and whatever gapps you prefer.
Click to expand...
Click to collapse
I am using TWRP. So after I follow your steps, go into the malladus rom and check the gps, then do I flash the latest Mahdi?
Nextcue said:
I am using TWRP. So after I follow your steps, go into the malladus rom and check the gps, then do I flash the latest Mahdi?
Click to expand...
Click to collapse
Yes, actually download maps and ensure it get a GPS lock on you. Then reboot to recovery, go to advanced wipe and select dalvik, cache, system, and data. Then flash the newest mahdi and the newest patch. The ROM is 6-28 and the patch is V6 I believe. Then gapps. You should be good to go then.
JRJ442 said:
Yes, actually download maps and ensure it get a GPS lock on you. Then reboot to recovery, go to advanced wipe and select dalvik, cache, system, and data. Then flash the newest mahdi and the newest patch. The ROM is 6-28 and the patch is V6 I believe. Then gapps. You should be good to go then.
Click to expand...
Click to collapse
Thank you so much, really, I appreciate all of your help!
Nextcue said:
Thank you so much, really, I appreciate all of your help!
Click to expand...
Click to collapse
No problem. Report back too please. And definitely make sure the md5 matches on your download for that baseband updater. That's super important
JRJ442 said:
No problem. Report back too please. And definitely make sure the md5 matches on your download for that baseband updater. That's super important
Click to expand...
Click to collapse
Will absolutely report back. I will be testing it later tonight.Just in case though: What do I do in the event I do not get a gps lock on maps?
Nextcue said:
Will absolutely report back. I will be testing it later tonight.Just in case though: What do I do in the event I do not get a gps lock on maps?
Click to expand...
Click to collapse
You'll get one. No need to worry about not getting one. You just have to do it because sometimes coming from 12B JB source, the sensors won't calibrate correctly on a ROM with true KK source. But I'm not really sure what you could do if you don't to be honest. You should get a lock fairly quick though. Just make sure location is on high accuracy and it will lock
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.