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

Can't use twrp and start my honor 8

Hello,
Sorry for this post but i have a real problem !
I have install a twrp and root my phone for flash rom but now i have factory rest and haven't any OS...
I cant' launch twrp and even i install with fastboot. I have just "your device is booting now".
I don't know how to "backup" and repair my honor.
If anyone undernstand my problem...
ps : I'm really sorry for my english

If you need picture or more information please tell me ...

Try to install TWRP 3.0.2 via fastboot. Install a stock image.zip via TWRP

djx24 said:
Try to install TWRP 3.0.2 via fastboot. Install a stock image.zip via TWRP
Click to expand...
Click to collapse
Thanks for your answer
I try to install a recovery on fastboot but when i reboot my phone stay on "your device is booting now..." that's the problem ...

I have try to use "fastboot boot twrp.img" but failed because command not allowed.
Try to erase but not allowed too. I can flash recovery, or flash boot but change nothing...

Rommco05 said:
Try instal full fw (M B120 or B131) via dload method
Click to expand...
Click to collapse
dload method ? But i need my phone turned ON for that no ? or i need twrp ? But i can't use recovery mode. I can use only erecovery and fastboot.
Thanks for your message

Rommco05 said:
...??? no. Turn off phone and turn on with buttons vol+/vol-/on,off press together. Make folder on SDcard dload/ put inside unzip full fw.
Click to expand...
Click to collapse
Thanks you ! Installing update...
I think it work
(Sorry for all i'm a noob ...)

SOLVED....Can´t get to TWRP because of my fault

SOLVED!......
So hello guys, I am 17 year old, amateur in this mobile topic . My mobile is honor 8 with android 7.0
I unlocked my boot loader and then I tried to flash the TWRP thorugh the fastboot. It didn´t work. Everytime when the mobile was starting I finished on the screen that told me :"your device is unlocked...., your device is starting..." just the normal window when you have bootloader unlocked. I couln´t get into anything. I tried multiple twrps and then I found one called like twrp-3.1.1-1-frd.img https://forum.xda-developers.com/honor-8/development/twrp-t3566563 that worked for me and everything was ok.
But yesterday I wanted to unroot the phone. I read here how to do that: https://forum.xda-developers.com/honor-8/help/honor-8-to-stock-locked-t3509004
But everytime I wanted to start through stock recovery.img (that was downloaded in update.app from https://forum.xda-developers.com/honor-8/development/models-stock-firmware-packages-honor-8-t3501942) nothing happen.
Still the window with the message your device is starting. I coun´t get elwhere then bootloader mode. When I flashed the twrp-3.1.1-1-frd again, it worked normal. But I still wanted to get stock.
I didn´t know what to do so I scrolled down the same site and found this:
"Extract the update.app use this attachment
take Boot , Recovery , Data , System .
Go to ur Fast-boot Folder move this Files inside it .
Open Terminal or CMD throw Admin Rights inside the folder
make sure ur device with fast-boot mode before connecting ur cable to ur device
and make sure u have drivers installed
Type in CMD
Fastboot flash Boot boot.img
Fastboot flash Recovery Recovery.img
Etc .. flash all .imgs
Last type fastboot oem lock <YourPersonalUnlockCodeHere> ( THIS ONLY IF U LIKE TO LOCK AGAIN !)
fastboot Reboot . unplug cable and hope Work Fine ."
So I did what is written there I extracted those img files from update.app and flashed them ...... Now even if I put twrp-3.1.1-1-frd.img nothing happen I am stuck there only thing I can do is to boot to bootloader mode or be in the windew that is telling me device is starting....
And what would I want is to unstuck and go stock again.
Thank you in advance for your reply and sorry for the english.
How did I solve. I flashed twrp in recovery2 too, this solved it and mobile booted. THX for help guys.

https://forum.xda-developers.com/honor-8/how-to/discussion-t3591964/post72056001and#post72056001

deadko said:
https://forum.xda-developers.com/honor-8/how-to/discussion-t3591964/post72056001and#post72056001
Click to expand...
Click to collapse
I dont understand what you meant. the twrp-3.1.1-1frd.img doesn´t work for me at the moment it worked but since I did what I wrote it stopped working.
I cant get even in recovery mod.

Rommco05 said:
I always prefer clean start. Is a longest way but for performace and battery is the best!! So u can make downgrade to Marshmalow and your bootloader will locked (relocked) auto. If don't know how (xda search) leave a post here
Click to expand...
Click to collapse
But I don´t know how and where to start the only 2 screens I get is bootloader boot and your device is starting...
and I dont know why all of the TWRPs stoped working for me

Rommco05 said:
If u can boot to os. Please check in fastboot and in developer section >> frp is locked or unlocked? oem is...?
Click to expand...
Click to collapse
I can´t boot at all not even in recovery mode. "Phone onlocked, FRP unlock"

Rommco05 said:
Your last fw was?
edit: unroot phone? I see first time thx
Click to expand...
Click to collapse
When I rooted I installed how I wrote twrp, then flashed super su
I dont have unrooted phone I just wanted to unroot the way that I would install update.app throught stock recovery mode.

Markus37CZ said:
When I rooted I installed how I wrote twrp, then flashed super su
I dont have unrooted phone I just wanted to unroot the way that I would install update.app throught stock recovery mode.
Click to expand...
Click to collapse
U can install even with root . It will bring back all the files to stock .dont worry about current system. It will be updated with the file in update.app and all ur changes to system will be erased

(HELP ME ) Bricked

So i did a stupid thing and flashed the wrong image when i was installing a new rom, I managed to lock myself out of ADB, TWRP and download mode. I'm in a bit of a pickle right now I've been trying everything I can to fix it, but I managed to do nothing. Is there anyone that can walk me through the steeps to get unbricked.
I've tried recovery through hisuite, but it says my device is not supported. My phone showed up via CMD command (fastboot devices) but not (adb devices). I have no idea what to do?
PLEASE HELP ME!!!

Nixonkai417 said:
So i did a stupid thing and flashed the wrong image when i was installing a new rom, I managed to lock myself out of ADB, TWRP and download mode. I'm in a bit of a pickle right now I've been trying everything I can to fix it, but I managed to do nothing. Is there anyone that can walk me through the steeps to get unbricked.
I've tried recovery through hisuite, but it says my device is not supported. My phone showed up via CMD command (fastboot devices) but not (adb devices). I have no idea what to do?
PLEASE HELP ME!!!
Click to expand...
Click to collapse
Give the all required information like Brand, model number in your post first.

Huawei honor 5x kiwi L24, I can't really acces the phone so finding some information is impossible. My main issue is when I boot it's failing to verify the Boot.img , recovery.img and system.img . I don't exactly know what all information I can give you

Nixonkai417 said:
So i did a stupid thing and flashed the wrong image when i was installing a new rom, I managed to lock myself out of ADB, TWRP and download mode. I'm in a bit of a pickle right now I've been trying everything I can to fix it, but I managed to do nothing. Is there anyone that can walk me through the steeps to get unbricked.
I've tried recovery through hisuite, but it says my device is not supported. My phone showed up via CMD command (fastboot devices) but not (adb devices). I have no idea what to do?
PLEASE HELP ME!!!
Click to expand...
Click to collapse
First open the tool
Select the update.app file
Then press Ctrl and select the imgs you want
And then right click and click extract selected
Like in here
https://up.harajgulf.com/imagef-149893652739431-png.html

-Hope- said:
First open the tool
Select the update.app file
Then press Ctrl and select the imgs you want
And then right click and click extract selected
Like in here
https://up.harajgulf.com/imagef-149893652739431-png.html
Click to expand...
Click to collapse
I have already done that, I've tried flashing it via SP flash tool but nothing, it won't show up. I've downloaded correct drivers and done what I could but my phone shows up as Lemobile android adb interface. It sometimes shows as a disk drive as well.
When I run CMD command (fastboot flash oem info) it shows everything but the recovery.img system.img and boot.img need verification how can I verify them without the debugging bridge active on the phone.

Nixonkai417 said:
I have already done that, I've tried flashing it via SP flash tool but nothing, it won't show up. I've downloaded correct drivers and done what I could but my phone shows up as Lemobile android adb interface. It sometimes shows as a disk drive as well.
When I run CMD command (fastboot flash oem info) it shows everything but the recovery.img system.img and boot.img need verification how can I verify them without the debugging bridge active on the phone.
Click to expand...
Click to collapse
What do you mean sir
Imgs are already verified cause they are official
And you don't need USB debug in fastboot mode
Your device is not has mtk processor so it won't work

-Hope- said:
What do you mean sir
Imgs are already verified cause they are official
And you don't need USB debug in fastboot mode
Your device is not has mtk processor so it won't work
Click to expand...
Click to collapse
I rooted my phone and was running xenon HD on my Huawei honor 5x, in the midst of switching ROMs I accidently targeted a TWRP recovery.img with the ROM and Gapps.
So what my phone dose now is when it powers on it an all green screen with a red box and a blue box. After a second it come up with " recovery image verify failed, please update to verified images." I can enter fastboot&rescue mode and a Huawei erecovery, but when i do try to download the recovery via WIFI it says package failure.

Nixonkai417 said:
I rooted my phone and was running xenon HD on my Huawei honor 5x, in the midst of switching ROMs I accidently targeted a TWRP recovery.img with the ROM and Gapps.
So what my phone dose now is when it powers on it an all green screen with a red box and a blue box. After a second it come up with " recovery image verify failed, please update to verified images." I can enter fastboot&rescue mode and a Huawei erecovery, but when i do try to download the recovery via WIFI it says package failure.
Click to expand...
Click to collapse
What happens when you try flashing through fastboot
Assuming that your bootloader is unlocked have you tried reflashing twrp?

-Hope- said:
What happens when you try flashing through fastboot
Assuming that your bootloader is unlocked have you tried reflashing twrp?
Click to expand...
Click to collapse
I had unlocked my bootloader but some research I was doing says, when you accidently flash wrong images it can relock the bootloader. I lost the original bootloader code and i don't exactly have the box anymore, so getting a new code will be difficult.

Nixonkai417 said:
I had unlocked my bootloader but some research I was doing says, when you accidently flash wrong images it can relock the bootloader. I lost the original bootloader code and i don't exactly have the box anymore, so getting a new code will be difficult.
Click to expand...
Click to collapse
As long as the bootloader says 'phone is unlocked' then its ok

-Hope- said:
As long as the bootloader says 'phone is unlocked' then its ok
Click to expand...
Click to collapse
I'm my case the bootloader has relocked, so in green it say phone status: locked.

Nixonkai417 said:
I'm my case the bootloader has relocked, so in green it say phone status: locked.
Click to expand...
Click to collapse
I've reread your previous post and you didn't mentioned what happens in the cmd window when trying to flash the files?

-Hope- said:
I've reread your previous post and you didn't mentioned what happens in the cmd window when trying to flash the files?
Click to expand...
Click to collapse
(REMOTE: command not allowed)

I have already sent an email to Huawei support, just waiting on a response to see if they can give me another unlock code. If I'm unable to unlock the boot loader again with the codes, what's my options for unlocling the boot loader without Huawei's help.

Huawei honor 6x Bricked? Need help please.

Hello all,
First of all I looked for a (sub) forum for the Honor 6x BLN-L21, but I can't seem to find it. If a admin/mod thinks this post should be placed elsewhere, feel free to move it.
Ok, now on to the problem I'm having with my Honor 6X (BLN-L21 All model)...
The phone is running the stock B361 firmware, I've unlocked the bootloader with the code I got from Huawei, installed TWRP and rooted the phone, all was working just fine.
Then, last Month y (sep 24, 2017) there was an OTA update to B373 available, tried to install it but it failed (nothing was installed btw, it never got to then point where the OTA did anything, phone would just reboot).
So after some searching and in a lapse of judgement I decided to (re)lock the bootloader thinking that was what kept the update from installing (command: sudo fastboot oem relock <code>).
And that's where my problem gets in.
Now I have a phone which only can only get into:
1.) Huawei eRecovery: Only options I have in eRecovery are: "Download latest version and recovery", "Reboot" and "Shutdown". No option to reset to factory or anything like that. "Download latest version and recovery" fails everytime, stating: "Failed to get package info from server". Gave my phone a static DHCP lease and even put it in DMZ on the router (just in case NAT/firewall was interfering), but that didn't help at all. Rebooting or shutdown will just put the phone back into eRecovery as soon as it's booted.
2.) Emergency/EDL: This is the mode where you're supposed to put the firmware you want to flash in the "dload" folder on sd-card. Tried that too, but it gets to about 5% and fails (tried B360, B371 and B373 update files, none work). When the phone gets into this mode it's also available to ADB. However, something seems to have changed dramaticly as I no longer seem to have any permissions on the phone. "adb devices" shows my phone but it also says "unauthorised". As soon as I try to do anything that requires root priviledges (like: "adb root" or "adb shell") I get an error stating: "This adb server's $ADB_VENDOR_KEYS is not set". Clearly that means there's an issue regarding the .pub keys on client/host side not being the same. Since I cannot pull anything from, or push anything to, my phone I don't know how I can fix this... And since I'm getting this message on the same machine that I used to flash TWRP on the phone earlier (which worked just fine), it seems to me this problem exists on the phone-side.
3.) Fastboot & rescue: fastboot finds my phone just fine, yet it flatout refuses all meaningful commands (only basic commands like reboot work) with the error: "FAILED (remote: Command not allowed)". Some searching tells me this is because the bootloader is locked and that's exactly what my phone shows on it's screen when it's in fastboot mode: "PHONE Relocked" and "FRP Lock". However fastboot command: "fastboot oem get-bootinfo" returns: "(bootloader) unlocked". This confuses me, a lot; if the bootloader is unlocked then what is preventing me from flashing anything? Trying to unlock the bootloader again through fastboot (fastboot oem unlock <code> / fastboot oem unlock "<code>") gives the "FAILED (remote: Command not allowed)" error. Trying to lock the bootloader again (fastboot oem relock <code> / fastboot oem relock "<code>") gives error: "FAILED (remote: stat not match)". Obviously I cannot flash anything from fastboot anymore.
Trying to recovery in HiSuite (newest version) doesn't work either, it just tells my my phone isn't supported, even though it does detect my phone when it's in fastboot mode.
Nothing has been flashed, so this is not a case of a flash gone wrong, it just looks like I'm locked out of my own phone and for the life of me I cannot figure out how to get back in. And there's no way to boot into system anymore, so I cannot check/change "OEM Unlock" and "ADB Debugging" settings in the phone developers options
.
Any help/advice would be greatly appreciated! I'm stuck, Huawei customer service only tells me to do a factory reset, which I can't, and when I tell them that's not possible all becomes awfully quiet on their end (they don't respond to my mails anymore). I simply can't think of anything I could try to fix this, spend the last 5 days searching the web but nothing seems to work. Maybe some Android-guru's have some suggestions (I'm certainly open to suggestions! ).
Thanks in advance.
Edit: Tried some fastboot commands with regards to "FRP Unlock", command: "sudo fastboot oem frp-unlock" returns: "FAILED (remote: oem_frp_check_password failed! Error = -1)" not sure what password is required here to be honest and "sudo fastboot oem frp-erase" returns: "FAILED (remote: Command not allowed!)".

This adb server's $ADB_VENDOR_KEYS is not set"- is when your USB debugging is either not enabled or havent accepted the RSA keys. (faced this on ELIte v^)
FRP unlock comamnd wont work as your USB debugging is disabled and hence OEM unlock option is disabled as well.
Manually flashing any .img wont work as FRP is locked.
Only way to restore is dload or service center.

I have the same phone with exactly the same problem ......
any solution ????

aamszia said:
I have the same phone with exactly the same problem ......
any solution ????
Click to expand...
Click to collapse
Are you on stock rom or custom?
What are you trying and what is the result?
Build number?
What all you tried?

shashank1320 said:
Are you on stock rom or custom?
What are you trying and what is the result?
Build number?
What all you tried?
Click to expand...
Click to collapse
Well phone is repaired ( by Sigma KEY Fastboot flashing ) ( Update.app )
B361
First flashed " update_data_full_BLN-L21_hw_meafnaf.zip " by Fastboot
than update.zip ( 1.55 GB ) Dload by SDCARD ....
now its repaired ..

aamszia said:
Well phone is repaired ( by Sigma KEY Fastboot flashing ) ( Update.app )
B361
First flashed " update_data_full_BLN-L21_hw_meafnaf.zip " by Fastboot
than update.zip ( 1.55 GB ) Dload by SDCARD ....
now its repaired ..
Click to expand...
Click to collapse
i want to try this what command you use with the fastboot ? i have a bricked honor 6x andi think its the only thing i have not tried yet please help

i have not use any commands ..
i have used sigma key software .. ( PAID BOX ) ..

well we booted the phone up. we dloaded the firmware BLN-L21C432B360 for the european model. it booted up fine, but now shows nrdm90 teskeys and generic a15. he dloaded the data folder but still its on nrdm 90 test keys. any solution. or try b361 now? @shashank1320

Nithin.15 said:
well we booted the phone up. we dloaded the firmware BLN-L21C432B360 for the european model. it booted up fine, but now shows nrdm90 teskeys and generic a15. he dloaded the data folder but still its on nrdm 90 test keys. any solution. or try b361 now? @shashank1320
Click to expand...
Click to collapse
Ok. Now flash the oeminfo file for BLN-L21 and it will reset the phone with correct formware and device details.

shashank1320 said:
Ok. Now flash the oeminfo file for BLN-L21 and it will reset the phone with correct formware and device details.
Click to expand...
Click to collapse
well oeminfo or the data zip via dload ?

Nithin.15 said:
well oeminfo or the data zip via dload ?
Click to expand...
Click to collapse
Oeminfo via multi tool ir twrp.data file is for regaining the updater app, theme, clock etc but oeminfo will fix your issue of generic device or nrd-test keys.

shashank1320 said:
Oeminfo via multi tool ir twrp.data file is for regaining the updater app, theme, clock multi tool got it.
Click to expand...
Click to collapse