Hi essential phone owners, I'm hoping you are willing to help me out.. Anyway, i used adb reboot bootloader for fastboot access after I enabled OEM unlock from the developer options. The device state is LOCKED. I then typed fastboot devices and received no permissions (verify udev rules). Does that mean I'm stuck on stock?
dirtyreturn said:
Hi essential phone owners, I'm hoping you are willing to help me out.. Anyway, i used adb reboot bootloader for fastboot access after I enabled OEM unlock from the developer options. The device state is LOCKED. I then typed fastboot devices and received no permissions (verify udev rules). Does that mean I'm stuck on stock?
Click to expand...
Click to collapse
What type of computer?
Hopefully, not using cable that came with the phone. Don't use it for flashing.
What are you trying to do?
tech_head said:
What type of computer?
Hopefully, not using cable that came with the phone. Don't use it for flashing.
What are you trying to do?
Click to expand...
Click to collapse
Thanks for your questions. I am using Ubuntu 18 I believe. I have a nexus 6p also, and adb/fastboot commands worked just fine with that phone. What i would like to do successfully is to unlock the bootloader and critical partition, flash twrp, and finally be able to flash AICP/Magisk.
Edit- from computer to phone I am using the extra type C USB cable that came with the 6p. And I must note that the essential is found using command adb devices. And command adb reboot bootloader gets me to the point of fastboot.
Ubuntu ?
sudo fastboot devices
I'm using Linux Mint, so basically Ubuntu. I created a file under /etc/udev/rules.d and put this line in it:
SUBSYSTEM=="usb", ATTR{idVendor}=="2e17", MODE="0666", GROUP="plugdev"
(My login ID is in the plugdev group.)
I'm able to execute adb and fastboot without needing sudo.
Related
So my dad went out and bought a nakasig/tilapia it's running Android 4.2.1 and bootloader is 4.13. Having just updated my razor/flo via fastboot everything was setup and working. "adb reboot bootloader" reboots the nakasig/tilapia into fastboot mode and "fastboot devices" shows the nakasig/tilapia serial number. Every other fastboot command just hangs there and does nothing. "fastboot oem unlock" does not prompt me to unlock bootloader. "fastboot reboot" doesn't even reboot the tablet. I use Linux so I figured I would try Windows following the thread sticky'd in this forum http://forum.xda-developers.com/showthread.php?t=2175086 same problem adb works fastboot will list the device but can't do anything with it. "fastboot getvar all" did give me an error however "FAILED (command write failed (Unknown error))" all the other commands just hang there doing nothing saying nothing. Having tried Windows and Linux setups which I have used on my other Nexus devices without issue I am starting to think its an issue with the bootloader maybe I need some older version of fastboot.
Is there a way to flash bootloader from inside Android or Recovery? I can use Towelroot to root the tablet then flash TWRP from Android and boot into TWRP but I don't think you can flash a bootloader from there or unlock the bootloader can you?
Edit: according to http://forum.xda-developers.com/showthread.php?t=2068207 the nakasig/tilapia bootloader is encrypted so you can't flash or unlock it without fastboot.
OK so you have a 2013 N7 that does not have this problem, but your dad's 2012 does. Two different pieces of hardware.
Could it be a driver issue? Sometimes when the drivers are not talking to it correctly you get these flaky results. Different USB cable/port?
Theoretically there is a flash all command you can use to flash an update of the whole thing including the bootloader without it being unlocked. However if you are getting write errors then you should really be cautious because that could just fry it instead of fixing it.
dextroamphetamine said:
So my dad went out and bought a nakasig/tilapia it's running Android 4.2.1 and bootloader is 4.13. Having just updated my razor/flo via fastboot everything was setup and working. "adb reboot bootloader" reboots the nakasig/tilapia into fastboot mode and "fastboot devices" shows the nakasig/tilapia serial number. Every other fastboot command just hangs there and does nothing. "fastboot oem unlock" does not prompt me to unlock bootloader. "fastboot reboot" doesn't even reboot the tablet. I use Linux so I figured I would try Windows following the thread sticky'd in this forum http://forum.xda-developers.com/showthread.php?t=2175086 same problem adb works fastboot will list the device but can't do anything with it. "fastboot getvar all" did give me an error however "FAILED (command write failed (Unknown error))" all the other commands just hang there doing nothing saying nothing. Having tried Windows and Linux setups which I have used on my other Nexus devices without issue I am starting to think its an issue with the bootloader maybe I need some older version of fastboot.
Is there a way to flash bootloader from inside Android or Recovery? I can use Towelroot to root the tablet then flash TWRP from Android and boot into TWRP but I don't think you can flash a bootloader from there or unlock the bootloader can you?
Edit: according to http://forum.xda-developers.com/showthread.php?t=2068207 the nakasig/tilapia bootloader is encrypted so you can't flash or unlock it without fastboot.
Click to expand...
Click to collapse
cmstlist said:
OK so you have a 2013 N7 that does not have this problem, but your dad's 2012 does. Two different pieces of hardware.
Click to expand...
Click to collapse
Correct.
cmstlist said:
Could it be a driver issue? Sometimes when the drivers are not talking to it correctly you get these flaky results.
Click to expand...
Click to collapse
ADB and fasboot use the same drivers don't they? While in Anroid adb works fine I can adb shell I can adb push/get I can adb reboot.
cmstlist said:
Different USB cable/port?
Click to expand...
Click to collapse
Tried every cable and port I have. Different computers even.
cmstlist said:
Theoretically there is a flash all command you can use to flash an update of the whole thing including the bootloader without it being unlocked. However if you are getting write errors then you should really be cautious because that could just fry it instead of fixing it.
Click to expand...
Click to collapse
NONE of the fastboot commands work except "fastboot devices"
dextroamphetamine said:
Correct.
ADB and fasboot use the same drivers don't they? While in Anroid adb works fine I can adb shell I can adb push/get I can adb reboot.
Click to expand...
Click to collapse
No, AFAIK they're different drivers, and different devices often require a distinct driver install too.
cmstlist said:
No, AFAIK they're different drivers, and different devices often require a distinct driver install too.
Click to expand...
Click to collapse
Got any sources on that info?
WOW
weird! really weird!
I really don't know what the issue, the fact that it happens on Linux and on Windows makes me think to an hardware realted issue, unfortunately..
As long as I know adb and fastboot do not use exactly the same drivers, but you download and install them together, so it should n not be a problem, this one..
The only think I can suggest you atm is to try with Linux by logging in as superuser (su). On my slackware with my "normal" user adb works as usual, but if I try to use fastboot the terminal says me No permissions..
I hope someway your distro has the same issue, even if your fastboot devices success!
So login as superuser and try to use fastboot. If you do not install it in /bin partition you should have to locate its directory and then use
./fastboot devices
or any other command but with ./fastboot instead of fastboot..
hope it helps.. I really hope!!
For that matter, on a whim... when you open a command prompt in Windows to adb to your device, try running Command Prompt as an Administrator. Sometimes Windows is weird like that.
Please keep questions in the Q&A section. Development sections are for development only.
Thread moved to Q&A.
Thanks,
Darth
Forum Moderator
OK so I have an issue that I just cannot seem to fix. I've followed Max Lee's guide to unlocking the bootloader, obtaining root, and getting twrp. I've followed the written and video instructions to the t and a few guides in here, I have installed and updated the proper drivers and sdk tools, but my hitch is when I type the "fastboot oem Unlock" command, it says it finishes but my device doesn't reboot and ask if I want to proceed to unlock my bootloader, instead it just stays on the fastboot logo and does nothing until I restart it. This happens on both my mac and my pc so I'm not sure what the issue is I have usb debugging enabled and the allow oem Unlock slider is in the on position, any help or advice 8s greatly appreciated, thank you.
Sent from my ONE A2005 using Tapatalk
do you run an actual version of sdk-tools? fastboot recognized your phone, right? You can test it with following command: fastboot devices
Output is something like this:
33a0cde4 fastboot
Click to expand...
Click to collapse
nevermind i just fixed it, thanks
Hi everyone,
I came from getting my nexus 6P and I wanted to install twrp and etc...
So I went to into developer mode, I check USB debugging and enable OEM unlock.
I head to my computer open a commend prompt that's has the fastboot and adb drivers. I connected my nexus 6p and I enter the following commends
Adb reboot bootloader
Fastboot devices
(Showed me my devices)
Fastboot OEM unlock
And just after I hit that I got the following
...
Failed ( remote : commend not found)
Finish 0.18
Does anyone know what I did wrong.
jonnyszt said:
Hi everyone,
I came from getting my nexus 6P and I wanted to install twrp and etc...
So I went to into developer mode, I check USB debugging and enable OEM unlock.
I head to my computer open a commend prompt that's has the fastboot and adb drivers. I connected my nexus 6p and I enter the following commends
Adb reboot bootloader
Fastboot devices
(Showed me my devices)
Fastboot OEM unlock
And just after I hit that I got the following
...
Failed ( remote : commend not found)
Finish 0.18
Does anyone know what I did wrong.
Click to expand...
Click to collapse
Your answer is here! http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Thank you.
Sent from my Nexus 6P using Tapatalk
So the title pretty much says it all..
I have a Nexus 6P
Last night It got stuck in a bootloop. The only access I have to the device is it will launch into the boot loader. But no options work, factory, recovery do not work. USB Debugging was turned off, OEM unlock is turned off, developer options are on. But I have zero access to the android only the boot loader screen. Fastboot does work but it gives me "DEVICE IS LOCKED" on most commands. Oh and the icing on top is I'm on Android N 7.0 beta.
I've ordered a replacement, but I have all my personal data on the phone. I'd like to either fix it and get it working so I can get all my stuff off it. Or at very least try to wipe the device.
Also Fastboot Format, erase, do not work. It says Locked Device. HELP PLEASE. I can answer any more questions.
can you adb pull and push files?
If so, on your Windows machine, type this:
Code:
cd ~/.android
adb push adbkey.pub /data/misc/adb/adb_keys
It won't connect via ADB only Fastboot.
adb devices
List of devices attached
Wiltron said:
can you adb pull and push files?
If so, on your Windows machine, type this:
Code:
cd ~/.android
adb push adbkey.pub /data/misc/adb/adb_keys
Click to expand...
Click to collapse
Not sure if this will work, but try downloading the latest TWRP img file from their website, then running this command:
Code:
fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img
If you get it into recovery, then pull the files you need for a backup, and then use adb push to push a new ROM to the device.
Make sure you format all partitions/data.
Note: adb push should work better in recovery, vs. the command line that didn't work earlier.
What do you mean by "recovery doesn't work"? Please explain what happens when you boot into it.
Sent from my Nexus 5X using Tapatalk
an276123 said:
It won't connect via ADB only Fastboot.
adb devices
List of devices attached
Click to expand...
Click to collapse
Why not download stock Marshmallow and attempt to flash?
https://developers.google.com/android/nexus/images#angler
A locked bootloader should still allow you to flash a signed ROM.
An unlocked bootloader means you can boot and install anything.
Rule #1 If you are running *ANYTHING* other than an OTA, unlock the bootloader!
Unlocking the bootloader DOES NOT void the warranty.
Final note, it's encrypted. If you can't get into it, nobody interested in your data can.
Even if they can, it's block level encrypted. Who cares, no need to wipe.
SlimSnoopOS said:
What do you mean by "recovery doesn't work"? Please explain what happens when you boot into it.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
When I click down and then power on recovery it should go into the recovery. But instead it just gets back into an endless loop of starting.
tech_head said:
Why not download stock Marshmallow and attempt to flash?
https://developers.google.com/android/nexus/images#angler
A locked bootloader should still allow you to flash a signed ROM.
An unlocked bootloader means you can boot and install anything.
Rule #1 If you are running *ANYTHING* other than an OTA, unlock the bootloader!
Unlocking the bootloader DOES NOT void the warranty.
Final note, it's encrypted. If you can't get into it, nobody interested in your data can.
Even if they can, it's block level encrypted. Who cares, no need to wipe.
Click to expand...
Click to collapse
On a side note. I am running stock android N 7.0 and it was OTA. I just didn't think to unlock it since it was all done OTA.
Thats what I'm thinking too on the data.
Wiltron said:
Not sure if this will work, but try downloading the latest TWRP img file from their website, then running this command:
Code:
fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img
If you get it into recovery, then pull the files you need for a backup, and then use adb push to push a new ROM to the device.
Make sure you format all partitions/data.
Note: adb push should work better in recovery, vs. the command line that didn't work earlier.
Click to expand...
Click to collapse
When I try to run this I get this.
downloading 'boot.img'...
OKAY [ 0.397s]
booting...
FAILED (remote: unlock device to use this command)
finished. total time 0.421s
That means you need to unlock your bootloader, which should already be done, or if it's not, it will erase your internal storage.
You can unlock your bootloader, or try too, with
Code:
fastboot flashing unlock
Wiltron said:
That means you need to unlock your bootloader, which should already be done, or if it's not, it will erase your internal storage.
You can unlock your bootloader, or try too, with
Code:
fastboot flashing unlock
Click to expand...
Click to collapse
He said OEM unlock is turned off so that won't work.
So any luck to boot this sucker ? Don't even have stock recovery ..
have you tried "fastboot boot boot.img" from the correct factory image ?
Boot loop plus no recovery equals BLOD. Sorry but likely you are done.
I want to downgrade back to the last version of the sprint nougat firmware. I want to use the phone as my daily driver again, I cannot afford to have any surprise bugs that a beta oreo might bring.
1 - I am using a mac that is currently updated to macOs High Sierra 10.13.3
2 - I have the latest android platform tools downloaded released in december
3 - I have no problems executing ./adb devices or ./adb reboot bootloader commands
4 - I have no problems executing ./fastboot devices or ./fastboot flashing unlock/./fastboot flashing lock commands
5 - I cannot how ever execute the ./flashall.sh command when I do it returns the message permission denied.
The phone is currently on the latest oreo beta build, I have tried every firmware that has been listed on essentials dev page. Each time I try ./flashall.sh I get permission denied. I have reached out to essential for the guide to downgrading but when you have an actual problem their response time seems to increase 10 fold.
6 - To upgrade to the beta I used the side load method, I put the phone in to recovery mode and select the apply update from adb. In the terminal I would run ./adb flash update.zip.(I changed the firmware name to update.zip)
7 - Can the apply update from adb method work to downgrade to an earlier firmware, I want to try but I dont want to risk bricking the phone. Then I will have a titanium and ceramic paper weight for my desk .
swagglepuff said:
I want to downgrade back to the last version of the sprint nougat firmware. I want to use the phone as my daily driver again, I cannot afford to have any surprise bugs that a beta oreo might bring.
1 - I am using a mac that is currently updated to macOs High Sierra 10.13.3
2 - I have the latest android platform tools downloaded released in december
3 - I have no problems executing ./adb devices or ./adb reboot bootloader commands
4 - I have no problems executing ./fastboot devices or ./fastboot flashing unlock/./fastboot flashing lock commands
5 - I cannot how ever execute the ./flashall.sh command when I do it returns the message permission denied.
The phone is currently on the latest oreo beta build, I have tried every firmware that has been listed on essentials dev page. Each time I try ./flashall.sh I get permission denied. I have reached out to essential for the guide to downgrading but when you have an actual problem their response time seems to increase 10 fold.
6 - To upgrade to the beta I used the side load method, I put the phone in to recovery mode and select the apply update from adb. In the terminal I would run ./adb flash update.zip.(I changed the firmware name to update.zip)
7 - Can the apply update from adb method work to downgrade to an earlier firmware, I want to try but I dont want to risk bricking the phone. Then I will have a titanium and ceramic paper weight for my desk .
Click to expand...
Click to collapse
You need to unlock the boot loader.
You will need to go into developer mode and check the oem unlock.
In fast boot you need to unlock and unlock_critical.
They you should be able to revert.
tech_head said:
You need to unlock the boot loader.
You will need to go into developer mode and check the oem unlock.
In fast boot you need to unlock and unlock_critical.
They you should be able to revert.
Click to expand...
Click to collapse
Awesome, no where in essentials guide does it ever mention unlock_critical, all it says it to use fastboot flashing unlock. Even then it still says permission denied. After I unlock the bootloader i will go back to the fastboot menu and the run ./fastboot flashing unlock_critical or is it ./fastboot unlock_critical
tech_head said:
You need to unlock the boot loader.
You will need to go into developer mode and check the oem unlock.
In fast boot you need to unlock and unlock_critical.
They you should be able to revert.
Click to expand...
Click to collapse
Here is my exact steps of what I just did.
open terminal set directory to required folder
./adb devices- recognizes phone and shows model number
./adb reboot bootloader- executes no problem now in fastboot mode
./fastboot devices- recognizes device and show model number
./fastboot flashing unlock-prompt screen shows on PH-1 select yes for unlocking bootloader
Do a quick set up and get back to the fastboot screen.
./fastboot flashing unlock_critical-prompt screen shows on PH-1 select yes for unlocking bootloader
Do a quick set up again, get back to the fastboot screen
./flashall.sh-permission denied
In the fastboot menu on the phone it says status is unlocked. Up next the spectacular smashing on a essential phone with a hammer!!!!!!!!!!!!!!!!
swagglepuff said:
Here is my exact steps of what I just did.
open terminal set directory to required folder
./adb devices- recognizes phone and shows model number
./adb reboot bootloader- executes no problem now in fastboot mode
./fastboot devices- recognizes device and show model number
./fastboot flashing unlock-prompt screen shows on PH-1 select yes for unlocking bootloader
Do a quick set up and get back to the fastboot screen.
./fastboot flashing unlock_critical-prompt screen shows on PH-1 select yes for unlocking bootloader
Do a quick set up again, get back to the fastboot screen
./flashall.sh-permission denied
In the fastboot menu on the phone it says status is unlocked. Up next the spectacular smashing on a essential phone with a hammer!!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
Do you have the script file set to execute?
Sent from my PH-1 using XDA Labs
avd said:
Do you have the script file set to execute?
Sent from my PH-1 using XDA Labs
Click to expand...
Click to collapse
That was my next question.
chmod +x flash-all.sh