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.
Related
Hi,
I did something stupid - I wanted to update my phone by creating a dload folder on internal memory and updating to EMUI 4.0 beta that's floating around on the internet (I got it from carbontesla). I knew it required a B326 version, I had B324 and still went through with it, because I mistakenly thought that B326 is only required for L10 (I have L09). Now the phone is stuck in bootloop.
I have tried the following:
1. Forced update - it was apparently successful, but still the phone kept resetting
2. I reset to factory settings and wiped cache - still keeps resetting
3. I tried to force update again, this time I get an 'update failed' info and asks me to reboot. Still the same.
4. Tried to reset to factory settings and wipe cache again - still no luck.
I can't even turn the phone off, so for now I keep it in recovery mode.
Any idea what can I do? Am I screwed for good?
I searched around on XDA and other forums but couldn't find anything - if anyone can help me, I will be very grateful. I just bought this phone 3 months ago and I can't afford a new one at the moment.
Khasim83 said:
Hi,
I did something stupid - I wanted to update my phone by creating a dload folder on internal memory and updating to EMUI 4.0 beta that's floating around on the internet (I got it from carbontesla). I knew it required a B326 version, I had B324 and still went through with it, because I mistakenly thought that B326 is only required for L10 (I have L09). Now the phone is stuck in bootloop.
I have tried the following:
1. Forced update - it was apparently successful, but still the phone kept resetting
2. I reset to factory settings and wiped cache - still keeps resetting
3. I tried to force update again, this time I get an 'update failed' info and asks me to reboot. Still the same.
4. Tried to reset to factory settings and wipe cache again - still no luck.
I can't even turn the phone off, so for now I keep it in recovery mode.
Any idea what can I do? Am I screwed for good?
I searched around on XDA and other forums but couldn't find anything - if anyone can help me, I will be very grateful. I just bought this phone 3 months ago and I can't afford a new one at the moment.
Click to expand...
Click to collapse
Experienced all. Tsk. Should have stayed away from the Marshmallow upgrade thread.
Khasim83 said:
Hi,
I did something stupid - I wanted to update my phone by creating a dload folder on internal memory and updating to EMUI 4.0 beta that's floating around on the internet (I got it from carbontesla). I knew it required a B326 version, I had B324 and still went through with it, because I mistakenly thought that B326 is only required for L10 (I have L09). Now the phone is stuck in bootloop.
I have tried the following:
1. Forced update - it was apparently successful, but still the phone kept resetting
2. I reset to factory settings and wiped cache - still keeps resetting
3. I tried to force update again, this time I get an 'update failed' info and asks me to reboot. Still the same.
4. Tried to reset to factory settings and wipe cache again - still no luck.
I can't even turn the phone off, so for now I keep it in recovery mode.
Any idea what can I do? Am I screwed for good?
I searched around on XDA and other forums but couldn't find anything - if anyone can help me, I will be very grateful. I just bought this phone 3 months ago and I can't afford a new one at the moment.
Click to expand...
Click to collapse
Uh-oh... Another Mate 7 phone bricked by the Marshmallow beta B511 update...
I guess you'll just have to wait for the full official marshmallow update (no longer beta) for your TL09 phone for your region, or at least, wait for the official TL09 marshmallow to lollipop downgrade package for your region. When Huawei releases one or both, then you can install one or both via forced update (power + volume up + volume down) and have a functioning phone again.
For now, there's nothing you can do but wait and wait... unless you know your way around rooting, unlocking bootloaders and custom ROMs. There are actually quite a lot of Mate 7 owners in the similar situation as you. If only you can BAND together with a common cause/objective, your 'bricked by Marshmallow B511' group could somehow be a FORCE to reckon with that Huawei cannot ignore. Your group can petition Huawei with emails to release at least the 'marshmallow to lollipop downgrade package' for other non-China regions NOW, or the EARLIEST humanly possible...
You may want to read other users similar experiences with their bricked mate 7 phone (by installing the beta marshmallow b511 update) here: http://forum.xda-developers.com/mat...-marshmallow-b511-t3304178/page2#post65176950
It will make you feel much better knowing you are not alone. Alternately, you can just vent out your frustrations to Huawei in another thread. Not sure if its allowed in XDA though.
Those with bricked mate 7 phones:
Can you try and see if this suggestion works?
=========== (quoted from http://www.carbontesla.com/2016/01/download-ascend-mate-7-b511-marshmallow-ota-zip/) by wissam marrash
wissam marrash • a day ago
Guys I have mt7-l09 and its working with marshmallow, yes it drains more battery and some lagging in some areas but this should happen because its a beta and incremental release. For people who got spoil their phone while installing, you should read the requirements very well before downloading this rom. Its clearly mentioned for B326 and for un-rooted phones. so before you install you should install the B326 (you can download using this link: http://m.huawei.com/pkmobile/c... make sure to choose mt7-l09 or mt7-l10 and after installing the B326 install marshmallow beta.
For people who wants to downgrade, yes you can but you have to choose a full release like the B326-B327-B328.
N.B. ONLY Marshmallow BETA rom, Don't unzip the after downloading, its not like the other updates. You should copy the zipped file as is to inside "dload" folder.
Just a tip, some releases are not supporting 4G lte especially when it marked Europe.
For people who keep rebooting, try to connect you phone to pc or take out the memory card and use card reader and access your files and then delete the files from the "dload" folder and then download using your pc any full release rom (b326 or b327 or b328) and extract it and then copy the "UPDATE" file to the dload folder and then turn off the phone and then boot your phone while holding Vol up + Vol down + Power buttons at same time to automatically trigger the update installation and should go smooth.
Hope my comments will help
==============
Here are the links to full ROMs:
TL10: B326 full ROM:
http://consumer.huawei.com/pk/support/downloads/detail/index.htm?id=62450&key4=MATE7
L09: B326 full ROM:
http://consumer.huawei.com/pk/support/downloads/detail/index.htm?id=62371&key4=MATE7
reboot
Hi Don
We tried to follow Wassim's nstructions unfortunately it didn't work. As you said there are so many mate 7 users' faced this problem.
Any way thanks a lot for your attention.
maksudbek said:
Hi Don
We tried to follow Wassim's nstructions unfortunately it didn't work. As you said there are so many mate 7 users' faced this problem.
Any way thanks a lot for your attention.
Click to expand...
Click to collapse
i had that problem when tray to update it to MM tray it all the way no LUUUUUUUUCK
last i went to the Huawei Services the joke is they also can noooooooooooot do anything ??
last they decide it to change the main board of the phone then .. phone start with KK after that no problem
but i will never ever buy this brand again !!!!!!
Hi guys,
for some reason after I did update to KangVIP I can't get rid off it. Besides I got no wifi and bt and I was going to start over with b023 as suggested but at this point I wont bother anymore.
I did wipe the system, I did advanced wipe using twrp but no matter what I do none of the stock firmwares are going through however the Kanga one always goes through.(KangaVIP goes through only in TWRP)
twrp 2.8.7.0
wipe
advanced wipe
I select all the partitions
mkdosfs process ended with error=1
unable to wipe /usb
unknown mtp message type: 1
unable to wipe /usb
I go back, restart to fastboot, (device is saying there is no OS installed), I restore the recovery, create dload folder on my sdcard, put there 028 (actually I tried all of them already), volume+ volume - power and I get error.
What am I missing ?
Anyone can help ?
Thanks in advance.
Eric
First you did a OTA from B029 to B209?
If so you are now on a Android 6 ROM you cant go back to Android 5 without a Rollback from Huawei.
Hirs_E_Fruit said:
First you did a OTA from B029 to B209?
If so you are now on a Android 6 ROM you cant go back to Android 5 without a Rollback from Huawei.
Click to expand...
Click to collapse
Yes I did then I wiped everything and started with b028 again.
Same thing, wifi didn't work same with BT.
Wipe again and this time I did local update and since the local update I can't go back not even b029.
77Eric77 said:
Yes I did then I wiped everything and started with b028 again.
Same thing, wifi didn't work same with BT.
Wipe again and this time I did local update and since the local update I can't go back not even b029.
Click to expand...
Click to collapse
Right now you are on a Android 5 or Android 6 ROM?
If you on a Android 5 ROM you can force update a Complete ROM to install a clean system and try if everything works.
Hirs_E_Fruit said:
Right now you are on a Android 5 or Android 6 ROM?
If you on a Android 5 ROM you can force update a Complete ROM to install a clean system and try if everything works.
Click to expand...
Click to collapse
I'm stuck on 6.0
I know I can do force update on 5.0 I said it above I just can't do it with 6.0 -> b029, only with your rom.
Anyone else is having this issue ?
The Kanga rom got a quite few problems no wifi and not BT, Google play services crashing (this can be fixed with gapps) my co worker just tried it with his own methods and same issue. After I went through the whole Kanga thread 60% of the posters got problems most of them are ignored.
I don't have any problems but I think the people with problems are people who have a DAV 701L.
Hirs_E_Fruit said:
Right now you are on a Android 5 or Android 6 ROM?
If you on a Android 5 ROM you can force update a Complete ROM to install a clean system and try if everything works.
Click to expand...
Click to collapse
Hirs_E_Fruit said:
I don't have any problems but I think the people with problems are people who have a DAV 701L.
Click to expand...
Click to collapse
I got DAV-703L, just simple question, why is the wifi and bt not working ?
When I get into Kanga I can remove the root or deny access to it is there a way to ditch it ?
Yeah I know it's working for you and it's not working for 10 other people including 703L owners. There is something wrong with the rom no doubt about it.
77Eric77 said:
I got DAV-703L, just simple question, why is the wifi and bt not working ?
When I get into Kanga I can remove the root or deny access to it is there a way to ditch it ?
Yeah I know it's working for you and it's not working for 10 other people including 703L owners. There is something wrong with the rom no doubt about it.
Click to expand...
Click to collapse
I think there was an error while flashing and without a full clean Rom flash i can't see a solution.
Before I got it to work I flashed it more than 3 times and everytime everything worked so I think don't think the ROM is that bugged.
Hirs_E_Fruit said:
I think there was an error while flashing and without a full clean Rom flash i can't see a solution.
Before I got it to work I flashed it more than 3 times and everytime everything worked so I think don't think the ROM is that bugged.
Click to expand...
Click to collapse
The first rom you introduced is working "fine" I get the wifi and bt no problem but once I switch into the latest build it's gone.
Any idea where can I get full clean Rom ?
This one is a no go http://www.needrom.com/download/p8max-dav-703l/
I managed to rollback to 5.1.1 but when I try to force flash it, it says it's not compatible.
If you don't update properly to B209, when you flash any B209 rom you are going to run into issues such as the wireless Bluetooth and sim card switching for some. If you properly updated the dload method should have completed successfully. Look at the kernel and radio version of B209 in About phone and compare it to others and see if they match.
ajsmsg78 said:
If you don't update properly to B209, when you flash any B209 rom you are going to run into issues such as the wireless Bluetooth and sim card switching for some. If you properly updated the dload method should have completed successfully. Look at the kernel and radio version of B209 in About phone and compare it to others and see if they match.
Click to expand...
Click to collapse
I don't want to use your rom even if you removed the Chinese it's still inside the system. Boot load times take much longer. Unexpected crashes. I did try it on 4 phones with OTA and local updates 2 are working but the Kang does crash twice a day minimum.
All what I'm asking is how to restore it to it's original settings, this was my worst mistake ever.
What I'm trying to say if I do something I do it properly just look at your thread 85% failure ratio that doesn't look like it was done properly does it ?
77Eric77 said:
I don't want to use your rom even if you removed the Chinese it's still inside the system. Boot load times take much longer. Unexpected crashes. I did try it on 4 phones with OTA and local updates 2 are working but the Kang does crash twice a day minimum.
All what I'm asking is how to restore it to it's original settings, this was my worst mistake ever.
What I'm trying to say if I do something I do it properly just look at your thread 85% failure ratio that doesn't look like it was done properly does it ?
Click to expand...
Click to collapse
Really dude?? No worries, it will be the last time I do anything for the P8Max. Maybe you should just sell the phone since you're having all sorts of issues with it....or maybe you should have left it totally stock then. Or maybe read through the Mediapad X2 forums because the two phones are very similar.
I just rooted my Honor 8 running B360 and was successfull. But apparently there are some strange things, for example, the settings menu to configure the smart key is gone. Also, I noticed something strange when I went into my build.prop to get the Google Assistant. The line ro.build.tags is set to test-keys, which was in my build number when I ran into some problems while rooting. Is this right or should this be something else? Also ro.build.description includes NRD90M test-keys which was the exact build number when I ran into these problems. This sounds strange as my current build is FRD-L09C432B360..
I ran into that issue when I tried to install nougat for the first time, basically, stuff is missing, and I'm not sure why.
The solution is a long one unfortunately.
You'll have to reflash the update.app from a marshmallow version (the only full one I found for my device was b162. Make sure it's full so you miss nothing.)
Then use the Charles update method, or just wait until the update rolls out and do the normal update, don't root it and install twrp, because it will not install properly.
Then you should be on nougat and good to go.
I have yet to root on nougat, because I'm waiting to see if they'll roll out any patches for small bugs, and waiting to see if a better root method is released.
Good luck either way!
SolarisSixth said:
I ran into that issue when I tried to install nougat for the first time, basically, stuff is missing, and I'm not sure why.
The solution is a long one unfortunately.
You'll have to reflash the update.app from a marshmallow version (the only full one I found for my device was b162. Make sure it's full so you miss nothing.)
Then use the Charles update method, or just wait until the update rolls out and do the normal update, don't root it and install twrp, because it will not install properly.
Then you should be on nougat and good to go.
I have yet to root on nougat, because I'm waiting to see if they'll roll out any patches for small bugs, and waiting to see if a better root method is released.
Good luck either way!
Click to expand...
Click to collapse
Before you answered here, I tried to reflash update_data_full_hw_eu.zip and then boot, but it was stuck at the Honor logo. Then I rebooted into TWRP and install both update.zip and update_data_full_hw_eu.zip. I was again stuck at the Honor logo, but after booting into the stock recovery and doing a factory reset the phone booted as clean in B360. Then I spent litterally 5 minutes rooting with TWRP and phh's SuperUser. (http://www.theandroidsoul.com/root-honor-8-nougat-twrp-phh-superuser/) I now have root on Nougat, and I have not seen any features missing yet. It still says NRD90M and test-keys all over my build.prop but I guess that is supposed to be there.
FreeLineTM said:
Before you answered here, I tried to reflash update_data_full_hw_eu.zip and then boot, but it was stuck at the Honor logo. Then I rebooted into TWRP and install both update.zip and update_data_full_hw_eu.zip. I was again stuck at the Honor logo, but after booting into the stock recovery and doing a factory reset the phone booted as clean in B360. Then I spent litterally 5 minutes rooting with TWRP and phh's SuperUser. (http://www.theandroidsoul.com/root-honor-8-nougat-twrp-phh-superuser/) I now have root on Nougat, and I have not seen any features missing yet. It still says NRD90M and test-keys all over my build.prop but I guess that is supposed to be there.
Click to expand...
Click to collapse
I might give this a go - do you know which update.zip and eu you flashed? I have heaps of different versions
JoshSnitz said:
I might give this a go - do you know which update.zip and eu you flashed? I have heaps of different versions
Click to expand...
Click to collapse
This is a very old thread..
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/
Hello there.
I'm using tulip for few months now. One of first things that I've done, have been unlocking device, rooting it and put stock rom with root access on it. So far, so good. I did not encounter any serious glitches etc, but now I would like to finally upgrade miui to 11 (currently having 10.3).
And there's my problem. I would love to dodge making clean installation (wipe data etc) and I do not wish to risk to bootlooping my phone. I've read on some threads (older ones, but still) that you cannot simply install ota update in system, because due to changed recovery (I do have TWRP instead of fabric one) you will cause bootloop. I've tried alternative method of installing zip BY twrp, but program says, that it encounter a problem called "package expects build fingerprint (...) of tulip 0/PKQ1.180904.001/V10.3.2.0.PEKMIXM or PKQ1.180804.001/V11.0.2.0; this device has omni_tulip/tulip:8.1.0/OPM8.181105.002/1", and then sait, that in had error 7.
Is it simply wrong rom being installed and I have to choose something that is being named the same way and supports ota, or is there a way to go more swiftly through this process? If so and I should pick rom with ota - what to choose? I like deep level customisation, but compatibility with google store, being able to use store, payments and paid apps, instead of "opening them" by some lucky patchers kind of apps.
OR MAYBE I just need to change recovery from TWRP to something different - like PBRP f.e.? Just like this thread says - https://forum.xda-developers.com/re...how-to-setup-official-miui-breeaking-t3893703
Just a quick update - changing twrp to pbrp does not change anything in upgrade process - still get the same error, now just without telling me, which version do I have.
Also, what's interesting, apparently twrp said to me that I do have android 8.1, but "about phone" in system says, that its android 9 (9PKQ1.180904.001 to be exact).
That's werid, because everywhere I check, phone says "android 9" as a version of it.
Have you tried wiping system and installing?
Nitin Rai said:
Have you tried wiping system and installing?
Click to expand...
Click to collapse
Not yet. I've found method of flashing via PBRB with usage of downloaded file and one option check, but I'm not gonna try it, unless I do a backup of my apps. If that won't work, I'll perform a clean instalation and choose rom that supports ota.
well, I've tried to do this with the method, that I've described before, but this did not ended successfully. I'll look for rom with ota update possibility and then install it most likely. Apps had backup, so I lost almost nothing.
It worked. I had to download bigger patch (1.7 GB, instead of circa 700 MB, that I've tried before), I also had to use method described here -> https://c.mi.com/thread-1782169-1-1.html (pitch black recovery, instead of twrp + one tweak in options). Start after flash was very long (it took like 10 minutes or so), but it booted successfully in the end. Not sure which rom I do have after all, but as far as I remember it was so close to stock, as possible (with only few extra options and tweaks). So yea, it just works.