Database Info

no command & no drivers

hello
my phone stuck on the circles dots that spins i gave it like 30 mints and nothing, when i try to plug it in the PC i dont have the drivers and when i try to get in the recovery mode i get the no command massage
i really dont know what to do now...
ty for your help

When you boot to recovery, you don't see the dead android on his back?

when i try to get to recovery i see the dead android with no command
but i have access to boot loader (not really helping)

When you see the dead android, press and hold power button, then press volume up.

audit13 said:
When you see the dead android, press and hold power button, then press volume up.
Click to expand...
Click to collapse
together or one after another?
what i should see?

One after the other and it will take you I to stock recovery.

ok got to there
when i try to make wipe i get stuck and the the died android get flashing(same as cache)

What happens when you factory wipe? How do you get back to the android?

when i factory wipe i see the dead android flashing like every 5 sec for 1 mili sec
and if i want to get back to boot loader or something else i press power button and up\down
i think its the cache that doing the problem becuas when i do the factory rest its saying:
--Wiping data...
formatting \data...(1-2 minuts wait)
formatting \cache...
after 5 sec flashing of dead android
and if i do wipe of cache i get the flashing like 5 sec after...

Try flashing a stock rom via fastboot. Make sure to perform a factory wipe before booting the rom for the first time.

audit13 said:
Try flashing a stock rom via fastboot. Make sure to perform a factory wipe before booting the rom for the first time.
Click to expand...
Click to collapse
how can i flash a rom if i dont have any drivers and the Pc dont recognize the phone when i press on "update from ADB"...?

Did you install the drivers before connecting the phone? You can't use stock recovery to flash a stock rom, you use fastboot mode.
Have you tried different USB cables, USB ports, computers, and operating systems? Is the bootloader unlocked?

ok so this is the deal with the phone.
i didn't touch this phone for the last 3 mounts and now i am thinking to buy new one or to fix this(prefer to fix).
the pc that i am using dont have the driver and the phone wont start(stuck in loop-dots circle) so i cant really install the drivers properly.
the phone is unlock-root dont remember if it have superuser and i cant think of a way to fix it
i dont have fast boot mode
thank you for your help i realy need him alive

Not sure how the phone can't have fastboot mode. What happens when you try to boot into fastboot mode?

i got the driver on the PC and tryed to install the factory rom
after he finished the phone starts to go up but still stuck on the circle dots(waited all day)
after that tried to wipe again and nothing..

After flashing the stock ROM, boot back into fastboot mode, flash userdata.img file, immediately boot into recovery from fastboot mode, perform a factory wipe, reboot.

"flash userdata.img file, immediately boot into recovery from fast boot mode"
need more info for that please its new to me...
how i can flash it if i dont have recovery mode?
i am using nrt program to install the images, if you have any other why i would like to know

just tried Flashing the factory images using method 1 from here:
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
but no success. got this error in the cmd line, GOT any suggestions?
target reported max download size of 1073741824 bytes
sending 'bootloader' (2506 KB)...
OKAY [ 0.284s]
writing 'bootloader'...
FAILED (remote flash write failure)
finished. total time 0.490s
rebooting into bootloader...
OKAY [ 0.106s]
finished. total time 0.109s
target reported max download size of 1073741824 bytes
sending 'radio' (42033 KB)...
OKAY [ 1.496s]
writing 'radio'...
FAILED (remote flash write failure)
finished. total time 2.725s
rebooting into bootloader...
OKAY [ 0.102s]
finished. total time 0.104s
target reported max download size of 1073741824 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
Creating filesystem with parameters
Size 13725835264
Block size 4096
Blocks per group 32768
Inodes per group 8144
Inode size 256
Journal blocks 32768
Label
Blocks 3351034
Block groups 103
Reserved block group size 823
Created filesystem with 11838832 inodes and 936543351034 blocks
Creating filesystem with parameters
Size 734003200
Block size 4096
Blocks per group 32768
Inodes per group 7472
Inode size 256
Journal blocks 2800
Label
Blocks 179200
Block groups 6
Reserved block group size 47
Created filesystem with 1144832 inodes and 5813179200 blocks
--------------------------------------------
Bootloader Version... HHZ12h
Baseband Version..... M8974A-2.0.50.2.26
Serial Number........ 04b3d59122d76e25
--------------------------------------------
checking product...
OKAY [ 0.100s]
checking version-bootloader...
FAILED
Device version-bootloader is 'HHZ12h'.
Update requires 'HHZ11d'.
finished. total time 0.547s
Press any key to exit...

