Huawei P8 (L09) bricked TWRP no OS - General Questions and Answers

I tried to do reset my phone for battery issues. The thing is that it seems i don't have operating system now and i can't flash the phone because TWRP is the only loader and it doesn't recognizes the update app. Any idea to install at least a custom rom via TWRP or any way to unbrick the phone? Thanks. Any other detail you need please ask me. It is the first time i need help to fix a phone.

icemann1908 said:
I tried to do reset my phone for battery issues. The thing is that it seems i don't have operating system now and i can't flash the phone because TWRP is the only loader and it doesn't recognizes the update app. Any idea to install at least a custom rom via TWRP or any way to unbrick the phone? Thanks. Any other detail you need please ask me. It is the first time i need help to fix a phone.
Click to expand...
Click to collapse
If you know the version of the rom, simply download that version stock rom and then extract from it the recovery using Huawei extractor tool and flash that recovery using adb. After that put the stock rom in a dload folder and put it on your sdcard or internal memory after that turnoff the device hold power and vol up and vol down at the same to make the flash process start and flash the stock rom. Sorry I am on the road and quite busy otherwise I would have written a detailed guide. But if you Google what I suggested you will find the tools needed to make it work. If still you can't manage to make it work let me know. After 2 days I would be around a pc to write a better guide.
Sent from my Nexus 6P using XDA-Developers mobile app

