Database Info

Stuck at "...unlocked...booting now..." Bricked?

Solved.
AL10, NXT-C900B133, rescue0.3, NEXT
I unlocked bootloader, installed TWRP, and rooted using SuperSU with no problem by following these directions:
http://forum.xda-developers.com/mate-8/general/guide-unlock-bootloader-root-install-t3301371
I then formatted data using TWRP wipe, then tried to install Stock Rooted No Encrypted Boot from
http://forum.xda-developers.com/mate-8/development/rom-stock-rooted-encrypted-boot-t3303606
The phone never gets past "...unlocked...booting now...." (I did not install insecure_boot because I had trouble finding it---it is not in Mate 8 Android Development, only in Mate 8 Original Android Development.)
I can get to fastboot and to the Huawei recovery in Chinese (which doesn't work---wifi downloading stops with an exclamation point), but TWRP is gone, and I can't get it back by reflashing it. I've tried HiSuite recovery, unbricking using the Italian knife following these instructions:
http://forum.xda-developers.com/mate-8/general/unbrick-updating-to-b321-t3375934
with various roms, and I've tried force flashing an UPDATE.APP from /sdcard/dload. No joy.
I caused the problem by installing a B331 rom when I was at B133—dyslexic much? Once I got TWRP back, flashing a B180 rom worked fine.
The difficulty was getting TWRP back. To do that, I flashed the following files using fastboot—it may be overkill:
TWRP-2.8.7.0-ENG.img,
insecure_boot_b331.img,
and the files in
L29Fastboot.rar.
TWRP

Hey ho!
I had exactly the same problem yesterday.
I figured out my system only was able to boot when I hold down [vol-]&[power].
Then the "not trusted message" had a few more lines and the phone booted up.
When it's up again, you can use adb to reboot to fastboot: adb reboot bootloader
You can also try to go directly to recovery if you alrteady flashed it: adb reboot recovery
From threre you can try again.
btw: I had to use a complete different TWRP version. 3.x somewhat. I think it was from here: http://forum.xda-developers.com/mate-8/development/recovery-twrp-huawei-mate-8-t3298567
Info: I was NOT able to use [vol+]&[power] for Recovery, eRecovery or anything else. I was just stuck.
I hope it helps.

I recommend after getting your device back on track to use twrp to make a recovery on your microsd card. That way u have a sure chance of getting bwck to working order

Same problem here, but when I try to flash recovery or boot image using fastboot, I get the message "FAILED <Remote: command not allowed> ".
Any idea?

iAngus said:
Same problem here, but when I try to flash recovery or boot image using fastboot, I get the message "FAILED <Remote: command not allowed> ".
Any idea?
Click to expand...
Click to collapse
Make sure you have turned on debugging mode and that your device is listed with "fastboot devices".

Make sure you have turned on debugging mode and that your device is listed with "fastboot devices".
Click to expand...
Click to collapse
The debugging mode is on since I unlocked and rooted the phone and the device is listed in "fastboot devices".

iAngus said:
The debugging mode is on since I unlocked and rooted the phone and the device is listed in "fastboot devices".
Click to expand...
Click to collapse
you could fix the same problem I have is not to do help me

Trying to flash TRWP Moto Z recovery - not working

Hey everyone, longtime lurker here finally going to try to get involved more since I just got a new Moto Z and I don't have much of a background with motorola hardware/software. I'm trying to flash recoveries through fastboot and I can't seem to get it working. I'm probably going to wait a while before I try again since there is not much support for the moto z yet. I am running MPL24.246-45 v6.0.1 XT1650-03, I have unlocked the bootloader through the instructions on the motorola website.
On the bootloader screen I can confirm it is now unlocked, but everytime I flash the TRWP recovery through fastboot I get the error message: "<bootloader> img not working or corrupt". I am trying to flash the most recent twrp recoveries for moto Z (twrp-3.0.2-0-griffin.img) but wasn't able to successfully flash it.
Coming from a samsung background, I might be skipping a step or doing something wrong. I am running the bell canadian firmware. Since I messed up my partitions on my last phone I want to be careful with this one, I mostly want to figure out why I am getting this error while trying to flash the recovery when
my bootloader is unlocked and when I check "adb devices" my moto is being read.
Thanks!!
szork

spacezork said:
Hey everyone, longtime lurker here finally going to try to get involved more since I just got a new Moto Z and I don't have much of a background with motorola hardware/software. I'm trying to flash recoveries through fastboot and I can't seem to get it working. I'm probably going to wait a while before I try again since there is not much support for the moto z yet. I am running MPL24.246-45 v6.0.1 XT1650-03, I have unlocked the bootloader through the instructions on the motorola website.
On the bootloader screen I can confirm it is now unlocked, but everytime I flash the TRWP recovery through fastboot I get the error message: "<bootloader> img not working or corrupt". I am trying to flash the most recent twrp recoveries for moto Z (twrp-3.0.2-0-griffin.img) but wasn't able to successfully flash it.
Coming from a samsung background, I might be skipping a step or doing something wrong. I am running the bell canadian firmware. Since I messed up my partitions on my last phone I want to be careful with this one, I mostly want to figure out why I am getting this error while trying to flash the recovery when
my bootloader is unlocked and when I check "adb devices" my moto is being read.
Thanks!!
szork
Click to expand...
Click to collapse
didn't try it yet, but did you try renaming it to recovery.img (if on windows be sure extenstions are shown so it is not actually recovery.img.img) and run (didn't see which command you are using:
Code:
fastboot flash recovery recovery.img
but search around forums about encryption thing and similar

the ljubich said:
didn't try it yet, but did you try renaming it to recovery.img (if on windows be sure extenstions are shown so it is not actually recovery.img.img) and run (didn't see which command you are using:
Code:
fastboot flash recovery recovery.img
but search around forums about encryption thing and similar
Click to expand...
Click to collapse
I've tried both with the original twrp name and extension as well as with renaming it to recovery.img, didn't seem to make a difference. If I am connection to the device itself does that mean that adb/sideload is installed properly? I mean I was able to unlocked the bootloader so I would assume so.
szork

spacezork said:
I've tried both with the original twrp name and extension as well as with renaming it to recovery.img, didn't seem to make a difference. If I am connection to the device itself does that mean that adb/sideload is installed properly? I mean I was able to unlocked the bootloader so I would assume so.
szork
Click to expand...
Click to collapse
i really don't know then.. if you successfully unlocked bootloader then fastboot should be ok. you can check in device manager. it should be bootloader iterface not adb interface there (you got me confused with mentioning adb so I am just writing to be sure).
also check if your device is shown when typing
Code:
fastboot devices
or try redownloading twrp.
otherwise I am out of ideas, sorry.

the ljubich said:
i really don't know then.. if you successfully unlocked bootloader then fastboot should be ok. you can check in device manager. it should be bootloader iterface not adb interface there (you got me confused with mentioning adb so I am just writing to be sure).
also check if your device is shown when typing
Code:
fastboot devices
or try redownloading twrp.
otherwise I am out of ideas, sorry.
Click to expand...
Click to collapse
Sorry for my confusion with adb/sideload - from what I understand I need both to be able to connect to my device (correct me if im wrong). In the bootloader menu I see "flashing_unlocked" which I believe confirms my bootloader being unlocked, but then at the top of the text right under the dead android guy I see "AP Fastboot Flash Mode (Secure)" could that be an issue?
I can retry downloading the recovery from the TWRP site, but I know I'm downloading the official one already, just can't put my finger on why I'm getting that error message if others are doing it successfully.
thanks for helping :good:

Do you have the Verizon model?

samwathegreat said:
Do you have the Verizon model?
Click to expand...
Click to collapse
I have the canadian BELL model XT1650-03

spacezork said:
I have the canadian BELL model XT1650-03
Click to expand...
Click to collapse
You're at the bootloader, it says Flashing Unlock so yes your bootloader is unlocked and you should be able to flash TWRP no problem.
Did you recently install this .45 firmware? Are you sure that TWRP wasnt actually flashed? I see lots of errors like this from the bootloader and its usually just rubbish.

The twrp does not show the actual memory value of my cell phone and does not let me paste ROM backup, from insufficient memory? how to support it?

I updated my phone to .45 when I bought the phone I believe 1-2 weeks ago, it's definitely NOT flashed as the flashing process runs for 0.2 seconds and fails. I can even boot in the stock recovery afterwards confirming that nothing flashed. I wish I knew what I was doing wrong? possibility of drivers not installed properly?
Before I try and flash recovery I check USB debugging, OEM is unlocked, don't verify ADB files and accept Unknown sources. Is there anything I'm missing?

What if fastboot boot twrpname.img
It's really weird anyway...

enetec said:
What if fastboot boot twrpname.img
It's really weird anyway...
Click to expand...
Click to collapse
I've been doing fastboot flash twrpname.img after opening cmd terminal with SHIFT-MOUSE2 in the designated folder. I have not tried that command specifically what's the difference between doing fastboot flash/boot as far as flashing a recovery.img
edit: I've read on different articles that people sometimes try and flash from the recovery menu? I understood it has to be while your are on the bootloader screen, could it be something to do with that? Or is it still a possibility the drivers may not be installed properly.

spacezork said:
I've been doing fastboot flash twrpname.img after opening cmd terminal with SHIFT-MOUSE2 in the designated folder. I have not tried that command specifically what's the difference between doing fastboot flash/boot as far as flashing a recovery.img
edit: I've read on different articles that people sometimes try and flash from the recovery menu? I understood it has to be while your are on the bootloader screen, could it be something to do with that? Or is it still a possibility the drivers may not be installed properly.
Click to expand...
Click to collapse
With fastboot boot you send recovery to your phone and ask it to boot on it without really flashing it...
It's useful e.g. to take a full stock backup including original recovery, to test a recovery prior to flash it or to use TWRP to root BUT remain on stock recovery...
Not on all phones it works, but on Moto Z should....
P.S.: you have to be on fastboot screen not on recovery when flashing...

enetec said:
With fastboot boot you send recovery to your phone and ask it to boot on it without really flashing it...
It's useful e.g. to take a full stock backup including original recovery, to test a recovery prior to flash it or to use TWRP to root BUT remain on stock recovery...
Not on all phones it works, but on Moto Z should....
P.S.: you have to be on fastboot screen not on recovery when flashing...
Click to expand...
Click to collapse
by fastboot screen you mean the bootloader menu right?
I've been accessing cmd from designated folder with .img file in it
- adb fastboot recovery
- fastboot flash recovery.img..
and I get the "img not working or corrupt" after it tries to flash it (lasts 0.2 seconds) and nothing is done.

spacezork said:
by fastboot screen you mean the bootloader menu right?
I've been accessing cmd from designated folder with .img file in it
- adb fastboot recovery
- fastboot flash recovery.img..
and I get the "img not working or corrupt" after it tries to flash it (lasts 0.2 seconds) and nothing is done.
Click to expand...
Click to collapse
Right, bootloader screen. Enter on it by key-comb... not by command...
Even the real flash take same time... Sending seems to work, is something on verify that doesn't "like" it...
Try to download again recovery and/or check its MD5...

if reading correctly (and what I told you yesterday) command is
fastboot flash recovery recovery.img
and not
fastboot flash recovery.img

hi can any one help me i need to get back to stock and lock boot loader to update i have eu any one please ???????????

Troll amiga said:
hi can any one help me i need to get back to stock and lock boot loader to update i have eu any one please ???????????
Click to expand...
Click to collapse
try following this instructions: http://forum.xda-developers.com/showpost.php?p=69065373&postcount=14
and download eu rom from here: https://mirrors.lolinet.com/firmware/moto/griffin/official/RETEU/
i don't know from which ROM you are coming, don't know if downgrading works, but this was onl RETEU ROM i could find.

I have the exact same phone and I've upgraded to Nougat but I got my TWRP working. You need an unlocked bootloader and after upgrading to nougat, the option "unlock OEM" need to be enabled again.
I've used this TWRP : https://dl.twrp.me/griffin/twrp-3.0.2-0-griffin.img.html
Also I tried to only boot on it at first with the command fastboot boot twrp.img then I saw it was working, I flashed it with fastboot flash recovery twrp.img but got the error : (bootloader) image not signed or corrupt . But I booted the recovery from the bootloader and TWRP was working even with this error.

cilk said:
...I flashed it with fastboot flash recovery twrp.img but got the error : (bootloader) image not signed or corrupt . But I booted the recovery from the bootloader and TWRP was working even with this error.
Click to expand...
Click to collapse
Yeessss... I don't know how could I forgot it!!! :silly:
The message (I forgot I received too...) is *only* to indicate that recovery is not signed! But before there is a clear "Done" confirming the flash!
Just boot on it!

Pixel 2 Recovery Not Working

Hello, I tried resetting my phone and flashing the latest Verizon pixel factory image by using the flash-all.bat file that comes with
"walleye-opd3.170816.012-factory-9626515d"
The bootloader fails to enter recovery mode, cycling back to the bootloader menu. The same thing occurs when I attempt to power on the device from "Start". The bootloader is also unlocked.
Put simply, the device isn't recognized via adb, but it's accessible through fastboot. I can't execute "fastboot boot x.img" because it keeps saying it can't authenticate the image.

Update your adb/fastboot. Only the latest adb works for the Pixel 2.

tina v. said:
Hello, I tried resetting my phone and flashing the latest Verizon pixel factory image by using the flash-all.bat file that comes with
"walleye-opd3.170816.012-factory-9626515d"
The bootloader fails to enter recovery mode, cycling back to the bootloader menu. The same thing occurs when I attempt to power on the device from "Start". The bootloader is also unlocked.
Put simply, the device isn't recognized via adb, but it's accessible through fastboot. I can't execute "fastboot boot x.img" because it keeps saying it can't authenticate the image.
Click to expand...
Click to collapse
You are not the only one. I have the same issue with taimen-opd1.170816.010-factory-c796ddb4.zip while using fastboot boot. I have a bricked phone that which isn't covered under the replacement warranty.

Have you both updated your adb drivers?
Because I had the same.
After updating adb I could flash the image without any problem.

Question The current image(boot/recovery) have been destroyed and can not boot? - Realme C2

Hi, I have trouble with flashing custom rom to my Realme C2 phone.
Last night i unlocked the bootloader and tried to flash custom rom to my phone, but i really can't get into twrp recovery or fastboot mode. (The screen stuck on fastboot_unlock_verify ok). Then i tried to relock the bootloader and decided to give up and go back to normal. When i entered : fastboot flashing lock : command in terminal (im using mac os), it kept rebooting and says the current boot image(boot/recovery) have been destroyed and can not boot.
Right now i can't boot into recovery mode or fastboot mode, any chance that i can get my phone working again? Is it because that my phone is carrier locked, so they locked my fastboot option? but i got the bootloader unlocked.
Big thanks for every reply and trying to help, I really appreciate it!!

Fastboot and ADB are 2 different drivers: don't mix up. Fastboot deals with device's boot-loader whereas ADB deals with Android OS.

jwoegerbauer said:
Fastboot and ADB are 2 different drivers: don't mix up. Fastboot deals with device's boot-loader whereas ADB deals with Android OS.
Click to expand...
Click to collapse
Sorry, It was in terminal not Adb, but fixed! Anyway that i can get my phone up running again?

To me it seems your installation of TWRP - what amonng other things modifies Android's boot.img and also removes device's Stock Recovery - miserably failed for whatever reason.
You can try to bring back phone's Stock Recovery ( overwrite TWRP ) by means of SP Flash Tool.

jwoegerbauer said:
Fastboot and ADB are 2 different drivers: don't mix up. Fastboot deals with device's boot-loader whereas ADB deals with Android OS.
Click to expand...
Click to collapse
jwoegerbauer said:
To me it seems your installation of TWRP - what amonng other things modifies Android's boot.img and also removes device's Stock Recovery - miserably failed for whatever reason.
You can try to bring back phone's Stock Recovery ( overwrite TWRP ) by means of SP Flash Tool.
Click to expand...
Click to collapse
I tried to follow the guide, but Realme C2 firmware doesn't have scatter file to let me flash the stock firmware

Wondering why you haven't created the Scatter file before starting to hack/mod the phone?

(Closed)<Fixed> Honor 8 emui 8 android oreo brick ( software i guess )

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