Hi guyz, i've a little problem here.
I've to Lock my bootloader. Now i did it several times, with different tools too. Now:
If i use correct droidboot version (lollipop one) and flash it, the bootloader is not (secure), so not locked.
But if i try with a tool and it flashes the KK fastboot, it works, it's relocked.
Can you tell me why? Thanks!
steakhutzeee said:
Hi guyz, i've a little problem here.
I've to Lock my bootloader. Now i did it several times, with different tools too. Now:
If i use correct droidboot version (lollipop one) and flash it, the bootloader is not (secure), so not locked.
But if i try with a tool and it flashes the KK fastboot, it works, it's relocked.
Can you tell me why? Thanks!
Click to expand...
Click to collapse
Seems the Lollipop fastboot doesn't have the signature check that kitkat fastboot has.
But, even you can flash custom files with locked bootloader and lollipop fastboot, the system don't boot, stucks at USB logo, so it means the bootloader is locked.
leonardohenrique10 said:
Seems the Lollipop fastboot doesn't have the signature check that kitkat fastboot has.
But, even you can flash custom files with locked bootloader and lollipop fastboot, the system don't boot, stucks at USB logo, so it means the bootloader is locked.
Click to expand...
Click to collapse
Thanks! You sure about this? I've to return the phone to amazon, and i would to be sure of this :silly:
steakhutzeee said:
Thanks! You sure about this? I've to return the phone to amazon, and i would to be sure of this :silly:
Click to expand...
Click to collapse
Yes, I tested in my phone, flashed custom kernel with locked bootloader and fastboot from Lollipop .87, flash sucessfully, but when I try to boot... USB logo.
Only KitKat fastboot has signature check.
leonardohenrique10 said:
Yes, I tested in my phone, flashed custom kernel with locked bootloader and fastboot from Lollipop .87, flash sucessfully, but when I try to boot... USB logo.
Only KitKat fastboot has signature check.
Click to expand...
Click to collapse
Ok, thank you
In fastboot (lollipop) i've an (?) next to signature and other values i don't remeber. You too?
steakhutzeee said:
Ok, thank you
In fastboot (lollipop) i've an (?) next to signature and other values i don't remeber. You too?
Click to expand...
Click to collapse
Yes, same on my device. I think it's normal.
Yes, fastboot mode of lollipop firmware on ZenFone 5 / 6 is able to flash custom kernel / recovery, but it won't boot until bootloader unlocked.
Related
I'm currently on lollipop stock firmware with phone rooted and bootloader unlocked. I have also flashed latest Twrp recovey.
But here is the problem, i downloaded Resurrection remix latest version and tried to flash it, but error 7 came up. I bypassed this error by editing the updater script ( i followed a tutorial ). Now when i flashed the rom it says its sucessful but when I select boot to system it goes to fastboot mode. Im a noob so please dont be harsh to me.
PLEASE HELP ME FAST
THANKS
You still need to upgrade to stock MM before flashing RR M.
24imelqui said:
You still need to upgrade to stock MM before flashing RR M.
Click to expand...
Click to collapse
WIll I have to unlock my bootloader again when i go to stock MM.
abhishek_los said:
WIll I have to unlock my bootloader again when i go to stock MM.
Click to expand...
Click to collapse
No, but to be sure go to fastboot the type:
fastboot oem device-info
if you see this -->> (bootloader)Device unlocked: true
then you are still unlocked.
24imelqui said:
No, but to be sure go to fastboot the type:
fastboot oem device-info
if you see this -->> (bootloader)Device unlocked: true
then you are still unlocked.
Click to expand...
Click to collapse
Thanks man it worked and i am able to flash Resurection remix.
Thanks a lot again
Glad I was able to help. Warning, flashing can be addictive! And make sure to have a nandroid back-up.
WRT the original post, I tried the same procedure but after having errors i flashed the twrp with adb through cmd:fastboot flash boot boot.img . And now it is showing no OS available and shows that it is not rooted in the twrp recovery. Now it is still not flashing the rom and showing error and now i have no idea what to do. So, please give me instructions on how to repair my asus zenfone 2 laser ze550kl. I did all this on MM.
If you have TWRP 3025 then you can flash any custom ROM. Try to redownload the ROM, maybe it's just a bad download. What error did you see?
Long story short. I had an Axon 7 A2017 B11 which I updated to B13. I was able to unlock the bootloader, root the phone then flash a custom rom Z.A.D.Mix7_v0.3. I was having fun with the phone but I did something very stupid when I realised I could not use Android pay due to unlocked boot loader. Without doing enough research, I went to fastboot and did a fastboot oem lock. The command was successful but I could no longer boot into the system or recovery or fastboot. I tried MiFlash with B07 which was posted in this forum, but it did not work, came back an error of bad format. Then I used axon7tool to flash TWRP 3.0.2 and the boot.img which I extracted from B13. I am now able to boot into TWRP and fastboot. But I still do not have a working system. I tried fastboot oem unlock, it does not let me do it. I flash ZAD Mix7 again but once I flash that it does not boot anymore. I am now really stuck. What should I do to go back to stock then start everything again. Thanks a lot for the help.
I understand your device doesn't boot into system anymore, but can adb on your pc detect it at all? If so, you can try following all steps after "B)" in my tutorial. I think your aboot img and fbop partition are messed up. If you can use adb to replace the files in aboot and fbop with files that allow the fastboot oem unlock command to be executed, it should be unlockable again. After that, custom ROMs should boot.
Stock bootloader
Controllerboy said:
If you can use adb to replace the files in aboot and fbop with files that allow the fastboot oem unlock command to be executed, it should be unlockable again. After that, custom ROMs should boot.
Click to expand...
Click to collapse
I'm having a similar issue. Although my phone boots to stock rom I seem to have messed up my bootloader. I had TWRP and unlocked bootloader. I, similarly, locked the bootloader and things seemed to be fine. After attempting to install Nougat received from OTA I realized my bootloader is corrupted. When I hold the power and volume up the phone seems to just turn off (or go to EDL mode? I'm not sure) I can always just hold power and it'll boot up normally. Is there a way to get the stock bootloader to work and keep it locked?
I also bricked my A7 after relocking my bootloader. I used tenfar's tool to make TWRP my boot.img, then flashed ZTE's stock B20 image. Here's the thread where I found the file links.
From there I updated all the way up to the OTA Nougat, but I suppose you can decide where you want to go after it's unbricked. Hope this helps.
Why are so many people relocking bl? Regardless, always take an ota before locking to ensure you are completely shock.
Stock bootloader
lafester said:
Why are so many people relocking bl? Regardless, always take an ota before locking to ensure you are completely shock.
Click to expand...
Click to collapse
Don't you have to be running a locked bootloader in order to be able to install OTAs?
aabnamak said:
Don't you have to be running a locked bootloader in order to be able to install OTAs?
Click to expand...
Click to collapse
Of course not.
aabnamak said:
Don't you have to be running a locked bootloader in order to be able to install OTAs?
Click to expand...
Click to collapse
No, you do not. I thought that was the case at first as well, but I was mistaken. You do, however, need the stock recovery and an untouched system partition.
My problem is that I don't seem to have a recovery at all. I realized once the ZTE logo pops up I can hold down both volume keys and get to the bootloader. The bootloader is locked but does not display a bootloader version or basedband version. I tried the tenfar tool (axon7root.exe) and now my phone doesn't boot into the system either. I really need help...
Just an update to everyone that helped.
I finally managed to fix it.
I used axon7tool to flash a signed TWRP, so that i can boot into TWRP. The signed TWRP is the only way to make it work. Then I downloaded the A2017 B11 from this thread
https://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484
There are two zip files. The boot stack and the rom. Because it is a stock rom, I can boot into the system. The next thing I did was to enable the developer option and turn back on the option to allow OEM unlock.
I went back to TWRP. boot into the fastboot screen. Then I simply typed in 'fastboot oem unlock'.
I went back to TWRP, which says can't read encrypted device. I formated everything. mount the USB then flash the custom rom again.
Hola, phone fixed. Made me sweat for the whole day.
deleted...forgot I had a micro sd card. Flashed stock update from the card and it worked. Phew!
Hi everybody
My Zenfone Selfie after a normal update (never modified) is in bootloop.
So I installed adb and fastboot and I flashed the twrp.
Then I tried in every way to flash a rom. I've tried both with official firmware and with various versions of cyanogenmod. Through fastboot and via adb sideload.
Even if seems to work, when I reboot I get the bootloop problem again.
As far as I can understand the problem it’s that I have the bootloader still locked. The official apk solution I guees it’s not applicable in my case. By fastboot oem unlock i get an error message (probably why i can not enable usb debug).
Do you know of other ways to unlock the bootloader or in general to flick my phone?
Thanks to everyone for the help
Here is a link for selfie's boot, recovery and system images for fastboot flashing
https://mega.nz/#F!Ao1RjT7D!hQ5x60r02WveB9-Hl32B4g!810z0DoQ
You can't unlocked bootloader on fastboot. I hope you can restore your device.
24imelqui said:
Here is a link for selfie's boot, recovery and system images for fastboot flashing
https://mega.nz/#F!Ao1RjT7D!hQ5x60r02WveB9-Hl32B4g!810z0DoQ
You can't unlocked bootloader on fastboot. I hope you can restore your device.
Click to expand...
Click to collapse
i tried evrything from flashing stock image , recovery partition , boot image . but nothing works. same i dont have unlocked bootloader. i am stuck at just rebooting phone. please help
Hi,
I am having a problem trying to relock my bootloader.
i am selling my g4, so needed to remove my custom rom, flash stock and relock my bootloader.
I downloaded and flashed via twrp the stock 8.1 ROM on the g4 plus page. ( stock rom in twrp format)
That went fine.
Then I booted into fastboot , and entered fastboot lock command fastboot oem lock
It said the android image was not valid?
So I then entered fastboot flashing lock
it rebooted fine to the stock android , but now the bootloader warning says ''your device has loaded a different operating system'', and thens boots 8.1.
DO you think I should go back anf flash stock rom ( not a twrp flashable version), using fastboot commands, ending with 'fastboot oem lock' ?
Just dont want to brick it, as it is now sold!
Many Thanks for any help
pootler
P.S. the TWRP I am using is a custom one ( i think )
pootler said:
Hi,
I am having a problem trying to relock my bootloader.
i am selling my g4, so needed to remove my custom rom, flash stock and relock my bootloader.
I downloaded and flashed via twrp the stock 8.1 ROM on the g4 plus page. ( stock rom in twrp format)
That went fine.
Then I booted into fastboot , and entered fastboot lock command fastboot oem lock
It said the android image was not valid?
So I then entered fastboot flashing lock
it rebooted fine to the stock android , but now the bootloader warning says ''your device has loaded a different operating system'', and thens boots 8.1.
DO you think I should go back anf flash stock rom ( not a twrp flashable version), using fastboot commands, ending with 'fastboot oem lock' ?
Just dont want to brick it, as it is now sold!
Many Thanks for any help
pootler
P.S. the TWRP I am using is a custom one ( i think )
Click to expand...
Click to collapse
Use LMSA flash rescue option if you have a Windows machine
(Lenovo) MOTO Smart Assistant (PC)
then see
Relocking the bootloader
sd_shadow said:
Use LMSA flash rescue option if you have a Windows machine
(Lenovo) MOTO Smart Assistant (PC)
then see
Relocking the bootloader
Click to expand...
Click to collapse
THanks for the reply.
Strange, thought I had already updated this
I went back to stock firmware and decided to flash with fastboot all individual files.
At some point, I got the same ''verification failed' but the command line suggested flashing system, boot, and ( something else, cant remember) again.
i did this this, and this time, no errors occured, and I had a complete install, with a locked bootloader, and no bootloader warning screen.!
Yay - result
Thanks again for your advice - I will remember it for the future.
I don't want to unlock the bootloader again and i don't like this update because it doesn't have google discover.. what can i do?
You can just stay on current version.
Or just install via fastboot and fastboot ROM
yaro666 said:
You can just stay on current version.
Or just install via fastboot and fastboot ROM
Click to expand...
Click to collapse
Without unlocking the bootloader? How?
Ok, so you stated that bootloader is locked, I thought you are considering locking it again.
In that case you have no option, but unlocking bootloader to flash different miui ROM
yaro666 said:
Ok, so you stated that bootloader is locked, I thought you are considering locking it again.
In that case you have no option, but unlocking bootloader to flash different miui ROM
Click to expand...
Click to collapse
I did exactly that. Thank you.