Database Info

[Q] stuck on: Warning bootloader unlocked screen

Guys really need some help.
Bought an unlocked Razr HD from the web, and ungraded via OTA from 4.0.4 to 4.1.2. Then I rooted using dan's method, ran the script, phone was rooted. Then i decided to install TWRP, same way, in fastboot mode, ran the cmd 'fastboot flash recovery twrp-2.5.0.0-recovery-vanquish.img' then rebooted, but what essentially happened after, i was never able to boot the phone in recovery and every single time i ended up with fastboot reason" flash failure.
Then i was able to recovery from falsh failure by running 'empty_radio.img', after rebooting, the phone started up normally, but stock recovery was still corrupt, every single time i used to get the 'red triangle dead andriod', so booted back into fastboot, performed a clean wipe with fastboot -w and booted back normally, and flash failure was gone, and i was was able to reboot the phone normally.
Then i decided to unlock the bootloader, was was successful using Dan's method; my goal was to install 4.2 from recovery. Then i installed DroidUtility and decided to perform an clean install wiping all data. The problem was at every step i got the FAILED (remote failure) line, soon after phone got stuck with fastboot reason: 'Sticky bit fastboot'.....every single time i reboot phone gets stuck in the initial screen ' WARNING BOOTLOADER UNLOCKED' and thats it....i can't do anything...stuck....screen stays on for 10mins, then reboots back to this screen and keeps on looping.
Please help guys!! i hope i haven't bricked the phone.

eomahos said:
Guys really need some help.
Bought an unlocked Razr HD from the web, and ungraded via OTA from 4.0.4 to 4.1.2. Then I rooted using dan's method, ran the script, phone was rooted. Then i decided to install TWRP, same way, in fastboot mode, ran the cmd 'fastboot flash recovery twrp-2.5.0.0-recovery-vanquish.img' then rebooted, but what essentially happened after, i was never able to boot the phone in recovery and every single time i ended up with fastboot reason" flash failure.
Then i was able to recovery from falsh failure by running 'empty_radio.img', after rebooting, the phone started up normally, but stock recovery was still corrupt, every single time i used to get the 'red triangle dead andriod', so booted back into fastboot, performed a clean wipe with fastboot -w and booted back normally, and flash failure was gone, and i was was able to reboot the phone normally.
Then i decided to unlock the bootloader, was was successful using Dan's method; my goal was to install 4.2 from recovery. Then i installed DroidUtility and decided to perform an clean install wiping all data. The problem was at every step i got the FAILED (remote failure) line, soon after phone got stuck with fastboot reason: 'Sticky bit fastboot'.....every single time i reboot phone gets stuck in the initial screen ' WARNING BOOTLOADER UNLOCKED' and thats it....i can't do anything...stuck....screen stays on for 10mins, then reboots back to this screen and keeps on looping.
Please help guys!! i hope i haven't bricked the phone.
Click to expand...
Click to collapse
Seeing how the phone is now updated to latest ota try Matt's Utility for the Droid RAZR HD i used this to get my phone is working condition then i did some adb and fastboot commands using some files to get rid of the sticky bit fastboot.
Heres a link to the RAZR HD utility: http://forum.xda-developers.com/showthread.php?t=2239425
Heres a link to get rid of the sticky bit fastboot menu (if you do end up getting this menu):http://forum.xda-developers.com/showthread.php?t=2260105
Hope this helps and good luck bro.
P.S if you did brick your phone its not the end of the world. the epic devs of XDA figured out how to fix problems like this. I bricked my phone by installing beats audio app ( worst mistake ever) came here for help and next thing i know my phone up and running like a charm ^^

well i did try matt's droid utility, and that's what put me in this state in the first place, since my stock recovery was corrupt, i decided to just clean install JB from Matt, but all the steps failed, it said remote failure at every step....and that was it! fastboot reason: flash failure,if i hold +/- and power, the phones boots up and gets stuck on the first screen..in this case since the bootloader is unlocked, it gets stuck on the WARNING message.
Also did try to fastboot with these commands:
adb reboot bootloader
fastboot oem fb_mode_set
fastboot oem fb_mode_clear
fastboot erase userdata
fastboot erase cache
fastboot reboot
same, gets stuck on WARNING screen after reboot.

