Hello everyone ! I have a big issue :
I installed the following rom OpenKirin's AOSP Treble Oreo For Honor 9. But, the capacity buttons didn't work at all.
So I went to the following topic [Oreo] [TWRP 3.2.1-0] [0.3] [+Capacitive fix].
This topic said that I "just" had to flash the kernel to get my capacitive buttons working again, but now, my phone can't boot at all. It keeps on restarting and shows me the honor disclaimer then the honor blue starting screen and it loops.
So can you guys tell me is there any fix or is my phone a brick, knowing that I still can access the fastboot and TWRP?
Thanks
You flash a B360's kernel over a build which is not B360 ; So bootloops.
What stock firmware were you on before flashing AOSP system ?
---------- Post added at 23:36 ---------- Previous post was at 23:34 ----------
Just flash back the stock kernel from your firmware version before AOSP.
oslo83 said:
You flash a B360's kernel over a build which is not B360 ; So bootloops.
What stock firmware were you on before flashing AOSP system ?
---------- Post added at 23:36 ---------- Previous post was at 23:34 ----------
Just flash back the stock kernel from your firmware version before AOSP.
Click to expand...
Click to collapse
Thank you for being that fast, I had the STF-L09C432B365 firmware.
So extract the stock kernel img (ramdisk) from the Update.app file included in the file update.zip from this firmware.
Use a windows app called HuaweiUpdateExtractor
---------- Post added at 23:43 ---------- Previous post was at 23:41 ----------
Then wait for a B365 kernel that fixes buttons.
(Or go back to stock B360 for applying the b360 kernel fix)
oslo83 said:
So extract the stock kernel img (ramdisk) from the Update.app file included in the file update.zip from this firmware.
Use a windows app called HuaweiUpdateExtractor
---------- Post added at 23:43 ---------- Previous post was at 23:41 ----------
Then wait for a B365 kernel that fixes buttons.
(Or go back to stock B360 for applying the b360 kernel fix)
Click to expand...
Click to collapse
OK, so once it's extracted I just have to do a ./fastboot flash kernel <my_extracted_stock_kernel>.img right?
I'll try it, once I finish to install my VM (I have a mac ><)
dandas said:
OK, so once it's extracted I just have to do a ./fastboot flash kernel <my_extracted_stock_kernel>.img right?
I'll try it, once I finish to install my VM (I have a mac ><)
Click to expand...
Click to collapse
Well it didn't work :/
Code:
./fastboot flash kernel KERNEL.img
does not work ? What does it output ?
(By the way adb and fastboot are working just fine on osx without need of a VM for those.)
oslo83 said:
So extract the stock kernel img (ramdisk) from the Update.app file included in the file update.zip from this firmware.
Use a windows app called HuaweiUpdateExtractor
---------- Post added at 23:43 ---------- Previous post was at 23:41 ----------
Then wait for a B365 kernel that fixes buttons.
(Or go back to stock B360 for applying the b360 kernel fix)
Click to expand...
Click to collapse
Really? I have made a thread on Guides with all stock EMUI8 kernels, ramdisks and recoveries for easy access to people but i guess no one noticed... why do i bother...
JBolho said:
Really? I have made a thread on Guides with all stock EMUI8 kernels, ramdisks and recoveries for easy access to people but i guess no one noticed... why do i bother...
Click to expand...
Click to collapse
No need to be offended mate, I tried all your files with the exact same commands, and none is working on my device
oslo said:
Code:
./fastboot flash kernel KERNEL.img
does not work ? What does it output ?
(By the way adb and fastboot are working just fine on osx without need of a VM for those.)
Click to expand...
Click to collapse
I did the same command, here's the log :
Code:
➜ platform-tools ./fastboot flash kernel ~/foo/KERNEL.img
target reported max download size of 471859200 bytes
sending 'kernel' (24576 KB)...
OKAY [ 0.650s]
writing 'kernel'...
OKAY [ 0.262s]
I still have a bootloop... And thanks for the VM advice, but you told me to use HuaweiUpdateExtractor which only works on Windows, so I still had to use a VM. Anyway, my previous message wasn't clear about that point, sorry for the misunderstanding.
Do you have any other suggestion? I start to doubt about my original build number, do you know if I can cat the original stock kernel with the adb shell, or if I can get out of the loop with some others kernel and ramdisks imgs?
Thank you guys
You'll need stock kernel of your actual build.
So it's seems you were not STF-L09C432B365 kernel as you still are bootlooping.
Try with stock kernels from :
STF-L09C432B364
STF-L09C432B363
STF-L09C432B362
STF-L09C432B360
You could try with images provided by JBolho : https://androidfilehost.com/?w=files&flid=266088
oslo83 said:
You'll need stock kernel of your actual build.
So it's seems you were not STF-L09C432B365 kernel as you still are bootlooping.
Try with stock kernels from :
STF-L09C432B364
STF-L09C432B363
STF-L09C432B362
STF-L09C432B360
You could try with images provided by JBolho : https://androidfilehost.com/?w=files&flid=266088
Click to expand...
Click to collapse
As I said, I tried them already, but I'll try again. BTW the B360_kernel.img is missing inside JBolho's repo
Maybe he messed something when uploading them.
Maybe you were not on one of those.
Ok, is there any other version I can try? Or maybe my process is wrong, I do the same commands, and in the same order as Jbolho describes in his post.
Except for the recovery flash, does it matter? Because since that I don't have the erecovery anymore, before I still had it in combination with the twrp.
Thanks
oslo83 said:
Maybe he messed something when uploading them.
Maybe you were not on one of those.
Click to expand...
Click to collapse
No, I didn't mess anything, checked them already, all in the same folder on AFH and properly uploaded.
And I never stated that the B360 fixed kernel was in my repo, I point it to zxz0O0's thread.
What I would recommend is to flash recovery and ramdisk too, not just kernel (corresponding to previously installed firmware of course)
@dandas Please note that recovery & erecovery are two differents mode.
help !!
did you find a solution for this problem
i have the same problem after flashing kernel to my honor 9 STF-AL10 please help me
kalilou23000 said:
did you find a solution for this problem
i have the same problem after flashing kernel to my honor 9 STF-AL10 please help me
Click to expand...
Click to collapse
What version did you flash specifically, on what firmware?
help honor STF-AL10
my phone was on
STF-AL10C00B172 the capacitive botton wont work when i google the problem xda team have solved the problem with flashing kernel
when i have flashed kernel the phone bootloop and reboot into e-recovery mode
i tried to download emergency software from erecovery with wifi but it didnt work ''failed ''
when i trie to flash the honor with his one version again onlly system.img flashed seccessfully via fastboot mode with cmd
other img wont pass it saise failed
i have tried other ways like flashing stock rom 5GB via upgrade mode with sd card but the flash failed and it write failed to install software
in my case i dont have money to activate dc unlocker and unbrick my device with dc-phoenix so i downloaded a board software '' xml file '' for my honor 9 and installed acm and handset driver but the device when i install acm device it is connected on com 11 huawei mobile connect Fake acm interface i cant flash my honor 9 via IDT tool what should i do !!!
kalilou23000 said:
my phone was on
STF-AL10C00B172 the capacitive botton wont work when i google the problem xda team have solved the problem with flashing kernel
when i have flashed kernel the phone bootloop and reboot into e-recovery mode
i tried to download emergency software from erecovery with wifi but it didnt work ''failed ''
when i trie to flash the honor with his one version again onlly system.img flashed seccessfully via fastboot mode with cmd
other img wont pass it saise failed
i have tried other ways like flashing stock rom 5GB via upgrade mode with sd card but the flash failed and it write failed to install software
in my case i dont have money to activate dc unlocker and unbrick my device with dc-phoenix so i downloaded a board software '' xml file '' for my honor 9 and installed acm and handset driver but the device when i install acm device it is connected on com 11 huawei mobile connect Fake acm interface i cant flash my honor 9 via IDT tool what should i do !!!
Click to expand...
Click to collapse
That's confusing to say the least. You flashed the kernel on B172 firmware??? That's Nougat firmware! No wonder you screwed everything up. Don't mess with board software and stuff like that, you have to install the firmware with dload method probably.
Related
hi guys!
Anyone knows how to install twrp in the latest stock rom?
I tried in windows 10 using flash tools and a preloader error apperas.
In windows XP i could install twrp but it did not load when trying to access it.
Thanks!
Fran Montero said:
hi guys!
Anyone knows how to install twrp in the latest stock rom?
I tried in windows 10 using flash tools and a preloader error apperas.
In windows XP i could install twrp but it did not load when trying to access it.
Thanks!
Click to expand...
Click to collapse
it might not have loaded because it was maybe an updated twrp eith an old preloader, try flashing an older twrp or update preloader
Ruben Craveiro said:
it might not have loaded because it was maybe an updated twrp eith an old preloader, try flashing an older twrp or update preloader
Click to expand...
Click to collapse
Have you installed it already?
Many thanks!
Fran Montero said:
Have you installed it already?
Many thanks!
Click to expand...
Click to collapse
Im using latest twrp with updated preloader and LOS13
Hi,
I'm unsure if this method will work for you, but I also had "preloader Error message" in FlashTools trying to flash TWRP in Stock Rom 2016810 while trying to flash the Eragon ROM.
As the Stock ROM you are using (20171201) is kinda newer than stock 2016810 Im kinda assuming it should work the same.
In order for it to flash without errors, I did the following and worked fine :
Use FlashTools ver v5.1612 - https://www.androidfilehost.com/?fid=24591000424940027
Download your stock rom 20171201
https://mega.nz/#!atZAyKxb!i6jpNQNR_VZZ3nS79LhL2xi78WHx7XI4gKFllc8 RJKw
Then download TWRP_3.0.2.8.zip here: https://www.androidfilehost.com/?fid=24727369092696060
Unzip all and and copy the "MT6755_Android_scatter" & "recovery.img" from TWRP_3.0.2.8 folder into the Elephone_P9000_20170112 Rom folder.
Then open Flash Tools - add the scatter file from the Elephone_P9000_20170112 Rom folder
Untick everything in flashtools except the recovery and then try to flash, hopefully it will work for you too. without errors '
jotei66 said:
Hi,
I'm unsure if this method will work for you, but I also had "preloader Error message" in FlashTools trying to flash TWRP in Stock Rom 2016810 while trying to flash the Eragon ROM.
As the Stock ROM you are using (20171201) is kinda newer than stock 2016810 Im kinda assuming it should work the same.
In order for it to flash without errors, I did the following and worked fine :
Use FlashTools ver v5.1612 - https://www.androidfilehost.com/?fid=24591000424940027
Download your stock rom 20171201
https://mega.nz/#!atZAyKxb!i6jpNQNR_VZZ3nS79LhL2xi78WHx7XI4gKFllc8 RJKw
Then download TWRP_3.0.2.8.zip here: https://www.androidfilehost.com/?fid=24727369092696060
Unzip all and and copy the "MT6755_Android_scatter" & "recovery.img" from TWRP_3.0.2.8 folder into the Elephone_P9000_20170112 Rom folder.
Then open Flash Tools - add the scatter file from the Elephone_P9000_20170112 Rom folder
Untick everything in flashtools except the recovery and then try to flash, hopefully it will work for you too. without errors '
Click to expand...
Click to collapse
Thanks for the answer.
I tried and TWRP is flashed succesfully and i can even load it, but when rebooting system it is not loading, it remains on the withe elephone logo
Fran Montero said:
Thanks for the answer.
I tried and TWRP is flashed succesfully and i can even load it, but when rebooting system it is not loading, it remains on the withe elephone logo
Click to expand...
Click to collapse
Maybe you have a sd card formatted as internal storage?
Fran Montero said:
Thanks for the answer.
I tried and TWRP is flashed succesfully and i can even load it, but when rebooting system it is not loading, it remains on the withe elephone logo
Click to expand...
Click to collapse
Hi, I think this maybe to do with the new preloader etc..
I read this in the thread for TWRP for Elephone P9000 3.0.2-8:
1. load scatter.txt in earlier post.
2. select preloader, lk and boot imgs, location of these from the stock 20160810 ROM.
3. select recovery, location of TWRP img.
4. unselect everything else.
Click to expand...
Click to collapse
Here: https://forum.xda-developers.com/el...hone-p9000-t3426678/post70713618#post70713618
So maybe Unzip the 20171201 Rom, copy TWRP scatter & recovery.img to this folder, open flash tools and select recovery and point to recovery.img
But also select preloader, lk and boot img (double check they are pointing to corresponding files from the 20171201 ROM
Again, I am unsure if that will work but as I noticed the above post in the TWRP thread, thought it maybe relevant to your issue
PS: Windows 10 can be awkward with splash tools at times, I have windows 10 but in order for it to work - I have to press the Download in SplashTools, kinda count to 5, then hold vol + and then attach USB to my phone and it works fine
If your device already rooted, you can also install flashyfi and flash the .img file.
jotei66 said:
Hi,
I'm unsure if this method will work for you, but I also had "preloader Error message" in FlashTools trying to flash TWRP in Stock Rom 2016810 while trying to flash the Eragon ROM.
As the Stock ROM you are using (20171201) is kinda newer than stock 2016810 Im kinda assuming it should work the same.
In order for it to flash without errors, I did the following and worked fine :
Use FlashTools ver v5.1612 - https://www.androidfilehost.com/?fid=24591000424940027
Download your stock rom 20171201
https://mega.nz/#!atZAyKxb!i6jpNQNR_VZZ3nS79LhL2xi78WHx7XI4gKFllc8 RJKw
Then download TWRP_3.0.2.8.zip here: https://www.androidfilehost.com/?fid=24727369092696060
Unzip all and and copy the "MT6755_Android_scatter" & "recovery.img" from TWRP_3.0.2.8 folder into the Elephone_P9000_20170112 Rom folder.
Then open Flash Tools - add the scatter file from the Elephone_P9000_20170112 Rom folder
Untick everything in flashtools except the recovery and then try to flash, hopefully it will work for you too. without errors '
Click to expand...
Click to collapse
a bit late (did came to it to test your solution earlier) but it worked indeed. perfect, very much appreciated.
Can u upload 20171201 again?! Link is not working... Thx
opss said:
Can u upload 20171201 again?! Link is not working... Thx
Click to expand...
Click to collapse
You'll find a link here: https://forum.xda-developers.com/el...t/rom-stock-rom-android-6-0-12-01-17-t3542463
Thx dude
jotei66 said:
Hi, I think this maybe to do with the new preloader etc..
I read this in the thread for TWRP for Elephone P9000 3.0.2-8:
Here: https://forum.xda-developers.com/el...hone-p9000-t3426678/post70713618#post70713618
So maybe Unzip the 20171201 Rom, copy TWRP scatter & recovery.img to this folder, open flash tools and select recovery and point to recovery.img
But also select preloader, lk and boot img (double check they are pointing to corresponding files from the 20171201 ROM
Again, I am unsure if that will work but as I noticed the above post in the TWRP thread, thought it maybe relevant to your issue
PS: Windows 10 can be awkward with splash tools at times, I have windows 10 but in order for it to work - I have to press the Download in SplashTools, kinda count to 5, then hold vol + and then attach USB to my phone and it works fine
Click to expand...
Click to collapse
I've wasted countless hours trying to get spf to work with my windows 10 machine. Your solution worked like a charm, the flashing was successful (managed to get the process to work when before I was getting only preloader errors), however I still don't have twrp but the standard android recovery. Have you got any other solution that I should try? Cheers.
---------- Post added 9th May 2017 at 12:18 AM ---------- Previous post was 8th May 2017 at 11:43 PM ----------
thecrazyfarang said:
I've wasted countless hours trying to get spf to work with my windows 10 machine. Your solution worked like a charm, the flashing was successful (managed to get the process to work when before I was getting only preloader errors), however I still don't have twrp but the standard android recovery. Have you got any other solution that I should try? Cheers.
Click to expand...
Click to collapse
I reflashed and managed to get twrp but now the phone won't boot, it is stuck in the Elephone logo
thecrazyfarang said:
I've wasted countless hours trying to get spf to work with my windows 10 machine. Your solution worked like a charm, the flashing was successful (managed to get the process to work when before I was getting only preloader errors), however I still don't have twrp but the standard android recovery. Have you got any other solution that I should try? Cheers.
---------- Post added 9th May 2017 at 12:18 AM ---------- Previous post was 8th May 2017 at 11:43 PM ----------
I reflashed and managed to get twrp but now the phone won't boot, it is stuck in the Elephone logo
Click to expand...
Click to collapse
Have you tried pressing power and then keep finger pressed on vol up to go straight to TWRP recovery and then flashing a new ROM in TWRP ?
I didn't do that as I didn't have another rom saved in my phone. What I eventually managed to do was flash the official nougat via spf tool. I'm saying eventually because this piece of crap windows 10 didn't want to make the connection even with the volume up button. When I was going to give up and order a new phone, it connected and now I am happy even though I don't have twrp nor root, but not going to risk it again. Thanks again for your help though, greatly appreciated.
thecrazyfarang said:
I didn't do that as I didn't have another rom saved in my phone. What I eventually managed to do was flash the official nougat via spf tool. I'm saying eventually because this piece of crap windows 10 didn't want to make the connection even with the volume up button. When I was going to give up and order a new phone, it connected and now I am happy even though I don't have twrp nor root, but not going to risk it again. Thanks again for your help though, greatly appreciated.
Click to expand...
Click to collapse
No worries, just glad you got it sorted out.
Btw (although I know you dont really wanna risk trying it) my son uses my P9000 and has TWRP installed with no issues at all and root with Magisk.
But great yous sorted out
Root twrp Step by step for newbeee-
Ok,so I've installed TWRP 3.0.2-8 and when I start the phone it goes into the recovery... what to do next? Can I find a tutorial somewhere how to do this? And wich image can I use or is the best for the moment?
thx for helping...
Hi I had Xpower5 Rom. I wanted to try new Nougat. I had many issues with flash (error of processing system.sin and loader.sin). I dont know how now it work. After that I flashed AndroPlus 43 kernel and TWRP 3.0.2. Kernel works but No white led on startup and no recovery there (also adb reboot recovery not work) . I tried another img of twrp and nothing changed. Any idea how install recovery? Anybody has the same problem with flashing? Thanks
As this phone doesn't support universal recovery and only sports a ota partition that can be used for recovery but then requires a kernel that supports booting recovery from ota partition, it's a hustle to use non standard recovery systems.
Is there even a nougat compatible kernel with included TWRP ota boot support for this phone?
This should work
https://forum.xda-developers.com/showpost.php?p=70807294&postcount=132
Also patching the stock kernel with the rootkernel tool integrates working twrp.
Gewiz said:
This should work
https://forum.xda-developers.com/showpost.php?p=70807294&postcount=132
Also patching the stock kernel with the rootkernel tool integrates working twrp.
Click to expand...
Click to collapse
It works! Thanks. Problem was: no white LED flash there. I have to press vol down and power on.
But I have still have a problem with flashing. Error of processing file loader.sin or system.sin. I cant flash again anything
Make sure you use latest ver of flashtool 0.9.23.2
Gewiz said:
Make sure you use latest ver of flashtool 0.9.23.2
Click to expand...
Click to collapse
Yes I have latest version. I tried older version as well but nothing changed
hromanse said:
Yes I have latest version. I tried older version as well but nothing changed
Click to expand...
Click to collapse
Flash firmware 5.11 first and flash nougat firmware afterwards.
This should work
Not work as well
the 3.1 3.0.2 TWRP bundled in rootkernel 5.23 messess up the internal permissions, so it will appear to work until you try and recover, or - TWRP runs a wipe with mkext4fs
i was talking a bit about it in https://forum.xda-developers.com/showthread.php?t=3560135
---------- Post added at 18:16 ---------- Previous post was at 18:13 ----------
Gewiz said:
Flash firmware 5.11 first and flash nougat firmware afterwards.
This should work
Click to expand...
Click to collapse
Yeah, going back to Lollipop and going all the way up to Nougat works, this is what happened to me. I thought I had a psuedo-recovery-dual system boot .... where i could switch between Marshmallow and Nougat
But then I decided to factory reset, and that started all the problems.
NeoBeum said:
Yeah, going back to Lollipop and going all the way up to Nougat works, this is what happened to me...
Click to expand...
Click to collapse
Thanks! It works
hromanse said:
Thanks! It works
Click to expand...
Click to collapse
Just make sure Restore works, so you don't get burned thinking everything is ok and end up with 12GB of partition mismatched data backup after a month, like I did
I currently have this problem that when I flash a version of TWRP(have tried both 3.0.2 and 3.1.0) I cannot reboot my current OS(have tried both stock 376 and 378). Simply pressing the power button will result in recovery mode. Stranger still, when i flashed a ROM as a zip out of twrp, it actually booted up, but then I could no longer return to recovery mode, despite fiddling around mith multiple button combinations.
Seems as though i am missing something obvious, as i have not found a thread regarding a similar issue. Anybody have a clue as to what it might be?
macjagger said:
I currently have this problem that when I flash a version of TWRP(have tried both 3.0.2 and 3.1.0) I cannot reboot my current OS(have tried both stock 376 and 378). Simply pressing the power button will result in recovery mode. Stranger still, when i flashed a ROM as a zip out of twrp, it actually booted up, but then I could no longer return to recovery mode, despite fiddling around mith multiple button combinations.
Seems as though i am missing something obvious, as i have not found a thread regarding a similar issue. Anybody have a clue as to what it might be?
Click to expand...
Click to collapse
it seems like u dint have an proper boot.img
try flashing ftf
I've been flashing the stock firmware(s) as ftf using flashtool (newest version) and xperifirm, that's why I think it's so odd. Before flashing TWRP, the stock ROM boots up and everything works as it should. After flashing TWRP, it only boots up into recovery.
macjagger said:
I've been flashing the stock firmware(s) as ftf using flashtool (newest version) and xperifirm, that's why I think it's so odd. Before flashing TWRP, the stock ROM boots up and everything works as it should. After flashing TWRP, it only boots up into recovery.
Click to expand...
Click to collapse
hmmm do u flash an kernel that has dm variety fix
---------- Post added at 08:32 AM ---------- Previous post was at 08:32 AM ----------
also what firmware ur are on
altvolt74 said:
hmmm do u flash an kernel that has dm variety fix
---------- Post added at 08:32 AM ---------- Previous post was at 08:32 AM ----------
also what firmware ur are on
Click to expand...
Click to collapse
Yes, I've been flashing kernels with that fix.
I managed to get stock 378 DE running using only flashtool with jutphaas' boot.img of this thread: https://forum.xda-developers.com/z5-compact/general/32-3-0-378-pushed-xperifirm-t3559906/page4
I've also had 376 DE and 376 AU firmware working with this ROM: https://forum.xda-developers.com/z5-compact/development/rom-stock-z5c32-3-0-376r2dau-t3570248
In this case I was able to flash the ROM .zip out of TWRP and boot into the ROM. Afterwards I could no longer enter TWRP though.
In both cases, after (re)flashing TWRP, I'd get stuck in recovery.
macjagger said:
Yes, I've been flashing kernels with that fix.
I managed to get stock 378 DE running using only flashtool with jutphaas' boot.img of this thread: https://forum.xda-developers.com/z5-compact/general/32-3-0-378-pushed-xperifirm-t3559906/page4
I've also had 376 DE and 376 AU firmware working with this ROM: https://forum.xda-developers.com/z5-compact/development/rom-stock-z5c32-3-0-376r2dau-t3570248
In this case I was able to flash the ROM .zip out of TWRP and boot into the ROM. Afterwards I could no longer enter TWRP though.
In both cases, after (re)flashing TWRP, I'd get stuck in recovery.
Click to expand...
Click to collapse
try flash e5823 lates nougat e5823_32.3.A.0.376_R2R_AU instead of (e5803) firmware
also to enter flash the rom using kernel partition
off phone . ...hold vol down and power release power when see sony keep holding volume down all the way till recovery
format system
flash zip
i will update intrustions since theres people having issues while flashing an rom using e5823 on e5803 or probably ur flashing it wrong using the recovery that is integrated to the boot.img
---------- Post added at 05:01 AM ---------- Previous post was at 05:00 AM ----------
also sorry for late reply been cooking xperia xz rom to our z5 compact also finish is uploading it now
I'll give it a try in a couple of days. Need my phone as a daily driver currently. Appreciate your help
macjagger said:
In both cases, after (re)flashing TWRP, I'd get stuck in recovery.
Click to expand...
Click to collapse
To me it seems like you are just flashing twrp to the wrong partition.
How do you flash it?
You have to flash it with command:
Fastboot flash recovery "twrp.img"
macjagger said:
I currently have this problem that when I flash a version of TWRP(have tried both 3.0.2 and 3.1.0) I cannot reboot my current OS(have tried both stock 376 and 378). Simply pressing the power button will result in recovery mode. Stranger still, when i flashed a ROM as a zip out of twrp, it actually booted up, but then I could no longer return to recovery mode, despite fiddling around mith multiple button combinations.
Seems as though i am missing something obvious, as i have not found a thread regarding a similar issue. Anybody have a clue as to what it might be?
Click to expand...
Click to collapse
oh hai
just wanted to link you in on this:
https://forum.xda-developers.com/z5...m-fix-twrp-t3560135/post71433741#post71433741
Hey fellas, I'm back. Excuse my absence, currently busy with exams.
It seems as though @Gewiz was correct. I was trying to flash twrp over "Flashtool>fastboot mode>select kernel to flash", which probably targets the wrong partition. Instead I now used "Flashtool>fastboot mode>reboot into fastboot mode via fastboot" and flashed it using the standard cmd window line ("fastboot flash recovery twrp.img") and it seems to have worked.
Thanks to everyone on this thread!
macjagger said:
Hey fellas, I'm back. Excuse my absence, currently busy with exams.
It seems as though @Gewiz was correct. I was trying to flash twrp over "Flashtool>fastboot mode>select kernel to flash", which probably targets the wrong partition. Instead I now used "Flashtool>fastboot mode>reboot into fastboot mode via fastboot" and flashed it using the standard cmd window line ("fastboot flash recovery twrp.img") and it seems to have worked.
Thanks to everyone on this thread!
Click to expand...
Click to collapse
Have you tried to do a restore yet?
Just wanted to ask so I can isolate twrp with rootkernel
Phone was ok with this version KII-L21C185B321CUSTC185D001, I tried to reflash but I couldn't find the same version in .app format. I tried to downgrade to KII-L21C185B310CUSTC185D001 through SDCard but it failed. I used ADB to flash KII-L21C185B310CUSTC185D001 through those commands:
fastboot flash recovery RECOVERY.img
fastboot flash boot BOOT.img
fastboot flash system SYSTEM.img
Fastboot flash cust CUST.img
All went fine except the cust file. Phone is working but with wrong info in the about panel as it has build 310 with emui 4.0.2 interface and it couldn't make both OTA or SDcard updates although I had the new update notification.
I used TWRP backup from XDA (GR5+TWRP+backup_KII-L21C185B130.rar) to go back to stock loilpop build 140 from this thread https://forum.xda-developers.com/hon...depot-t3328288. Phone has correct info in the about panel build 130 lilopop but with no fingerprint menu and it can't make both OTA or SDcrad updates.
Any help would be appreciated. Regards.
mohamed75 said:
Phone was ok with this version KII-L21C185B321CUSTC185D001, I tried to reflash but I couldn't find the same version in .app format. I tried to downgrade to KII-L21C185B310CUSTC185D001 through SDCard but it failed. I used ADB to flash KII-L21C185B310CUSTC185D001 through those commands:
fastboot flash recovery RECOVERY.img
fastboot flash boot BOOT.img
fastboot flash system SYSTEM.img
Fastboot flash cust CUST.img
All went fine except the cust file. Phone is working but with wrong info in the about panel as it has build 310 with emui 4.0.2 interface and it couldn't make both OTA or SDcard updates although I had the new update notification.
I used TWRP backup from XDA (GR5+TWRP+backup_KII-L21C185B130.rar) to go back to stock loilpop build 140 from this thread https://forum.xda-developers.com/hon...depot-t3328288. Phone has correct info in the about panel build 130 lilopop but with no fingerprint menu and it can't make both OTA or SDcrad updates.
Any help would be appreciated. Regards.
Click to expand...
Click to collapse
Did you try the erecovery method?
gopinaidu77 said:
Did you try the erecovery method?
Click to expand...
Click to collapse
Do you mean that menu when phone asks to connects through wifi to recover system?
I already tried this but it didnot start affer wifi connecting.
mohamed75 said:
Do you mean that menu when phone asks to connects through wifi to recover system?
I already tried this but it didnot start affer wifi connecting.
Click to expand...
Click to collapse
No , iam saying about the dload method
gopinaidu77 said:
No , iam saying about the dload method
Click to expand...
Click to collapse
I have already tried with different FW versions. it stuck at 5% then update failed.
mohamed75 said:
I have already tried with different FW versions. it stuck at 5% then update failed.
Click to expand...
Click to collapse
Update failed for no package or else failed to verify package ? Can u plz elaborate, pretty sure i can help u about this !
gopinaidu77 said:
Update failed for no package or else failed to verify package ? Can u plz elaborate, pretty sure i can help u about this !
Click to expand...
Click to collapse
It passes verification then stops at 5%.
mohamed75 said:
It passes verification then stops at 5%.
Click to expand...
Click to collapse
U need to get the right package bro .
gopinaidu77 said:
U need to get the right package bro .
Click to expand...
Click to collapse
I have already used this package (HUAWEI GR5 Firmware (KII-L21, Android 6.0.1, EMUI 4.0, C185B310CUSTC185D004)) before with my phone without any problem then I OTA upadted the phone to KII-L21C185B321CUSTC185D001. I tried to clean flash the phone after some bugs with viper4android and such mods but I couldn't find full flash KII-L21C185B321CUSTC185D001 so I tried dload method to downgrade to the previous full build (C185B310CUSTC185D004) which is available but it failed at 5%. So I extracted the rom files from (C185B310CUSTC185D004) and pushed them with ADB then I have the wrong info problem and I couldn't make SD card or OTA updates. I tried TWRP backup from device sticky thread and I couldn't make SD card or OTA updates plus fingerprint is not working.
mohamed75 said:
I have already used this package (HUAWEI GR5 Firmware (KII-L21, Android 6.0.1, EMUI 4.0, C185B310CUSTC185D004)) before with my phone without any problem then I OTA upadted the phone to KII-L21C185B321CUSTC185D001. I tried to clean flash the phone after some bugs with viper4android and such mods but I couldn't find full flash KII-L21C185B321CUSTC185D001 so I tried dload method to downgrade to the previous full build (C185B310CUSTC185D004) which is available but it failed at 5%. So I extracted the rom files from (C185B310CUSTC185D004) and pushed them with ADB then I have the wrong info problem and I couldn't make SD card or OTA updates. I tried TWRP backup from device sticky thread and I couldn't make SD card or OTA updates plus fingerprint is not working.
Click to expand...
Click to collapse
They will work. Extract the update.app and get the files named SYSTEM.IMG ,CUST.IMG , BOOT.IMG,RECOVERY.IMG .
Get these five files from update.app . I will help u with the rest of work. U can unbrick ur phone easily
gopinaidu77 said:
They will work. Extract the update.app and get the files named SYSTEM.IMG ,CUST.IMG , BOOT.IMG,RECOVERY.IMG .
Get these five files from update.app . I will help u with the rest of work. U can unbrick ur phone easily
Click to expand...
Click to collapse
SYSTEM.IMG ,CUST.IMG , BOOT.IMG,RECOVERY.IMG
These are 4 files , where is the fifyh?
Anyway, I have already tried flashing them many times before andI still have the wrong info problem.
fastboot flash recovery RECOVERY.img
fastboot flash boot BOOT.img
fastboot flash system SYSTEM.img
Fastboot flash cust CUST.img
All files are flashed successfully except the .CUST file, it gives error message REMOTE DEVICE NOT AVAILABLE.
mohamed75 said:
SYSTEM.IMG ,CUST.IMG , BOOT.IMG,RECOVERY.IMG
These are 4 files , where is the fifyh?
Anyway, I have already tried flashing them many times before andI still have the wrong info problem.
fastboot flash recovery RECOVERY.img
fastboot flash boot BOOT.img
fastboot flash system SYSTEM.img
Fastboot flash cust CUST.img
All files are flashed successfully except the .CUST file, it gives error message REMOTE DEVICE NOT AVAILABLE.
Click to expand...
Click to collapse
Wait , u need to flash only cust is it ? All wrong info is caused by the cust partition . I can help u to flash that too.
Do u have twrp installed ?
gopinaidu77 said:
Wait , u need to flash only cust is it ? All wrong info is caused by the cust partition . I can help u to flash that too.
Do u have twrp installed ?
Click to expand...
Click to collapse
I already tried this too through twrp but it always fails
mohamed75 said:
I already tried this too through twrp but it always fails
Click to expand...
Click to collapse
Hmm. Can you try with fastboot again?
---------- Post added at 05:14 PM ---------- Previous post was at 05:12 PM ----------
mohamed75 said:
I already tried this too through twrp but it always fails
Click to expand...
Click to collapse
And i jist asked u if twrp exists now . Can u answer me if it exists ? I can help u flash cust through recovery
gopinaidu77 said:
Hmm. Can you try with fastboot again?
---------- Post added at 05:14 PM ---------- Previous post was at 05:12 PM ----------
And i jist asked u if twrp exists now . Can u answer me if it exists ? I can help u flash cust through recovery
Click to expand...
Click to collapse
Yes it exists
mohamed75 said:
SYSTEM.IMG ,CUST.IMG , BOOT.IMG,RECOVERY.IMG
These are 4 files , where is the fifyh?
Anyway, I have already tried flashing them many times before andI still have the wrong info problem.
fastboot flash recovery RECOVERY.img
fastboot flash boot BOOT.img
fastboot flash system SYSTEM.img
Fastboot flash cust CUST.img
All files are flashed successfully except the .CUST file, it gives error message REMOTE DEVICE NOT AVAILABLE.
Click to expand...
Click to collapse
instead of fastboot try mfastboot for cust.img it might give you success
miststudent2011 said:
instead of fastboot try mfastboot for cust.img it might give you success
Click to expand...
Click to collapse
Name never change binary . that command wont work when all above works
gopinaidu77 said:
Name never change binary . that command wont work when all above works
Click to expand...
Click to collapse
agree with you, but mfastboot has higher success rate while falshing stock images.
miststudent2011 said:
agree with you, but mfastboot has higher success rate while falshing stock images.
Click to expand...
Click to collapse
Thats only with motorola and Nexus phones
gopinaidu77 said:
Thats only with motorola and Nexus phones
Click to expand...
Click to collapse
even though they are specific for Nexus and Motorola devices they can be used with other devices and has solved issues with many others you can have a glance in XDA threads.
Hello.
My honor 9 (stf al00) cant boot. It stuck on huawei erecovery.
I've tried hard reset, wipe cache & wipe data but still stuck.
And also I dont have the driver.
Can anyone please help me.
What happened before ?
You were on nougat or oreo ? which build ?
Which region ? C00 ? or rebranded C432 or else ?
oslo83 said:
What happened before ?
You were on nougat or oreo ? which build ?
Which region ? C00 ? or rebranded C432 or else ?
Click to expand...
Click to collapse
I dont know what happend, give my brother use for awhile, suddenly he return to me with this problem.
its on nougat. sorry what build, i dont know.
Region China?. i dont know about the C00 or rebranded and c432 that you said. really have no idea.
OK.
So your Honor9 is STF-AL00 and was on nougat.
But:
-you don't know on which firmware region it was and you don't know if it was rebranded to STF-L09
-i guess your brother could also have updated it to oreo, or rebranded it before bricking it...
If you did not have any chinese app stock installed like QQ, Weibo or Tancent News then you could be probably on region C432 (or C10 or C185) ;
If so use this with an exfat external micro sdcard or usb-otg EXFAT formatted:
https://forum.xda-developers.com/honor-9/development/firmware-huawei-honor-9-stf-l09-stock-t3696892
First try with C432B130, read the instructions inside, do it, then report.
thanks.. i will try it tonight,
i've done try update with sd card before, but not with those file inside the link you give.
and also not with EXFAT fromat sd card, but it said Software Update Failed.
i will try this and update here again..
thanks
honor 9 stf-al00
phone unlocked and frp unlock
bricked the phone installing oreo.
twrp is installed but all the roms i flash i get error 9.
dload with update.app get stuck at 5% and after "system update failed"
i also extracted update.app and i can flashed boot,kernel and recovery but i get an error flashing system
At this point i just want the phone running anything but everything that i do doenst work
ruigarcia said:
honor 9 stf-al00
phone unlocked and frp unlock
bricked the phone installing oreo.
twrp is installed but all the roms i flash i get error 9.
dload with update.app get stuck at 5% and after "system update failed"
i also extracted update.app and i can flashed boot,kernel and recovery but i get an error flashing system
At this point i just want the phone running anything but everything that i do doenst work
Click to expand...
Click to collapse
Are you with nougat or oreo partitionni'g scheme ?-> are you actually booting on a nougat twrp or on a oreo twrp ?
Which region your phone were on on ?
original chinese C00 ?
or rebranded C432, C10 or else?[/QUOTE]
oslo83 said:
Are you with nougat or oreo partitionni'g scheme ?-> are you actually booting on a nougat twrp or on a oreo twrp ?
Which region your phone were on on ?
original chinese C00 ?
or rebranded C432, C10 or else?
Click to expand...
Click to collapse
[/QUOTE]
right now with oreo partitions, never rebranded the phone, and i was running update b362 so i assume im still on c00, otherwise i dont think i would have worked.
twrp is 3.1.1.1 open kirin edition
right now with oreo partitions, never rebranded the phone, and i was running update b362 so i assume im still on c00, otherwise i dont think i would have worked.
twrp is 3.1.1.1 open kirin edition[/QUOTE]
OK so, the facts :
1) B362 firmware are mostly european (C432) or russian (C10) and could be japanese (C635).
So your phone was previously rebranded from chinese to one of these region.
It's not a problem if not done wrong, maybe your case...
2)'twrp 3.1.1.1 open kirin edition' is a custom recovery for NOUGAT and not for oreo.
And then some more questions:
-Can you boot your phone to normal mode ?
-You were on nougat before brick ?
-You were one oreo B362 before brick ?
-The brick happens after it upgraded from mogat to oreo B362 ? If so, how did you update ? normal OTA ? forced OTA with android app Firmware Finder ?
i can only boot the phone in recovery mode (twrp and erecovery) and fastboot
i installed b360 through forced ota and then when i was in the system i updated again to b362 throught settings\system update
i was on oreo b362 before brick, and i remember now that my navigations buttons were not working so i flashed a custom kernel to fix it, but
that prevented me from booting to the system again. (Proto Kernel)
edit: used that tool you gave me and i managed to flash STF-L09_C432B360.
ruigarcia said:
i installed b360 through forced ota and then when i was in the system i updated again to b362 throught settings\system update
Click to expand...
Click to collapse
So your phone was correctly rebranded in the past and we can deduce you are now on region C432 or C10.
ruigarcia said:
i was on oreo b362 before brick, and i remember now that my navigations buttons were not working so i flashed a custom kernel to fix it, but
that prevented me from booting to the system again. (Proto Kernel)
Click to expand...
Click to collapse
You flashed a custom B360 kernel over your B362 : It was why your phone bootlooped just after !!
Flashing a stock B362 kernel would have solve the bootloop.
ruigarcia said:
i also extracted update.app and i can flashed boot,kernel and recovery but i get an error flashing system
Click to expand...
Click to collapse
You said you had flashed boot, kernel and recovery from an update.app.... Which build number and region this update.app was from ?
You could flash back B362 stock boot, kernel and recovery and it should boot if you did not messed something else...
So, the best for you will be to:
1) use HuRUpdater to flash C432B360 or C10B360 firmware (depending of your actual phone region)
2)then flash the B360 kernel fix
3)then update via OTA or huRUpdater.
oslo83 said:
So your phone was correctly rebranded in the past and we can deduce you are now on region C432 or C10.
You flashed a custom B360 kernel over your B362 : It was why your phone bootlooped just after !!
Flashing a stock B362 kernel would have solve the bootloop.
You said you had flashed boot, kernel and recovery from an update.app.... Which build number and region this update.app was from ?
You could flash back B362 stock boot, kernel and recovery and it should boot if you did not messed something else...
So, the best for you will be to:
1) use HuRUpdater to flash C432B360 or C10B360 firmware (depending of your actual phone region)
2)then flash the B360 kernel fix
3)then update via OTA or huRUpdater.
Click to expand...
Click to collapse
i flashed many update.app, i messed up with that, cant remember the last one.
just flashed twrp for oreo now, went to terminal and i can see "ro.hw.vendor: (hw)
does this tell me my phone region?
with this twrp for oreo i also get another error when flashing a rom zip "failed to mount "\system" (permission denied)
Stop messing with random dload folder and update.app ; From what i seen only special one called 'service repair' will work.
No. It does not.
Stop messing trying to flash random zip when on twrp ; From what i heard only special one called 'FullOTA-MF-PV' will work this way with twrp.
Be bold and try HuRUpdater witj C432B360 following my latter post.
oslo83 said:
Stop messing with random dload folder and update.app ; From what i seen only special one called 'service repair' will work.
No. It does not.
Stop messing trying to flash random zip when on twrp ; From what i heard only special one called 'FullOTA-MF-PV' will work this way with twrp.
Be bold and try HuRUpdater witj C432B360 following my latter post.
Click to expand...
Click to collapse
i used HuRUpdater and worked. thank you! cant update to b362 through settings tho
C432 is maybe the wrong region if you don't get ota update notification to b362/b364 when checking for update in settings :
1) What's your build number version on Settings/System/about ?
2) What's the country shown when you dial**#*#2846579#*#**- on the dial pad, then go to 'Network Information Query' and then to 'Vendor Country Info' ?
---------- Post added at 19:44 ---------- Previous post was at 19:42 ----------
Dial**#*#2846579#*#*
---------- Post added at 19:46 ---------- Previous post was at 19:44 ----------
sorry typos.
So dial:
Code:
*#*#2846579#*#*
im so sorry, i cant access my pc right now.
i will update soon i can get access to my pc.
oslo83 said:
C432 is maybe the wrong region if you don't get ota update notification to b362/b364 when checking for update in settings :
1) What's your build number version on Settings/System/about ?
2) What's the country shown when you dial**#*#2846579#*#**- on the dial pad, then go to 'Network Information Query' and then to 'Vendor Country Info' ?
---------- Post added at 19:44 ---------- Previous post was at 19:42 ----------
Dial**#*#2846579#*#*
---------- Post added at 19:46 ---------- Previous post was at 19:44 ----------
sorry typos.
So dial:
Code:
*#*#2846579#*#*
Click to expand...
Click to collapse
vendor:hw
country:eu
build number:stf-l09 8.0.0.360(c432)~
reflashed b360 and now i get update to b364 on settings. still no capacity buttons..
So, you're fine on C432.
Just flash the B360 kernel fix while you're still on B360 https://forum.xda-developers.com/showpost.php?p=75772700 ;
This will fix your buttons.
You can then do a normal update via settings
ok so i tried to update using vol up + vol down + power button, again it said software install failed
inside those rar file got 2 file, 1 is UPDATE.APP which is 4gb++ and another one is update_STF-L09_hw_eu.app size around 1.4gb.
try update with 4gb file, appear 5% loading and then appear software install failed, same with 1.4gb file...
the only option i got is reboot system now when the error come out..
already did wipe cache & data before i do the update..
any idea? am i doing wrong step?
I have the same problem...When the installation begins, it stops at 5%
My phone is turned off. I tried to install recovery but got nothing
any idea please