Related
Hi Guys, i have 1 little problem.
im on the last Android N Preview 5 and i wannt to root it.
i have downloaded SuperSU 2.76 and TWRP 3.0.2.0
I rebooted to bootloader flashed thw twrp via Terminal, now i wanna boot into recovery because of the SuperSU zip, but i am stucking on TWRP Logo.
Phone is working normal, but i cant enter into recovery, anyone else has the same problem?
Thanks and best Regards,
Taker
You have to flash another version of TWRP... But, dude, i'm on the exact same case, same preview, and i can't get it to work. TWRP doesn't seem to work :/ I always got the god damn "no command" even if i follow some of the tutorials here...
EDIT : Try flashing the 3.0.0 or 3.0.1, and when all will be working (if you achieve, tell me how xD) update it.
EDIT 2 : I may find something, i'll let you know !
TWRP doesnt work with the developer previews without modifying the boot image.
If you want to root, you can use CF-Auto root.
You will still have the stock recovery.
Taker18 said:
Hi Guys, i have 1 little problem.
im on the last Android N Preview 5 and i wannt to root it.
i have downloaded SuperSU 2.76 and TWRP 3.0.2.0
I rebooted to bootloader flashed thw twrp via Terminal, now i wanna boot into recovery because of the SuperSU zip, but i am stucking on TWRP Logo.
Phone is working normal, but i cant enter into recovery, anyone else has the same problem?
Thanks and best Regards,
Taker
Click to expand...
Click to collapse
This is a known issue, Search the forum for the resolution. Basically TWRP won't work on the Android N on Encrypted device.
The solution is pretty simple. You need to decrypt your device's storage. TWRP currently doesn't work with encrypted N preview.
This could be easily done by flashing the modified boot image, that will disable forced-encryption. After that, you will need to format the current userdata partition to decrypt the storage.
Code:
fastboot format userdata
fastboot format cache
Once that is done, you can flash TWRP and then use SuperSU to root.
Another way to direct root is by using Cf-Auto-Root. But I am not sure about that specifically. While some users have succeeded, there are a few who have failed to root using Cf-Auto-Root.
Just use CF-Auto Root, it will do all the things.
Make sure you have unlocked your Bootloader and downloaded the good version of CF for your device.
Reboot your phone in bootloader mode, plug it to a computer, and just open the .bat (if you're on windows, or the equivalent for Mac / Linux). It will install SuperSU. When it's done, don't forget to download the TWRP Manager on the Playstore, and you'll have a working Recovery ! I did that, i know have a rooted nexus 6P on Android N preview 5
Also, lot's of Root's only apps will not work properly, because lots of changes took place on Android N. So make sure you follow some guide out there (exemple : Ex Kernel don't work if you don't tweak some things, same with Ad Away, so make sure you're googling)
I followed the premise of this thread here so all credits go to the OP http://forum.xda-developers.com/showthread.php?t=3410906 I flashed the latest Marshmallow vendor.img via fastboot, then flashed TWRP via fastboot. Booted into recovery from the bootloader then side loaded supersu using adb side load in TWRP. After that I rebooted to bootloader from TWRP and fastboot flashed the DP5 vendor.img and recovery.img. All is working well.
Don´t know if anybody had this kind of Problem before. Couldnt find anything.
Was on Stock V image with cutom kernel flashed via fastboot and SU flashed via fastboo boot to root.
Problem:
bootet TWRP via fastboot with newest drivers. Flashed RC via booted TWRP.
Wanted to reboot system, but was stuck in a TWRP bootloop. No chance to boot into bootloader also. Even tried changing slots in twrp but still only bootloop to twrp.
Than I thought about sideload because that's what I did with latest ota image from Google.
Here is what I did:
sideloaded the ota.zip via TWRP from PC "adb sideload ota_file.zip" ota_file should be the name of your ota file
It gave me an error, but after rebooting system all fine again. Back to stock V and bootloader is there again.
Easier thing to do is flash boot.img from the factory image to boot_a and boot_b if you are having issues.
This problem occurs when you flash TWRP if you have root installed. To avoid, remove root before installing TWRP.
Oh, I should mention to get into bootloader from TWRP, simply use the adb command "adb reboot bootloader". Should work, worked for me.
I just have avoided flashing TWRP altogether. I rarely need to flash anything, so it can wait until I am at work or home to use a PC to BOOT TWRP each time I need it, instead of flashing it.
Nitemare3219 said:
I just have avoided flashing TWRP altogether. I rarely need to flash anything, so it can wait until I am at work or home to use a PC to BOOT TWRP each time I need it, instead of flashing it.
Click to expand...
Click to collapse
Until it gets a little more stable on the Pixel, this is probably a good idea.
Good idea. But I M sometimes flashing when I am at or on the way to work.
Flash junkie needs his daily dosis
mikaole said:
Don´t know if anybody had this kind of Problem before. Couldnt find anything.
Was on Stock V image with cutom kernel flashed via fastboot and SU flashed via fastboo boot to root.
Problem:
bootet TWRP via fastboot with newest drivers. Flashed RC via booted TWRP.
Wanted to reboot system, but was stuck in a TWRP bootloop. No chance to boot into bootloader also. Even tried changing slots in twrp but still only bootloop to twrp.
Than I thought about sideload because that's what I did with latest ota image from Google.
Here is what I did:
sideloaded the ota.zip via TWRP from PC "adb sideload ota_file.zip" ota_file should be the name of your ota file
It gave me an error, but after rebooting system all fine again. Back to stock V and bootloader is there again.
Click to expand...
Click to collapse
I know its already solved, but here is what helps (for future):
Just flash SuperSU (latest Version)
Done. This will patch the boot.img so your phone boots in the OS again.
Shadow of Destiny said:
I know its already solved, but here is what helps (for future):
Just flash SuperSU (latest Version)
Done. This will patch the boot.img so your phone boots in the OS again.
Click to expand...
Click to collapse
I have this issue and flashing supersu didn't fix my problem. Will go to factory image flashing.
Shadow of Destiny said:
I know its already solved, but here is what helps (for future):
Just flash SuperSU (latest Version)
Done. This will patch the boot.img so your phone boots in the OS again.
Click to expand...
Click to collapse
Thanks! This worked for me.
EDIT: Never mind, I missed the comment guiding ppl to flash SuperSU. I suppose that when this thread was posted, that SuperSU was still being used instead of Magisk, so solution is essentially the same thing I'm recommending.
I think this thread is missing the much easier solution here:
I just ran into this issue with my Pixel 2 XL when I tried to update my TWRP version from 3.2.1-2 to 3.2.3-0. Here's how it went:
1. Downloaded the TWRP zip, md5 and so on from the official TWRP website for the Pixel 2 XL
2. Booted to TWRP and installed / flashed the zip of TWRP 3.2.3-0
3. Wiped dalvik and then chose Reboot to System from TWRP -- the phone booted right back into TWRP
4. Tried again to reboot the same way. Same result.
5. Installed / Flashed the 3.2.1-2 TWRP zip which was still on my phone, in order to revert to the previous version, and then Rebooted to System -- same result
6. Flashed 3.2.3-0 zip again, then flashed the Flash Kernel that I've been using, and then Flashed the Magisk v16.0 zip that I used to root, then chose Reboot to System -- AND IT WORKED; the phone booted normally and now I'm updated to the latest TWRP successfully.
tl;dr - The solution is to flash Magisk again after updating TWRP. Pretty sure this goes for kernel updates too.
cognitivedissonance said:
EDIT: Never mind, I missed the comment guiding ppl to flash SuperSU. I suppose that when this thread was posted, that SuperSU was still being used instead of Magisk, so solution is essentially the same thing I'm recommending.
I think this thread is missing the much easier solution here:
I just ran into this issue with my Pixel 2 XL when I tried to update my TWRP version from 3.2.1-2 to 3.2.3-0. Here's how it went:
1. Downloaded the TWRP zip, md5 and so on from the official TWRP website for the Pixel 2 XL
2. Booted to TWRP and installed / flashed the zip of TWRP 3.2.3-0
3. Wiped dalvik and then chose Reboot to System from TWRP -- the phone booted right back into TWRP
4. Tried again to reboot the same way. Same result.
5. Installed / Flashed the 3.2.1-2 TWRP zip which was still on my phone, in order to revert to the previous version, and then Rebooted to System -- same result
6. Flashed 3.2.3-0 zip again, then flashed the Flash Kernel that I've been using, and then Flashed the Magisk v16.0 zip that I used to root, then chose Reboot to System -- AND IT WORKED; the phone booted normally and now I'm updated to the latest TWRP successfully.
tl;dr - The solution is to flash Magisk again after updating TWRP. Pretty sure this goes for kernel updates too.
Click to expand...
Click to collapse
This is a Pixel XL forum.
Homeboy76 said:
This is a Pixel XL forum.
Click to expand...
Click to collapse
Aren't the two systems (Pixel OG and Pixel 2) extremely similar? If they're not, then my advice should be ignored for anyone using the Pixel OG.
I was trying to root my phone and I installed Supersu but than my phone refused to boot. It would open fastboot but nothing after that. I tried to revert to the stock image and i think i made it past that but, that did not fix anything i can still only boot into fastboot. Please help me I want to save my phone.
fireop958 said:
I was trying to root my phone and I installed Supersu but than my phone refused to boot. It would open fastboot but nothing after that. I tried to revert to the stock image and i think i made it past that but, that did not fix anything i can still only boot into fastboot. Please help me I want to save my phone.
Click to expand...
Click to collapse
SuperSU should have a uninstall file, try flashing that in twrp
Sent from my validus_athene using Tapatalk
fireop958 said:
I was trying to root my phone and I installed Supersu but than my phone refused to boot. It would open fastboot but nothing after that. I tried to revert to the stock image and i think i made it past that but, that did not fix anything i can still only boot into fastboot. Please help me I want to save my phone.[/Q
Flash a temporary rom and then install a stock recovery, and then boot back into stock rom by flashing stock image on pc
through fastboot mode
Click to expand...
Click to collapse
@fireop958
Installing SuperSU or any root app needs custom kernel installed, if you flash it on stock kernel then its anti-root mechanism will get activated and it will refuse to boot;
now first flash the stock rom via fast boot from here : https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
then after its booted successfully, then flash the TWRP from fastboot and flash the ElimentalX kernel from TWRP, reboot and check the kernel info in about phone in settings; after then
simply flash SuperSU or magisk from TWRP to get root access
siddhesh9146 said:
@fireop958
Installing SuperSU or any root app needs custom kernel installed, if you flash it on stock kernel then its anti-root mechanism will get activated and it will refuse to boot;
now first flash the stock rom via fast boot from here : https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
then after its booted successfully, then flash the TWRP from fastboot and flash the ElimentalX kernel from TWRP, reboot and check the kernel info in about phone in settings; after then
simply flash SuperSU or magisk from TWRP to get root access
Click to expand...
Click to collapse
Thank you so much. You saved my life right there.
So I just got my Nexus 6p today and I've tried rooting this thing but it just kept making me stuck on the google logo. I successfully unlocked the bootloader and installed TWRP but everytime I installed from ZIP SuperSU or Magisk it would keep getting me stuck on the google logo. I've tried this several times because I could still go to bootloader. I've flashed the stock image a couple of times and reinstalled TWRP but I just can't get it to root.
Edit: I have flashed to stock and I'm on 6.0. I haven't tried reinstalling TWRP but the bootloader is unlocked and everything else is stock.
Edit 2: I just flashed TWRP and now I'm stuck on the google logo. Wtf is this??
nemesis101x said:
So I just got my Nexus 6p today and I've tried rooting this thing but it just kept making me stuck on the google logo. I successfully unlocked the bootloader and installed TWRP but everytime I installed from ZIP SuperSU or Magisk it would keep getting me stuck on the google logo. I've tried this several times because I could still go to bootloader. I've flashed the stock image a couple of times and reinstalled TWRP but I just can't get it to root.
Edit: I have flashed to stock and I'm on 6.0. I haven't tried reinstalling TWRP but the bootloader is unlocked and everything else is stock.
Edit 2: I just flashed TWRP and now I'm stuck on the google logo. Wtf is this??
Click to expand...
Click to collapse
Could be because you are on older version of Android. Did you make sure you are on the correct bootloader? Anyways I found with stock you must complete the initial setup then you can go back and root later. I've had success with Magisk 16.0 on nougat and Oreo so don't see why it wouldn't work on marshmallow.
Exodusche said:
Could be because you are on older version of Android. Did you make sure you are on the correct bootloader? Anyways I found with stock you must complete the initial setup then you can go back and root later. I've had success with Magisk 16.0 on nougat and Oreo so don't see why it wouldn't work on marshmallow.
Click to expand...
Click to collapse
What is a 'correct bootloader' anyway? I am on the latest bootloader and flashed latest factory images and still bootlooping, can't even make it to recovery mode (flashed 4-cores TWRP after I flashed stock).
Gamool said:
What is a 'correct bootloader' anyway? I am on the latest bootloader and flashed latest factory images and still bootlooping, can't even make it to recovery mode (flashed 4-cores TWRP after I flashed stock).
Click to expand...
Click to collapse
Ok sorry you said 6.0 in comment that's why I asked about bootloader. Also thought was just the root giving you a hard time not the dreaded bootloop that some 6Ps get.
my oneplus 6t has the red ! warning and will not boot. i can get into the stock recovery menu and the fastboot menu. can someone please help me.
i unlocked my bootloader
installedd twrp (which i can only seem to get the stock recovery)
rooted
installed custom rom
and thats what i get when it rebooted.
am i just screwed or is there hope for my phone ?
skaroger867 said:
my oneplus 6t has the red ! warning and will not boot. i can get into the stock recovery menu and the fastboot menu. can someone please help me.
i unlocked my bootloader
installedd twrp (which i can only seem to get the stock recovery)
rooted
installed custom rom
and thats what i get when it rebooted.
am i just screwed or is there hope for my phone ?
Click to expand...
Click to collapse
Go to below link, download and flash latest fastboot ROM.
https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
If that does not work, use MS tool to recover phone to factory state.
Thanks this worked for me. Was freaking out a little. The scene has really changed since I've been here.
skaroger867 said:
Thanks this worked for me. Was freaking out a little. The scene has really changed since I've been here.
Click to expand...
Click to collapse
As an FYI, in order to root on this phone, assuming you are using Magisk (recommended) you will need to:
Unlock bootloader
Install custom rom (Optional step, but also recommended)
Then flash TWRP zip (This phone, TWRP is part of the boot.img)
Boot the phone
Reboot to recovery
Install GAPPS (OpenGAPPS Stock recommended personally, but any should work)
Then flash Magisk
sandix said:
As an FYI, in order to root on this phone, assuming you are using Magisk (recommended) you will need to:
Unlock bootloader
Install custom rom
Then flash TWRP zip (This phone, TWRP is part of the boot.img)
Boot the phone
Reboot to recovery
Install GAPPS (OpenGAPPS Stock recommended personally, but any should work)
Then flash Magisk
Click to expand...
Click to collapse
Custom rom is not required for root
bladestonez said:
Custom rom is not required for root
Click to expand...
Click to collapse
Correct. I edited my comment to reflect that, however since OP installed a custom rom, I put the step in since I figured he would have asked about it.
sandix said:
As an FYI, in order to root on this phone, assuming you are using Magisk (recommended) you will need to:
Unlock bootloader
Install custom rom (Optional step, but also recommended)
Then flash TWRP zip (This phone, TWRP is part of the boot.img)
Boot the phone
Reboot to recovery
Install GAPPS (OpenGAPPS Stock recommended personally, but any should work)
Then flash Magisk
Click to expand...
Click to collapse
Ok so my phone currently is bootloader unlocked and rooted with magisk. So if I want to install a custom rom I flash in twrp, then flash twrp (while still in twrp), boot phone, reboot to recovery, flash gapps then flash magisk?
read the OP in any custom rom you want to flash, and the dev will have the details on how to flash..
skaroger867 said:
Ok so my phone currently is bootloader unlocked and rooted with magisk. So if I want to install a custom rom I flash in twrp, then flash twrp (while still in twrp), boot phone, reboot to recovery, flash gapps then flash magisk?
Click to expand...
Click to collapse
Essentially. Each custom ROM is differrent, so make sure to read the OP of each custom ROM you try to confirm flashing instructions but that's the **general** flashing method I use. Magisk is overwritten with each flash because Magisk installs to the same partition as the kernel.