Related
EDIT: removed issues and added current.
Edit 2:
well, good new, im able to fastboot and log in to TWRP.
also flashed the previous file working.
anyway, to get the best help i will post some links and stuff...
The journey started here:
http://www.honornews.de/downloads/honor-6-android-6-0-marshmallow-beta-verfuegbar/
i did this and it worked.
B803 was running fine until i decided i wanted to run 804 and 805.
so i downloaded 804 TWRP and installed from this post:
http://forum.xda-developers.com/honor-6/general/emui-4-0-download-honor-6-l04-b803-t3290927/page20 (post 198 or something like that)
this also worked after some fiddling around.
the problems arose when i was trying to install the 805 recovery from the same post.
what I am wondering now is:
1. Could there be some issues with build.prop and local prop (and how can i check these files?)
2. could it be that either of the B805 i downloaded added some code, images or kernels to internal storage(the hidden directories that wont get wiped in TWRP)?
3. I notice that theres a whole lot of new folders in the internal memory, even after wiping in TWRP, which ones to delete?what is obsolete and can be safely removed.
4. Could it possibly be a permissions issue?one of my attempts with 805 booted into EMUI 4.0 but didnt recognize my simcard etc. and lagged after i tried changing permissions for both options. the linux and other android code.
After some charging i will try to do the unbrick feature again and test with the 550 update.app and/or mix the system.img and recovery.img from this one and then the other two files from the 805 update.zip...
so the downgrade to 550 worked!
its located here:
and extensively posted to. i laughed when it said i needed to wait to insert the SD until install screen, but it was truth.
note that the last two steps of installing 550, there is really no need to push those two images again.
just remember to add it to your SD before installing...
so, now i will update to 803 again
Full story:.
I downloaded the Android M, 803 last week and it worked fine, but i noticed that 804 and 805 had arrived so I wanted to test those.
Installing 804 went like normal and i used one of the guides here.
However, i wanted to root so I could downscale to 720p as i almost gain half a day extra on my device.
so i downloaded the tool and used the various steps, installed TWRP
and added root at the end
got stuck at bootloop
downloaded a recovery of 804 and restored with TWRP
this worked after some messing around in the logfile etc.
then the next step was trying to do the same with 805
i got stuck on bootloop for a while
tried the unbrick solution in the tool, tried to flash stock and other recovery options
tried adding manual update. app(on SD)
tried using cmd to add .img files(system, cust, boot, recovery)
this didnt work either
mixed and matched some old .img and new ones.
tried TWRP recovery of 805, also did not work
so i downloaded a downgrade pack that was intended for 803 to 521.
tried that
didnt work
used unbrick and added the system, cust, boot, recovery images from my B521.
and finally then i achieved a full brick
at least it appears i cant load into fastboot or any recovery,
eventually the phone boots to the b/w bootscreen but stuck there til battery runs out
the bootloader is unlocked, but im afraid its now hardbricked and not just softbricked, (at least when charging, the light turns on, but it doesnt appear to be charging much and it doesnt dim like it usually does when charging. i wish i somehow could enter the internal storage and just wipe everything(i guess i could run kali of it or something for a while) but i dont know how i can do that. i guess pros have tools for this.
if anyone can confirm, and/or know what the repair costs of this might be(i know this varies around the world, but any european estimate would be ok)
how did you resolve your problem? can you share with us?
kmlnvm said:
how did you resolve your problem? can you share with us?
Click to expand...
Click to collapse
look at post 198 or somewhere along pages 12-14 if i remember correctly, i followed those instructions...however, im properly done for now...
I picked up two Honor 6X BLN-24 models, the serial numbers are within a couple hundred of each other, so I'm assuming they're from the same batch. Right now they're both on Nougat, but one looks like it has a partial install of Nougat and the other has a "normal" install. Here's what happened:
1) The partial install phone - I unboxed it, connected it to WiFi, did a check for updates; it found the Nougat update, so I let the system update itself, rebooted, had Nougat B360. Flashed TWRP, which is working fine on the phone.
2) The "normal" install phone - instead of updating straight to Nougat, I installed TWRP first and had a bunch of issues with the wrong TWRP .img file; that's a separate issue. Got Nougat installed eventually on the phone but ended up with the "Test Keys" build issue. Ended up doing the rollback to MM, then did the check for updates, it found the Nougat update and I let it install. Phone has Nougat, build shows as B360.
Thought everything was fine and didn't really take a good look at the phones since I had to do other stuff to do before migrating to the Honors.. Now I'm ready and I'm noticing that one phone - the one that went to Nougat straight out of the box - doesn't have a bunch of apps that the second phone has, like the FM radio, CNN, Lyft, News Republic. Outside of the FM radio, I don't care about the other apps, but something else is missing - the System Update option in Settings. There may be other stuff missing, but the System Update thing is problematic.
So I figure my options are:
1) Rollback the phone that's missing things to MM, then retry the update, or
2) Try a dirty flash of the Nougat B360 update and data files.
3) Flash the smaller update_data file for the B360 build that contains most of the apps (but doesn't look like it has the FM radio)
Or is there another option?
Go with option 2. If no success then I would suggest for option 1.
Need couple of favours as you did rollback. Do you have the rollback package file? If yes, please share.
If you are rooted, use Huawei mutli tool and backup the oeminfo file. I need both these files so that if anyone messed up with their phone we will be able to revive and also address the nrd test keys issue and the best we can do is to debrand from other variant to US variant.
Thanks beforehand.
I had similar issues my phone was showing as nrd test keys and the backup of twrp also indentify phone as nrd test keys. When I checked updated update it was showing no update. My phone wassoft bricks so i download and updated package for build no b 340 and in build no it was showing nrd test key
Later i flashed zip shared in volte fix thread on xda as I was not having volte.
After flashing all thing went good test key issues resolved also so u can try that zip also.
Thanks for the replies, I'm away from the phones for a few days but will report back.
For shashank1320, the intermediate rollback package (the one that's flashed first from Nougat before the actual MM ROM) is still available on the US Honor site at http://www.hihonor.com/us/support/details/?DOC_ID=94205
You can use it if it matches with your last build no
WetWilly said:
Thanks for the replies, I'm away from the phones for a few days but will report back.
For shashank1320, the intermediate rollback package (the one that's flashed first from Nougat before the actual MM ROM) is still available on the US Honor site at http://www.hihonor.com/us/support/details/?DOC_ID=94205
Click to expand...
Click to collapse
Thanks downloading now. Yes then you can use this file for rollback.
Here's the latest update. - I tried the dirty flash method and it wouldn't work. AT ALL. I'm getting the "software failed update" at 5% message that several others have received. I downloaded the BLN-24C567B360 FullOTA package from three different sources; all had the same hash and *none* of them would work using the dload method. I ended up flashing the MM rollback package (which worked perfectly via the dload method) then flashed the MM firmware (also worked perfectly using the dload method). The phone booted into MM, it found the 2.35GB Nougat update (which is the same size of the Nougat .zips I downloaded), and it installed the update. It also installed the FM Radio (a system app) and the US package of apps that for some reason it didn't install when it upgraded to Nougat fresh out of the box.
I actually did this rollback/roll-forward twice since something odd happened while playing with SafetyNet with Magisk and the FRP Lock tripped. The next thing I know I'm getting the "data partition is corrupted" message and, again the B360 update.app files wouldn't flash. Thankfully the rollback worked. FYI, rolling back to MM relocks the bootloader. At this point I'm just keeping both the rollback and MM packages saved together on an SD card; flash rollback, pop card, rename folders on PC, pop card back in 6X, flash MM, reboot, find update, OTA to Nougat. Easier done than said, actually.
I am curious about why none of the B360 Nougat update.app files will flash on either phone. I don't think it's coincidental because the e-Recovery via WiFi doesn't find a package, and if I try System Recovery in HiSuite it says "no recovery available; take device to a Service Center".
WetWilly said:
I actually did this rollback/roll-forward twice since something odd happened while playing with SafetyNet with Magisk and the FRP Lock tripped. The next thing I know I'm getting the "data partition is corrupted" message and, again the B360 update.app files wouldn't flash.
Click to expand...
Click to collapse
If you get this issue again, try to format data inside TWRP.
itisiryan said:
If you get this issue again, try to format data inside TWRP.
Click to expand...
Click to collapse
I actually tried that. I ran into this same issue previously when I had TWRP installed, and TWRP's wipe data didn't work. Ultimately had to do the rollback to MM/roll-forward to Nougat and re-unlock the bootloader.
I can't figure out why my two phones won't flash Nougat using the dload method. The only logical reason is the upload.app file signatures, but I haven't found any alternative Nougat files for BLN-24C567B660.
I have tried quite a few ROMs, and all ended up going back to stock firmware because they wouldn't boot. I know I have to format data, and some ROMs ask you to change the data partition as f2fs.
Still, I think that there may be no ROMs that currently work for the US variant. One guy said LOS 13 worked, but when I flashed it, it failed. If someone has gotten it to work, can you please post as many steps as you remember on how to get it work?
Debrand to BLN-L21 following this guide and you're ready to flash cooked ROMs https://forum.xda-developers.com/honor-6x/how-to/guide-successful-debranding-to-bln-t3701050
RedSkull23 said:
Debrand to BLN-L21 following this guide and you're ready to flash cooked ROMs https://forum.xda-developers.com/honor-6x/how-to/guide-successful-debranding-to-bln-t3701050
Click to expand...
Click to collapse
Thanks, but wouldn't there be more issues down the line with a debranded phone? What if I soft-bricked my phone, it seems like it'd be really hard to restore? Has anyone actually ever done this on a BLN-L24?
Hello all,
I too am having issues with flashing roms to this device, US variant (BLN-L24). In my particular case, the rom boots up (EliteRom v7.1) and will actually function. However, wifi does not work, as well as I have no sound whatsoever. Youtube also will not play, nor will any videos, which I'm guessing is tied to whatever issue is with the sound. I have flashed multiple times per the step by step instructions, as well as following the Youtube video, all with the same result over the last few days. At this point, my phone is effectively useless to me, though cellular data does still work, just no calls can be answered. Anyone have any suggestions I might be able to follow? Also, even my TWRP backup that I made before installing the rom will not restore at this point. Any help is appreciated, thanks.
Jessooca said:
You must be missing a step or something, because [Elite ROM][EMUI 5.1] Elite ROM v7.1 for Honor 6X by HassanMirza01 works on the L24 us variant without issues, I have none.
Perhaps go back to stock and start over. I haven't had any issues with his rom and I didn't do anything more than what's needed to root/install twrp and flash the rom per his instructions.
Click to expand...
Click to collapse
I just followed the instructions; I believe to the best I could, and I'm stuck in a bootloop now. Which version of EMUI were you on before flashing? I was on EMUI 5.0 which may be my issue.
I started from EMUI 5.0
Unlocked my bootloader
Let it factory reset
Installed the Elite TWRP on the page
Booted to Elite TWRP
Formatted all partitions excpet for external sd card
Reformatted Data to f2fs
Re-wiped data
Checked that it was f2fs
Installed Elite ROM zip
Installed open gapps 7.0 ARM64
Installed the patch
Rebooted
Bootloop
i4ybrid said:
I just followed the instructions; I believe to the best I could, and I'm stuck in a bootloop now. Which version of EMUI were you on before flashing? I was on EMUI 5.0 which may be my issue.
I started from EMUI 5.0
Unlocked my bootloader
Let it factory reset
Installed the Elite TWRP on the page
Booted to Elite TWRP
Formatted all partitions excpet for external sd card
Reformatted Data to f2fs
Re-wiped data
Checked that it was f2fs
Installed Elite ROM zip
Installed open gapps 7.0 ARM64
Installed the patch
Rebooted
Bootloop
Click to expand...
Click to collapse
On one of the attempts that I did for installing, I installed the patch and it put me in a boot loop. Maybe not installing the patch can help you?
I cant get anything to work for the US version. Sure stuff boots but some of it is just broken. On octOS i am unable to use root unless i switch supersu to automatically grant root to apps. I cant get root access by using prompt because nothing pops up. On crdroid i have the same exact issue. Id rather have the prompt than allow any app root access without my knowledge. With ELITE ROM my first boot brings up a home screen with no keyboard. It completely skips any kind of setup screen. I can get the setup screen by flashing a keyboard from an aroma gapps installer but then i lose google services. The US version also seems to be forgotten as for most roms you wont see it anywhere under supported lists.
I've never been able to get a custom rom to work on my BLN-L24. Everything just ends in a never-ending bootloop of frustration.
Though, I have only ever tried with EMUI 5.0+. Maybe an earlier version of EMUI gets better results...?
code_name_duchess said:
I've never been able to get a custom rom to work on my BLN-L24. Everything just ends in a never-ending bootloop of frustration.
Though, I have only ever tried with EMUI 5.0+. Maybe an earlier version of EMUI gets better results...?
Click to expand...
Click to collapse
It really sucks that nothing seems to work. Ive tried flashing using multiple recoveries and ive tried all kinds of flashing to fix issues with the ROMS. Nothing helps. If anyone has successfully gotten a ROM fully working on BLN-L24 they need to tell people exactly what they did step by step.
It seems that for the roms located here, they seem to all assume that the phone has been debranded to bln-l21 variant. I don't know if it has any bearing on the current issues we're all experiencing, but I did notice that all twrps available for this device on the forums state they are the "Open Kirin Edition". It's been a while since I've rooted or rom'd a phone besides this one, but I've never encountered a twrp with a custom name like that.
I know that the developer of the EliteRom had his custom twrp, but is there a different twrp besides that one that does not state it is an "Open Kirin Edition"? Like I said, not sure if it has any bearing on things here, but I've been very confused about that.
TurtlePwr82 said:
It seems that for the roms located here, they seem to all assume that the phone has been debranded to bln-l21 variant. I don't know if it has any bearing on the current issues we're all experiencing, but I did notice that all twrps available for this device on the forums state they are the "Open Kirin Edition". It's been a while since I've rooted or rom'd a phone besides this one, but I've never encountered a twrp with a custom name like that.
I know that the developer of the EliteRom had his custom twrp, but is there a different twrp besides that one that does not state it is an "Open Kirin Edition"? Like I said, not sure if it has any bearing on things here, but I've been very confused about that.
Click to expand...
Click to collapse
For most phone i've ever owned you never had to change the recovery for each ROM. Its confusing. Most recoverys say Open Kirin Edition when booting. What confuses me is why we need to debrand to get the ROMS to work. If the phone pretty much run on the same hardware then why is L24 having so many issues? Why are the devs not testing on these devices?
BakedOnSomeSour said:
For most phone i've ever owned you never had to change the recovery for each ROM. Its confusing
Click to expand...
Click to collapse
Right, that's what I was thinking. For any phone I've ever rom'd, there was always just one twrp that everyone worked from.
Edit: found this while looking through the roll back to stock forum. I don't know if it will help anyone else, but figured I'd put it here as well if it might. All credit for this goes to the original poster johnnyrichter:
johnnyrichter said:
Tried this method after being on LineageOS for a week or two and having poor LTE signal, no MMS, and voicemail issues so I'm trying to go back to stock so I can have a fully functional phone since I rely on it heavily for work. Followed all steps using BLN-L24 B360 firmware. On step 10 I rebooted to update and it went right to "5% Installing Update" and stuck there for 5 mins, then rebooted itself, has been sitting at "honor" boot screen for 14 minutes so I made it reboot to EMUI recovery, wiped/factory reset, rebooted, loaded EMUI afte 2 more minutes. Appears to have worked and hopefully my issues are fixed!
Edit: Signal, mms, and voicemail issues fixed.
Click to expand...
Click to collapse
Hopefully will benefit someone here as well.
When debranding the BLN-L24, and branding it to BLN-L21, are there any issues with the ROMs once they're installed? I imagine the radios, and such are different for the two models??
BakedOnSomeSour said:
Why are the devs not testing on these devices?
Click to expand...
Click to collapse
Devs can only test devices they have in possession. If they don't have your phone model, how are they going to test it?
galapagos said:
Devs can only test devices they have in possession. If they don't have your phone model, how are they going to test it?
Click to expand...
Click to collapse
well, many don't want to give them a phone because most developers here tend to stop work on a ROM and leave people hanging.
I have gotten several ROMs working on L24 variant...
Yes it seems to me any Elite kernel based ROM works or should work on the L24. But /data must be ext4 format. Then even that the ROM works, the fingerprint scanner never allows a complete successful scan. I think because it must be f2fs format for that encryption to work or something. This is the link to those ROMS https://hassanmirza01.blogspot.com/p/custom-roms.html?m=1
On the other hand the LOS based ROMs never work or at least they reboot and the screen is always black or the ROM branding just stays there flashing. This sucks cause I want to run the newest Resurrection ROM but I ask the developer about why I have that problem or how long that ROM takes to boot and I never get an answer. He also just put a new beta AOKP ROM up and it does the same black screen thing too.
I am also suspicious it has to do with the version of TWRP. I think some are capable of formatting f2fs correctly or the encryption or whatever. Point is some of the devs need to be a little more consistent answering questions at a minimum. I know it takes time to fix bugs but give us a little heads up.
Hey,
Need some help here and not sure what's gone wrong, I've managed to root and flash custom ROM's before, but for some reason, my S7 now will not let me flash the BL file when trying to restore a stock ROM.
I can flash AP, CP and CSC with no problems, but trying to flash the BL file it gets half way and then the box at the top just goes red and says FAIL!
I've tried wiping everything from TWRP, installing custom ROM's and so forth to try and then restore from - phone is UK on BT Mobile and usually I use the XEU stock rom to reset.
The problem is, I have no carrier signal or IMEI information (I've tried the SIM in a different phone and it's working fine) so I can only presume it's something to do with the BL flash?
Any help is really appreciated!
Ok, well, hours of playing I found a SM-G930F combination firmware to flash (COMBINATION_FA60_G930FXXU2ARA2_BoxWares) - this has gotten me into FACTORY BINARY and lots of factory test / setting modes - phone now has it's IMEI number back AND I was able to receive a call from my girlfriends phone...
This seems to be running on Marshmallow 6.0.1 but obviously is not usable as an OS - so I need help to uprade firmwares in the correct order as trying to flash to 7 or 8 just fails in Odin and I can't seem to install TWRP recovery either from this.
I'm on BT Mobile (I used XEU before without issue - until recently!) so presume that's still the correct version...
Thanks!
Before I say anything DO you have a backup of your EFS folder do that first
Assuming you can only flash the binary 2 combination file firmware ,Samsung has recently updated their bootloader to not allow downgrades , you can only flash Nougat firmware from this year
Hey, I actually found that from some random spanish forum late last night... so I now have the combination rom with a useless (daily) front end / homescreen running android 6.0.1 but believe the bootloader is locked (from the nice little red error messages on startup) to a more recent version.
Supposedly I should be able to flash a `current` stock firmware then... but cannot seem to flash an AP file over this Combination rom install....
I did manage to download APKInstaller and install Kingroot (TWRP flash does not work - you cannot get into recovery anymore) and some other android apps (phone / sms / messenger) so have limited functionality but better than none for now.
No backups.
Boot into download mode , flash only the Sboot ( unzip the tar and make tar with only sboot) from any recent stock rom .
in AP put TWRP , untick the auto reboot.
when it passes( unplug phone ) hold the volume done , home power button till phone reboots (screen goes off) , quickly press volume up ,home and power button , you should be in TWRP
The combination firmware do not allow recovery modifications , it will just go in bootloop
OK, I'll try that when I get home later... lets say it works, what is my course of action then?
I still think I won't be able to flash a rom from Odin just by installing TWRP, so what actions do I need to take in TWRP? complete format ?
Thanks!
In TWRP make a backup of the EFS and Baseband partitions , copy to memory card .
I learned it the hard way , I ended up buying a second S7 with broken LCD so I can use the board
No box or tool can patch the certificate once you on Nougat as of yet
then you can go back to download mode and flash the AP ,CP ,CSC and phone should boot up , Leave the BL
Managed to get into stock recovery somehow (wasn't working before) and can see options for ADB sideloading etc again so that's something I guess lol
Presumably, if I can flash the boot file then twrp, I can then install a custom rom (i originally went from 7.0 up to 8 with Pixel Experience and Lineage, before things went tits up)
I'm guessing it'll be a case of formating data / wiping cache and installing the custom rom - assuming the BL is running 7.0 - or am i going to need to try and flash everything again via Odin (unsuccessful so far and only rom that will install is Combination)? also what about the CSC file...?
The only reason I'm in this predicament is because one of the custom roms somewhere (or google) screwed my IMEI settings, but Combination has brought those back.
you should be able to install any stock firmware from March 2018 onwards without any problems
Hmm ok so the network things I'm on T-Mobile and not BT Mobile lol (presumably because of the EUR flash) not sure if this will have implications when it comes to billing etc (BT bought out EE/T-Mobile but are different businesses still).
So does anyone have a working link to the XEU firmware? XEU-G930FXXS2DRC3-20180329132652 seems to be the filename... I can only find crap sites with 4kb downloads unless you pay $10-$20 lol
Success - in the absence of an upto date firmware from March for XEU - I found and installed the EUR one - BL everything went straight in and I've booted to setup screen now \o/
In Greek.... OK so hopefully I can just change language and wait for the XEU to surface (or is it OK to use the EUR? I have IMEI everything so looking good so far!)
I will probably flash Pixel Experience again unless someone recommends another over this?
Dreamz2k said:
Success - in the absence of an upto date firmware from March for XEU - I found and installed the EUR one - BL everything went straight in and I've booted to setup screen now \o/
In Greek.... OK so hopefully I can just change language and wait for the XEU to surface (or is it OK to use the EUR? I have IMEI everything so looking good so far!)
I will probably flash Pixel Experience again unless someone recommends another over this?
Click to expand...
Click to collapse
As someone said before.. Flash TWRP using ODIN; boot to twrp and make a backup of the EFS partition ONLY. Store the backup in the SD card and then copy it to the pc/dropbox/Drive/whatever. There are no guaranties that you wont loose the IMEI again if you attempt to flash the custom rom again. Then If you want to be on a completely stock rom, reflash the rom using ODIN. If you want to backup the baseband too, do the same procedure again but select only the baseband partition (untick the others)
To download stock roms you can use either the SamFirm tool (google search it.. it is on XDA) or Updato (site). Both of them provide really fast download speeds as there are no caps, and they are free. The files are downloaded straight from Samsung servers.
Sent from my SM-G930F using Tapatalk
Dreamz2k said:
Success - in the absence of an upto date firmware from March for XEU - I found and installed the EUR one - BL everything went straight in and I've booted to setup screen now \o/
In Greek.... OK so hopefully I can just change language and wait for the XEU to surface (or is it OK to use the EUR? I have IMEI everything so looking good so far!)
I will probably flash Pixel Experience again unless someone recommends another over this?
Click to expand...
Click to collapse
i guess i have the same problem like u....cant flash anything...just the combination file like u.....i have the stockrom from march but i cant flash this!! Odin does "Set partition" an do nothing!...
what can i do?
Hello everybody!
A couple of months ago, I successfully rooted my Mate 9 and we've been living happily ever since.
But since life is a big chunk of dirt and you'll have to get some of it at some point, I have to let my device go and sell it to a better owner.
So out of respect, I decided to restore the device to it's original state (e.g. unrooting and flash stock it).
But things got a bit out of control...
I downloaded the latest rom for my device, extracted the UPDATE.APP and flashed boot, recovery and system.
But from that point, the device went hectic:
*Bootlooping on the Huawei logo
*eRecovery indicating that there's a problem gathering the info
*Donwload Mode indicating that there's a problem with the software install
*TWRP Recovery accessible
*Fastboot still accessible with everything unlocked
I've been trying with almost a dozen of different firmwares (same region, same phone model) and nothing.
I looked over the forum, been trying some tricks here and there and still nothing good.
So here I am, waiting for your wisdom gents.
Thanks a lot !
jeanbono67 said:
Hello everybody!
A couple of months ago, I successfully rooted my Mate 9 and we've been living happily ever since.
But since life is a big chunk of dirt and you'll have to get some of it at some point, I have to let my device go and sell it to a better owner.
So out of respect, I decided to restore the device to it's original state (e.g. unrooting and flash stock it).
But things got a bit out of control...
I downloaded the latest rom for my device, extracted the UPDATE.APP and flashed boot, recovery and system.
But from that point, the device went hectic:
*Bootlooping on the Huawei logo
*eRecovery indicating that there's a problem gathering the info
*Donwload Mode indicating that there's a problem with the software install
*TWRP Recovery accessible
*Fastboot still accessible with everything unlocked
I've been trying with almost a dozen of different firmwares (same region, same phone model) and nothing.
I looked over the forum, been trying some tricks here and there and still nothing good.
So here I am, waiting for your wisdom gents.To start:
Thanks a lot !
Click to expand...
Click to collapse
Was it running a Nougat based ROM or an Oreo based ROM to start? That determines the firmware version you should be trying to restore: Oreo changes the partition table on the device, so loading an Oreo system.img and such won't get you back up and running if you were running a custom Nougat ROM.
Easy way to tell:
- If you tried "fastboot flash recovery recovery.img", was it successful? If so, you're on Nougat; if not, you're on Oreo - the "boot" and "recovery" partitions go away on Oreo and become "kernel", "ramdisk", and "recovery_ramdisk".
- If you tried "fastboot flash recovery_ramdisk recovery_ramdisk.img", was it successful? If so, that's Oreo.
If you _are_ on Oreo, the way I've gone about getting to a stock Oreo build:
Flash kernel, recovery_ramdisk, system from a relevant UPDATE.APP
Use HiSuite to roll back to Nougat
Upgrade back to Oreo.
It ends up working because the roll back to Nougat is a full device update image, meaning it'll put everything back into a like-new state, at which point the upgrade to Oreo goes off without a hitch.
There are more straightforward ways of doing it, but I haven't personally gotten into trying any of those:
- HWOTA (Nougat) and HWOTA8 (Oreo) would likely do the job, since you've still got TWRP there.
- /dload using stock recovery (putting the relevant update.zip files into the /dload folder on an SD card and booting with all buttons pressed, IIRC)
- FunkyHuawei via eRecovery
- If all else fails, DC-Unlocker / HCU Client.
The last of those, I recommend against UNLESS you're really and truly bricked - the device no longer comes up at all because xloader / ptable / trustfirmware / fastboot is screwed up.
irony_delerium said:
Was it running a Nougat based ROM or an Oreo based ROM to start? That determines the firmware version you should be trying to restore: Oreo changes the partition table on the device, so loading an Oreo system.img and such won't get you back up and running if you were running a custom Nougat ROM.
Easy way to tell:
- If you tried "fastboot flash recovery recovery.img", was it successful? If so, you're on Nougat; if not, you're on Oreo - the "boot" and "recovery" partitions go away on Oreo and become "kernel", "ramdisk", and "recovery_ramdisk".
- If you tried "fastboot flash recovery_ramdisk recovery_ramdisk.img", was it successful? If so, that's Oreo.
If you _are_ on Oreo, the way I've gone about getting to a stock Oreo build:
Flash kernel, recovery_ramdisk, system from a relevant UPDATE.APP
Use HiSuite to roll back to Nougat
Upgrade back to Oreo.
It ends up working because the roll back to Nougat is a full device update image, meaning it'll put everything back into a like-new state, at which point the upgrade to Oreo goes off without a hitch.
There are more straightforward ways of doing it, but I haven't personally gotten into trying any of those:
- HWOTA (Nougat) and HWOTA8 (Oreo) would likely do the job, since you've still got TWRP there.
- /dload using stock recovery (putting the relevant update.zip files into the /dload folder on an SD card and booting with all buttons pressed, IIRC)
- FunkyHuawei via eRecovery
- If all else fails, DC-Unlocker / HCU Client.
The last of those, I recommend against UNLESS you're really and truly bricked - the device no longer comes up at all because xloader / ptable / trustfirmware / fastboot is screwed up.
Click to expand...
Click to collapse
Well I started working around with the phone and remembered I installed this custom rom [ROM] RomAur-v2.2-[16/10]-[UB][7.0_Fw.b197]-FAST-STABLE and, from what I understood, I'm still running Nougat.
So I came to this, after all this hustle, my device build number is MHA-L29C432B194 and even with some other B194 roms, I wasn't able to install anything except for the RomAur above.
So to update this whole mess:
*Phone is running RomAur 2.1 (Nougat 7.0)
*TWRP won't install any other rom (even with the correct build) showing me a "status 7 error"
So should I give the HWOTA method a go ?
Thanks a lot for replying !
That's probably what I'd go hunt down. I have no experience with it myself, so I can't say much except that I've read about it here, and it sounds like others have had good experience with it. (I didn't get mine until after Oreo had come out, chosen because it wasn't too expensive, still had good performance, and had Treble support, so it was likely that more ROMs would come for it.)
irony_delerium said:
That's probably what I'd go hunt down. I have no experience with it myself, so I can't say much except that I've read about it here, and it sounds like others have had good experience with it. (I didn't get mine until after Oreo had come out, chosen because it wasn't too expensive, still had good performance, and had Treble support, so it was likely that more ROMs would come for it.)
Click to expand...
Click to collapse
Well, even with the HWOTA method it's not doing anything :/
You should have a look at this, I messed up my mate 8 pretty badly, much worse than what you have described above, and this gave it life, and I had to mess it up over and over after just to get it back to what I wanted, lost my original Oeminfo, lol long story, anyway with this, you can flash pretty much any official update from Huawei, give it a try
https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279/