Hello,
First of all I want to tell, that I have read all topics about flashing new firmware to Stratos
And also I have unocked bootloader.
My sad story have begun at the moment my Stratos with factory EN 2.3.2.8 firmwary started to hangs.
I could wait for click reaction for a long time, animation was shown with huge delays.
Ones I managed to factory reset Stratos from menu.
But in shirt time it again became in non-working mode.
After reboot the watch I could see only Amazfit logo
But nothing changed with hangs.
So I decided to unlock bootloader and reflash the Stratos with firmware 2.3.2.7
Well, afer flashing the situation didn't change.
I saw only Amazfit logo.
Also I couldn't make adb shell
adb shows device, but adb shell command gives me:
Code:
- exec '/system/bin/sh' failed: Permission denied (13) -
using port=5555
I only managed to unbrick it with The English AmazFit firmware 1.3.0n (nor CN version, nor other firmware worked for my Stratos)
but it appears the Pace firmware.
Once I managed to flash boot from EN 1.3.0n and system from EN 2.3.0.8
It boots, but onlt one power button worked. Touchpad and other buttons - didn't.
After that I flashed misc.img (was found here) and nothing.
So I decided that it's boot issue in my case.
Please help with advice how can I manage to return my Startos back to life.
This may help:
https://forum.xda-developers.com/smartwatch/amazfit/tools-unbrick-huami-amazfit-stratos-t3777380
Pazzl said:
Hello,
First of all I want to tell, that I have read all topics about flashing new firmware to Stratos
And also I have unocked bootloader.
My sad story have begun at the moment my Stratos with factory EN 2.3.2.8 firmwary started to hangs.
I could wait for click reaction for a long time, animation was shown with huge delays.
Ones I managed to factory reset Stratos from menu.
But in shirt time it again became in non-working mode.
After reboot the watch I could see only Amazfit logo
But nothing changed with hangs.
So I decided to unlock bootloader and reflash the Stratos with firmware 2.3.2.7
Well, afer flashing the situation didn't change.
I saw only Amazfit logo.
Also I couldn't make adb shell
adb shows device, but adb shell command gives me:
Code:
- exec '/system/bin/sh' failed: Permission denied (13) -
using port=5555
I only managed to unbrick it with The English AmazFit firmware 1.3.0n (nor CN version, nor other firmware worked for my Stratos)
but it appears the Pace firmware.
Once I managed to flash boot from EN 1.3.0n and system from EN 2.3.0.8
It boots, but onlt one power button worked. Touchpad and other buttons - didn't.
After that I flashed misc.img (was found here) and nothing.
So I decided that it's boot issue in my case.
Please help with advice how can I manage to return my Startos back to life.
Click to expand...
Click to collapse
You flashed a Stock ROM from Amazfit Pace in your Amazfit 2 Stratos, I'm sorry to tell that you probably ruined your watch, as you probably lost your serial number (SN) and locked your bootloader too, and for being now in a stock ROM without root access, I'm afraid you have nothing to do to recover your watch.
You may check your bootloader and SN firstly, and read this restoration thread: https://forum.xda-developers.com/smartwatch/amazfit/guide-restore-null-sn-locked-t3775998
Saratoga79 said:
You flashed a Stock ROM from Amazfit Pace in your Amazfit 2 Stratos, I'm sorry to tell that you probably ruined your watch, as you probably lost your serial number (SN) and locked your bootloader too, and for being now in a stock ROM without root access, I'm afraid you have nothing to do to recover your watch.
You may check your bootloader and SN firstly, and read this restoration thread: https://forum.xda-developers.com/smartwatch/amazfit/guide-restore-null-sn-locked-t3775998
Click to expand...
Click to collapse
Hello,
well, fastboot getvar all shows me correct SN and unlocked bootloader.
And yes, I flashed misc.img with correct values (SN factory, BT and WiFi macs are ok)
And it didn't help.
I can get root access to the device via boot-US-adb-root.img from fastboot mode
I can also access to system partition and mount it from recovery mode.
I several times wipe cache and data.
Also yesterday I managed to flash STRATOSfied 2.0.22.0 and after reboot into recovery it started to update, but hangs almost at the end.
When I mounted system partition I saw that it was only one dir there with app. So update process didn't finish the task.
I don't think that I ruined my watch
lfom said:
This may help:
https://forum.xda-developers.com/smartwatch/amazfit/tools-unbrick-huami-amazfit-stratos-t3777380
Click to expand...
Click to collapse
Hello,
well, it didn't. either full install, either unbrick
Pazzl said:
Hello,
well, fastboot getvar all shows me correct SN and unlocked bootloader.
And yes, I flashed misc.img with correct values (SN factory, BT and WiFi macs are ok)
And it didn't help.
I can get root access to the device via boot-US-adb-root.img from fastboot mode
I can also access to system partition and mount it from recovery mode.
I several times wipe cache and data.
Also yesterday I managed to flash STRATOSfied 2.0.22.0 and after reboot into recovery it started to update, but hangs almost at the end.
When I mounted system partition I saw that it was only one dir there with app. So update process didn't finish the task.
I don't think that I ruined my watch
Click to expand...
Click to collapse
Lucky you
Maybe your system partition is corrupted somehow. You could try maybe flashing the US Stock firmware as your bootloader is unlocked and see if that helps.
Saratoga79 said:
Lucky you
Maybe your system partition is corrupted somehow. You could try maybe flashing the US Stock firmware as your bootloader is unlocked and see if that helps.
Click to expand...
Click to collapse
So you think the issue in the system partition?
Not boot partition?
Could you please tell me how can I unpack img files to check what exactly is in images?
Cause I do think that smth wrong with boot once.
I couldn't mount boot partition under recovery cause it mmc format I think, not ext4
Pazzl said:
So you think the issue in the system partition?
Not boot partition?
Could you please tell me how can I unpack img files to check what exactly is in images?
Cause I do think that smth wrong with boot once.
I couldn't mount boot partition under recovery cause it mmc format I think, not ext4
Click to expand...
Click to collapse
Both boot and recovery use the same format, then need to be unpacked. System.img normally used to flash via dd is a common ext4 partition.
Either way, the correct way t fix it is what Saratoga said: flash a stock ROM (both boot.img and system.img) to boot correctly, and stock recovery if you want OTA. I send a private message, but you didn't reply. Good luck.
lfom said:
Both boot and recovery use the same format, then need to be unpacked. System.img normally used to flash via dd is a common ext4 partition.
Either way, the correct way t fix it is what Saratoga said: flash a stock ROM (both boot.img and system.img) to boot correctly, and stock recovery if you want OTA. I send a private message, but you didn't reply. Good luck.
Click to expand...
Click to collapse
Hello,
I will try again to flash stock boot and system.
The boot partition could be flashed via fastboot flash command or only dd is acceptable?
Pazzl said:
Hello,
I will try again to flash stock boot and system.
The boot partition could be flashed via fastboot flash command or only dd is acceptable?
Click to expand...
Click to collapse
Hello, any update on this? I have the exact same situation you have. Stratos became sluggish, but when factory reset it works back fine, after few days/months its sluggish again until it stucks in amazfit logo only, everything is stock on this point as well as boot loader is locked, I managed to unlock my bootloader via fastboot. Tried most of the unbrick thread here but haven't managed to make it work. Tried stratosfied and it went to recovery where it is updating firmware but stuck at the end. Exactly same situation with you. Hoping I could get information in here, thanks
Edit: Was able to fix it following this -> https://forum.xda-developers.com/smartwatch/amazfit/tutorial-unbrick-huami-amazfit-t3547300
Somehow custom rom, newer stock firmware doesnt work but old 1.3.0n in the thread works yaay!
Related
Hey guys, I think I've bricked my N9. What happened was I rooted it successfully, but then on flashing a custom recovery, I used the wrong image file. Instead of using the flounder image, I mistakenly flashed the volantis one. And then I flashed twrp for flounder. But after that, the recovery could not mount anything and ADB Sideload did not work. After that, I when and restore everything back to stock with factory image, however I cannot boot into system. I am effectively stuck in bootloader, and that's where I am. I tried rooting and flashing twrp recovery, and again, it could not mount and ADB Sideload is not working. I tried everything. Is my N9 done for? Or can someone point me in the right direction and get my N9 back?
I once bricked my lg g2 pretty badly, couldn't use adb or recovery.
I managed to repair it by booting a linux and manually overwrite the partitions with the factoy image.
There is a thread with instructions here on xda in the g2 forum, could work with the nexus to.
nexus 9
DoeBoi said:
Hey guys, I think I've bricked my N9. What happened was I rooted it successfully, but then on flashing a custom recovery, I used the wrong image file. Instead of using the flounder image, I mistakenly flashed the volantis one. And then I flashed twrp for flounder. But after that, the recovery could not mount anything and ADB Sideload did not work. After that, I when and restore everything back to stock with factory image, however I cannot boot into system. I am effectively stuck in bootloader, and that's where I am. I tried rooting and flashing twrp recovery, and again, it could not mount and ADB Sideload is not working. I tried everything. Is my N9 done for? Or can someone point me in the right direction and get my N9 back?
Click to expand...
Click to collapse
just look for the image for your device on recovery. as long as you have fastboot it can be saved. just look for your version flounder custom recovery and it should work
MoooN said:
I once bricked my lg g2 pretty badly, couldn't use adb or recovery.
I managed to repair it by booting a linux and manually overwrite the partitions with the factoy image.
There is a thread with instructions here on xda in the g2 forum, could work with the nexus to.
Click to expand...
Click to collapse
I don't have a Linux system and looking through thread seems too advance for me. I can't relate it to the N9. However, there seems to be something wrong partition, because I can't mount storage.
matt4787 said:
just look for the image for your device on recovery. as long as you have fastboot it can be saved. just look for your version flounder custom recovery and it should work
Click to expand...
Click to collapse
I can flash custom recovery, but I can't push files or adb sideload, therefore I can't do anything in recovery anyway.
Did you try to use the nexus toolkits flying around here?
Maybe they could be of some help..
@DoeBoi you need to flash the factory image. This should help http://forum.xda-developers.com/showthread.php?p=58956577
Sent from my Nexus 5 using XDA Free mobile app
Does the Google Logo flash for a second or so before it goes to bootloader?
nexus 9
Try to get into bootloader by holding power and volume down.
MoooN said:
Did you try to use the nexus toolkits flying around here?
Maybe they could be of some help..
Click to expand...
Click to collapse
I will look in to it, thank you.
jd1639 said:
@DoeBoi you need to flash the factory image. This should help http://forum.xda-developers.com/showthread.php?p=58956577
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I already tried one version of the image, which didn't work, will try to flash the others.
scrosler said:
Does the Google Logo flash for a second or so before it goes to bootloader?
Click to expand...
Click to collapse
restart - sometimes yes and sometimes no, if plug into computer - no, if not plugged - yes,
matt4787 said:
Try to get into bootloader by holding power and volume down.
Click to expand...
Click to collapse
you mean power + volume up, but yes, no problem getting there, also adb is working
thanks for all your help, I will try different factory image and flashing from OTG
The problem is your kernel is not loading or mismatched to the operating system. I have experienced this a lot on HTC devices when I screw something up... I mean "experiment"
You need to flash the boot system and vendor image from the latest factory ROM.
You need to do it manually...
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
Then reboot to recovery and wipe data. Not factory rest but actually wipe all of /data partition.
That should get you back. If not post back results.
If you are not familiar with fastboot then state so and I will help you.
Yes! I got it booting again, thank you everyone for helping. Apparently, the problem was, I think, wiping manually, that is, system, cache, recovery, boot, user data, and vendor didn't erase everything. What did the trick was [fastboot -w], I did this instead of erasing one by one. Thank you so much guys!
DoeBoi said:
Hey guys, I think I've bricked my N9. What happened was I rooted it successfully, but then on flashing a custom recovery, I used the wrong image file. Instead of using the flounder image, I mistakenly flashed the volantis one. And then I flashed twrp for flounder. But after that, the recovery could not mount anything and ADB Sideload did not work. After that, I when and restore everything back to stock with factory image, however I cannot boot into system. I am effectively stuck in bootloader, and that's where I am. I tried rooting and flashing twrp recovery, and again, it could not mount and ADB Sideload is not working. I tried everything. Is my N9 done for? Or can someone point me in the right direction and get my N9 back?
Click to expand...
Click to collapse
First question - Did you flash a bad bootloader? If no, then you cannot have possibly bricked your nexus 9. I do believe this is the ONLY way you could brick a nexus. If you still have access to fastboot mode, you are totally fine. I would recommend flashing the factory images and just starting fresh. Depending on which nexus 9 you have, either the wifi only or LTE variant, you can download the appropriate packages at https://developers.google.com/android/nexus/images . Basically, you need to extract the package into a folder, boot your device into fastboot mode, and run the flashall.bat (windows) or flashall.sh(linux). As long as you have fastboot and ADB properly installed into your $PATH or atleast have fastboot and adb in your working folder, everything should be ok. If you run into any problems, contact me via PM or I can be found on IRC (Network freenode, #android, #cyanogenmod, #android-root). Good luck
bynarie said:
First question - Did you flash a bad bootloader? If no, then you cannot have possibly bricked your nexus 9. I do believe this is the ONLY way you could brick a nexus. If you still have access to fastboot mode, you are totally fine. I would recommend flashing the factory images and just starting fresh. Depending on which nexus 9 you have, either the wifi only or LTE variant, you can download the appropriate packages at https://developers.google.com/android/nexus/images . Basically, you need to extract the package into a folder, boot your device into fastboot mode, and run the flashall.bat (windows) or flashall.sh(linux). As long as you have fastboot and ADB properly installed into your $PATH or atleast have fastboot and adb in your working folder, everything should be ok. If you run into any problems, contact me via PM or I can be found on IRC (Network freenode, #android, #cyanogenmod, #android-root). Good luck
Click to expand...
Click to collapse
Um, he's got it fixed.
Sent from my Nexus 5 using XDA Free mobile app
I too thought I bricked my device and found this thread. Using the recovery from Google I was getting "sending sparse 'system' FAILED (status read failed (Protocol error))" until I used "fastboot -w" like the post above mentioned. Leaving this here in case someone else runs into the problem.
sototallycarl said:
I too thought I bricked my device and found this thread. Using the recovery from Google I was getting "sending sparse 'system' FAILED (status read failed (Protocol error))" until I used "fastboot -w" like the post above mentioned. Leaving this here in case someone else runs into the problem.
Click to expand...
Click to collapse
Thanks for paying it forward.
I have a similar problem my nexus 9 wont turn on and would freeze in the optimizing apps screen after going past the nexus logo but i can get to the fastboot and recovery. But i cannot flash the factory image because my bootloader is locked and i didn't enable developer options prior to the problem. I'm thinking about sideloading the latest ota would that help me ? And is there anyway to unlock bootloader if i can't boot the device?
---------- Post added at 10:10 PM ---------- Previous post was at 10:07 PM ----------
sototallycarl said:
I too thought I bricked my device and found this thread. Using the recovery from Google I was getting "sending sparse 'system' FAILED (status read failed (Protocol error))" until I used "fastboot -w" like the post above mentioned. Leaving this here in case someone else runs into the problem.
Click to expand...
Click to collapse
Can you please explain to me what fastboot w- command means ?
It erases userdata and cache. Often needed if you run into bootloops. But it does wipe your data so backup off your device first.
Bricked N9
Hi everyone, well my problem is that i was trying to flash Android 6.0 but i accidentally execute the flash-all.bat file while i was trying to open it in the note block. It was booting normally but it seems that my N9 was encrypted, so it said that the Unencrypted was incorrect so it forced me to hard reset my tablet. i did this but it was taking like 20 min to erase my file (the android appeared and it was over a message that was "Wiping" -it was in spanish borrando-) so i turn it off and now my tablet is on a bootloop, after it appears the Google logo the 4 dots start to move but then the tablet turn off and repeat that cycle. Apparently i dont have recovery (appears the android laid down with a red triangle with an exclamation mark) and when i try to enter the hard reset the bootloop happens, the same if i try to reboot, i cant activate usb debugging i can only use the fastboot mode, my pc doesnt reconize my N9.
Thanks
PD: Sorry about my english, im from mexico, but i expect i had explained myself.
emi.guego said:
Hi everyone, well my problem is that i was trying to flash Android 6.0 but i accidentally execute the flash-all.bat file while i was trying to open it in the note block. It was booting normally but it seems that my N9 was encrypted, so it said that the Unencrypted was incorrect so it forced me to hard reset my tablet. i did this but it was taking like 20 min to erase my file (the android appeared and it was over a message that was "Wiping" -it was in spanish borrando-) so i turn it off and now my tablet is on a bootloop, after it appears the Google logo the 4 dots start to move but then the tablet turn off and repeat that cycle. Apparently i dont have recovery (appears the android laid down with a red triangle with an exclamation mark) and when i try to enter the hard reset the bootloop happens, the same if i try to reboot, i cant activate usb debugging i can only use the fastboot mode, my pc doesnt reconize my N9.
Thanks
PD: Sorry about my english, im from mexico, but i expect i had explained myself.
Click to expand...
Click to collapse
I had the same problem... I had to manually flash each image through fastboot starting with the recovery img
Sent from my HTC One M9 using XDA Free mobile app
But how can I do it if I can't enable USB debugging?
Enviado desde mi Moto MAXX mediante Tapatalk
I screwed up my phone lol, when I was updating it to oreo, I didn't know that the update.zip file was corrupted.
Now I'm stuck on
Error!
Func NO : 9 (hifi image)
Error NO : 1 (security image failed)
My version was...
STF-L09C185B170
What i tried to install that failed is...
STF-L09C185B361 (8.0.0.361)
I can still go to fastboot with everything unlocked, I can also flash a twrp recovery, but only by typing flash recovery_ramdisk(instead "recovery"), and when I try to do the update method by pressing vol up, vol down, and power, it doesnt take me to the update section, it just show me a crashed screen, then goes back to error message.
I also tried volup and power, I can't seem to go to twrp(I think booting to twrp and flashing zip files can be one of the only ways to fix this). Is there a way to go to twrp recovery using fastboot?
I've also tried flashing extracted files from update.app manually, it doesn't work. Some files can be flashed, while some can't.
Please I'm begging u guys, pls halp :crying:
also I guess the lesson here is: double check if your file is corrupted before installing/flashing
First, what is the way you took triying to update ?
(When done from system UI, official or FF, there is an integrity check of downloaded files.)
It seems you got oreo partition scheme during your failed update.
First see this guide:
https://forum.xda-developers.com/mate-8/general/fastboot-erecovery-recovery-upgrade-mode-t3543441
Try to restore using erecovery. (download and update firmware via wifi)
If not working you could use HWOTA8.
For launching recovery (stock or twrp) from bootloader type "fastboot reboot recovery".
oslo83 said:
First, what is the way you took triying to update ?
(When done from system UI, official or FF, there is an integrity check of downloaded files.)
It seems you got oreo partition scheme during your failed update.
First see this guide:
https://forum.xda-developers.com/mate-8/general/fastboot-erecovery-recovery-upgrade-mode-t3543441
Try to restore using erecovery. (download and update firmware via wifi)
If not working you could use HWOTA8.
For launching recovery (stock or twrp) from bootloader type "fastboot reboot recovery".
Click to expand...
Click to collapse
I downloaded the oreo file using a browser and installed it with HWOTA, everything got inserted into my device, but the update failed and it gave me the error when I reboot. Also I can't get to erecovery or upgrade mode(that's the crashed screen), and "fastboot reboot recovery" doesn't work, it just show me a list of commands(which I assume happens if the command is invalid).
Ok I'll try HWOTA8, but I need to configure it so it recognizes my device, only my adb recognizes it.
Do 'fastboot devices work'?
Try english hwota8.
oslo83 said:
Do 'fastboot devices work'?
Try english hwota8.
Click to expand...
Click to collapse
Nah, I figured it out, I backed up my adb folder and just merged hwota8 with it. Yes, it does work.
Btw how do I fully turn off the device? it just keeps bootlooping if i hold down the volup and power key, maybe this is the reason why I can't get into twrp recovery.
My only hope is that I can flash something on fastboot that will let me go to update mode(or erecovery) or twrp.
Like.. anything, even boot.img fails when I try to flash it. It must be stuck on oreo partition.
Also I did considered dc phoenix, but I don't have the money to pay for an account. Man, why is unbricking not free on huawei devices? That guy prolly made a fortune by now(for holding everyone with unbrick leverage lel), and it's a huge mistake for me to fiddle with a huawei device, it has so many problems with twrp and root.
If anyone can find a way to do unbrick it, like anything, that would be great.
So you didn't manage to use honor9's hwota8 ?
oslo83 said:
So you didn't manage to use honor9's hwota8 ?
Click to expand...
Click to collapse
I used it but it didn't worked, I need to be either booted in the phone's os or inside twrp recovery bec. all of the commands executed by hwota8 are adb shell, not fastboot. Like I said, I only have access to fastboot, but I'll try again tomorrow. This is taking a lot of my time and I'm having panic attacks that I may not be able to fix this lol. Oh yeah, thanks for helping out.
Note: Since Oreo, partitions names have changed ; "recovery" changed to "recovery_ramdisk" now.
Use this command to flash recovery: fastboot flash recovery_ramdisk YourStockOrTwrpRecovery.img
Use oreo stock recovery or oreo twrp.
But I thought with hwotas available for honor 9 you started from bootloader...
oslo83 said:
Note: Since Oreo, partitions names have changed ; "recovery" changed to "recovery_ramdisk" now.
Use this command to flash recovery: fastboot flash recovery_ramdisk YourStockOrTwrpRecovery.img
Use oreo stock recovery or oreo twrp.
But I thought with hwotas available for honor 9 you started from bootloader...
Click to expand...
Click to collapse
I already did that, read the OP. Like I said, I can't boot into any recovery, not twrp not stock, not even upgrade mode, nothing.
As for hwota8, nope, it doesnt start from the bootloader, it's already trying to use the adb shell commands.
Anyway I'm taking all chances, I'm trying to research oreo's partitions names, and I'm also trying to find out how to bypass this message "FAILED (remote: Command not allowed)" bec. it might be the only way I can salvage this phone.
edit: ok im trying hwota8 again, maybe i missed something, and yes it has fastboot, sorry i was rushing but im trying again now, i'll post my progress later
Hi everybody i need your help,
I got an honor 9 STF-L09. I got bricked and I want to install the stock firmware because my phone doesnt on again. I have Twrp installed and unlocked bootloader but when i try to boot into system it says "Func NO: 10 (boot image)".
I tried to flash firmware from thi guide https://forum.xda-developers.com/honor-9/development/firmware-huawei-honor-9-stf-l09-stock-t3696892 but nothing to do.
I tried to flash using twrp but the ionstallation fail everytime.
Is there someone that can help me with a stock firmware or even other firmwares that makes my H9 on againg.
Please help me I'am DESPERATE
Did you take a look here ?
http://droidvendor.com/download-8-0-0-360-c432-official-oreo-for-honor-9-stf-l09/
sorry, I'm not expert on this topic, it's the only help i can give you
What rom did you have before? EMUI 8 or 5.1?
JBolho said:
What rom did you have before? EMUI 8 or 5.1?
Click to expand...
Click to collapse
I had emui 8
leocap33 said:
I had emui 8
Click to expand...
Click to collapse
I will provide you with the files that (hopefully) will bring your device back to life. Just need to upload the first, i'll update this post with the link and instructions, hang on a second.
JBolho said:
I will provide you with the files that (hopefully) will bring your device back to life. Just need to upload the first, i'll update this post with the link and instructions, hang on a second.
Click to expand...
Click to collapse
thank you man
leocap33 said:
thank you man
Click to expand...
Click to collapse
In the link you will find Stock EMUI 8 Ramdisk, Recovery and System, as well as TWRP and a Kernel that fixes the possibility of losing the capacitive buttons. Download them into a folder on the root of your PC (for example C:\Temp)
https://www.dropbox.com/sh/88l72rypm6u1u94/AADtPyvsIFhyBl1mcJ5raTBZa?dl=0
I don't know what caused your boot to disappear, mine disappeared when i tried to unroot it from within SuperSU app (Big Mistake), but let's not be drastic just yet. You need Fastboot and ADB on your PC, turn off your phone, hold Volume - and connect the USB cable from the PC to the device. You should enter Fastboot mode. I hope your device is FRP unlocked as well.
Open a command line and input "fastboot devices" to make sure your device is connected
First let's try restoring Ramdisk, TWRP and Kernel:
Run "fastboot flash ramdisk STF-L09_ramdisk.img", then "fastboot flash recovery_ramdisk stf_twrp_oreo.img" and finally "fastboot flash kernel B360_fix_kernel.img"
After that just run "fastboot reboot" and see if it boots or not... This should take care of your problem, if not, let's go drastic:
Turn off the device and plug it in fastboot mode again onto your PC.
On the command line run "fastboot flash recovery_ramdisk RECOVERY_RAMDISK.img" (this will flash stock recovery), and "fastboot flash system SYSTEM.img" (this will flash your system partition, in small bathes at a time, fresh.)
After that, just "fastboot reboot" and it should boot to your system (and without a factory reset!) If it bootloops for some reason, turn off the device, boot into stock recovery and wipe cache (or do a full factory reset, but that should not be necessary i think...)
Hope all this helps!
JBolho said:
In the link you will find Stock EMUI 8 Ramdisk, Recovery and System, as well as TWRP and a Kernel that fixes the possibility of losing the capacitive buttons. Download them into a folder on the root of your PC (for example C:\Temp)
https://www.dropbox.com/sh/88l72rypm6u1u94/AADtPyvsIFhyBl1mcJ5raTBZa?dl=0
I don't know what caused your boot to disappear, mine disappeared when i tried to unroot it from within SuperSU app (Big Mistake), but let's not be drastic just yet. You need Fastboot and ADB on your PC, turn off your phone, hold Volume - and connect the USB cable from the PC to the device. You should enter Fastboot mode. I hope your device is FRP unlocked as well.
Open a command line and input "fastboot devices" to make sure your device is connected
First let's try restoring Ramdisk, TWRP and Kernel:
Run "fastboot flash ramdisk STF-L09_ramdisk.img", then "fastboot flash recovery_ramdisk stf_twrp_oreo.img" and finally "fastboot flash kernel B360_fix_kernel.img"
After that just run "fastboot reboot" and see if it boots or not... This should take care of your problem, if not, let's go drastic:
Turn off the device and plug it in fastboot mode again onto your PC.
On the command line run "fastboot flash recovery_ramdisk RECOVERY_RAMDISK.img" (this will flash stock recovery), and "fastboot flash system SYSTEM.img" (this will flash your system partition, in small bathes at a time, fresh.)
After that, just "fastboot reboot" and it should boot to your system (and without a factory reset!) If it bootloops for some reason, turn off the device, boot into stock recovery and wipe cache (or do a full factory reset, but that should not be necessary i think...)
Hope all this helps!
Click to expand...
Click to collapse
thank you a lot, u give me hope. When I return home I'll try everything
JBolho said:
In the link you will find Stock EMUI 8 Ramdisk, Recovery and System, as well as TWRP and a Kernel that fixes the possibility of losing the capacitive buttons. Download them into a folder on the root of your PC (for example C:\Temp)
https://www.dropbox.com/sh/88l72rypm6u1u94/AADtPyvsIFhyBl1mcJ5raTBZa?dl=0
I don't know what caused your boot to disappear, mine disappeared when i tried to unroot it from within SuperSU app (Big Mistake), but let's not be drastic just yet. You need Fastboot and ADB on your PC, turn off your phone, hold Volume - and connect the USB cable from the PC to the device. You should enter Fastboot mode. I hope your device is FRP unlocked as well.
Open a command line and input "fastboot devices" to make sure your device is connected
First let's try restoring Ramdisk, TWRP and Kernel:
Run "fastboot flash ramdisk STF-L09_ramdisk.img", then "fastboot flash recovery_ramdisk stf_twrp_oreo.img" and finally "fastboot flash kernel B360_fix_kernel.img"
After that just run "fastboot reboot" and see if it boots or not... This should take care of your problem, if not, let's go drastic:
Turn off the device and plug it in fastboot mode again onto your PC.
On the command line run "fastboot flash recovery_ramdisk RECOVERY_RAMDISK.img" (this will flash stock recovery), and "fastboot flash system SYSTEM.img" (this will flash your system partition, in small bathes at a time, fresh.)
After that, just "fastboot reboot" and it should boot to your system (and without a factory reset!) If it bootloops for some reason, turn off the device, boot into stock recovery and wipe cache (or do a full factory reset, but that should not be necessary i think...)
Hope all this helps!
Click to expand...
Click to collapse
Hi sir I tried, everything flashes ok but when I reboot it continue bootloops until it enter into erecovery. I tried to wipe data but when I press the button to wipe cache after it displays a red '!' into the circle and the same for the wiping data.
sorry for my English, how can I solve ..? FRP was written "FRP unlock"
leocap33 said:
Hi sir I tried, everything flashes ok but when I reboot it continue bootloops until it enter into erecovery. I tried to wipe data but when I press the button to wipe cache after it displays a red '!' into the circle and the same for the wiping data.
sorry for my English, how can I solve ..? FRP was written "FRP unlock"
Click to expand...
Click to collapse
Everything flashes ok, no errors? What did you flash? Everything?
eRecovery is to rescue the device, that won't work with Oreo (at least not for me). The stock recovery you enter it by keeping the Vol + pressed and power up the device (just as TWRP), you can enter it? And it gives error when wiping the cache?
JBolho said:
Everything flashes ok, no errors? What did you flash? Everything?
eRecovery is to rescue the device, that won't work with Oreo (at least not for me). The stock recovery you enter it by keeping the Vol + pressed and power up the device (just as TWRP), you can enter it? And it gives error when wiping the cache?
Click to expand...
Click to collapse
yes it gives me an error while I wipe cache or factory data. I enter normally into recovery with vol+.
leocap33 said:
yes it gives me an error while I wipe cache or factory data. I enter normally into recovery with vol+.
Click to expand...
Click to collapse
What ROM exactly were you using? OldDroid's B360? Or some other?
I were using the stock emui8 I don't know the build number because I can't get it. My region is italy
leocap33 said:
I were using the stock emui8 I don't know the build number because I can't get it. My region is italy
Click to expand...
Click to collapse
The only explanation i see is that the EMUI8 you were using has something different from the one in OldDroid's thread... On mine i did exactly what i told you, those files are the ones i used on mine as well.
Right now you have everything stock right? Can you try to flash one of the Treble Roms? Either AOSP or RR-O?
You just have to download them (they're a system.img file) and run the "fastboot flash system system.img" command, go to recovery and factory reset. Your device should boot.
If everything fails, the only hope i see if to go to OldDroid's thread - https://forum.xda-developers.com/honor-9/how-to/stf-l09c432-how-to-install-oreo-h9-t3707729 and download the files, and follow the instructions on the OP to rollback to Nougat.
sonneper said:
Did you take a look here ?
http://droidvendor.com/download-8-0-0-360-c432-official-oreo-for-honor-9-stf-l09/
sorry, I'm not expert on this topic, it's the only help i can give you
Click to expand...
Click to collapse
I think the link you probided is a fake bull$hiting guide :
1) it states european C432 but provided two of the three files of a russian C10 firmware.
2) almost sure. the file provided won't flash the dload way as stated in guide.
leocap33 said:
Hi everybody I got an honor 9 STF-L09, my region is italy. I got bricked and I want to install the stock firmware because my phone doesnt on again. I have Twrp installed and unlocked bootloader but when i try to boot into system it says "Func NO: 10 (boot image)".
I tried to flash firmware from thi guide https://forum.xda-developers.com/honor-9/development/firmware-huawei-honor-9-stf-l09-stock-t3696892 but nothing to do.
I tried to flash using twrp but the ionstallation fail everytime.
Is there someone that can help me with a stock firmware or even other firmwares that makes my H9 on againg.
Please help me I'am DESPERATE
Click to expand...
Click to collapse
OK, so you were on oreo, and now the nougat's service repair dload firmware are not working.
I'll start by asking:
-how do you get bricked, what did you do just before ?
Try this tool for honor 9:
https://forum.xda-developers.com/newreply.php?do=newreply&p=75084955
(xda link to russian tool)
https://forum.xda-developers.com/newreply.php?do=newreply&p=75661658
(xda link to english translated scripts)
http://4pda.ru/forum/index.php?showtopic=833645&st=2400#entry69940847
(pda link to russian tool)
Same here, I just have access to eRecovery and fastboot mode
I was on the last version (oreo) and I wanted root my phone so I have unlock bootloader and install twrp but after twrp install in the wipe my internal stockage was empty and when I wanted install supersu I have some error like failed to mount: data, failed to mount: cache, ect..
but I still had access to my phone
Except that I had to go through the eRecovery every time so I tried to look at the side of my errors mount and I tried unbrick with the software Huawei Multi Tool and images of a rom stock publish on the forum except that I had even more access to my phone but I no longer have the errors mount.. With Huawei Multi Tool I have try the recovery option but nothing, now I don't know what make
Hi everyone I tried all the tools given into this thread but no success, it seems like a big lost challenge
Tell us more..
so you were on oreo or nougat before brick ?
and now the nougat's service repair dload firmware are not working ?
how do you get bricked, what did you do just before ?
Yeah never see a sht like that, I guess we have to send our phones to a huawei repair center..
Ok you were on oreo emui8.
MANUALLY INSTALLING FULL NOUGAT 7.11 FIRMWARE 2018/03/15(security_patch 2018-02-05) (RECOVERY, BOOT, SYSTEM) Even If Its Soft Bricked Because You Messed Up Somewhere. Files Here Are For Asus Zenfone 3 Zoom ZE553KL Z01HD WW Sku .
Its The Last Nougat Update Before Oreo Was Released.
MORE FIRWARES HERE
Story Time:
As I Remember It.....Condensed Version, This Was Over A Few Days Of Trial And Error, Mainly Because Adb SideLoad Refused To Flash Asus's Stock Firmware Zip Files.
I Messed Up My Friends Asus Zenfone 3 Zoom, ZE553KL.
He Bought Used, He Quickly Updated To Oreo From Within The Phones Update But Was Having Missed Texts And Slow Lte(4g) Speeds, He Wasnt Sure If It Happened On Nougat Which The Phone Was On Originally.
Downgraded To 6.01, Installed Twrp, Magisk, Still Having Same Issues, Flashing An Update Zip W/a Modded Updater Script Via Twrp Caused A Soft Bricked Phone, It Never Completed The Flash, Twrp Backup Didnt Work, Factory Reset A No Go, Couldn't Manually Flash Stock Rom As Adb Sideload Always Gave Errors, Fastboot System images Didnt Help For One Reason Or Another, Phone Was Just Bootlooping Back To The Unlocked Bootloader Menu.
Down Loaded Alot Of Stuff, Read Countless Pages, And Somehow Got The Right Firmware Files(recovery, boot, system img files) That Was Flashable Via Fastboot Extracted From A Zip, My Fix Is Below. These Are Not My Files But I Cant Remember Where I Got Them From As I Dl-ed Alot Of Stuff Trying To Get This Phone To A Running State. No I Havent Tried Oreo Yet, He Has His Phone Back Now And Not Sure When He'll Let Me Play With It Again, Lol.
UPDATE TO THIS STORY
HOWTO FLASH
PREREQUISITES:
Make A Nandroid Backup
If Bootable Remove/Signout Of Google Account
(Might Work With Locked Bootloader, IDK)
Ze553kl(Zenfone3 Zoom) Phone With Unlocked Bootloader(used unlocker apk from asus website when phone was in running state)
Unlocking Bootloader App Available From Asus - was for upto nougat 7.11
Usb Asus Drivers
Usb Debugging Enabled On Phone, Maybe Not But Wont Hurt To Try
Adb Fastboot Program(Included)
Recovery, Boot, And System Img Files Of Nougat 7.11(Included)
Computer Running Windows
Usb Data Cable For Phone
ON PHONE-
If Bootable Enable Usb Debugging, Uncheck Verify Apps Via Usb, Install From Unknown Sources, Remove Google Account
Backup Internal Sdcard - Most Def
Remove Sdcard, Just In Case
Put Phone Into Fast Boot Mode- Unplugged, Phone Powered Off - Vol Up + Power Button Pressed, Hold Both Until Screen Comes On.
Plug Usb In Cable To Phone From Pc.
ON COMPUTER-
From The Download Section Below Dl ADB_FASTBOOT_1.4.1.ZIP File And Extract It Into A New Empty Folder.
Download And Copy The Three .Img Files From The Download Section Below Into This New Adb Folder
HOW TO RUN ADB VIA COMMAND PROMPT? -
From Within Adb-fastboot Folder You Created, Nothing Selected, Hold Down The Shift Key Then Use The Right Mouse Button To Click In Empty Space In The Adb-fastboot Folder, Select "Open Command Window Here" From The Menu That Pops Up.
From Within Command Prompt Type-
Adb Devices
It Should Output A Device With A String Of Letters And Numbers, Thats Your Phone.
Next Steps Will Install Nougat 7.11 And Consequently Wipe Your Phone
Run These 5 "fastboot" Commands One At A Time.
When Each Step Is Completed Run The Next Command, You Can Copy And Paste These Five (5) Fastboot Commands Into The Command Prompt Window
----------------------------------------------------------------------
1.
Code:
fastboot flash recovery recovery-zoom-7.11.img
2.
Code:
fastboot flash boot boot-zoom-7.11.img
3.
this one @ ~4gb will take awhile to initialize and complete, patience needed
CAN REDO THIS SYSTEM FLASH NOW TO MAKE SURE IT "STICKS"
Code:
fastboot flash system system-zoom-7.11.img
4.
wipes internal sdcard
Code:
fastboot format userdata
5.
Code:
fastboot reboot
-------------------------------------------------------------------------------------------
if you were successfull it will boot into 7.11, takes about 3-5 mins to boot.
IF DID NOT FLASH PROPERLY OR ODD BEHAVIOR AFTER REBOOT THEN REDO STEPS AGAIN....ELSE KEEP READING!
------------------------------------------------------------------------
IF STILL BRICKED OR ODD BEHAVIOR BUT CAN BOOT TO BOOTLOADER/FASTBOOT THEN DO THESE COMMANDS WHEN IN FASTBOOT MODE
Code:
fastboot erase system
fastboot erase recovery
fastboot erase boot
fastboot erase userdata
fastboot -w
fastboot erase splash
fastboot erase cache
THEN RE-BOOT BACK INTO BOOTLOADER AND DO THE FLASH FOR 7.11 FIRMWARE
STILL HAVING ISSUES, RESTORE USING TECH FW THAT REFLASHES ALL MDMS, RADIOS, DRIVERS ETC FROM HERE
[FW] 7.1.1 & 6.0.1 Service Tech Firmwares - Debrick - Upgrade - Downgrade
- -------------------------------------------------------------------------------------
disclaimer im not responsible for yours or anyone elses devices, do at your own risk
DOWNLOADS
PHONE FILES ARE FROM A Asus Zenfone 3 Zoom ZE553KL WW SKU FIRMWARE Version WW-71.60.139.30 2018/03/15
RECOVERY-ZOOM-7.11.IMG
md5 03d8358e1341a73b5a492c12e3dbe39e
BOOT-ZOOM-7.11.IMG
md5 1ad55f9852d56b79a95654173af5649a
SYSTEM-ZOOM-7.11.IMG
md5 7217f778701c988271739ab18fb0fb30
ADB_FASTBOOT_1.4.1.ZIP
..
Thanks for the information...
I can provide you latest system,boot, recovery.img files if you want...
Do you know how to make raw firmware?? Because that could come handy for hard bricked phones.
Deleted. Double post
Naman Vashishth said:
Thanks for the information...
I can provide you latest system,boot, recovery.img files if you want...
Do you know how to make raw firmware?? Because that could come handy for hard bricked phones.
Click to expand...
Click to collapse
What do u mean by raw. In what format is it in.
I've converted oreo stock firmware .dat files to .img files but I can't test them as I don't have the phone. My friend seems happy on nougat and I don't think he'll let me flash it on his phone.
I haven't tried dl-ing official stock and seeing if phone will see it as an update to manually self install via nougat recovery or maybe to try adb sideload again.
Naman Vashishth said:
I can provide you latest system,boot, recovery.img files if you want...
Click to expand...
Click to collapse
Please do - I could sure use them.
Work very well !
ciao
God bless you! You made my quite dead phone, live again!
Thank you
I can't update to Oreo via ota... do you know why?
the op here. lol, my friend dropped the phone and now its dead screen, no display/no touch but phone still works.
he doesnt want to get a screen for it as it will cost almost as much as he paid for it.......so its mine now.
been flashing stuff to it, gave it a very hard soft brick, still dealing with that.
my goal was to run it remotely but get adb/usb debugging enabled and get pc trusted by phone. i thought he wanted to sell it as is but decided to give to me to do whatever i want to it
got out of the hard soft brick, installed twrp, use twrp cli, twrp backups and restore, rooted w/magisk, installed 6.0.1 (fluked it), 7.11 using my method above with the extra erase commands, removed frp, got adb /usb debugging enabled and device adb authorized by hacking , got vysor, a remote control mirroring app running, all without a working screen.
i'll write up a tut for any1 else that needs help. fyi, weak screen if dropped even short distance, but he had no cover, but pretty to hard to brick it, imo, ymmv
So can i downgrade my phone from android 8 to 7.1.1 following this process.
kingairtel08 said:
So can i downgrade my phone from android 8 to 7.1.1 following this process.
Click to expand...
Click to collapse
yes, i went from 8.0 to 7.11 then to 6.01
more fw here https://forum.xda-developers.com/ze...fw-7-11-6-0-1-service-tech-firmwares-t3850000
Bro i am on 8.0 and want to unlock bootloader and root it n enable cam2api in it, as unlocker nt working in android 8.0 so i want to back to 7.1.1. thank u bro,i will try it tonight.
Bro installed successfully 7.1.1 but microphone sound stopped.when calling cant hear anything.what to do ?unlock tool not working on it.
kingairtel08 said:
Bro installed successfully 7.1.1 but microphone sound stopped.when calling cant hear anything.what to do ?unlock tool not working on it.
Click to expand...
Click to collapse
after flashing did u, in stock recovery, do a factory reset and wipe caches aka wipe user data in fastboot.
else do a complete wipe as outlined in op
yes bro i m on stock recovery ,did wipe cache etc.
kingairtel08 said:
yes bro i m on stock recovery ,did wipe cache etc.
Click to expand...
Click to collapse
does etc mean factory reset?
did u do the extra procedure to completely erase everything as posted in op in the section of when still having issues
yes bro. i followed all steps .
kingairtel08 said:
yes bro.
Click to expand...
Click to collapse
yes to which
this?
fastboot erase system
fastboot erase recovery
fastboot erase boot
fastboot erase userdata
fastboot -w
fastboot erase splash
fastboot erase cache
if yes then do a full restore of radio, mdm etc from here using method 1 or 2
https://forum.xda-developers.com/att-s7-edge/how-to/fw-7-11-6-0-1-service-tech-firmwares-t3850000
i did all this steps then flash firmware img.
kingairtel08 said:
i did all this steps then flash firmware img.
Click to expand...
Click to collapse
which method did u use from the link i posted
bro i dnt have the 7.1..1 zip file ,i used ur 7.1.1.img file,used method 2.
i will try once again ,wil reply within 2hours.
bro i want to unlock my phone whats why i downgrade,but after downgrading checked official unlock tool gives the same network error that gives on android 8.0.is there any way to unlock it on this 7.1.1 firmware?
I was using Corvus OS (Android 10). After updating few apps on play store, one of them was maybe android framework related my phone stopped responding and got black screen errors. (I think a system UI crash). So i tried rebooting, got stuck on boot animation. when i went back to orangefox recovery, the phone was simply not responding to any touch even though i could see the files on my phone (orange fox homescreen). Please help ASAP. Thank You.
If someone is actually listening, i ended up clearing everything, installed new recovery, no luck. and sideloading rom returns with "error closed"
I really need some help guys. Please respond.
Sp_3ctr_3 said:
If someone is actually listening, i ended up clearing everything, installed new recovery, no luck. and sideloading rom returns with "error closed"
I really need some help guys. Please respond.
Click to expand...
Click to collapse
Did you format the data partition?
DarthJabba9 said:
Did you format the data partition?
Click to expand...
Click to collapse
#To format system partition
fastboot format system
#To format boot partition
fastboot format boot
#To format cache partition
fastboot format cache
#To format user data partition
fastboot format userdata
#To format recovery partition
fastboot format recovery
did all of these. thanks for responding almost lost all hopes.
DarthJabba9 said:
Did you format the data partition?
Click to expand...
Click to collapse
i managed to install twrp since i could only file .img of it. while trying to install my os using adb shell twrp sideload, the phone just disconnects when it starts installing vendor files after installing data ones.
Also, the adb shell returns Total Xfer 1.00x
Sp_3ctr_3 said:
i managed to install twrp since i could only file .img of it. while trying to install my os using adb shell twrp sideload, the phone just disconnects when it starts installing vendor files after installing data ones.
Also, the adb shell returns Total Xfer 1.00x
Click to expand...
Click to collapse
Yep, your system is well and truly messed up. Your best bet is to download a fastboot MIUI ROM and flash it with the Mi Flash tool. Just make sure that you don't accidentally lock your boot loader again (hint - after unpacking the fastboot ROM, first delete all .bat and .sh files with "lock" in their names before trying anything with Mi Flash).
https://play.google.com/store/apps/details?id=com.google.android.webview&hl=en_IN
I think this was the app that i update and later caused the crashes.
DarthJabba9 said:
Yep, your system is well and truly messed up. Your best bet is to download a fastboot MIUI ROM and flash it with the Mi Flash tool. Just make sure that you don't accidentally lock your boot loader again (hint - after unpacking the fastboot ROM, first delete all .bat and .sh files with "lock" in their names before trying anything with Mi Flash).
Click to expand...
Click to collapse
Alright, i will try that and respond. thanks for the reply.
DarthJabba9 said:
Yep, your system is well and truly messed up. Your best bet is to download a fastboot MIUI ROM and flash it with the Mi Flash tool. Just make sure that you don't accidentally lock your boot loader again (hint - after unpacking the fastboot ROM, first delete all .bat and .sh files with "lock" in their names before trying anything with Mi Flash).
Click to expand...
Click to collapse
Did this, succesfully flashed with Bootloader intact. Still touch is not responsive, all i can see is a black screen with "This Device is Locked, for security reasons you need to enter the password to verify the device" but i cant select any option since it wont respond to touch.
DarthJabba9 said:
Yep, your system is well and truly messed up. Your best bet is to download a fastboot MIUI ROM and flash it with the Mi Flash tool. Just make sure that you don't accidentally lock your boot loader again (hint - after unpacking the fastboot ROM, first delete all .bat and .sh files with "lock" in their names before trying anything with Mi Flash).
Click to expand...
Click to collapse
Woohoo thank you, my phone is working again t. Although i had to reinstall mi flash tool with bootloader back to off or locked, but atleast now i have a working phone. It seems during login screens sometimes the scree still remains unresponsive, but gets back to normal after 4-5 lock unlock screen routine. I will miss using root and other customization, but i guess it is what it is. Thanks again.
Have a nice day.
Sp_3ctr_3 said:
Woohoo thank you, my phone is working again t. Although i had to reinstall mi flash tool with bootloader back to off or locked, but atleast now i have a working phone. It seems during login screens sometimes the scree still remains unresponsive, but gets back to normal after 4-5 lock unlock screen routine. I will miss using root and other customization, but i guess it is what it is. Thanks again.
Have a nice day.
Click to expand...
Click to collapse
It is good that you have your device back! With regard to the bootloader, you can always go through the unlock procedure again.
PS: updating something from the Play Store should not cause a problem like this. It looks like corruption of the firmware, and/or the persist partition. Flashing a fastboot ROM via Mi Flash (the "flash all" option) should have solved the problem completely. If it didn't, then this might actually be a sign of impending hardware failure, rather than a mere corruption of partitions.
Which version of MIUI did you install?