Is the bootloader unlocked before the flashed process starts?

the phone is ulocked and if i try to get in bootloader i get the died android, in the prosses of the flash of the factory imege the phone stayes in the same state(in fastboot) after its finished i get all the failers and then the phone restarts and stuck on the dots spin

TF700T - Bootloop TWRP after install with official TWRP app

Hi Guys, I need some help.
I tried to flash TWRP 3.1 over a 3.0 using the official TWRP app from the store (With root access) The img file I downloaded using the app is the one specific for the TF700T.
Now my device got stuck in a TWRP bootloop. Initially I got the classic RCK/ANDROID/WHIPE DATA menu, but since I used whipe data it is only cycling through TWRP boot loops. (No more menu)
I can only stop the loop using the volume-up rocker during boot.
I'm trying the adb sideload but I am unable to flash the recovery partition.
adb devices does return the device ID followed by 'recovery' but when flashing the new img file the process only waits for a responding device.
> adb devices (output above)
> adb reboot bootloader
> adb devices (output above)
> fastboot -i 0x0B05 flash recovery twrp31.img (Here is where it fails, the device reboot by itself returning to the bootloop / TWRP is obviously not flashed)
Tx a lot for your help
JS:crying:

Geez - where to start?
You should never use Wipe Data from the bootloader menu if you have a custom recovery installed!
You cannot use fastboot commands while connected in adb.
Two different protocols or tools:
Use adb in recovery or Android, and fastboot when I the bootloader.
And that is where you want to be to fix this.
So you have to use bootit.ko to kick the tablet out of the loop and into the bootloader. Not literally please
Check out the guide below and ask if not clear before you completely brick it...
And then never use an app again to flash a recovery. Ever!
http://www.transformerforums.com/fo...my-transformer-tf700-boots-only-recovery.html
Sent from my Nexus 5X using Tapatalk

Hi
Thanks for your comments on my post. I will have a good look at the info tonight and check if all is clear before I execute the next step.
Kindest regards
JS
PS: I'll be a good boy from now on and keep your advice in the back of my head at all times.

It's not the first time that I see a story like yours. These apps have to be designed for many, many different devices and identify the correct partition to the flash the recovery to for each device. So they either need a large data base of Android devices with the correct partition tables (not likely) or they need to read the partition table off the device - correctly... And that's the weak spot. If you're unlucky it could flash the recovery to the boot partition - good luck getting out of that one.
In your case it flashed it wrong but not super wrong and then you made it worse with that wipe data.
As long as you have adb in recovery this should be fixable. Good luck!
Sent from my Nexus 5X using Tapatalk

