Related
Hi There, need some help if you can...any educated and experienced help would be appreciated thanks.
After downloading my stock firmware and extracting via Huawei update Extractor all the image files ( System, user data, Cache, etc) I backed up oeminfo and cust files via Rayglobe Knife and saving the extracted update.app file to my dload folder on SDCard and successfully resetting my phone to factory using the vol+/- and power method I was quietly confident to make the jump and flash a rom the Android 7.0 (N) Nougat beta on Huawei posted by Somboons
I followed the instructions and dirty flashed this thru TWRP as instructed which seemed to go ok until I tried to reboot, the phone booted to stock recovery so I wiped Dalvik, Cache and Factroy reset, this completed and it all went down hill from there, basically now just stuck at boot screen saying that its about to reboot but never moves unless I use button combos
(OK so yes I feel stupid now and I'll beat myself up so you don"t have to, but I reallyt thought that I could always get back to stock via my SDCard)
What I can do...
Phone can only boot to eRecovery ( with WIFI failed message )
I can go into fastboot ( shows Bootloader and FRP unlocked)
What i can't do...
Cant access my update file on SDCard....Trying to boot using vol+/- and power to access my dload/update.app file on my SDCard just freezes at initial boot screen and tells me to push vol up button for 3 second and this takes me to eRecovery where all i can do is reboot or shut down.
I can't adb sideload files " no SU Binary detected"
What I've tried...
I have tried Rayglobe knife UNBRICK option placing my extracted boot, cust, system, recovery .img files but his fails with my PC popping up and saying this operation can't be performed on this PC please contact developer so this fails.
I then tried to fastboot flash all the image files which seemed to work successfully but no changes to the situation.
I have tried to fastboot flash the update.app which went thru the sparse process of all seven files and then come up with error command can not complete ( something in those words)
I have tried to fastboot new stock recovery from my rom as well as TWRP recovery but nothing works even if it says seems to have completed in the adb command prompt.
I have a feeling this is to do with the encryption of the rom and now my system cannot recognise my partition and without recovery I have no way of mounting my sdcard.
Thank god I have my old and reliable Lumia 1520 to fall back on untill I get this sorted.
Any Help would be appreciated....thanks in advance
Are you able to boot into Huawei recovery?
Mickie.C said:
Hi There, need some help if you can...any educated and experienced help would be appreciated thanks.
After downloading my stock firmware and extracting via Huawei update Extractor all the image files ( System, user data, Cache, etc) I backed up oeminfo and cust files via Rayglobe Knife and saving the extracted update.app file to my dload folder on SDCard and successfully resetting my phone to factory using the vol+/- and power method I was quietly confident to make the jump and flash a rom the Android 7.0 (N) Nougat beta on Huawei posted by Somboons
I followed the instructions and dirty flashed this thru TWRP as instructed which seemed to go ok until I tried to reboot, the phone booted to stock recovery so I wiped Dalvik, Cache and Factroy reset, this completed and it all went down hill from there, basically now just stuck at boot screen saying that its about to reboot but never moves unless I use button combos
(OK so yes I feel stupid now and I'll beat myself up so you don"t have to, but I reallyt thought that I could always get back to stock via my SDCard)
What I can do...
Phone can only boot to eRecovery ( with WIFI failed message )
I can go into fastboot ( shows Bootloader and FRP unlocked)
What i can't do...
Cant access my update file on SDCard....Trying to boot using vol+/- and power to access my dload/update.app file on my SDCard just freezes at initial boot screen and tells me to push vol up button for 3 second and this takes me to eRecovery where all i can do is reboot or shut down.
I can't adb sideload files " no SU Binary detected"
What I've tried...
I have tried Rayglobe knife UNBRICK option placing my extracted boot, cust, system, recovery .img files but his fails with my PC popping up and saying this operation can't be performed on this PC please contact developer so this fails.
I then tried to fastboot flash all the image files which seemed to work successfully but no changes to the situation.
I have tried to fastboot flash the update.app which went thru the sparse process of all seven files and then come up with error command can not complete ( something in those words)
I have tried to fastboot new stock recovery from my rom as well as TWRP recovery but nothing works even if it says seems to have completed in the adb command prompt.
I have a feeling this is to do with the encryption of the rom and now my system cannot recognise my partition and without recovery I have no way of mounting my sdcard.
Thank god I have my old and reliable Lumia 1520 to fall back on untill I get this sorted.
Any Help would be appreciated....thanks in advance
Click to expand...
Click to collapse
I have solved so
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
warsangel said:
I have solved so
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
Click to expand...
Click to collapse
A very big thanks ....this worked with no hitches except I now have no service now have to find unlock code for sim and get rid of the Ascend 7 splash screen that appears before the original Huawei Boot screen.?
After the above issues with thanks to warsangel's suggestion to use DC_Phoenix, I have managed to get my phone back up and running...got sim working so I now can detect my network and call and text using HCU client.
I now want to get rid of the annoying splash screen on bootup that shows Huawei Ascend spalsh screen before the mate 8 factory Huawei animated boot up screen. I still cannot access my dload folder on SDCard using vol-/+ and power button combo and if I dial in to manufacturers settings using*#*#2846579#*#* when i select upgrade from sd card i get a "PT failed do you still want to continue" if i click yes it re installs the firmware but makes no changes at all. Does any one have any other ideas. Of how to clear the splash screen and get the phone working back on Mate 8 button and bootup settings. Everything else works perfectly just a couple of things that will niggle at me...just want to get it back to out of the box as I have the Original Firmware zip file for this phone and region. cheers
bluheart said:
Are you able to boot into Huawei recovery?
Click to expand...
Click to collapse
Hi blueheart...no I can't, I think this is my problem, I can get to fast boot and I can't fastboot anything now because the boot loader is locked with a different code than the original one that I paid for with dc-unlocker. I have manged thru HCU cLIENT to get my original imei number and serial number but this serial number doesnt show up when I fastboot devices, lists one that come with the Phoenix firmware I flashed which is an Ascend as this was a NXT image closest to my NXT-L09.
My problem still is that I seem to go in to 2G and lose the signal all the time, I'm thinking I need to enter more details in CDMA repair in HCU Client or am I going about this the wrong way???
Oh bru, no idea!
HCU client is good enough. Keep trying dload if your bootloader is locked, it will flash for sure. Phone isn't easy to brick.
bluheart said:
Oh bru, no idea!
HCU client is good enough. Keep trying dload if your bootloader is locked, it will flash for sure. Phone isn't easy to brick.
Click to expand...
Click to collapse
Cheers Mate, managed to get to dload/update now but this doesnt seem to give a full reset, but modem is holding a signal but intermittently will drop into no service. I managed via HCU to re enter my imei and serial but a different serial number showsup in my settings still ??? getting back to where i need to but the signal dropping is a real problem. The next step is to try and get bootloader unlocked....any advice from any one.... if I fastboot flash modem will this be enough to bring my base band back or is there another file I should be looking at? cheers
You need to have cust and oem info of your own area for best signal
bluheart said:
You need to have cust and oem info of your own area for best signal
Click to expand...
Click to collapse
Thanks....I have my backup oeminfo it isnt a .img or .app file it just says oeminfo (type=file) can i fast boot this ? or do I have to use SRKtool as I don't want to unlock bootloader.
DC-Phoenix tool lets me fastboot .img files via backdoor and app files can I convert the oeminfo file to and .img file?
Cheers
How did you do the back up?
You can flash via fastboot
bluheart said:
How did you do the back up?
You can flash via fastboot
Click to expand...
Click to collapse
Backup was done through Rom Manager but the back up isn't an image it's a series of files like system.ext4, boot.emmc.win etc with MD5 info files. I've re-rooted device and tried to use rom manager to restore but when it boots to TWRP recovery nothing happens??? and I can't see any of the files if I go into the twrp folder on the SDcard because they aren't zip or img file.
My biggest problem even after doing full factory reset, wipe cache or install my original firmware update.app file, it doesn't seem to over write the image file that I used to recover my phone with the DC-Phoenix app, every thing indicates that it has been successful, but when I boot up,, It never goes to the stock setup mode where you would normally, choose your region, set your pin etc....it's like my install is only a shell or part of my install is not overwriting the dgtks firmware file I used which was a Huawei Ascend 7. The system re-defaults after rest to this firmware. Anyone help me to get rid of it and get back to my stock please?
I can use my stock update.app but it's not installing over the NXT AL10_M00A095_Factory_firmware_Android_6.0_EMUI_4.0.dgtks that I use ( this was the closest firmware that they had ) I think I need to format my whole system to ext4 ??? especially the partition that it storing this data that is preventing me to get my stock firmware back....any help or advice on this ...thanks
Yes format via Huawei recovery then flash
Or
Root and flash via TWRP after unzipping
bluheart said:
Yes format via Huawei recovery then flash
Or
Root and flash via TWRP after unzipping
Click to expand...
Click to collapse
just to update....I tried formatting and resetting all partitions to ext4 format most of the partitioning was successful with the exception of Systrem and Cust...TWRP would allow me to do these....I did numerous wipes via TWRP and Stock RECOVERY but unfortunately even with a full update.app via sdcard / dload folder and fastboot update.app (my firmware) via DC-Phoenix I couldn't seem to get a full factory stock install, same problems as discussed above and file system always goes to Encrypting screen and then I end up with the Ascend 7 screen and settings with obviously the wrong base band for my region. So I hate to admit defeat, but I've relocked bootloader, reset as much as I can and sent off to the Huawei Workshop to see if they can reset all the partitons back to normal.
Hahaha
Cool, let's see
bluheart said:
Hahaha
Cool, let's see
Click to expand...
Click to collapse
Update: well I dodged a bullet today....I sent my Mate 8 away 5 days ago to the Huawei tech support up the other end of the country and it arrived back today, back to stock and they replaced the main board with no cost to me at all. I was sure that they would call foul play and charge me but I obviously did such a number on the phone and then cleaned up all traces that they couldn't make that call lesson learn't and I see a few other people having similar problems with the Beta Nougat Rom....that you may need to post a big warning and send them to this posting so they are fair warned. I think this thread is done....I might just leave my phone alone and no tweaking for a while
Absolutely true!
XDA is not a playground for kids
You need courage to keep the Mate's balls on fire and get burnt with the nuclear reactions while keeping the blame on self
@Allooosh98 . I flashed this rom by full format in twrp but unable to open the phone. Just see a note7 logo and shutdown within 2 sec. Unfortunately i also lost the stock rom twrp backup from my SD card. Now please help what i will do..
Try here for a FAST download
http://updato.com/firmware-archive-select-model?q=j700h
Flash via Odin.
And keep another copy of your ROM backup on a pc / laptop
Good Luck!
But What happened? I keep my stock ROM backup by twrp recovery in my SD card then done wipe data - format - install custom ROM zip (855 MB ) from SD card. Got massage Successful after flash . But after reboot just showing the boot logo for a second and then gone. Even don't showing anything if i press power button. ** Unfortunately i lost the TWRP recovery stock ROM backup file from my SD card.** Also tried another Custom ROM ( J7(2015)_Stock_MM_Optimized_Rom_V3_Built_By_ @moluntic ) which don't have any bug, but it also acting same.. Can anyone please help what i did wrong and which will be the next action to see my phone alive? **** Experts please help me ****
Bappa89 said:
But What happened? I keep my stock ROM backup by twrp recovery in my SD card then done wipe data - format - install custom ROM zip (855 MB ) from SD card. Got massage Successful after flash . But after reboot just showing the boot logo for a second and then gone. Even don't showing anything if i press power button. ** Unfortunately i lost the TWRP recovery stock ROM backup file from my SD card.** Also tried another Custom ROM ( J7(2015)_Stock_MM_Optimized_Rom_V3_Built_By_ @moluntic ) which don't have any bug, but it also acting same.. Can anyone please help what i did wrong and which will be the next action to see my phone alive? **** Experts please help me ****
Click to expand...
Click to collapse
Say ur problem again completly
---------- Post added at 08:36 PM ---------- Previous post was at 08:29 PM ----------
tell me which varient is ur phone??
H/F/M ??
moluntic said:
Say ur problem again completly
---------- Post added at 08:36 PM ---------- Previous post was at 08:29 PM ----------
tell me which varient is ur phone??
H/F/M ??
Click to expand...
Click to collapse
My model is J700H . And after done a successful flash my phone shut down automatically when the model number appeared after reboot system. flash by TWRP recovery but somehow i lost the stock rom recovery file from my sd card. Now whats the way? Even i tried your rom but same output. Format all when wipe data in TWRP.
try flash stock firmware by odin.flash twrp.then flash any rom.just wait.do not do anything till phone boot.om sure u did soething wrong in instruction,so do this
I can't connect via USB as mtp
Just boot into download mood...nd install usb driver on pc and open odin choose stock firmware and flash
Hi guys i was trying to install a custom rom on my mate 9 (MHA-L29C432-156)so i followed the instructions ; unlocked the bootloader; then installed twrp 3.1.0-0; on twrp formated data; then full wiped and try to install AurRom from SD; but get a message that zip file is corrupted; so I tried with S.H.I.E.L.D ROM and it flashed , but then when boot goes to eRecovery, and give me 3 options download latest version and recovery; reboot and shutdown. So now I cant boot the phone, when I restarted, followed same steps , format data, full wipe and trying to installing again but getting a message about all zip files of the roms are corrupted; then i try to restore backup; and same again get the huawei logo, then the android logo , phone restarts and eRecovery again.
Please someone HELP, I use this phone for my work...........!!!!!!!!!
How did you full wipe?
Also try with Twrp 3.0.2-2
Here:www.androidfilehost.com/?fid=745425885120697579
dannytgt said:
on twrp formated data
Click to expand...
Click to collapse
Something went wrong here. You can run 'adb logcat' to see the crash details while starting.
If you have a backup on twrp then restore to get phone working. You may need to flash the public and hw-data zips afterwards though.
If you don't have a backup then you could try flashing the C636 off line firmware and then use firmware finder to go back to your original firmware
Sent from my MHA-L09 using XDA-Developers Legacy app
you may just flash the modified recovery ( See Guide subforum ) ) to bypass the update certification and authorization and reflash an original firmware. your stored files will be lost anyway in most cases.
I would bet superuser ( shield ) and SuperSU ( Aurom) messed your boot image. Both are incompatible to each other and, afaik both are incompatible to twrp 3.1.
Flash TWRP 3.0.2.2, reboot to recovery again to change version, flash the rom ( f.e. shield rom), boot once up, reboot to recovery and THEN you may flash twrp 3.1
Thanks all of you guys, I've solved the problem, it seems that's something related to the sd card, I've formated the sd and transfer the files trough another phone and then put the sd on the mate 9, I follow the steps as followed before and works successfully, now I'm on AurRom and 182 firmware.
I have European honor8 32gb b389
i install lineage os 7.1.2 but dont like it and wont do restore backup with twrp, but after restore the phone blocked on honor screen.
i tried everything, and now i have a lot of confusion, i tried dload, but nothing happened when i turn on with +-power. I try with huawai extractor to flash boot system cust and recovery but nothing device go in bootloop. if i flash recovery from b131 firmware i can go in dload but freeze at 5%
what i can do? sorry for my English, i speak Italian and Russian if somebody want to help me in pm.
crn4 said:
I have European honor8 32gb b389
i install lineage os 7.1.2 but dont like it and wont do restore backup with twrp, but after restore the phone blocked on honor screen.
i tried everything, and now i have a lot of confusion, i tried dload, but nothing happened when i turn on with +-power. I try with huawai extractor to flash boot system cust and recovery but nothing device go in bootloop. if i flash recovery from b131 firmware i can go in dload but freeze at 5%
what i can do? sorry for my English, i speak Italian and Russian if somebody want to help me in pm.
Click to expand...
Click to collapse
Are you sure you're using the rollback package before? You can download it from honor official website, then you move the firmware file in a dload folder on your sdcard. Boot up using both + and - buttons and the power button in the same time and the phone will force the flashing of the rollback ( package needed to go back from android 7 to android 6) file. Then you have to download the android 6 firmware for your device from the honor official website again and flash it with the same process of the rollback package. If you can't undestand i can try to explain it in italian
davide.melkior said:
Are you sure you're using the rollback package before? You can download it from honor official website, then you move the firmware file in a dload folder on your sdcard. Boot up using both + and - buttons and the power button in the same time and the phone will force the flashing of the rollback ( package needed to go back from android 7 to android 6) file. Then you have to download the android 6 firmware for your device from the honor official website again and flash it with the same process of the rollback package. If you can't undestand i can try to explain it in italian
Click to expand...
Click to collapse
thnx , i know this method, i tried it yesterday but don't worked, now i retry and reply to you the results
ok, i tried now the first update.app to rollback but device freeze (Your device is booting now)
i think i need to flash from fastboot stock recovery from b389 firmware before do this
crn4 said:
thnx , i know this method, i tried it yesterday but don't worked, now i retry and reply to you the results
Click to expand...
Click to collapse
Unless you flash the rollback package you can't flash older version. Not sure if rollback package for your model os released
---------- Post added at 03:50 PM ---------- Previous post was at 03:49 PM ----------
crn4 said:
thnx , i know this method, i tried it yesterday but don't worked, now i retry and reply to you the results
ok, i tried now the first update.app to rollback but device freeze (Your device is booting now)
i think i need to flash from fastboot stock recovery from b389 firmware before do this
Click to expand...
Click to collapse
Ofcourse you need to flash the stock recovery. Are you trying in twrp?
davide.melkior said:
Are you sure you're using the rollback package before? You can download it from honor official website, then you move the firmware file in a dload folder on your sdcard. Boot up using both + and - buttons and the power button in the same time and the phone will force the flashing of the rollback ( package needed to go back from android 7 to android 6) file. Then you have to download the android 6 firmware for your device from the honor official website again and flash it with the same process of the rollback package. If you can't undestand i can try to explain it in italian
Click to expand...
Click to collapse
shashank1320 said:
Unless you flash the rollback package you can't flash older version. Not sure if rollback package for your model os released
---------- Post added at 03:50 PM ---------- Previous post was at 03:49 PM ----------
Ofcourse you need to flash the stock recovery. Are you trying in twrp?
Click to expand...
Click to collapse
yes i tried to flash twrp with fastboot but cant reboot the phone in twrp recovery
crn4 said:
yes i tried to flash twrp with fastboot but cant reboot the phone in twrp recovery
Click to expand...
Click to collapse
Flash stock recovery and try
shashank1320 said:
Flash stock recovery and try
Click to expand...
Click to collapse
yes i tried a lot of times, i have huawei tool, i tried now another time, but with the tool can't reboot in twrp, and with power and+ also
crn4 said:
yes i tried a lot of times, i have huawei tool, i tried now another time, but with the tool can't reboot in twrp, and with power and+ also
Click to expand...
Click to collapse
Are you able to get into the bootloader?
shashank1320 said:
Are you able to get into the bootloader?
Click to expand...
Click to collapse
what do you mean?
in fastboot (- and pw) i have PHONE unlocked and FRP unlocked
crn4 said:
what do you mean?
in fastboot (- and pw) i have PHONE unlocked and FRP unlocked
Click to expand...
Click to collapse
Just flash the stock recovery there in fastboot. And reboot. Shutdown the phone and use dload method
Basically you missed one thing before restoring stock backup. You should have performed a full factory reset using the second recovery and then restored your TWRP backup.
Your device being stuck on Honor screen is because you forgot to enable encryption (that is done by performing a factory wipe through second recovery).
shashank1320 said:
Just flash the stock recovery there in fastboot. And reboot. Shutdown the phone and use dload method
Click to expand...
Click to collapse
I tried flash stock recovery from different firmwares and after try with dload, but dont work, the device freeze e dont wont boot dload, with recovery from b131 firmware (MM) the dload go on but freeze at 5%, now i try with b389 (Nougat) fw, within 15 minutes I tell you the result
hackslash said:
Basically you missed one thing before restoring stock backup. You should have performed a full factory reset using the second recovery and then restored your TWRP backup.
Your device being stuck on Honor screen is because you forgot to enable encryption (that is done by performing a factory wipe through second recovery).
Click to expand...
Click to collapse
Ahhh ok, and now for recover my phone what i need to do ?
now i flashed boot, cust , recovery and system from b389 firmware but nothing, the phone dont boot, dont want to dload, i dont know what to do....
crn4 said:
Ahhh ok, and now for recover my phone what i need to do ?
Click to expand...
Click to collapse
Follow my guide here https://forum.xda-developers.com/honor-8/how-to/guide-flashing-unapproved-firmwares-t3668306
Before you do it, flash stock Nougat recovery (if you were on EMUI 5) and perform a factory reset. Then flash TWRP again through Fastboot.
Use the TWRP method since you are unable to boot to EMUI. Chose any firmware you want, whether it be Marshmallow or Nougat.
hackslash said:
Follow my guide here https://forum.xda-developers.com/honor-8/how-to/guide-flashing-unapproved-firmwares-t3668306
Before you do it, flash stock Nougat recovery (if you were on EMUI 5) and perform a factory reset. Then flash TWRP again through Fastboot.
Use the TWRP method since you are unable to boot to EMUI. Chose any firmware you want, whether it be Marshmallow or Nougat.
Click to expand...
Click to collapse
i flashed stock recovery from you guide but i cant boot in recovery, i flashed different recoverys, from MM to Nougat but nothing i think this is bootloader problem
edit:
in fastboot i see this
ap_s_abnormal na
what is the signification?
crn4 said:
i flashed stock recovery from you guide but i cant boot in recovery, i flashed different recoverys, from MM to Nougat but nothing i think this is bootloader problem
edit:
in fastboot i see this
ap_s_abnormal na
what is the signification?
Click to expand...
Click to collapse
Are you following the steps exactly as mentioned?
You need to flash TWRP first then setup your device to install the firmware. Read the TWRP section again and follow it exactly as mentioned.
Nothing to worry about that Fastboot status. It is normal.
SOLVED!!!!!! thanks at all people, and very sorry for my English,
i relock end unlock boot loader many times and i flash every is flashable from firmware b131 (boot, system......) and whola!!!! the system dont boot but the dload after this has been restored to work, now i update to last fw and root and dont touch more nothing =D
crn4 said:
SOLVED!!!!!! thanks at all people, and very sorry for my English,
i relock end unlock boot loader many times and i flash every is flashable from firmware b131 (boot, system......) and whola!!!! the system dont boot but the dload after this has been restored to work, now i update to last fw and root and dont touch more nothing =D
Click to expand...
Click to collapse
Damn. I forgot you could simply flash files from Fastboot.
In the future only flash system, cust, vendor, boot and recovery. Do not attempt to flash any other file.
Still, if you want to update to the latest OTA, my guide is always there to help you out.
hackslash said:
Damn. I forgot you could simply flash files from Fastboot.
In the future only flash system, cust, vendor, boot and recovery. Do not attempt to flash any other file.
Still, if you want to update to the latest OTA, my guide is always there to help you out.
Click to expand...
Click to collapse
now i have another problem, i tried to update with stock updator, but from 6 to 7 go wrong, device boot but dont work right, the keyboard dont exist and other lags, try to factory reset but error. after this i flash twrp and format data but see this : failed to mount /cust /system /data; repair or change file system do the same.
if i flash with dload b131 the phone freeze on honor screen
Hello,
I recently got my new Mate 10 Lite and wanted to debrand it, update to Oreo, root and install useful Magisk plugins. Everything went fine and I got my phone debranded from C738 to C432, then I updated to Oreo B330 and tried to root. Couldn't succeed with dry Magisk 16.6 install, so I installed 16.0. Decided to give 16.6 a shot one more time but the story went the same, no 16.6 was installed and Magisk Manager had weird, arabic-like layout (inverted), so I wanted to patch boot image with 16.0 once again in order to clear all the "leftovers" 16.6 could leave. Unfortunately, after this operation my phone got softbricked, constantly entering ERROR MODE trying to boot both system and recovery, getting respectively Func NO 10 and 2 (boot image load failed!) and Func NO 11 and 2 (recovery image load failed!). I hoped that maybe I could just recover via TWRP installing it once again, but, unfortunately, it wasn't a thing and I couldn't boot anyway. I was, of course, installing Mate 10 Lite Oreo version of TWRP. HwOTA 8 doesn't help as well. dload update leaves me with crash at 5%. Any hopes for my baby, or only locking a bootloader and sending on warranty will do (if they even accept it)?
Thank you in advance,
Seven-
EDIT: Fixed. Just had to reflash kernel.img. As simple as that. Seems much more harder, doesn't it?
So here's a quick solution:
1. Go here: http://pro-teammt.ru/firmware-database/ Download Firmware Finder, search for Oreo ROM for your specific phone model and codename
2. Find update.zip. Unzip it and put UPDATE.APP to Huawei Update Extractor
3. Extract kernel.img and flash it via fastboot - "fastboot flash kernel kernel.img"
4. Reboot, should work from now.
This is solution for Oreo as I think it's a problem specific for Oreo because this partitioning system, but if you experience such problem with Nougat, download Nougat ROM and change all "kernel" words to "boot".
Hope you have a nice day, I'm glad that I might have helped a few of fellow Mate 10 Lite users
you can enter in recovery mode true?
try rebrand your device to stock and download the stock rom to flash via HwOTA or dload.
Can boot only to stock recovery, dload and fastboot. As I said, I rebranded to C432 and did it successfully and installed ROM for this version. I tried flashing both Nougat I used to rebrand and Oreo, both crash at 5% when flashing via dload, HwOTA doesn't work as it flashes TWRP you have to boot into, and I can't enter TWRP because I get Func NO 11 and 2 (recovery image load failed!). I tried 2 different TWRPs, this one from HwOTA and Azan Mughal's version. Neither of them works. Nougat versions don't even flash properly, which is normal because I "have" Oreo
Well, I might just say that this is the toughest phone I have ever been modding. I have just noticed that plugging the phone to charger also makes it enter ERROR MODE, which is also normal in this situation as boot image fails to load.
Just thinking... Might it be that recovery and boot partitions are somehow unformatted? I have no other idea why would recovery boot fail when installed. But on the other hand if it was unformatted it would either format it properly or not install at all, right?
EDIT: Tried to erase recovery but "Command not allowed".
I've got the exact same problem except dload because I don't know how to do that.
dload works with emui 4.x
It should always work. It's there for a reason, isn't it?
I might have discovered why am I getting boot and recovery failures. Obviously having Oreo there are no boot and recovery partitions but recovery_ramdisk and I think kernel (notsure) instead. I only have a question how do I repartition mobile device? There must be a way, right?
Like MTK-based devices have SP Flash Tool.
One click away from pushing all the files from UPDATE.APP from stock Oreo through Fastboot, is it safe enough? I mean, what if, for example, fastboot.iso fails to write or is corrupted, completely bricked phone?
Never been so scared modifying a phone, this one is so tough to mod and soft at once...
Can't boot to system, recovery, installing through dload crashes at 5%
i am in same problem plz developers do some work on these issues of this device to get back our devices thanks.
i have tried many mehods (dload, update. app, update. zip etc...... 1 different problem i got is when fladhing boot. img or recovery. img using cmd fastboot flash boot boot. img
failed remote; partition get size error.
---------- Post added at 09:17 PM ---------- Previous post was at 09:13 PM ----------
SevenUp9 said:
It should always work. It's there for a reason, isn't it?
I might have discovered why am I getting boot and recovery failures. Obviously having Oreo there are no boot and recovery partitions but recovery_ramdisk and I think kernel (notsure) instead. I only have a question how do I repartition mobile device? There must be a way, right?
Like MTK-based devices have SP Flash Tool.
Click to expand...
Click to collapse
keep searchig
@BaBa Yoga, you have Oreo, right? Try installing proper TWRP for 8.0 then and flash it as recovery_ramdisk instead, because it's how do partitions on Oreo look like. But I doubt it changes anything and makes your phone alive again.
FIXED IT, FIXED IT!!! Reflashed kernel and it works. Guys up here, you might want to try this out. As I thought, Magisk must have messed up with my boot file.
Adding solution to the main post.
SevenUp9 said:
@BaBa Yoga, you have Oreo, right? Try installing proper TWRP for 8.0 then and flash it as recovery_ramdisk instead, because it's how do partitions on Oreo look like. But I doubt it changes anything and makes your phone alive again.
Click to expand...
Click to collapse
yes oreo.... i am still trying twrps of azan mughal and other twrp for my device but now when i install custom recovery {fastboot flash recovery_ramdisk recovery. img}
it shows ok but when i reboot device in recovery mode there is no twrp recovery....... only stock recovery
---------- Post added at 10:02 PM ---------- Previous post was at 09:55 PM ----------
SevenUp9 said:
FIXED IT, FIXED IT!!! Reflashed kernel and it works. Guys up here, you might want to try this out. As I thought, Magisk must have messed up with my boot file.
Adding solution to the main post.
Click to expand...
Click to collapse
great bro....
plz share info here how to reflash kernal
@BaBa Yoga, I posted simple walkthrough in the first post, if you ever need explanation just ask here, I'll try to be more detailic then. Good luck unbricking your phone bro :victory:
SevenUp9 said:
Hello,
I recently got my new Mate 10 Lite and wanted to debrand it, update to Oreo, root and install useful Magisk plugins. Everything went fine and I got my phone debranded from C738 to C432, then I updated to Oreo B330 and tried to root. Couldn't succeed with dry Magisk 16.6 install, so I installed 16.0. Decided to give 16.6 a shot one more time but the story went the same, no 16.6 was installed and Magisk Manager had weird, arabic-like layout (inverted), so I wanted to patch boot image with 16.0 once again in order to clear all the "leftovers" 16.6 could leave. Unfortunately, after this operation my phone got softbricked, constantly entering ERROR MODE trying to boot both system and recovery, getting respectively Func NO 10 and 2 (boot image load failed!) and Func NO 11 and 2 (recovery image load failed!). I hoped that maybe I could just recover via TWRP installing it once again, but, unfortunately, it wasn't a thing and I couldn't boot anyway. I was, of course, installing Mate 10 Lite Oreo version of TWRP. HwOTA 8 doesn't help as well. dload update leaves me with crash at 5%. Any hopes for my baby, or only locking a bootloader and sending on warranty will do (if they even accept it)?
Thank you in advance,
Seven-
EDIT: Fixed. Just had to reflash kernel.img. As simple as that. Seems much more harder, doesn't it?
So here's a quick solution:
1. Go here: Download Firmware Finder, search for Oreo ROM for your specific phone model and codename
2. Find update.zip. Unzip it and put UPDATE.APP to Huawei Update Extractor
3. Extract kernel.img and flash it via fastboot - "fastboot flash kernel kernel.img"
4. Reboot, should work from now.
This is solution for Oreo as I think it's a problem specific for Oreo because this partitioning system, but if you experience such problem with Nougat, download Nougat ROM and change all "kernel" words to "boot".
Hope you have a nice day, I'm glad that I might have helped a few of fellow Mate 10 Lite users
Click to expand...
Click to collapse
bro i did not find firmware for my region i. e RNE L21 C185..... I FOUND DOME FIRMWARES on other sites one of thek i extract update. app using huawei updates extractor but there is no kernal.img file..... i found i. gs of boot, system, recovery, cust etc but no kernal. img what i do.....
You downloaded Nougat then, and you have to download Oreo that ends with B3xx, in your case then it will be RNE-L21C185B3xx There must be Oreo for C185, I know that because I was looking at C185 too when I was rebranding but then I noticed that C432 is what I should install for my region.
http://pro-teammt.ru/firmware-database/?firmware_model=rne-l21c185B3 - these are all the official Oreo builds for your specific region. I think all of them should do, I am certain that all the kernels in these packages are similar. Eventually you can just flash another one later
SevenUp9 said:
You downloaded Nougat then, and you have to download Oreo that ends with B3xx, in your case then it will be RNE-L21C185B3xx There must be Oreo for C185, I know that because I was looking at C185 too when I was rebranding but then I noticed that C432 is what I should install for my region.
[m/?firmware_model=rne-l21c185B3[/url] - these are all the official Oreo builds for your specific region. I think all of them should do, I am certain that all the kernels in these packages are similar. Eventually you can just flash another one later
Click to expand...
Click to collapse
should i download OTA-MF or FULLOTA-MF?
I Hope i could find kernal file now....
i am downloading FULLOTA-MF thanks to provide me firmware list of my region
thanks sevenup9 for getting back my device out of that problem i flash the kernel successfully wnd get back my twrp as well now what next..???????? thanks again
---------- Post added at 06:54 AM ---------- Previous post was at 06:01 AM ----------
i flashed kernel. img, cust. img, system. img and then reboot now i have twrp but still in bootloop what next
Yeah, good that you downloaded FullOTA, as it's a full system image. I assume there is no system.img or kernel.img in OTA package at all.
Since you have TWRP now but stuck in bootloop, try to wipe data and cache and try to boot again. If you don't succeed, then maybe try getting all of the 3 zips from FullOTA package on SD card (or USB stick if you have a USB OTG cable) and flash them via TWRP, starting from "update.zip". Should work just fine. Maybe your phone got more partitions messed up, but that should be recoverable as you have a good base being able to boot into TWRP
SevenUp9 said:
Yeah, good that you downloaded FullOTA, as it's a full system image. I assume there is no system.img or kernel.img in OTA package at all.
Since you have TWRP now but stuck in bootloop, try to wipe data and cache and try to boot again. If you don't succeed, then maybe try getting all of the 3 zips from FullOTA package on SD card (or USB stick if you have a USB OTG cable) and flash them via TWRP, starting from "update.zip". Should work just fine. Maybe your phone got more partitions messed up, but that should be recoverable as you have a good base being able to boot into TWRP
Click to expand...
Click to collapse
i did usb mathed as well but when flash update. zip via twrp error 9 shows
---------- Post added at 10:10 AM ---------- Previous post was at 10:06 AM ----------
then usi g fastboot i flash recovery_ramdisk kernel cust system ramdisk all these images..... now reboot and i lost twrp and it replaced with stock recovery.... in stock recovery i wiped cache... done... wipe data and factory reset..... stuck at 0% after 10 minutes... plz bro
---------- Post added at 10:12 AM ---------- Previous post was at 10:10 AM ----------
i didn't lock bootloader yet... i keep it still unlock