Hi
I installed latest 20s for lepro 3 x727 and i want to install cm.
The problem is that i cannot unlock the bootloader
It said remote unlock failed.
Maybe this update came with a security patch for stop unlock bootloaders.
chemicalboyxda said:
Hi
I installed latest 20s for lepro 3 x727 and i want to install cm.
The problem is that i cannot unlock the bootloader
It said remote unlock failed.
Maybe this update came with a security patch for stop unlock bootloaders.
Click to expand...
Click to collapse
Go to the persistent bootloader unlock thread, download the bootloader files, unzip and run these commands
fastboot flash xbl xbl.elf
fastboot flash aboot emmc_appsboot.mbn
Then reboot and do the bootloader unlock command.
I've been searching for an answer to this to avoid a new thread but I will ask here. Can you confirm that taking the 20s OTA after being on stock 19s that the same unlock methods and files do still work? Thanks in advance!
I did an ota update fully stock no root.
I can confirm that unlocking the method works multiple ways:
1: LeEco aio toolkit latest version
2: Both methods in the thread of persistant bootloader unlock 19's
suhridkhan said:
Go to the persistent bootloader unlock thread, download the bootloader files, unzip and run these commands
fastboot flash xbl xbl.elf
fastboot flash aboot emmc_appsboot.mbn
Then reboot and do the bootloader unlock command.
Click to expand...
Click to collapse
That worked!!! Thanks man
xerythul said:
I've been searching for an answer to this to avoid a new thread but I will ask here. Can you confirm that taking the 20s OTA after being on stock 19s that the same unlock methods and files do still work? Thanks in advance!
Click to expand...
Click to collapse
yes...
suhridkhan said:
Go to the persistent bootloader unlock thread, download the bootloader files, unzip and run these commands
fastboot flash xbl xbl.elf
fastboot flash aboot emmc_appsboot.mbn
Then reboot and do the bootloader unlock command.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
. I can't get to flash the elf file
Sent from my SM-P600 using XDA-Developers Legacy app
how check which bootloader i have?
have new phone out of box with rom from 2016
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I finally managed to install this goddamn lollipop. I had a custom recovery and I could not find the stock version. Finally I found it here (http://forum.xda-developers.com/showthread.php?p=54872143#post54872143).
So, fastboot everything!
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
This is my OTA copied from /cache.
Name: Blur_Version.210.12.40.falcon_umts.O2SL.en.GB
SHA-1: 2d7cd57a59986f80c185fc6ab87b848e773f9ca0
Mega link: https://mega.co.nz/#!EsYFTIqL!0pBkt3m61QH2QhHzZWYe4JJDo5RXqclMegQmb4GD_Mk
Enjoy
iBART said:
edit. I'm an idiot. I copied the wrong file (Version.210.12.40). Please delete this post -.-
Click to expand...
Click to collapse
The file name of an OTA update matches the currently installed firmware. So it's probably the right file
It's the right file !!!!!!!!!!! just upload it ! I will make a mirror for google drive.
Ok. Uploading it again...
k-kuchen said:
The file name of an OTA update matches the currently installed firmware. So it's probably the right file
Click to expand...
Click to collapse
Eurofighter_ty said:
It's the right file !!!!!!!!!!! just upload it ! I will make a mirror for google drive.
Click to expand...
Click to collapse
I don't understand. I tried to update and it says "Installation aborted" due to fingerprint... it says i have the 4.3 but i have 4.4.4 installed
I think it is because i'm trying to update my phone using a custom recovery and i need the stock one.
No way. I suck. Sorry ^_^
You need to flash stock recovery from the development section.
By the way, I take it that it isn't retail but o2 filmware?
ignore this.
eemgee said:
You need to flash stock recovery from the development section.
By the way, I take it that it isn't retail but o2 filmware?
Click to expand...
Click to collapse
O2 ... inside develop section the link of stock firmawares is 404.
cra1g321 said:
Available here - http://forum.xda-developers.com/moto-g/general/xt1032-ota-5-0-2-en-gb-captured-t3050342/post59324115
Click to expand...
Click to collapse
Not really. You captured the Retail version!
iBART said:
Not really. You captured the Retail version!
Click to expand...
Click to collapse
oops my bad, thought they were the same .
Ok. Uploaded. Have fun.
Hi Everyone,
I'm using a Moto X Pure Edition XT1575 32GB running MM 6.0 stock with Feb 1, 2016 security update with unlocked bootloader.
I wanted to flash the MM 6.0 factory images released by Motorola to revert my phone to complete stock and lock the bootloader again.
When I flash, I'm getting the following error
(bootloader) Preflash validation failed
FAILED (remote failure)
Please help... I have also attached a screenshot.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Why did you fastboot oem lock begin before flashing system images? That wasn't in the list of instructions that came with the file...
mxpe 6.0
Same thing happened to me and I didn't even use the fastboot oem lock.
If the February update changed the partition then it will fail. It also happens when you try to downgrade from 6.0 to 5.1.1. If that's the case, then you just ignore it and flash the other files.
Edit: I just checked in the update zip. It updates the partition so it can't be downgraded. Just ignore that and flash the other files.
Thanks. I'm actually in the progress of downloading the files straight from Motorola so I know for sure they are legit.
Thanks everyone, I will follow the instructions and flash others.
joeldroid said:
Thanks everyone, I will follow the instructions and flash others.
Click to expand...
Click to collapse
Let me know how it goes. I'm actually gonna go back to stock just to see if it works for future use. I just received my moto x pure yesterday. I don't think the stock rom is up to date like the files from the Motorola website.
got the same issue nothing seems to work. Any ideas ?
bskbeast said:
got the same issue nothing seems to work. Any ideas ?
Click to expand...
Click to collapse
There are a dozen threads here about flashing stock images... all of them talk about pre-flash validation errors... Maybe one my signature will help?
acejavelin said:
There are a dozen threads here about flashing stock images... all of them talk about pre-flash validation errors... Maybe one my signature will help?
Click to expand...
Click to collapse
i have tried several. When i get home i will look for yours.
Thanks
Hi,
I downloaded the latest firmware miui8 from miui .com for my Redmi 2 prime to update because VOLTE was not enable.
After flashing using this command , it doesn't power on .
I use this command
Code:
fastboot flash tz tz.mbn
fastboot flash dbi sdi.mbn
fastboot flash sbl1 sbl1.mbn
fastboot flash rpm rpm.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot erase boot
fastboot flash misc misc.img
fastboot flash modem NON-HLOS.bin
fastboot flash system system.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot reboot
It doesn't detect on device manager , no recovery mode, no fastboot mode.
Completely dead, No led while charging also.
Help!
Here's the file that i use
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
try this.. http://en.miui.com/thread-382180-1-1.html
Thanks i have done it after sorting the two test points and it detect as Qualcomm.
Does this thing will happen in miui 8 lollipop firmware or only in kitkat firmwire
Broo Why u try tiz method...!! Mi flash Tool is easy method so If u r flashing redmi2 flashing tiz method.. Dont try othr methods ??
While Downgrading i bricked my redmi 2 1gb.... No response...screen dead ...but i removed the battery and pressed volume down and power button and it just vibrated then i connected to pc( thank god it was showing device id in cmd) just fresh flashed everything and it restarted and my phone was back to live.. I hope ur device gets to fastboot mode.
Hi, can anyone help me with my moto g5 plus
is failing the commands
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash recovery recovery.img
fastboot erase customize
fastboot erase clogo
help me
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
naldojesus2 said:
Hi, can anyone help me with my moto g5 plus
is failing the commands
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash recovery recovery.img
fastboot erase customize
fastboot erase clogo
help me
[IM G]https://photos.google.com/photo/AF1QipOxdS0MVvPp2_PbQ1MDTFrVJsiJ9ssl4Y_lQVQT[/ IMG]
Click to expand...
Click to collapse
Your image link is broken, can you give us more information and perhaps a copy of the terminal output?
acejavelin said:
Your image link is broken, can you give us more information and perhaps a copy of the terminal output?
Click to expand...
Click to collapse
When you restart a message appears on the ERASING screen
Before booting into recovery or booting the rom my device goes to the bootloader 1st any fix on this
skooter32 said:
Before booting into recovery or booting the rom my device goes to the bootloader 1st any fix on this
Click to expand...
Click to collapse
fastboot oem fb_mode_clear
acejavelin said:
fastboot oem fb_mode_clear
Click to expand...
Click to collapse
Cheers ?
acejavelin said:
fastboot oem fb_mode_clear
Click to expand...
Click to collapse
Thanks a tried that maybe should mention am running los 15 do a need to be on stock?
skooter32 said:
Thanks a tried that maybe should mention am running los 15 do a need to be on stock?
Click to expand...
Click to collapse
No, do the command in the bootloader... If that doesn't work, post an output of "fastboot getvar all"
acejavelin said:
No, do the command in the bootloader... If that doesn't work, post an output of "fastboot getvar all"
Click to expand...
Click to collapse
Ok then what?
---------- Post added at 05:32 AM ---------- Previous post was at 05:20 AM ----------
skooter32 said:
Ok then what?
Click to expand...
Click to collapse
EDIT
All good got it now thank you for your help bro??
So I'm trying to root my huawei p9 lite vns-l31 but had no luck
I did ulock bootloader and i do get the message when i reboot
but why i try to boot into the twrp from fastboot i get FAILED (remote: Command not allowed)
also the thing when you press the power button and vol up it will jsut reboot it
I tried many TWRP files none woked also I have android 7.0 and emui 5.0
P.S. sorry for bad english
Unlock bootloader again with ADB command:
"Fastboot oem unlock YOUR_CODE"
Reboot and flash a good version of TWRP for you.
Done!
Therand said:
Unlock bootloader again with ADB command:
"Fastboot oem unlock YOUR_CODE"
Reboot and flash a good version of TWRP for you.
Done!
Click to expand...
Click to collapse
Not working for me aswell
chakalovski2 said:
Not working for me aswell
Click to expand...
Click to collapse
What's not work?
ADB command?
Or fastboot?
What's return of command?
Error text?
What did you make on your phone?
How do you want help without explaining your problem?..
Hello,
When I try to send a command as flashing through fastboot it's telling me command not allowed it's kind of impossible to write or send data like a flash to my phone. Though the drivers are installed and adb too.
help me pls Command Not Allowed
I have bootloader code but when I write the command fastboot oem unlock ******* I get the command not allowed error 210 stock rom is not loaded with the three key method I want to install a twrp in vendor, system, product invalid argument error how to fixed pls help me (sorry my bad english) i can not open the oem lock because i do not know how to use the usb debug mode
Elite Rom 5.1 (Hassan Mirza) came to me after I uploaded it and I could not fix it again
TEL: P9 LİTE VNS-L31
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please help me
did you fixed that error
Failed (Remote: Command not allowed)
If yes How?
Because i am also in same problem...:crying::crying::crying:
Revert to stock OS, then go to Developer settings and enable OEM unlock.
Then repeat hte process.
How can I get the stock OS without TWRP? I tryed dload method, but theres is allways a problem when eRecovery tries to install the update.zip... Idon't know what to do.. My bluetooth is not working, that my problem