Hi, I have a Nexus 5X Android 8.1.0 with TWRP on it. I'm trying to root my phone. I'm using Nexus Root Toolkit. It's unlocked and ready for NRT. When I click "Root" (with or without Custom Recovery), I get an error "ADB Recovery device was not found." It asks me to select drivers on my computer (Android Device > Android ADB Interface.) I have 3 "Standard MTP Device" Drivers. The Live Log shows "Checking ADB Recovery Connectivity" and then fails. I get the error. So how do I root with NRT and get past the "ADB Recovery device was not found"? Has anyone heard of this problem? What drivers do I need? Everything else works fine. Also, Will rooting with Toolkit install Super SU and BusyBox? I've never successfully rooted using NRT. So how do I fix the Recovery Connectivity? Please reply. Thanks
Hi, I'm back. Does anyone know what "Recovery Connectivity" means? My phone is plugged in. I used Magisk once but I'd like to try Nexus Root Toolkit. I'll check back later.
I'm back. I found that Recovery Connectivity means TWRP isn't working. When I try the bootloader and hit Recovery, I get a screen saying "no command." Then it reboots to the system. I tried reinstalling TWRP using "adb reboot bootloader", when I try "fastboot flash recovery twrp-2.8.x.x-xxx.img", it completes but when I reboot and try Recovery from bootloader, I get the same "no command" error. I tried from C:/...NexusRootToolkit/data/Root_Files and "C:\AIO" which is a second file I downloaded. Both have Bullhead img files in them. They say flashing recovery is successful, but when I reboot and try Recovery, I get the above error. Does anyone know how I can flash the TWRP Recovery?
I installed TWRP. I can boot into it whenever I want. When I click "Root" and check "Custom Recovery" (on NRT) it completes and says rooting was successful. That's good. It also says I need SuperSU and Busybox. I tried flashing them (the zips) in TWRP and it says it completes. When I open my root checker or BusyBox it says "no Root." So my root was incorrect. I think I need SuperSU to root in NRT. I flashed it but it doesn't show up. I can't find it in Google Play. The live log says SuperSU flashed successfully. Still no Root. So where do I download SuperSU? NRT has it. Not working. BusyBox shows up on my phone but says it needs root. Does anyone know where I can download SuperSU? And how to Root? Please reply. Thanks
Hi, I'm going to try Magisk. It doesn't use System and I can update. Instead of using SuperSU. Now my Nexus 5X won't show up in Windows Explorer. I need to move Magisk on my phone. Can't do that. It shows up in Device Manager. I've been trying a lot of Drivers. Not connecting just MTP Device. I found a few drivers but I get an error "This device cannot start. code 10." So what driver do I need for MTP Device? It used to say Nexus 5X in Windows Explorer and Device Manager. For screenshots try this question on Microsoft Community... https://answers.microsoft.com/en-us/windows/forum/windows_10-hardware/need-android-mtp-drivers-for-nexus-5x/d59c47c4-df80-410c-b2de-45a7869604a6?tm=1574728076937
I got it working. I downloaded Magisk on my phone. Then rebooted to TWRP and installed the zip from my Downloads folder. Then I restarted to the system and my App showed up there. I now have my phone rooted with Magisk.
Related
Hi,
First of all I'd like to say I tried to look this up in the forum but since my problem is kind of a combination of several problems, I failed to find a proper solution.
I have a rooted galaxy nexus running 4.3 deodexed. I downloaded a Mod to flash in CWM Recovery. Did a flash and factory reset and as I tried to flash it, it gave an error and aborted the installation and since then I can't get the phone out of bootloader. I can enter recovery mod from there however, I can't boot the phone.
Unfortunately I don't have a stock rom or any other zip/img/tar etc file on my sdcard.
When I plug my phone on bootloader I get the error message FASTBOOT fail command
I downloaded adb drivers but when I try to use adb push command I get an error message saying "ADB is not a recognized as an internal or external command etc." I'm doing this on the folder where extracted adb files.
I used to skipnote nexus toolkit. But even though I can get it to recognize my phone on either fastboot or adb mode, I fail to flash / push or install anything on my phone. If I try ADB, it waits forever on waiting for ADB phase. If I use fastboot however, it gives an error message and aborts the operation.
Downloaded & installed kies on the computer. I tried ODIN to push files but I failed at that too. Seems like Odin doesn't recognize the device.
As a result, I can't use my phone right now. I'm open for any suggestions for installing a stock rom and unrooting or rooting and installing a custom rom.
Thank you all very much in advance,
solved
I used another laptop with a fresh skipnote nexus toolkit and everything worked just fine.
shakrooph said:
Hi,
First of all I'd like to say I tried to look this up in the forum but since my problem is kind of a combination of several problems, I failed to find a proper solution.
I have a rooted galaxy nexus running 4.3 deodexed. I downloaded a Mod to flash in CWM Recovery. Did a flash and factory reset and as I tried to flash it, it gave an error and aborted the installation and since then I can't get the phone out of bootloader. I can enter recovery mod from there however, I can't boot the phone.
Unfortunately I don't have a stock rom or any other zip/img/tar etc file on my sdcard.
When I plug my phone on bootloader I get the error message FASTBOOT fail command
I downloaded adb drivers but when I try to use adb push command I get an error message saying "ADB is not a recognized as an internal or external command etc." I'm doing this on the folder where extracted adb files.
I used to skipnote nexus toolkit. But even though I can get it to recognize my phone on either fastboot or adb mode, I fail to flash / push or install anything on my phone. If I try ADB, it waits forever on waiting for ADB phase. If I use fastboot however, it gives an error message and aborts the operation.
Downloaded & installed kies on the computer. I tried ODIN to push files but I failed at that too. Seems like Odin doesn't recognize the device.
As a result, I can't use my phone right now. I'm open for any suggestions for installing a stock rom and unrooting or rooting and installing a custom rom.
Thank you all very much in advance,
Click to expand...
Click to collapse
I have a nexus 7 2013 LTE build KOT49H
I initially managed to unlock and root using nrt 1.8...everything was perfect...there was some confusion getting adb setup though..
(for WugFresh...your instructions are fantastic but you should add a line to "check your device for the message to accept a connection for adb and select ok"...I found myself waiting and waiting, staring at my computer screen thinking that the nrt was hanging when all I needed to do was press "ok" on my device.)
Like I said...everything was perfect but I had to go one step further...
I then installed cyanogenmod 10.2 using twrp...tihs also went fine but I hated it and wanted to get back to my original google os. I had a really hard time getting adb set up once cyanogen was installed but once I finally did I was able to get back to stock again using nrt 1.8.
So now I'm back to stock image KOT49H. Everything runs fine and I see the unlocked logo when I boot so I assume I'm still unlocked.
Here's the problem..
When I try to root now, (I always run the NRT driver test until I get "success" message first) my device hangs on the "Booting modified boot.img to enable..." message.
And I mean hangs...can't even power it down without popping the cover and disconnecting the battery! Thankfully this gets me back to a running device but I still want to root this thing.
Any idea what might be wrong or where I should go to from here?
Thanks for any help you can suggest!
Did you re-enable USB debugging? Another thing is to switch to PTP mode instead of MTP. If none of that is the issue, it may be drivers, fire up wugs toolkit, hook up your device, and click the button "Full Driver Installation Guide", skip to Step 3 tab, and run the "Full Driver Test", if it fails then you're going to need to run through the steps in that "Full Driver Installation Guide, going through each step.
Well all you need to do for root is flash supersu.zip binary. If you have twrp on your device, boot to recovery. When you power on, hold down the volume down button also. When in boot loader mode, select recovery. If its not booting, you could just wipe to factory reset. Flash your supersu zip you'll be good.
Sent from my Nexus 7 using xda app-developers app
mdamaged said:
Did you re-enable USB debugging? Another thing is to switch to PTP mode instead of MTP. If none of that is the issue, it may be drivers, fire up wugs toolkit, hook up your device, and click the button "Full Driver Installation Guide", skip to Step 3 tab, and run the "Full Driver Test", if it fails then you're going to need to run through the steps in that "Full Driver Installation Guide, going through each step.
Click to expand...
Click to collapse
Thanks for the response...
All these check...I do have to switch to PTP to get adb functional and I do get success on the full driver test before I try rooting...device still hangs at "Booting modified boot.img to enable running privileged commands" message and then wont power down without disconnecting battery...
Which recovery are you on stock or still on twrp? If still on twrp, you might want to try flashing the supersu.zip yourself, just get the latest SuperSU put it on your device, and boot into twrp and manually flash it like datallboy suggests, this eliminates the PC/drivers/usb connection as a possible issue.
If you are on stock recovery either flash twrp, or if you want to keep stock recovery, you can boot into twrp temporarily without replacing the stock recovery.
datallboy said:
Well all you need to do for root is flash supersu.zip binary. If you have twrp on your device, boot to recovery. When you power on, hold down the volume down button also. When in boot loader mode, select recovery. If its not booting, you could just wipe to factory reset. Flash your supersu zip you'll be good.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the suggestions...
I lost twrp when I went back to stock build.
Sorry...I'm real green at all of this...
You think I should:
power up to fastboot mode...select boot loader mode...then select recovery to see if it boots?
You need to be real clear for me, I'm a total newb
I would need a link to thorough instructions for wiping to factory reset and flashing the supersu.zip...I do have adt installed and have my path modified so that I can run instructions like "adb devices" in a command window but I'm unclear as to where to place files so they will be seen if I try to flash them via adt. (like I say...this is all new to me and I'm not even sure if that last sentence makes sense)
mdamaged said:
Which recovery are you on stock or still on twrp? If still on twrp, you might want to try flashing the supersu.zip yourself, just get the latest SuperSU put it on your device, and boot into twrp and manually flash it like datallboy suggests, this eliminates the PC/drivers/usb connection as a possible issue.
If you are on stock recovery either flash twrp, or if you want to keep stock recovery, you can boot into twrp temporarily without replacing the stock recovery.
Click to expand...
Click to collapse
Thanks for responding!
TWRP was wiped when I went back to stock build...I'm assuming I have stock recovery now but when your device freezes in fastboot mode and wont power down without pulling the battery you cable you gotta wonder if you have any recovery at all!!!
I'll need instruction on how to flash twrp again...but I believe that this is the step that WugFresh's NRT is trying to do when the device freezes.
SMELZBAD said:
Thanks for responding!
TWRP was wiped when I went back to stock build...I'm assuming I have stock recovery now but when your device freezes in fastboot mode and wont power down without pulling the battery you cable you gotta wonder if you have any recovery at all!!!
I'll need instruction on how to flash twrp again...but I believe that this is the step that WugFresh's NRT is trying to do when the device freezes.
Click to expand...
Click to collapse
I typed this up on the fly so pardon any mistakes, there's more than one way to do this, but I'm basing this on already having wugs toolkit installed and updated and configured for your device on the PC you're going to do this on.
Plug device in, enable USB debugging mode, connect to PC, verify you can access your device through the PC, get the latest UPDATE-SuperSU-v1.XX zip, save it to your device (in the root of the sdcard).
EDIT: OR, even better, you can just boot the device and download it with chrome or whatever and save it to the sdcard, then you can continue:
Open windows explorer and navigate to (assuming you picked the default install directory):
C:\Program Files (x86)\WugFresh Development\data
...in that window, hold down shift, right click, select "Open command windows here", in it, type:
adb devices
...if nothing shows up post back (screenshot would be nice), if your device shows up, then open another windows explorer window and navigate to:
C:\Program Files (x86)\WugFresh Development\data\Recovery_Custom\TWRP\
...and copy the img (mine is openrecovery-twrp-2.6.3.1-flo.img) file you see in there to the other explorer window I told you to open earlier, now assuming you put the SuperSU file on your device in the root folder of the device, you should be able to do:
fastboot boot openrecovery-twrp-2.6.3.1-flo.img
This should reboot your device and boot twrp (this method does not replace whatever recovery you have on there now).
If you want to flash twrp and replace your current recovery you'd want to do:
fastboot flash recovery openrecovery-twrp-2.6.3.1-flo.img
Then once in twrp recovery you can select flash file, navigate to the UPDATE-SuperSU-v1.XX.zip file on your device, select it, and swipe to flash, reboot, run/install busybox and see what happens..it will let you know if there is a problem with root.
mdamaged said:
I typed this up on the fly so pardon any mistakes, there's more than one way to do this, but I'm basing this on already having wugs toolkit installed and updated and configured for your device on the PC you're going to do this on.
Plug device in, enable USB debugging mode, connect to PC, verify you can access your device through the PC, get the latest zip, save it to your device (in the root of the sdcard).
Open windows explorer and navigate to (assuming you picked the default install directory):
C:\Program Files (x86)\WugFresh Development\data
...in that window, hold down shift, right click, select "Open command windows here", in it, type:
adb devices
...if nothing shows up post back (screenshot would be nice), if your device shows up, then open another windows explorer window and navigate to:
C:\Program Files (x86)\WugFresh Development\data\Recovery_Custom\TWRP\
...and copy the img (mine is openrecovery-twrp-2.6.3.1-flo.img) file you see in there to the other explorer window I told you to open earlier, now assuming you put the SuperSU file on your device in the root folder of the device, you should be able to do:
fastboot boot openrecovery-twrp-2.6.3.1-flo.img
This should reboot your device and boot twrp (this method does not replace whatever recovery you have on there now).
If you want to flash twrp and replace your current recovery you'd want to do:
fastboot flash recovery openrecovery-twrp-2.6.3.1-flo.img
Then once in twrp recovery you can select flash file, navigate to the UPDATE-SuperSU-v1.XX.zip file on your device, select it, and swipe to flash, reboot, run busybox and see what happens.
Click to expand...
Click to collapse
Thanks a ton for the instruction!
I'm starting to make sense of this.
Found some other instruction for getting twrp back on the device which I think I'll try before flashing the superSU:
They're exactly what you're describing. I've also figured out where the flashboot.exe stuff is on my computer and added twp.img file there. I'' try getting twrp on and then I'll flash the superSU via twrp.
It'll probably be tomorrow before I get a chance to try all this but I'll be sure to post back once I do.
I'm still in the dark as to why missing this superSU thingy would be causing the device to freeze up the way it does when I try to root using WugFresh's NRT...I thought that flashing twrp and superSU is what the NRT is trying to do when it tries to root my device???
Anyway gtg...thanks all for assisting...I'll post back after the flash attempts...hopefully with happy news!
SMELZBAD said:
Thanks a ton for the instruction!
I'm starting to make sense of this.
Found some other instruction for getting twrp back on the device which I think I'll try before flashing the superSU:
They're exactly what you're describing. I've also figured out where the flashboot.exe stuff is on my computer and added twp.img file there. I'' try getting twrp on and then I'll flash the superSU via twrp.
It'll probably be tomorrow before I get a chance to try all this but I'll be sure to post back once I do.
I'm still in the dark as to why missing this superSU thingy would be causing the device to freeze up the way it does when I try to root using WugFresh's NRT...I thought that flashing twrp and superSU is what the NRT is trying to do when it tries to root my device???
Anyway gtg...thanks all for assisting...I'll post back after the flash attempts...hopefully with happy news!
Click to expand...
Click to collapse
Wug's toolkit is doing exactly that, the main difference in doing it manually is we get to see where the problem is.
If this fails then I would probably say you should backup anything on your device you don't want wiped, and try one click restore and try rooting again.
Good luck.
mdamaged said:
I typed this up on the fly so pardon any mistakes, there's more than one way to do this, but I'm basing this on already having wugs toolkit installed and updated and configured for your device on the PC you're going to do this on.
Plug device in, enable USB debugging mode, connect to PC, verify you can access your device through the PC, get the latest UPDATE-SuperSU-v1.XX zip, save it to your device (in the root of the sdcard).
EDIT: OR, even better, you can just boot the device and download it with chrome or whatever and save it to the sdcard, then you can continue:
Open windows explorer and navigate to (assuming you picked the default install directory):
C:\Program Files (x86)\WugFresh Development\data
...in that window, hold down shift, right click, select "Open command windows here", in it, type:
adb devices
...if nothing shows up post back (screenshot would be nice), if your device shows up, then open another windows explorer window and navigate to:
C:\Program Files (x86)\WugFresh Development\data\Recovery_Custom\TWRP\
...and copy the img (mine is openrecovery-twrp-2.6.3.1-flo.img) file you see in there to the other explorer window I told you to open earlier, now assuming you put the SuperSU file on your device in the root folder of the device, you should be able to do:
fastboot boot openrecovery-twrp-2.6.3.1-flo.img
This should reboot your device and boot twrp (this method does not replace whatever recovery you have on there now).
If you want to flash twrp and replace your current recovery you'd want to do:
fastboot flash recovery openrecovery-twrp-2.6.3.1-flo.img
Then once in twrp recovery you can select flash file, navigate to the UPDATE-SuperSU-v1.XX.zip file on your device, select it, and swipe to flash, reboot, run/install busybox and see what happens..it will let you know if there is a problem with root.
Click to expand...
Click to collapse
Followed your instructions...everything went as it should until I got to:
fastboot boot openrecovery-twrp-2.6.3.1-deb.img
instead of rebooting the device I only got waiting for device message in command window...
is device supposed to be put in bootloader mode before entering this instruction maybe???
okay I got twrp to flash...took like .7 seconds so I guess it was already on there...
when I tried to flash UPDATESuperSU (and by flash I assume you mean install???)
I get:
Updating partition details...
E: Unable to open zip file.
Error flashing zip ' /sdcard/UPDATE-SuperSU-v1.89.zip
Updating partition details...
and the in red underneath: Failed
and the 3 twrp button choices of home Wipe cache/davlik and Reboot System
I selected reboot system and then got message "this device is not rooted swipe to install SuperSU now
I swiped...and the system has rebooted and I now have SuperSU installer app icon in apps bit after running root checker I get device is not properly rooted message
I then ran the SuperSU installer app and it gave me an option to update via the play store...which I did...then ran SuperuserSU which was now updated and installed and it completed rooting...after rebooting the device Root Checker now shows device properly rooted!
THANKS A TON GUYS!!!
SMELZBAD said:
okay I got twrp to flash...took like .7 seconds so I guess it was already on there...
when I tried to flash UPDATESuperSU (and by flash I assume you mean install???)
I get:
Updating partition details...
E: Unable to open zip file.
Error flashing zip ' /sdcard/UPDATE-SuperSU-v1.89.zip
Updating partition details...
and the in red underneath: Failed
and the 3 twrp button choices of home Wipe cache/davlik and Reboot System
I selected reboot system and then got message "this device is not rooted swipe to install SuperSU now
I swiped...and the system has rebooted and I now have SuperSU installer app icon in apps bit after running root checker I get device is not properly rooted message
I then ran the SuperSU installer app and it gave me an option to update via the play store...which I did...then ran SuperuserSU which was now updated and installed and it completed rooting...after rebooting the device Root Checker now shows device properly rooted!
THANKS A TON GUYS!!!
Click to expand...
Click to collapse
Curious. It sounds like a permissions problem, not sure if fix permissions would have helped (no need to try if it's working as it should).
Oh well, glad to help and that it's sorted.
mdamaged said:
Curious. It sounds like a permissions problem, not sure if fix permissions would have helped (no need to try if it's working as it should).
Oh well, glad to help and that it's sorted.
Click to expand...
Click to collapse
Ya...something likely still abit wacky...I'll be sure to post if anything weird starts happening but for now all is good...I'm definitely rooted though...I was just able to mount a flash drive via Stick Mount and run a video off of it!
Ive been reviewing some of the threads on this forum for 2.3.3.0 and this doesn't look good. In my case I went ahead and downloaded Android 5.1.1 and transferred the zip file to the nexus (ADB Driver) as well as usb otg. I attempted to install the zip file but keep getting the message: "error flashing zip" (log is attached). After the first failed attempt I went ahead and removed then re-downloaded 5.1.1 again but still failed, Ive tried Android 4.1.2 but had the same result. Ive went to TWRPs site and attempted to perform a recovery using TWRP 2.8.7.0 but the recovery in TWRP 2.3.3.0 wont recognize any images. One last resort was to load from ADB SIDELOAD within TWRP 2.3.3.0 but still fails. Are there any other troubleshooting steps that could be performed?
Hi!
Try to flash any stock rom via NRT.
Heres what im getting when trying to communicate with the device: "ADB Device not found". Attached are the images of communication with the device while in TWRP 2.3.3.0 recovery mode, Is there a way to get NRT to recognize the device during the bootloader?
EDIT: I Found the FAQ, I will need to do some more research.
pepper55 said:
Is there a way to get NRT to recognize the device during the bootloader?
Click to expand...
Click to collapse
Hi!
Of course it is, just boot your tablet to fastboot mode, and choose in NRT Current status: Soft-Bricket/Bootloop.
If you really have a Nexus 7 (2012), you're using the wrong factory image (and you're in the wrong forum).
pavel2084 said:
Hi!
Of course it is, just boot your tablet to fastboot mode, and choose in NRT Current status: Soft-Bricket/Bootloop.
Click to expand...
Click to collapse
Kept trying with fastboot mode but ADB still wont recognize the device. When i boot in TWRP it does recognize the device just fine. Any other suggestions?
pepper55 said:
Kept trying with fastboot mode but ADB still wont recognize the device. When i boot in TWRP it does recognize the device just fine. Any other suggestions?
Click to expand...
Click to collapse
Hi, pepper55.
In recovery you can use ADB sideload
Simple ADB (not sideload) doesn't work without OS.
Use fastboot for the soft-bricked device.
Try to restore your tablet using stock google image, and "Flashing Instructions".
[Q] fastboot flash system system.img FAILED <remote: Permission denied>, need fix
Hey,
I have a ZE551ML and want to install CM. I am following the guide here. I have run into a problem on the first step which points to the guide here. At step 7 of this guide it has me use the command: fastboot flash system system.img. This fails with the error in the title of this post: FAILED <remote: Permission denied>. I have been googling this and no one has a concrete solution. Currently my phone will not even boot as the three fastboot commands before this one worked just fine and replaced the files. Any help would be greatly appreciated!
Cheers,
Eric.
Even though it'll say permission denied, flashing recovery WILL work. From there you can either flash a custom ROM (from twrp) or reflash stock firmware (through stock recovery).
That's the only fix I've found. To flash a usable ROM and boot into it. May need to turn on USB debugging in dev options. But after doing those two things, fastboot will stop with the permission denied issues.
Hey, thanks for the quick reply.
Currently the phone does not boot at all.
What do you mean by flashing recovery?
When I enter recovery mode at the moment it says applying update and then gives me the android on its side with the red triangle and error! below it.
So i can't currently flash though recovery mode as far as I can tell.
eric_lensherr said:
Hey, thanks for the quick reply.
Currently the phone does not boot at all.
What do you mean by flashing recovery?
When I enter recovery mode at the moment it says applying update and then gives me the android on its side with the red triangle and error! below it.
So i can't currently flash though recovery mode as far as I can tell.
Click to expand...
Click to collapse
Found a guide here dealing with this error, working on it.
Hey,
So I got my phone unbricked by flashing the recovery with the stock ASUS firmware "ASUS ZenFone 2=ZE551ML(Z00AD/Z00ADA/Z00ADB/Z00ADC) software Image: V2.19.40.22 for WW SKU only" available at the ASUS official website and following a guide at an outside link that I can't post.
Now, I have enabled developer mode and turned on USB debugging but am now getting the permission denied on all fastboot commands of the OTA guide, step 7.
Does anyone know a good next step?
Hey, managed to root the phone with: Temporary CWM
After setting USB debug on did you connect the phone to PC via USB and authenticated the PC? When you connect the phone to PC via USB with debugging on, it should pop up a window on the phone after a few seconds asking you for permission for the PC. You can checkmark the box that says always trust this computer's RSA fingerprints or something along those lines.
Hope this helps!
rlaw said:
After setting USB debug on did you connect the phone to PC via USB and authenticated the PC? When you connect the phone to PC via USB with debugging on, it should pop up a window on the phone after a few seconds asking you for permission for the PC. You can checkmark the box that says always trust this computer's RSA fingerprints or something along those lines.
Hope this helps!
Click to expand...
Click to collapse
Yes, I did do this but I have now checked the check mark to make it always trust my computer. I then booted into fastboot but still get permission denied despite having root through CWM and having this checked off.
When I got root through CWM by the fastboot tethered recovery it gave me permission denied on all steps but it still booted into CWM recovery. I was then able to install SuperSU to root it, though it gave me an error, and I used Root Checkerr to see if the phone was rooted. It says it is but I am still unable to flash any images onto the phone since I re-installed the stock firmware.
I'm super confused about this whole thing, IDK what to do now.
Flash stock recovery again and adb sideload the stock firmware all over.
This is the latest up-to-date 2.20.40.59 firmware: http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE551ML/UL-Z00A-WW-2.20.40.59-user.zip
If that doesn't work then idk. You can Google the permission denied errors for fastboot like I did and there are various possible problems/solutions.
So, none of this is working.
I installed the latest firmware as you suggested and got root again by using Temporary CWM. However despite anything I try (been googling for hours with little help found) I cannot get the phone to let me flash anything I always get the permission denied error.
eric_lensherr said:
So, none of this is working.
I installed the latest firmware as you suggested and got root again by using Temporary CWM. However despite anything I try (been googling for hours with little help found) I cannot get the phone to let me flash anything I always get the permission denied error.
Click to expand...
Click to collapse
You can still flash recovery via fastboot even though it'll say permission denied it works. That's all you really need to do as you can install stock firmware via stock recovery or flash ROMs and whatever else through twrp recovery.
rlaw said:
You can still flash recovery via fastboot even though it'll say permission denied it works. That's all you really need to do as you can install stock firmware via stock recovery or flash ROMs and whatever else through twrp recovery.
Click to expand...
Click to collapse
How can i tell if twrp recovery is successfully installed?
Hey, took a few days to cool off.
So it does seem I can replace recovery even though it says permission denied. I do this by using fastboot to flash the recovery, then from the bootloader on the phone I select restart bootloader and then when the bootloader re-appears I enter recovery mode ( I do this to prevent the possible replacing of the custom recovery by the stock OS). However recovery mode never boots when the latest twrp recovery is on the phone, I just end up back in the bootloader. When I flash the stock recovery back on this method successfully enters recovery mode. This also occurs if I just directly enter recovery mode after flashing twrp recovery.
Any thoughts?
eric_lensherr said:
So, none of this is working.
I installed the latest firmware as you suggested and got root again by using Temporary CWM. However despite anything I try (been googling for hours with little help found) I cannot get the phone to let me flash anything I always get the permission denied error.
Click to expand...
Click to collapse
Same here. I'm using elevated cmd, and fastboot is recognizing my device. But I can't flash anything, can't erase cahce, can't reformat partitions. Always failed due to permissions. And I'm stuck in a bootloop, and can't get to recovery (it just goes back into the bootloop when I try). Literally the only avenue I have to interact with this phone is fastboot, and I can't do anything with it.
My Samsung Galaxy Nexus is stuck in this boot loop, where it first boots normally and then after about 10 seconds shuts down and reboots. I have tried installing a stockrom using adb sideload, but it returns "E: signature verification failed". I researched the problem and apparently verification can be disable using RomManager. I tried to flash the app using adb install, but this returns "error: closed". The device is displayed as a sideload device when i type in "adb devices", but the Nexus Root Toolkit does not detect any adb fastboot devices, although it does detect that a phone is connected.
Model Type according to Nexus Root Toolkit:
Galaxy Nexus
GSM/HSPA+
Android *.*.* Any
I am frankly at a loss, as i have no prior experience with rooting etc., so i would be grateful for any advice.
The same problem started, too. I've tried every method, but the problem is not solved. What should we do ?
Try adb reboot bootloader or adb reboot recovery. If adb doesn't accept any reboot commands, try going to the bootloader and get into recovery from there (or, install or boot a custom recovery) and install a different ROM.