eomahos said:
well i did try matt's droid utility, and that's what put me in this state in the first place, since my stock recovery was corrupt, i decided to just clean install JB from Matt, but all the steps failed, it said remote failure at every step....and that was it! fastboot reason: flash failure,if i hold +/- and power, the phones boots up and gets stuck on the first screen..in this case since the bootloader is unlocked, it gets stuck on the WARNING message.
Also did try to fastboot with these commands:
adb reboot bootloader
fastboot oem fb_mode_set
fastboot oem fb_mode_clear
fastboot erase userdata
fastboot erase cache
fastboot reboot
same, gets stuck on WARNING screen after reboot.
Click to expand...
Click to collapse
Have you tried flashing the phone with rsd lite?

Oh boy!! i made a major error, i someone didn't read the version...and used matt's utility xt912 on my xt925. is there a link for xt925? what can i do now? Can i use matt's xt926 on my 925?

eomahos said:
Oh boy!! i made a major error, i someone didn't read the version...and used matt's utility xt912 on my xt925. is there a link for xt925? what can i do now? Can i use matt's xt926 on my 925?
Click to expand...
Click to collapse
Try this: http://forum.xda-developers.com/showthread.php?t=2241788 from what i heard it works both on xt925 and xt926

oh wow....it did work. But now the problem is not sure if it locked the phone or not, but it's not recognizing my SIM. it said stock rom for both xt925/926. it seems that this is a verizom ROM, and on the device info it's listed at xt926. Not sure if that is the issue or not? can flashing the ROM lock the phone?

unfortunately, i have tried everything to install RSD, but it just wont install. Having a nightware, so all i need now is to install a stock JB ROM for xt925, but the recovery is corrupt, so need Matt's or MR. PARKINSON'S to flash a xt925 ROM. Can someone please help?

eomahos said:
unfortunately, i have tried everything to install RSD, but it just wont install. Having a nightware, so all i need now is to install a stock JB ROM for xt925, but the recovery is corrupt, so need Matt's or MR. PARKINSON'S to flash a xt925 ROM. Can someone please help?
Click to expand...
Click to collapse
Why dont you just flash twrp. Have it the same directory as the fastboot files from Hashcodes page on goo. Im. Cd to the directory with a command prompt and type faatboot flash recovery then the name of the file. Should overwrite your stock recovery and allow you to flash whatever you want.
Sent from my Transformer TF101 using xda premium

eomahos said:
unfortunately, i have tried everything to install RSD, but it just wont install. Having a nightware, so all i need now is to install a stock JB ROM for xt925, but the recovery is corrupt, so need Matt's or MR. PARKINSON'S to flash a xt925 ROM. Can someone please help?
Click to expand...
Click to collapse
I know you've stated that you can't get RSD to install, however if you can; perhaps borrow a friends computer to do it, then there's a variety of stock XT925 ROMs on this page http://sbf.droid-developers.org/vanquish_u/list.php
and instructions for flashing here http://www.andromods.com/tips-trick...-unroot-unbrick-droid-razr-maxx-hd-xt926.html which states its for the XT926 however I restored my 925 using my carrier's ROM from the first link and the tool and instructions on the second link. I only had one line with getvar in it to remove from the xml file. I've actually flashed both my carrier's ROM and then a generic one for my locale.
If you go this route, borrowing a friends computer, make sure you download the ROM from your carrier (assuming its there) with the higher version number or you'lle be attempting to flashing ICS and there's some post floating around that implies a downgrade from 4.1.2 to ICS causes problems.
The instructions look a little daunting but the xml files I saw, in both ROMs, were very short. Just be sure to use notpad when you edit. The other thing to be sure of, which isn't otherwise stated, is that RSDlite runs for a while even after the phone reboots. I made the mistake of pulling the cable when I got to the setup screen the first time I did it and thought it was a problem with the ROM or the flash of it. The reality, I think, after looking more carefully the second time, is that RSD is still running and doesn't say finished for a little bit after the boot and until I was still filling out the thing for the intial phone setup... Google acount, Google Plus, etc.
Link to a thread on the subject (also heavily 926 implied) http://forum.xda-developers.com/showthread.php?t=2211234
Since your'e unlocked you no longer need to use any exploit to gain root. Get a flashable supersu.zip on the phone, install a recovery and root you will have; just install the zip...
Have a full battery when starting the ROM flash.

