Hi there, let me explain...
I f*ckup re-installing the latest Oreo stock fastboot image onto my Lineage 16 December firmware, and guess what, without paying attention I choose "Flash all and lock".
So now I am bootlooping, I cannot flash anything (twrp/rom or other) through fastboot.
I can EDL flash, but since December Pie beta brought us rollback protection, flashing the latest stock Oreo fastboot with EDL image won't fix my problem.
I guess my one and only solution is to flash a Pie Fastboot image through edl. I tried with this one (https://www.theandroidsoul.com/how-to-download-mi-a1-android-pie-update/) but unfortunately mi flash tool gives my this error: "programmer file not found", I looked into the " flash_all.bat provided" and everything look fine...
So I am seeking you help. And maybe someone over here might be able to provide me a stock pie fastboot image?
Thanks in advance, cheers
I also faced this problem bro!!!
I enterd in fastboot mode and boot into twrp recovery then flashed only linegeOs 15.1 that means 8.1 then my mobile boots into system ?
i was also searching for pie fastboot image,,, but right now its not availabe,, so can you try this.. i am also using this pie https://forum.xda-developers.com/mi-a1/development/twrp-stock-8-1-0-t3856328
@Manojyaligar @taran181
Thanks for replying, my problem is I cannot flash anything through Fastboot as my phone's bootloader is actually locked.
So the only way I have to flash anything is through EDL, and I don't think that you can boot into TWRP from EDL.
Unipo said:
@[email protected]
Thanks for replying, my problem is I cannot flash anything through Fastboot as my phone's bootloader is actually locked.
So the only way I have to flash anything is through EDL, and I don't think that you can boot into TWRP from EDL.
Click to expand...
Click to collapse
You can try flashing a nougat fastboot image. That might allow you to boot up and enable unlocking the bootloader.
Unipo said:
@Manojyaligar @taran181
Thanks for replying, my problem is I cannot flash anything through Fastboot as my phone's bootloader is actually locked.
So the only way I have to flash anything is through EDL, and I don't think that you can boot into TWRP from EDL.
Click to expand...
Click to collapse
just flash oreo 8.1.1.0 version january patch 2018... you will be able to boot ... there is a chance you will loose imei,, but then flash pie through twrp you will get imei back and phone will be normal
@taran181
Will I be able to flash this ROM despite the anti-rollback protection?
Anyway I am going to give it a shot tomorrow, thank you.
Wow that was something
So tried to follow the guide on "Guides, news and discutions". But end up loosing my imei, and nothing worked I flashed nougat January and Oreo march and november, unable to recover imei.
I had to downgrade to nougat, and write back imei on nvram.
But it's all sorted now :victory:
Related
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
I came back from LOS 16.0. Flashed A2017G_B10_NOUGAT_FULL_EDL in EDL but there's a warning that my bootloader is locked. I wanted to relock it but the warning prevents me from entering bootloader or fastboot (or maybe they are not even present....). Next I flashed A2017U_FASTBOOT_UNLOCK_EDL in MiFlash but it did not do anything. It flashed OK but I still cannot access fastboot. Should I flash some marshmallow rom? Thanks in advance.
I have the same problem. Cannot enter fastboot mode on Nougat ROM.
Ok I found the way usin Axon 7 Toolkit
1. Set the Android version to 7 using option 13
2. Perform unlock bootloader
Following instruction Axon & Tookit gives you EDL image of the proper fastboot partition giving the possibility to enter fastboot mode
then fasboot oem lock
I wanted to say thanks that works, but apparently my phone is bricked now - it hangs on green ZTE logo. PC recognizes it as DFU. Cannot enter EDL either. I guess I look for some guide how to recover from this situation
Managed to fix that. Somehow I was able to enter fastboot. It said my bootloader was locked so i flashed TWRP and from TWRP using ADB installed stock Nougat rom
ma_ko said:
I wanted to say thanks that works, but apparently my phone is bricked now - it hangs on green ZTE logo. PC recognizes it as DFU. Cannot enter EDL either. I guess I look for some guide how to recover from this situation
Managed to fix that. Somehow I was able to enter fastboot. It said my bootloader was locked so i flashed TWRP and from TWRP using ADB installed stock Nougat rom
Click to expand...
Click to collapse
If you was able flash twrp mens your boolaeder was unlocked?
No there's a TWRP that works on locked bootloader.
ma_ko said:
No there's a TWRP that works on locked bootloader.
Click to expand...
Click to collapse
Seems that TWRP was inatlled before the bootloder was locked again.
I updated to Pie today using OTA. This resulted in a bootloop. Since my bootloader was already unlocked, I booted TWRP (not flashed) and swapped slots. This resulted in booting to the recovery "no command" prompt instead. So I downloaded the only ROM Xiaomi has on their site - 8.1 - and flashed this with the "flash_all_except_storage" script. Still bootloops, only now the bootloader is relocked.
So, anyone know how to unlock the bootloader on a non-booting Android One device? Is there an EDL mode on these?
tin2001 said:
I updated to Pie today using OTA. This resulted in a bootloop. Since my bootloader was already unlocked, I booted TWRP (not flashed) and swapped slots. This resulted in booting to the recovery "no command" prompt instead. So I downloaded the only ROM Xiaomi has on their site - 8.1 - and flashed this with the "flash_all_except_storage" script. Still bootloops, only now the bootloader is relocked.
So, anyone know how to unlock the bootloader on a non-booting Android One device? Is there an EDL mode on these?
Click to expand...
Click to collapse
Seriously? No one reads thread online?! I quote to NEVER, EVER, FLASH OREO/NOUGAT ROMS AFTER UPDATING TO PIE!!!
I downloaded the latest OFFICIAL ROM when it was already bootlooping.... Seriously? I'm supposed to go searching online for 3rd party information rather than the official?
Now how about people with useful information instead of arrogance?
If I'm not wrong you just need to boot into bootloader and fastboot oem unlock. With unlocked bootloader, go fastboot mode and flash official stock pie fastboot rom
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.