Please help me to unlock the bootloader, access the network. I use USB a - USB A. after the update, only the logo is loaded. Enable debugging via usb is not possible
PS D:\Amazon\platform-tools> adb reboot bootloader
* daemon not running; starting now at tcp:5037
* daemon started successfully
error: no devices/emulators found
PS D:\Amazon\platform-tools> fastboot devices
7090020141650DN4 fastboot
PS D:\Amazon\platform-tools> fastboot reboot bootloader
rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.000s
PS D:\Amazon\platform-tools> fastboot devices
7090020141650DN4 fastboot
PS D:\Amazon\platform-tools> fastboot oem device-info
(bootloader) Device tampered: false
OKAY [ 0.000s]
Finished. Total time: 0.000s
PS D:\Amazon\platform-tools> fastboot -w
Finished. Total time: 0.016s
PS D:\Amazon\platform-tools> fastboot getvar all
all:
Finished. Total time: 0.000s
PS D:\Amazon\platform-tools>
If your FTV is on FireOS 5 (505 and up), then forget about this sh*t. No unlock possible^^
Sus_i said:
If your FTV is on FireOS 5 (505 and up), then forget about this sh*t. No unlock possible^^
Click to expand...
Click to collapse
I don't even know what version is out there. Given.
Wanted to add that fastboot works!!!
Maybe have the option of using test points to unlock?
Boot the FTV1 up (with disabled updates) and look in the settings for your fireOS version. Afaik the devices with 51.xxx (5 digits) can unlocked/rooted with software/adb.
FireOS 5 can´t bootloader unlocked, because bootloader checks fuses (5.0.5 and up). Last software rootable version is 5.0.5.
Aside from fireOS, if you build a low voltage emmc reader and solder wires to a few pins onto the board of the FTV, you can flash the emmc with twrp (for locked bootloader) and a prerooted rom from rbox.
https://www.exploitee.rs/index.php/Exploitee.rs_Low_Voltage_e-MMC_Adapter
Sus_i said:
Boot the FTV1 up (with disabled updates) and look in the settings for your fireOS version. Afaik the devices with 51.xxx (5 digits) can unlocked/rooted with software/adb.
FireOS 5 can´t bootloader unlocked, because bootloader checks fuses (5.0.5 and up). Last software rootable version is 5.0.5.
Aside from fireOS, if you build a low voltage emmc reader and solder wires to a few pins onto the board of the FTV, you can flash the emmc with twrp (for locked bootloader) and a prerooted rom from rbox.
https://www.exploitee.rs/index.php/Exploitee.rs_Low_Voltage_e-MMC_Adapter
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have it only boots to the logo and all to go to settings is not possible. I used a usb a-usb a cable to connect. So I have a prefix is defined in the device Manager as a fastboot device, and as adb is not. Will you be able to specify on the scheme to specify the contacts to which you want to connect and more detailed instructions for recovery?
Take a look at the gtv hackers, you can see the pin out of the adapter and the pins on the board. There is also a video.
https://www.exploitee.rs/index.php/Amazon_FireTV
If you get this adapter (seems sold out/ you need to build it on your own) you can read/write to all partitions on the emmc (with a pc running linux), flash a new recovery and so on.
But maybe you find a way to reset the FTV on this site?
http://www.aftvnews.com/how-to-unbrick-and-prevent-bricking-an-amazon-fire-tv/
Sus_i said:
Take a look at the gtv hackers, you can see the pin out of the adapter and the pins on the board. There is also a video.
https://www.exploitee.rs/index.php/Amazon_FireTV
If you get this adapter (seems sold out/ you need to build it on your own) you can read/write to all partitions on the emmc (with a pc running linux), flash a new recovery and so on.
But maybe you find a way to reset the FTV on this site?
http://www.aftvnews.com/how-to-unbrick-and-prevent-bricking-an-amazon-fire-tv/
Click to expand...
Click to collapse
Unfortunately, I don't have a low voltage eMMC adapter and don't know if I can find one. With UART you can unlock something? Uart is more available to me.
Don´t know, but don´t think so.
Sus_i said:
Don´t know, but don´t think so.
Click to expand...
Click to collapse
And how do you know why it doesn't switch to adb mode? Only fastboot works for me.
smurat_82 said:
And how do you know why it doesn't switch to adb mode? Only fastboot works for me.
Click to expand...
Click to collapse
I would try a usb hub with a usb keyboard for reset if the reset via remote doesn´t work.
You can look in the bueller bootloader unlock threads here on xda (fire tv android development section), maybe the fastboot commands work for you.
Sus_i said:
I would try a usb hub with a usb keyboard for reset if the reset via remote doesn´t work.
You can look in the bueller bootloader unlock threads here on xda (fire tv android development section), maybe the fastboot commands work for you.
Click to expand...
Click to collapse
Unfortunately, did not help a full reset Alt+i+Print screen, and adb is not available, only fastboot mode
Maybe try this:
fastboot erase data
fastboot erase cache
Sus_i said:
Maybe try this:
fastboot erase data
fastboot erase cache
Click to expand...
Click to collapse
I tried, didn't help
PS D:\Amazon\platform-tools> fastboot devices
7090020141650DN4 fastboot
PS D:\Amazon\platform-tools> fastboot erase data
Erasing 'data' FAILED (remote: 'erasing not allowed for locked hw')
Finished. Total time: 0.016s
PS D:\Amazon\platform-tools> fastboot erase cache
Erasing 'cache' FAILED (remote: 'erasing not allowed for locked hw')
Finished. Total time: 0.016s
PS D:\Amazon\platform-tools>
Probably only this method will help, thank you very much for your help
https://www.youtube.com/watch?v=IgC4iDzQ8gw&feature=youtu.be
You can try this.
https://forum.xda-developers.com/fire-tv/development/prerooted-stock-images-t2882337/post56987752#post56987752
Related
I seem to be unable to flash any recovery images using
Code:
fastboot flash recovery IMG
. When I put the tablet into fastboot mode, attach it to the computer using a microusb adapter and run the command, I get the following error:
Code:
sending 'recovery' (9158 KB)...
FAILED (data transfer failure (Protocol error))
finished. total time: 0.057s
If I repeat the command, any number of times, I get another error:
Code:
sending 'RECOVERY' (9158 KB)...
FAILED (command write failed (Bad file descriptor))
finished. total time: 0.000s
I've tried this with TWRP MultiROM and ClockworkMod Recovery. Why do I get this error? How can I troubleshoot/solve this in order to flash recovery images?
Device: (original) Google Nexus 7 16GB WIFI
Android Version: 4.3 (stock)
Kernel Version: 3.1.10-g1e8b3d8
PC Software: Ubuntu 13.04 with android-tools-fastboot 4.2.2+git20130218-3ubuntu3~raring
The full steps I took to unlock bootloader and attempt flashing the recovery (from a factory reset):
Put the device into developer mode by tapping the 'Build number' in 'Settings->About tablet' several times.
Enabled USB debugging in 'Settings->Developer options'.
Connected the USB cable to a laptop running Ubuntu 13.04 with android-tools-adb and android-tools-fastboot installed.
Ran
Code:
adb devices
which showed the device
Code:
adb reboot bootloader
>> rebooted into the fastboot bootloader
Code:
sudo fastboot devices
>> showed the device
Code:
sudo fastboot oem unlock
>> bootloader successfully unlocked
Code:
sudo fastboot continue
>> booted the device
Repeated the steps to enable developer mode and USB debugging
Downloaded kernel_kexec_430.zip, multirom_v12_n7-signed.zip, TWRP_multirom_n7_20130727.img to the current folder (and verified the md5sums)
Copied TWRP_multirom_n7_20130727.img to recovery.img
Copied kernel_kexec_430.zip, multirom_v12_n7-signed.zip, recovery.img to Nexus 7/Internal Storage root directory using nautilus
Ran
Code:
adb reboot bootloader
which put the device into fastboot mode
Ran
Code:
sudo fastboot flash recovery recovery.img
, which failed
Code:
flashboot flash bootloader [URL="http://d-h.st/QFd"]bootloader-grouper-4.23.img[/URL]
Running:
Code:
flashboot flash bootloader bootloader-grouper-4.23.img
has the same problem:
Code:
sending 'bootloader' (2100 KB)...
FAILED (data transfer failure (Protocol error))
finished. total time: 81.438s
lazyteq said:
Running:
Code:
flashboot flash bootloader bootloader-grouper-4.23.img
has the same problem:
Code:
sending 'bootloader' (2100 KB)...
FAILED (data transfer failure (Protocol error))
finished. total time: 81.438s
Click to expand...
Click to collapse
change usb cable and try different ports...
It seems this is a problem with the usb cable and usb ports. Fastboot seems very flaky and intemittently works on different USB ports.
Now for a story about how I softbricked and eventually unbricked the tablet.
By changing around USB ports on my laptop, I eventually managed to flash TWRP recovery. In the process of messing around, I managed to delete the os from the tablet, so I tried to reinstall the stock os.
I ran the flash-all script and it started to install. Unfortunately, fastboot decided to fail once it had erased the partitions and was starting to re-flash them. So I was left with a tablet with no os, no recovery and only a bootloader that wouldn't communicate properly with fastboot on my laptop!
I decided to try a different computer. The only one I had available was a very old Windows XP desktop with 256MB RAM and USB 1.0 ports (!). I managed to download the Android SDK on this incredibly slow machine and also installed device drivers using the Nexus 7 toolkit. I couldn't get fastboot to work for ages but eventually, after plugging the tablet out and in and repeating the
Code:
fastboot devices
command, I managed to get the device to show up.
I then managed to reflash TWRP onto the recovery partition. Fastboot was still very dodgy but seemed a bit more reliable at sending the data across than it had been on my laptop. Once I had flashed TWRP, I put the latest Cyanogenmod ROM onto a usb stick, connected it via OTG and managed to install it.
So now I have a working tablet with TWRP and Cyanogenmod and I finally have proper root permissions including the ability to use usb-otg which was one of the main reasons for rooting in the first place. I'm going to give MultiROM a miss because I really don't trust fastboot / my usb cable / my usb ports to properly flash images.
Username invalid said:
Code:
flashboot flash bootloader [URL="http://d-h.st/QFd"]bootloader-grouper-4.23.img[/URL]
Click to expand...
Click to collapse
I there, I am not at all a novice to Android but I have only owned two Nexus devices. The other two devices that I have had and modded were the Vzw Galaxy s4 and s3. I've been modding for quite a while now and am quite familiar with Android software modifying and using adb. That being said quick semi topic related question: How do I know what Bootloader my Nexus 7 has already? I just sent it in to repair at Asus and got it back compeletely wiped running stock (sent it in unlocked running Rootbox). I have previously flashed to the most recent bootloader, but I'm not sure if it still has it. I don't know what all they did to it.
Is there a way to find out exactly what bootloader it is running? Maybe there is an adb shell command I can run to find out or something?
I have searched but I couldn't find a definitive answer. And I didn't want to start a whole new thread just to ask this simple question.
Thanks for your time.
nicholi2789 said:
I there, I am not at all a novice to Android but I have only owned two Nexus devices. The other two devices that I have had and modded were the Vzw Galaxy s4 and s3. I've been modding for quite a while now and am quite familiar with Android software modifying and using adb. That being said quick semi topic related question: How do I know what Bootloader my Nexus 7 has already? I just sent it in to repair at Asus and got it back compeletely wiped running stock (sent it in unlocked running Rootbox). I have previously flashed to the most recent bootloader, but I'm not sure if it still has it. I don't know what all they did to it.
Is there a way to find out exactly what bootloader it is running? Maybe there is an adb shell command I can run to find out or something?
I have searched but I couldn't find a definitive answer. And I didn't want to start a whole new thread just to ask this simple question.
Thanks for your time.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Or you can use
Code:
fastboot getvar all
Version 4.23 is the latest released with Android 4.3.
Username invalid said:
Or you can use [Code ]fastboot getvar all[/CODE]
Version 4.23 is the latest released with Android 4.3.
Click to expand...
Click to collapse
Haha wow. Now I really feel like a noob. I guess I probably should have noticed that.
Thanks
I had the same problem and then realized I was using 3.0 usb port.
Plugged cable into 2.0 port and it suddendly worked.
I have the same error:
Code:
FAILED (command write failed (Protocol error))
In my case my phone was connected through USB HUB so i connected it to PC and everything starts working.
Did not work
sending 'recovery' (12396 KB)...
OKAY [ 0.409s]
writing 'recovery'...
FAILED (remote:
partition 'recovery' not support flash)
finished. total time: 0.458s
I see this also when my USB cable was too long.
I also just used a shorter cable and it worked
Introduction
As we know, the official way to unlock the bootloader of Zuk Z1 is through fastboot.
For a untouched device, the status of the bootloader should be:
Code:
fastboot -i 0x2b4c oem device-info
...
(bootloader) Device tampered: [COLOR="Red"]false[/COLOR]
(bootloader) Device unlocked: [COLOR="Red"]false[/COLOR]
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
To unlock the bootloader, you need to enable 'OEM unlocking' under Developer options first, then via bootloader/fastboot interface:
Code:
fastboot -i 0x2b4c oem unlock-go
It'll eventually erase the userdata.
Then the status of the bootloader should be:
Code:
fastboot -i 0x2b4c oem device-info
...
(bootloader) Device tampered: [COLOR="Red"]false[/COLOR]
(bootloader) Device unlocked: [COLOR="Red"]true[/COLOR]
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
Inspired by the findings on similar devices, we can actually unlock the bootloader of Zuk Z1 without using fastboot, while keeping the userdata intact.
How-to
Warning!
It is dangerous! This whole thing is basically one giant hack - which is not intended to be done by normal users. It is messing with the bootloader partition, so it is possible that something goes wrong and you will have a nice & costly brick in your pocket. Be prepared to revive the device from a hard-brick.
1.
Enable 'OEM unlocking' under Developer options. You may need to tap the Build number 7 times under About phone to get the Developer options under Settings.
2.
We need root access (kinda expected!). To root the device without unlocking bootloader, use KingRoot. Use the Android version.
Now there is a catch! KingRoot can root the device, cause the latest build of Cyanogen OS (cm-12.1-YOG4PAS3OH-ham ATM) contains such vulnerabilities which can be exploited by the root exploits used by KingRoot. But we can't ensure about future.
3.
After being rooted, use adb shell or any terminal emulator to dump the 'aboot' i.e bootloader partition in internal sdcard:
Code:
su
dd if=/dev/block/bootdevice/by-name/aboot of=/sdcard/aboot.img
4.
Now we need to modify the dumped image using hex-editor. For Zuk Z1:
Code:
Unlock Bit Position - 0x001FFE10 Hex
Tamper Bit Position - 0x001FFE14 Hex
'00' means false, '01' means true. So to set the bootloader as unlocked, we just need to change the following:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Save the modified image as 'abootmod.img' inside your sdcard.
5.
Now its time to flash back the modded bootloader. Execute the following from adb shell or any terminal emulator:
Code:
su
dd if=/sdcard/abootmod.img of=/dev/block/bootdevice/by-name/aboot
Do a reboot & voila! You have unlocked the bootloader! Don't just believe me - check the status of the bootloader to ensure.
Note
1. We can also reset the tamper bit using this procedure.
2. If you prefer GUI, then you can use this fantastic app by @wanam.
3. This is tested on an international Zuk Z1 running cm-12.1-YOG4PAS3OH-ham. Please test & post feedback to ensure compatibility.
4. I'm not providing pre-modified images as it increases the risk of bricking the devices having older/newer bootloaders - please do it yourself. The offsets should be unchanged in future, though.
Credits
1. @osm0sis
2. @segv11
3. @Mnt-XDA
4. @Tengo10 - for risking his device for this experiment.
5. Users of XDA.
Happy tinkering! :highfive: :good:
Reserved for future.
I tested now and working okay. Thaaaaaaaaaaaaaaaaanks
after using dd for writing the modified image it worked. seems to be a problem using the app Partitions Backup & Restore
old post
Doesn't worked for me.
fastboot -i 0x2b4c oem device-info still shows
Code:
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.009s]
finished. total time: 0.010s
when I read the aboot-partition after writing the modified image my modification is gone, i used Partitions Backup & Restore App for reading and writing
Click to expand...
Click to collapse
Hi everybody
I am trying to unlock the bootloader with fastboot but I am stucked (I have the drivers installed properly, adb recognize my device):
C:\adb>fastboot -i 0x2b4c oem unlock-go
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.003s
I am trying for hours to unlock the device, can you tell me what is wrong?
Thank you
Lems84 said:
Hi everybody
I am trying to unlock the bootloader with fastboot but I am stucked (I have the drivers installed properly, adb recognize my device):
C:\adb>fastboot -i 0x2b4c oem unlock-go
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.003s
I am trying for hours to unlock the device, can you tell me what is wrong?
Thank you
Click to expand...
Click to collapse
Did you do this?
To unlock the bootloader, you need to enable 'OEM unlocking' under Developer options first
yes I did it, USB debogging and OEM unlocking on the ZUI interface.
Planet X said:
Did you do this?
To unlock the bootloader, you need to enable 'OEM unlocking' under Developer options first
Click to expand...
Click to collapse
Planet X said:
Did you do this?
To unlock the bootloader, you need to enable 'OEM unlocking' under Developer options first
Click to expand...
Click to collapse
I also have the same problem.I enabled OEM.solutions please?kindly?
Thanks!
Hello Titokhan,
can you please upload the modified abootmod.img for the international version. Then it will be very easy for me and the only thing i must do is to install the file... many thx
carstenheuer said:
Hello Titokhan,
can you please upload the modified abootmod.img for the international version. Then it will be very easy for me and the only thing i must do is to install the file... many thx
Click to expand...
Click to collapse
The Problem is that he don't own that phone.
Tengo10 said:
The Problem is that he don't own that phone.
Click to expand...
Click to collapse
what happen when i flash TWRP with flashify app when the bootloader is still locked?
carstenheuer said:
what happen when i flash TWRP with flashify app when the bootloader is still locked?
Click to expand...
Click to collapse
Nothing special, you only can't flash unsignt zips and IMG.
Hello, I'm having this problem. I do not see the "OEM Unlocking". I have enabled USB Debugging already. Please help.
Planet X said:
Did you do this?
To unlock the bootloader, you need to enable 'OEM unlocking' under Developer options first
Click to expand...
Click to collapse
Problems with fastboot
I was going to follow this guide but fastboot doesn't recognize my zuk. I tried to install all the drivers from sdk, and then i tried also to manually select them in the devices settings of windows but my pc says that there aren't any drivers in the folders. Ho can I solve it? I looked over and over the internet but this phone is apparently really rare so there are no working solutions for this. Can someone help me? :crying:
It works!
Zuk Z1 international, it worked perfectly! Just, I had to change the name of abootmod in about to substitute the original file, so " dd if=/sdcard/aboot.img of=/dev/block/bootdevice/by-name/aboot "
You should have written a bigger warning that it ERASES USERDATA!
Tuberomix said:
You should have written a bigger warning that it ERASES USERDATA!
Click to expand...
Click to collapse
Well, this method doesn't touch the userdata partition.
Titokhan said:
Well, this method doesn't touch the userdata partition.
Click to expand...
Click to collapse
Whatever it wipes, I do ask that you put a warning in big, bold, red letters!
@Tuberomix
Looks like there is some misunderstanding; this method doesn't wipe anything. Can you please elaborate about your experience?
I cant enter adb. only something like fastboot (bootloader) . also can start like ZTE Handset Diagnostic Interface(DFU)
can you help me? nothing works
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
C:\adb> adb devices
List of devices attached
C:\adb>fastboot devices
2a47d296 fastboot
C:\adb>fastboot flash recovery twrp-3.0.3-1-ailsa_ii.img
target reported max download size of 536870912 bytes
sending 'recovery' (13536 KB)...
OKAY [ 0.316s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.331s
I HAVE THE SAME ISSUE!(A2017G) SOMEONE HELP! :crying:
You're not bricked, you're just down ATM. If you can get into bootloader or EDL mode you're fine. Just gotta put some work in. First, you've probably got a bootloader that doesn't allow fastboot commands. (the reason why you're getting the unknown command error). You need to flash that via EDL if you don't want to downgrade/unlock your bootloader. There is SOOOO much to read out there that with a little searching and reading you'll be up in no time. This toolkit is a good place to start looking. https://forum.xda-developers.com/axon-7/development/tool-axon7toolkit-t3573108
nolimit78 said:
You're not bricked, you're just down ATM. If you can get into bootloader or EDL mode you're fine. Just gotta put some work in. First, you've probably got a bootloader that doesn't allow fastboot commands. (the reason why you're getting the unknown command error). You need to flash that via EDL if you don't want to downgrade/unlock your bootloader. There is SOOOO much to read out there that with a little searching and reading you'll be up in no time. This toolkit is a good place to start looking. https://forum.xda-developers.com/axon-7/development/tool-axon7toolkit-t3573108
Click to expand...
Click to collapse
Hey, I CAN use Fastboot commands. but i cant get to recovery mode even tho i flash it. my bootloader is unlocked. please help!! i am stuck
Well with the error message you posted, "unknown command" means that you're on the wrong bootloader. You have two methods to install TWRP. Bootloader or EDL. If you want to do it via bootloader you need to load the B20 bootloader and that'll allow for the fastboot flash recovery "name of img file".img command. If you're wanting to use EDL you'll need to use a tool to force the recovery image.
nolimit78 said:
You're not bricked, you're just down ATM. If you can get into bootloader or EDL mode you're fine. Just gotta put some work in. First, you've probably got a bootloader that doesn't allow fastboot commands. (the reason why you're getting the unknown command error). You need to flash that via EDL if you don't want to downgrade/unlock your bootloader. There is SOOOO much to read out there that with a little searching and reading you'll be up in no time. This toolkit is a good place to start looking. https://forum.xda-developers.com/axon-7/development/tool-axon7toolkit-t3573108
Click to expand...
Click to collapse
fastboot flash recovery twrp-3.0.3-1-ailsa_ii.img
target reported max download size of 536870912 bytes
sending 'recovery' (13536 KB)...
OKAY [ 0.316s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.331s
I cant go to edl. Only DFU.
C:\adb>fastboot oem device-info
...
FAILED (remote: unknown command)
finished. total time: 0.034s
FAILED to all commands in fastboot
nolimit78 said:
Well with the error message you posted, "unknown command" means that you're on the wrong bootloader. You have two methods to install TWRP. Bootloader or EDL. If you want to do it via bootloader you need to load the B20 bootloader and that'll allow for the fastboot flash recovery "name of img file".img command. If you're wanting to use EDL you'll need to use a tool to force the recovery image.
Click to expand...
Click to collapse
Check This;;
:\Users\Bumthimble\Desktop\ADB>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (17917 KB)...
OKAY [ 0.424s]
writing 'recovery'...
OKAY [ 0.141s]
finished. total time: 0.565s
I get this but when i try to boot into recovery, it boots into fastboot mode. Help
Ok that means that both of you are using the G model. If you're able to get to your bootloader try using the tool that I linked above. I have the U model so I can't relate with some of your issues but I believe that if you can reach the bootloader the tool can help. Have you tried manually booting to EDL?
nolimit78 said:
Ok that means that both of you are using the G model. If you're able to get to your bootloader try using the tool that I linked above. I have the U model so I can't relate with some of your issues but I believe that if you can reach the bootloader the tool can help. Have you tried manually booting to EDL?
Click to expand...
Click to collapse
I did. but it doesnt boot into EDL ever. I dont know why, i doesnt recognise its commands
nolimit78 said:
Ok that means that both of you are using the G model. If you're able to get to your bootloader try using the tool that I linked above. I have the U model so I can't relate with some of your issues but I believe that if you can reach the bootloader the tool can help. Have you tried manually booting to EDL?
Click to expand...
Click to collapse
I have China version. I cant manually booti to EDL. it booting in DFU
i can only boot it to fastboot
See this thread: https://forum.xda-developers.com/axon-7/help/edl-twrp-stuck-fastboot-luck-t3569879
don't work.
ZTE Handset Diagnostic Interface(DFU)
with handmade deepflash cable
if I connect with a closed cable, it blinks the symbol of charging(empty battery with the lightning bolt) several times and boot in DFU
fatax said:
don't work.
ZTE Handset Diagnostic Interface(DFU)
with handmade deepflash cable
if I connect with a closed cable, it blinks the symbol of charging(empty battery with the lightning bolt) several times and boot in DFU
Click to expand...
Click to collapse
I have exactly the same issue.
And 2 weeks already. Can't find any solution. Searched all the internet.
There is no solution so far.
Have to wait untill someone will create a flashtool for DFU mode for Snapdragon 820.
Vick78 said:
I have exactly the same issue.
And 2 weeks already. Can't find any solution. Searched all the internet.
There is no solution so far.
Have to wait untill someone will create a flashtool for DFU mode for Snapdragon 820.
Click to expand...
Click to collapse
I gave the phone to a service center (unofficial) they will try to flash the phone directly to memory
fastboot still locked. they can not do anything
fatax said:
fastboot still locked. they can not do anything
Click to expand...
Click to collapse
that's a sad news. did they say anything?
what do they need to fix?
Vick78 said:
that's a sad news. did they say anything?
what do they need to fix?
Click to expand...
Click to collapse
I do not know, but my acquaintance with 4pda wrote: Hello. It's JOY NEWS! We HAVE RISE ONE BRICK! So wait soon we will lay out the instruction how to raise. The phone will have to be dismantled.
I have now the same problem how did you solved the problem? Or is there generaly any solution?
cybertronixx said:
I have now the same problem how did you solved the problem? Or is there generaly any solution?
Click to expand...
Click to collapse
Did you search on the forum before bumping a year-old thread?
So far there are 2 DFU guides, mine is the latest. (Google "dfu unbrick"). Though you might want to try an EDL cable before doing the process on the guide. Just use MiFlash or EDL Tool along with the cable, and you might fix it.
Hi folks,
I just received my Essential Phone, purchased through amazon. As you recall, the Essential Phone was rumored to have an unlocked bootloader. This was confirmed by @essential confirming that it will, in a tweet.
However, this is not what I'm experiencing with the phone.
After powering it up and playing around a bit, I enabled USB debugging and linked it to my computer, where I have the latest (as of today) android platform tools installed. I rebooted to fastboot and tried to issue "fastboot oem unlock", as I did with my previous phone, a nexus 6p. However, it seems "oem" is no longer a valid subcommand of fastboot; it has been renamed to "flashing unlock", along with some other new-to-me commands:
Code:
$ fastboot --help
usage: fastboot [ <option> ] <command>
commands:
.....
flashing lock Locks the device. Prevents flashing.
flashing unlock Unlocks the device. Allows flashing
any partition except
bootloader-related partitions.
flashing lock_critical Prevents flashing bootloader-related
partitions.
flashing unlock_critical Enables flashing bootloader-related
partitions.
flashing get_unlock_ability Queries bootloader to see if the
device is unlocked.
flashing get_unlock_bootloader_nonce Queries the bootloader to get the
unlock nonce.
flashing unlock_bootloader <request> Issue unlock bootloader using request.
flashing lock_bootloader Locks the bootloader to prevent
bootloader version rollback.
The "flashing unlock" command looks interesting. Let's try that:
Code:
$ fastboot flashing unlock
...
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.003s
Hmmm... I don't like the look of that. Well, let's see what "get_unlock_ability" says:
Code:
$ fastboot flashing get_unlock_ability
...
(bootloader) get_unlock_ability: 0
OKAY [ 0.000s]
finished. total time: 0.000s
Ok, that looks bad too. Let's try those other new commands and see if we can get anywhere...
Code:
$ fastboot flashing unlock_critical
...
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.002s
Nope.
Code:
$ fastboot flashing get_unlock_bootloader_nonce
...
FAILED (remote: unknown command)
finished. total time: 0.000s
Double nope.
Well that's not encouraging. I don't claim to be any sort of expert in regards to unlocking phones, but I can't find any other methods using these tools, and Essential's docs aren't any help. I've contact their phone support but haven't heard back after about an hour. (They use some ridiculous system where you schedule a callback... Not happy.)
So, I'm feeling pretty upset. Let's be clear here:
Essential said this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
But shipped a product with this:
Code:
$ fastboot flashing get_unlock_ability
...
(bootloader) get_unlock_ability: 0
OKAY [ 0.000s]
finished. total time: 0.000s
Did you turn on the allow unlocking toggle in developer options?
tw1tch175 said:
Did you turn on the allow unlocking toggle in developer options?
Click to expand...
Click to collapse
Thanks, that did the trick
xMopx said:
Thanks, that did the trick
Click to expand...
Click to collapse
So ...wich are the right steps and command d to unlock the bootloader?
thx
mastercut said:
So ...wich are the right steps and command d to unlock the bootloader?
thx
Click to expand...
Click to collapse
1) Check the box next to OEM Unlockable.
2) Then reboot your phone to fastboot
3) In a command prompt within the adb folder: type -> fastboot flashing unlock
4) Use the volume button to click yes when prompted.
Cheers
frhoward said:
1) Check the box next to OEM Unlockable.
2) Then reboot your phone to fastboot
3) In a command prompt within the adb folder: type -> fastboot flashing unlock
4) Use the volume button to click yes when prompted.
Cheers
Click to expand...
Click to collapse
I've tried all of these steps and once I get to the fastboot flashing unlock step my cmd prompt just hangs at waiting for device and I never get the option for "Yes." Instead I have Start, Recovery, Power off, etc.
What am I doing wrong?
DenverDroid said:
I've tried all of these steps and once I get to the fastboot flashing unlock step my cmd prompt just hangs at waiting for device and I never get the option for "Yes." Instead I have Start, Recovery, Power off, etc.
What am I doing wrong?
Click to expand...
Click to collapse
First in fastboot type "fastboot devices" if a string of numbers answers it is ok otherwise you need fastboot driver ....have you cheked?
Hi guys, I have an issue with unlocking the bootloader. fastboot devices returns the device ID, but flashing unlock gives me failed, unknown command error. I cannot get it working. Any ideas?
/edit: changing PC's helped
Essential Phone stuck in Start up screen with Locked Bootloader
My Essential Phone is frozen at boot up screen while trying to Update the latest Android P Beta 3 ... I restarted the phone on promoting to do so after downloading the update and now I'm here stuck with boot up screen.
Boot loader: Locked
Please let me know if there is a way around this to get it back up !!
Pleaseeeee....
Thanks in advance!!
[email protected] said:
My Essential Phone is frozen at boot up screen while trying to Update the latest Android P Beta 3 ... I restarted the phone on promoting to do so after downloading the update and now I'm here stuck with boot up screen.
Boot loader: Locked
Please let me know if there is a way around this to get it back up !!
Pleaseeeee....
Thanks in advance!!
Click to expand...
Click to collapse
If you've already waited for some time to pass, i would let it go dead, then plugin and allow it to power up on its own. I've only had limited success with this though. Other options are goto into recovery mode and factory reset.
wrecklesswun said:
If you've already waited for some time to pass, i would let it go dead, then plugin and allow it to power up on its own. I've only had limited success with this though. Other options are goto into recovery mode and factory reset.
Click to expand...
Click to collapse
Yeah, I had such instances too in the past. But no luck this time...
My OEM locking is not switched on and I'm unable to sideload the OTA or Rest the phone to factory.
Hi i've done something stupid, i've blocked bootloader idk why, anyway im in LineageOs 16, but now i can't back to stock or flash something else ¿i cant re-unlock bootloader?
What is the error that you're getting?
Fastboot flash bootloader permission denied
elHeisen said:
Fastboot flash bootloader permission denied
Click to expand...
Click to collapse
Yes you can't flash before unlocking? How about 'fastboot unlock bootloader' or was it 'fastboot bootloader unlock'? Sorry, tired hehe.
weazie said:
Yes you can't flash before unlocking? How about 'fastboot unlock bootloader' or was it 'fastboot bootloader unlock'? Sorry, tired hehe.
Click to expand...
Click to collapse
yep i've tried too but i get this
...
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
OKAY [ -0.000s]
finished. total time: -0.000s
and i can't enable OEM unlocking in Android P
elHeisen said:
yep i've tried too but i get this
...
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
OKAY [ -0.000s]
finished. total time: -0.000s
and i can't enable OEM unlocking in Android P
Click to expand...
Click to collapse
Did you find any solution?
Same problem!
Works for me!
elHeisen said:
yep i've tried too but i get this
...
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
OKAY [ -0.000s]
finished. total time: -0.000s
and i can't enable OEM unlocking in Android P
Click to expand...
Click to collapse
First, install gnirehtet for reverse tethering internet with usb and pc
https://github.com/Genymobile/gnirehtet
Then you will see that you can enable OEM
I'm still not able to unlock oem in settings. I have WIFI on and did all the updates to the latest
elHeisen said:
Fastboot flash bootloader permission denied
Click to expand...
Click to collapse
Same error here. Did anyone find a solution?
Constantinologia said:
Same error here. Did anyone find a solution?
Click to expand...
Click to collapse
Can you update your phone in settings? if not wait 7 days with phone on and try again. An update fixed my phone.
mrsiri said:
Can you update your phone in settings? if not wait 7 days with phone on and try again. An update fixed my phone.
Click to expand...
Click to collapse
I can't even load the system. The only two screens i can see are the Fastboot and "your device is corrupted". The Flashing option is locked and every rom i try to flash gives me the access denied error.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Constantinologia said:
I can't even load the system. The only two screens i can see are the Fastboot and "your device is corrupted". The Flashing option is locked and every rom i try to flash gives me the access denied error.
View attachment 5251849 View attachment 5251851
Click to expand...
Click to collapse
Can you download the stock rom from your current version flashed and boot it? use command "fastboot boot boot.img". Boot.img is inside of the flashable stock rom zip. After this try toggling the oem unlock if not wait 7 days and try to update phone like regular ota in setings
mrsiri said:
Can you download the stock rom from your current version flashed and boot it? use command "fastboot boot boot.img". Boot.img is inside of the flashable stock rom zip. After this try toggling the oem unlock if not wait 7 days and try to update phone like regular ota in setings
Click to expand...
Click to collapse
I found a stock rom that matches the descriptions from ro.build.fingerprint[0]: motorola/rav_retail/rav:10/QPJS30 and 63-35-1-15. Coudn'd find a match for 37df17:user/release-key.
Still got the error for fastboot boot boot.img:
downloading 'boot.img'...
OKAY [ 1.463s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 37.486s
Constantinologia said:
I found a stock rom that matches the descriptions from ro.build.fingerprint[0]: motorola/rav_retail/rav:10/QPJS30 and 63-35-1-15. Coudn'd find a match for 37df17:user/release-key.
Still got the error for fastboot boot boot.img:
downloading 'boot.img'...
OKAY [ 1.463s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 37.486s
Click to expand...
Click to collapse
I don't remember the steps to reproduce, but I remember being possible to take the very own boot.img currently flash on your phone. I think it was through adb commands, what if you try booting that one instead? That's what I did on mine, but it didn't help with toggling oem unlock, only entering the system
I accidentally locked mine and im in the same situation as everyone here, but i think the only solution is BlankFlashing or sideloading a signed OTA on it... Im trying everyday new possible methods of fixing it and if i get into some ill share here
hi guys, had exact same issue, spent hours trolling through the net, forums etc and this forum fixed it for me. I was about to throw the phone out.
something tells me that you have to have the boot image from the software you had installed before the crash/brick. Run the "fastboot boot boot.img"
i tried numerous boot.img's thinking I've spent too much time this device so as I turned my back on the phone I hear a 'Hello Moto' WTF...Up and running again. Good Luck
thehulk1969 said:
hi guys, had exact same issue, spent hours trolling through the net, forums etc and this forum fixed it for me. I was about to throw the phone out.
something tells me that you have to have the boot image from the software you had installed before the crash/brick. Run the "fastboot boot boot.img"
i tried numerous boot.img's thinking I've spent too much time this device so as I turned my back on the phone I hear a 'Hello Moto' WTF...Up and running again. Good LuckView attachment 5274327
Click to expand...
Click to collapse
It would be the solution if the stock was corrupted, but i have locked mine on StyxOS, and there isn't any boot.img for it so stock boot.img gives a system corrupted error. But nice idea.
Edit: Does it need to match the ro.fingerprint on getvar all? only tested with latest pie, so