Hello guys I have the version bln-l21c185 so I was at bln-l21c185b140 (4.1.3 MM) I had no updates nothing so I decided to update manually I unlocked the bootloader install twrp I downloaded the bln-l21c185b361 and updated with FF app when the updated download my phone turn it off and boot to twrp after the installation was completed it was all good but now I tried to boot to bootloader it doesn't boot at all it goes to this yellow letter with the options to boot the device or to boot to erecovery and when I tried to boot to twrp it boot to erecovery
Any help how to got back again the bootloader ?
Maybe with the update I lock my bootloader ?
Place update.app in sdcard then boot into fastboot by holding volume down button and plug in usb. Then flash stock recovery and shutdown phone and boot phone using 3 button combination method
Related
Hi there,
Yesterday I decided to upgrade from 5.1.1 (Sultan unofficial) to 6.0.1 (Sultan unofficial). :good:
Sh*t went down because I was running TWRP 2.8.6.1 and OP stated you must run 2.8.6.0.
So I got stuck into bootloot, hence I booted into recovery, put image of 2.8.6.0 into my phone and then flashed the img file through the appropriate menu.
Sh*t went down once again (And I'm not sure of why, but maybe because you cannot downgrade that way). Now I have a messed up recovery.
Well then, I get into fastboot, use Wugfresh's one-click-tool to flash back to 5.1.1. Everything goes well : my phone boots up :good:.
I disable update recovery with system updates in developers options (even though I am aware that this switch doesn't work on Lollipop)
Then I decide to root again and install TWRP 2.8.6.0 and the process fails : not that I get errors, but the command :
fastboot boot recovery.img
isn't doing its thing, hence I never boot into recovery
I'm quite surprised, but well I try to flash recovery :
fastboot flash recovery twrp-2.8.6.0.img
command executes without errors
I reboot into cm, try to boot into recovery and :
"Surprise Motherf*cker !" CM recovery shows.
I read that I must clear cache before (or after) flashing recovery
fastboot erase cache
Then shut the phone down holding Vol-down and power buttons and then boot into recovery holding Vol-down once again.
No luck, this time, every time I try to boot into recovery with this method, 1+ logo shows, phone vibrates, and 1+ logo shows etc. indefinitely
I abandoned... flashed 4.4.4 used wugfresh tool to root and flash twrp, then flashed marshmallow
Now I am rooted and running Marshmallow, but TWRP has been erased... Tried to flash through Flashify and Rashr, no luck.
(I disabled update cm recovery under developer settings)
Does someone understand why I don't manage to get TWRP under Android 5 and 6, and could explain me why ? :fingers-crossed:
Thank you !
debilausaure said:
Hi there,
Yesterday I decided to upgrade from 5.1.1 (Sultan unofficial) to 6.0.1 (Sultan unofficial). :good:
Sh*t went down because I was running TWRP 2.8.6.1 and OP stated you must run 2.8.6.0.
So I got stuck into bootloot, hence I booted into recovery, put image of 2.8.6.0 into my phone and then flashed the img file through the appropriate menu.
Sh*t went down once again (And I'm not sure of why, but maybe because you cannot downgrade that way). Now I have a messed up recovery.
Well then, I get into fastboot, use Wugfresh's one-click-tool to flash back to 5.1.1. Everything goes well : my phone boots up :good:.
I disable update recovery with system updates in developers options (even though I am aware that this switch doesn't work on Lollipop)
Then I decide to root again and install TWRP 2.8.6.0 and the process fails : not that I get errors, but the command :
fastboot boot recovery.img
isn't doing its thing, hence I never boot into recovery
I'm quite surprised, but well I try to flash recovery :
fastboot flash recovery twrp-2.8.6.0.img
command executes without errors
I reboot into cm, try to boot into recovery and :
"Surprise Motherf*cker !" CM recovery shows.
I read that I must clear cache before (or after) flashing recovery
fastboot erase cache
Then shut the phone down holding Vol-down and power buttons and then boot into recovery holding Vol-down once again.
No luck, this time, every time I try to boot into recovery with this method, 1+ logo shows, phone vibrates, and 1+ logo shows etc. indefinitely
I abandoned... flashed 4.4.4 used wugfresh tool to root and flash twrp, then flashed marshmallow
Now I am rooted and running Marshmallow, but TWRP has been erased... Tried to flash through Flashify and Rashr, no luck.
(I disabled update cm recovery under developer settings)
Does someone understand why I don't manage to get TWRP under Android 5 and 6, and could explain me why ? :fingers-crossed:
Thank you !
Click to expand...
Click to collapse
Normally when you flash TWRP via fastboot, if you boot to the OS it will replace your recovery so the workaround is to flash recovery via fastboot. Turn off phone via long pressing power button then volume down + power button and you should have TWRP. That's how I've always done it
Sent from my A0001 using Tapatalk
Renosh said:
Normally when you flash TWRP via fastboot, if you boot to the OS it will replace your recovery so the workaround is to flash recovery via fastboot. Turn off phone via long pressing power button then volume down + power button and you should have TWRP. That's how I've always done it
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Thank you for your answer
As I mentionned, I have already tried the method you described, I just ran through the process again to confirm you this isn't working
The commands I used :
Code:
C:\adb>adb reboot bootloader
C:\adb>fastboot flash recovery twrp-2.8.6.0-bacon.img
target reported max download size of 1073741824 bytes
sending 'recovery' (10180 KB)...
OKAY [ 0.313s]
writing 'recovery'...
OKAY [ 0.156s]
finished. total time: 0.469s
Then I unplug my phone, then long press power button, and when the phone is off I press power button + volume down
With this process 1+ logo shows up for 7~8 secs, then the phone vibrates and the screen goes dark, and then the 1+ logo shows up again indefinitely like there's no recovery to be found...
If I release vol-down, phone ends up booting system
SUMMARY OF PROBLEM WHAT HAPPENED:
1.Flashed an miui 8 stable rom from xiaomi.eu not official rom so it shouldn't lock bootloader.
2.Cant boot into any recovery i just get miui boot up logo then then it turns off.
3.Cant root via kingroot and other root apps ect to flash twrp via flashify.
4. Cant manually enter fastboot due to damaged volume down button not working *(The plastic​ film. On the button ripped off)*
5.Don't know other way to enter fast boot please help!
:crying:
Fix your volume button first
By flashing MIUI you most likely updated your bootloader to nougat, which removed TWRP. You need to apply for xiaomi permission to unlock bootloader and then reflash TWRP in fastboot. If you can't go into fastboot you should be able to use ADB commands or a terminal app.
Edit: Terminal app requires root to reboot so that's not an option. I can't try adb because I don't have access to PC right now.
I want to root my device:angel: Huawei GR5 mini NMO-L31 emui 5.0. so I unlock bootloader and flash twrp IMG file.
I use this commands...
adb reboot bootloader
fastboot flash recovery twrp.img
fastboot reboot
It worked successfuly:good:. But when I tried to go on recovery mode by powering off my device and perss power button and volume up Button my phone shows a warning message and below that it shows your device is booting now.
I wait about 1 hour but it still the same.
What to do now?
Please help me xda-devolopers with possible way.
THANK YOU.
Hello everyone, i have an honor 8 frd-l09c432(europe)
so i flashed a wrong kernel in twrp and fastboot
and now the phone can't boot
i can get into fastboot and flash stuff
erecovery works in factory resetting and cache partition cleaning
my bootloader is unlocked
my phone is frp unlocked
when i flash twrp in fastboot and reboot to recovery, it doesn't boot twrp but the stock recovery ( idk why )
so anyone can help ?
and when i put my phone in charge when its off
a message appears to update again
no : 10 ( boot image
no : 2 ( load failed )
which im guessing its because of the wrong kernel flash
so what should i flash in fastboot to unbrick my phone ?
i have update.app extracted and etc ... ( please please if anyone can help )
OPTION 1: MAYBE MIGHT BE WHY FLASHING MIGHT NOT BE WORKING
Make sure that you are not trying to flash the recovery.img on the error fastboot look alike screen, because I dont think you can flash files when on that screen error screen. Try to boot into fastboot without the errors on the screen.
OPTION 2: FLASH STOCK KERNEL IMAGE
You can flash kernel images using adb:
"fastboot flash kernel [KERNEL.IMG]"
Make sure that you are not trying to flash the recovery.img on the error fastboot look alike screen, because I dont think you can flash files when on that screen error screen.
OPTION 3: IF YOU WANT TO BOOT INTO TWRP WITHOUT FLASHING
1. Connect device to computer and boot into fastboot, make sure that you are not on the error fastboot look alike screen because I dont think you can flash files when on that screen error screen.
2. On adb, do "fastboot boot [Recovery File]"
3. It should boot into the recovery file you put in there
OPTION 4:: RESET DEVICE FROM ERECOVERY FROM "recovery2"
If those did not work, restart you device and when it says "Your device has been unlocked and can't be trusted", quickly hold volume up until you have booted into a stock recovery look alike "recovery2", which has an extra button.If you do not have the button, you need to hold the volume up button faster on the "Your device has been unlocked and can't be trusted" screen. When on the stock recovery look alike screen,, click the option that says something about download latest firmware. Select your wifi and it should download stock oreo and fix device, but though, it will factory reset device.
The Honor 8 has 2 recoveries called maybe "recovery" where you usually flash twrp and "recovery2" when you hold the volume button up on "Your device has been unlocked and can't be trusted"
The bootloader should relock after this
if you manage to boot into twrp and reflash back to the kernel then you dont have to do this.
CHECK_123 said:
OPTION 1: MAYBE MIGHT BE WHY FLASHING MIGHT NOT BE WORKING
Make sure that you are not trying to flash the recovery.img on the error fastboot look alike screen, because I dont think you can flash files when on that screen error screen. Try to boot into fastboot without the errors on the screen.
OPTION 2: FLASH STOCK KERNEL IMAGE
You can flash kernel images using adb:
"fastboot flash kernel [KERNEL.IMG]"
Make sure that you are not trying to flash the recovery.img on the error fastboot look alike screen, because I dont think you can flash files when on that screen error screen.
OPTION 3: IF YOU WANT TO BOOT INTO TWRP WITHOUT FLASHING
1. Connect device to computer and boot into fastboot, make sure that you are not on the error fastboot look alike screen because I dont think you can flash files when on that screen error screen.
2. On adb, do "fastboot boot [Recovery File]"
3. It should boot into the recovery file you put in there
OPTION 4:: RESET DEVICE FROM ERECOVERY FROM "recovery2"
If those did not work, restart you device and when it says "Your device has been unlocked and can't be trusted", quickly hold volume up until you have booted into a stock recovery look alike "recovery2", which has an extra button.If you do not have the button, you need to hold the volume up button faster on the "Your device has been unlocked and can't be trusted" screen. When on the stock recovery look alike screen,, click the option that says something about download latest firmware. Select your wifi and it should download stock oreo and fix device, but though, it will factory reset device.
The Honor 8 has 2 recoveries called maybe "recovery" where you usually flash twrp and "recovery2" when you hold the volume button up on "Your device has been unlocked and can't be trusted"
The bootloader should relock after this
if you manage to boot into twrp and reflash back to the kernel then you dont have to do this.
Click to expand...
Click to collapse
Hi, Thanks for the fully informative reply
I got my phone unbricked a week after this thread but somehow i completely forgot to close the thread
so, sorry about my mistake, I'm new to xda
have a nice day
Hi all,
I was following the steps to root my pixel 6a using Magdisk I had put the patch boot image on my macbook and then went into fastboot, and then used the command "fastboot flash boot [image]"
I got the okays and then I went to reboot and it's stuck in a boot loop.
I've tried to get into recovery but I just keep getting a splash screen about the device bootloader being unlocked.
Any suggestions? I've tried rescue mode too but it also goes to the bootloader unlocked screen.
Hold the power button till it turns off, volume down + power button to get to bootloader. Reflash stock boot.
ALWAYS fastboot boot first before actually flashing in case this happens
Make sure you're using the correct boot image to patch for your build number too
AphoticAffinity said:
Hi all,
I was following the steps to root my pixel 6a using Magdisk I had put the patch boot image on my macbook and then went into fastboot, and then used the command "fastboot flash boot [image]"
I got the okays and then I went to reboot and it's stuck in a boot loop.
I've tried to get into recovery but I just keep getting a splash screen about the device bootloader being unlocked.
Any suggestions? I've tried rescue mode too but it also goes to the bootloader unlocked screen.
Click to expand...
Click to collapse
What version of Magisk did you use? You must use 24.0 or newer.
As @ctfrommn recommended, you can "live boot" the patched image instead of flashing it:
fastboot boot <patched boot image>
If this fails for whatever reason, it'll reboot with the stock boot image.