Made some progress
Here are the results of my attempt
adb push bootit.ko /
1136 KB/s (27690 bytes in 0.023s)
adb shell insmod /bootit.ko
(No return, so I asume its ok)
GOT OUT OF BOOTLOOP
fastboot devices
015d2bbce63fec14 fastboot
fastboot erase misc
erasing 'misc'...
OKAY [ 0.260s]
finished. total time: 0.261s
fastboot reboot
rebooting...
finished. total time: 0.020s
fastboot -i 0x0B05 flash recovery twrp31.img
< waiting for device >
sending 'recovery' (7218 KB)...
OKAY [ 2.863s]
writing 'recovery'...
OKAY [ 8.069s]
finished. total time: 10.933s
fastboot reboot
rebooting...
finished. total time: 0.021s
TWRP 3.1.0.0 is loaded, when I boot I get the splash screen, but there it loops again. Stop bootloop by using Volume down rocker.
I have used following commands with the new 3.1.0.0
fastboot erase recovery
erasing 'recovery'...
OKAY [ 1.249s]
finished. total time: 1.249s
fastboot -w
Creating filesystem with parameters:
Size: 29618601984
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7231104
Block groups: 221
Reserved block group size: 1024
Created filesystem with 11/1810432 inodes and 157662/7231104 blocks
Creating filesystem with parameters:
Size: 448790528
Block size: 4096
Blocks per group: 32768
Inodes per group: 6848
Inode size: 256
Journal blocks: 1712
Label:
Blocks: 109568
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/27392 inodes and 3534/109568 blocks
erasing 'userdata'...
OKAY [ 64.078s]
sending 'userdata' (139133 KB)...
OKAY [ 25.092s]
writing 'userdata'...
OKAY [ 2.166s]
erasing 'cache'...
FAILED (command write failed (Unknown error))
finished. total time: 96.343s
fastboot -i 0x0B05 flash recovery filename.img
sending 'recovery' (7126 KB)...
OKAY [ 2.029s]
writing 'recovery'...
OKAY [ 7.546s]
finished. total time: 9.590s
fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.021s
TWRP does start OK, I am able to flash a custom ROM
Thanks a lot for your incredible support. I hope to have your knowledge and understanding on this topic on day
Kindest regards
JS

It's just practice my friend, just practice. And making a lot of stupid mistakes. Like you did.
Glad you're up and running
Sent from my Nexus 5X using Tapatalk

Hi,
I had to erase/format the system and data partition to get access to TWRP. (fastboot -w)
Once that was done, it all went smooth and silky.
Tx again
JS :good:

berndblb said:
Geez - where to start?
You should never use Wipe Data from the bootloader menu if you have a custom recovery installed!
You cannot use fastboot commands while connected in adb.
Two different protocols or tools:
Use adb in recovery or Android, and fastboot when I the bootloader.
And that is where you want to be to fix this.
So you have to use bootit.ko to kick the tablet out of the loop and into the bootloader. Not literally please
Check out the guide below and ask if not clear before you completely brick it...
And then never use an app again to flash a recovery. Ever!
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I made this same stupid mistake. However, my situation is a bit more irritating. TWRP never actually finishes loading on my TF700T; rather the splash screen appears and about 20 seconds or so later it reboots and continues this same vicious cycle. So I can't keep an adb device attached long enough to issue the adb commands. Any ideas how I can get out of this mess? Any ideas are much appreciated!
---------- Post added 15th April 2017 at 12:01 AM ---------- Previous post was 14th April 2017 at 11:49 PM ----------
[email protected] said:
I made this same stupid mistake. However, my situation is a bit more irritating. TWRP never actually finishes loading on my TF700T; rather the splash screen appears and about 20 seconds or so later it reboots and continues this same vicious cycle. So I can't keep an adb device attached long enough to issue the adb commands. Any ideas how I can get out of this mess? Any ideas are much appreciated!
Click to expand...
Click to collapse
Ha, never mind. I created a batch file to execute the two commands quicker than I could type them and ran it as soon as TWRP appeared and this got me back to the bootloader. Thanks!

[email protected] said:
I made this same stupid mistake. However, my situation is a bit more irritating. TWRP never actually finishes loading on my TF700T; rather the splash screen appears and about 20 seconds or so later it reboots and continues this same vicious cycle. So I can't keep an adb device attached long enough to issue the adb commands. Any ideas how I can get out of this mess? Any ideas are much appreciated!
---------- Post added 15th April 2017 at 12:01 AM ---------- Previous post was 14th April 2017 at 11:49 PM ----------
Ha, never mind. I created a batch file to execute the two commands quicker than I could type them and ran it as soon as TWRP appeared and this got me back to the bootloader. Thanks!
Click to expand...
Click to collapse
Hey @[email protected] - how about sharing the script? I'd like to add it to the guide.

