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
Related
Hello anyone know how to remove unlock bootloader warning logo ? Please Help i will be very gratitude for any info
Just download the firmware for your region and extract the file logo_signed, put the device into fastboot mode (press power + vol -) open a console and run the command fastboot flash ulogo logo_signed and reboot your device Hope this helps
Sent from my XT890 using xda app-developers app
You can do it this way
Only ICS and, if the case, maybe Jelly Beam accesed for Homemade
Does not work on Jelly Beam accessed by OTA or RSD Lite
If you mean the caveat that you unlocked bootloader, use the information to a htcmania forum, and as if you can not make a link to there without censor me,
is simple, get files
1. - Fastboot.exe
2. - logo_signed (must be obtained from the firmware, exploring the zip file)
sorry for my bad English
Donwload files
http://db.tt/tak1LsuU
note: logo_signed file is of the firmware: Brasil.en.BR
Procedure
1. - Put the downloaded files in a folder in the root "C" on your pc, (I call this folder Android for example)
2.- Put the phone in fastboot mode (power button and Vol - squeezing them a few seconds until the screen fastboot mode) and connect with USB the phone to pc
3.- Opening a cmd screen, we stand there, I'm in cmd C:\Android\
4. - cheking with command fastboot devices
5. - Performed the command fastboot flash ulogo logo_signed
6. - Conducted after ending command fastboot reboot and that's it
7.- enjoy
Warning: only share what I see written on a forum and I served, so I do not take responsibility for any damage this may cause to your phone
hello
keeps saying somethink about verication lads!!
Does anynone know how to remove this warning from Jelly Bean?
andy_macleod said:
Does anynone know how to remove this warning from Jelly Bean?
Click to expand...
Click to collapse
My friend, download the attatched file and enter fastboot mode, in CMD prompt write the following:
fastboot flash logo logo-CMAK.bmp
fastboot flash ulogo logo-CMAK.bmp
Cheers.
xpc21 said:
My friend, download the attatched file and enter fastboot mode, in CMD prompt write the following:
fastboot flash logo logo-CMAK.bmp
fastboot flash ulogo logo-CMAK.bmp
Cheers.
Click to expand...
Click to collapse
Thanks for you quickly response.
I use stock JB 4.1, may I do your procedure or it just work with cyanogenmod rom?
andy_macleod said:
Thanks for you quickly response.
I use stock JB 4.1, may I do your procedure or it just work with cyanogenmod rom?
Click to expand...
Click to collapse
Sorry andy!
This method i´ve tried and worked on Omar-AVelar ROM April 09, the newer ones didnt worked.
I dunno if will work on another.
Bounty
andy_macleod said:
Thanks for you quickly response.
I use stock JB 4.1, may I do your procedure or it just work with cyanogenmod rom?
Click to expand...
Click to collapse
I too am interested in removing the unlocked warning on OTA JB. We should set up a bounty
xd69 said:
I too am interested in removing the unlocked warning on OTA JB. We should set up a bounty
Click to expand...
Click to collapse
The biggest problem of Razr i is the intel architecture x86 not common in mobiles.
xpc21 said:
Sorry andy!
This method i´ve tried and worked on Omar-AVelar ROM April 09, the newer ones didnt worked.
I dunno if will work on another.
Click to expand...
Click to collapse
Do you mean that you think we will never be free from this ugly warning? :crying:
marcospbs said:
Do you mean that you think we will never be free from this ugly warning? :crying:
Click to expand...
Click to collapse
I don't think so. Just for while, soon someone will find a way to disable this "ugly" warning.
xpc21 said:
My friend, download the attatched file and enter fastboot mode, in CMD prompt write the following:
fastboot flash logo logo-CMAK.bmp
fastboot flash ulogo logo-CMAK.bmp
Cheers.
Click to expand...
Click to collapse
It doesn't works on Pi-Lama ROM 0.6
I suggest you don't even try to flash it. You'll brick your phone. I'm currently stuck on Fastboot and can't boot properly, but i've a CWM backup and can't access CWM anymore.
If you're stucked, i suggest you to flash Omar-Avelar boot.img found here.
Speeding up the process
andy_macleod said:
I don't think so. Just for while, soon someone will find a way to disable this "ugly" warning.
Click to expand...
Click to collapse
A high enough bounty would make someone dev it alot faster!
xd69 said:
A high enough bounty would make someone dev it alot faster!
Click to expand...
Click to collapse
For sure. Lets find at least 100 users from razr i and all deposit US$1,00 in a specific paypall account and give the bounty for who find a way to disable this boring warning.
andy_macleod said:
For sure. Lets find at least 100 users from razr i and all deposit US$1,00 in a specific paypall account and give the bounty for who find a way to disable this boring warning.
Click to expand...
Click to collapse
Im willing to input $20 to the cause so that this gets done faster!
Any luck on JB?
Well, this is what I tried just now:
- I pulled 'logo_signed' and 'ulogo_signed' from 'CFC_9.8.2I-50_SMI-26_S7_USASMIJBRTEU.xml.zip' file, which is the one I had flashed before Omar's ROM.
- I then simple renamed them one with the name of the other (logo became ulogo and viceversa) and tried to flash via 'fastboot flash'
- The error I got was 'Invalid OSID for logo : 2' when attempted to flash 'logo_signed' and 'Invalid OSID for ulogo : 0' for 'ulogo_signed'
- Opened both files using XVI32 and found almost the same header up to hex addr 9A, where there was a 02 on logo file and a 00 on ulogo file
- I edited them, changing the 02 for 00 and viceversa, saved them and tried to flash again, I then get:
At phone's screen:
Fastboot command failed
Getvar max-download size
In cmd screen:
writing 'ulogo'...
Invalid image ulogo
Preflash validation failed
writing 'logo'...
Invalid image logo
Preflash validation failed
At least I got rid of the first error, but have no idea on this second one... any guesses?
.
Hi, what is your command line ? Do you use fastboot ? Rsd lite ?
nick7722 said:
...
- I then simple renamed them one with the name of the other (logo became ulogo and viceversa) and tried to flash via 'fastboot flash'
...
Click to expand...
Click to collapse
I was probably not very clear, I tried flashing them via fastboot, that is 'fastboot flash logo logo_signed' and 'fastboot flash ulogo ulogo_signed'
.
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
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.
Long time lurker first time poster, but I need help!!!
Getting tired of waiting for my OTA 7.11 and after a long night at work decided rather than just manually flashing the file that I would use the NRT. I must've encountered an error as it left me in Fastboot so I try to manually flash everything with it being stuck on the "Google" pre-boot screen. I try again with the version that I was on prior to update (NBD91X) and still the same results. Looking at the log from my Command Prompt I notice upon flashing the bootloader I have this error:
sending 'bootloader' (4071 KB)...
OKAY [ 0.219s]
writing 'bootloader'...
(bootloader) Motoboot: invalid GPT
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.408s
I am only able to boot into Fastboot and unable to boot into Recovery. What are my options to getting my N6 back?
Thank you all for the help.
Hi. Download last adb + fastboot executables here:
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Extract the files somewhere.
Download Google factory image and extract it in the same folder you have the fastboot executable.
Boot in bootloader "power + volume down" and follow this guide:
https://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
I always choose the second option (manually flashing all files).
Good luck..!
5.1 said:
Hi. Download last adb + fastboot executables here:
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Extract the files somewhere.
Download Google factory image and extract it in the same folder you have the fastboot executable.
Boot in bootloader "power + volume down" and follow this guide:
https://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
I always choose the second option (manually flashing all files).
Good luck..!
Click to expand...
Click to collapse
Thanks for your reply. Even after getting a fresh download of adb/fastboot files I'm still encountering this error when trying to flash the bootloader;
c:\Users\matt\Downloads\platform-tools>fastboot devices
ZX1G3249HB fastboot
c:\Users\matt\Downloads\platform-tools>fastboot flash bootloader C:\Users\matt\D
ownloads\platform-tools\shamu-n6f26r\bootloader-shamu-moto-apq8084-72.01.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:bootloader: not found
target reported max download size of 536870912 bytes
sending 'bootloader' (4071 KB)...
OKAY [ 0.134s]
writing 'bootloader'...
(bootloader) Motoboot: Preflash validation for aboot
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.433s
Any other suggestions?
bootloader is locked correct?
SynisterWolf said:
bootloader is locked correct?
Click to expand...
Click to collapse
The bootloader has been unlocked from the day I took it out of the box. I still have the little "unlocked" icon at the bottom of the "Google pre-boot" screen that it stays stuck at when I try to boot the phone.
Can you issue this command while in bootloader:
fastboot oem device-info
"Remote failure" sounds like as the bootloader is locked...
Also your problem sounds similar to this one:
https://forum.xda-developers.com/nexus-6/help/bricked-t3523844
I really don't know what you can do now sorry
5.1 said:
Can you issue this command while in bootloader:
fastboot oem device-info
"Remote failure" sounds like as the bootloader is locked...
Also your problem sounds similar to this one:
https://forum.xda-developers.com/nexus-6/help/bricked-t3523844
I really don't know what you can do now sorry
Click to expand...
Click to collapse
I just issued the command and got this back:
C:\Users\matt\Downloads\platform-tools>fastboot devices
ZX1G3249HB fastboot
C:\Users\matt\Downloads\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.011s
I hope I'm not screwed like the thread you suggested. At this point if I could just get a fresh install I'd be happy with that. Otherwise I guess I could start looking for an N6 replacement...I've put my sim card in my old MotoX 2013 and boy is this phone smaller than I remember.
AGGHHHHH!!! Thanks for your help and please let me know if there is anything else you could suggest for me to try.
Try: fastboot getvar all
Paste the result. Just hide you imei...
5.1 said:
Try: fastboot getvar all
Click to expand...
Click to collapse
I'm not sure, but wasn't it possible to unbrick the n6 by flashing the 7.0 developer preview image????
coremania said:
I'm not sure, but wasn't it possible to unbrick the n6 by flashing the 7.0 developer preview image????
Click to expand...
Click to collapse
That's interesting. I'd be game for whatever weird ass technique there is to get it up and running.
the200sx said:
That's interesting. I'd be game for whatever weird ass technique there is to get it up and running.
Click to expand...
Click to collapse
But I can't find a download of any early preview, maybe a member here has made backup. If you get a copy, try to flash it step by step without inserted simcard
Edit: may najoor has the original file for you
https://forum.xda-developers.com/nexus-6/general/android-n-preview-2-npc91k-flashable-t3358335
coremania said:
But I can't find a download of any early preview, maybe a member here has made backup. If you get a copy, try to flash it step by step without inserted simcard
Edit: may najoor has the original file for you
https://forum.xda-developers.com/nexus-6/general/android-n-preview-2-npc91k-flashable-t3358335
Click to expand...
Click to collapse
I just read through the entire thread, while it sounds like method 2 would most likely be the option considering how I can't get into recovery, I wasn't able to find where anyone talked about it unbricking the phone. At this point I'm ready to try just about anything, but I had hoped there would be a method to keep data. It may have to wait until tomorrow so I can dedicate enough time to it. In the meantime, if anyone can point me into the direction of someone being stuck similarly to me and what they did to get out of it, I would be extremely grateful.
Thanks
Hmm... Could you just try to flash twrp?
https://dl.twrp.me/shamu/twrp-3.0.3-0-shamu.img
Place the file in fastboot folder open a cmd, cd in fastboot folder and flash it:
fastboot flash recovery twrp-3.0.3-0-shamu.img
There's 0.01% it works but doesn't anything to try at this point...
5.1 said:
Hmm... Could you just try to flash twrp?
https://dl.twrp.me/shamu/twrp-3.0.3-0-shamu.img
Place the file in fastboot folder open a cmd, cd in fastboot folder and flash it:
fastboot flash recovery twrp-3.0.3-0-shamu.img
There's 0.01% it works but doesn't anything to try at this point...
Click to expand...
Click to collapse
I'll give it a shot
the200sx said:
I just read through the entire thread, while it sounds like method 2 would most likely be the option considering how I can't get into recovery, I wasn't able to find where anyone talked about it unbricking the phone. At this point I'm ready to try just about anything, but I had hoped there would be a method to keep data. It may have to wait until tomorrow so I can dedicate enough time to it. In the meantime, if anyone can point me into the direction of someone being stuck similarly to me and what they did to get out of it, I would be extremely grateful.
Thanks
Click to expand...
Click to collapse
Ok, I didn't remember this right, the developer preview ota sideloading with adb was for fixing the Google ota update which bricked some devices as the n previews were released.
But you have nothing to loose, so you may try to do this. Here's a working download in the link, if you don't sideloading the userdata your data may stay intact. https://www.reddit.com/r/nexus6/comments/49txh3/bricked_nexus_6_after_android_n_ota_update_stock/
5.1 said:
Hmm... Could you just try to flash twrp?
https://dl.twrp.me/shamu/twrp-3.0.3-0-shamu.img
Place the file in fastboot folder open a cmd, cd in fastboot folder and flash it:
fastboot flash recovery twrp-3.0.3-0-shamu.img
There's 0.01% it works but doesn't anything to try at this point...
Click to expand...
Click to collapse
It looks like it pushed the TWRP recovery but I still can't seem to get it to boot it into recovery. Only the main fastboot screen pops up trying to Power + Vol and when I VOL select it recovery, it will just reboot back to the main fastboot screen.
Damn... Try:
fastboot erase cache
And try to boot in twrp again?
5.1 said:
Damn... Try:
fastboot erase cache
And try to boot in twrp again?
Click to expand...
Click to collapse
That didn't work either. However it made it take a split-second longer to restart, which gave me a moment of hope. Hope Crushed!!!
Last question... When you power your phone, does it stay on Google logo, or boot animation forever? Or directly bootloader?
If one of the first two, is the phone detected on your computer device manager? If yes, how?
Hay soo i wanted to relock bootloader after failing to install custom recovery (both) i turned off oem unlocking in developer options and did fastboot oem lock. Now the phone is looping in "your device can't be checked for corruption. Please lock the bootloader" and it reboots and says the same again.
When i try to unlock the bootloader with fastboot oem unlock i get "FAILED (remote: Flashing Unlock is not allowed)
I really dont know what to do and i need a phone for comunication. Please help!
You should only lock the bootloader after installing the stock ROM, otherwise your device will be bricked and the only way you'll get it back working is by flashing the EDL test points near the phone's battery and reflashing the stock ROM back in EDL mode.
Try downloading this tool then try to unlock oem, flashing and flashing critical.
Yepi69 said:
You should only lock the bootloader after installing the stock ROM, otherwise your device will be bricked and the only way you'll get it back working is by flashing the EDL test points near the phone's battery and reflashing the stock ROM back in EDL mode.
Try downloading this tool then try to unlock oem, flashing and flashing critical.
Click to expand...
Click to collapse
Noted. Thanks!
I really messed up here. The problem is i toggled allow oem unlocking off and to top it all off i did oem lock. Now its bootlooped (check the video). Does xiaomi fix this by warrenty? I really dont want to open the device up because i am afraid i will do more demage and void the warrenty and the device wont ever be fixed.
NotCat_ said:
Noted. Thanks!
I really messed up here. The problem is i toggled allow oem unlocking off and to top it all off i did oem lock. Now its bootlooped (check the video). Does xiaomi fix this by warrenty? I really dont want to open the device up because i am afraid i will do more demage and void the warrenty and the device wont ever be fixed.
Click to expand...
Click to collapse
I have seen another guy who did this. How is this possible that you turn off the unlock bootloader option when you've already unlocked it? The option gets greyed out and becomes non-functional.
Anyways I guess the best option is to give your phone to Xiaomi for the fix.
Njaiker said:
I have seen another guy who did this. How is this possible that you turn off the unlock bootloader option when you've already unlocked it? The option gets greyed out and becomes non-functional.
Anyways I guess the best option is to give your phone to Xiaomi for the fix.
Click to expand...
Click to collapse
It wasn't grayed out for me. I'm thinking of test pointing the device because i dont really want to wait few months until i get my phone back from service. (There is no xiaomi service in my Country)
But i'm afraid if i open the device i will void my warrenty for future.
NotCat_ said:
It wasn't grayed out for me. I'm thinking of test pointing the device because i dont really want to wait few months until i get my phone back from service. (There is no xiaomi service in my Country)
But i'm afraid if i open the device i will void my warrenty for future.
Click to expand...
Click to collapse
I don't think you will since you don't need to disassemble the device, all you need to do is remove the aluminum back cover carefully with damaging it and you'll find the test points right besides the battery
Yepi69 said:
I don't think you will since you don't need to disassemble the device, all you need to do is remove the aluminum back cover carefully with damaging it and you'll find the test points right besides the battery
Click to expand...
Click to collapse
will try to do that. all tho i think screen goes off first thanks for your help and sparking some hope into me and my phone <3
It finally booted up! After having some hard time shorting test points i finally did and it booted up just fine! Big thanks to @Yepi69
use custom rom
NotCat_ said:
Hay soo i wanted to relock bootloader after failing to install custom recovery (both) i turned off oem unlocking in developer options and did fastboot oem lock. Now the phone is looping in "your device can't be checked for corruption. Please lock the bootloader" and it reboots and says the same again.
When i try to unlock the bootloader with fastboot oem unlock i get "FAILED (remote: Flashing Unlock is not allowed)
I really dont know what to do and i need a phone for comunication. Please help!
Click to expand...
Click to collapse
since your device is already unlocked i recommend you using havoc os need instructions? instagram hsghumaan01
honey ghumaan01 said:
since your device is already unlocked i recommend you using havoc os need instructions? instagram hsghumaan01
Click to expand...
Click to collapse
Yes i do want to flash that rom, but i can't get twrp to boot on my unit. When i do fastboot boot "recovery name".img it says everything went fine, but i get black screen and thus can't get it to work nor install.
try other slot
NotCat_ said:
Yes i do want to flash that rom, but i can't get twrp to boot on my unit. When i do fastboot boot "recovery name".img it says everything went fine, but i get black screen and thus can't get it to work nor install.
Click to expand...
Click to collapse
try on both slots
honey ghumaan01 said:
try on both slots
Click to expand...
Click to collapse
Whats the fastboot command to change slots?
Mtp works fine tho.
NotCat_ said:
Whats the fastboot command to change slots?
Mtp works fine tho.
Click to expand...
Click to collapse
fastboot set-active {a or b}
To see what slot you current is on,
fastboot getvar current-slot
the command to chang slot with fastboot is
NotCat_ said:
Whats the fastboot command to change slots?
Mtp works fine tho.
Click to expand...
Click to collapse
fastboot set_active a/b
---------- Post added at 12:44 PM ---------- Previous post was at 12:41 PM ----------
NotCat_ said:
Whats the fastboot command to change slots?
Mtp works fine tho.
Click to expand...
Click to collapse
fastboot set_active a/b not sure can be fastboot set-actve a/b , you should use pitch black recovery instead of simple twrp
---------- Post added at 12:45 PM ---------- Previous post was at 12:44 PM ----------
honey ghumaan01 said:
try on both slots
Click to expand...
Click to collapse
dm me on instagram hsghumaan01
honey ghumaan01 said:
fastboot set_active a/b
Click to expand...
Click to collapse
That command doesn't seem to work on my pc :/ cmd just gives out all commands when i type
fastboot set_active B (on pc)
And nothing happens :/
Are there any particular adb/fastboot files i need to download?
MarcusMario0605 said:
fastboot set-active {a or b}
To see what slot you current is on,
fastboot getvar current-slot
Click to expand...
Click to collapse
Took a screenshot of your comment for later, thanks!
Are there any particular adb/fastboot files i need to download?[/QUOTE]
use this tool; https://mega.nz/#!cr4SUIqY!Rzlftk2OFun8XIkNQb2aXRtP7-t3f4DB92vMIl90pgw
(this tool,can disable driver signature,Install all drivers,qcom,etc)
https://forum.xda-developers.com/showthread.php?t=2588979
Download SDK Platform-Tools for Windows ; https://developer.android.com/studio/releases/platform-tools
QDLoader HS-USB Driver ; https://mega.nz/#!EqJwTIzB!KJF3CldYq_u7KylaL0iO6rs05RWs2_dcUfaENjJcDpU
fastboot edl (useful) ; https://mega.nz/#!x6BkXY5A!hx8SXoBwd4-fW1UkZ1poHc7p-MFDaQ85FYH7Yk8bLZ8
See and here how to use adb & fastboot from any directory on pc ; https://www.xda-developers.com/adb-fastboot-any-directory-windows-linux/
all of these are useful tools,that you must to have on pc
sry for english
don't use ''oem unlock'' on this device ...
try these commands : fastboot flashing unlock / fastboot flashing unlock_critical
__Test points-edl A2 see here : https://en.miui.com/thread-3524265-1-1.html (edl mode do not need unlocked bootloader)
daitalos said:
don't use ''oem unlock'' on this device ...
try these commands : fastboot flashing unlock / fastboot flashing unlock_critical
__Test points-edl A2 see here : https://en.miui.com/thread-3524265-1-1.html (edl mode do not need unlocked bootloader)
Click to expand...
Click to collapse
I already flashed the phone with edl test points. I'm running havoc os +hex
daitalos said:
don't use ''oem unlock'' on this device ...
try these commands : fastboot flashing unlock / fastboot flashing unlock_critical
__Test points-edl A2 see here : https://en.miui.com/thread-3524265-1-1.html (edl mode do not need unlocked bootloader)
Click to expand...
Click to collapse
Why not use oem unlock?