Related
Hi i have rooted and flashed the phone it got stuck on the htc screen so i tried factory reset bad idea now my phone will just go into the bootlader menu i can enable fastboot usb but it dont show up on computer but the computer makes a noise to say ive connected it i cant enable usb debugging because the phone wont come on i have tried to flash another boot img through fastboot with no luck im hoping its not bricked
please any help would be appreciated thanks
pl4yb0y78 said:
Hi i have rooted and flashed the phone it got stuck on the htc screen so i tried factory reset bad idea now my phone will just go into the bootlader menu i can enable fastboot usb but it dont show up on computer but the computer makes a noise to say ive connected it i cant enable usb debugging because the phone wont come on i have tried to flash another boot img through fastboot with no luck im hoping its not bricked
please any help would be appreciated thanks
Click to expand...
Click to collapse
Hmm. so you probably need to flash a recovery first.
then you will be able to use the recovery to mount usb and put a new rom on your "sd card"
Then you can flash the rom on your new recovery and don't forget to fastboot flash the boot.img.
edit: the all in one toolkit is great for things like this. It will put a new recovery on your phone with just a click of the button.
http://forum.xda-developers.com/showthread.php?t=1604677
tivofool said:
Hmm. so you probably need to flash a recovery first.
then you will be able to use the recovery to mount usb and put a new rom on your "sd card"
Then you can flash the rom on your new recovery and don't forget to fastboot flash the boot.img.
Click to expand...
Click to collapse
Thanks for the reply but i dont know how to do this ?
could you please explain it ?
pl4yb0y78 said:
Thanks for the reply but i dont know how to do this ?
could you please explain it ?
Click to expand...
Click to collapse
I just edited my original post. just in case you didn't know how. I guess I was a little slow.
Also I can't remember if a bootloader factory reset relocked your phone but you might want to check that too. up on top it would say locked or relocked. If it still says unlocked you don't have to do that step again. Like you did when you first rooted the phone.
(all in one tool kit is great for unlocking and relocking too) just put a copy of that bin file in all in one tool kit (data file i believe, but it says what to do in that thread)
tivofool said:
I just edited my original post. just in case you didn't know how. I guess I was a little slow.
Also I can't remember if a bootloader factory reset relocked your phone but you might want to check that too. up on top it would say locked or relocked. If it still says unlocked you don't have to do that step again. Like you did when you first rooted the phone.
(all in one tool kit is great for unlocking and relocking too) just put a copy of that bin file in all in one tool kit (data file i believe, but it says what to do in that thread)
Click to expand...
Click to collapse
hi i have got the tool kit run twrp s3 now i have a black htc logo screen on what next
pl4yb0y78 said:
hi i have got the tool kit run twrp s3 now i have a black htc logo screen on what next
Click to expand...
Click to collapse
Your phone is an s3?
My phone is an S4 as are I would guess the majority of users. I think the s3 is the international version. If you are on T mobile then it's a s4.
Ok,,,
so .... if your phone is an s3 version then you will have to check that the Rom you download is specific for your phone as most of the Roms on this site are for the s4 version.
you need to go to your recovery. press the volume down button and hold it. Then press the power button (don't hold it). That will get you to recovery.
when in twrp recovery you will see a mounts button. hit that then the next screen will have mount usb. then you will be able to move a rom you downloaded on your computer to your phone.
then you can install the rom zip in twrp.
then from your computer, I assume you know how to flash a boot.img
put a boot.img in your fastboot folder, open up a comand prompt.
fastboot flash boot boot.img
if you wanted a different recovery than you are using, find the download the recovery. *I would rename the recovery to recovery.img
fastboot flash recovery recovery.img
(I only mention a different recovery because in some of the Rom threads you might read that you can only install a particular rom with an older version of twrp.)
I'm not sure of your skill or experience with all of this. If you are very new to it (then you are probably really frustrated) have no fear there is a little bit to learn but not that much. Just keep reading the development thread and the guides in it.
tivofool said:
Your phone is an s3?
My phone is an S4 as are I would guess the majority of users. I think the s3 is the international version. If you are on T mobile then it's a s4.
Ok,,,
so .... if your phone is an s3 version then you will have to check that the Rom you download is specific for your phone as most of the Roms on this site are for the s4 version.
you need to go to your recovery. press the volume down button and hold it. Then press the power button (don't hold it). That will get you to recovery.
when in twrp recovery you will see a mounts button. hit that then the next screen will have mount usb. then you will be able to move a rom you downloaded on your computer to your phone.
then you can install the rom zip in twrp.
then from your computer, I assume you know how to flash a boot.img
put a boot.img in your fastboot folder, open up a comand prompt.
fastboot flash boot boot.img
if you wanted a different recovery than you are using, find the download the recovery. *I would rename the recovery to recovery.img
fastboot flash recovery recovery.img
(I only mention a different recovery because in some of the Rom threads you might read that you can only install a particular rom with an older version of twrp.)
I'm not sure of your skill or experience with all of this. If you are very new to it (then you are probably really frustrated) have no fear there is a little bit to learn but not that much. Just keep reading the development thread and the guides in it.
Click to expand...
Click to collapse
Thank you for the reply yes i am getting stressed at this and i am new had a break before i smashed the phone now ive just got to find out what my phone is s3 or s4 ? google will help
when i connect my phone to the computer in recovery or flashboot it does not let me see it so i can not put rom on the hdd
(tried restart phone no luck tried restart comy no luck, cant get it to show phone ) all drivers installed
can i use the tool kit to flash recovery ?
phone on orange uk ,is it a s4 ?
thanks for the help guys with your knowledge i will get it working i pray!
pl4yb0y78 said:
when i connect my phone to the computer in recovery or flashboot it does not let me see it so i can not put rom on the hdd
(tried restart phone no luck tried restart comy no luck, cant get it to show phone ) all drivers installed
can i use the tool kit to flash recovery ?
phone on orange uk ,is it a s4 ?
thanks for the help guys with your knowledge i will get it working i pray!
Click to expand...
Click to collapse
do you have your box the phone came in?
Z520e is S4
Z560e is S3
So were you able to put twrp on your phone? when you are in boot loader and click on the recovery does it take you to twrp? Yes the all in one toolkit will flash a recovery for you. but you have your boot loader unlocked first.
tivofool said:
do you have your box the phone came in?
Z520e is S4
Z560e is S3
So were you able to put twrp on your phone? when you are in boot loader and click on the recovery does it take you to twrp? Yes the all in one toolkit will flash a recovery for you. but you have your boot loader unlocked first.
Click to expand...
Click to collapse
yes i now have the twrp in recovery it says enter password and cancel i tried both it was the s4 one that worked so im guessing its an s4
what will the next step be? (if i need anything please could you leave a link)
thanks for all the help starting to feel i might win lol
in twrp when you press "mounts" then press "mount usb", does your computer finally see your phone?
I was looking at your first post, you say that you rooted and flashed your phone. What do you mean by that? Did you download a ROM and attempt to flash it? Or did you "fastboot flash boot boot.img"?
If you are able to access your phone via computer it is as simple as downloading a rom on your computer moving it to your phone then in twrp "install from zip". Then fastboot flash the boot.img.
http://forum.xda-developers.com/showthread.php?t=1583427
how to flash fastboot
http://forum.xda-developers.com/showthread.php?t=1752270
if you are just fed up and want your phone back to stock then you will need to run an RUU.
http://forum.xda-developers.com/showthread.php?t=2094414
To run a RUU you would need to relock your bootloader.
in console type "fastboot lock oem" or use your all in one toolkit to relock it.
if that fails you will need to put your stock recovery back. (you need to have boot loader unlocked to do this)
on the clockworkmod recovery page the stock recovery is the second download link.
http://www.modaco.com/topic/353006-...ch-recovery-for-the-htc-one-s-stock-download/
Ok i am now really confused nothing works downloaded recovery roms they wont install always says failed tried to adb sideload it after google it failed again tried 3 recovery roms all fail what is going wrong icant get it to work
so far ive put twrp on it pressed mount so i can put rom on phone worked
pressed install pressed zip failed
pressed adb sideload then start on comy sent rom 100% install failed
reeboot phone still no os
tried this 3 times different roms all failed
please help
pl4yb0y78 said:
Ok i am now really confused nothing works downloaded recovery roms they wont install always says failed tried to adb sideload it after google it failed again tried 3 recovery roms all fail what is going wrong icant get it to work
so far ive put twrp on it pressed mount so i can put rom on phone worked
pressed install pressed zip failed
pressed adb sideload then start on comy sent rom 100% install failed
reeboot phone still no os
tried this 3 times different roms all failed
please help
Click to expand...
Click to collapse
Do you know how to FASTBOOT FLASH boot.img which is present inside the ROM.ZIP?
Try wiping data, cache, dalvik. Then reinstall.
Sent from my Nexus 7 using Tapatalk HD
khan.orak said:
Do you know how to FASTBOOT FLASH boot.img which is present inside the ROM.ZIP?
Try wiping data, cache, dalvik. Then reinstall.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
thanks and yes i can do that i will try and get back to you
C:\adt-bundle-windows-x86_64-20130522\sdk\platform-tools>fastboot boot boot.img
creating boot image...
creating boot image - 16779264 bytes
downloading 'boot.img'...
OKAY [ 1.890s]
booting...
FAILED (remote: reproduce boot image with on-flash ramdisk error)
finished. total time: 1.926s
this is what i get when i try tried 3 imgs
pl4yb0y78 said:
C:\adt-bundle-windows-x86_64-20130522\sdk\platform-tools>fastboot boot boot.img
creating boot image...
creating boot image - 16779264 bytes
downloading 'boot.img'...
OKAY [ 1.890s]
booting...
FAILED (remote: reproduce boot image with on-flash ramdisk error)
finished. total time: 1.926s
this is what i get when i try tried 3 imgs
Click to expand...
Click to collapse
The command is:
Code:
fastboot flash boot boot.img
khan.orak said:
The command is:
Code:
fastboot flash boot boot.img
Click to expand...
Click to collapse
ok i try this i am only learning but getting there lol
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!
Hi!
Okay, this case is really weird and of course is thanks to my negligence. I'm gonna post it hoping someone can help me, or at least keep other people aware about trying stupid things lol
I tried to update to Nougat with an unofficial method (I don't consider necessary to tell what method...) and I just messed it up, badly. I'll try to give a detailed explanation:
The phone has the bootloader unlocked. After trying to update to Nougat, it got stuck when rebooting. After the unlocked bootloader warning message, the phone won't go further than that, it just stays there. If I hold and press the power button for more than 10 seconds the phone won't shut down, it will restart to get stuck again after the unlocked BL warning, making impossible to turn it off completely.
I try to enter to stock recovery by pressing vol + and power button at the same time (tried other combinations, vol - and power button & vol -, vol + and power button) but I have no luck, it just gets stuck at the same point.
I already tried extracting BOOT.img, RECOVERY.img, CUST.img and SYSTEM.img from an official update.app and flash them in that order via fastboot (yeah, I can enter to fastboot mode). The process is successful in terminal (I use Linux) but when I reboot the phone, it gets stuck again after the warning.
The only recovery that is actually working is TWRP, the one ported for the Honor 8 (flashed via fastboot), but it won't let me install any custom ROM, it just stays in "patching image unconditionally" forever, making me press and hold the power button but this won't shutdown the phone, it reboots, gets stuck and... so on *infinite loop*
Btw, when I wipe cache, dalvik and data in TWMP, the message "failed to mount /cust" with red letters appears, so it's probably a very corrupted system partition. also, It's impossible to repair the custom partition. This appears:
Repairing Custom using e2fdck...
/sbin/e2fsck -fp /devblock/mmcblk0p44 process ended with ERROR: 8
Unable to repair Custom.
Click to expand...
Click to collapse
Tried HiSuite from Huawei (in Windows) and it doesn't even recognize the phone.
Hope somebody could possibly give a solution, if there's any. If not, I'm afraid I have a beautiful paperweight now...
Oh yeah, one very important part: my Honor 8 is the US version (FRD-L04), and yes, I'm making sure I'm getting the current update.app for this model.
Any help would be greatly appreciated. Thanks in advance.
Hi There
you try this method.
Get a SD CARD
make a directory at the card root name dload
put your best update.app in the directory (the most older version the best)
insert into your phone 2nd sim slot
try everyway to make the 3 button combo.
hope this help
edit: you need stock recovery to do this
chongns said:
Hi There
you try this method.
Get a SD CARD
make a directory at the card root name dload
put your best update.app in the directory (the most older version the best)
insert into your phone 2nd sim slot
try everyway to make the 3 button combo.
hope this help
edit: you need stock recovery to do this
Click to expand...
Click to collapse
Hey, thanks!
unfortunately, as far as I know is that for this method I have to enter to stock recovery, but then again, I can't get in. The phone gets stuck trying any combination of pressed buttons... But I'll try it.
Edit: Trying your method right now, hope it goes well...
El Brillantinas said:
Hey, thanks!
unfortunately, as far as I know is that for this method I have to enter to stock recovery, but then again, I can't get in. The phone gets stuck trying any combination of pressed buttons...
Click to expand...
Click to collapse
Yes, but since you r able to go into TWRP, can your use adb command like adb reboot bootloader than flash stock recovery image?
after that since it is keep rebooting, you can hold your volume up and down all the way to force update.
IDK if this work. but no harm to try it, since it is "very hard brick"
Edit: Fastboot erase {partition} before flash back the image maybe help
chongns said:
Yes, but since you r able to go into TWRP, can your use adb command like adb reboot bootloader than flash stock recovery image?
after that since it is keep rebooting, you can hold your volume up and down all the way to force update.
IDK if this work. but no harm to try it, since it is "very hard brick"
Click to expand...
Click to collapse
Yep, I'm trying it now and right now is installing the update (the EMUI logo with the circular progress bar). Hope it works *crossed fingers*
Edit: No luck. After the process finished, it says:
Software install failed!
Get help from: http//www.emui.com/emotionetcetc.
Click to expand...
Click to collapse
El Brillantinas said:
Yep, I'm trying it now and right now is installing the update (the EMUI logo with the circular progress bar). Hope it works *crossed fingers*
Edit: No luck. After the process finished, it says:
Click to expand...
Click to collapse
I assume you having the update.app from a L04 full firmware, not the OTA.
for the not able to repair partition like custom maybe you can erase it using fastboot erase command and fastboot flash it back
or you can fastboot erase all the known partition like system, cache, data, custom etc.... and fastboot flash back the image.
i assume your fastboot still able to access
chongns said:
I assume you having the update.app from a L04 full firmware, not the OTA.
for the not able to repair partition like custom maybe you can erase it using fastboot erase command and fastboot flash it back
or you can fastboot erase all the known partition like system, cache, data, custom etc.... and fastboot flash back the image.
i assume your fastboot still able to access
Click to expand...
Click to collapse
I did it!!
I could bring it back following some of your methods. Here's how I achieved it:
-Formatted the Custom partition in fastboot.
-Flashed BOOT.img, RECOVERY.img, CUST.img and SYSTEM.img again.
-Forced the update by putting the entire firmware in the dload folder located in the sdcard, it failed at the end, but I rebooted by pressing and holding the power button.
-The phone passed beyond the point where it was getting stuck (finally!), but now it got stuck in the Honor 8 blue screen. Rebooted it again doing coldboot.
-Entered to stock recovery, wiped everything.
Then I just rebooted it and Voalá! It started all new!
Guess it was not that hard brick haha. I'll have to change the name of the topic.
A million thanks @chongns, you rock!
El Brillantinas said:
I did it!!
I could bring it back following some of your methods. Here's how I achieved it:
-Formatted the Custom partition in fastboot.
-Flashed BOOT.img, RECOVERY.img, CUST.img and SYSTEM.img again.
-Forced the update by putting the entire firmware in the dload folder located in the sdcard, it failed at the end, but I rebooted by pressing and holding the power button.
-The phone passed beyond the point where it was getting stuck (finally!), but now it got stuck in the Honor 8 blue screen. Rebooted it again doing coldboot.
-Entered to stock recovery, wiped everything.
Then I just rebooted it and Voalá! It started all new!
Guess it was not that hard brick haha. I'll have to change the name of the topic.
A million thanks @chongns, you rock!
Click to expand...
Click to collapse
Good to know you succeed.
please tag a moderator to move your thread to Guide, News and Discussion section..
most of the time ppl search solution at there.
Guide in another Huawei phone XDA forum.
http://forum.xda-developers.com/mate-8/general/fuss-debrick-restore-mate-8-t3457969
Moderatos, can you please move this topic to the Guides and discussion section? Thanks in advance.
Glad you fixed it bro. That was very critical.
El Brillantinas said:
Moderatos, can you please move this topic to the Guides and discussion section? Thanks in advance.
Click to expand...
Click to collapse
good to hear u go phone back , and there is another guides already exist to restore a framware throw the same method , thank you for sharing ur experience .
Here's the issure I'm having. My Honor 8 FRD-L04 is stuck at a hard brick. It won't reach the recovery. I tried to flash images using fastboot. But I end up with the error: FAILED (remote: Command not allowed)
Any help would be appreciated
bho01 said:
Here's the issure I'm having. My Honor 8 FRD-L04 is stuck at a hard brick. It won't reach the recovery. I tried to flash images using fastboot. But I end up with the error: FAILED (remote: Command not allowed)
Any help would be appreciated
Click to expand...
Click to collapse
Is your frp status lock in fastboot?
faizalotai said:
Is your frp status lock in fastboot?
Click to expand...
Click to collapse
No it's unlocked
bho01 said:
No it's unlocked
Click to expand...
Click to collapse
Your phone status?
faizalotai said:
Your phone status?
Click to expand...
Click to collapse
Still can't get into recovery and I'm still getting the "FAILED(Command not allowed)" error whenever I try to flash stock images
bho01 said:
Still can't get into recovery and I'm still getting the "FAILED(Command not allowed)" error whenever I try to flash stock images
Click to expand...
Click to collapse
I mean your phone status in fastboot.
Its comes with frp and phone status..both have to be unlocked in order to flash images.
Try using the dload method of flashing
faizalotai said:
I mean your phone status in fastboot.
Its comes with frp and phone status..both have to be unlocked in order to flash images.
Click to expand...
Click to collapse
Also unlocked
Hello Guys,
Please help me in the following case.
I have a Mate 7 TL-10. Originally, it was from China, it's system was Chinese.
Today, I rooted, I changed the location from CN to EU (I am from Hungary). Everything was okay, I wanted to flash a new (European) ROM, but before it, I wanted to wipe. Oh, no! Here, I was stupid. I wiped everything by that recovery, what the SRK Tool installs.
I lost everything, it wrote me, that no OS. I cannot enter to the recovery, it stucked at the Huawei logo. I even cannot switch the phone off, it only restarts!
Can you please help me to solve this problem and survive my phone?
Thank you for all in advance.
montisHU said:
Hello Guys,
Please help me in the following case.
I have a Mate 7 TL-10. Originally, it was from China, it's system was Chinese.
Today, I rooted, I changed the location from CN to EU (I am from Hungary). Everything was okay, I wanted to flash a new (European) ROM, but before it, I wanted to wipe. Oh, no! Here, I was stupid. I wiped everything by that recovery, what the SRK Tool installs.
I lost everything, it wrote me, that no OS. I cannot enter to the recovery, it stucked at the Huawei logo. I even cannot switch the phone off, it only restarts!
Can you please help me to solve this problem and survive my phone?
Thank you for all in advance.
Click to expand...
Click to collapse
Don't worry tell me what firmware you have is your bootloader unlocked or not it'll be fine don't worry...
fazi2015 said:
Don't worry tell me what firmware you have is your bootloader unlocked or not it'll be fine don't worry...
Click to expand...
Click to collapse
Hello!
Than kyou very much for your help. Yesterday night, I could survive the phone, this is what I did:
VOL- and POWER: fastboot mode
In fastboot mode, I connected to the PC and (beofr it, I downloaded an update.zip and extracted:
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash boot boot.img
Now, it is working (seems to be) But what should I do with the other .img files from the update.zip?
Do I have to do any other steps? I think yes, 'cause if I check the Vendor info in th*#*#2846579#*#* menu, there is no country code in my phone
Can you help me, what should I do?
Thank you for your help again.
montisHU said:
Hello!
Than kyou very much for your help. Yesterday night, I could survive the phone, this is what I did:
VOL- and POWER: fastboot mode
In fastboot mode, I connected to the PC and (beofr it, I downloaded an update.zip and extracted:
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash boot boot.img
Now, it is working (seems to be) But what should I do with the other .img files from the update.zip?
Do I have to do any other steps? I think yes, 'cause if I check the Vendor info in th*#*#2846579#*#* menu, there is no country code in my phone
Can you help me, what should I do?
Thank you for your help again.
Click to expand...
Click to collapse
You can download the mobopx app by chudy on the first post of this page:
https://forum.xda-developers.com/mate-7/general/huawei-mt7-l09-l10-stock-firmware-ota-t3275784
This app lets you change the country/vendor information on your phone, amongst other things
montisHU said:
Hello!
Than kyou very much for your help. Yesterday night, I could survive the phone, this is what I did:
VOL- and POWER: fastboot mode
In fastboot mode, I connected to the PC and (beofr it, I downloaded an update.zip and extracted:
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash boot boot.img
Now, it is working (seems to be) But what should I do with the other .img files from the update.zip?
Do I have to do any other steps? I think yes, 'cause if I check the Vendor info in th*#*#2846579#*#* menu, there is no country code in my phone
Can you help me, what should I do?
Thank you for your help again.
Click to expand...
Click to collapse
First off all you should flash your regional firmware(original) then if you want to change region changing region is not big deal download the official one and flash by putting update.app into dload folder in sd card and flash by force update and if you are able to flash recovery then flash twrp recovery and flash custom rom like @chudy rom & @Ale rom if you stay in official states then flash chudy rom much likely to stock and if you like custom rom then flash Ale rom which I use and many other.
Flash twrp recovery and make a full backup then wipe all without sd card and then flash the rom zip file after that wipe both cache and reboot first time it'll take some time but don't worry keep it booting you all done..
Further help needed please ask.:good:
montisHU said:
Hello!
Than kyou very much for your help. Yesterday night, I could survive the phone, this is what I did:
VOL- and POWER: fastboot mode
In fastboot mode, I connected to the PC and (beofr it, I downloaded an update.zip and extracted:
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash boot boot.img
Now, it is working (seems to be) But what should I do with the other .img files from the update.zip?
Do I have to do any other steps? I think yes, 'cause if I check the Vendor info in th*#*#2846579#*#* menu, there is no country code in my phone
Can you help me, what should I do?
Thank you for your help again.
Click to expand...
Click to collapse
same probleme here can you help me?
So I had an unlocked H8 with LOS. As I wanted to install EMUI, I put the proper restore Update.app into the dload folder and started Huawei's recovery. Everything went well, I formated data and wanted to install the EMUI 4.1 ROM using the same method.
Unfortunately my H8 is bootlooping and there is now way into erecovery nor any other recovery. It simply reboots on every single known vol up or down key pressing combination. The only thing I can go to is fastboot mode when holding down vol down and plugging in usb wire. But, it says frd locked and I can't install nor boot twrp. It's simply gone and reboots all the time.
Any hints? I can't even turn it off.
I wanted to give away that phone that's the reason. Last time I did it this way, I could flash the EMUI 4.1 since it's signed. But not this time.
Interesting part is, that although fastboot says frd locked, I still get the "phone unlocked" warning on every reboot. dload method isn't working, as it simply keeps rebooting.
It's my hardest brick so far I ever encountered
the same thing happened to me.....on my phone lock/unlocked frp and bootloader were tweaked for some reason(I mean that what was written wasn't the reality) so how did I fix it? I kept on to flash rollback package many times and I tried to unlock/relock bootloader again, at the end the phone let me to flash the firmware, I didn't know how but the phone allowed me to flash things throw recovery(using dload method). At the begin I only could access to erecovery and fastboot. I suppose that I broke system and data partition and while I looked/unlocked the bootloader, the wipe fixed the partition table. Sorry I'm tired and I know that my English sucks, I hope you understand what I have written.
How did you enter erecovery as this isn't working for me.... What did you flash over fastboot?
Have you tried flashing the firmware separately using adb on computer?
For this you just need to extract the Update.app using the firmware extractor for huawei. Then flash them individually using adb commands in cmd.
I can't access any state that would allow to do adb.
faeArai said:
How did you enter erecovery as this isn't working for me.... What did you flash over fastboot?
Click to expand...
Click to collapse
sorry. I'll try to explain better, however on Huawei/honor devices there are not one but two recoveries, so one is the normal recovery flashed in recovery partition, the second one is the Huawei recovery that is flashed in recovery2 partition, so if you didn't touch recovery2 partition, your erecovery is still there, now, if you press VOL+ VOL- and POWER it will reboot to recovery2 and it starts to flash something from dload in your sd card, so in my opinion you should do this things, first try this method to flash rollback package(this is the transition package from 7 to 6 and you will find it on honor site) if this is still not working try locking and unlocking again your bootloader(I hope this fix partitions of your device) then try to enter recovery and do a wipe and then boot your device, if this doesn't work flash rollback package(now it would work) and then flash an emui 4 full firmware image, always using dload method. trust me... I did the same... and it worked for me. let me know if it works for you :good:
faeArai said:
So I had an unlocked H8 with LOS. As I wanted to install EMUI, I put the proper restore Update.app into the dload folder and started Huawei's recovery. Everything went well, I formated data and wanted to install the EMUI 4.1 ROM using the same method.
Unfortunately my H8 is bootlooping and there is now way into erecovery nor any other recovery. It simply reboots on every single known vol up or down key pressing combination. The only thing I can go to is fastboot mode when holding down vol down and plugging in usb wire. But, it says frd locked and I can't install nor boot twrp. It's simply gone and reboots all the time.
Any hints? I can't even turn it off.
Click to expand...
Click to collapse
I ran into this issue not that long ago. What you have to do is relock your bootloader using ADB. The ADB commands and instructions can be found in this thread.
Just a FYI, do not use the links to the software listed in that thread as it is a little outdated. The method still works but the software will probably not work. Just be sure to get the most recent/appropriate version of SuperSU and TWRP via their official threads (This is if you want to re-root). There are Honor 8 specific TWRP files if I remember correctly, so be sure to check around the Honor 8 forums for the correct files.
A quick summary of what I did:
1) Power your phone off and then boot into fastboot by holding Vol down + Power; as soon as it boots up, plug your phone into your combuter via your usb cord.
2) With ADB running, type:
Code:
fastboot oem relock [COLOR="LightBlue"]################[/COLOR]
NOTE: The '#' should be replaced with your unique unlock code that you obtained to unlock your bootloader.
3) Wait for it to format and reset your phone and go through the setup. BE SURE TO BYPASS all google registration; skip everything you can to get into the phone itself. If you do register, it will reactivate FRP and you'll have to start over again.
4) Turn on USB Debugging and every other setting that enables developer administrative navigation and control just to be safe. USB Debugging being the most important one, though.
5) Restart your phone and boot into fastboot again using Vol down + Power.
6) Unlock your phone again with:
Code:
fastboot oem unlock [COLOR="LightBlue"]################[/COLOR]
7) Once the command is entered, it'll reset your phone once more and - as stated before - bypass/skip all google (FRP) registration.
8) Enable developer options and USB debugging again and make sure that OEM Unlocked is checked and grayed out.
9) Reboot into fastboot mode to confirm that FRP is disabled and you should be able to install TWRP now via ADB.
@Numerics thanks. The thing is, that I can't boot anything. I can't even go into eRecovery. Nor can I flash a stock EMUI 4.1. It just boot loops all the time and I can only access fastboot.
If you can flash twrp..........Install los or other Rom ..................Go back to stock.......you must flash b360 ober adb...... because los is 7.1...............if you on b360 you can usw the rollback for emui 4.1........,..............sry for bad english
I can easily go to fastboot. But I can't flash anything. I extracted the img from the update.app but can't flash. It simply says that it's not permitted.
faeArai said:
I can easily go to fastboot. But I can't flash anything. I extracted the img from the update.app but can't flash. It simply says that it's not permitted.
Click to expand...
Click to collapse
With my method, you don't need to flash anything. Just relock your bootloader via adb in fastboot mode and let it reset. Unless I'm not understanding your issue entirely.
@Numerics as I said, in won't boot anything as it is constantly boot looping. There is no way to access any kind of recovery nor erecovery. There is no boot into Android. The only thing accessible right now is fast boot (which is not ADB). But even in fast boot I can't do anything als operations are not permitted.
after boot looping and starting fast boot mode, I can see a "Android reboot reason" section saying:
AP_S_PANIC
data is invalid
There is still a lineageos installed on system as firmware but as I tried to get rid of it by going back to stock EMUI, I guess Huawei's rollback did something wrong and killed recovery (although I did it in the past successfully).
I tried to run HiSuite to recover my phone, but it just says, that my phone is not supported.
Speaking of this, Huawei messed up with that whole fastboot locking bull****.
faeArai said:
@Numerics as I said, in won't boot anything as it is constantly boot looping. There is no way to access any kind of recovery nor erecovery. There is no boot into Android. The only thing accessible right now is fast boot (which is not ADB). But even in fast boot I can't do anything als operations are not permitted.
after boot looping and starting fast boot mode, I can see a "Android reboot reason" section saying:
AP_S_PANIC
data is invalid
There is still a lineageos installed on system as firmware but as I tried to get rid of it by going back to stock EMUI, I guess Huawei's rollback did something wrong and killed recovery (although I did it in the past successfully).
I tried to run HiSuite to recover my phone, but it just says, that my phone is not supported.
Speaking of this, Huawei messed up with that whole fastboot locking bull****.
Click to expand...
Click to collapse
No, I know ADB isn't Fastboot. What I'm trying to say is that you should be able to still run ADB via CMD on Windows when you're in fastboot mode to relock your bootloader with the directions I gave in my previous post. It'll force-restore your phone to a non-bricked/vanilla state. At least that is how I fixed mine.
Like... You can't even try using the 'fastboot oem relock ################' function via the ADB console while in fastboot?
yes boy trust us, you haven't a working OS so it is a normal thing that your phone reboot, you cannot access to recovery because some partitions are corrupted (data partition) , so these are the steps that could help you:
1) using fastboot, relock your boot loader
2)using fastboot, unlock your boot loader (partition table would be ok now, and you would be able to use load method to flash things trow stock recovery)
4)put inside your sd card \dload\update.app(use rollback package)
3) press all the buttons while your device is rebooting(do this before the blue screen logo appear), your phone is now looking for something inside your sd card
5) if the next step doesn't work do a factory reset from recovery that now would be working
6) put inside your sd card a full android 6 (emus 4) update.app and pressing all buttons it will install the firmware
7) your device now is locked and back to stock, maybe without cust partition or maybe in test mode but it is certainly alive
8) do a factory reset and reinstall the firmware
9) your phone is now ok
You don't lock the bootloader via ADB but via fastboot.
As I said, northing was restored and nothing is booting and I can't unlock my bootloader again. As I said, recovery is not working so the file in dload is not loaded and used. Which is strange.
Locking bootloader didn't do anything besides locking the bootloader. Device is still dead and I still can only access fastboot.
faeArai said:
You don't lock the bootloader via ADB but via fastboot.
As I said, northing was restored and nothing is booting and I can't unlock my bootloader again. As I said, recovery is not working so the file in dload is not loaded and used. Which is strange.
Locking bootloader didn't do anything besides locking the bootloader. Device is still dead and I still can only access fastboot.
Click to expand...
Click to collapse
Which model do u own?
Sent from my Honor 8 using XDA Labs
The European one.
faeArai said:
You don't lock the bootloader via ADB but via fastboot.
As I said, northing was restored and nothing is booting and I can't unlock my bootloader again. As I said, recovery is not working so the file in dload is not loaded and used. Which is strange.
Locking bootloader didn't do anything besides locking the bootloader. Device is still dead and I still can only access fastboot.
Click to expand...
Click to collapse
This is not the truth.....locking bootloader will erase all your data and fix partitions....and with fixed partition you can access to recovery ......trust me the only thing that you can do is to lock your bootloader......you can't flash anything from fastboot and boot recovery or system now...... lock your bootloader and then unlock it again, try using "fastboot OEM lock *****" or "fastboot OEM relock *******" (try cmd runned as admin, people say that this makes the difference) then unlock your device again and .....magic your recovery will boot......the same thing happened to me and I fixed my phone using this trick, however, even if you had frp unlocked it would say you that isn't possible to write anything because you broke some partition, and that's the reason why you can't boot recovery, wait one second and think: why doesn't my recovery boot?
It has nothing to do with trust. I did it and device is still a full stone brick. Nothing changed by locking the bootloader besides that now I can't unlock the bootloader anymore.