[email protected] said:
I made this same stupid mistake. However, my situation is a bit more irritating. TWRP never actually finishes loading on my TF700T; rather the splash screen appears and about 20 seconds or so later it reboots and continues this same vicious cycle. So I can't keep an adb device attached long enough to issue the adb commands. Any ideas how I can get out of this mess? Any ideas are much appreciated!
---------- Post added 15th April 2017 at 12:01 AM ---------- Previous post was 14th April 2017 at 11:49 PM ----------
Ha, never mind. I created a batch file to execute the two commands quicker than I could type them and ran it as soon as TWRP appeared and this got me back to the bootloader. Thanks!
Click to expand...
Click to collapse
Hello can you share your batch file because I have the same problem as you had.

The unsolvable bootloop [Help Request]

Where to start after all the troubleshooting I've done...:crying:
I have the NVIDIA Shield Tablet K1 and rooted it a while back, it was working fine for a long time, months.... Then I went to use my tablet again after about a week or so of not using it so it was dead of course, charged it. Turned it on and was welcomed by a lovely bootloop. So I restart it and go into my TWRP recovery and go to format the device only to find that none of my partitions are able to mount.
When I Factory reset I get the following...
PHP:
Failed to mount '/cache' (Invalid argument)
E: Primary block device '/dev/block/platform/sdhci-tegra.3./by-name/UDA' for mount point '/data' is not present !
Failed to mount '/data' (Invalid argument)
Unable to recreate /data/media folder.
Updating partition details...
Failed to mount '/system' (Invalid argument)
Failed to mount '/cache' (Invalid argument)
Failed to mount '/data'
...done
Unable to mount storgae
Failed to mount '/data' (Invalid argument)
Full SELinux support is present.
Unable to mount /data/media/TWRP/.twrps
MTP Enabled
Updating partition details...
Failed to mount '/system' (Invalid argument)
Failed to mount '/cache' (Invalid argument)
Failed to mount '/data' (Invalid argument)
...done
Unable to mount storage
But it says successful, and pretty much same error if I try to format the data.
It won't let me mount any partitions even after the following commands which are successful in ADB
I have even tried the nice script NVIDIA made to flash everything as well.
PHP:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
Some extra things I have noticed was that my [nvtboot] (version *) appeared as a weird looking symbol , like a circle with a square and a triangle scrambled together and same as my boot.
^^This was the first time I noticed this
Then when I flashed the everything even the bootloader it made this symbol disappear and changed it to [nvtboot] (version 19951_588.2760)
The device still would not boot.
I then loaded TWRP and to my surprise it worked and I got back to square one with the inability to mount any partitions. And for each partition showed 0MB.
I think the device may be bricked but I want to save it because I loved my tablet. It's in pristine condition and is about a year old only after the RMA turn ins for the old model.
When I do the flashall.bat which I am doing right now. I reboot and it still does not boot up.
HTML:
target reported max download size of 570425344 bytes
sending 'recovery' (10286 KB)...
OKAY [ 0.450s]
writing 'recovery'...
OKAY [ 0.413s]
finished. total time: 0.866s
target reported max download size of 570425344 bytes
sending 'boot' (6996 KB)...
OKAY [ 0.297s]
writing 'boot'...
OKAY [ 0.276s]
finished. total time: 0.576s
target reported max download size of 570425344 bytes
erasing 'system'...
OKAY [ 0.232s]
sending sparse 'system' (556862 KB)...
OKAY [ 23.301s]
writing 'system'...
OKAY [ 22.077s]
sending sparse 'system' (547639 KB)...
OKAY [ 22.936s]
writing 'system'...
OKAY [ 20.968s]
sending sparse 'system' (127570 KB)...
OKAY [ 5.434s]
writing 'system'...
OKAY [ 4.940s]
finished. total time: 99.897s
target reported max download size of 570425344 bytes
erasing 'userdata'...
OKAY [ 1.758s]
sending sparse 'userdata' (557052 KB)...
OKAY [ 23.332s]
writing 'userdata'...
OKAY [ 18.589s]
sending sparse 'userdata' (557052 KB)...
OKAY [ 24.195s]
writing 'userdata'...
OKAY [ 18.511s]
sending sparse 'userdata' (517936 KB)...
OKAY [ 22.409s]
writing 'userdata'...
OKAY [ 17.156s]
sending sparse 'userdata' (129718 KB)...
OKAY [ 5.656s]
writing 'userdata'...
OKAY [ 4.516s]
finished. total time: 1028.914s
target reported max download size of 570425344 bytes
sending 'staging' (18041 KB)...
OKAY [ 0.783s]
writing 'staging'...
OKAY [ 0.659s]
finished. total time: 1.445s
Press any key to exit...
I am open to all troubleshooting steps you guys can throw at me. I am very tech savvy and hold a Tier II IT position currently with multiple certifications. I for the life of me can't figure this one out. I have been working on this one for weeks and weeks and decided to post on here to get some assistance.

