Related
Hi!
This morning I updated supersu binaries via CWM, beacuse "normal" upgrade didn't work.
Now the phone is stucked with the boot logo animation.... I tried to clear the dalvik cache, but I don't understand very well what is going on...
I neither know if the un-brick procedures applies to me, because I didn't ugpraded the EMUI
Any ideas?
Thanks in advance and sorry for my poor english
Follow this procedure to get your phone back to stock:
Download your phone's latest firmware and extract system.img, boot.img, recovery.img, cust.img from UPDATE.APP using Huawei Update Extractor tool.
Boot into bootloader mode by switching off the phone then pressing only the Vol DOWN button, and connecting it to PC simultaneously.
Flash recovery first, using this command.
Code:
fastboot flash recovery recovery.img
Flash all other extracted files similarly firing these commands.
Code:
fastboot flash boot boot.img
fastboot flash cust cust.img
fastboot flash system system.img
After doing this put that very UPDATE.APP from which you extracted the files in dload folder of your external SDCARD.
Switch off your phone, and press Vol UP + Vol DOWN + Power button simultaneously.
Your device will now get to the full stock firmware.
NOTE: If the manual flashing doesn't works or you get any errors, then first try only the force update method, i.e Putting the UPDATE.APP from which you extracted the files in dload folder of your external SDCARD and pressing Vol UP + Vol DOWN + Power button simultaneously after switching off your phone.
Thank you.
Is there no other way to "revert" SuperSU changes?
I guess something went wrong with that. I have same problem, but I did not update SuperSU, i just installed it and choose to clear dalvik cache.
atarifreak said:
Thank you.
Is there no other way to "revert" SuperSU changes?
I guess something went wrong with that. I have same problem, but I did not update SuperSU, i just installed it and choose to clear dalvik cache.
Click to expand...
Click to collapse
Install an older version of SuperSU, like 2.51 or 2.62.
Don´t clean cache or Dalvik after install.
It might do a couple or reboots, just wait.
atarifreak said:
Thank you.
Is there no other way to "revert" SuperSU changes?
I guess something went wrong with that. I have same problem, but I did not update SuperSU, i just installed it and choose to clear dalvik cache.
Click to expand...
Click to collapse
If you have a twrp backup restore only system. Or maybe try flashing only system img from fastboot. Worked for me.
goldfinv said:
If you have a twrp backup restore only system. Or maybe try flashing only system img from fastboot. Worked for me.
Click to expand...
Click to collapse
Thank you.
older SuperSU does not work. I think it iss because of Android 6.
I need some sort of boot.img patching...
I reflashed system.img from huawai extract and all fine (except of rooting...)
Okay cool. I rooted by flashing SU 2.47 and was able to update from play store. Which I don't recommend. Just root and stick to that SU version
well, rooting without working supersu.zip - flash would be great, but I dont get it with Android 6.
no Problem with Android 5.1
And I dont want to use some strange chinese tool (that does not support honor 6 plus any more).
So you got Android 6 and root with Honor 6plus?
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
Hello there, I've been trying to return to stock EMUI after messing around with some AOSP-based ROMs, but my US model Honor 6x is unable to boot up the TWRP backup of it. And the dload method is unsuccessful, as it just says the firmware is incompatible with my device. Does anyone know a way to return back to stock EMUI and make my device as it was coming out of the factory?
Rommco05 said:
Hi, which is your model number...BLxLxxCxxx? Still you have access to twrp?
Click to expand...
Click to collapse
I believe it's the BLN-L24C567, since I have the US model of the Honor 6x.
Rommco05 said:
Ok, can you flash back twrp?
Click to expand...
Click to collapse
I still have TWRP and the backup of my original software, but it won't boot up. It just goes into a boot loop. I don't know what proper steps to take in order to get the software to boot up again.
Rommco05 said:
Ok, download this two zips and try flash via twrp. First small zip, right after big one. After go to reboot and make reboot recovery, now you will be in stock recovery and here tap factory reset, after normal reboot and should boot to rom
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1279/g104/v82815/f1/full/update.zip
http://update.hicloud.com:8180/TDS/...24_hw_usa/update_data_full_BLN-L24_hw_usa.zip
Click to expand...
Click to collapse
Thank you so much; I'll do it. However, should I do a factory reset or format data in TWRP before flashing these ZIPs?
Rommco05 said:
No, no need be wiped anything
Click to expand...
Click to collapse
The update.zip (the bigger one) ended with "ERROR: 7" I'm not sure if this should have happened or not. Any idea?
Rommco05 said:
Try format data after reboot twrp and again format data now try flash zips.
If this doesn't help, u need this one:
-download Huawei Extractor from xda
-unzip big zip and extract from update.app, recovery.img
-flash recovery.img over fastboot (fastboot flash recovery recovery.img)
-now make update over dload method
(unzip both files and separately put to dload folder on sdcard, first big second small, but must be unzipped)
Click to expand...
Click to collapse
Okay, one more question: For the dload method, do I have both ZIPs in the dload folder and flash it at the same time, or do I flash one ZIP at a time in the stock recovery?
Rommco05 said:
Yes u need install both zips, becasue big one is system and small are apps. Flash stock recovery and after install big one (unzipped) after reboot (if phone boot to rom immediately turn him off) and install second one, same like first
Click to expand...
Click to collapse
My phone is currently installing the first UPDATE.app. Once I go back into the recovery, will my phone know to install UPDATE.APP(1) (the smaller one)? Or will there be a way to select the file? How exactly does it work?
Rommco05 said:
No you need deleted first one from dload and put in second one (small)
Click to expand...
Click to collapse
Sorry to keep asking questions, but how should I turn off the device once the first UPDATE.APP installs? It keeps trying to boot up.
Rommco05 said:
Leave him try boot to rom, should be boot in but rom will be incomplete and after turn him off
edit: if will be booting more like 10 min boot to recovery and here remove sdcard
edit1: hopefully will be all ok, I going slowly sleep
Click to expand...
Click to collapse
Thanks for those edits; I was a bit confused. Thank you for all your help; I'll update you if it works or not. Have a nice night.
I just wanted to leave a reply to let others know what I did:
1. Flashed stock recovery from the big update.zip file (I used the Huawei extractor to get it from the file)
2. Unzipped the big and little zip files
3. Made a folder called dload
4. Put the unzipped contents of the big zip in the dload folder
5. Held power and volume up + down buttons until it installed the big update file
6. I went into the recovery by holding volume up and power
7. I removed the SD card and deleted the contents of the big update and inserted the little update to the dload folder
8. I rebooted and used the same dload method to install the contents of the little update file
9. I went back into the recovery (power and volume up) and did a factory reset
10. I rebooted and everything worked!
11. Installed the intermediate package first and then the official 6.0 software through the dload method
12. Upgraded back to Nougat via the Marshmallow build
Rommco05 said:
Leave him try boot to rom, should be boot in but rom will be incomplete and after turn him off
edit: if will be booting more like 10 min boot to recovery and here remove sdcard
edit1: hopefully will be all ok, I going slowly sleep
Click to expand...
Click to collapse
Thank you for all your help! Seriously, I couldn't have done it without you!
Rommco05 said:
Leave him try boot to rom, should be boot in but rom will be incomplete and after turn him off
edit: if will be booting more like 10 min boot to recovery and here remove sdcard
edit1: hopefully will be all ok, I going slowly sleep
Click to expand...
Click to collapse
The only unfortunate thing was that I received a Nougat beta built, but I think I'll be able to find a finalized version online.
Rommco05 said:
You stuck in beta version? Now you have already instaled stable version
Click to expand...
Click to collapse
I just installed the files from Honor's site (the intermediate package and the 6.0 firmware) and went back to the official Marshmallow build and then upgraded to the official Nougat release. Everything is all good now!
That's good
Hello, I would like some help since I got this device just yesterday.
I got it with the EMUI 4 Android 6.0 stock installed on it. Since there was no update for it I unlocked the bootloader installed twrp rooted and manually flashed EMUI 5 7.0. Everything worked fine.
I created a backup through TWRP and restored it succefully multiple times.
Then I installed the Meticulus TWRP (since I was told it is a prerequisite for the AOSP). I Flashed the AOSP but it stuck during the boot animation (30 minutes afterwards I powered it off).
I reflashed my old TWRP and tried restoring my backup. IT fails with the explanation "Cannot wipe /vendor" while at the top it says "Cannot mount /vendor (invalid argument)" "Cannot mount /product (invalud argument)".
Anyone has a clue how to fix this? Fastboot adb all works so there should be a way to boot into an OS properly?
Since AOSP was not booting i guess you forgot formatting /data partition to ext4... And did u Used Stock vendor and not openkirin ones ?
Gesendet von meinem Honor 6X mit Tapatalk
As said I have replaced the custom TWRP with the default one so I think this should not apply anymore?
The "cannot mount vendor/product" messages came from the default TWRP after I reflashed it again.
At the top it says "cannot mount /vendor" either so I guess that is the actual problem?
It would be nice to get teh AOSP up but I really want to be able to boot into something first honestly.
And did u Used Stock vendor and not openkirin ones
Click to expand...
Click to collapse
Can you please explain? When I flashed your ROM i was on your TWRP. Does this even matter anymore?
At best I would be able to restore my backup.
To me it appears to be caused by the vendor partition.
Is there any way I can manually create that through TWRP?
algg said:
To me it appears to be caused by the vendor partition.
Is there any way I can manually create that through TWRP?
Click to expand...
Click to collapse
Yes you can but not creating it through twrp, but flashing it by fastboot mode: this is because
image (.img) files needs to be flashed by fastboot mode to avoid any kind of problem.
So, you should look for the last version of stock firmware on which you was before going custom, like BLN-L21CXXXB368 for example; tell me your build number and I'll find the package for you. Then, extract from the UPDATE.APP (a very big file that contains every partition in your phone like recovery, vendor, data, ecc. - you'll find this file inside the zip archive that contains the downloaded update) the vendor.img using Huawei Update Extractor, and then flash it through fastboot mode using the command "fastboot flash vendor vendor.img".
Otherwise, you could rely on dload method to reflash a full update package, and this should really fix everything since that it'll be like a new and clean installation of the OS. Then, unlocking the bootloader again and reflash TWRP to finally restore your previous backup made when it was working would be the final step.
Feel free to ask for further help
Thanks for the reply first really appreciate it.
I got the device on EMUI 4 Marshmallow rooted it and unlocked the bootloader then installed the BLN-L21C185B140 which worked smoothly.
I used that update.zip and extracted into dload root folder and started the huawei recovery installer but it said "package not found".
I tried flashing something to vendor before with fastboot but it said command not allowed.
Maybe I am doing something wrong?
algg said:
Thanks for the reply first really appreciate it.
I got the device on EMUI 4 Marshmallow rooted it and unlocked the bootloader then installed the BLN-L21C185B140 which worked smoothly.
I used that update.zip and extracted into dload root folder and started the huawei recovery installer but it said "package not found".
I tried flashing something to vendor before with fastboot but it said command not allowed.
Maybe I am doing something wrong?
Click to expand...
Click to collapse
Latest build on Nougat after the update was BLN-L22C185B140 so? If yes, the package that you need to download is that one. Unluckily i can't help about dload method, i never had fortune using dload because package verification always failed at 5%, i tried every combination but without success.
Command not allowed while flashing vendor image... but flashing others, like recovery or boot.img is allowed? If yes, i don't know what's causing this sorry... I'm sure that my friend @shashank1320 could surely help more than me about how using dload method correctly. Check his signature, it should contain a guide on how to use it
RedSkull23 said:
Latest build on Nougat after the update was BLN-L22C185B140 so? If yes, the package that you need to download is that one. Unluckily i can't help about dload method, i never had fortune using dload, i never be able to using it successfully because package verification always failed at 5%.
Command not allowed while flashing vendor image... but flashing others, like recovery or boot.img is allowed? If yes, i don't know what's causing this sorry... I'm sure that my friend @shashank1320 could surely help more than me about how using dload method correctly. Check his signature, it should contain a guide on how to use it
Click to expand...
Click to collapse
For fastboot yes flashing recovery or boot do work but vendor does not. Maybe the ISO is corrupted somehow I will try it again on a different machine now with the tool.
The link you posted the dload method from is the one where I initially found it as well so yea.
Also it shouldn't matter what I install since the only thing I need is the actual vendor (and product?) partition to work. I have a functional backup just TWRP cannot create/mount the partitions. So even a way to just create them without any data would actually fix my problem (at least I hope so?)
When trying to use Fastboot to flash the vendor/product img I get remote: Command not allowed (yes my bootloader is unlocked) although I can flash the recovery without any problem.
The dload method does not work as said. I placed the extracted content of the update.zip into the dload folder but the software "cannot find" the package.
algg said:
When trying to use Fastboot to flash the vendor/product img I get remote: Command not allowed (yes my bootloader is unlocked) although I can flash the recovery without any problem.
The dload method does not work as said. I placed the extracted content of the update.zip into the dload folder but the software "cannot find" the package.
Click to expand...
Click to collapse
@RedSkull23, thanks for the tag mate.
@algg, No need to flash the vendor image as you already had the stock vendor img.
Now what else you can try is to flash the stock recovery, boot to stock recovery, select factory reset and reboot. It should most probably fix the issue.
If not, reflash the TWRP, a regular TWRO available and not specific to elite or meticulous, but generic one given by OldDroid.
I hope you have downloaded the content for dload, if not, download these for B140.
Flash this via TWRP- http://update.hicloud.com:8180/TDS/...afnaf/update_data_full_BLN-L21_hw_meafnaf.zip
no further changes and Then use dload method for this file- http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1756/g1755/v105054/f1/full/update.zip
Try above and provide feedback. This is what I could think of best possible way to have everything with all system app working.
If not, let me know and I will try to help further.
Hi, I thought I need the vendor image since TWRP (all versions) tell me "Could not mount/wipe vendor" and "Could not mount/wipe product" "invalid argument" for both.
I tried the factory reset before but it does not work. It stops at 23% then shows a red exclamation mark and just goes to the original screen with the 3 buttons (restart, shutdown and wipe).
I am currently trying to get it to recognize my sd card. But somehow it does not work through TWRP it just does not recognize the 8GB SD Card. Also I am currently on the TWRP I was before all of this happened (3.1 openkirin). Without the SD Card recognized I can't put the dload files for it on it and in turn I can't use the dload.
I mean technically it should very well be possible to fix the device since it isn't a real brick and even TWRP and Fastboot load. It's just that all those little things are somehow ruining it.
Edit: I will get a new micro sd for some reason this one does nt work. I'll say then whether the flash then dload worked.
@shashank1320
Mind explaining why I should first use TWRP to flash something and then on top of it use dload?
And why those specific files?
algg said:
Edit: I will get a new micro sd for some reason this one does nt work. I'll say then whether the flash then dload worked.
@shashank1320
Mind explaining why I should first use TWRP to flash something and then on top of it use dload?
And why those specific files?
Click to expand...
Click to collapse
Sure, let me explain.
The first file is the data file which will install few systems apps like file manager, updater, themes, clock, fm radio etc. This will work via dload as well but the installation time is around 3-7 seconds so, over the course of time and flashing few times, i realised that these PV files cannbe flashed via TWRP and it works perfectly fine specific to PV files( twrp won't supoort other stock zips). We foash this first so that it updates your buld number and also does not replace the recovery with stock (as if you flash the main update zip first, it will replace with stock recovery so flashing the 2nd file will be quick but with unstable system apps, sometime).
Now we flash the main zip file with update.app via dload and it Install the main firmware for boot, vendor, recovery, system, usrdata etc.
Hope this explanation helps, if not let me know and I will rephrase myself.
It does help. I did all of this and now in the dload app I get "Software install failed Incompatibilty with current version please download the correct update package".
When I flashed the zip you linked me with TWRP it said "cannot mount /data /vendor /product". Appearently data cannot be mounted since it is encrypted.
Any clue as to what I am doing wrong? Or is this device now a real brick with functioning recovery but without OS?
Is there any way I can "debug" what is going on while the boot animation is playing?
What is confusing me is that the boot animation plays just normal but it simply does not continue to the actual OS.
algg said:
It does help. I did all of this and now in the dload app I get "Software install failed Incompatibilty with current version please download the correct update package".
When I flashed the zip you linked me with TWRP it said "cannot mount /data /vendor /product". Appearently data cannot be mounted since it is encrypted.
Any clue as to what I am doing wrong? Or is this device now a real brick with functioning recovery but without OS?
Click to expand...
Click to collapse
Not bricked..its just Data is not mounted or encryption. Should never encrypted it. NVM.
Do one thing, boot to twrp recovery. Try flashing and get error, then go to main TWRP page and click on reboot, select recovery out of 4 options( power off, system, bootloader and recovery). It will boot to recovery, now try flashing it again and see. Most if the time it helps.
Else, go to main page, select wipe, click on format rather than wipe here, it will prompt for typing Yes to confirm. Biit to recovery from main twrp page ( as mentioned above). And try this same thing of formatting data couple of times and then flash the zip and then dload.
I know these are tedious steps but inhave revived my device many a times with all these tricks after some efforts.
Good luck
YAY it works.
Just to recap what I did:
I flashed your thing first through TWRP tried to flash your other link with dload (which did NOT work)
Then I flashed the thing (emui5 Android 7 for Europe) through TWRP played in my old backup of exactly this through TWRP cleared dalvik & cache.
Then I waited 20 minutse and now it started.
Really thanks to all of you very nice people here. I would be very baffled if it wasnt able to repair the device since Fastboot and Recovery still work.
But Huaweis recovery is beyond terrible.
algg said:
YAY it works.
Just to recap what I did:
I flashed your thing first through TWRP tried to flash your other link with dload (which did NOT work)
Then I flashed the thing (emui5 Android 7 for Europe) through TWRP played in my old backup of exactly this through TWRP cleared dalvik & cache.
Then I waited 20 minutse and now it started.
Really thanks to all of you very nice people here. I would be very baffled if it wasnt able to repair the device since Fastboot and Recovery still work.
But Huaweis recovery is beyond terrible.
Click to expand...
Click to collapse
It is terrible indeed. Glad your phone working.
Thanks to @RedSkull23 for tagging, else I may have not responded as he was already involved and was helping as usual.:good:
algg said:
Really thanks to all of you very nice people here. I would be very baffled if it wasnt able to repair the device since Fastboot and Recovery still work.
But Huaweis recovery is beyond terrible.
Click to expand...
Click to collapse
I'm happy for you man, indeed it would be so bad, especially because you got this device 3 or 4 days ago if i didn't read bad, anyway what matters is that now it works. Are you able to restore the previous backup through TWRP now? (But before trying... Make a backup of your actual OS )
shashank1320 said:
It is terrible indeed. Glad your phone working.
Thanks to @RedSkull23 for tagging, else I may have not responded as he was already involved and was helping as usual.:good:
Click to expand...
Click to collapse
Are you joking man? I just tagged you for more help, but practically you helped him in everything, not me; I'm sure that you would noticed the thread and helped as always even without my tag, i just speeded up things for being helpful to algg.
algg, I'd like to apologize myself; i didn't vanished after tagging shashank, today i just was at work and obviously i was busy for help, but as i saw with pleasure he already helped you to restore your OS and that was the objective. Nice one, guys!
I know, i know there's plenty of resources over the net already and I already spent 10+ hrs on this.
I bricked my phone when SuperSU prompts me to install su binary. And it got me into bootloop.
Tried https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108 but failed at 61%
Tried the backup oem file method but TWRP kept saying permission denied when trying to backup
Couldn't find a way to import dload+Update.app file into internal storage without actually booting up the phone first. I didn't knew the exact directory for internal storage so I couldn't copy it from OTG
Bootloader Unlocked, Rooted(before recovery), using TWRP.
I wanna go back to clean stock firmware
Any helps would be appreciated.
ADDED: ITS ORIGINALLY OREO
Any luck? I have the same problem here ..
Still have unlocked bootloader & know the firmware version you were on?
Right. Go to Firmware Finder. Download the FullOTA version of it.
Get one of the firmware extractor utilities. You're going to want SYSTEM, KERNEL, RAMDISK, and RECOVERY_RAMDISK (or RECOVERY_RAMDIS, depending on the extractor).
Get into fastboot mode.
Flash those 4 items to the partitions named the same.
Reboot into recovery - you're now in an EMUI recovery. Factory reset.
Reboot.
You should be back to stock with an unlocked bootloader. If you've gone poking around with root or whatnot and might have modified one of the other partitions, don't relock your device - it won't boot. Instead, hwota8 or a NoCheck stock recovery are probably the way you'd want to go. (To be honest, I haven't used either. If I want to get back to full stock knowing it's not modified, I usually do a downgrade flash to Nougat through HiSuite and then upgrade again.)
irony_delerium said:
Still have unlocked bootloader & know the firmware version you were on?
Right. Go to Firmware Finder. Download the FullOTA version of it.
Get one of the firmware extractor utilities. You're going to want SYSTEM, KERNEL, RAMDISK, and RECOVERY_RAMDISK (or RECOVERY_RAMDIS, depending on the extractor).
Get into fastboot mode.
Flash those 4 items to the partitions named the same.
Reboot into recovery - you're now in an EMUI recovery. Factory reset.
Reboot.
You should be back to stock with an unlocked bootloader. If you've gone poking around with root or whatnot and might have modified one of the other partitions, don't relock your device - it won't boot. Instead, hwota8 or a NoCheck stock recovery are probably the way you'd want to go. (To be honest, I haven't used either. If I want to get back to full stock knowing it's not modified, I usually do a downgrade flash to Nougat through HiSuite and then upgrade again.)
Click to expand...
Click to collapse
Data reset/factory reset not working !!
hussam_qashu said:
Data reset/factory reset not working !!
Click to expand...
Click to collapse
Try this one: https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
And use this TWRP with it (won't work otherwise, most likely): https://forum.xda-developers.com/mate-9/development/recovery-twrp-3-2-1-0-t3783353
(Also, that TWRP has decryption support so you can backup /data.)
Search and download your fw from http://pro-teammt.ru/firmware-database/
You'll want Update.zip, update_data_full_public.zip and the hw data zip. (Make sure it's actually for your phone, e.g. check region cust)
Rename update_data_full_public.zip to update_data_public.zip, rename hw data zip to update_all_hw.zip.
Put update zips and HuRupdater zip in the same folder on your sdcard/internal memory, flash HuRupdater with TWRP.
i have a question, im on mha l29 dual sim version with stock oreo magisk and twrp (368 update) how can i revert back to clean oreo? so i can get the updates normally. thanks !!
ante0 said:
Try this one: https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
And use this TWRP with it (won't work otherwise, most likely): https://forum.xda-developers.com/mate-9/development/recovery-twrp-3-2-1-0-t3783353
(Also, that TWRP has decryption support so you can backup /data.)
Search and download your fw from http://pro-teammt.ru/firmware-database/
You'll want Update.zip, update_data_full_public.zip and the hw data zip. (Make sure it's actually for your phone, e.g. check region cust)
Rename update_data_full_public.zip to update_data_public.zip, rename hw data zip to update_all_hw.zip.
Put update zips and HuRupdater zip in the same folder on your sdcard/internal memory, flash HuRupdater with TWRP.
Click to expand...
Click to collapse
that recovery wont work for me, only work twrp from pretoriano80 3.2.1-0, i got a mate 9 MHA-L29 dual sim...
edit:
well aparently theres 2, i dont get it, but when the recovery boot and show the logo of pretoriano, that version doesnt works, but when boot and show the classic twrp logo with pretoriano80 letters in red works...
so, if you flash recovery with fastboot and reboot recovery for the first time doesnt works, but if you reboot in recovery from twrp will show another version ...???? and works. sorry for my english
Colicablb said:
that recovery wont work for me, only work twrp from pretoriano80 3.2.1-0, i got a mate 9 MHA-L29 dual sim...
edit:
well aparently theres 2, i dont get it, but when the recovery boot and show the logo of pretoriano, that version doesnt works, but when boot and show the classic twrp logo with pretoriano80 letters in red works...
so, if you flash recovery with fastboot and reboot recovery for the first time doesnt works, but if you reboot in recovery from twrp will show another version ...???? and works. sorry for my english
Click to expand...
Click to collapse
That is weird, considering that he only made one TWRP for Mate 9