I'm picking up a Nexus 6P this week, would like to try out the latest Android N DP #4, but I always like to have Root on my phone, mainly for ad blocking and custom Kernels. So my phone will be brand new, should I just try out the Developer Preview before I do the whole Root and TWRP thing ? And then after that root it and install custom Recovery ?
I just didn't know if there were custom ROM's based off the Developer Previews ? Or at least Root available while running the N preview ?
You can have root and twrp on N dp4
Zorachus said:
I'm picking up a Nexus 6P this week, would like to try out the latest Android N DP #4, but I always like to have Root on my phone, mainly for ad blocking and custom Kernels. So my phone will be brand new, should I just try out the Developer Preview before I do the whole Root and TWRP thing ? And then after that root it and install custom Recovery ?
I just didn't know if there were custom ROM's based off the Developer Previews ? Or at least Root available while running the N preview ?
Click to expand...
Click to collapse
Here you go mate n rom do all the normal wipes might have to flash vendor for n https://www.androidfilehost.com/?fid=24572369242686616
jaythenut said:
Here you go mate n rom do all the normal wipes might have to flash vendor for n https://www.androidfilehost.com/?fid=24572369242686616
Click to expand...
Click to collapse
Thanks, but right now I'm just running stock, haven't unlocked bootloader or anything yet, but I did enroll for the N beta, which I'm on right now.
Question, if I want to unlock bootloader now, and root, etc... Do I have to revert back to Marshmallow first ?
Zorachus said:
Thanks, but right now I'm just running stock, haven't unlocked bootloader or anything yet, but I did enroll for the N beta, which I'm on right now.
Question, if I want to unlock bootloader now, and root, etc... Do I have to revert back to Marshmallow first ?
Click to expand...
Click to collapse
No all can be done on n unlock boot will wipe the phone then fastboot modified boot.Img that will decrypt the phone then twrp then flash SuperSU in twrp that should do it
PLEASE HELP:
Ok need a little help, I am following the excellent video by Rootjunky ( thank you ), and got through the unlocked bootloader part easily, and now installed TWRP Recovery, but upon first time booting into TWRP, it's just sitting at the Blue and Gray teamwin screen, and not doing anything else, it's not actually entering into the Recovery, to see the list of options, etc...
I powered the device down, and started up again in Fastboot mode, then chose Recovery, and does the same again, just sits at the blue gray colored teamwin screen, and does nothing.
What happened ?
UPDATE:
I powered the device down / off. Then started up again, it went and booted up, to the fresh clean Android N DP 4. But I am not rooted at all yet, due not being able to fully enter Recovery and flash the SuperSU zip yet.
Related
I was running 4.4.3 Rooted with TWRP recovery. Bootloader was unlocked.
I accepted the 4.4.4 OTA update and when it was done I found I lost root.
Tried to go into recovery to install Supersu.zip but had also lost TWRP.
Just got the dead android with the ! mark.
My Boot loader is still unlocked. I ran fastboot. Verified that I got a device id with Fastboot devices.
Then used Fastboot to install openrecovery-twrp-2.6.3.1-manta.img
Completed with no errors. Rebooted the device and then shut it down.
Rebooted into Fastboot, selected recovery and I still get the dead Android with the ! mark.
What did I do wrong?
Len
If you want to stay stock here you go. Look at the last page or so and it also has a link to the newest TWRP which you need to get going again.
http://forum.xda-developers.com/showthread.php?t=2529492
sfobrien said:
If you want to stay stock here you go. Look at the last page or so and it also has a link to the newest TWRP which you need to get going again.
http://forum.xda-developers.com/showthread.php?t=2529492
Click to expand...
Click to collapse
No, I don't want to stay stock. I want to be able to install TWRP so I can flash SuperSu.zip and get root back. When I do a fast boot install of the TWRP Image, it completes with no errors but when I reboot into recovery, I get the dead Android with the exclamation point not TWRP
Lenster45 said:
No, I don't want to stay stock. I want to be able to install TWRP so I can flash SuperSu.zip and get root back. When I do a fast boot install of the TWRP Image, it completes with no errors but when I reboot into recovery, I get the dead Android with the exclamation point not TWRP
Click to expand...
Click to collapse
Since you took the OTA your bootloader may be locked. After you get it unlocked I gave you where to get the recovery you need, the one you have is not KitKat friendly.
Lenster45 said:
I was running 4.4.3 Rooted with TWRP recovery. Bootloader was unlocked.
I accepted the 4.4.4 OTA update and when it was done I found I lost root.
Tried to go into recovery to install Supersu.zip but had also lost TWRP.
Just got the dead android with the ! mark.
My Boot loader is still unlocked. I ran fastboot. Verified that I got a device id with Fastboot devices.
Then used Fastboot to install openrecovery-twrp-2.6.3.1-manta.img
Completed with no errors. Rebooted the device and then shut it down.
Rebooted into Fastboot, selected recovery and I still get the dead Android with the ! mark.
What did I do wrong?
Len
Click to expand...
Click to collapse
Well, you didn't do anything wrong per se. When you flash the OTA (which I assume you did in TWRP), you lose root and your custom recovery since it replaces it with stock. You did the right thing by fastboot flashing your custom recovery back. However, the only thing you did "wrong" was rebooting into the Android OS instead of booting into the newly flashed recovery first. After you flash the custom recovery, select the recovery option in the bootloader, and it will boot into your custom recovery. If you don't boot directly into your custom recovery, and instead boot into the OS, the recovery will revert back to stock, which is why you saw the dead Android with the ! mark (that is the stock recovery). Just fastboot flash TWRP again, and boot straight into it. Then, just flash the SuperSU zip and reboot system. You should be good to go.
EDIT: Oh, and having an unlocked bootloader has no effect on receiving an OTA or your ability to flash it. If your bootloader was unlocked before flashing an OTA, it will remain unlocked. The only way it would become locked again is if you locked it yourself. You can even completely flash the stock image, and the bootloader will remain unlocked.
charesa39;53763629
EDIT: Oh said:
Strange, had a friend who took the OTA awhile back and it locked the bootloader. It was a JB version maybe they changed it with KitKat ? ( he could have locked it prior to my getting it going who knows) Thanks for the info, have never used an OTA since I got my N10 when it first came out.
Click to expand...
Click to collapse
charesa39 said:
Well, you didn't do anything wrong per se. When you flash the OTA (which I assume you did in TWRP), you lose root and your custom recovery since it replaces it with stock. You did the right thing by fastboot flashing your custom recovery back. However, the only thing you did "wrong" was rebooting into the Android OS instead of booting into the newly flashed recovery first. After you flash the custom recovery, select the recovery option in the bootloader, and it will boot into your custom recovery. If you don't boot directly into your custom recovery, and instead boot into the OS, the recovery will revert back to stock, which is why you saw the dead Android with the ! mark (that is the stock recovery). Just fastboot flash TWRP again, and boot straight into it. Then, just flash the SuperSU zip and reboot system. You should be good to go.
EDIT: Oh, and having an unlocked bootloader has no effect on receiving an OTA or your ability to flash it. If your bootloader was unlocked before flashing an OTA, it will remain unlocked. The only way it would become locked again is if you locked it yourself. You can even completely flash the stock image, and the bootloader will remain unlocked.
Click to expand...
Click to collapse
That did it. Thanks
Hi,
Could you add a [SOLVED] tag to the title, as it is now solved ?
~Lord
"Dream On! Dream Until Your Dreams Come True!" - Dream On (Aerosmith)
Sent from my GT-I9505
Hi I am using the windroid toolkit trying to root my new x pure. I got thru the first two steps ok, with a message thats its ok to move on to step 3, root access by flashing superuser.... everytime I try to flash super user I get a message that the phone is in the wrong state? I am still in the fastboot mode, start option. Is that correct? I tried rebooting the phone into the recovery mode by selecting the power and up volume keys, but that did not work? Im confused.......If I got by the 2nd step, should team win be in the recovery? thanks for any ideas here......
Why do you need a toolkit to root?
update,,,, the toolkit was on youtube and looked like an easy way to go thru the unlock, install recovery, root process. It worked fine and fast for the first two sections. I have an unlocked bootloader and teamwin recovery. I went to a different video that showed how to flash superuser into the recovery. I did that and now the phone is stuck on the Android M bootup screen. I am able to boot into the fastboot flash mode and teamwin recovery, so Im not completely bricked. Just stuck on the boot screen. Turns out the flashing superuser method does not work on Marshmellow... Anyone know how to fix this?
Did a bunch of searching and after a very long night I was able to return to stock, 5.1.1. Phone is back to normal and rooted. Lots of info here....just need to find it.....
Garyalp said:
Did a bunch of searching and after a very long night I was able to return to stock, 5.1.1. Phone is back to normal and rooted. Lots of info here....just need to find it.....
Click to expand...
Click to collapse
You can update to Android M 6.0 and then you should flash SuperSU 2.62-3 through TWRP to gain root, after rooting with this version or SuperSU, you should be able to update to a new version of SuperSU, I have update to SuperSu 2.65 with no issue. This was the easiest way that I have found to root our phone running Android M 6.0.
Thank you for that information. Wish I had it from the beginning, would have saved a bunch of trouble. Turns out I spoke to soon. I am having the wi fi issue that some have had. I have gone from a stock 5.1.1 to 6.0, unlocked bootloader, teamwin recovery, soft brick, back to 5.1.1, now rooted. Not sure exactly where the phone is. The bootloader remained unlocked thru the reflash to stock 5.1.1. I noticed that the mac address and Ip address are both, "unavailable", when I go to: settings/wifi/ advanced. Most likely the reason wifi is inop. Is there a way to find the mac and Ip address? Which modem should I be on, now that Im 5.1.1? Will a factory reset bring them back or does that just clear user data? As you can tell I know just enough to be dangerous....lol.
mcx6 said:
You can update to Android M 6.0 and then you should flash SuperSU 2.62-3 through TWRP to gain root, after rooting with this version or SuperSU, you should be able to update to a new version of SuperSU, I have update to SuperSu 2.65 with no issue. This was the easiest way that I have found to root our phone running Android M 6.0.
Click to expand...
Click to collapse
exactly what I did, works great.
I like swapping between new ROM's, and I've been on Android N since the first preview. But now I'm interested in trying out Paranoid.
The bootloader is unlocked and I have just reflashed TWRP. But it asked for a password in the start which I got passed where I wiped everything on it. But whenever I try to boot into any rom (not just Paranoid) it's just stuck on the Google logo. Why so?
Will I need to downgrade my bootloader to the version from Marshmallow or am I missing something?
I'll give the default answer to any ROM issues you ever have on a Nexus device. Reflash the FULL stock factory image and see if it fixes it.
andreglud said:
I like swapping between new ROM's, and I've been on Android N since the first preview. But now I'm interested in trying out Paranoid.
The bootloader is unlocked and I have just reflashed TWRP. But it asked for a password in the start which I got passed where I wiped everything on it. But whenever I try to boot into any rom (not just Paranoid) it's just stuck on the Google logo. Why so?
Will I need to downgrade my bootloader to the version from Marshmallow or am I missing something?
Click to expand...
Click to collapse
Basic Android Mod 101- BACKUP, BACKUP, BACKUP!!! Always do a backup, Nandroid b/ups are best. With Nexus device's you can unroot, and Flash the entire Google stock image. Brand new again.
Sent from my Nexus 5 using XDA-Developers mobile app
andreglud said:
I like swapping between new ROM's, and I've been on Android N since the first preview. But now I'm interested in trying out Paranoid.
The bootloader is unlocked and I have just reflashed TWRP. But it asked for a password in the start which I got passed where I wiped everything on it. But whenever I try to boot into any rom (not just Paranoid) it's just stuck on the Google logo. Why so?
Will I need to downgrade my bootloader to the version from Marshmallow or am I missing something?
Click to expand...
Click to collapse
Yeah that won't work since the vendors are different. There's a thread already about downgrading from N to Marshmallow..
http://forum.xda-developers.com/nexus-6p/help/trying-to-manually-downgrade-android-n-t3391373
It is all about the boot.img image.
if you flashed a rooted rom, flash the modified boot.img that allows root ( you can find it for each version here http://forum.xda-developers.com/nexus-6p/general/stock-modified-boot-img-regular-root-t3306684 )
if you flashed a non rooted stock rom, flash the stock boot.img ( you can extract it from the stock image file
that's it
andreglud said:
I like swapping between new ROM's, and I've been on Android N since the first preview. But now I'm interested in trying out Paranoid.
The bootloader is unlocked and I have just reflashed TWRP. But it asked for a password in the start which I got passed where I wiped everything on it. But whenever I try to boot into any rom (not just Paranoid) it's just stuck on the Google logo. Why so?
Will I need to downgrade my bootloader to the version from Marshmallow or am I missing something?
Click to expand...
Click to collapse
Just flash the correct vendor image for Marshmallow.
Two-Click Unlock for Zenfone 2 official Android 6.0
original post in Taiwan Asus Zentalk by @shakalaca
**do it at your risk**
1.Your PC must be adb environment ready.
2.You should know how to get into stock bootloader.( press Power and Volume up together)
files needed:
1. Download unlock.bat and restore.bat from here.
2. Recomended TWRP for verification.(repacked)
steps:
1.Copy unlock.bat and restore.bat on to your PC.
2.Plug your device in PC, click unlock.bat. The program will enter bootloader mode, reboot and then unlock.
3.After it run through unlock, the device will indicate it will reboot in 5 second. **important** PRESS VOLUME UP at the moment to enter bootloader.
4. If you miss step 3, the device will stuck in Asus logo. Don't worry. Just press POWER and VOLUME UP to enter bootloader.
5.When the device is in bootloader, click restore.bat Wait for the reboot and you are done unlock.
6.To verify unlock status, flash the recommended TWRP.
Good luck and all credits to @shakalaca
Is it the same as the unofficial method for bootloader unlock? also is there a way to relock bootloader like flashing it again over MM Beta?
Sent from my ASUS_Z00AD using XDA-Developers mobile app
Flynhx said:
Is it the same as the unofficial method for bootloader unlock? also is there a way to relock bootloader like flashing it again over MM Beta?
Sent from my ASUS_Z00AD using XDA-Developers mobile app
Click to expand...
Click to collapse
Different by the looks , the date gives it away and not a temp twrp-- although i am going to find out in about 10 mins --lets hope this works :highfive:
Not working for me
says flashing droidboot .184
anyone got this to work ?
no recovery after trying this - got stock recovery back from here ok
mega:///#F!k4MHiAgL!dVuOKeH3eokcwPSNI79ffw!ok8SQKII
timbernot said:
Different by the looks , the date gives it away and not a temp twrp-- although i am going to find out in about 10 mins --lets hope this works :highfive:
Not working for me
says flashing droidboot .184
anyone got this to work ?
no recovery after trying this - got stock recovery back from here ok
mega:///#F!k4MHiAgL!dVuOKeH3eokcwPSNI79ffw!ok8SQKII
Click to expand...
Click to collapse
According to @shakalaca, the restore process get back to 6.0 ifwi. After the unlock, the droidboot stay at .184 alright.
What is the status of your device before unlock, rooted or unrooted? Can you flash the twrp provided by him ?
samcjtsai said:
According to @shakalaca, the restore process get back to 6.0 ifwi. After the unlock, the droidboot stay at .184 alright.
What is the status of your device before unlock, rooted or unrooted? Can you flash the twrp provided by him ?
Click to expand...
Click to collapse
my device doesnt get to this part > 3.After it run through unlock, the device will indicate it will reboot in 5 second. **important** PRESS VOLUME UP
but stays on > press any key to finish...... which then closes the window
I flash twrp,says ok but reboots back to bootloader after restarting recovery.
flashed back stock recovery and factory reset for another attempt...lets see
Works good to me. Miss that step where I supposed to pressed vol up button and phone stuck on white splash screen. Force off and then go to bootloader, then execute restore.bat and done. After that root and exposed and then I mess up some another stuff so need to flash 6.0.1 MOFD_SDUPDATE manually from stock recovery. Everything pass smoothly but root and exposed framework disappeared obviously. Root and exposed again no problems
cannot flash custom roms???
Hi everyone,
I successfully unlocked my bootloader from MM beta, I successfully flashed the recommended twrp recovery, I successfully flashed rom and gapps but when I reboot the phone goes back to twrp recovery. Anyone else facing the same issue? Or is it impossible to flash custom roms?
Yousvel said:
Hi everyone,
I successfully unlocked my bootloader from MM beta, I successfully flashed the recommended twrp recovery, I successfully flashed rom and gapps but when I reboot the phone goes back to twrp recovery. Anyone else facing the same issue? Or is it impossible to flash custom roms?
Click to expand...
Click to collapse
ATM this unlock can backup/restore stock rom in recommended twrp, but can't flash CM. Seems its boot.img need to be repacked.
Yousvel said:
Hi everyone,
I successfully unlocked my bootloader from MM beta, I successfully flashed the recommended twrp recovery, I successfully flashed rom and gapps but when I reboot the phone goes back to twrp recovery. Anyone else facing the same issue? Or is it impossible to flash custom roms?
Click to expand...
Click to collapse
Same problem here
samcjtsai said:
ATM this unlock can backup/restore stock rom in recommended twrp, but can't flash CM. Seems its boot.img need to be repacked.
Click to expand...
Click to collapse
how can i flash a stock 5.0 rom from the recommended twrp? I tried to do that but it doesn't work. Do I have to flash a stock 6.0.1 beta rom?
It worked perfectly!Thanx a mill!
Can't flash TWRP although the splash screen became white after unlock.bat -> unlocked
After restore.bat the splash screen went black as usual. Then I flash the recommended TWRP. But when I choose recovery mode in fastboot, it reboot to fastboot. When I adb reboot recovery in Android OS, it reboot to stock recovery. Can anyone help me to solve this problem?
I'm running .69 MM beta, I replaced the .54 fastboot image in the package with .69 one. Does this effect the unlock state?
timbernot said:
Different by the looks , the date gives it away and not a temp twrp-- although i am going to find out in about 10 mins --lets hope this works :highfive:
Not working for me
says flashing droidboot .184
anyone got this to work ?
no recovery after trying this - got stock recovery back from here ok
mega:///#F!k4MHiAgL!dVuOKeH3eokcwPSNI79ffw!ok8SQKII
Click to expand...
Click to collapse
Edit Unlock.bat, find "sleep 3" in the line 24 and change it to "sleep 25" to increase the waiting time to detect back the fastboot after your phone reboots...
This fixed me the issue.... try it...
can i flash supersu to become root after unlock with this method?
ponnuvelpandian said:
Edit Unlock.bat, find "sleep 3" in the line 24 and change it to "sleep 25" to increase the waiting time to detect back the fastboot after your phone reboots...
This fixed me the issue.... try it...
Click to expand...
Click to collapse
Thanks :good: , i`ll keep that in mind when the time comes back on 5 atm
kamyk70 said:
Works good to me. Miss that step where I supposed to pressed vol up button and phone stuck on white splash screen. Force off and then go to bootloader, then execute restore.bat and done. After that root and exposed and then I mess up some another stuff so need to flash 6.0.1 MOFD_SDUPDATE manually from stock recovery. Everything pass smoothly but root and exposed framework disappeared obviously. Root and exposed again no problems
Click to expand...
Click to collapse
How you root your MM beta?, please tell me, i wanna root mine too
Sent from my ASUS_Z008D using XDA-Developers mobile app
Bring twrp zip android 6 please.
Can anyone backup with TWRP and upload?
Factory reset, backup with TWRP, and upload[emoji6]
Gesendet von meinem ASUS_Z00AD mit Tapatalk
KarloHD said:
Bring twrp zip android 6 please.
Can anyone backup with TWRP and upload?
Factory reset, backup with TWRP, and upload[emoji6]
Gesendet von meinem ASUS_Z00AD mit Tapatalk
Click to expand...
Click to collapse
Are you going to post this in EVERY tread?
Sent from my ASUS_Z00A using Tapatalk
Now, if we can unlock stock 6.0, can anyone confirm me if we can directly flash custom roms without downgrading to 5.0
after running restore it worked, however when running unlock.bat, I get permission denied and the device goes tinto bootloader bootloop, and I had the device rooted and bootunlocked already in lollipop, I wonder why that happens?
HI
I WAS ON 7.1.2 PURE NEXUS rom and...
i've decided to flash the stock image based on 6.0.1
i pluged my 6p to PC and head straight to NexusRootToolkit and i pick up my wanted image and the procces goes well untill the 6p bootloping in google screen . i changed the image and didnt work
one thing has killin me the bootloader was locked before i do that BUT THE PHONE IN bootloader menu shows me that device is unlocked
any help ... i want to go back to 6.0.1 safely
thank you. lol i swear if the issue got fixed i'll never ever rooting anymore loool
Try to flash the image with fastboot, if the bootloader is unlocked, don't use such tools.
Edit: it doesn't matter that your device was rooted, and why you want to flash old marshmallow image, flash the latest nougat.
Use the heisenberg guide. Adb shell using fastboot commands has never failed me.
coremania said:
Try to flash the image with fastboot, if the bootloader is unlocked, don't use such tools.
Edit: it doesn't matter that your device was rooted, and why you want to flash old marshmallow image, flash the latest nougat.
Click to expand...
Click to collapse
OMG! what a Stupid Problem, i just flashed Nougat version not MM and it works ..
i checked the OEM it says bootloader is already unlocked.
is it safe now to go back to MM via Nexus Root toolkit?
Abdulaziz6p said:
OMG! what a Stupid Problem, i just flashed Nougat version not MM and it works ..
i checked the OEM it says bootloader is already unlocked.
is it safe now to go back to MM via Nexus Root toolkit?
Click to expand...
Click to collapse
I advice you to use fastboot, yes you have to read a little bit for this, but you will know what you are doing. And as long as you're flashing your phone don't lock your bootloader.
Sure you can move to mm, if you want to do it with toolkits I can't give you any support because I don't use them.
Better you read a little bit and you will understand what you are doing.