At least tell me I am screwed haha.

if u boot on TWRP . for me it's maybe soft bricked.
where did u find the nvidia script ?
could u see ur device in adb ?

suicyko said:
if u boot on TWRP . for me it's maybe soft bricked.
where did u find the nvidia script ?
could u see ur device in adb ?
Click to expand...
Click to collapse
So I can freely remove or install TWRP and boot from most versions. But within the TWRP it shows that there are no partitions as stated above which is odd. I got the Nvidia script from developer.nvidia.com / gameworksdownload
And i did see my devices in ADB

Try going into TWRP while connected to PC and see if your PC can detect your tablet as removable storage. If it can try reformatting your tablet.

fpozar said:
Try going into TWRP while connected to PC and see if your PC can detect your tablet as removable storage. If it can try reformatting your tablet.
Click to expand...
Click to collapse
I managed to get it to detect as 'wx_na_wf'. Unable to format or do anything of the sort. I used TWRP 2.8.7.0 to format the partitions as ext4 and still errored out as not being able to mount. Pretty much said unable to repair /'anything' and or unable to mount anything either. I used the file manager and could view some of the files within the devices and even rename or delete them with TWRP but as far as mounting anything or booting the device when I run the install.bat. Nothing works. It's really weird. I can even install different versions of TWRP so how can the recovery work but nothing else. It's really odd

Install the newest twrp from twrp.me or find twrp with f2fs support by BitObsession.
Check &/or repair file system for all partitions. For stock all should be ext4. @Rogark

