Trying to root my Nexus 6 with Marshmallow
I installed the modified boot from Chainfire using fastboot, it succeeded, then restarted bootloader, then installed TWRP 2.8.7.1, it succeeded, then booted to TWRP and installed the 2.52 beta of SuperSU and restarted and the phone is saying the 'device is corrupted', gives me some crap URL (g.co/ABH) and doesn't start, is there any way to fix this?
Edit: sort of fixed by using Despair Kernel, however, isn't there a way to do this without installing a custom kernel?
wrsg said:
Trying to root my Nexus 6 with Marshmallow
I installed the modified boot from Chainfire using fastboot, it succeeded, then restarted bootloader, then installed TWRP 2.8.7.1, it succeeded, then booted to TWRP and installed the 2.52 beta of SuperSU and restarted and the phone is saying the 'device is corrupted', gives me some crap URL (g.co/ABH) and doesn't start, is there any way to fix this?
Edit: sort of fixed by using Despair Kernel, however, isn't there a way to do this without installing a custom kernel?
Click to expand...
Click to collapse
yea, you just ignore the message, press a button, and let it boot. it has NOTHING to do with root being broken. its a message that appears, using the stock kernel, if you have unlocked your bootloader. next time dont freak out, lol :silly:
Well if that had worked I would have not said I already tried doing that...
wrsg said:
Well if that had worked I would have not said I already tried doing that...
Click to expand...
Click to collapse
then you are the only one that it did not boot up afterwards.
simms22 said:
then you are the only one that it did not boot up afterwards.
Click to expand...
Click to collapse
It has happened to someone else. If you touch the system partition at all with the stock kernel you will get the warning. Only way is a modified kernel (or boot?). You can use a stock kernel that has a small mod to remove the message.
I switched to the vortex kernel mm beta and am very happy with it. No problems at all and way more responsive.
johnciaccio said:
It has happened to someone else. If you touch the system partition at all with the stock kernel you will get the warning. Only way is a modified kernel (or boot?). You can use a stock kernel that has a small mod to remove the message.
I switched to the vortex kernel mm beta and am very happy with it. No problems at all and way more responsive.
Click to expand...
Click to collapse
using despair/elementalx myself
johnciaccio said:
It has happened to someone else. If you touch the system partition at all with the stock kernel you will get the warning. Only way is a modified kernel (or boot?). You can use a stock kernel that has a small mod to remove the message.
I switched to the vortex kernel mm beta and am very happy with it. No problems at all and way more responsive.
Click to expand...
Click to collapse
We are talking about two different things: one is the red triangle, and the other is shutting down if rooted.
In this case pressing the power key while showing the triangle is what turns the phone off. It is so if somebody else tampered with your phone to stop it from booting and messing with your stuff.
On the other hand, stopping if rooted can be avoided if you have a custom kernel with all SELinux turned off, or using Chainfires boot.img that dabbles with the security settings so the kernel is satisfied and boots. You will have the red triangle, just let it boot.
And if the red triangle troubles you then by using a modified ramdisk, it can be switched off.
Related
Okay guys so I just rooted my att note 3 that was completely up to date using the towelroot.com method found here. Stupidly of me I was trying to follow a thread to change my system language in build.prop but after doing that It ONLY boots to recovery / safestrap. After the safestrap screen I tell it to continue to boot normaly and all i get after that is a black screen.
Any ideas? Is it possible to flash safestrap from odin / heimdall / recovery?
Ive tried factory resetting from safestrap and recovery and that didn't change anything.
I not even sure I have safestrap at this point I can get into recovery, and download mode but it sits at the "Samsung Galaxy NOTE 3 [Unlocked Icon] Custom" screen. It wont actually progress to the safestrap.
Before I tried to edit that build.prop the root / safestrap worked fine all day today, restarted several times for different reasons and still worked afterwards.
I had no encryption enabled.
Via recovery -
"Android system recovery <3e>
KOT49H.N900AUCUCNC2"
**** This Worked ****
Possibly? this as a fix?
Would this be okay to use as a stock Kitkat firmware resource for an Odin flash?
Anyone have a N900AUCUCNC2 ROM or firmware I can flash?
BLMaros said:
Anyone have a N900AUCUCNC2 ROM or firmware I can flash?
Click to expand...
Click to collapse
i have the .zip files for it and odin 3
*it sounds to me like a bootloop or a softbrick, I would recommend using this odin 3 and flash the stock kk rom the one i have is the unofficial and is pre-rooted. but it works when i bricked mine repeatedly trying roms.
farmerj said:
i have the .zip files for it and odin 3
*it sounds to me like a bootloop or a softbrick, I would recommend using this odin 3 and flash the stock kk rom the one i have is the unofficial and is pre-rooted. but it works when i bricked mine repeatedly trying roms.
Click to expand...
Click to collapse
That'd be awesome if you could get that to me some how. I more or less have everything fixed but the wake-up after entering my pattern lock is ungodly slow so I'd like to possibly try a different one.
BLMaros said:
That'd be awesome if you could get that to me some how. I more or less have everything fixed but the wake-up after entering my pattern lock is ungodly slow so I'd like to possibly try a different one.
Click to expand...
Click to collapse
I am assuming you know how to use odin.
https://www.dropbox.com/s/2hl1s7pvf5jatbm/NC2_Bootloader_N900AUCECMLG_VER_2.zip
hope this helps. let me know
farmerj said:
I am assuming you know how to use odin.
https://www.dropbox.com/s/2hl1s7pvf5jatbm/NC2_Bootloader_N900AUCECMLG_VER_2.zip
hope this helps. let me know
Click to expand...
Click to collapse
I do, this is perfect thank you!
Did it work?
Sent from Awesome Note 3 At&t
running Purerom CE.
SU Binary needs to be updated on my phone - it's causing my phone to boot up, run for about 30 seconds, and then reboot over and over again.
How can I update the binary? I go to Superuser and it gives me the option to, but the phone reboots before I get the chance to update it.
I found the file I need to flash, but how can I get it onto my phone? The phone doesn't stay on long enough for me to transfer the file onto the phone...
PLEASE HELP!!
Sounds like you flashed a GSm rom that is not compatible with Sprint.
BD619 said:
Sounds like you flashed a GSm rom that is not compatible with Sprint.
Click to expand...
Click to collapse
Forgot to mention that I haven't flashed any ROM's - I rooted just so I could access mobile hotspot for free and what not.
Anyway, I actually ended up fixing it. Was able to get into SU and it posted the update file to my phone and I accessed it via recovery. Flashed it and the problem is fixed.
saj1jr said:
Forgot to mention that I haven't flashed any ROM's - I rooted just so I could access mobile hotspot for free and what not.
Anyway, I actually ended up fixing it. Was able to get into SU and it posted the update file to my phone and I accessed it via recovery. Flashed it and the problem is fixed.
Click to expand...
Click to collapse
thanks for the tip, i'm going to give this a try. something is throwing my phone into boot loops today too, I just unfroze all the stuff I froze with TB this week thinking that was the trouble.... I am on stock/rooted 4.4.2 with SU as well.
Update:
Booted to recovery, used adb to push the new Su binary (v2.00) over to phone, used custom recovery to install new su binary zip, all seems right with the world. will post again if I have troubles, but this appears to be working *crosses fingers*
I've got no idea what started this boot loop off today, maybe some OTA tweak I didn't approve? Not really sure...
bobsbobbers said:
thanks for the tip, i'm going to give this a try. something is throwing my phone into boot loops today too, I just unfroze all the stuff I froze with TB this week thinking that was the trouble.... I am on stock/rooted 4.4.2 with SU as well.
Update:
Booted to recovery, used adb to push the new Su binary (v2.00) over to phone, used custom recovery to install new su binary zip, all seems right with the world. will post again if I have troubles, but this appears to be working *crosses fingers*
I've got no idea what started this boot loop off today, maybe some OTA tweak I didn't approve? Not really sure...
Click to expand...
Click to collapse
hey man. same issue. i just tried the latest update. seems to work for now, but did the problem ever come back for you?
Hi, hoping I haven't done something terrible here.
Rooted Sprint Note 4. Stock other than that, including bootloader
Installed Xposed Installer
then RootCloak module
Xposed Installer: Install->Update
Rebooted directly into a never-ending boot loop (Samsung logo, Sprint logo, reboot).
I was able to get it into recovery once, using a little sh script, but it's not working anymore.
When I was able to get it into recovery, I figured I'd try doing a factory reset, to no avail. Same loop.
I just tried repeatedly pressing a hardware button during boot to disable xposed, no result.
I have the disable .zip file, but no way to push it to the device or flash it, since I can't get into recovery - and even then, it seems I need a custom bootloader to do run it.
I did take an adb backup.
Now, I can only get to the stock Download screen (by holding hardware keys during boot).
Any help? Please?
I'm thinking of flashing this with Odin:
http://forum.xda-developers.com/not...-nie-stockish-knox-root-sprint-stock-t2919346
Hoping that is a reasonable thing to try?
Sigh of relief
OK, I fixed it.. I just redid the same process I did when I first rooted - using cf-auto-root.
And boom! Booted back to stock :victory:
Same issue
blackshawarma said:
ok, i fixed it.. I just redid the same process i did when i first rooted - using cf-auto-root.
And boom! Booted back to stock :victory:
Click to expand...
Click to collapse
having the same issue can fig how fix it?
xcrippleddemonx said:
having the same issue can fig how fix it?
Click to expand...
Click to collapse
Is you're problem with the new Xposed on Lollipop?
not reall sure
ldeveraux said:
Is you're problem with the new Xposed on Lollipop?
Click to expand...
Click to collapse
um its on xposed i honesty dont know if it was lollipop or not i have the note 4 and only updated the firmware once i cant factory reset all i can do is download mode it must be lollipop because it was the uptodate version of xposed
xcrippleddemonx said:
um its on xposed i honesty dont know if it was lollipop or not i have the note 4 and only updated the firmware once i cant factory reset all i can do is download mode it must be lollipop because it was the uptodate version of xposed
Click to expand...
Click to collapse
The first post in the Xposed thread says not to use it on touchwiz UI. Reflash your ROM in ODIN, and wait for Rovo to update Xposed for your system.
Maybe you should check the first posts before flashing something. Samsung roms aren't supported on lollipop
This is a really old post, and people might have already figured this out- HOWEVER, wanam has made a modded version of xposed 87.1 that is supposedly working on TouchWiz ui. Trying now
So I tried to root and put on a custom recovery using the nexus root toolkit, since I am not very advanced at this type of stuff. But after pushing the root files to my phone from the TWRP recovery I got the message that the device is corrupt. I press the volume down button and power button to continue boot, but then the screen just goes black, and stays that way. Any advice?
pakman5391 said:
So I tried to root and put on a custom recovery using the nexus root toolkit, since I am not very advanced at this type of stuff. But after pushing the root files to my phone from the TWRP recovery I got the message that the device is corrupt. I press the volume down button and power button to continue boot, but then the screen just goes black, and stays that way. Any advice?
Click to expand...
Click to collapse
I got that message before. I fixed it by going back to stock, (the message will still appear even after going back to stock) then in the stock recovery factory reset the device. Then root as usual. I dont know how you're rooting but I flash the factory reset then install the custom reocery then flash super SU beta with a custom kernel and I havent had that pop up
xxxrichievxxx said:
I got that message before. I fixed it by going back to stock, (the message will still appear even after going back to stock) then in the stock recovery factory reset the device. Then root as usual. I dont know how you're rooting but I flash the factory reset then install the custom reocery then flash super SU beta with a custom kernel and I havent had that pop up
Click to expand...
Click to collapse
I think they key is the custom kernel. I was doing the stock kernel and kept getting the black screen. I will try doing a kernel that is friendly with 6.0.
Thanks for the advice, I will try to flash the stock recovery and factory reset the phone.
pakman5391 said:
I think they key is the custom kernel. I was doing the stock kernel and kept getting the black screen. I will try doing a kernel that is friendly with 6.0.
Thanks for the advice, I will try to flash the stock recovery and factory reset the phone.
Click to expand...
Click to collapse
Maybe i just downloaded it last night and started to tinker with it
Im using Benzocore at the moment, I was using Hells-kernel on Lolipop but it seems like Benzo works 100% with Marsh. I tried another kernel that says thatll work with marshmallow but it ended up in bootloop.
xxxrichievxxx said:
Maybe i just downloaded it last night and started to tinker with it
Im using Benzocore at the moment, I was using Hells-kernel on Lolipop but it seems like Benzo works 100% with Marsh. I tried another kernel that says thatll work with marshmallow but it ended up in bootloop.
Click to expand...
Click to collapse
Hellscore B7 works with MM 100%. Running it right now while rooted and using Layers. So I can vouch for Hells at least.
this fixes that message:
http://forum.xda-developers.com/nexus-6/development/kernel-stock-kernel-root-color-control-t3218958
kronikings said:
this fixes that message:
http://forum.xda-developers.com/nexus-6/development/kernel-stock-kernel-root-color-control-t3218958
Click to expand...
Click to collapse
That did make the message go away, and the black screen too! Thank you so much!
Now to re-try hellscore kernel.
Peylix said:
Hellscore B7 works with MM 100%. Running it right now while rooted and using Layers. So I can vouch for Hells at least.
Click to expand...
Click to collapse
If b7 works, then b8 should work no?
pakman5391 said:
If b7 works, then b8 should work no?
Click to expand...
Click to collapse
It appears so, it was posted just a few hours ago under their Nexus 6 section. I can't comment directly on B8 but I'm downloading to flash now.
Peylix said:
Hellscore B7 works with MM 100%. Running it right now while rooted and using Layers. So I can vouch for Hells at least.
Click to expand...
Click to collapse
Can you link me to the kernel version? I tried the latest one and that one bootlooped lol Thank you
xxxrichievxxx said:
Can you link me to the kernel version? I tried the latest one and that one bootlooped lol Thank you
Click to expand...
Click to collapse
Sure!
b7-m is here
b8-m is here
Also, on the b8. To not get the bootloop. Follow these instructions.
CHeers!
Are their currently any kernals which support marshmallow now? I installed emotions kernals but the wifi doesn't work and I do not know how to get back to stock kernel.
Thank you
hunter99507 said:
Are their currently any kernals which support marshmallow now? I installed emotions kernals but the wifi doesn't work and I do not know how to get back to stock kernel.
Thank you
Click to expand...
Click to collapse
try flashing dr.ketens data fix in recovery.
funtimez said:
try flashing dr.ketens data fix in recovery.
Click to expand...
Click to collapse
Using an N910t3 I flashed emotion MM rc25 , confirmed wifi didn't work, tried the data fix it put me in a bootloop, luckily I had made a complete backup in TWRP and restored it already, just want to warn anyone else before they try it.
You should keep A backup of the original the "boot" partition in twrp. In TWRP>Backup>select "boot" only. That keeps the stock kernel.
I haven't tested any alternative kernels personally.
I feel that the stock MM kernel is doing great.
MM works fine. I'm waiting for MM kernel
I had a few problems with Marshmallow but finally installed the latest PG2. My phone N910T boot looped and caused some problems but eventually I finally had a working 6.0.1 stock. I installed TWRP and SuperSU SYSTEMLESS and used the phone for 2 days.
I tried flashing Beastmode and Emotion kernels but neither worked and I was stuck in a boot loop. Eventually I tried to reinstall stock without a wipe as this always works and keeps my apps etc.
The stock said the md5 checksum was invalid even though it was the same file from 2 days earlier. To fix this I removed the file extension, preventing it from doing the MD5 check and attempted to install. It bricked my phone as the process appeared to stop at halfway and I aborted. I found modem and bootloader files for PG2 and took a shot at installing them. I got to another bootloop.
I tried the stock tarfile again and was a little more patient this time. The previous delay was only a few minutes long. It installed succesfully. I Installed TWRP with ODIN, followed by a systemless root in recovery mode.
I'm currently waiting for MM kernels. I hope my little adventure helps somebody else on their journey.
FungusTB said:
I had a few problems with Marshmallow but finally installed the latest PG2. My phone N910T boot looped and caused some problems but eventually I finally had a working 6.0.1 stock. I installed TWRP and SuperSU SYSTEMLESS and used the phone for 2 days.
I tried flashing Beastmode and Emotion kernels but neither worked and I was stuck in a boot loop. Eventually I tried to reinstall stock without a wipe as this always works and keeps my apps etc.
The stock said the md5 checksum was invalid even though it was the same file from 2 days earlier. To fix this I removed the file extension, preventing it from doing the MD5 check and attempted to install. It bricked my phone as the process appeared to stop at halfway and I aborted. I found modem and bootloader files for PG2 and took a shot at installing them. I got to another bootloop.
I tried the stock tarfile again and was a little more patient this time. The previous delay was only a few minutes long. It installed succesfully. I Installed TWRP with ODIN, followed by a systemless root in recovery mode.
I'm currently waiting for MM kernels. I hope my little adventure helps somebody else on their journey.
Click to expand...
Click to collapse
You're able to flash TWRP and root on stock PG2 for N910T?
thebestiam said:
You're able to flash TWRP and root on stock PG2 for N910T?
Click to expand...
Click to collapse
Yes it works. I'm experiencing battery drain through.
FungusTB said:
Yes it works. I'm experiencing battery drain through.
Click to expand...
Click to collapse
Doesn't it update the bootloader to PG2 from PE3 and it'll still work?
Sent from my GT-I9500 using XDA-Developers mobile app
thebestiam said:
Doesn't it update the bootloader to PG2 from PE3 and it'll still work?
Click to expand...
Click to collapse
I don't know. I've upgraded bootloader in the past without issues. There seems to be issues surrounding mismatched modems and bootloader recently.
FungusTB said:
I don't know. I've upgraded bootloader in the past without issues. There seems to be issues surrounding mismatched modems and bootloader recently.
Click to expand...
Click to collapse
Okay, thanks for the clear up
Sent from my SM-N910T using XDA-Developers mobile app