thanks alot buddy, i'll start reading into it. So, i did finally manage to install TWRP, and did manage to flash the ROM with stock 4.2, tried both xt926/925, however, now the issue is i dont get any reception, nothing at all, everytime i search, it comes back with no network found. Can you please advise? i was able to bypass the corrupt recovery, install a clean 4.1.2 xt926 ROM, but i never got any reception, installed TWRP, then tried 4.2 ROMs. No, i get nothing...miss i mess up the radio?

eomahos said:
thanks alot buddy, i'll start reading into it. So, i did finally manage to install TWRP, and did manage to flash the ROM with stock 4.2, tried both xt926/925, however, now the issue is i dont get any reception, nothing at all, everytime i search, it comes back with no network found. Can you please advise? i was able to bypass the corrupt recovery, install a clean 4.1.2 xt926 ROM, but i never got any reception, installed TWRP, then tried 4.2 ROMs. No, i get nothing...miss i mess up the radio?
Click to expand...
Click to collapse
Hi, I tried replying to your PM however the server isn't reporting it sent or is having troubles sending or whatnot. Let me know if you got it or not.
In any case, of most relevance, who was your carrier when your phone did work? That is going to hopefully be the starting point, I believe.
...also, please quote my text if responding so that I get an email notification, otherwise I'll forget XDA exists for days at a time...

[Q] help - unlocked, recovery wont flash

So I have my bootloader unlocked, but for some reason I can't flash a recovery (CWM or TWRP). I've tried to flash recovery through fastboot using adb fastboot commands, mfastboot commands, and mototool aio. I've also tried to flash recovery through rom manager and rashr. ( I am rooted )
cmd: getvar:max-download--size
cmd: download:007b1800
cmd: flash:recovery
mismatched partition size (recovery)
Click to expand...
Click to collapse
I get
Boot up failed
Click to expand...
Click to collapse
Whenever trying to enter recovery afterwards. I get the warning bootloader unlocked motorolla screen for .1s before going back to fastboot.
Can anyone point me towards what I should be doing please? Thank you

Is the phone being detected when you type "adb devices" in cmd window ?
If not you need to install correct and drivers, then in while in the boot loader type "fastboot flash recovery RECOVERYNAME.img" obviously you change it to your Recovery's image file and it has to be in the directory with adb and fastboot of course.
Sent from my Nexus 5

Yes it is, it is detected as the phone boots ( it still boots to the stock rom ) and detected in fastboot as w ell.
edit:
to clarify, this is on 4.4.3 if it matters

kdbrown5 said:
Yes it is, it is detected as the phone boots ( it still boots to the stock rom ) and detected in fastboot as w ell.
edit:
to clarify, this is on 4.4.3 if it matters
Click to expand...
Click to collapse
I guess I didn't look up as well as I should have. So even with an unlocked bootloader, there are no recoveries out for 4.4.3 ?

kdbrown5 said:
I guess I didn't look up as well as I should have. So even with an unlocked bootloader, there are no recoveries out for 4.4.3 ?
Click to expand...
Click to collapse
Yeah, of course there are recoveries for 4.4.3/4.4.4. Try to flash another recovery bro
Sent from my Moto G using XDA Premium 4 mobile app

I've tried like 5 recoveries so far. i just tried cwm 6.0.4.5 and now i can't even get into the bootloader, (adb reboot recovery, as well as holding recovery keys at phone turn on) just goes into the rom now. Does it sound like i have to recover everything to stock now?
Not sure that it matters, but I am rooted if that helps or gives you ideas for any other options
edit: through rom manager i was able to reflash the latest CWM and now i have bootloader access back. I still can't get into any recovery though.

kdbrown5 said:
I've tried like 5 recoveries so far. i just tried cwm 6.0.4.5 and now i can't even get into the bootloader, (adb reboot recovery, as well as holding recovery keys at phone turn on) just goes into the rom now. Does it sound like i have to recover everything to stock now?
Not sure that it matters, but I am rooted if that helps or gives you ideas for any other options
edit: through rom manager i was able to reflash the latest CWM and now i have bootloader access back. I still can't get into any recovery though.
Click to expand...
Click to collapse
You can try to go back to stock, and after, flash a custom recovery and see what happens
Sent from my Moto G using XDA Premium 4 mobile app

