[Q] HUAWEI Ascend Y300: Flash Recovery with a Locked Bootloader - Android Q&A, Help & Troubleshooting

Are there other ways to flash a recovery with a locked bootloader?
My Problems:
I can't flash my stock recovery through fastboot with a locked bootloader.
I can't boot into my recovery because my current recovery is TWRP 2.5.0.1 and I have a locked bootloader.
I can't unlock my bootloader because I have used an IMEI Hack Tool and set my IMEI to 0 (I guess).
I can't boot into my ROM because I used an IMEI Hack Tool.
I can't Force Upgrade too (Vol Up + Down + Power). It only shows a pink/purple screen.
Solutions:
I can only flash a recovery with an unlocked bootloader.
I can only boot into a recovery with an unlocked bootloader (except for stock).
I can only unlock bootloader if my IMEI has restored.
I can only restore my IMEI if I can boot into my ROM.
I can only boot into my ROM if I have a stock recovery.
I can only Force Upgrade if I have restored my IMEI.
If I could only restore my IMEI through fastboot, that would be great!
So, please help!

You cant restore stock recovery ?
You cant enter to trwp ?
You cant restore IMEI cuz rom bootloop ?
You cant force flash stock firmware cuz fastboot is pink ?
I also "zero" my imei many times to flash stock firmware, but i allways can enter trwp and restore buckup or flash rom in zip

OmenHTX said:
You cant restore stock recovery ?
You cant enter to trwp ?
You cant restore IMEI cuz rom bootloop ?
You cant force flash stock firmware cuz fastboot is pink ?
I also "zero" my imei many times to flash stock firmware, but i allways can enter trwp and restore buckup or flash rom in zip
Click to expand...
Click to collapse
I can force upgrade now since i formatted my sd card. But the force upgrade fails at step 2/2.

.vonpatrick. said:
I can force upgrade now since i formatted my sd card. But the force upgrade fails at step 2/2.
Click to expand...
Click to collapse
If upgrade fail as step 2/2 your IMEI its not "zero" cuz IMEI block upgrading firmware from branded to nonbranded

OmenHTX said:
If upgrade fail as step 2/2 your IMEI its not "zero" cuz IMEI block upgrading firmware from branded to nonbranded
Click to expand...
Click to collapse
If my imei is not zero, then why can't i boot my phone?
And why can't i unlock my bootloader with my unlock code?

.vonpatrick. said:
If my imei is not zero, then why can't i boot my phone?
And why can't i unlock my bootloader with my unlock code?
Click to expand...
Click to collapse
OK, lest start from beggining
1.You must unlock bootloader by code ( first run check Lock / Unlock status ) (fastboot mod)
2. Flash TRWP (fastboot mod)
3. Flash SuperSU or Superuser zip (trwp)
4. Backup IMEI on running rom
5. Hack IMEI on running rom
6. Update phone by forceupdate flash update.app (rom in root of sd card > folder dload > update.app)
7. Run stock rom , lest install, shut down phone
8. Run TRWP to install SuperSU/Superuser zip
8. Restore IMEI (on working rom)
9. Go to TRWP and Wipe dalvik cache
10. Now you have working newest stock rom with root
So :
1. You cant have trwp in lockedbootloader
2. If update fail on 2/2 IMEI is not "zero"
3. Pink LCD on "update mod" = no rom in sd card
Next :
Hold Vol Down + Vol Up + Power to forceupdate firmware mod
Hold Vol Up + Power to run TRWP or stock recovery ( hold about 5s)
Hold Vol Down + Power for fastboot mod (5s-10s)
If you now have locked bootloader , with stock recovery, and force update fail, you cant unlock bootloader and flash trwp > Last hope is in "oryginal" rom, your IMEI will not block it.

