I am trying to root my second Nexus Player but cannot install TWRP. After I type "fastboot flash recovery twrp.img", I get and
error: cannot load twrp.img.
I also tried the Nexus Root Toolkit and got stuck in bootloop when rebooting.
What is the cause of these problems?
You could try downgrading to 5.1.1 and then flashing twrp. Just don't flash 6.0's recovery. If that still doesn't do it, just boot to twrp (fastboot boot twrp.img) and do what you need to that way. It's not a permanent flashing, but it will accomplish whatever task you need done.
kibmikey1 said:
You could try downgrading to 5.1.1 and then flashing twrp. Just don't flash 6.0's recovery. If that still doesn't do it, just boot to twrp (fastboot boot twrp.img) and do what you need to that way. It's not a permanent flashing, but it will accomplish whatever task you need done.
Click to expand...
Click to collapse
Can u say, how to downgrade to android 5.1.1?
i must download from google: factory android 5.1.1? and install it? ya?
Related
Hi folks,
after returned the 16gb version, i got my 32gb n7.
following the same step to root my 16gb one, i fail the root of my 32gb nexus7!
i donot why it kind of stuck in the step saying " booting the donowaled image' and just restart again. it should send me to the CWM [email protected]@
please HELP!!!!!!!!!!!!!!!!!!!! plase
fastboot OEM unlock, fastboot flash a custom recovery, flash the su binaries or a custom ROM, boot, and profit. that's all that is needed(without a toolkit). did you use a toolkit?
simms22 said:
fastboot OEM unlock, fastboot flash a custom recovery, flash the su binaries or a custom ROM, boot, and profit. that's all that is needed(without a toolkit). did you use a toolkit?
Click to expand...
Click to collapse
I succeeded to unlock the device............................ then when i flash the CWM into the device....i cannot get into the recovery mode. instead the device restart to the normal GOogle screen
seedzeng said:
I succeeded to unlock the device............................ then when i flash the CWM into the device....i cannot get into the recovery mode. instead the device restart to the normal GOogle screen
Click to expand...
Click to collapse
try twrp recovery. but cwm should work too. try booting recovery through fastboot..
fastboot boot recovery recoveryname.img
If you have installed the new boot loader latest official CWM will not work unless you flash an unofficial version (6.0.1.5 if I remember well).
Sent from my Nexus 7 using xda app-developers app
Guys... when i tried to flash oos 3.0 on my op2 through twrp, i first wiped the data to install new rom, then install oos 3.0, it failed. I then flashed the recovery i downloaded from the thread, then restart the recovery
I cant boot into the recovery.
System can't boot
Is it called "brick"?
So i tried to flash stock recovery in pc by command, but it says "remote: device is locked. cannot flash images". any solution to this problem?
I can boot into fastboot mode
You need to run the phone in Qualcomm mode on a PC and run the recovery tool to fix you bootloader.
I did the same and it was a royal ball ache trying to find out how to fix it
Don't do what rosswaa said
Why not?
What you should do is boot your phone into fastboot mode, connect it to your pc. Flash this modified TWRP recovery img to your phone https://www.androidfilehost.com/?fid=24459283995297945. After that you have to flash this modified SuperSU (through the new recovery) https://www.androidfilehost.com/?fid=24459283995297946.
The normal recovery doesn't work in OOS 3.0 (just like in HOS) and it's the SuperSU that gives you the soft brick. A dirty flash of the modified SuperSU should fix it.
I also had your problem and I did what rosswaa said which shouldn't be necessary (I lost all my data and backups).
I didn't lose anything, but I tried doing what you said and my bootloader was screwed so wouldn't take a flashed recovery or anything (yes the modified one)
Wish I hadnt been so excited and just flashed but all sorted now
Hmm okay, if it doesn't work with flashing the new recovery img then do what rosswaa said and after that follow this post https://forums.oneplus.net/threads/installation-instructions-faqs-oxygenos-3-0-0.439108/
Obviously try what green says first, if it works then happy days
first i am really glad that someone give some advices on me. But since i am a noob, how can i flash twrp in fastboot mode? using command? "fastboot flash recovery xxx.img"? thx
SPiCa39's said:
Guys... when i tried to flash oos 3.0 on my op2 through twrp, i first wiped the data to install new rom, then install oos 3.0, it failed. I then flashed the recovery i downloaded from the thread, then restart the recovery
I cant boot into the recovery.
System can't boot
Is it called "brick"?
So i tried to flash stock recovery in pc by command, but it says "remote: device is locked. cannot flash images". any solution to this problem?
I can boot into fastboot mode
Click to expand...
Click to collapse
1 Install official TWRP 3.x via fastboot twrp.me/devices/oneplustwo.html
Reboot to recovery
2 install this modified version of TWRP
forum.xda-developers.com/oneplus-2/development/recovery-teamwin-recovery-project-3-0-0-t3310713
Reboot to recovery
3 install oos3 (And supersu)
Sorry i can't post link
Hey XDA, Recently installed Paranoid Android coming from Chroma and it's not stuck in a boot loop. I can boot just fine every time besides the annoying corruption google warning, but no matter how many times I try to install TWRP it just won't let me boot into recovery. I'm using WugFresh's NRT kit. Can't seem to figure it out. Any suggestions?
carterl96 said:
Hey XDA, Recently installed Paranoid Android coming from Chroma and it's not stuck in a boot loop. I can boot just fine every time besides the annoying corruption google warning, but no matter how many times I try to install TWRP it just won't let me boot into recovery. I'm using WugFresh's NRT kit. Can't seem to figure it out. Any suggestions?
Click to expand...
Click to collapse
My suggestion is for you to fastboot flash the TWRP recovery image instead of using a toolkit. You cant see the inner workings of a toolkit and have no idea of what it is doing. The toolkit could be using the wrong commands to install a recovery image to your 6P. Go to www.twrp.me and search for the recovery image for your specific device and download the file. Next, rename the file to recovery.img Then, on your PC, navigate to the folder where you downloaded the TWRP image. Open a command prompt in that folder by pressing and holding the SHIFT KEY + RIGHT CLICK on your mouse and select OPEN A COMMAND WINDOW HERE. Boot to the bootloader on your device and connect it to your PC. Then type this:
fastboot flash recovery recovery.img
Then type this:
fastboot reboot bootloader
fastboot reboot recovery
Here is the link to download TWRP for your Nexus 6P
This will reboot your device to TWRP
All of this is based on the assumption that you have a working ADB installation and unlocked the bootloader and have USB Debugging turned on in DEVELOPER OPTIONS.
Sent from my Nexus 6 using XDA-Developers mobile app
Same thing, successful install and it won't open. Just shows the dead android when going to recovery.
carterl96 said:
Same thing, successful install and it won't open. Just shows the dead android when going to recovery.
Click to expand...
Click to collapse
You get the same results after fastboot flashing the TWRP image? I'd say your next step is to start fresh by fastboot flashing the factory images to return to a fully stock state. Then fastboot flash TWRP again.
Sent from my Nexus 6 using XDA-Developers mobile app
Do not boot directly into system after flashing the custom recovery.
After flashing boot into TWRP. I remember on previous devices that I owned that if you do not boot into the custom recovery after flashing it, you revert to the factory recovery.
Just a thought
tech_head said:
Do not boot directly into system after flashing the custom recovery.
After flashing boot into TWRP. I remember on previous devices that I owned that if you do not boot into the custom recovery after flashing it, you revert to the factory recovery.
Just a thought
Click to expand...
Click to collapse
I thought about that too. What is probably happening is his custom recovery is being patched by the ROM each time he boots into recovery. Thanks for picking up on that. I forgot to include that in my last post.
Sent from my Nexus 6 using XDA-Developers mobile app
tech_head said:
Do not boot directly into system after flashing the custom recovery.
After flashing boot into TWRP. I remember on previous devices that I owned that if you do not boot into the custom recovery after flashing it, you revert to the factory recovery.
Just a thought
Click to expand...
Click to collapse
That's correct. After flashing TWRP the next step is reboot into the bootloader using the volume keys and power key , then from there boot into recovery using the volume keys and power key, then the phone can be rebooted from TWRP into Android and then after that TWRP should stick.
If the boot image is not patched, the ROM will overwrite TWRP once you reboot. flashing latest SU from TWRP will prevent this.
Thanks for all the replies guys! All the advice combined got it to work. I did some more research and found that Paranoid doesn't actually come preprooted like all the other roms I've been used to. So using the tool kit I just had it root it with the latest SuperSu and also flash a custom recovery. It has booted into TWRP no problems now a few times. Hopefully it will stay like this. Will keep everyone posted and appreciate the advice. Thanks XDA!
I installed TWRP custom recovery on my Nexus 6P. I was able to boot into it ONCE. When i next tried to enter Recovery, i get a screen showing the Android Robot and the following statement: NO COMMAND
I tried to re-install TWRP using adb twice, but the result is the same.
How can i either fix TWRP, or re-install the stock recovery
I am basically a beginner here, so any help would be appreciated
If you installed the stock system image and then booted into it, it likely automatically reinstalled stock recovery also. I don't know why it does that, but it does. This is why I usually just reinstall TWRP again after each monthly update is completed.
You should use fastboot to install the images, not adb. The command should look like:
fastboot flash recovery twrp.img
I think i just worded it wrong - I used the above command (fastboot flash recovery twrp.img) to install twrp, and then, when i couldn't get back into recovery (Power - Volume Up combo just lest to screen that stated "No Command".), i used the fastboot flash recovery twrp.imp twice to try to re-install TWRP, but it didn't work
I also downloaded the latest stock Oreo ROM, copied the recovery.img file, and used fastboot.flash.recovery.img to try to re-install the stock recovery, but that didn't work either
The once time that TWRP work, it asked it I wanted to use TWRP is read only, to twice i selected NO (don't know if this matters)
Any other suggestions to fix TWPR, or re-install the stock recovery image???
When you say it didn't work, can you expand on that? Was there an error or anything?
hmodiano said:
I think i just worded it wrong - I used the above command (fastboot flash recovery twrp.img) to install twrp, and then, when i couldn't get back into recovery (Power - Volume Up combo just lest to screen that stated "No Command".), i used the fastboot flash recovery twrp.imp twice to try to re-install TWRP, but it didn't work
I also downloaded the latest stock Oreo ROM, copied the recovery.img file, and used fastboot.flash.recovery.img to try to re-install the stock recovery, but that didn't work either
The once time that TWRP work, it asked it I wanted to use TWRP is read only, to twice i selected NO (don't know if this matters)
Any other suggestions to fix TWPR, or re-install the stock recovery image???
Click to expand...
Click to collapse
If you want TWRP to stick, you need to flash either SuperSU or magisk. The Android with the exclamation mark is what stock recovery looks like.
Once you have TWRP installed and wish to keep it, you don't need to flash stock recovery in the monthly update. Just boot into TWRP after flashing update and root again.
chaoticyeshua said:
When you say it didn't work, can you expand on that? Was there an error or anything?
Click to expand...
Click to collapse
When the phone is turned on, it never progresses beyond the first screen. No error codes, it just does not proceed to boot up.
I had to buy a new phone (need it for business, but i given up on trying to install Resurrection Remix on the Nexus 6P, which was the reason I was trying to install TWPR and SuperSU. So far, I have only accomplished turning the phone into a brick door stop!!!
hmodiano said:
When the phone is turned on, it never progresses beyond the first screen. No error codes, it just does not proceed to boot up.
I had to buy a new phone (need it for business, but i given up on trying to install Resurrection Remix on the Nexus 6P, which was the reason I was trying to install TWPR and SuperSU. So far, I have only accomplished turning the phone into a brick door stop!!!
Click to expand...
Click to collapse
Use Magisk it's the better solution for root. Never had boot up issues with it just stock you have to boot once through before flashing. Custom ROMs you can flash right away.
Currently running into some issues with TWRP. I follow the official guide on TWRP's website;
I reboot into bootloader (adb reboot bootloader)
Flash the twrp.img (fastboot flash recovery twrp.img)
Reboot straight into TWRP (without any issues) – plugging out the cable and holding the combination keys
When I try to boot up after all of these steps I end up with a bootloop, not going into recovery but getting the Sony screen over and over again. Is this a common issue or am I just a total idiot with an obvious mistake?
ImBrakkie said:
Currently running into some issues with TWRP. I follow the official guide on TWRP's website;
I reboot into bootloader (adb reboot bootloader)
Flash the twrp.img (fastboot flash recovery twrp.img)
Reboot straight into TWRP (without any issues) – plugging out the cable and holding the combination keys
When I try to boot up after all of these steps I end up with a bootloop, not going into recovery but getting the Sony screen over and over again. Is this a common issue or am I just a total idiot with an obvious mistake?
Click to expand...
Click to collapse
Which rom/version? Rooted? Bootloader unlocked? What did you do with the phone before flashing twrp?
levone1 said:
Which rom/version? Rooted? Bootloader unlocked? What did you do with the phone before flashing twrp?
Click to expand...
Click to collapse
Sorry for lack of information in the post.
Running Customized UK (8.0.0) downloaded with XperiFirm and flashed with FlashTool. I got no root, bootloader is unlocked. Phone was working fully and running like it should be before installation of TWRP, after installation of TWRP there is no way of me booting to the system.
ImBrakkie said:
Sorry for lack of information in the post.
Running Customized UK (8.0.0) downloaded with XperiFirm and flashed with FlashTool. I got no root, bootloader is unlocked. Phone was working fully and running like it should be before installation of TWRP, after installation of TWRP there is no way of me booting to the system.
Click to expand...
Click to collapse
I know that if you don't modify your boot img, (rootkernel), Sony security will cause boot failure at any sign of modification. I didn't realize that it would happen just by flashing recovery, and not modifying anything, but I guess so... Flash the rom again, then flash modified boot img before you turn it on, (you can use rootkernel to make one, or copy one from root thread in this forum), then flash TWRP...
levone1 said:
I know that if you don't modify your boot img, (rootkernel), Sony security will cause boot failure at any sign of modification. I didn't realize that it would happen just by flashing recovery, and not modifying anything, but I guess so... Flash the rom again, then flash modified boot img before you turn it on, (you can use rootkernel to make one, or copy one from root thread in this forum), then flash TWRP...
Click to expand...
Click to collapse
That makes sense, I will give it a go another day. Thanks