This is only for FireTV 1 running version 51.1.0.2 software.
Unlike FireTV Partial Bootloader Unlock, this is a full bootloader unlock. fastboot flash and fastboot boot will both work. Of course you need an A to A USB cable to take advantage of it.
This is a tool to run on your Fire TV that will unlock the bootloader and then reboot. For now, this requires root. Apparently, the IDs that are required for this can be gotten through fastboot, so if someone can figure that out, then brand new Fire TVs with 51.1.0.2 or older can be unlocked and have recovery installed before booting the first time. Please refer to the linked thread below for more information.
As usual, this WILL void your warranty and I am NOT responsible for anything you do with this. Using this tool won't brick your Fire TV, but doing stupid things afterwards might.
This was all code I had written for recovery before the partial unlock, just tweaked to be used in this situation. Thanks to http://forum.xda-developers.com/kin...bootloader-unlock-procedure-software-t3030281 for showing what needed to be encrypted.
I have also published the full source at: https://github.com/androidrbox/aftv-full-unlock
To use:
Downgrade: You must first downgrade to 51.1.0.2. If you already have CWM installed, you can skip this.
adb push aftv-full-unlock /data/local/tmp/
adb shell
chmod 755 /data/local/tmp/aftv-full-unlock
su
/data/local/tmp/aftv-full-unlock
If after it reboots and you run 'adb shell' and you get a root prompt, it has worked.
* Feb 16, 2015: The binary has been updated. The old version was unable to unlock certain Fire TVs. If you've already unlocked, you are fine. If it failed, this one should work.
You can download it here
Awesome!
Thank you
Wow! And I just ordered a fastboot cable 2 days ago...this is pretty amazing. Thanks!
Actually...it appears the aftvnews guide is linking to a 3.0 usb A to A, NOT a fastboot cable. Is this just a regular usb we need? Will a usb 2.0 work? I know I have one of those on hand...
Edit--got my answer. No fastboot cable needed and usb 2.0 should work. Now I'm wondering if an android terminal for a phone or tablet would work as that would be real convenient but I'm guessing not since its not mentioned.
Nice i will be updating my tool to include this thanks
Could you clarify step 1? Does it mean if your already rooted you and have cwm, that you can skip downgrading to 51.1.0.2 ?
Reason I ask is I'm on 5.1.1.3.0, and ran the aftv-full-unlock, it did it's thing, rebooted. I rebooted to fastboot to do some tests.
Code:
C:\Android>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
OKAY [ 0.008s]
finished. total time: 0.008s
C:\Android>fastboot boot firetv-cwm_recovery-6.0.5.1.2.img
downloading 'boot.img'...
OKAY [ 0.269s]
booting...
FAILED (remote: boot not allowed for locked hw)
finished. total time: 0.286s
C:\Android>
Luxferro said:
Could you clarify step 1? Does it mean if your already rooted you and have cwm, that you can skip downgrading to 51.1.0.2 ?
Reason I ask is I'm on 5.1.1.3.0, and ran the aftv-full-unlock, it did it's thing, rebooted. I rebooted to fastboot to do some tests.
Code:
C:\Android>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
OKAY [ 0.008s]
finished. total time: 0.008s
C:\Android>fastboot boot firetv-cwm_recovery-6.0.5.1.2.img
downloading 'boot.img'...
OKAY [ 0.269s]
booting...
FAILED (remote: boot not allowed for locked hw)
finished. total time: 0.286s
C:\Android>
Click to expand...
Click to collapse
Hrm, if cwm works, then you are on the correct bootloader. Can you try running the unlock again and paste the output? Can you also run these 2 commands:
cat /sys/block/mmcblk0/device/manfid
cat /sys/block/mmcblk0/device/serial
some questions.
1. Must you "aftv-unlock lock" re-lock the partial unlock which might be there, before one does an "aftv-full-unlock" full unlock of the bootloader?
2. aftv-news states as long as you are on any of rbox's pre-rooted custom roms. So cwm 6.5.0.1.4a and 5.1.4.1_user_514013920 from rbox is not an issue.
3. will bootmenu be an issue with that rbox custom rom.
3. which keys are the sleep, vol up , vol down keys on a logitech k400r keyboard.
4. I could only fnd that it states using a linux environment. what about a windows environment and using Koush's universal adb driver or is there another driver needed for a firetv.
thanks.
sorry to ask. I'm just having issues connecting
rp201 said:
some questions.
1. Must you "aftv-unlock lock" re-lock the partial unlock which might be there, before one does an "aftv-full-unlock" full unlock of the bootloader?
2. aftv-news states as long as you are on any of rbox's pre-rooted custom roms. So cwm 6.5.0.1.4a and 5.1.4.1_user_514013920 from rbox is not an issue.
3. will bootmenu be an issue with that rbox custom rom.
3. which keys are the sleep, vol up , vol down keys on a logitech k400r keyboard.
4. I could only fnd that it states using a linux environment. what about a windows environment and using Koush's universal adb driver or is there another driver needed for a firetv.
thanks.
sorry to ask. I'm just having issues connecting
Click to expand...
Click to collapse
1. no, partial doesn't matter
2. yes, if you have cwm working, then you are good
3. if bootmenu is working for you already, this won't change that
4. there are tons of threads already that talk about using logitech stuff
5. there are tons of threads on how to get adb working
Thanks for your work on this rbox
I have a (noob) question; are the DRM keys still intact after the full unlock?
Will this work with emmc hardware root on latest software?
I have the same question. Is this unlock of any use by people that have hardware rooted their newer firmware?
Resnoid said:
Thanks for your work on this rbox
I have a (noob) question; are the DRM keys still intact after the full unlock?
Click to expand...
Click to collapse
Netflix and Amazon Prime both work fine.
pj1115 said:
Will this work with emmc hardware root on latest software?
Click to expand...
Click to collapse
papars said:
I have the same question. Is this unlock of any use by people that have hardware rooted their newer firmware?
Click to expand...
Click to collapse
No. As the OP states, you MUST be on the 51.1.0.2 bootloader. If you are on 51.1.4.0 or earlier, you can downgrade. Otherwise if 51.1.4.1 or above ever booted, it will brick if you attempt to use 51.1.0.2 bootloader.
I have updated the link in the OP with a new version. Some Fire TVs were having issues with the original version. This should work for all now.
@rbox
Full unlock will not work with bueller-ota-51.1.4.1_user_514013920-signed with su (Nov 19, 2014), isn't it?
Please help with bricked FireTV
I'm alive!
hi,
awesome work but i got a question.
i attempt to use your second unlock file, but before i already used your first one.
what makes me a little bit irritated, is the fact, that the unlock code is different compered to the first one.
i'll pm you
schybiorz said:
hi,
awesome work but i got a question.
i attempt to use your second unlock file, but before i already used your first one.
what makes me a little bit irritated, is the fact, that the unlock code is different compered to the first one.
i'll pm you
Click to expand...
Click to collapse
If the code is different that means it didn't unlock it the first time, because the code was wrong. Now it is right, so it should be unlocked.
thanks for reply.
is there any adb shell command we can use to determin unlock status?
or only via fastboot testing command?
schybiorz said:
thanks for reply.
is there any adb shell command we can use to determin unlock status?
or only via fastboot testing command?
Click to expand...
Click to collapse
adb shell will give you a root prompt if its unlocked.
Thanks a lot! Much appreciated. Worked like a charm..
Best regards tuxen
Related
Thank You seniors for supporting me for the last few days.
This thread is about my discussions with you http://forum.xda-developers.com/nex...6-recovery-flashable-fastboot-t3066052/page54 and the following pages.
I have to move here as my issue was off topic in that thread.
When i type fastboot oem unlock command it says check OEM unlock option is developer settings.
But my problem is i cant boot my phone to go there.
I erased everything and locked boot loader by mistake.
I can boot my phone to bootloader and recovery i cant flash anything via fastboot as my bootloader is locked.
But i can do adb sideload in recovery.
I am now on lmy48i recovery i tried lmy48i from lmy47z it says the file is incorrect and i am already on lmy48i.
Kindly help.
openbook said:
Thank You seniors for supporting me for the last few days.
This thread is about my discussions with you http://forum.xda-developers.com/nex...6-recovery-flashable-fastboot-t3066052/page54 and the following pages.
I have to move here as my issue was off topic in that thread.
When i type fastboot oem unlock command it says check OEM unlock option is developer settings.
But my problem is i cant boot my phone to go there.
I erased everything and locked boot loader by mistake.
I can boot my phone to bootloader and recovery i cant flash anything via fastboot as my bootloader is locked.
But i can do adb sideload in recovery.
I am now on lmy48i recovery i tried lmy48i from lmy47z it says the file is incorrect and i am already on lmy48i.
Kindly help.
Click to expand...
Click to collapse
If you have TWRP installed, there may be hope. If not, RMA is the only option.
Evolution_Tech said:
If you have TWRP installed, there may be hope. If not, RMA is the only option.
Click to expand...
Click to collapse
On the Motorola Website https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b
It says i have to type $ fastboot oem get_unlock_data
How do i get $ prompt when i type that it says $ is not recognized.
And when i type fastboot oem get_unlock_data i get
C:\Users\RAO\AppData\Local\Android\sdk\platform-tools>fastboot oem get_unlock_data
...
(bootloader) This command is not needed to unlock. Run fastboot oem
(bootloader) unlock directly.
OKAY [ 0.000s]
finished. total time: 0.000s
When i type fastboot oem unlock it says check allow OEM unlock under developer options.
What do i do?
openbook said:
On the Motorola Website https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b
It says i have to type $ fastboot oem get_unlock_data
How do i get $ prompt when i type that it says $ is not recognized.
And when i type fastboot oem get_unlock_data i get
C:\Users\RAO\AppData\Local\Android\sdk\platform-tools>fastboot oem get_unlock_data
...
(bootloader) This command is not needed to unlock. Run fastboot oem
(bootloader) unlock directly.
OKAY [ 0.000s]
finished. total time: 0.000s
When i type fastboot oem unlock it says check allow OEM unlock under developer options.
What do i do?
Click to expand...
Click to collapse
As @Evolution_Tech told you, IF you have TWRP installed you can boot into recovery and move a flashable ROM.zip from your PC to your phone.
If you do not have TWRP Recovery installed, you are out of options. You will have to return it for repair or replacement.
You don't type $.
Anyway, as above, no TWRP recovery, nothing you can do
seems like you could flash a factory image in Wug's toolkit if you can into bootloader mode. (power off/ hold vol down + power button at the same time)
then flash a factory image in "soft brick" mode.
norwoodesteel said:
seems like you could flash a factory image in Wug's toolkit
Click to expand...
Click to collapse
No. Did you read the thread? Bootloader is locked.
danarama said:
No. Did you read the thread? Bootloader is locked.
Click to expand...
Click to collapse
doesn't matter, you can do it with a locked bootloader. it asks if your bootloader is locked and then flashes.
norwoodesteel said:
doesn't matter, you can do it with a locked bootloader. it asks if your bootloader is locked and then flashes.
Click to expand...
Click to collapse
It does matter. It can only unlock the bootloader if the bootloader can be unlocked. It cannot unlock the bootloader if the bootloader cannot be unlocked, which is the case here.
danarama said:
No. Did you read the thread? Bootloader is locked.
Click to expand...
Click to collapse
sorry, it's the sideload function where you don't have to be unlocked
norwoodesteel said:
sorry, it's the sideload function where you don't have to be unlocked
Click to expand...
Click to collapse
Yep, unfortunately there is nothing to do here. All he can do is send it in for repair
danarama said:
Yep, unfortunately there is nothing to do here. All he can do is send it in for repair
Click to expand...
Click to collapse
I dont care about any data inside my phone.
Let me explain how i messed my Nexus 6.
I wanted to flash a fresh lmy48i full version so i erased everything via fastboot.
Then i started flashing using flashall.bat it flashed everything except system it said the device cannot accept such a huge file.
I thought may be i was unlocked it doesn't wanna work so i typed fastboot oem lock the device said successfully locked and thats the end of my N6 i can't unlock it anymore because it says enable allow oem unlock which i cant do because i erased system. when i try to boot i see GOOGLE logo but nothing after that i even left it for more than an hour nothing happens no boot animations.
Now i cant flash anything via fastboot because my bootloader is locked.
But i can get into recovery and i have the option to do ADB Sideload.
When i try lmy48i from lmy47z ...zip my phone says expecting lmy47z release keys but device already has lmy48i ...relese keys etc...
So i am thinking the next update which google releases would be xyz from lmy48i .zip and that will solve my problem.
After reading forums i understood my mistake was not using the latest fastboot file that is why my system.img failed and it said the file is huge latest fastboot.exe uses sparse method if the file is big than the acceptable size of the phone.
Prior reading would have saved my Nexus 6.I leant a good lesson.
Do you thing xyz from lmy48i ...zip in future can fix my phone?
openbook said:
I dont care about any data inside my phone.
Let me explain how i messed my Nexus 6.
I wanted to flash a fresh lmy48i full version so i erased everything via fastboot.
Then i started flashing using flashall.bat it flashed everything except system it said the device cannot accept such a huge file.
I thought may be i was unlocked it doesn't wanna work so i typed fastboot oem lock the device said successfully locked and thats the end of my N6 i can't unlock it anymore because it says enable allow oem unlock which i cant do because i erased system. when i try to boot i see GOOGLE logo but nothing after that i even left it for more than an hour nothing happens no boot animations.
Now i cant flash anything via fastboot because my bootloader is locked.
But i can get into recovery and i have the option to do ADB Sideload.
When i try lmy48i from lmy47z ...zip my phone says expecting lmy47z release keys but device already has lmy48i ...relese keys etc...
So i am thinking the next update which google releases would be xyz from lmy48i .zip and that will solve my problem.
After reading forums i understood my mistake was not using the latest fastboot file that is why my system.img failed and it said the file is huge latest fastboot.exe uses sparse method if the file is big than the acceptable size of the phone.
Prior reading would have saved my Nexus 6.I leant a good lesson.
Do you thing xyz from lmy48i ...zip in future can fix my phone?
Click to expand...
Click to collapse
No! Stop clutching at straws. We've already told you what the only thing you can do is.
openbook said:
I dont care about any data inside my phone.
Let me explain how i messed my Nexus 6.
I wanted to flash a fresh lmy48i full version so i erased everything via fastboot.
Then i started flashing using flashall.bat it flashed everything except system it said the device cannot accept such a huge file.
I thought may be i was unlocked it doesn't wanna work so i typed fastboot oem lock the device said successfully locked and thats the end of my N6 i can't unlock it anymore because it says enable allow oem unlock which i cant do because i erased system. when i try to boot i see GOOGLE logo but nothing after that i even left it for more than an hour nothing happens no boot animations.
Now i cant flash anything via fastboot because my bootloader is locked.
But i can get into recovery and i have the option to do ADB Sideload.
When i try lmy48i from lmy47z ...zip my phone says expecting lmy47z release keys but device already has lmy48i ...relese keys etc...
So i am thinking the next update which google releases would be xyz from lmy48i .zip and that will solve my problem.
After reading forums i understood my mistake was not using the latest fastboot file that is why my system.img failed and it said the file is huge latest fastboot.exe uses sparse method if the file is big than the acceptable size of the phone.
Prior reading would have saved my Nexus 6.I leant a good lesson.
Do you thing xyz from lmy48i ...zip in future can fix my phone?
Click to expand...
Click to collapse
nothing can fix your phone unfortunately. only thing you can try to do is a RMA.
I have such operations
openbook said:
I dont care about any data inside my phone.
Let me explain how i messed my Nexus 6.
I wanted to flash a fresh lmy48i full version so i erased everything via fastboot.
Then i started flashing using flashall.bat it flashed everything except system it said the device cannot accept such a huge file.
I thought may be i was unlocked it doesn't wanna work so i typed fastboot oem lock the device said successfully locked and thats the end of my N6 i can't unlock it anymore because it says enable allow oem unlock which i cant do because i erased system. when i try to boot i see GOOGLE logo but nothing after that i even left it for more than an hour nothing happens no boot animations.
Now i cant flash anything via fastboot because my bootloader is locked.
But i can get into recovery and i have the option to do ADB Sideload.
When i try lmy48i from lmy47z ...zip my phone says expecting lmy47z release keys but device already has lmy48i ...relese keys etc...
So i am thinking the next update which google releases would be xyz from lmy48i .zip and that will solve my problem.
After reading forums i understood my mistake was not using the latest fastboot file that is why my system.img failed and it said the file is huge latest fastboot.exe uses sparse method if the file is big than the acceptable size of the phone.
Prior reading would have saved my Nexus 6.I leant a good lesson.
Do you thing xyz from lmy48i ...zip in future can fix my phone?
Click to expand...
Click to collapse
I have such operations, unlock, Brush unsuccessful, lock, then can not boot, how do ah
imtv said:
I have such operations, unlock, Brush unsuccessful, lock, then can not boot, how do ah
Click to expand...
Click to collapse
@ IMTV: Can you explain in detail.
openbook said:
@ IMTV: Can you explain in detail.
Click to expand...
Click to collapse
He isn't giving you a fix if that's what you're hoping, because there is no fix.
It looks like he is saying he has the same problem as you.
http://forum.xda-developers.com/nexus-6/help/info-nexus-6-nexus-9-enable-oem-unlock-t3113539
jamescable said:
http://forum.xda-developers.com/nexus-6/help/info-nexus-6-nexus-9-enable-oem-unlock-t3113539
Click to expand...
Click to collapse
Only works if you have TWRP installed. And IF you have TWRP installed, there are other, easier solutions....
Every Software Lock should have an unlock procedure.
That is what i am searching for.
@ Danarama:I am noticing your reply's for a while now.where ever i post you respond saying RMA is the only option. Please don't make conclusions.If you don't know unlock procedure then ignore my posts.
I live in Kuwait and i bought the phone from UAE paying customs duty delivered to me via DHL no local warranty.
So i am trying all options.Let other's respond.
For people living in US,UK or few other countries RMA might be an easy procedure so they just use that option.
There are Nexus lovers everywhere so don't talk about RMA or Direct Play Store return procedures here after.
I am using Android since 2010 and i have played, rooted, reinstalled etc... with lots of android phones. I was shocked when i ended up with a dead lock like this that too on a nexus.
How stupid is this Google's Anti Theft Feature with out a back door option even for genuine owners like me.I am not a theif.I know my google account credentials which i used on my nexus 6.
Atleast Google should give an option to genuine owners to prove themselves by logging into their website with the gmail ID used on the phone to request for an unlock procedure.
Hi,
I am unable to unlock the bootloader on my Nexus 6, which was purchased new from Amazon.com. Or more accurately, I can issue the fastboot flashing unlock command without error, but my phone still says LOCKED and screen is frozen for 60 seconds.
I have followed the various HOWTOs on this website to the best of my ability:
1. Installed latest Android SDK tools(25.1.4.rc1), Platform-tools (24rc2) & Java8. I originally installed with the 23.1 platform-tools but then moved to the preview channel release when I had no luck.
2. USB debugging and OEM unlocking are both ON
3. Both "adb device" and "fastboot device" show my phone's serial number when in their respective modes, so I know communication is good between my laptop and phone.
How to replicate problem:
a. With my phone connected, I first issued "adb reboot bootloader". My phone then sucessfully changes to the AP Fastboot Flash Mode (Secure) screen. Beneath the green BATTERY OK (Charging) are the lines
Device is LOCKED. Status Code: 2
Transfer Mode: USB Connected
b. I then type "fastboot flashing unlock" and the output is
...
OKAY [ 0.016s]
finished. total time: 0.016s
However my phone does not ask me if I want to unlock. In fact, the screen then appears to be frozen -- pressing the volume up and down buttons does not change the power button selection menu. If I try to issue any other fastboot command, it says FAILED (command write failed (Unknown error)) finished. total time: 5.017s
The screen is frozen for 60 seconds. After that, the bootloader screen is once again functional (I can change menu options again) and I can issue new fastboot commands, such as 'fastboot reboot'
However, the device still says LOCKED and will refreeze for 60 seconds if I type 'fastboot flashing unlock'
Any suggestions would be appreciated!
Thank you.
type fastboot oem unlock to unlock your bootloader, then follow instruction. But beware, this will wipe your device
TMG1961 said:
type fastboot oem unlock to unlock your bootloader, then follow instruction. But beware, this will wipe your device
Click to expand...
Click to collapse
In newer versions of fastboot, the command is fastboot flashing unlock, not OEM unlock.
Code:
$ ./fastboot
usage: fastboot [ <option> ] <command>
commands:
update <filename> Reflash device from update.zip.
flashall Flash boot, system, vendor, and --
if found -- recovery.
flash <partition> [ <filename> ] Write a file to a flash partition.
flashing lock Locks the device. Prevents flashing.
flashing unlock Unlocks the device. Allows flashing
any partition except
bootloader-related partitions.
@webtrader,
@TMG1961 was trying to help you. Have you tried his recommendation before replying?
cam30era said:
@webtrader,
@TMG1961 was trying to help you. Have you tried his recommendation before replying?
Click to expand...
Click to collapse
No, I had not. I tried using fastboot oem unlock on an older version of the SDK toolkit and that had failed, but I had not tried using oem unlock again on the latest version, having noticed that "oem unlock" was no longer listed as an option.
I just tried it now on the latest SDK toolkit and it does indeed work for me. :good:
Thank you to the both of you for helping me out!
webtrader said:
No, I had not. I tried using fastboot oem unlock on an older version of the SDK toolkit and that had failed, but I had not tried using oem unlock again on the latest version, having noticed that "oem unlock" was no longer listed as an option.
I just tried it now on the latest SDK toolkit and it does indeed work for me. :good:
Thank you to the both of you for helping me out!
Click to expand...
Click to collapse
Welcome
i do believe the "fastboot flashing unlock" is for when a manufacture issues a binary token kinda of like how HTC does it. If the Nexus or any phone that is not carrier branded, "fastboot oem unlock" will be the command to pass.
Hello,
Does any one know if the below link still applies to rooting all firmware versions (Android Version = 7.0, Build NBD92D) on the Nexus 6 (Project Fi)?
https://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
Thanks in advance!
gil_happy said:
Hello,
Does any one know if the below link still applies to rooting all firmware versions (Android Version = 7.0, Build NBD92D) on the Nexus 6 (Project Fi)?
https://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
Thanks in advance!
Click to expand...
Click to collapse
Flash Magisk. Install Magisk Manager. Done.
Optional: Install cool modules to modify your phone further.
I found out that this ( http://www.wugfresh.com/nrt/ ) was an easy and up to date way to get rooted... Read all the instructions and watch videos if you need to before doing anything
http://www.wugfresh.com/nrt/
_P__ said:
I found out that this ( http://www.wugfresh.com/nrt/ ) was an easy and up to date way to get rooted... Read all the instructions and watch videos if you need to before doing anything
http://www.wugfresh.com/nrt/
Click to expand...
Click to collapse
Personally I prefer not to rely on toolkits. It's better to do things yourself so you can troubleshoot and fix if anything goes wrong.
snowrelyt said:
Flash Magisk. Install Magisk Manager. Done.
Optional: Install cool modules to modify your phone further.
Click to expand...
Click to collapse
I am in the process of trying the Magisk route and I'm having difficulty understanding the flash process. I have downloaded the Magisk-v11.1 zip to my Windows desktop and then copied it into the /Download directory on my Nexus 6. After googling a few things, I'm confused about how to flash / install on my Nexus 6. Some articles come up indicating I need to install TWRP Recovery, but I'm confused even more if I need to install this? Then I read another article (which I can't find now) about powering device down, then holding Vol Up, Vol Down, and PWR buttons to power phone back on and put in Recovery Mode (I think), and navigate and install the ZIP file. If this is the correct method, I didn't see an option to install from file or install from zip file.
gil_happy said:
I am in the process of trying the Magisk route and I'm having difficulty understanding the flash process. I have downloaded the Magisk-v11.1 zip to my Windows desktop and then copied it into the /Download directory on my Nexus 6. After googling a few things, I'm confused about how to flash / install on my Nexus 6. Some articles come up indicating I need to install TWRP Recovery, but I'm confused even more if I need to install this? Then I read another article (which I can't find now) about powering device down, then holding Vol Up, Vol Down, and PWR buttons to power phone back on and put in Recovery Mode (I think), and navigate and install the ZIP file. If this is the correct method, I didn't see an option to install from file or install from zip file.
Click to expand...
Click to collapse
Hey... You may flash TWRP recovery from bootloader using fastboot command. You can't root using stock recovery...
Download the latest TWRP from here and save it on your computer, preferably in the same folder you have ADB/fastboot:
https://dl.twrp.me/shamu/twrp-3.1.0-0-shamu.img
Just remove all security first before proceeding with the next steps (lockscreen scheme, password, pin. You can reenable them afterward. Just to avoid issues with twrp).
Your bootloader must be unlocked, otherwise unlock it first (you can find infos regarding bootloader unlock method in the general section of the Nexus 6 forum). Once/if the bootloader is unlocked, power down your device. Just press volume down and power button for a few seconds until you see a green Android laying down with it's belly opened...
Use fastboot to install TWRP using this command:
fastboot flash recovery twrp-3.1.0-0-shamu.img (the file you saved earlier on your computer).
Once it's finished, use the volume rocker and select "recovery mode" and press power button. It will reboot to TWRP.
Allow TWRP to make system modifications. Then tap install and go to the folder you saved the magical zip and install it.
Reboot and install magical manager as @snowrelyt said and you'll be ok.
Every info's you need can be found on the forum. If you're unsure, just ask again...
Good luck...
5.1 said:
Hey... You may flash TWRP recovery from bootloader using fastboot command. You can't root using stock recovery...
Download the latest TWRP from here and save it on your computer, preferably in the same folder you have ADB/fastboot:
https://dl.twrp.me/shamu/twrp-3.1.0-0-shamu.img
Just remove all security first before proceeding with the next steps (lockscreen scheme, password, pin. You can reenable them afterward. Just to avoid issues with twrp).
Your bootloader must be unlocked, otherwise unlock it first (you can find infos regarding bootloader unlock method in the general section of the Nexus 6 forum). Once/if the bootloader is unlocked, power down your device. Just press volume down and power button for a few seconds until you see a green Android laying down with it's belly opened...
Use fastboot to install TWRP using this command:
fastboot flash recovery twrp-3.1.0-0-shamu.img (the file you saved earlier on your computer).
Once it's finished, use the volume rocker and select "recovery mode" and press power button. It will reboot to TWRP.
Allow TWRP to make system modifications. Then tap install and go to the folder you saved the magical zip and install it.
Reboot and install magical manager as @snowrelyt said and you'll be ok.
Every info's you need can be found on the forum. If you're unsure, just ask again...
Good luck...
Click to expand...
Click to collapse
Thank you for this info... now I've gone down another rabbit hole after reading on different web sites
You say the bootloader must be unlocked - again after reading on different sites, there are 2 methods to determine if the bootloader is unlocked:
a) dial *#*#7378423#*#* (this did not work which upon reading said this method might now work)
b) C:\platform-tools>fastboot oem device-info
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) 'device-info' is not a supported oem command
(bootloader) See 'fastboot oem help'
FAILED (remote failure)
finished. total time: 0.007s
So 2 things; I read that if the bootloader is not unlocked and you need to unlock it, it will wipe your phone (obviously I can't have that) and secondly, the command to determine if the bootloader is unlocked did not seem to work for some reason on my PC (the 'fastboot devices' detected my phone when I ran it).
gil_happy said:
Thank you for this info... now I've gone down another rabbit hole after reading on different web sites
You say the bootloader must be unlocked - again after reading on different sites, there are 2 methods to determine if the bootloader is unlocked:
a) dial *#*#7378423#*#* (this did not work which upon reading said this method might now work)
b) C:\platform-tools>fastboot oem device-info
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) 'device-info' is not a supported oem command
(bootloader) See 'fastboot oem help'
FAILED (remote failure)
finished. total time: 0.007s
So 2 things; I read that if the bootloader is not unlocked and you need to unlock it, it will wipe your phone (obviously I can't have that) and secondly, the command to determine if the bootloader is unlocked did not seem to work for some reason on my PC (the 'fastboot devices' detected my phone when I ran it).
Click to expand...
Click to collapse
Well search how to boot into bootloader...
In bootloader you'll see this result:
Device is unlocked status code 3
If it says device locked... Well... You know what to do if you wish root...
Good luck...
5.1 said:
Hey... You may flash TWRP recovery from bootloader using fastboot command. You can't root using stock recovery...
Download the latest TWRP from here and save it on your computer, preferably in the same folder you have ADB/fastboot:
https://dl.twrp.me/shamu/twrp-3.1.0-0-shamu.img
Just remove all security first before proceeding with the next steps (lockscreen scheme, password, pin. You can reenable them afterward. Just to avoid issues with twrp).
Your bootloader must be unlocked, otherwise unlock it first (you can find infos regarding bootloader unlock method in the general section of the Nexus 6 forum). Once/if the bootloader is unlocked, power down your device. Just press volume down and power button for a few seconds until you see a green Android laying down with it's belly opened...
Use fastboot to install TWRP using this command:
fastboot flash recovery twrp-3.1.0-0-shamu.img (the file you saved earlier on your computer).
Once it's finished, use the volume rocker and select "recovery mode" and press power button. It will reboot to TWRP.
Allow TWRP to make system modifications. Then tap install and go to the folder you saved the magical zip and install it.
Reboot and install magical manager as @snowrelyt said and you'll be ok.
Every info's you need can be found on the forum. If you're unsure, just ask again...
Good luck...
Click to expand...
Click to collapse
5.1 said:
Well search how to boot into bootloader...
In bootloader you'll see this result:
Device is unlocked status code 3
If it says device locked... Well... You know what to do if you wish root...
Good luck...
Click to expand...
Click to collapse
Thanks so much! The bootloader was unlocked (I guess from an earlier root I performed using a Toolkit), and now I am rooted using Magisk.
gil_happy said:
Thanks so much! The bootloader was unlocked (I guess from an earlier root I performed using a Toolkit), and now I am rooted using Magisk.
Click to expand...
Click to collapse
Nice. Be careful what you do with your phone though. Since you seem to lack a bit of knowledge (no offence here). Read well before flashing anything... Avoid as much as possible the use of toolkits. I say this, since there are a lot of people bricking their device, unsure about what they did...
Cheers...
5.1 said:
Nice. Be careful what you do with your phone though. Since you seem to lack a bit of knowledge (no offence here). Read well before flashing anything... Avoid as much as possible the use of toolkits. I say this, since there are a lot of people bricking their and unsure about what they did...
Cheers...
Click to expand...
Click to collapse
No problem at all... thanks for the tips and advice
When i downloaded the RootNexus6MacToolkit, i unzipped the file and got this......RootNexus6MacToolkitzip.cpgz 411 bytes. What does that mean?
grunt0300 said:
When i downloaded the RootNexus6MacToolkit, i unzipped the file and got this......RootNexus6MacToolkitzip.cpgz 411 bytes. What does that mean?
Click to expand...
Click to collapse
It's the universe telling you to stop using toolkits...
Seriously though, further up this thread there are quite good instructions on how to root without toolkits.
Didgeridoohan said:
It's the universe telling you to stop using toolkits...
Seriously though, further up this thread there are quite good instructions on how to root without toolkits.
Click to expand...
Click to collapse
My problem has always been the command line. I've been reading up on terminal commands, and i might give it another try. A number of years ago, i bricked a Samsung Galaxy 3, and i've been gun shy ever since. I split my hard drive a while back, and if i can't figure out these commands, i'll go to the Windows 10 side and use Wug's toolkit.
grunt0300 said:
My problem has always been the command line. I've been reading up on terminal commands, and i might give it another try. A number of years ago, i bricked a Samsung Galaxy 3, and i've been gun shy ever since. I split my hard drive a while back, and if i can't figure out these commands, i'll go to the Windows 10 side and use Wug's toolkit.
Click to expand...
Click to collapse
As long as you keep your bootloader unlocked it's pretty difficult to brick a Nexus...
And to root your device you only really need to use two terminal commands. While in the bootloader (press and hold power + volume down to get there) run these commands from your computer (you can get adb and fastboot from here):
Code:
fastboot oem unlock
fastboot flash recovery <[I]insert_path_and_name_of_recovery_image_file_here[/I]>
The first one unlocks your bootloader. That will wipe your device though, so make sure to have a backup. If it's already unlocked, disregard....
The second one installs a custom recovery. Get the latest TWRP from here: https://twrp.me/motorola/motorolanexus6.html
After that you can boot to TWRP (from the bootloader), and flash the root zip of your choice.
Those are the basics. You've got lots more info in the stickies in the forum.
Didgeridoohan said:
As long as you keep your bootloader unlocked it's pretty difficult to brick a Nexus...
And to root your device you only really need to use two terminal commands. While in the bootloader (press and hold power + volume down to get there) run these commands from your computer (you can get adb and fastboot from here):
Code:
fastboot oem unlock
fastboot flash recovery <[I]insert_path_and_name_of_recovery_image_file_here[/I]>
The first one unlocks your bootloader. That will wipe your device though, so make sure to have a backup. If it's already unlocked, disregard....
The second one installs a custom recovery. Get the latest TWRP from here: https://twrp.me/motorola/motorolanexus6.html
After that you can boot to TWRP (from the bootloader), and flash the root zip of your choice.
Those are the basics. You've got lots more info in the stickies in the forum.
Click to expand...
Click to collapse
Getting my Nexus 6 next week. I'll let you know how it turned out. Thanks.
Hello Guys,
My R1 HD Amazon prime version got 8.4 update, since them WiFi and Bluetooth connectivity is broken/unstable. Their 8.3 has also the same issue.BLU support is also not that great.
I want to roll back the my phone to 7.4, with 8.4 on I cannot root or unlock the boot loader with tools and procedures posted earlier in the forum.
Can any one help me?
Appreciate your help.
Thanks
Gags
gags_bd said:
Hello Guys,
My R1 HD Amazon prime version got 8.4 update, since them WiFi and Bluetooth connectivity is broken/unstable. Their 8.3 has also the same issue.BLU support is also not that great.
I want to roll back the my phone to 7.4, with 8.4 on I cannot root or unlock the boot loader with tools and procedures posted earlier in the forum.
Can any one help me?
Appreciate your help.
Thanks
Gags
Click to expand...
Click to collapse
I have an Idea that I wanted to try but I cannot, because I cannot re-lock my boot loader.
It gives me lock failed error..
So the idea is as follows if you are willing and able to try it out.
I believe with a locked bootloader you are supposed to be able to boot "official" images.
So if you "fastboot boot v6.1-boot.img" android will not exactly boot into visual interface but will give adb access. And from there will be kernel before they patched dirty cow. So maybe the unlock tool will work.
UPDATE
I did complete my test and dirty-cow did work on 8.4 when I "fastboot boot 6.1-boot.img" even though the screen stayed on the frozen boot animation the whole time.
That leaves the last part of the idea needing testing , and that is the fact that fastboot supposed to allow official images to boot. And if the copy of boot.img is accepted as official.
mrmazak said:
I have an Idea that I wanted to try but I cannot, because I cannot re-lock my boot loader.
It gives me lock failed error..
So the idea is as follows if you are willing and able to try it out.
I believe with a locked bootloader you are supposed to be able to boot "official" images.
So if you "fastboot boot v6.1-boot.img" android will not exactly boot into visual interface but will give adb access. And from there will be kernel before they patched dirty cow. So maybe the unlock tool will work.
UPDATE
I did complete my test and dirty-cow did work on 8.4 when I "fastboot boot 6.1-boot.img" even though the screen stayed on the frozen boot animation the whole time.
That leaves the last part of the idea needing testing , and that is the fact that fastboot supposed to allow official images to boot. And if the copy of boot.img is accepted as official.
Click to expand...
Click to collapse
Thanks mrmazak, for your response. I am relatively new to fast boot and adb. I am happy to test if you can post the steps to follow. I have adb and fastboot utilities on my machine and can communicate to my R1 HD from my machine.
Thanks
Gags
gags_bd said:
Thanks mrmazak, for your response. I am relatively new to fast boot and adb. I am happy to test if you can post the steps to follow. I have adb and fastboot utilities on my machine and can communicate to my R1 HD from my machine.
Thanks
Gags
Click to expand...
Click to collapse
the test i propose is only to see if the image of 6.1 boot i have willl boot on locked bootloader.
If test works out good, then some type of update to the unlock tool will follow
1. open terminal
2. type "adb reboot bootloader"
3. type "fastboot boot v6.1_stock_boot.img"
I have made batch file that does those steps.
1. unzip files to location of your choice
2. connect usb cable to phone, make sure adb is enabled
3, click the "test_boot-6.1.bat"
I get the below error : -(
C:\Gags\Other\R1HD\R1-HD-Tool-V11\Tool-V11>fastboot boot v6.1-stock-boot.img
downloading 'boot.img'...
OKAY [ 1.589s]
booting...
FAILED (remote: oem unlock is false)
finished. total time: 1.589s
Note: I do not have "OEM Unlock" option in developers options.
-Gags
gags_bd said:
I get the below error : -(
C:\Gags\Other\R1HD\R1-HD-Tool-V11\Tool-V11>fastboot boot v6.1-stock-boot.img
downloading 'boot.img'...
OKAY [ 1.589s]
booting...
FAILED (remote: oem unlock is false)
finished. total time: 1.589s
Note: I do not have "OEM Unlock" option in developers options.
-Gags
Click to expand...
Click to collapse
was afraid of that. the image I have is untouched, and original, but because it was read back from device it is missing the signature.
or because the signature is below v8.4 it is rejected.
Wonder if there is a way to apply the signature file from the 8.4 update to that older boot.img.
so for now there is still no way to roll you back to older version rom.
Is it even possible to ... make it a bare metal and install everything from scratch? Similar to how we would install OS on a PC.
The situation I am in w.r.t BLU R1 HD, is something like BIOS is locked and hence I cannot boot PC from other media , in PC world?
gags_bd said:
Is it even possible to ... make it a bare metal and install everything from scratch? Similar to how we would install OS on a PC.
The situation I am in w.r.t BLU R1 HD, is something like BIOS is locked and hence I cannot boot PC from other media , in PC world?
Click to expand...
Click to collapse
The system app "settings" is what is missing the OEM unlock switch. A while ago @vampirefo patched the settings app for v17. The patched app returns the toggle. That settings app still works in v8.4 to give back the toggle. Problem is , as with most of rooting methods, stock recovery will not install unsigned packages.
It's the standard "catch 22" of rooting (if I could only.......)
Same issue as OP
I have the same issue, does anyone have a solution? I am stuck on 8.4 with slow wifi, I want to revert the update
brandex07 said:
I have the same issue, does anyone have a solution? I am stuck on 8.4 with slow wifi, I want to revert the update
Click to expand...
Click to collapse
Factory reset seems to have worked for me , I would give couple of more days to conclude.
gags_bd said:
Factory reset seems to have worked for me , I would give couple of more days to conclude.
Click to expand...
Click to collapse
Since the day I did factory reset it is working for me.
This guide won't work with OFFICIAL Oreo. I've also made a batch script for this so you don't have to type though
This is the new guide for TWRP without the need of OST. I'll cover the other thread later
What you need:
-Service bootloader which is in the attachment, just delete the .zip extension
-ADB: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
-Nokia driver, available when you plug in the phone
Tutorial:
-Install Nokia driver and ADB first in which way you feel the most convenient
-Plug in your phone after allowing USB Debugging
-Type these commands, each one at a time
Boot your phone to download mode
adb reboot bootloader
Click to expand...
Click to collapse
Get the product ID
fastboot getvar productid
Click to expand...
Click to collapse
It will throw back a string begin with D1A. Copy that string and generate its MD5. I use this service https://md5.gromweb.com
Unlock the bootloader
fastboot oem dm-verity <your MD5 here>
Click to expand...
Click to collapse
When it says failed, your MD5 might be wrong
Flash the service bootloader
fastboot flash aboot <path to mbn file>
Click to expand...
Click to collapse
BE CAREFUL AS CORRUPTED ABOOT MIGHT BRICK YOUR PHONE
If it says OK, proceed to the flashing part, else dm-verity again
Reboot bootloader again
fastboot reboot-bootloader
Click to expand...
Click to collapse
Re-unlock your bootloader
fastboot oem dm-verity <your MD5 here>
Click to expand...
Click to collapse
Congrats! Now you can flash anything you want, shoutout to anyone who provided OST
Note
-Again, special thanks to @heineken78 and @the_laser for their discussion, and anyone involved with the great tool called OST
-The command is found within the file named AdbCmdDll.dll. You can just crack open it with IDA or whatever to find the command yourself
-After flashing, log is in C:\LogData\OUT or OST. Just find the txt file which is about 15KB in size, thanks @hikari_calyx
You mean if I use this option to OEM unlock the boot loader is still locked
Note, doesnt work after Oreo update
heineken78 said:
Note, doesnt work after Oreo update
Click to expand...
Click to collapse
Do you have IDA on your PC?
wolfyapl said:
Do you have IDA on your PC?
Click to expand...
Click to collapse
Yes I have.
Tools "must have":
Beyond Compare, IDA Pro, WinHex.
heineken78 said:
Yes I have.
Tools "must have":
Beyond Compare, IDA Pro, WinHex.
Click to expand...
Click to collapse
Hey, can you patch the exe of OST 6.0.4? Thanks!
wolfyapl said:
Hey, can you patch the exe of OST 6.0.4? Thanks!
Click to expand...
Click to collapse
look here https://forum.xda-developers.com/showpost.php?p=75486360&postcount=64
heineken78 said:
look here https://forum.xda-developers.com/showpost.php?p=75486360&postcount=64
Click to expand...
Click to collapse
Do you know the password of the mbn zip?
Does it work after oreo update... Is there is any way to root oreo
Birbal said:
Does it work after oreo update... Is there is any way to root oreo
Click to expand...
Click to collapse
If you're talking about official Oreo, I'm afraid not
wolfyapl said:
If you're talking about official Oreo, I'm afraid not
Click to expand...
Click to collapse
Thanks bro for the info i am running official oreo btw
I've accidentally tried to do this with the mbn file of Nokia 5 TWRP link of this tread:
https://forum.xda-developers.com/nokia-5/development/root-twrp-nokia-5-t3703423
When I tried to reboot the bootloader, the phone started acting like it's dead and Windows couldn't recognize it anymore. Do you know how I can fix this?
LInk doesn't work
Can someone upload the TWRP link as the above one doesn't work. Thank you!
pls help
after entering "fastboot oem dm-verity e9fcead1112f39bf19a83fc753b4bc1d" it says OK but nothing happens
here:
PS C:\adb> adb reboot bootloader
PS C:\adb> fastboot devices
D1AGAD1781632534 fastboot
PS C:\adb> fastboot oem dm-verity e9fcead1112f39bf19a83fc753b4bc1d
...
OKAY [ 0.008s]
finished. total time: 0.010s
PS C:\adb> fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.016s]
finished. total time: 0.031s
It shows "Waiting for device"
It shows "Waiting for device"
When i type 2nd command line.
My phone is in download mode after i typed first line.
Please help me , I need to change my imei . So i have to root. But i am not having any proccess. I googled a lot but cant unlock the bootloader.
Even when i tried flashing twrp ,that said the same thing waiting for device in adb command line. :crying:
black screen
my device is on screen deny and windows does not recognize it, nor does it enter download mode with buttons volume up and power
thankyou ... its work for TA-1053
Besides the effort you made to place this into the forum; I disregard having to make click in a Website in Chinese.
Perhaps you know Chinese. Well.. Imagine all the users clicking blindly... Is that safe? Even though you've tested it; it is still pretty uncertain that users will not end with malware.
Or end up with anti privacy on their devices or receiving millions of ads. I honestly find this thread offensive and unsafe to everyone.
If you are the author; a mirror would be nice. Some information regarding TWRP; indicating that the TWRP itself wont be in Chinese.
Therefore i disregard this thread.
wolfyapl said:
It will throw back a string begin with D1A. Copy that string and generate its MD5. I use this service
When it says failed, your MD5 might be wrong
Click to expand...
Click to collapse
Do we need to copy that string in capital or lowercase ?
after the command "fastboot getvar productid", i'm stuck at [waiting for device]... please help me solve this