Rashad83 said:
If you know the version of the rom, simply download that version stock rom and then extract from it the recovery using Huawei extractor tool and flash that recovery using adb. After that put the stock rom in a dload folder and put it on your sdcard or internal memory after that turnoff the device hold power and vol up and vol down at the same to make the flash process start and flash the stock rom. Sorry I am on the road and quite busy otherwise I would have written a detailed guide. But if you Google what I suggested you will find the tools needed to make it work. If still you can't manage to make it work let me know. After 2 days I would be around a pc to write a better guide.
Goood Afternoon,
I have the same problem but i tried what you said and when i try to flash my device i would get:
C:\Users\Ebonique\Downloads\fastboot>fastboot flash recovery RECOVERY.img
target reported max download size of 471859200 bytes
sending 'recovery' (28228 KB)...
OKAY [ 0.640s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.648s
C:\Users\Ebonique\Downloads\fastboot>
And Honestly i do not know what to do. Any suggestions?
Click to expand...
Click to collapse

ebbytay said:
Rashad83 said:
If you know the version of the rom, simply download that version stock rom and then extract from it the recovery using Huawei extractor tool and flash that recovery using adb. After that put the stock rom in a dload folder and put it on your sdcard or internal memory after that turnoff the device hold power and vol up and vol down at the same to make the flash process start and flash the stock rom. Sorry I am on the road and quite busy otherwise I would have written a detailed guide. But if you Google what I suggested you will find the tools needed to make it work. If still you can't manage to make it work let me know. After 2 days I would be around a pc to write a better guide.
Goood Afternoon,
I have the same problem but i tried what you said and when i try to flash my device i would get:
C:\Users\Ebonique\Downloads\fastboot>fastboot flash recovery RECOVERY.img
target reported max download size of 471859200 bytes
sending 'recovery' (28228 KB)...
OKAY [ 0.640s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.648s
C:\Users\Ebonique\Downloads\fastboot>
And Honestly i do not know what to do. Any suggestions?
Click to expand...
Click to collapse
You need to make sure your bootloader is unlocked otherwise it won't work. If your bootloader is indeed unlocked then it could be a PC communication issue try to reinstall drivers of the phone, even better try it on another PC/Laptop with a fresh install of drivers and applications needed.
Click to expand...
Click to collapse

Rashad83 said:
ebbytay said:
You need to make sure your bootloader is unlocked otherwise it won't work. If your bootloader is indeed unlocked then it could be a PC communication issue try to reinstall drivers of the phone, even better try it on another PC/Laptop with a fresh install of drivers and applications needed.
Click to expand...
Click to collapse
My bootloader is unlocked
I have tried to install the usb drivers but im not sure if i am currently installing them correctly.
When i type enter fastboot devices i get:
C:\Users\Ebonique\Downloads\fastboot>fastboot devices
S7M0215B19000640 fastboot
C:\Users\Ebonique\Downloads\fastboot>
but when i enter adb devices i get:
C:\Users\Ebonique\Downloads\fastboot>adb devices
List of devices attached
C:\Users\Ebonique\Downloads\fastboot>
Is there any possibility that you can walk me through installation of the devices? I have a Huawei Gra-L09 (P8)
Click to expand...
Click to collapse

ebbytay said:
Rashad83 said:
My bootloader is unlocked
I have tried to install the usb drivers but im not sure if i am currently installing them correctly.
When i type enter fastboot devices i get:
C:\Users\Ebonique\Downloads\fastboot>fastboot devices
S7M0215B19000640 fastboot
C:\Users\Ebonique\Downloads\fastboot>
but when i enter adb devices i get:
C:\Users\Ebonique\Downloads\fastboot>adb devices
List of devices attached
C:\Users\Ebonique\Downloads\fastboot>
Is there any possibility that you can walk me through installation of the devices? I have a Huawei Gra-L09 (P8)
Click to expand...
Click to collapse
That's normal, in order to see your device using adb commands it needs to be turned on and working properly also the developer mode needs to be enabled in order to see your device code serial number so in other words it's not possible at your current situation.
Regarding the device drivers just connect the device to the PC and let it auto install the drivers needed make sure Hisuite package is installed before that.
The only commands you can use at your current case with the phone in bootloader mode is only fastboot commands. So just try to flash the stock recovery like before and hopefully it will work out. If it does try to flash the same stock rom using the dload method. I cannot at the Moment give you a step by step I am really sorry but if you google the things you need you will find it easily.
Edit:
Similar issue maybe it can help you.
http://forum.xda-developers.com/showpost.php?p=68037081&postcount=304
Click to expand...
Click to collapse

Rashad83 said:
ebbytay said:
That's normal, in order to see your device using adb commands it needs to be turned on and working properly also the developer mode needs to be enabled in order to see your device code serial number so in other words it's not possible at your current situation.
Regarding the device drivers just connect the device to the PC and let it auto install the drivers needed make sure Hisuite package is installed before that.
The only commands you can use at your current case with the phone in bootloader mode is only fastboot commands. So just try to flash the stock recovery like before and hopefully it will work out. If it does try to flash the same stock rom using the dload method. I cannot at the Moment give you a step by step I am really sorry but if you google the things you need you will find it easily.
Edit:
Similar issue maybe it can help you.
http://forum.xda-developers.com/showpost.php?p=68037081&postcount=304
Click to expand...
Click to collapse
Thank you very much for the link it actually helped me and I was able to fix my phone.
I had no clue which stock version my phone came with so I downloaded all and then use the dload method. The phone was able to update to its original form.
I Really appreciate all of your responses, thank you once again.
Click to expand...
Click to collapse

ebbytay said:
Rashad83 said:
Thank you very much for the link it actually helped me and I was able to fix my phone.
I had no clue which stock version my phone came with so I downloaded all and then use the dload method. The phone was able to update to its original form.
I Really appreciate all of your responses, thank you once again.
Click to expand...
Click to collapse
You're welcome. Good luck.
Click to expand...
Click to collapse

Related

[Q] bad flash

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

[Q] How to install custom ROM on stock phone (HBOOT 1.xx/2.xx)

I'm really new to this, and don't want to break my device.
What exact steps do I have to do to root my device, and install a custom rom on it?
Got the HTC One S
rifek4 said:
http://forum.xda-developers.com/wiki/HTC_One_S
http://forum.xda-developers.com/showthread.php?t=2076086
http://forum.xda-developers.com/showthread.php?p=51291053
Links are a little bit older but good. Look at forum General and Development category for more stuff.. You must first do a unlock bootloader, then flash custom recovery (newest unofficial TWRP is best), then you can install new ROM which doesn't need S-OFF/superCID after that flash new kernel for it ROM via fastboot. You must looking some thread's on forum, explore the possibilities, find out what and how you can use... I can't say you everything in one word - I don't have such power
Click to expand...
Click to collapse
I tried all this, but once I get in the bootloader and try to get my "Token ID" or whatever to root it, it just says device not found and that its waiting for device.
Its in USB Debugging mode, and the drivers are fine, its latest drivers and the command to goto bootloader works fine.
Not sure what to do.
I appreciate you taking the time to link me all this though
Just not sure how to do it, I'm probably doing something wrong.
But I got as far as getting to the bootloader.
rifek4 said:
http://forum.xda-developers.com/showthread.php?t=1583427
Try unlock with this thread, not with toolkit. You use newest HTC Drivers? Delete old drivers, install this one then restart PC and try again with above thread.
Click to expand...
Click to collapse
In fastboot menu, got the CMD in right directory, typed the command to get identifier token, says "Waiting For Device..."
Still same issue :/
rifek4 said:
You do reinstall drivers? You see "FASTBOOT USB" text on fastboot menu after connect cable?
Click to expand...
Click to collapse
Says "FASTBOOT" with red highlight.
Then just has instructions, says "BOOTLOADER", Reboot, Reboot Bootloader and Power Down as options.
Also, said that driver you linked isn't compatible with my OS.
I'm on Windows 8.1
Edit: Followed those instructions, went back to repeat and try again. Still did same thing, saying waiting for device.
rifek4 said:
So is not good. After connect USB cable there must be "FASTBOOT USB" text. Check link now, I change URL. If you are on Windows 8.1 install new drivers from right URL (I change now one post before) and look HERE.
Click to expand...
Click to collapse
Says Fastboot USB now.
Going to try it out!
LunarSAF said:
Says "FASTBOOT" with red highlight.
Then just has instructions, says "BOOTLOADER", Reboot, Reboot Bootloader and Power Down as options.
Also, said that driver you linked isn't compatible with my OS.
I'm on Windows 8.1
Edit: Followed those instructions, went back to repeat and try again. Still did same thing, saying waiting for device.
Click to expand...
Click to collapse
Fastboot Win 8.1 fix
Latest official driver
Seems as you already got it
rifek4 said:
So is not good. After connect USB cable there must be "FASTBOOT USB" text. Check link now, I change URL. If you are on Windows 8.1 install new drivers from right URL (I change now link in this post before or they are JUST HERE) and look HERE. You must do fix fastboot for Windows 8.1.
Click to expand...
Click to collapse
Installing that driver now.
Then going to restart PC and reconnect phone, will let you know if it works!
rifek4 said:
Link for fix doesn't work I give him the same version drivers
Click to expand...
Click to collapse
Links fixed
rifek4 said:
After it, do a also fix fastboot for Windows 8.1
Click to expand...
Click to collapse
Sweet, just got the token! Doing the rest of the tutorial!
Believe everything is going to work now
This happened on next step:
c:\fastboot>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
FAILED (command write failed (Too many links))
finished. total time: 0.000s
rifek4 said:
Good luck!
EDIT:
Try again, reconnect phone etc.
Click to expand...
Click to collapse
Tried reconnecting phone, bootloader says "Fastboot USB" and everything, tried to put it in and still same error.
rifek4 said:
Reboot phone / reboot PC / try again?
P.S.
Sorry for asking again but you do fix for Win 8.1 ?
Click to expand...
Click to collapse
Just rebooted phone, restarted PC and did the Win 8.1 Fix thing.
Still failed D:
LunarSAF said:
Just rebooted phone, restarted PC and did the Win 8.1 Fix thing.
Still failed D:
Click to expand...
Click to collapse
Generate a new unlocktoken
BTW did you uninstall HTC sync?
LS.xD said:
Generate a new unlocktoken
BTW did you uninstall HTC sync?
Click to expand...
Click to collapse
Got it working!
Now, I'm at Step 3.
Issue is, when I go to recovery, it doesn't actually open ClockWorkMod which is the one I installed. http://www.clockworkmod.com/rommanager (6.0.4.8).
It said everything went fine in command prompt, but just boots the device instead of recovery.
Should I try with the Paul one?
LunarSAF said:
Got it working!
Now, I'm at Step 3.
Issue is, when I go to recovery, it doesn't actually open ClockWorkMod which is the one I installed. http://www.clockworkmod.com/rommanager (6.0.4.8).
It said everything went fine in command prompt, but just boots the device instead of recovery.
Should I try with the Paul one?
Click to expand...
Click to collapse
Flash TWRP 2.8.5.0
Recovery can be entered by starting up bootloader mode and select "recovery"
rifek4 said:
Why not unofficial TWRP v2.8.5.5?
Click to expand...
Click to collapse
Missing option to clean sd card. And the developer says "should work, give me feedback". As @LunarSAF just starts modding the phone official should totally do it. At least he shouldn't go for CWM.
Trying to flash TWRP v2.8.5.0
sending 'recovery' is taking forever, and hasn't finished yet.
Will edit post with results once its finished!
Not sure why its taking so long.
Edit: been a while, decided to try and restart it, reconnected phone and new CMD.
Still didn't work.
"fastboot flash recovery twrp.img"
Edit: Nvm just finished.
Going to get into recovery, install SU and see how it goes from there!
Hmm....
I put the TWRP v2.8.5.0 on the device.
Tried to get into Recovery, and it just rebooted device, wouldn't get into recovery.
rifek4 said:
Flash THIS ONE - unofficial TWRP v2.8.5.5.
Click to expand...
Click to collapse
That link doesn't work :/ Found twrp-2.8.5.5-ville.img online though.
Will that work?
rifek4 said:
Link changed. Yes I think. After write unlocktoken you choose right option on display your phone? Vol + & Power button to confirm unlock?
Click to expand...
Click to collapse
Just restarted from write unlocktoken part.
Put it in to flash it and it said it did it successfully, but isn't showing up with anything to confirm.
Confirmed something way earlier when I did it though, so might not have to do it again.
Going to try writing TWRP again and booting into recovery.
Edit: Just did that, tried to go in recovery now and it doesn't work. It just reboots the device. Don't understand why.
rifek4 said:
For me wipe internal storage option work without problems
Click to expand...
Click to collapse
On HBOOT 2.15 the option is totally missing

Fastboot FAILED (remote: failed to erase partition )

I have OPO 64GB and unlocked via fastboot. Every fastboot command related to flash or erase or format gave same error, unable to erase or write the partition.
I was able to fastboot boot <custom_recovery.img> into TWRP 2.7 I believe but TWRP gives errors, unable to mount <partition>, etc. Any command in TWRP results into a failure to mount or write.
I tried ADB Sideload <zip> and at 12% it rebooted back into Cyanogen Mod ready logo.
TWRP only runs if I boot to it via fastboot, it can't write to the bootloader via fastboot. One strange thing under TWRP storage it shows Internal Storage 0MB and USB-OTG 0MB, the partitions also show 0MB excep for system, but can't format anything or resize.
I feels like there is no storage in this device, is this something that can be fixed or is this a DOA device? It was working fine and a Cyanogen update ran and bricked it!
When I try to fastboot flash I get this error, fail to write. I even tried the OnePlusRestoreTool and it fails to write to the phone.
fastboot flash recovery twrp3.img
target reported max download size of 1073741824 bytes
sending 'recovery' (13326 KB)...
OKAY [ 0.422s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 5.479s
Thoughts?
Thank You
It seems that your partitions are corrupt.
I had the same issue and solved it by restoreing completley to stock Rom. There must be a thread for this anywhere out, if not download a fastboot image from cyanogen support site extract it and try to flash it.
That is what I was leaning towards, but in every solution to restore the stock ROM I have to use fastboot and fastboot just fails to write anything. I can't even get TWRP to stick, fails to write every time. I tried the OnePlusRestoreTool but the driver installs ok but the tool can't find the phone, tried 2 different PCs. I was hoping for another solution other than fastboot or the OnePlusRestoreTool, I searched but could not find another method, I was hoping someone could point me in the right direction.
Thanks
newpop1_android said:
I have OPO 64GB and unlocked via fastboot. Every fastboot command related to flash or erase or format gave same error, unable to erase or write the partition.
I was able to fastboot boot <custom_recovery.img> into TWRP 2.7 I believe but TWRP gives errors, unable to mount <partition>, etc. Any command in TWRP results into a failure to mount or write.
I tried ADB Sideload <zip> and at 12% it rebooted back into Cyanogen Mod ready logo.
TWRP only runs if I boot to it via fastboot, it can't write to the bootloader via fastboot. One strange thing under TWRP storage it shows Internal Storage 0MB and USB-OTG 0MB, the partitions also show 0MB excep for system, but can't format anything or resize.
I feels like there is no storage in this device, is this something that can be fixed or is this a DOA device? It was working fine and a Cyanogen update ran and bricked it!
When I try to fastboot flash I get this error, fail to write. I even tried the OnePlusRestoreTool and it fails to write to the phone.
fastboot flash recovery twrp3.img
target reported max download size of 1073741824 bytes
sending 'recovery' (13326 KB)...
OKAY [ 0.422s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 5.479s
Thoughts?
Thank You
Click to expand...
Click to collapse
Try this
geowolf1000 said:
Try this
Click to expand...
Click to collapse
So I tried the link but also their method uses FastBoot and FastBoot fails to write to the OPO every time no matter what, see below. I can put TWRP in memory but can't write to the SD I guess. Any tool that can reformat the storage and put it back together since FastBoot and ADB can't write to it?
Thx
target reported max download size of 1073741824 bytes
sending 'persist' (4244 KB)...
OKAY [ 0.137s]
writing 'persist'...
FAILED (remote: flash write failure)
finished. total time: 5.208s
Has a second method from terminal
Run command from twrp rerminal
Στάλθηκε από το A0001 μου χρησιμοποιώντας Tapatalk
Try this http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732 , it will rewrite all the partition and then change the rom and recovery you want, it should work
Chinaroad said:
Try this http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732 , it will rewrite all the partition and then change the rom and recovery you want, it should work
Click to expand...
Click to collapse
He tried that one, but as the PC doesn't detect his phone that ain't gonna work...
@newpop1_android could you sent me a PM, I'll try to resolve your issue in a teamviewer session.
Chinaroad said:
Try this http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732 , it will rewrite all the partition and then change the rom and recovery you want, it should work
Click to expand...
Click to collapse
Hello, so I managed to get an older PC to do all this in as well and tried another PC anyway. I ran the color.zip install, drivers installed OK and phone is detected, I ran the Msm8974DownloadTool.exe and it found the phone in COM3, I see a progress bar in one file, the image file and then it reboots the phone but it comes back to the Cyanogen splash screen and it does not go anywhere, so I reboot it again manually power+VUp and the tool finds it again and tries to send the *same* file again, and then I tried this loop at least 10 times.
I conclude that it is unable to write the image to the cell, same symptom I encountered with Fastboot flash boot img. Does this mean that the cell is bricked since nothing can write to the SD?
Do the progressbars you see in Msm8974DownloadTool.exe become green?
Maybe see there:
http://www.technobuzz.net/guide-to-recover-from-hard-bricked-oneplus-one/
It is nearly the same like the one posted before, but has some screenshots.
After doing this color OS should boot up, not cyanogen os.
If only one image file is "flashed", check if your color.zip is downloaded correctly
Hope this helps
Flo9818 said:
Do the progressbars you see in Msm8974DownloadTool.exe become green?
Maybe see there:
http://www.technobuzz.net/guide-to-recover-from-hard-bricked-oneplus-one/
It is nearly the same like the one posted before, but has some screenshots.
After doing this color OS should boot up, not cyanogen os.
Hope this helps
Click to expand...
Click to collapse
Hello, not really, it does one file and then I see progress bar move on the first file, progress bar finished and then the phone boots to the cyanogen screen again, then i tried again, it still shows the same file again. It does not save the file, fails to write pretty much, same thing as fastboot.
There should be serveral progressbars. One for each image in color.zip. Try to reinstall the qualcomm 2012 drivers.
Have you restarted your PC?
Flo9818 said:
There should be serveral progressbars. One for each image in color.zip. Try to reinstall the qualcomm 2012 drivers.
Click to expand...
Click to collapse
I actually did that and tried one plus one as well, I also tried the other unbrick toll as well with other drivers. The phone is recognized no problem, but nothing can write to it, just like fastbook flash , write denied every time.
Restarted your PC after qualcomm driver install?
Maybe there be driver problems related to win10.
Also check
fastboot oem device-info if your bootloader is really unlocked
Flo9818 said:
Restarted your PC after qualcomm driver install?
Maybe there be driver problems related to win10.
Also check
fastboot oem device-info if your bootloader is really unlocked
Click to expand...
Click to collapse
It won't work, his device is not recognized by adb or fastboot.
My device is in the same state, I rebooted it and it hard bricked, I tried using the ColorOS flash tool but, when I start it, it is stuck in a loop trying to flash "8974_msimage.mbn", any solution would be appreciated, because I hard bricked it in the first day after receiving my OPO (I bought an used one).
I already tried on two different computers, the same issue happens, I also tried to find a fix, but everyone that had this issue never replied, so I think this state is really THE hard brick, with no ways to go back to the original state.
@newpop1_android did you find a solution for your problem?
MrPowerGamerBR said:
It won't work, his device is not recognized by adb or fastboot.
My device is in the same state, I rebooted it and it hard bricked, I tried using the ColorOS flash tool but, when I start it, it is stuck in a loop trying to flash "8974_msimage.mbn", any solution would be appreciated, because I hard bricked it in the first day after receiving my OPO (I bought an used one).
I already tried on two different computers, the same issue happens, I also tried to find a fix, but everyone that had this issue never replied, so I think this state is really THE hard brick, with no ways to go back to the original state.
@newpop1_android did you find a solution for your problem?
Click to expand...
Click to collapse
Did you run the programm as administrator?
Someone in the oneplus forum had the same problem with loop flashing the 8974_msiimage.mbn and solved it with
http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
Maybe a try?
Flo9818 said:
Did you run the programm as administrator?
Someone in the oneplus forum had the same problem with loop flashing the 8974_msiimage.mbn and solved it with
http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
Maybe a try?
Click to expand...
Click to collapse
Yes, I did.
I also tried that tool before, same issue.
Flo9818 said:
Did you run the programm as administrator?
Someone in the oneplus forum had the same problem with loop flashing the 8974_msiimage.mbn and solved it with
http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
Maybe a try?
Click to expand...
Click to collapse
The problem is that the device gets disconnected when flashing for some reason. I tried two different drivers, both didn't work.
I'm willing to pay 5$ to someone who can fix this issue for me.
MrPowerGamerBR said:
The problem is that the device gets disconnected when flashing for some reason. I tried two different drivers, both didn't work.
I'm willing to pay 5$ to someone who can fix this issue for me.
Click to expand...
Click to collapse
Which Windows Version do you use? I would try with win7. With win 8.1 and 10 you have to disable driver verification.
Have you disabled your antivirus?
Have you disabled UAC?
Maybe another USB cable?
If all this does not work see here:
https://forums.oneplus.net/threads/solution-bricked-oneplus-one-recovery.306306/
Flo9818 said:
Did you run the programm as administrator?
Someone in the oneplus forum had the same problem with loop flashing the 8974_msiimage.mbn and solved it with
http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
Maybe a try?
Click to expand...
Click to collapse
Flo9818 said:
Which Windows Version do you use? I would try with win7. With win 8.1 and 10 you have to disable driver verification.
Have you disabled your antivirus?
Have you disabled UAC?
Maybe another USB cable?
If all this does not work see here:
https://forums.oneplus.net/threads/solution-bricked-oneplus-one-recovery.306306/
Click to expand...
Click to collapse
Windows 7, but Windows 7 also needs to disable driver verification.
I don't use any antivirus.
No, but I ran the tool as administrator.
I already tried that, I tried with the original cable that came with the device and my Moto G 2014 cable, same issue on both.
It isn't a missing driver issue tho, Qualcomm drivers are installed and working because the ColorOS flash tool detects the device.
Anyway, thanks for helping

GUIDE: eRecovery / HiSuite failing to restore - RESCUE on PIE: L29 L09 432 -- v190

WARNING
By doing this you may lose your data, this is intended for when you have nowhere else to turn to.
Back Story
Hi All,
Like a massive child I stupidly jumped on the Pie bandwagon away from a very well maintained Honor 10 ROM which ran beautifully on my P20 Pro..
After restoring EMUI, the PIE update quickly made itself visible, so i took a deep breath and committed.
After the installation, I tried to install a bunch of ROM's, I messed up a bit.
Anyway, what I found was, I was unable to recovery from eRecovery OR HiSuite, so I then found myself on the wobbly road that is restoring each parition via the bootloader using fastboot, tried to install just the recovery_ramdisk, didn't work, tried to install, kernel / cust / system / recovery_ramdisk..... STILL Didn't work.
So i downloaded another firmware, this time the exact version i was using albeit for the L-09 and not the L-29, I needed to extract the update part of the zip then read it using a tool called firmware extractor.
Ton of files in there, the files i just mentioned which are all .img files and some others.
In the end i needed several to get a perfect restore which has worked every single time without fail.
As it was a massive ballache and a learning curve for me as I'd never done it before, so I thought i'd share my experience and the files required on Mega so there aren't any ads blocking your way Yaay, also what to do and where to obtain the firmwares from my experiences.
Hope it helps someone avoid the pain I had to go through when downloading firmwares for 5 hours at a time, wasn't fun.
Good luck, any questions let me know. :good:
START HERE
*NOTE: You can do this from scratch by downloading the firmware for your device, i required 9.0.0.190 for the L29 - c432.
The best place I found was this site https://support.halabtech.com/index.php?a=downloads&b=file&c=download&id=105974
They require an account to be made but besides that they were faster and had more choice.
Once you have the firmware you'll need the Extractor, then you'll need to move several of the files into the ADB folder for flashing, see below...
Anyway, moving on........
FILES
At the foot of this guide is a link, inside it is everything you should require in order to complete this guide
ADB - Move this folder to the root of C, it should be like this C:\ADB (reason for this is it's much easier to navigate to, most people will already have this)
IMG Files for 9.0.0.190 - All of the file names you see below are img files which we'll be using to un-brick / recover / restore your device to a functional state.
Move all of them after downloading to the ADB folder in C:\ADB
CACHE.img
CUST.img
ERECOVERY_RAMDI.img
KERNEL.img
RECOVERY_RAMDIS.img
USERDATA.img
VENDOR.img
SYSTEM.img
EMUI Extractor - Not a part of this guide but you will need it should you need to download your own firmware and obtain the above files.
Pre-requisites
- A device on a maximum firmware of 9.0.0.190 (If you are on a higher firmware, then use the link above to obtain it)
- A device variant of either L-09 or L-29 (others may work but i have not tested)
- A device variant of c432 (the 782 may work but i have not tested)
- Access to the bootloader (white screen with vol down and power whilst connected to a laptop)
- Drivers so that fastboot / adb commands can be sent to your device (I won't show how to do this, it's pretty standard stuff)
- I have an unlocked bootloader myself and OEM unlocking is on (REQUIRED)
- A Windows based PC /Laptop and a functional USB-C cable. (I'm sure you can
GUIDE
On your computer / laptop
STEP 1 Download all the files from the mega link provided.
STEP 2 Copy the ADB Folder to the root of C: so it looks like this
C:\ADB
STEP 3 Open the folder called "IMG Files for 9.0.0.190" Copy the .IMG files to the ADB folder so they are loose.
STEP 4 Press Start / Windows key and type in cmd then press enter, a black window will appear
STEP 5 In the black window type the following:
cd c:\adb then press Enter
STEP 6 Connect your phone to your laptop using the USB-C cable and allow it to be seen by windows
On your Phone
STEP 7 Press and hold the power button and volume down, don't let go, your screen will go blank, once it turns back on, release the power key but continue holding vol down, a white screen should appear, you can now release the power volume key, you are now in fastboot mode and can input commands.
On your computer / laptop
Step 8 Click the CMD window and type in the following commands, you will have to wait for them to go all the way through, some take longer ie: System.img
*NOTE: For speed you can use the tab key to pre fill certain words or files, so if you've typed in "Fastboot flash cust "
You could then press the tab key and scroll through the files in the folder.
eg: if you were to press enter with this command listed fastboot flash cust c after pressing tab it would say fastboot flash cust CUST.img
PRESS ENTER AFTER EACH COMMAND, MAKE SURE EACH ONE COMPLETES.
fastboot flash cust CUST.img
fastboot flash cache CACHE.img
fastboot flash recovery_ramdisk RECOVERY_RAMDIS.img
fastboot flash userdata USERDATA.img
fastboot flash kernel KERNEL.img
fastboot flash vendor VENDOR.img
fastboot flash system SYSTEM.img
STEP 9 Once they've all been flashed, in CMD simply type the below command and allow the device to boot up, you can disconnect now.
fastboot reboot
If all has worked and it should have, then you will have a stock ROM of PIE on 9.0.0.190
You can then root and use your device as you see fit.
Here is the link to the said files (WHICH WILL NOT BE TAKEN DOWN )
NOTE: they actually now have, sorry
https://mega.nz/#F!qdMWDKZA!5PIsAnakvENegV-4GPWKdg
Any questions, please ask away and i'll do what i can to help
c:\ADB>fastboot flash cust CUST.img
target reported max download size of 471859200 bytes
sending 'cust' (176429 KB)...
OKAY [ 4.121s]
writing 'cust'...
FAILED (remote: Command not allowed)
finished. total time: 4.130s
OEM is LOCKED
@mdda7
You must have an unlocked bootloader.
titi66200 said:
@mdda7
You must have an unlocked bootloader.
Click to expand...
Click to collapse
bootloader is unlocked
but
OEM is locked
mdda7 said:
bootloader is unlocked
but
OEM is locked
Click to expand...
Click to collapse
As I said in the guide you need OEM to be unlocked. I have no idea how you can unlock it without accessing the system. I think one version of pie locked it down but then the next one unlocked it.
Did you turn off OEM unlocking yourself?
What version are you on?
Maybe a paid service can help mate. Not sure.
dladz said:
As I said in the guide you need OEM to be unlocked. I have no idea how you can unlock it without accessing the system. I think one version of pie locked it down but then the next one unlocked it.
Did you turn off OEM unlocking yourself?
What version are you on?
Maybe a paid service can help mate. Not sure.
Click to expand...
Click to collapse
Did you turn off OEM unlocking yourself?
- NO
What version are you on?
- 9.0.0.108
mdda7 said:
Did you turn off OEM unlocking yourself?
- NO
What version are you on?
- 9.0.0.108
Click to expand...
Click to collapse
OEM unlocking needs to be off mate, 108 shouldn't matter but i believe that it's the version that has the OEM greyed out.
There is a way around it but i'm not sure.
any way?
mdda7 said:
any way?
Click to expand...
Click to collapse
Certainly not with this method as you don't meet the pre-requisites.
That being said I suppose some kind of low level flash tool may work, like i said before a paid for service maybe?
Lets find out everything there is to know.
So your bootloader is unlocked.
Have do you have TWRP installed?
Did any of the images i've listed actually flash successfully?
Have you tried to use eRecovery? or Hi Suite (neither of these worked for me hence this guide)
Beyond that i suppose the only way would be a paid service but their pre-requisites may be the same as mine. In that case I would say you're out of luck, afaik this guide is essentially the lowest you can go. I don't believe anything will work without OEM unlocking turned on.
How do you get onto the firmware you're currently on ? 108 and what state is the phone in right now?
What works? Whats accessible?
@dladz thanks for the guide. You got me out of a jam already and this useful information to restore to stock.
~clumsy~ said:
@dladz thanks for the guide. You got me out of a jam already and this useful information to restore to stock.
Click to expand...
Click to collapse
Haha no worries fella.
dladz said:
Haha no worries fella.
Click to expand...
Click to collapse
Used your guide @dladz, everything flashed perfectly but on the fastboot reboot command, the PC made a noise to say the USB had disconnected as expected.
All I've got is a black screen and red flashing LED.
chrissyyyw said:
Used your guide @dladz, everything flashed perfectly but on the fastboot reboot command, the PC made a noise to say the USB had disconnected as expected.
All I've got is a black screen and red flashing LED.
Click to expand...
Click to collapse
Weird. Not sure pal. This is what I did when I was stuck. Did you read everything and follow to the letter? A higher or same firmware?
On fastboot reboot the pc saying it's disconnected is correct. Should have come on.
Does anything ever come on screen?
Thank you, life saver!!
:good:
Johnny Eng said:
Thank you, life saver!!
Click to expand...
Click to collapse
You're very welcome Use the thanks button buddy :good:
dladz said:
:good:
You're very welcome Use the thanks button buddy :good:
Click to expand...
Click to collapse
Done buddy ?
Anyway when I extract update.app, I did not find userdata.img
However I go ahead and flash only. It works too.
Thanks
Johnny Eng said:
Done buddy
Anyway when I extract update.app, I did not find userdata.img
However I go ahead and flash only. It works too.
Thanks
Click to expand...
Click to collapse
Which FW version did you flash? I’ve got the same on .282
chrissyyyw said:
Which FW version did you flash? I’ve got the same on .282
Click to expand...
Click to collapse
As i'm still on 190 I wouldn't know this, but would it be possible that userdata isn't actually a part of the update app no more?
Seeing as it still works I would assume that is the case.
There’s a user data.app packaged with update.app, just noticed it.
In update.app I’ve got file names 11.cache.img 09.cust.img
Did you have to rename yours?
chrissyyyw said:
There’s a user data.app packaged with update.app, just noticed it.
In update.app I’ve got file names 11.cache.img 09.cust.img
Did you have to rename yours?
Click to expand...
Click to collapse
No because you're going to be picking them via fastboot anyway, I don't believe the name matters.
The ones in the update I used were not named like that IIRC.

Can't do anything - need help!

After updating TWRP using TWRP it self i can't boot into custom recovery again the phone just stays loading forever, the phone is also wiped so no custom image or stock image and i cant use it since even in fastboot it just keeps saying "FAILED (remote: Command not allowed)".
The phone on FASTBOOT mode says:
Phone unlocked
but says FRP lock
maybe that is the problem? if so how can i solve it? i really want to make my honor 8 work again so thanks for your help!
Ps. Sorry for my bad English
RicardoVs said:
After updating TWRP using TWRP it self i can't boot into custom recovery again the phone just stays loading forever, the phone is also wiped so no custom image or stock image and i cant use it since even in fastboot it just keeps saying "FAILED (remote: Command not allowed)".
The phone on FASTBOOT mode says:
Phone unlocked
but says FRP lock
maybe that is the problem? if so how can i solve it? i really want to make my honor 8 work again so thanks for your help!
Ps. Sorry for my bad English
Click to expand...
Click to collapse
What android version are you on? Have you tried flashing stock recovery? Which twrp are you using? Are sure that you did not flash twrp on the wrong partition?
PremiumBlaze said:
What android version are you on? Have you tried flashing stock recovery? Which twrp are you using? Are sure that you did not flash twrp on the wrong partition?
Click to expand...
Click to collapse
I was using Paranoid android 7.1 i believe but i wiped the phone so there is no Android at all at the moment, i tried updating to the latest twrp since i was getting error 7 trying to flash the stock room, stock recovery just says "failed to get information from the server" every time and for last i did flash it in the right partition, every comand i execute in fastboot it gives me that error and it's also important to mention that i can't find my phone in "adb devices" only in "fastboot devices". I saw some people using the Dload get the stock system back maybe thats an option? i dont know i feel completely lost.
Thanks for the reply
RicardoVs said:
I was using Paranoid android 7.1 i believe but i wiped the phone so there is no Android at all at the moment, i tried updating to the latest twrp since i was getting error 7 trying to flash the stock room, stock recovery just says "failed to get information from the server" every time and for last i did flash it in the right partition, every comand i execute in fastboot it gives me that error and it's also important to mention that i can't find my phone in "adb devices" only in "fastboot devices". I saw some people using the Dload get the stock system back maybe thats an option? i dont know i feel completely lost.
Thanks for the reply
Click to expand...
Click to collapse
Are you able to boot inside TWRP at this moment? And also what is this "latest twrp" that you said that your were flashing. I believe if the TWRP stays loading forever, it means that it does not work for the device.
Make sure your trying to flash this TWRP for nougat:
https://forum.xda-developers.com/honor-8/development/twrp-t3566563/amp/
PremiumBlaze said:
Are you able to boot inside TWRP at this moment? And also what is this "latest twrp" that you said that your were flashing. I believe if the TWRP stays loading forever, it means that it does not work for the device.
Make sure your trying to flash this TWRP for nougat:
https://forum.xda-developers.com/honor-8/development/twrp-t3566563/amp/
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp-3.1.1-1-frd.img
target reported max download size of 471859200 bytes
sending 'recovery' (25188 KB)...
OKAY [ 0.538s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.546s
RicardoVs said:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp-3.1.1-1-frd.img
target reported max download size of 471859200 bytes
sending 'recovery' (25188 KB)...
OKAY [ 0.538s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.546s
Click to expand...
Click to collapse
Have you tried dload yet?
PremiumBlaze said:
Have you tried dload yet?
Click to expand...
Click to collapse
No, what do I need to do? What files should I put in the Dload folder? I never used that method and didn't manage to find information online
RicardoVs said:
No, what do I need to do? What files should I put in the Dload folder? I never used that method and didn't manage to find information online
Click to expand...
Click to collapse
1. Download the update.zip of the stock rom
2. Extract the update.zip of the stock rom
3. Make a folder named "dload" on your sdcard
4. Place the UPDATE.APP on the dload folder
5. Press volume up + volume down + power button until Huawei logo appears
PremiumBlaze said:
1. Download the update.zip of the stock rom
2. Extract the update.zip of the stock rom
3. Make a folder named "dload" on your sdcard
4. Place the UPDATE.APP on the dload folder
5. Press volume up + volume down + power button until Huawei logo appears
Click to expand...
Click to collapse
Ok, i already had the files so i did everything and it didnt work "Software install failed!"
RicardoVs said:
Ok, i already had the files so i did everything and it didnt work "Software install failed!"
Click to expand...
Click to collapse
In the old nougat days, Ive had the same problem. As I always say, dont use twrp on honor 8. They all suck! Anyways, did you tried eRecovery?
Or you should be able to dload a proper firmware in all cases. You just need to find the right package. It fixed me the same problem in the past.
Braiteyy said:
In the old nougat days, Ive had the same problem. As I always say, dont use twrp on honor 8. They all suck! Anyways, did you tried eRecovery?
Or you should be able to dload a proper firmware in all cases. You just need to find the right package. It fixed me the same problem in the past.
Click to expand...
Click to collapse
I got the update.zip for my specific FRD device but still... it failed... im starting to think there is no way so fix this
RicardoVs said:
I got the update.zip for my specific FRD device but still... it failed... im starting to think there is no way so fix this
Click to expand...
Click to collapse
Dont loose hope man! There is a way to fix it every time. Just try another full ota package with same vendor as you are running rn.
Braiteyy said:
Dont loose hope man! There is a way to fix it every time. Just try another full ota package with same vendor as you are running rn.
Click to expand...
Click to collapse
I tried every single file for my FRD-L09C432B405 on Team mt and nothing :/
Do i need to delete everything on the sd card and leave only de dload folder? Maybe i need to format it in an specific format?
No, you dont need to format your sd card. I am gonna help you tomorrow. I am going to sleep rn. See you! need to format it in an specific format?[/QUOTE]
RicardoVs said:
I tried every single file for my FRD-L09C432B405 on Team mt and nothing :/
Do i need to delete everything on the sd card and leave only de dload folder? Maybe i need to format it in an specific format?
Click to expand...
Click to collapse
I realised you said that you updated your TWRP and you cant get in. Did you tried different buttons? I remember some of twrps had volume up + power button and some had volume down and power button and some had vol up and down and power button. Try everything. The frp lock is probably because it somehow disabled oem unlocking by itself. I am gonna try to find a link for latest nougat for you. Good luck man!
EDIT: You should try to relock yor bootloader and unlock it again.
Here are the links: http://update.dbankcdn.com/TDS/data/files/p3/s15/G1774/g1755/v208402/f1/full/update.zip
http://update.dbankcdn.com/TDS/data...l/FRD-L09_hw_eu/update_full_FRD-L09_hw_eu.zip
http://update.dbankcdn.com/TDS/data...02/f1/full/public/update_data_full_public.zip
RicardoVs said:
I tried every single file for my FRD-L09C432B405 on Team mt and nothing :/
Do i need to delete everything on the sd card and leave only de dload folder? Maybe i need to format it in an specific format?
Click to expand...
Click to collapse
Could you try to follow this guide to see if it works:
https://www.stechguide.com/downgrade-honor-8-from-nougat-to-marshmallow/
It may lead your to marshmallow but hopefully it makes the device works. You are going to need the B131 update.zip and flashing rollback package (the site has rollback package download) using dload first before flashing the B131's update.app using dload.
So basically:
1. Flash the rollback package's update.app using dload
2. Flash update.app from B131's update.zip using dload
Once your in marshmallow, you can go back to nougat because there should be at least a twrp for honor 8 marshmallow somewhere around xda
PremiumBlaze said:
Could you try to follow this guide to see if it works:
https://www.stechguide.com/downgrade-honor-8-from-nougat-to-marshmallow/
It may lead your to marshmallow but hopefully it makes the device works. You are going to need the B131 update.zip and flashing rollback package (the site has rollback package download) using dload first before flashing the B131's update.app using dload.
I am really sure that this would work because I tried it before and I was able to go to Marshmallow without any software install fails using dload.
So basically:
1. Flash the rollback package's update.app using dload
2. Flash update.app from B131's update.zip using dload
Once your in marshmallow, you can go back to nougat because there should be at least a twrp for honor 8 marshmallow somewhere around xda
Click to expand...
Click to collapse
The rollback package worked but not the B131, i tried to flash the update.app for my android the B405 as well but nothing...
RicardoVs said:
The rollback package worked but not the B131, i tried to flash the update.app for my android the B405 as well but nothing...
Click to expand...
Click to collapse
I thought this is gonna happen. It happened to me too. I just dont ****in remmember how did I make dload work.
delete

Categories

Resources