Ok, I guess I'll try that tomorrow. The thing I'm wondering is, If it doesn't work flashing through fastboot, outside of the ROM, how would reverting back to stock help at all? A stock flash shouldn't change the bootloader at all?

bump : (

Can't update my phone.

Hi, I have a Moto G 1st Gen xt1033 Dual Sim. The phone, to my knowledge is completely stock, it is unrooted and I haven't tampered with anything developer-wise. The problem is that I can't seem to update the phone. I get an OTA message telling me the update is ready, I download it, my phone shuts down and then it reboots normally. Not only that, but it also enters a bootloop of about 5 boots. Afterwards, nothing happens, the update is unsuccessful. What also bothers me is that I can't enter recovery. I can select the option from the menu that appears after I press the volume down key+power button, but it just boots normally. Please help, I really want to update my phone and this is getting really annoying.

Sounds like your phone can't update and you cannot manually enter recovery mode.. Did you try re-flashing stock recovery?

I didn't, can you maybe link me to a thread that can help me do that?
Sent from my XT1033 using XDA Free mobile app

Search for your stock ROM here: http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=filename&order=ASC&show=100&page=1
If you find it, download it, unzip, use fastboot commands to flash the recovery by typing "fastboot flash recovery recovery.img" with the quotes when your phone is in fastboot mode and connected to your PC.

Alright, I'll see what I can do. Does this delete any of my files?
Sent from my XT1033 using XDA Free mobile app

No, it should not wipe your data. Just in case, make sure all of your data file are backed up somewhere else before doing any flashing.
Do you have an unlocked bootloader? I recommend unlocking the bootloader after making your backup. Restoring the phone after a bad flash is always easier with an unlocked bootloader.

Alright, I found my stock firmware, it contains a recovery.img, I set up fastboot, and I'm ready to flash the image. Do I need to uninstall the current recovery or can I just flash over it?

Also, my bootloader is locked, and I would prefer not unlocking it unless it's absolutely necessary.. Do I need to put the recovery.img into a specific folder before entering the fastboot command?

Just put recovery.img in the same folder as your fastboot command.
Just flash over the existing recovery.
If it will not flash, you may have to find a different rom or unlock the bootloader.

I managed to do everything you said. I even unlocked the bootloader and had a bit of a scare cause it got bricked so I had to eventually do a full wipe.. Afterwards I flashed the recovery, installed the 4.4.4 update and got the 5.0 update immediately. Running 5.0 now thanks to you!

Can't flash twrp need help!

Okay so I received my opo today and wanted to unlock and root etc.. I managed to install drivers and download a toolkit which managed to unlock my bootloader but wouldn't flash the recovery so I attempted it manually via fastboot and after flashing it would reboot to a back screen then vibrate and reboot to system.. Been doing that all night? Any ideas? many thanks in advance new to this phone

Exactly what recovery version are you trying to flash? What OS is on the phone? Get rid of the toolkit, they're nothing but trouble.

Twrp 2.8.1. And its running android 4.4.4 cyanogen mod.. I have mate haha. I take it fastboot and adb are installed correctly as it shows my opo after typing fastboot devices and it unlocked my boot loader soo I'm confused

daviss101 said:
Twrp 2.8.1. And its running android 4.4.4 cyanogen mod.. I have mate haha. I take it fastboot and adb are installed correctly as it shows my opo after typing fastboot devices and it unlocked my boot loader soo I'm confused
Click to expand...
Click to collapse
Try flashing the recovery again, followed by this command
Code:
fastboot erase cache
Then:
Code:
fastboot reboot
Then try booting into recovery.
PS. You've unchecked the "update CM recovery" option in Developer Options, right?

same problem for me. tried manually installing any custom recovery, tried two different toolkits. it flashes and reboots, but then you can never enter the recovery app. even attempting to put stock back fails. i attempted the format the cache and that didn't do a thing for me. basically had to enable cm recovery updates and reset to factory in the os. after that i was back to scratch at least.

I was able to figure it out. Appears the version of TWRP is quite particular for some reason. Once I tried the latest build from here dl dot twrp dot me/bacon/ the problem was solved. Thanks for the tip @snickler

GrizzlyD said:
I was able to figure it out. Appears the version of TWRP is quite particular for some reason. Once I tried the latest build from here dl dot twrp dot me/bacon/ the problem was solved. Thanks for the tip @snickler
Click to expand...
Click to collapse
No problemo. ^_^

How to Downgrade bootloader 41.1A to 41.18 or 41.19

please..
i have problem with bootloader version 41.1A
i want to Downgrade to version 41.18 or 41.19
anyone know ..??
please share it
thank you

Up
Me too
My bootloader v 41.1A I downgrade 41.18 Help

Why do you need to downgrade? Messing with Bootloaders can destroy your phone.

even i want to downgrade... I cant flash custom recovery on 41.1A

poran123 said:
even i want to downgrade... I cant flash custom recovery on 41.1A
Click to expand...
Click to collapse
Bootloader cannot be downgraded. You're stuck on w/e version you have currently installed.

Okay so I'm stuck on 41.1A and my phone will continue to restart itself and then stuck in bootloop till the battery dies... and then when I connect it to the charger boot's up normally...

@lost101
Can you please let me know how to check bootloader version?
I am using Moto G XT1033 model(Asia).
It was updated to Lollipop 5.0.2 by Motorola Stock Lollipop update.
Later on I had unlocked bootloader and downgraded it to Kitkat 4.4.4 using this thread.
I don't have any clue about current version of bootloader in my Moto G.
I want to try Lollipop 5.1 Optimized stock rom link here, so just wanted to ensure compatibility of bootloader so that my phone works after flashing it.

kalpesh.fulpagare said:
@lost101
Can you please let me know how to check bootloader version?
Click to expand...
Click to collapse
Enter bootloader (hold volume-down while turning it on), read text on screen (second line).

I too want to know if there is a way to downgrade or at least reflash my damaged bootloader which is causing weird behaviour.
Sent from my Nexus 6P using Tapatalk

I have the exact same problem.
Stuck on 41.1A
Was on a slim6 rom before. Tried to return to STOCK_ASIA_RETAIL. All fastboot commands successfully executed but no apparent change. I have the exact same wallpaper, the same layers RRO navbars, everything. I would not need to go to STOCK but since the slim installation is unstable and everything force closes, the phone is unusable.
Additional note: Somehow even TWRP is stuck in the splash screen, so cant flash any other ROM. Even tried to access TWRP using adb, but the TWRP service fails to start.
I fastboot flashed phillz recovery, stock recovery & newer TWRP versions, but nothing happens. Phone still stuck in TWRP screen.
To my surprise I was able to pull my personal files from the internal SD using ADB (which still works btw).
But I'm left with a phone in a zombie unusable condition, it just doesn't react to anything.
Any help from the XDA community would be greatly appreciated. I am still keeping my fingers crossed, so that one day a guide comes up to brick my device (STOCK 5.1 bootloader) and unbrick it using some sort of unbrick tool.

Why is not possible to create a flashable zip with the bootloader inside? I want to downgrade to KitKat bootloader too

SLATE21&MOTOG said:
Why is not possible to create a flashable zip with the bootloader inside? I want to downgrade to KitKat bootloader too
Click to expand...
Click to collapse
Creating such a zip is possible, but flashing it may either not work or hard brick your phone.

How to install working recovery on 41.1A bootloader
I had the situation on my Moto G XT1039 where I had formatted the partitions on my phone (using my old CWM recovery), then flashed the 41.1A bootloader, but 41.1A would not allow me to flash any recovery.
So I had a working bootloader, but no recovery and no OS. And apparently no way to install a recovery, to install an OS...
I got the phone back like this:
- Flashed 4.4.4 stock manually using the bootloader (if you do this, DO NOT flash the 4.4.4 motoboot.img, according to everything on here that will permanently brick your phone; I am not sure about partition gpt.bin - I flashed this, but I was already on the 4.4.4 partition layout anyway). Do flash boot.img, that is the OS boot.
- So now I had a bootable phone OS (back on 4.4.4 again, with a flickering screen), but still no recovery.
- From the bootloader, I booted into an old recovery which I knew had previously worked with my phone:
Code:
fastboot boot clockworkmodrecovery.6051.peregrine.img
(this boots into a temporary copy of the recovery, without actually installing it on the recovery partition).
- Using that, I installed the SuperSU binary.
- Then I booted back into my 4.4.4 OS, installed the SuperSU app, checked it was working, then installed the TWRP Manager app (which requires root, hence the previous steps), then used that to successfully install the TWRP recovery on my phone.
From there I now had the correct recovery in place to flash the 5.1 Optimized distro (which I would definitely recommend - clean, stable, excellent battery life!).
Yay!

Bmju said:
- So now I had a bootable phone OS (back on 4.4.4 again, with a flickering screen), but still no recovery.
- From the bootloader, I booted into an old recovery which I knew had previously worked with my phone:
Code:
fastboot boot clockworkmodrecovery.6051.peregrine.img
(this boots into a temporary copy of the recovery, without actually installing it on the recovery partition).
- Using that, I installed the SuperSU binary.
- Then I booted back into my 4.4.4 OS, installed the SuperSU app, checked it was working, then installed the TWRP Manager app (which requires root, hence the previous steps), then used that to successfully install the TWRP recovery on my phone.
Click to expand...
Click to collapse
Why didn't you simply fastboot flash a TWRP image?

_that said:
Why didn't you simply fastboot flash a TWRP image?
Click to expand...
Click to collapse
I hope I haven't misunderstood, but isn't the whole point of this thread that the 41.1A bootloader won't let some poeple (including me) successfully flash anything to the recovery partition? You can run the command, but the recovery won't boot up. At least that's how it was for me.

Bmju said:
I hope I haven't misunderstood, but isn't the whole point of this thread that the 41.1A bootloader won't let some poeple (including me) successfully flash anything to the recovery partition? You can run the command, but the recovery won't boot up. At least that's how it was for me.
Click to expand...
Click to collapse
I see. So "fastboot boot" worked, but "fastboot flash" wouldn't write anything? In that case you could probably also have used fastboot boot with TWRP and then use TWRP's "install image" feature to flash it.

_that said:
I see. So "fastboot boot" worked, but "fastboot flash" wouldn't write anything? In that case you could probably also have used fastboot boot with TWRP and then use TWRP's "install image" feature to flash it.
Click to expand...
Click to collapse
Thanks! I definitely tried that first! Maybe this bit I didn't make clear in my post, but actually:
- fastboot boot was only working for me with older recovery ROMS, i.e. the older CWM recovery which I mentioned, which I had lying around from when I first rooted my phone on 4.4.4, and also - not that it's much use - with the recovery in the 4.4.4 image, which just brings up the dead Android logo
- fastboot flash recovery was not working at all, not even with the recovery roms which would boot with fastboot boot
- but fastboot flash to all the other partitions seemed to work fine (I could see that it seemed to be working because I was able to flash different logo.bin files to change the phone logo which shows before the phone tries to boot into recovery or OS) and as per my post this was how I was able to get my phone back eventually
This thread was the only place I could find which seems to represent people having the same set of problems, so I thought the above workaround might be useful in future to someone in the same situation.

Bmju said:
- fastboot flash recovery was not working at all, not even with the recovery roms which would boot with fastboot boot
Click to expand...
Click to collapse
So far nobody has posted a terminal transcript of "not working". Did it appear to succeed or did you get an error message?
Bmju said:
- but fastboot flash to all the other partitions seemed to work fine (I could see that it seemed to be working because I was able to flash different logo.bin files to change the phone logo which shows before the phone tries to boot into recovery or OS) and as per my post this was how I was able to get my phone back eventually
Click to expand...
Click to collapse
That doesn't make any sense. Not that I don't believe you, I just can't explain how fastboot could fail writing recovery but succeed in writing a different partition.
Bmju said:
This thread was the only place I could find which seems to represent people having the same set of problems, so I thought the above workaround might be useful in future to someone in the same situation.
Click to expand...
Click to collapse
Thanks for sharing your experience though, maybe it will help someone who has the same weird issue.

_that said:
So far nobody has posted a terminal transcript of "not working". Did it appear to succeed or did you get an error message?
Click to expand...
Click to collapse
It appears to succeed, except that it gives the 'mismatched partition size error' on the bootloader screen at the end of flashing. (Although other posts seem to state that this is normal for a non-strock recovery?)

Bmju said:
It appears to succeed, except that it gives the 'mismatched partition size error' on the bootloader screen at the end of flashing. (Although other posts seem to state that this is normal for a non-strock recovery?)
Click to expand...
Click to collapse
Yes, I've got that one too, but my flashed recovery then worked fine. However I upgraded my bootloader by installing the complete 5.1 stock ROM, maybe your bootloader update was somehow incomplete.