Everytime I try to repair using TWRP, I receive the below error, I tried every build up from 3.0.0-0 to the latest.
Code:
Failed to mount '/cache' (Invalid argument)
E: Primary block device '/dev/block/platform/sdhci-tegra.3./by-name/UDA' for mount point '/data' is not present !
Failed to mount '/data' (Invalid argument)
Unable to recreate /data/media folder.
Updating partition details...
Failed to mount '/system' (Invalid argument)
Failed to mount '/cache' (Invalid argument)
Failed to mount '/data'
...done
Unable to mount storgae
Failed to mount '/data' (Invalid argument)
Full SELinux support is present.
Unable to mount /data/media/TWRP/.twrps
MTP Enabled
Repairing System using e2fsck...
/sbin/e2fsck -fp process ended with ERROR: 16
Unable to repair System
Same thing with f2fs. (mkfs.f2fs -t 0 processs ended with ERROR: 1
Unable to wipe System.
Error changing file system.
Updating partition details
unable to mount the same as above.
What I don't get is how I can change my recovery just fine and fix my NVTBOOT with a stock shield rom but it's acting like my partitions are not seen or they contain no memory. I don't want to give up on this but
I also don't know what else to do. This is really weird, maybe this is a brick at this point.

Try formatting with stock recovery?

lafester said:
Try formatting with stock recovery?
Click to expand...
Click to collapse
I tried this as well. I boot to recovery, I tried different stock versions from factory to 5.2. When I boot to recovery it takes about 5 minutes for me to get the dead android, sometimes it says no command.

Any other tips or things to try? I am pondering the microwave at this point.

Bump, still want to save my tablet.

Have you tried the Mutlirom TWRP from last Year that is floating around? Give it a shot if not.

I was having the same issue, I did some looking around and found another post stating that after flashing the factory image, to flash the tegra124-tn8-p1761-1270-a04-e-battery.dtb file. I did that and it worked like a charm and now im running lineageOS 15.1, Hopefully that helps you out, although i did try many things prior to that like using fastboot commands to erase/ format my cache and data partitions.

So, I flashed the tegra battery file and tried that and now the screen just begins to load on boot but after about 4 seconds of loading, it will freeze the image of the NVIDIA symbol and get brighter and pixelate until it shuts out and goes black for another reboot. This is a new error. I will flash everything again once more and try this one more time. I miss my tablet lol

Still states that it can't find partition sizes on TWRP after flashing everything to stock even battery.dtb. It continue states unable to mount /data,cache, etc. <--This was with multirom and even tried all of the repairs which all failed out.
I will try whatever else you guys recommend. Just need further guidance please. This one is mind-boggling for sure

Something else to maybe help you guys. I flash to a stock rom even the dtb file and go to recovery mode in which i receive a dead android. Then I hold power and the up volume button to get the sys options and proceed to factory reset or mount /system files in there and receive the partition mounting errors as well. Why does it flash the ROMs successfully but can never mount them or boot properly?

So I can flash TWRP to my recovery and actually use adb to push files to the different /sdcard /data directories and such, I pushed .imgs and even SuperSU.zip and installed it but something is wrong with my partition table.

Did you try flashing the original stock lollipop rom?

fpozar said:
Did you try flashing the original stock lollipop rom?
Click to expand...
Click to collapse
Just tried that and even cleaned all of my partitions once more before hand and flashed everything to the stock build. Still does same thing. This is crazy lol

Fastboot -w (format userdata) not working (File system type raw not supported.) while installing twrp

Hi, so i am trying to root my "Motorola G7 power" but first i want to install TWRP and to do this i need to format the userdata first but every time i try to this i get this output(error):
C:\...\platform-tools>fastboot -w
Erasing 'userdata' OKAY [ 0.033s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata' (bootloader) Permission denied
FAILED (remote: '')
fastboot: error: Command failed
Click to expand...
Click to collapse
I also tried to install TWRP witout formatting but that doesn't work. Does someone maybe know how i can fix this issue? If you need any more info please tell me.

Hey there. Do you found any solution to this? I'm having the error:
File system type raw not supported

I have the same error for moto g7 power (ocean) trying to run 'fastboot -w'

backup your data imei and qcn,then use 9008&qfil to flash the firmware again.

Huawei Honor 8 Unable to install any ROMs, flash IMGs, and mount specific partitions

I just realized that I probably bricked my phone while trying to install a ROM.
After failing to install the custom ROM, my phone displayed that it is unable to mount:
Failed to mount '/cust' (Invalid Argument)
Failed to mount '/vendor' (Invalid Argument)
Failed to mount '/product' (Invalid Argument)
I have tried to use TWRP to:
Change file system for all of these partitions by switching to EXT2 back to EXT4 but resulted in error messages like this:
Unable to wipe Vendor
Error changing file system
Next I tried to repair these partitions but only resulted in this error message:
Repairing Vendor using e2fsck...
/sbin/e2fsck -fp process ended with ERROR: 16
Unable to repair Vendor
I concluded that perhaps the cust, vendor, and product partitions don't exist.
I then tried to use bootloader to erase the existing partitions of cust, vendor, and product and since my device originally doesn't have a vendor, I decided to just delete and reinstall it (except for cust & product):
platform-tools> .\fastboot.exe erase vendor
Erasing 'vendor' FAILED (remote: 'Command not allowed')Erasing 'vendor'
fastboot: error: Command failed
platform-tools> .\fastboot.exe erase cust
Erasing 'cust' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
platform-tools> .\fastboot.exe flash cust .\System\CUST.img
Sending 'cust' (258509 KB) OKAY [ 6.442s]
Writing 'cust' FAILED (remote: 'partition error')
fastboot: error: Command failed
After these error messages, I tried installing another custom OS that worked previously but it seems like the phone is stuck in the "your device is currently booting" screen although the initial installation of the OS was successful in TWRP besides the error messages of:
Failed to mount '/cust' (Invalid Argument)
Failed to mount '/vendor' (Invalid Argument)
Failed to mount '/product' (Invalid Argument)
I searched online and found that I could use the dload method by having an UPDATE.APP inside a folder called dload on a SD Card which should allow your huawei phone to boot into the stock image. Unfortunately, that did absolutely nothing.
I have then tried to flash the stock BOOT.img from the UPDATE.APP through fastboot:
platform-tools> .\fastboot.exe boot .\System\BOOT.img
creating boot image...
creating boot image - 15863808 bytes
Sending 'boot.img' (15492 KB) OKAY [ 0.332s]
Booting FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
but unfortunately with no success...
I have tried connecting HiSuite with the phone in bootloader but HiSuite returned a message saying that this device isn't supported.
I have lastly tried to relock the bootloader which did nothing with the factory reset failing at ~15%.
Erecovery mode doesn't work for this phone due to a failure to get the packets as well...
Now I am just left with a phone with no OS with TWRP installed...
Are there any solutions to installing an OS on this phone to get this phone running? Thanks in advance!
Some additional information:
My phone displayed that its a FRD-L14C567 before installing a custom OS
After installing the custom OS, it displayed that my phone is a FRD-L04
Since I cannot find any free ROM for FRD-L14, I decided to use the ROM for FRD-L04C567 which are the .img files I flashed to the phone.

paulLi_01 said:
I just realized that I probably bricked my phone while trying to install a ROM.
After failing to install the custom ROM, my phone displayed that it is unable to mount:
Failed to mount '/cust' (Invalid Argument)
Failed to mount '/vendor' (Invalid Argument)
Failed to mount '/product' (Invalid Argument)
I have tried to use TWRP to:
Change file system for all of these partitions by switching to EXT2 back to EXT4 but resulted in error messages like this:
Unable to wipe Vendor
Error changing file system
Next I tried to repair these partitions but only resulted in this error message:
Repairing Vendor using e2fsck...
/sbin/e2fsck -fp process ended with ERROR: 16
Unable to repair Vendor
I concluded that perhaps the cust, vendor, and product partitions don't exist.
I then tried to use bootloader to erase the existing partitions of cust, vendor, and product and since my device originally doesn't have a vendor, I decided to just delete and reinstall it (except for cust & product):
platform-tools> .\fastboot.exe erase vendor
Erasing 'vendor' FAILED (remote: 'Command not allowed')Erasing 'vendor'
fastboot: error: Command failed
platform-tools> .\fastboot.exe erase cust
Erasing 'cust' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
platform-tools> .\fastboot.exe flash cust .\System\CUST.img
Sending 'cust' (258509 KB) OKAY [ 6.442s]
Writing 'cust' FAILED (remote: 'partition error')
fastboot: error: Command failed
After these error messages, I tried installing another custom OS that worked previously but it seems like the phone is stuck in the "your device is currently booting" screen although the initial installation of the OS was successful in TWRP besides the error messages of:
Failed to mount '/cust' (Invalid Argument)
Failed to mount '/vendor' (Invalid Argument)
Failed to mount '/product' (Invalid Argument)
I searched online and found that I could use the dload method by having an UPDATE.APP inside a folder called dload on a SD Card which should allow your huawei phone to boot into the stock image. Unfortunately, that did absolutely nothing.
I have then tried to flash the stock BOOT.img from the UPDATE.APP through fastboot:
platform-tools> .\fastboot.exe boot .\System\BOOT.img
creating boot image...
creating boot image - 15863808 bytes
Sending 'boot.img' (15492 KB) OKAY [ 0.332s]
Booting FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
but unfortunately with no success...
I have tried connecting HiSuite with the phone in bootloader but HiSuite returned a message saying that this device isn't supported.
I have lastly tried to relock the bootloader which did nothing with the factory reset failing at ~15%.
Erecovery mode doesn't work for this phone due to a failure to get the packets as well...
Now I am just left with a phone with no OS with TWRP installed...
Are there any solutions to installing an OS on this phone to get this phone running? Thanks in advance!
Some additional information:
My phone displayed that its a FRD-L14C567 before installing a custom OS
After installing the custom OS, it displayed that my phone is a FRD-L04
Since I cannot find any free ROM for FRD-L14, I decided to use the ROM for FRD-L04C567 which are the .img files I flashed to the phone.
Click to expand...
Click to collapse
Unlock bootloader with PotatoNV or DC Unlocker or DC Phoenix
then u will allowed commands.

sircamot said:
Unlock bootloader with PotatoNV or DC Unlocker or DC Phoenix
then u will allowed commands.
Click to expand...
Click to collapse
Yes, I have already done that! Unfortunately, I believe that these commands requires root access which I have tried installing super SU with which did not help with my problem...
I have already bought a new phone since there are no official huawei repair centers in the US with the Canada one not supporting repairs on this huawei honor 8 international model. However, fixing it would be nice though...
In addition, I have tried installing Havoc OS for hopes to have the partitions rewritten for android 9 but it didn't help at all

Really used DC Phoenix? this tool will rewrite all phone firm to DC Original firmware like OFW
after all, unlock bootloader in phone's setting, now again DC Phoenix, choose Update by TP,
check Load and temporally unclock boot loader, select ur cpu at bootloader files, and press Do job
(Maybe Kirin650 will success after all)
now, u can use PotatoNV and make ur bootloader unlock num
then open windows powershell, enter like this
fastboot oem unlock numbers (PotatoNV generated)
u know? u already can use fastboot command at this time but wait patiently
next, push vol+ buttom to toggle bootloader unclock and push power to comfirm.
ur phone will reboot and initialize user data
again enter bootloader mode and open DC Phoenix
check Load and temporally unclock boot loader, select ur cpu at bootloader files, and press Do job
now u can use fastboot commands
Note: this method means reflesh ur phone at all so of course ur root should lost
u need to flash TWRP and super su after all again

sircamot said:
Really used DC Phoenix? this tool will rewrite all phone firm to DC Original firmware like OFW
after all, unlock bootloader in phone's setting, now again DC Phoenix, choose Update by TP,
check Load and temporally unclock boot loader, select ur cpu at bootloader files, and press Do job
(Maybe Kirin650 will success after all)
now, u can use PotatoNV and make ur bootloader unlock num
then open windows powershell, enter like this
fastboot oem unlock numbers (PotatoNV generated)
u know? u already can use fastboot command at this time but wait patiently
next, push vol+ buttom to toggle bootloader unclock and push power to comfirm.
ur phone will reboot and initialize user data
again enter bootloader mode and open DC Phoenix
check Load and temporally unclock boot loader, select ur cpu at bootloader files, and press Do job
now u can use fastboot commands
Note: this method means reflesh ur phone at all so of course ur root should lost
u need to flash TWRP and super su after all again
Click to expand...
Click to collapse
I haven't used DC Pheonix. I can try it right now! Thanks!

paulLi_01 said:
I haven't used DC Pheonix. I can try it right now! Thanks!
Click to expand...
Click to collapse
Welcome, cheers!