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.
Related
So i need to flash a cust.img through recovery because fastboot doenst work gives me "remote:command not allowed fastboot" but if i want to flash it through the recovery it says "Error: File larger then target device" i basicly only need to flash the cust.img to fix my phone.
What i tried:
Use fastboot, tried new version of android SDK
flashed diffrent recoverys, same results.
Please help i really need my phone ;/
Demian3112 said:
So i need to flash a cust.img through recovery because fastboot doenst work gives me "remote:command not allowed fastboot" but if i want to flash it through the recovery it says "Error: File larger then target device" i basicly only need to flash the cust.img to fix my phone.
What i tried:
Use fastboot, tried new version of android SDK
flashed diffrent recoverys, same results.
Please help i really need my phone ;/
Click to expand...
Click to collapse
Are you on stock rom? if so you have to enable oem for fastboot to work, it should be somewhere in the developer settings. otherwise i wouldn't know
jimandroidnerd said:
Are you on stock rom? if so you have to enable oem for fastboot to work, it should be somewhere in the developer settings. otherwise i wouldn't know
Click to expand...
Click to collapse
Im on b130 kiw l21 my phone shows wrong data under about phone and i cant apply a update to go back to stock from the dload file it simply instant says syatem update failed. I just want to revert back to stock then update to b140 and then to B330 emui 4.0 but i cant because the dload keeps failing
Demian3112 said:
Im on b130 kiw l21 my phone shows wrong data under about phone and i cant apply a update to go back to stock from the dload file it simply instant says syatem update failed. I just want to revert back to stock then update to b140 and then to B330 emui 4.0 but i cant because the dload keeps failing
Click to expand...
Click to collapse
you say you are on b130 but than you say you wanna go to stock rom? I dont really understand what you are telling me here
jimandroidnerd said:
you say you are on b130 but than you say you wanna go to stock rom? I dont really understand what you are telling me here
Click to expand...
Click to collapse
My device got bricked B330. So i had to reflash some stuff and ended up with false info under the section About Phone i had the same issue as him So i followed that instructions but i couldnt flash the Cust.img in the recovery (twrp) it gives me the error that i have as title. Without flashing the cust.img i cant use a revert package through dload since my Phone shows other information then the update package (denies to do the update instant) . My question how can i fix the error "File bigger then target device" so i can flash the Cust.img since fast boot doesnt work (error remote: command not allowed recovery) and twrp is my only option..
Instructions i followed to get back to stock.
Flash Boot.img, system.img, cust.img through twrp > flash stock recovery > Apply UK back to stock through dload
I cant flash cust.img so step 1 fails and i cant do the rest.
Anyone a idea why i cant flash this file through TWRP and fastboot? This is littery my last hope to get back to stock ;/
Demian3112 said:
Anyone a idea why i cant flash this file through TWRP and fastboot? This is littery my last hope to get back to stock ;/
Click to expand...
Click to collapse
I could give you my twrp backup? Maybe that will help
jimandroidnerd said:
I could give you my twrp backup? Maybe that will help
Click to expand...
Click to collapse
I mean i should be able to flash cust.img through fastboot right?
Demian3112 said:
I mean i should be able to flash cust.img through fastboot right?
Click to expand...
Click to collapse
No, i meant i can give u my twrp backup so you van restore it from twrp. Do you want it or not?
jimandroidnerd said:
No, i meant i can give u my twrp backup so you van restore it from twrp. Do you want it or not?
Click to expand...
Click to collapse
Nvm thanx! Fixed it im an idiot.
I was so bussy almost 2 days with this. I have no experience (14old) and i simply went bussy so much with it that i started looking over the simple things. I fixed it now it left me with a damm headache thnx anyways, i learned something again!
jimandroidnerd said:
No, i meant i can give u my twrp backup so you van restore it from twrp. Do you want it or not?
Click to expand...
Click to collapse
Oke i got a bit too excited. The fingerprint option is gone like it never has been there. Honor boot logo has a red H, i get the b140 update but cant apply it same issue with dload. Would you mind sharig your TWRP update? If it is possible for B330 and B130 Thx!
Demian3112 said:
Oke i got a bit too excited. The fingerprint option is gone like it never has been there. Honor boot logo has a red H, i get the b140 update but cant apply it same issue with dload. Would you mind sharig your TWRP update? If it is possible for B330 and B130 Thx!
Click to expand...
Click to collapse
You need to use kiwi_twrp_5-14_recovery.img
and the backup needs to contain all these partitions
boot.emmc.win
cust.ext4.win"
erecovery.emmc.win"
firmware.info"
firmware.vfat.win"
misc.emmc.win"
persist.ext4.win
system.ext4.win000
system.ext4.win001
restore those and you'll be back in business
This rom also contains the /cust partition for b130
http://forum.xda-developers.com/honor-5x/development/custom-rom-starter-template-honor-5x-t3328809
clsA said:
You need to use kiwi_twrp_5-14_recovery.img
and the backup needs to contain all these partitions
boot.emmc.win
cust.ext4.win"
erecovery.emmc.win"
firmware.info"
firmware.vfat.win"
misc.emmc.win"
persist.ext4.win
system.ext4.win000
system.ext4.win001
restore those and you'll be back in business
This rom also contains the /cust partition for b130
http://forum.xda-developers.com/honor-5x/development/custom-rom-starter-template-honor-5x-t3328809
Click to expand...
Click to collapse
This is what i got.. http://prntscr.com/brv0ay the Repository doesnt contain this files aswell any idea? Is it possible to flash for example a full Kiw L22 rom and then use a revert package for L21 through Dload?
Oke what i did:
Wipe
Apply Cust partition with terminal
Apply backup/restore
flash stock recovery
Boots same issue, I just need the dload to get to work so i can flash the recovery pack. But it stays at 0 percent even after 15 mins.
What i found out is that i dont have the stock firmware (Dont have fingerprint and stuff, device doenst show as KIW L21), so i doenst do a ota update and local update ofcourse. I need a TWRP backup with firmware included. What im trying now is installing L21 MIDDLE-EAST firmware and then try to use a revert package for L21 through OTA.
Arobase40 said:
Well, I'm not sure this is a good idea as it took me 11 days to upgrade from B140 (Lollipop) to B330 (Marshmallow) and only a few minutes to brick my Honor 5x L21 using a backup from kiwi_twrp_5-14_recovery.img when I wanted to revert back to B140... ^^
At boot time after the restore, I have an animated red H letter from the Honor Logo and impossible to get back to the welcome screen nor to any other screen so I don't have access to TWRP anymore...
We really need to have access to the official downgrade firmware from Honor !!!
Click to expand...
Click to collapse
Same issue.. I get red H honor logo.. cant apply a single update through ota/dload and finger print is gone.. I can do everything, installing apps and stuff but i cant revert back to full stock.
clsA said:
You need to use kiwi_twrp_5-14_recovery.img
and the backup needs to contain all these partitions
boot.emmc.win
cust.ext4.win"
erecovery.emmc.win"
firmware.info"
firmware.vfat.win"
misc.emmc.win"
persist.ext4.win
system.ext4.win000
system.ext4.win001
restore those and you'll be back in business
This rom also contains the /cust partition for b130
http://forum.xda-developers.com/honor-5x/development/custom-rom-starter-template-honor-5x-t3328809
Click to expand...
Click to collapse
Could you link me the firmware.vfat and misc.emmc and persist.ext. Is there a way to make the update.app a flashable zip? Anyways any idea what i still could do?
Anyways what would you recommend me to go back to stock right now? Is it cuz my system partition is messed up? How to fix? thx anyways!
Arobase40 said:
As I said it is NOT really a good idea to use a TWRP backup to revert back from Marshmallow to Lollipop as it will brick your device !
I also said : ask your local Honor technical support for an official revert back firmware as your whole system is obviously messed up.
I don't know how you upgraded your smartphone but better downgrade to Lollipop first and try to upgrade again to MM a "proper way"...
Click to expand...
Click to collapse
]
Thats the point.. I simply cant. Phone doenst accept dload updates instant says "System Failed", most near honor technical support is 98 km out.
Ok anyways does anyone have a B330 full stock backup?
Arobase40 said:
I didn't say you had to move yourself to a technical support but place a phone call or mail them. You should find their phone number or their email address from your the Honor Website.
I'll do it myself by tomorrow...
Click to expand...
Click to collapse
I fixed it. Go to hi honor and search for honor 5x firmware, download it unpack it put the update.app on dload on microsd make sure you flashed stock recovery through fastboot hold power + volume down + volume up until it vibrates and done. I couldnt install any dload file on XDA the error "system failed" means the update is not for your device. The one on hihonor was the only one that worked for me ive been bussy 3 days its worth trying. I can link/upload you the download and instructions if you want to but ill do it tomorrow.
jimandroidnerd said:
No, i meant i can give u my twrp backup so you van restore it from twrp. Do you want it or not?
Click to expand...
Click to collapse
Hello i have the same problem could you please give me your backup so i can try it?
Same issue
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.
hi there.
soooo I kinda bricked my mate 10 lite (RNE-L21C432)
bootloader is unlocked, rooted.
I tried flashing a flashable rom and got a bootloop...sooooo
I downloaded the firmware via huawei firmware finder , the oreo one.
I opened the UPDATE.APP via huawei update extractor, there are alot of files, so can you please tell me what files I need to extract and flash to unbrick my phone?
I extracted system, kernel, vendor and odm for now, system flashed fine. but I cant flash kernel it gives me the error FAILED: remote: command not allowed
can you pleaste help me?
Edit: I can flash system, I did flash kernel, I can flash recovery too, but when I try to flash anything else, it gives me that error
Edit2: can someone tell me which files do I need to extract via huawei update extractor to flash? I know that system.img is one of them
konopla4 said:
hi there.
soooo I kinda bricked my mate 10 lite (RNE-L21C432)
bootloader is unlocked, rooted.
I tried flashing a flashable rom and got a bootloop...sooooo
I downloaded the firmware via huawei firmware finder , the oreo one.
I opened the UPDATE.APP via huawei update extractor, there are alot of files, so can you please tell me what files I need to extract and flash to unbrick my phone?
I extracted system, kernel, vendor and odm for now, system flashed fine. but I cant flash kernel it gives me the error FAILED: remote: command not allowed
can you pleaste help me?
Click to expand...
Click to collapse
Check if you're still FRP unlock in Fastboot.
ante0 said:
Check if you're still FRP unlock in Fastboot.
Click to expand...
Click to collapse
Both bootloader and from are unlocked
konopla4 said:
Both bootloader and from are unlocked
Click to expand...
Click to collapse
Ah, didn't see your edit.
Fastboot is limited in flashing, you can't flash everything.
From memory I think it is:
System, vendor, recovery_ramdisk, recovery_vendor, recovery_vbmeta, ramdisk, kernel, cache, userdata
You could use HWOTA for Mate 10 Lite if you can get into stock recovery, as it will flash the full update.app rather than the limited partitions fastboot can flash.
https://forum.xda-developers.com/ma...development/hwota-huawei-mate10-lite-t3777115
ante0 said:
Ah, didn't see your edit.
Fastboot is limited in flashing, you can't flash everything.
From memory I think it is:
System, vendor, recovery_ramdisk, recovery_vendor, recovery_vbmeta, ramdisk, kernel, cache, userdata
Click to expand...
Click to collapse
So I can flash all of these without getting the error and it'll will restore my system?
I remember on p8 lite I needed to flash only system, boot, and cust. To restore the system. It was much easier.
konopla4 said:
So I can flash all of these without getting the error and it'll will restore my system?
I remember on p8 lite I needed to flash only system, boot, and cust. To restore the system. It was much easier.
Click to expand...
Click to collapse
Edited while you posted, use HWOTA if you can get into stock recovery
https://forum.xda-developers.com/ma...development/hwota-huawei-mate10-lite-t3777115
ante0 said:
Edited while you posted, use HWOTA if you can get into stock recovery
https://forum.xda-developers.com/ma...development/hwota-huawei-mate10-lite-t3777115
Click to expand...
Click to collapse
Yeah, just noticed.
So hwota. I don't have the "stock recovery" I can only flash the recovery that I extract from update.app
The one I flash is bugged for some reason, probably because it's from a slightly different system than the one I had.
konopla4 said:
Yeah, just noticed.
So hwota. I don't have the "stock recovery" I can only flash the recovery that I extract from update.app
The one I flash is bugged for some reason, probably because it's from a slightly different system than the one I had.
Click to expand...
Click to collapse
If it can be booted into it should work. HWOTA will replace it anyway with a no-check recovery. Or you could use TWRP by Caucava21 and use HuRUpdater (https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279) to update from TWRP.
Either way will work.
ante0 said:
If it can be booted into it should work. HWOTA will replace it anyway with a no-check recovery. Or you could use TWRP by Caucava21 and use HuRUpdater (https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279) to update from TWRP.
Either way will work.
Click to expand...
Click to collapse
Waaaait it, I can update from TWRP?
Or is it a specialized one?
konopla4 said:
Waaaait it, I can update from TWRP?
Or is it a specialized one?
Click to expand...
Click to collapse
It's a script, but it needs a TWRP that's compatible. The one by Catuva21 is (or so I've heard).
"The current image(boot/recovery) have been destroyed and can not boot.
Please flash the corret image"
Hey guys can someone help me ?
my device can't booting, because I patched my boot.img because I need to root it, and I don't have stock boot.img
Already downloaded from stock rom 4 times and corrupt
but I still can use the bootloader / fastboot
Maybe someone can help me with the boot.img ? I mean send/upload it
NB : I'm in .14 Rom
My device already unlocked/UBL
please someone help me with booting.img recovery.img
6 times downloaded firmware but I still got corrupted file
puttr said:
please someone help me with booting.img recovery.img
6 times downloaded firmware but I still got corrupted file
Click to expand...
Click to collapse
Bro, join telegram channel. you will get better support.
Telegram channel's full of impatient youth who are irreverent, arrogant and talk in pidgin English....If you fit the bill, you'll fit right in....
puttr said:
"The current image(boot/recovery) have been destroyed and can not boot.
Please flash the corret image"
Hey guys can someone help me ?
my device can't booting, because I patched my boot.img because I need to root it, and I don't have stock boot.img
Already downloaded from stock rom 4 times and corrupt
but I still can use the bootloader / fastboot
Maybe someone can help me with the boot.img ? I mean send/upload it
NB : I'm in .14 Rom
My device already unlocked/UBL
Click to expand...
Click to collapse
don't panic, it's pretty easy.
all you have to do is just install boot.img in the stock room. and the problem is fixed
Boot loop
AndriezSetyawan said:
don't panic, it's pretty easy.
all you have to do is just install boot.img in the stock room. and the problem is fixed
Click to expand...
Click to collapse
Im stuck at boot loop pls help
aslo give me the telegram link
Cookie Ninja said:
Telegram channel's full of impatient youth who are irreverent, arrogant and talk in pidgin English....If you fit the bill, you'll fit right in....
Click to expand...
Click to collapse
excuse me, wtf?
---------- Post added at 06:12 AM ---------- Previous post was at 06:11 AM ----------
malakaz27 said:
Im stuck at boot loop pls help
aslo give me the telegram link
Click to expand...
Click to collapse
may I know what you were doing before bootloop?
also feel free to join https://t.me/realme3pros
malakaz27 said:
Im stuck at boot loop pls help
aslo give me the telegram link
Click to expand...
Click to collapse
join this group https://t.me/r3pindonesia
your problem has fixed
same problem with me pls hlp
i got the same problem please heeeeeeeeeeeeeeelp i hope to fing solution quickly
I have the same problem.i am going to flash all image files throuh fastboot.i will confirm here if it works
well, but i dont know how to flash
venky34268 said:
I have the same problem.i am going to flash all image files throuh fastboot.i will confirm here if it works
Click to expand...
Click to collapse
i searched a lot and i ddnt find except one flash file .ofp and i dont know how to flash it ... pls tell me how to flash
Follow the guide only fastboot method.
nasser.56 said:
i searched a lot and i ddnt find except one flash file .ofp and i dont know how to flash it ... pls tell me how to flash
Click to expand...
Click to collapse
https://forum.xda-developers.com/realme-3-pro/how-to/guide-to-stock-rom-stock-recovery-t3940604
the files are there with the link
my phone is done
my phone is done :fingers-crossed:
i toke it to realme warranty and they flashed it
for free
they thought i flashed it with wrong way hahaha
Help me bro
harikp6247 said:
Bro, join telegram channel. you will get better support.
Click to expand...
Click to collapse
I aslo brick my phone
boot/recovery destroyed
give me link boot.img please bro
but how?
AndriezSetyawan said:
don't panic, it's pretty easy.
all you have to do is just install boot.img in the stock room. and the problem is fixed
Click to expand...
Click to collapse
#can you give tutorial, pls help me.
venky34268 said:
I have the same problem.i am going to flash all image files throuh fastboot.i will confirm here if it works
Click to expand...
Click to collapse
if you have the img files please share the link
Mod Edit: Every member is responsible for what they do with their device. Please be sure you know what you are doing, and that the method you want to use is correct for your device.
Guys finally I found the way to recover the device.
It should work on any real me device currently I am using real me 3 pro with color OS 6.0.1.
This is the solution for recovery/ boot destroyed message.
Here are the steps :
You are probably facing this issue because you have unlocked your bootloader.
First of all you have to lock bootloader of real me 3 pro using fastboot
Reboot your phone to bootloader mode
And connect to computer with USB.
here are the commands to lock the bootloader
fastboot oem lock
fastboot flashing lock -- this one I used
fastboot oem relock
( No need to use all you can try anyone of them )
Once you type this command in computer and hit enter it will ask to confirm the lock on phone
Use volume down keys for confirmation.
So here is the trick,
Color OS recovery is made to wipe the data whenever you lock / unlock bootloader.
So once you lock your bootloader on you real me 3 your color OS recovery will pop up ( even it is broke) for some seconds which will format your internal data.
Once you format the data your phone again will boot to recovery mode and same error will popup
" Boot / recovery has been destroyed "
Don't worry
Again power off the device wait for 10 seconds and reboot to bootloader mode not to recovery (very Imp) by pressing volume down + power key
Now you will boot in color OS recovery
( Note : if you didn't succeed try the above step 3-4 time because it took 3 attempt for me )
Surely you will boot in color OS recovery.
Now download the color OS OTA update file to your Memory card
( It is necessary to use SD card )
link :
https://www.realme.com/in/support/software-update
Download the latest firmware ozip file
Now create the folder in memory card and paste the firmware file over there
If you are already in color OS recovery don't reboot the phone just insert the SD card and select update. Select storage as
SD card
Select the folder and file and update.
It will take few minutes and you will be able to successfully boot in stock color OS ROM.
Enjoy.
You know the best part that I am writing this blog from the same phone only.
when i select the ozip file for update the processing stuck on 30%. thn faild
when i select the ozip file for update the processing stuck on 30%. thn failed
SharonBlack said:
when i select the ozip file for update the processing stuck on 30%. thn failed
Click to expand...
Click to collapse
Looks like the ozip file is not downloaded properly
Download the diffrent version and check
You can also try to flash the flashable zip from xda without bloat...
different ozip installation also failed
hacker786 said:
Looks like the ozip file is not downloaded properly
Download the diffrent version and check
You can also try to flash the flashable zip from xda without bloat...
Click to expand...
Click to collapse
flashable zip support stock recovery?? different ozip installation also failed .so plz help me
---------- Post added at 05:34 AM ---------- Previous post was at 05:01 AM ----------
hacker786 said:
Looks like the ozip file is not downloaded properly
Download the diffrent version and check
You can also try to flash the flashable zip from xda without bloat...
Click to expand...
Click to collapse
i also tried a14,a8 ozip stock rom.but after starting installation 2 minutes then failed
Please need help to unbrick my phone model dub-lx2 . i tried to flash system, ramdisk, ramdisk recovery, kernel via fastboot. no errors but system don't boot. i tried to update by dload but every time uodate fail. i don't konw how or Wich uppdate.app to restore the stock system.
Phone no not booting only fastboot command works
Delhamito said:
Please need help to unbrick my phone model dub-lx2 . i tried to flash system, ramdisk, ramdisk recovery, kernel via fastboot. no errors but system don't boot. i tried to update by dload but every time uodate fail. i don't konw how or Wich uppdate.app to restore the stock system.
Phone no not booting only fastboot command works
Click to expand...
Click to collapse
How did you unlock the bootloader?
Sent from my HUAWEI DUB-LX1 using XDA Labs
Paid service 4$ : ministryofsolutions.com/huawei-bootloader
Please if u have sotck rom or system backup please share it could not find firmware for this model only online update
Did you fix it??
Delhamito said:
Paid service 4$ : ministryofsolutions.com/huawei-bootloader
Please if u have sotck rom or system backup please share it could not find firmware for this model only online update
Click to expand...
Click to collapse
Delhamito said:
Please need help to unbrick my phone model dub-lx2 . i tried to flash system, ramdisk, ramdisk recovery, kernel via fastboot. no errors but system don't boot. i tried to update by dload but every time uodate fail. i don't konw how or Wich uppdate.app to restore the stock system.
Phone no not booting only fastboot command works
Click to expand...
Click to collapse
If you need help you should post here your mobile build number .you have to convert Update.app file to raw-xml file and correct loader for flash.if you have umt qfire tool then you can unbrick your phone .:good:
i can easy unbrick dub-lx,
Huawei y7 pro สามารถใช้แอป King Root ใด้ใหมครับ