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.
Related
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
I just got my replacement M8 today.
Went in and rooted it. All went fine. (At least i think it did)
Then installed SU.
Installed CT TWRP version 2.7.1.0 from here
Thats when everything went bad. (By no means am i saying CT's TWRP did something to my phone!)
I am now stuck in a vicious boot loop.
My M8 will boot up to the OS, sit there for a few minutes and then reboot. Over and over.......
I tried downgrading the TWRP version to 2.7.0.8 thinking maybe i had a bad flash. That didnt help at all.
So right now I am rooted with stock ROM and Captains TWRP version 2.7.0.8 stuck in a loop.
Anyone have any idea what is going on here?
ive been doing this for quite a while and by no means am i a N00b. Just dont understand what happened.
jayjam99 said:
I just got my replacement M8 today.
Went in and rooted it. All went fine. (At least i think it did)
Then installed SU.
Installed CT TWRP version 2.7.1.0 from here
Thats when everything went bad. (By no means am i saying CT's TWRP did something to my phone!)
I am now stuck in a vicious boot loop.
My M8 will boot up to the OS, sit there for a few minutes and then reboot. Over and over.......
I tried downgrading the TWRP version to 2.7.0.8 thinking maybe i had a bad flash. That didnt help at all.
So right now I am rooted with stock ROM and Captains TWRP version 2.7.0.8 stuck in a loop.
Anyone have any idea what is going on here?
ive been doing this for quite a while and by no means am i a N00b. Just dont understand what happened.
Click to expand...
Click to collapse
Did you S-OFF?
Did you flash SuperSU?
Captain_Throwback said:
Did you S-OFF?
Did you flash SuperSU?
Click to expand...
Click to collapse
I did not soff yet. Cant keep the phone up long enough to try to get firewater ran.
I did flash SU.
jayjam99 said:
I did not soff yet. Cant keep the phone up long enough to try to get firewater ran.
I did flash SU.
Click to expand...
Click to collapse
Which version of SuperSU?
You could also try TWRP version 2.7.0.7 from my thread. That seems to be the "magical" version.
Captain_Throwback said:
Which version of SuperSU?
You could also try TWRP version 2.7.0.7 from my thread. That seems to be the "magical" version.
Click to expand...
Click to collapse
Version 1.94
Ok, ill give 2.7.0.7 a shot now and let you know.
Thanks for the help CT!
jayjam99 said:
Version 1.94
Ok, ill give 2.7.0.7 a shot now and let you know.
Thanks for the help CT!
Click to expand...
Click to collapse
That's an old version of SuperSU. Try updating to the latest.
Captain_Throwback said:
That's an old version of SuperSU. Try updating to the latest.
Click to expand...
Click to collapse
Looks like it was the outdated version of superSU that i installed.
Updated to 2.00 and all is well again.
Thanks so much for your time and help good sir.
I'm using chroma ROM and my satellite provider requires it's app to run on an unrooted phone. I'd there an easy way to unroot my Nexus without having to wipe?
slekkas said:
I'm using chroma ROM and my satellite provider requires it's app to run on an unrooted phone. I'd there an easy way to unroot my Nexus without having to wipe?
Click to expand...
Click to collapse
Flash the system image from a factory image. If your kernel is modified, flash the boot IMG as well.
Use wugs toolkit.
Evolution_Tech said:
Flash the system image from a factory image. If your kernel is modified, flash the boot IMG as well.
Click to expand...
Click to collapse
So just to get this straight and I don't screw up my phone. I find the stock rom same version as my chroma which is LMY48B. I extract it and using fastboot I install system.img and boot.img? My phone is unencrypted right now... Will it get encrypted?
And when I need root again I must just install it along with Franco Kernel I'm using?
I appreciate the help...
Nickchapstick said:
Use wugs toolkit.
Click to expand...
Click to collapse
I installed it on my laptop but even though my phone is rooted I don't see an option to unroot... Maybe because I didn't use regular rom and used chroma instead?
slekkas said:
So just to get this straight and I don't screw up my phone. I find the stock rom same version as my chroma which is LMY48B. I extract it and using fastboot I install system.img and boot.img? My phone is unencrypted right now... Will it get encrypted?
And when I need root again I must just install it along with Franco Kernel I'm using?
I appreciate the help...
Click to expand...
Click to collapse
First, why are you trying to unroot?
You would download a factory image form the Google developer page. Extract twice, and grab the system image from there. Yes, match the version your phone is currently on.
Evolution_Tech said:
First, why are you trying to unroot?
You would download a factory image form the Google developer page. Extract twice, and grab the system image from there. Yes, match the version your phone is currently on.
Click to expand...
Click to collapse
I'm trying to unroot because my satellite provider uses an app like sky go that requires your phone to be unrooted... I need to watch a game sometimes when I'm at work.
slekkas said:
I'm trying to unroot because my satellite provider uses an app like sky go that requires your phone to be unrooted... I need to watch a game sometimes when I'm at work.
Click to expand...
Click to collapse
Have you considered multi ROM? You could have your rooted normal set up and a non rooted as well.
Can't you just go into supersu settings and unroot? That way you can stay on chroma
Kreateablaze said:
Can't you just go into supersu settings and unroot? That way you can stay on chroma
Click to expand...
Click to collapse
Depends on how deeply his situation is looking for root files. The unroot feature of SuperSU doesn't remove everything.
Evolution_Tech said:
Have you considered multi ROM? You could have your rooted normal set up and a non rooted as well.
Click to expand...
Click to collapse
My friend I didn't know this was possible with the nexus 6. That would really interest me.... I already have twrp installed. Is there an easy guide you can point out for me?
slekkas said:
My friend I didn't know this was possible with the nexus 6. That would really interest me.... I already have twrp installed. Is there an easy guide you can point out for me?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3074529
Evolution_Tech said:
Depends on how deeply his situation is looking for root files. The unroot feature of SuperSU doesn't remove everything.
Click to expand...
Click to collapse
Tried this keeps telling me that I need to unroot. So i'm about to start the multi rom procedure
Evolution_Tech said:
Have you considered multi ROM? You could have your rooted normal set up and a non rooted as well.
Click to expand...
Click to collapse
How about the encryption? Chroma is unencrypted. If the second rom is encrypted what happens there?
I'm also trying to find a stock rom that is not pre-rooted to install from recovery. Can you show me the latest I can get?
Evolution_Tech said:
Have you considered multi ROM? You could have your rooted normal set up and a non rooted as well.
Click to expand...
Click to collapse
My friend I installed multirom and used an older Chroma rom that wasn't pre-rooted. it worked like a charm.... Now I can just go to this rom and use all my apps that require the phone to be unrooted.... Again thanks for the idea....
Can I just ask what version of chroma wasn't pre rooted? I want to do the same if possible. Thanks
Drefsab said:
Can I just ask what version of chroma wasn't pre rooted? I want to do the same if possible. Thanks
Click to expand...
Click to collapse
well, 2 months ago it was being called older.. anyways, the far majority of roms do not have root. you need to flash the supersu file shen flashing the roms, for root. but, to flash a rom, yoh need an unlocked bootloader and twrp recovery. most apps that check for root will still think that you have root though.
simms22 said:
well, 2 months ago it was being called older.. anyways, the far majority of roms do not have root. you need to flash the supersu file shen flashing the roms, for root. but, to flash a rom, yoh need an unlocked bootloader and twrp recovery. most apps that check for root will still think that you have root though.
Click to expand...
Click to collapse
i must have fell asleep during this development lol
far as i have ever seen, its rare for a rom to not be rooted, however, more frequently devs have had it off by default, and its a treasure hunt to find where to turn it on.
i do always flash the su zip, to avoid this tedious hunting though.
bweN diorD said:
i must have fell asleep during this development lol
far as i have ever seen, its rare for a rom to not be rooted, however, more frequently devs have had it off by default, and its a treasure hunt to find where to turn it on.
i do always flash the su zip, to avoid this tedious hunting though.
Click to expand...
Click to collapse
cm based, probably have root. aosp roms, the far majority do mot have root. you need to grab it if you want it
simms22 said:
cm based, probably have root. aosp roms, the far majority do mot have root. you need to grab it if you want it
Click to expand...
Click to collapse
yup I found that most are pre-rooted, though found cleancore that works great. I've just installed multirom and that booted into it then tested a couple of apps that are blocked on root (Banking app and Sky Go), and happy days they work great.
Its annoying and rather wasteful having have a second rom just to run a couple of apps but at least now I can use the apps on my device if I want to. Thanks
Typical apps block hacking (root) so the work around instead of unrooting is to go deeper with the hacks/mods
HI
I´ve rooted my Nexus 6 on MPA44I
1) twrp-2.8.7.1-shamu
2) BETA-SuperSU-v2.49
3) Despair.M.Shamu.R6.4.zip
but i can´t use apps like Adaway , its saying "can´t create /system/etc/hosts: read only file-system"
Root Checker says "got root"
Titanium Backup works
how can i get full Access to stop these anoying ads?
thanks for your help
you need to flash the unencrypted img before flashing Despair. and fwiw the order i use is: unencrypted img, then the kernel, then SU
cmh714 said:
you need to flash the unencrypted img before flashing Despair. and fwiw the order i use is: unencrypted img, then the kernel, then SU
Click to expand...
Click to collapse
funny, i am on preview 3, didnt flash the unencrypted img, but despair kernel, and i have full root access, including write.
Just flashed Preview 3. Could you guys please add a few links and maybe a little bit more detailed description? Thanks!
f2 said:
Just flashed Preview 3. Could you guys please add a few links and maybe a little bit more detailed description? Thanks!
Click to expand...
Click to collapse
try a different radio until you find one that you like, they all work.
and you do not have to flash an unencrypted boot.img before flashing despair.
simms22 said:
try a different radio until you find one that you like, they all work.
and you do not have to flash an unencrypted boot.img before flashing despair.
Click to expand...
Click to collapse
Thanks, I decided to use a JDX rom instead. That one was pretty much stock but pre-rooted...
f2 said:
Thanks, I decided to use a JDX rom instead. That one was pretty much stock but pre-rooted...
Click to expand...
Click to collapse
cool, thats what im using
Ok, so im running MOAR 7.0 on my SGS5 and i have the alpha installer and several SDK 21 zips and all of them make the phone get stuck on the bootanimation. It never reboots, so not technically a bootloop, but itll never boot after flashing any of the zips. Ive even gone so far as to try SDK 22 and 23 versions, no dice. Itll only boot after running the uninstall sip file. Any thoughts?
youdoofus said:
Ok, so im running MOAR 7.0 on my SGS5 and i have the alpha installer and several SDK 21 zips and all of them make the phone get stuck on the bootanimation. It never reboots, so not technically a bootloop, but itll never boot after flashing any of the zips. Ive even gone so far as to try SDK 22 and 23 versions, no dice. Itll only boot after running the uninstall sip file. Any thoughts?
Click to expand...
Click to collapse
I don't know what version android your rom is, or if you're unlocked bootloader, or how you flashed the zip, what zip you flashed, what apk you installed...
Try providing information so people can help
ldeveraux said:
I don't know what version android your rom is, or if you're unlocked bootloader, or how you flashed the zip, what zip you flashed, what apk you installed...
Try providing information so people can help
Click to expand...
Click to collapse
my bad. Its 5.0, its unlocked, running OK4 bootloader, flashed it via twrp 3.0.2-1, i flashed xposed-v67-sdk21-arm.zip, xposed-v80-sdk21-arm.zip and xposed-v84-sdk21-arm.zip. All of those zips ive tried individually flashing them all and they all did the same thing. Just the boot animation until i flash the uninstaller zip, then it boots normally. I should add that im wiping the caches when flashing the installer zips and waiting an appropriate length of time to see the "starting app ### of ###" screen to appear. Im quite familiar with how long it takes to get to that screen after flashing stuff.
Thanks for replying and for the help!!
youdoofus said:
my bad. Its 5.0, its unlocked, running OK4 bootloader, flashed it via twrp 3.0.2-1, i flashed xposed-v67-sdk21-arm.zip, xposed-v80-sdk21-arm.zip and xposed-v84-sdk21-arm.zip. All of those zips ive tried individually flashing them all and they all did the same thing. Just the boot animation until i flash the uninstaller zip, then it boots normally. I should add that im wiping the caches when flashing the installer zips and waiting an appropriate length of time to see the "starting app ### of ###" screen to appear. Im quite familiar with how long it takes to get to that screen after flashing stuff.
Thanks for replying and for the help!!
Click to expand...
Click to collapse
Stop clearing each time, completely unnecessary. Are you using the correct zip file? Touchwiz based roms require a special zip to flash, not just that released by rovo, you know?
ldeveraux said:
Stop clearing each time, completely unnecessary. Are you using the correct zip file? Touchwiz based roms require a special zip to flash, not just that released by rovo, you know?
Click to expand...
Click to collapse
I didn't think it was necessary, but I figured it couldn't hurt. Would you happen to know which zip I'd need for a tw 5.0 ROM?
Sent from my SM-G900P using XDA Free mobile app
youdoofus said:
I didn't think it was necessary, but I figured it couldn't hurt. Would you happen to know which zip I'd need for a tw 5.0 ROM?
Sent from my SM-G900P using XDA Free mobile app
Click to expand...
Click to collapse
It's from arter97's thread, it says unofficial.
ldeveraux said:
It's from arter97's thread, it says unofficial.
Click to expand...
Click to collapse
Yep, found it last night actually
Sent from my SM-G900P using XDA Free mobile app
youdoofus said:
Yep, found it last night actually
Sent from my SM-G900P using XDA Free mobile app
Click to expand...
Click to collapse
Did you have any luck with arters build on MOAR 7? All I got was endless system ui has stopped responding. Blah blah has stopped responding. Blah 3, Etc. Millions of clicking to close loops.
mordantly said:
Did you have any luck with arters build on MOAR 7? All I got was endless system ui has stopped responding. Blah blah has stopped responding. Blah 3, Etc. Millions of clicking to close loops.
Click to expand...
Click to collapse
i found that this happens when you flash the wrong version. i did get it to work, but i gave up on it after reflashing MOAR several times after trying other roms. I just dont see any use for myself personally for xposed
I was just turned on to two versions for SDK21 (MOAR). Will be returning to MOAR and testing them out.
V85
http://forum.xda-developers.com/showpost.php?p=68550646&postcount=5292
V86
http://forum.xda-developers.com/showpost.php?p=65373013&postcount=3960