OmenHTX said:
OK, lest start from beggining
1.You must unlock bootloader by code ( first run check Lock / Unlock status ) (fastboot mod)
2. Flash TRWP (fastboot mod)
3. Flash SuperSU or Superuser zip (trwp)
4. Backup IMEI on running rom
5. Hack IMEI on running rom
6. Update phone by forceupdate flash update.app (rom in root of sd card > folder dload > update.app)
7. Run stock rom , lest install, shut down phone
8. Run TRWP to install SuperSU/Superuser zip
8. Restore IMEI (on working rom)
9. Go to TRWP and Wipe dalvik cache
10. Now you have working newest stock rom with root
So :
1. You cant have trwp in lockedbootloader
2. If update fail on 2/2 IMEI is not "zero"
3. Pink LCD on "update mod" = no rom in sd card
Next :
Hold Vol Down + Vol Up + Power to forceupdate firmware mod
Hold Vol Up + Power to run TRWP or stock recovery ( hold about 5s)
Hold Vol Down + Power for fastboot mod (5s-10s)
If you now have locked bootloader , with stock recovery, and force update fail, you cant unlock bootloader and flash trwp > Last hope is in "oryginal" rom, your IMEI will not block it.
Click to expand...
Click to collapse
Wait, let me put this in summary:
1.
- I have a locked bootloader.
- I can't unlock the bootloader because it says "recovery image verify failed".
- It can only mean one thing: my IMEI must have changed.
2.
- I have a TWRP recovery.
- At first, my original recovery was the stock when I have a locked bootloader.
- Then I flashed the TWRP recovery even if I have a locked bootloader and didn't warned me. (Shoudn't it be accepted to be flashed since I have a locked bootloader).
- In my experience, if I have a stock recovery when I'll hack my IMEI, it will format my cache and data and let me boot into my phone.
- If I have a TWRP recovery when I'll hack my IMEI, it will only redirect me to the TWRP menu.
3.
- I can access Force Upgrade.
- But it doesn't show any text. (For example: it doesn't show if it is unpacking or installing, only a bar.)
- When I access Force Upgrade, the loading stops at 1/4 of the bar. (So I'm not really sure if it failed at step 2/2.)
So my questions are:
1. Why can't I unlock my bootloader with my original IMEI's unlock code if my IMEI is not "zero"?
2. Why is it when I Force Upgrade, it doesn't show any text?
3. Why did fastboot accepted the TWRP recovery being flashed when my bootloader was locked?
And, what do you mean by "original"? Do you mean the B182 firmware upgrade, not the B175?

After hacking IMEI you cant have stock recovery, cuz you need root for shell script. So its not making "auto wipe" to change OEM info.
TRWP should not be installed on lockbootloader, but i dont make it ...
So , do you have working trwp or not ?
Oryginal firmware ... version when you get with phone, like my Y300-0100 branded T-Mobile PL B167

OmenHTX said:
After hacking IMEI you cant have stock recovery, cuz you need root for shell script. So its not making "auto wipe" to change OEM info.
TRWP should not be installed on lockbootloader, but i dont make it ...
So , do you have working trwp or not ?
Oryginal firmware ... version when you get with phone, like my Y300-0100 branded T-Mobile PL B167
Click to expand...
Click to collapse
I am sure i have twrp.
If i have a stock recovery, i would be able to boot into recovery.
Based in my experience:
1. To hack the imei, you must first root your phone.
2.a. Next, the phone will reboot, but it won't boot into system.
2.b. Fastboot, force upgrade, and recovery is still accessible.
3.a. If you have a twrp recovery when you hacked the imei and rebooted, it will redirect you to the twrp menu.
3.b. If you tried to restore from twrp recovery, it still won't reboot into system.
3.c. If you have a stock recovery, it will directly boot into stock recovery and format your cache and data and reboot to system (still leaves your imei to zero)
4. If you go to force upgrade, you can flash any official roms (leaves your imei to zero)
5. After you have flashed a rom or was redirected to stock recovery, your phone will reboot.
6.a. Then root your phone and restore imei then your phone will reboot.
6.b. If you have a stock recovery, it will wipe your cache and data.
6.c. If you have a twrp recovery, it will redirect you to the twrp menu (you can manually reboot into system)
Am i right?
And where can i get the original rom for my b182? There's no local huawei store here.

.vonpatrick. said:
I am sure i have twrp.
If i have a stock recovery, i would be able to boot into recovery.
Click to expand...
Click to collapse
So why you dont run TRWP and flash any rom in zip ?

OmenHTX said:
So why you dont run TRWP and flash any rom in zip ?
Click to expand...
Click to collapse
Twrp is not accessible if you have a locked bootloader.

bricked
I have a big problem. My Ascend y300 started to work strange yesterday, my PC didnt see the internal sd nor the external SD correctly. Today I restarted it and now I get blue screen when I start it. I had TWRP installed, but when I try to access it, it gives blue screen aswell. Any solutions?

gery0518 said:
I have a big problem. My Ascend y300 started to work strange yesterday, my PC didnt see the internal sd nor the external SD correctly. Today I restarted it and now I get blue screen when I start it. I had TWRP installed, but when I try to access it, it gives blue screen aswell. Any solutions?
Click to expand...
Click to collapse
Try this through fastboot:
fastboot erase recovery
fastboot flash recovery <path to recovery.img>

.vonpatrick. said:
Try this through fastboot:
fastboot erase recovery
fastboot flash recovery <path to recovery.img>
Click to expand...
Click to collapse
My problem is a little bit more complex unfortunately. I tried what you said. When I push the buttons to enter fastboot, my phone dont freez at splashscreen and I get bluescreen. When I connect it to my PC my PC recognizes it though, BUT ADB cant see it. I reinstalled the drivers any times, without success.

gery0518 said:
My problem is a little bit more complex unfortunately. I tried what you said. When I push the buttons to enter fastboot, my phone dont freez at splashscreen and I get bluescreen. When I connect it to my PC my PC recognizes it though, BUT ADB cant see it. I reinstalled the drivers any times, without success.
Click to expand...
Click to collapse
What did you do anyway why it got the blue screen?

.vonpatrick. said:
What did you do anyway why it got the blue screen?
Click to expand...
Click to collapse
That is the most strange part of the story. I totally did nothing. I opened bootloader, installed twrp, rooted it, installed init.d support, installed a ramscript. The phone worked totally fine until yesterday. I did a restart yesterday and bumm, bluescreen. And I did nothing before this happened. Srsly, no problems detected, it came from nothing...

gery0518 said:
That is the most strange part of the story. I totally did nothing. I opened bootloader, installed twrp, rooted it, installed init.d support, installed a ramscript. The phone worked totally fine until yesterday. I did a restart yesterday and bumm, bluescreen. And I did nothing before this happened. Srsly, no problems detected, it came from nothing...
Click to expand...
Click to collapse
Can't you really boot into fastboot (Power + up)?
Hold it for like 10 seconds.
If it still shows blue screen, try connecting it to pc, maybe it'll read it.
Then erase recovery and flash twrp.
Wipe everything and restore a backup you made.

.vonpatrick. said:
Can't you really boot into fastboot (Power + up)?
Hold it for like 10 seconds.
If it still shows blue screen, try connecting it to pc, maybe it'll read it.
Then erase recovery and flash twrp.
Wipe everything and restore a backup you made.
Click to expand...
Click to collapse
Well, my problem is, that despite of the blue screen, fastboot seems to work. My pc sees my device, BUT ADB refuses to see it, and I dont know why. I will try it from win xp under virtualbox now.

hi Gery
How do you manage to get the phone into fastboot mode?
my y300 also enters blue screen everytime now. I try to press voldown + power for like 10 seconds, yet the fastboot command is not working.

gery0518 said:
Well, my problem is, that despite of the blue screen, fastboot seems to work. My pc sees my device, BUT ADB refuses to see it, and I dont know why. I will try it from win xp under virtualbox now.
Click to expand...
Click to collapse
Well, that's perfect! If the PC can read the device from fastboot, you can erase the recovery and flash the twrp and restore from backup. But if it still goes blue, flash the system, data, cache, boot, recovery from your twrp backup.

Related

[Tutorial] Get Recovery working on UNLOCKED BOOTLOADER, when you're on MM NO DATALOSS

Hello,
I noticed that many people want to get recovery working on Marshmallow-Beta. Most people don't want to loose there data, settings ....
So I thought about writing a little Tutorial.
We need:
boot.img with included Recovery
TWRP for unlocked Bootloader
FTF of the .264-firmware (you can download it via XperiaFirm (keep in mind selecting your Phone (e.g. D6503))
[URL="http://www.flashtool.net/downloads.php"]flashtool and it's latest update
A few GB space on your SD-Card
MM-Beta-Zip
Installed Drivers
Time ​[/URL]
The first thing we need to do is to backup our Data, but How to do this without Recovery, TitaniumBackup isn't a good solution.
So .. one way would be to flash a boot.img, so we can boot a recovery, which is included into that file
Step1: Shutdown your Phone (you should have at least 50% battery for a safe flash)
Step2: Connect your Phone to your Computer, while pressing the Volume UP Button (if you have a blue light you're now in fastboot-mode)
Step3: flash the boot.img (fastboot flash boot stock-17.1.1.A.0.402-sirius-repack.img via cmd) NOW YOUR PHONE CAN NOT BOOT TO MARSHMALLOW ANYMORE​Step4: Connect Phone to PC and backup your Data From internalSD
Enter recovery and make a backup
Step1: reboot your phone (fastboot reboot), then press the vol down Button repeatedly, until you enter the recovery.
Step2: make a backup and select everything, but boot IMPORTANT !​
Flashing new bootloader
Step1: shutdown your phone completely
Step2: start flashtool and select the thunder symbole + flashmode
Step3: select your downloaded FTF and select wipe Userdata+Apps-Logs
Step4: plug in your phone with vol+ pressed, so that you're in flashmode
Step5: flash firmware​
Flashing TWRP
Step1: Shutdown your Phone
Step2: Boot into Fastboot
Step3 Flash TWRP for unlocked bootloader : fastboot flash recovery recovery.img​Restoring MM
Step1: Shutdown your phone
Step2: Boot into Recovery (hold Power and VolDown, release Power when phone vibrates)
Step3: flash MM-Zip
Step4: restore your Backup
Step5: restore Internal-SD-Backup-files to InternalSD​---
Done
OK, thanks
So you mean we're going to use TWPR's backup function. But does TWRP Backup restore internal sd's general files(photos, songs....etc)?
Flashing ftf with wipe userdata option will wipe EVERYTHING on my internal-sd, including photos and songs. So It's no use if twrp cannot restore them
Or do you write this guide only for people who only want to keep their appdata and settings(/data/data, /data/app)?
Also, you mentioned about NEW Bootloader of .264 firmware. Many ppl told me that I should update to new BL to install recovery in MM.
Does the NEW BL has seperated partitions for each recovery and boot(kernel)?
hw0603 said:
So you mean we're going to use TWPR's backup function. But does TWRP Backup restore internal sd's general files(photos, songs....etc)?
Flashing ftf with wipe userdata option will wipe EVERYTHING on my internal-sd, including photos and songs. So It's no use if twrp cannot restore them
Or do you write this guide only for people who only want to keep their appdata and settings(/data/data, /data/app)?
Click to expand...
Click to collapse
You're right .. I didn't noticed that internalSD is wiped, too. But you can back up it via PC in Recovery or in Android
@backupfunction ... No Recovery has the option to backup InternalSD (because the developers think its useless)
hw0603 said:
Also, you mentioned about NEW Bootloader of .264 firmware. Many ppl told me that I should update to new BL to install recovery in MM.
Does the NEW BL has seperated partitions for each recovery and boot(kernel)?
Click to expand...
Click to collapse
Yes exactly there is a seperate recovery partition
raolleel said:
You're right .. I didn't noticed that internalSD is wiped, too. But you can back up it via PC in Recovery or in Android
@backupfunction ... No Recovery has the option to backup InternalSD (because the developers think its useless)
Yes exactly there is a seperate recovery partition
Click to expand...
Click to collapse
Thanks for reply I'm going to try installing MM on weekend
I tried it, it worked perfectly, thanks!

Dumb Mistake PLEASEE HELP!

So earlier today I was trying to install my stock recovery. Was a success but I also accidentally installed my stock recovery over my boot image. So now no matter what keys I hold to get to bootloader or recovery it automatically takes me to the recovery screen. Yes I have tried wiping data/factory rest and also tried caches partition. I have also tried doing it the older way by using adb/fastboot but my device wont connect. Yes I have the correct drivers. Im thinking its because I cant get into my phone to enable USB debugging. So any ideas on how I can re flash a new boot.img and recovery.img?
So you did a fastboot flash boot and typed in your recovery file?
Try the forced update method.
Download the latest firmware for your phone, extract it to get dload folder containing update.app, copy that dload folder to an SD card. Since your phone already boots up into recovery it should start the update.
rslimitless said:
So earlier today I was trying to install my stock recovery. Was a success but I also accidentally installed my stock recovery over my boot image. So now no matter what keys I hold to get to bootloader or recovery it automatically takes me to the recovery screen. Yes I have tried wiping data/factory rest and also tried caches partition. I have also tried doing it the older way by using adb/fastboot but my device wont connect. Yes I have the correct drivers. Im thinking its because I cant get into my phone to enable USB debugging. So any ideas on how I can re flash a new boot.img and recovery.img?
Click to expand...
Click to collapse
Boot to TWRP then copy boot.img to your phone and then use Install / Image / choose boot.img
you can boot TWRP from the bootloader screen with fastboot boot TWRP.img
To enter the bootloader - turn off phone - plug phone into the PC - boot up phone with vol down + power

Need help with CM12.1 on Oukitel K4000 Lite

I was able to install CM12.1 on my Oukitel K4000 Lite.
But I have a problem:
1) Baseband version: Unknown;
2) Sim status section: Not available;
3) IMEI information: Unknow;
4) Bluetooth address: Unavailable;
Everything else works.
I want to know if I should change any system files(porting) before I flash it again?
I have both: stock and the CM12.1 roms.
I have installed TWRP, Gapps, SuperSU.
I have looked Google and other sites for a couple days now and haven't found any fixes that would work.
I have a backup made with TWRP and even tried to restore nvram, protect_f, protect_s partitions; flashed secro.img via TWRP; did a factory reset also but still no help.
I would really appreciate any help.
I will provide any further information and needed files.
I cant seem to get it to boot into twrp.. although I did flash it with fastboot
hardcorehenry said:
I was able to install CM12.1 on my Oukitel K4000 Lite.
But I have a problem:
1) Baseband version: Unknown;
2) Sim status section: Not available;
3) IMEI information: Unknow;
4) Bluetooth address: Unavailable;
Everything else works.
I want to know if I should change any system files(porting) before I flash it again?
I have both: stock and the CM12.1 roms.
I have installed TWRP, Gapps, SuperSU.
I have looked Google and other sites for a couple days now and haven't found any fixes that would work.
I have a backup made with TWRP and even tried to restore nvram, protect_f, protect_s partitions; flashed secro.img via TWRP; did a factory reset also but still no help.
I would really appreciate any help.
I will provide any further information and needed files.
Click to expand...
Click to collapse
I was able to OEM unlock and flash the recovery.img but when I issue fastboot reboot it does not boot into recovery but rather a normal boot..
I know i've missed something simple...
can you help?
I should mention that OEM unlocking this phone does force a Factory Data Reset.. just in case anyone tries this on their own.
> fastboot oem unlock
> fastboot flash recovery recovery.img # NOTE: use the TWRP for k6000 Pro
> fastboot reboot # this is where the problem happens.. normal reboot.. not reboot into recovery
> fastboot bootloader # definitely not recovery.. android with gutsy triangle "no command"
:/
any help would be greatly appreciated.. I dont think I want to flash the supersu until I get it into twrp (nor can I .. right?)
Thanks
-Bill
Sorry.. I'm an idiot.. I should mention as well that I have the v12 ROM.
Also after the FDR android claims not to recognise my 32gb SanDisk microSD that it was using just fine before the FDR... so now i get to rescue the data and reformat it..
vlaad1970 said:
I was able to OEM unlock and flash the recovery.img but when I issue fastboot reboot it does not boot into recovery but rather a normal boot..
I know i've missed something simple...
can you help?
I should mention that OEM unlocking this phone does force a Factory Data Reset.. just in case anyone tries this on their own.
> fastboot oem unlock
> fastboot flash recovery recovery.img # NOTE: use the TWRP for k6000 Pro
> fastboot reboot # this is where the problem happens.. normal reboot.. not reboot into recovery
> fastboot bootloader # definitely not recovery.. android with gutsy triangle "no command"
:/
any help would be greatly appreciated.. I dont think I want to flash the supersu until I get it into twrp (nor can I .. right?)
Thanks
-Bill
Sorry.. I'm an idiot.. I should mention as well that I have the v12 ROM.
Also after the FDR android claims not to recognise my 32gb SanDisk microSD that it was using just fine before the FDR... so now i get to rescue the data and reformat it..
Click to expand...
Click to collapse
No, you cant flash supersu until you are in twrp. Lol. And fastboot reboot is normal boot, its not supposed to reboot into recovery its supposed to boot into system.and bootloader is bootloader. and for triangle no command, keep clicking on volume and power buttons at the same time. to boot into recovery, you need to power off the phone, then hold down volume up+power button at the same time. then a menu will pop up: recovery, fastboot, normal. use volume up to change options.click on volume down to choose recovery. then it will boot into recovery.flash supersu from there. and after u boot into system again later. install simplereboot app from play store and give root access to it then u can reboot into recovery through that app next time.
and what v12 rom? what rom is that?

Can't boot to bootloader after bootloader unlocked

Hi,
I unlocked my Honor 9 bootloader using the "fastboot oem unlock 'unlock key'" method.
After that it did low level reset or something of the sort and booted to Android.
After that I wanted to install TWRP using fastboot, the problem is that every time I do "adb reboot bootloader" I get a message the device cannot be trusted (see pic) and it boots to android.
I tried pressing power button, up button (this gets me to the recovery), but it always gets back to Android and not to fastboot.
What can I do???
Thank you
Return fully stock, then try again
PalakMi said:
Return fully stock, then try again
Click to expand...
Click to collapse
How do I do that, use the original recovery?
OK, I managed to get to the bootloader by turning off the phone, pressing the volume down button and connecting the USB cable.
I flashed twrp and somehow booted to the recovery I wanted to flash the supersu.zip but all the folders and file names in the sdcard were gibberish.
I rebooted and everything was ok (not gibberish) but instead of having twrp I got the original recovery back.
Since then even if I flash using fastboot the twrp recovery I keep getting the original recovery.
In the fastboot screen there's a message "Android reboot reason: bootloader NA reboot_enter_fastboot_common_func" is it normal? (see pic)
And one last question, should I use SuperSU-v2.82-201705271822.zip or Magisk-v14.0.zip to root?
UPDATE:
I managed to get twrp working.
I did fastboot oem relock, and then unlocked the bootloader again, and it booted to twrp (without re-flashing twrp).
When I tried to flash supersu all the files were gibberish (see pic), what am I missing?
If I wipe data it seems fine, but then I boot to system to copy the supersu file and once I load twrp it is gibberish again.
Also should I use SuperSU-v2.82-201705271822.zip or Magisk-v14.0.zip to root?
Appreciate any help I can get.
This mate is called encryption
Put the SuperSU zip on a SD card and you should be able to flash it without any problems if you use the latest beta release.
Magisk is another story.
Midhon58 said:
This mate is called encryption
Put the SuperSU zip on a SD card and you should be able to flash it without any problems if you use the latest beta release.
Magisk is another story.
Click to expand...
Click to collapse
yeah I figured as much.
Didn't think of using external SD, thanks, was about to try adb sideload, I assume it would have worked too.
Many thanks, the external sd did the trick

Help honor 9 stf-l09 stock firmware!

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.

Categories

Resources