Database Info

Unable to install Twrp

Hey folks, im hoping someone can help me out as im at my wits end here.
When i first got my phone i was able to install TWRP and root the phone and install a custom rom.
Then i downloaded the latest version of Twisted mate 8 and used TWRP to install it and for whatever reason when the phone went to reboot it put me into EMUI recovery and forced me to install the latest version with recovery.
Now that my phone is cllean slate, im trying to install TWRP and with no success. My bootloader is still unlocked but no matter what process i use, wether its ADB or SRK tool kit, after i do the cmd entry and it says its been installed, when i try to reboot into TWRP (holding volume up with power) I get EMUI.
its as if the latest version of EMUI is preventing me from installing TWRP again.
Does anyone know what could be the issue.
also can anyone recommend a site that has a clear simple step by step guide to rooting this phone?
I need to install Twisted Mate 8 or Kang VIP ASAP.
Thanks

Yeah. Install twrp manager from play store and try to reboot from there. But both volume buttons at start and release them almost immidietly
Skickat från min HUAWEI NXT-L29 via Tapatalk

I was finally able to install TWRP but when I enter TWRP and it first asks me for a code for the encrypted data, which I never encrypted, and when I bypass that and try to install an img all the storage options say 0 mb

spinward said:
I was finally able to install TWRP but when I enter TWRP and it first asks me for a code for the encrypted data, which I never encrypted, and when I bypass that and try to install an img all the storage options say 0 mb
Click to expand...
Click to collapse
Hi spinward,
You have to format data with twrp. Don't forget to save it first and restore it after formating.

grofock said:
Hi spinward,
You have to format data with twrp. Don't forget to save it first and restore it after formating.
Click to expand...
Click to collapse
I've done the format in TWRP and nothing changes, except the stock ROM is reset.
When i enter TWRP again the partitions/hd all say 0mb still

Flash TWRP via TWRP and see

Hi,
I think I ran into the same problem while updating my AL-10 from B172 to B361 and all the detours one has to make during that update trajectory.
After flashing TWRP, you have to reboot but make sure your phone isn't connected with USB-cable to your computer. That did the trick for me
Regards,

Soft bricked MHA-L29C432; please help!!!!

Hi guys i was trying to install a custom rom on my mate 9 (MHA-L29C432-156)so i followed the instructions ; unlocked the bootloader; then installed twrp 3.1.0-0; on twrp formated data; then full wiped and try to install AurRom from SD; but get a message that zip file is corrupted; so I tried with S.H.I.E.L.D ROM and it flashed , but then when boot goes to eRecovery, and give me 3 options download latest version and recovery; reboot and shutdown. So now I cant boot the phone, when I restarted, followed same steps , format data, full wipe and trying to installing again but getting a message about all zip files of the roms are corrupted; then i try to restore backup; and same again get the huawei logo, then the android logo , phone restarts and eRecovery again.
Please someone HELP, I use this phone for my work...........!!!!!!!!!

How did you full wipe?
Also try with Twrp 3.0.2-2
Here:www.androidfilehost.com/?fid=745425885120697579

dannytgt said:
on twrp formated data
Click to expand...
Click to collapse
Something went wrong here. You can run 'adb logcat' to see the crash details while starting.

If you have a backup on twrp then restore to get phone working. You may need to flash the public and hw-data zips afterwards though.
If you don't have a backup then you could try flashing the C636 off line firmware and then use firmware finder to go back to your original firmware
Sent from my MHA-L09 using XDA-Developers Legacy app

you may just flash the modified recovery ( See Guide subforum ) ) to bypass the update certification and authorization and reflash an original firmware. your stored files will be lost anyway in most cases.
I would bet superuser ( shield ) and SuperSU ( Aurom) messed your boot image. Both are incompatible to each other and, afaik both are incompatible to twrp 3.1.
Flash TWRP 3.0.2.2, reboot to recovery again to change version, flash the rom ( f.e. shield rom), boot once up, reboot to recovery and THEN you may flash twrp 3.1

Thanks all of you guys, I've solved the problem, it seems that's something related to the sd card, I've formated the sd and transfer the files trough another phone and then put the sd on the mate 9, I follow the steps as followed before and works successfully, now I'm on AurRom and 182 firmware.

[SOLVED] Can't boot to system, recovery, installing through dload crashes at 5%

Hello,
I recently got my new Mate 10 Lite and wanted to debrand it, update to Oreo, root and install useful Magisk plugins. Everything went fine and I got my phone debranded from C738 to C432, then I updated to Oreo B330 and tried to root. Couldn't succeed with dry Magisk 16.6 install, so I installed 16.0. Decided to give 16.6 a shot one more time but the story went the same, no 16.6 was installed and Magisk Manager had weird, arabic-like layout (inverted), so I wanted to patch boot image with 16.0 once again in order to clear all the "leftovers" 16.6 could leave. Unfortunately, after this operation my phone got softbricked, constantly entering ERROR MODE trying to boot both system and recovery, getting respectively Func NO 10 and 2 (boot image load failed!) and Func NO 11 and 2 (recovery image load failed!). I hoped that maybe I could just recover via TWRP installing it once again, but, unfortunately, it wasn't a thing and I couldn't boot anyway. I was, of course, installing Mate 10 Lite Oreo version of TWRP. HwOTA 8 doesn't help as well. dload update leaves me with crash at 5%. Any hopes for my baby, or only locking a bootloader and sending on warranty will do (if they even accept it)?
Thank you in advance,
Seven-
EDIT: Fixed. Just had to reflash kernel.img. As simple as that. Seems much more harder, doesn't it?
So here's a quick solution:
1. Go here: http://pro-teammt.ru/firmware-database/ Download Firmware Finder, search for Oreo ROM for your specific phone model and codename
2. Find update.zip. Unzip it and put UPDATE.APP to Huawei Update Extractor
3. Extract kernel.img and flash it via fastboot - "fastboot flash kernel kernel.img"
4. Reboot, should work from now.
This is solution for Oreo as I think it's a problem specific for Oreo because this partitioning system, but if you experience such problem with Nougat, download Nougat ROM and change all "kernel" words to "boot".
Hope you have a nice day, I'm glad that I might have helped a few of fellow Mate 10 Lite users

you can enter in recovery mode true?
try rebrand your device to stock and download the stock rom to flash via HwOTA or dload.

Can boot only to stock recovery, dload and fastboot. As I said, I rebranded to C432 and did it successfully and installed ROM for this version. I tried flashing both Nougat I used to rebrand and Oreo, both crash at 5% when flashing via dload, HwOTA doesn't work as it flashes TWRP you have to boot into, and I can't enter TWRP because I get Func NO 11 and 2 (recovery image load failed!). I tried 2 different TWRPs, this one from HwOTA and Azan Mughal's version. Neither of them works. Nougat versions don't even flash properly, which is normal because I "have" Oreo

Well, I might just say that this is the toughest phone I have ever been modding. I have just noticed that plugging the phone to charger also makes it enter ERROR MODE, which is also normal in this situation as boot image fails to load.

Just thinking... Might it be that recovery and boot partitions are somehow unformatted? I have no other idea why would recovery boot fail when installed. But on the other hand if it was unformatted it would either format it properly or not install at all, right?
EDIT: Tried to erase recovery but "Command not allowed".

I've got the exact same problem except dload because I don't know how to do that.

dload works with emui 4.x

It should always work. It's there for a reason, isn't it?
I might have discovered why am I getting boot and recovery failures. Obviously having Oreo there are no boot and recovery partitions but recovery_ramdisk and I think kernel (notsure) instead. I only have a question how do I repartition mobile device? There must be a way, right?
Like MTK-based devices have SP Flash Tool.

One click away from pushing all the files from UPDATE.APP from stock Oreo through Fastboot, is it safe enough? I mean, what if, for example, fastboot.iso fails to write or is corrupted, completely bricked phone?
Never been so scared modifying a phone, this one is so tough to mod and soft at once...

Can't boot to system, recovery, installing through dload crashes at 5%
i am in same problem plz developers do some work on these issues of this device to get back our devices thanks.
i have tried many mehods (dload, update. app, update. zip etc...... 1 different problem i got is when fladhing boot. img or recovery. img using cmd fastboot flash boot boot. img
failed remote; partition get size error.
---------- Post added at 09:17 PM ---------- Previous post was at 09:13 PM ----------
SevenUp9 said:
It should always work. It's there for a reason, isn't it?
I might have discovered why am I getting boot and recovery failures. Obviously having Oreo there are no boot and recovery partitions but recovery_ramdisk and I think kernel (notsure) instead. I only have a question how do I repartition mobile device? There must be a way, right?
Like MTK-based devices have SP Flash Tool.
Click to expand...
Click to collapse
keep searchig

@BaBa Yoga, you have Oreo, right? Try installing proper TWRP for 8.0 then and flash it as recovery_ramdisk instead, because it's how do partitions on Oreo look like. But I doubt it changes anything and makes your phone alive again.

FIXED IT, FIXED IT!!! Reflashed kernel and it works. Guys up here, you might want to try this out. As I thought, Magisk must have messed up with my boot file.
Adding solution to the main post.

SevenUp9 said:
@BaBa Yoga, you have Oreo, right? Try installing proper TWRP for 8.0 then and flash it as recovery_ramdisk instead, because it's how do partitions on Oreo look like. But I doubt it changes anything and makes your phone alive again.
Click to expand...
Click to collapse
yes oreo.... i am still trying twrps of azan mughal and other twrp for my device but now when i install custom recovery {fastboot flash recovery_ramdisk recovery. img}
it shows ok but when i reboot device in recovery mode there is no twrp recovery....... only stock recovery
---------- Post added at 10:02 PM ---------- Previous post was at 09:55 PM ----------
SevenUp9 said:
FIXED IT, FIXED IT!!! Reflashed kernel and it works. Guys up here, you might want to try this out. As I thought, Magisk must have messed up with my boot file.
Adding solution to the main post.
Click to expand...
Click to collapse
great bro....
plz share info here how to reflash kernal

@BaBa Yoga, I posted simple walkthrough in the first post, if you ever need explanation just ask here, I'll try to be more detailic then. Good luck unbricking your phone bro :victory:

SevenUp9 said:
Hello,
I recently got my new Mate 10 Lite and wanted to debrand it, update to Oreo, root and install useful Magisk plugins. Everything went fine and I got my phone debranded from C738 to C432, then I updated to Oreo B330 and tried to root. Couldn't succeed with dry Magisk 16.6 install, so I installed 16.0. Decided to give 16.6 a shot one more time but the story went the same, no 16.6 was installed and Magisk Manager had weird, arabic-like layout (inverted), so I wanted to patch boot image with 16.0 once again in order to clear all the "leftovers" 16.6 could leave. Unfortunately, after this operation my phone got softbricked, constantly entering ERROR MODE trying to boot both system and recovery, getting respectively Func NO 10 and 2 (boot image load failed!) and Func NO 11 and 2 (recovery image load failed!). I hoped that maybe I could just recover via TWRP installing it once again, but, unfortunately, it wasn't a thing and I couldn't boot anyway. I was, of course, installing Mate 10 Lite Oreo version of TWRP. HwOTA 8 doesn't help as well. dload update leaves me with crash at 5%. Any hopes for my baby, or only locking a bootloader and sending on warranty will do (if they even accept it)?
Thank you in advance,
Seven-
EDIT: Fixed. Just had to reflash kernel.img. As simple as that. Seems much more harder, doesn't it?
So here's a quick solution:
1. Go here: Download Firmware Finder, search for Oreo ROM for your specific phone model and codename
2. Find update.zip. Unzip it and put UPDATE.APP to Huawei Update Extractor
3. Extract kernel.img and flash it via fastboot - "fastboot flash kernel kernel.img"
4. Reboot, should work from now.
This is solution for Oreo as I think it's a problem specific for Oreo because this partitioning system, but if you experience such problem with Nougat, download Nougat ROM and change all "kernel" words to "boot".
Hope you have a nice day, I'm glad that I might have helped a few of fellow Mate 10 Lite users
Click to expand...
Click to collapse
bro i did not find firmware for my region i. e RNE L21 C185..... I FOUND DOME FIRMWARES on other sites one of thek i extract update. app using huawei updates extractor but there is no kernal.img file..... i found i. gs of boot, system, recovery, cust etc but no kernal. img what i do.....

You downloaded Nougat then, and you have to download Oreo that ends with B3xx, in your case then it will be RNE-L21C185B3xx There must be Oreo for C185, I know that because I was looking at C185 too when I was rebranding but then I noticed that C432 is what I should install for my region.
http://pro-teammt.ru/firmware-database/?firmware_model=rne-l21c185B3 - these are all the official Oreo builds for your specific region. I think all of them should do, I am certain that all the kernels in these packages are similar. Eventually you can just flash another one later

SevenUp9 said:
You downloaded Nougat then, and you have to download Oreo that ends with B3xx, in your case then it will be RNE-L21C185B3xx There must be Oreo for C185, I know that because I was looking at C185 too when I was rebranding but then I noticed that C432 is what I should install for my region.
[m/?firmware_model=rne-l21c185B3[/url] - these are all the official Oreo builds for your specific region. I think all of them should do, I am certain that all the kernels in these packages are similar. Eventually you can just flash another one later
Click to expand...
Click to collapse
should i download OTA-MF or FULLOTA-MF?
I Hope i could find kernal file now....
i am downloading FULLOTA-MF thanks to provide me firmware list of my region

thanks sevenup9 for getting back my device out of that problem i flash the kernel successfully wnd get back my twrp as well now what next..???????? thanks again
---------- Post added at 06:54 AM ---------- Previous post was at 06:01 AM ----------
i flashed kernel. img, cust. img, system. img and then reboot now i have twrp but still in bootloop what next

Yeah, good that you downloaded FullOTA, as it's a full system image. I assume there is no system.img or kernel.img in OTA package at all.
Since you have TWRP now but stuck in bootloop, try to wipe data and cache and try to boot again. If you don't succeed, then maybe try getting all of the 3 zips from FullOTA package on SD card (or USB stick if you have a USB OTG cable) and flash them via TWRP, starting from "update.zip". Should work just fine. Maybe your phone got more partitions messed up, but that should be recoverable as you have a good base being able to boot into TWRP

SevenUp9 said:
Yeah, good that you downloaded FullOTA, as it's a full system image. I assume there is no system.img or kernel.img in OTA package at all.
Since you have TWRP now but stuck in bootloop, try to wipe data and cache and try to boot again. If you don't succeed, then maybe try getting all of the 3 zips from FullOTA package on SD card (or USB stick if you have a USB OTG cable) and flash them via TWRP, starting from "update.zip". Should work just fine. Maybe your phone got more partitions messed up, but that should be recoverable as you have a good base being able to boot into TWRP
Click to expand...
Click to collapse
i did usb mathed as well but when flash update. zip via twrp error 9 shows
---------- Post added at 10:10 AM ---------- Previous post was at 10:06 AM ----------
then usi g fastboot i flash recovery_ramdisk kernel cust system ramdisk all these images..... now reboot and i lost twrp and it replaced with stock recovery.... in stock recovery i wiped cache... done... wipe data and factory reset..... stuck at 0% after 10 minutes... plz bro
---------- Post added at 10:12 AM ---------- Previous post was at 10:10 AM ----------
i didn't lock bootloader yet... i keep it still unlock

[TWRP] [Port] L.R.-Team recovery OMFG-Mod-From Cactus -to -Umidigi-F1

First version shared was twrp 3.2
New version is 3.3.0
***ORIGINAL TWRP is not my work. Only the porting of it to this device. I take no credit for the source.
*** DISSCLAIMER ALLERT***
I started having issues with encryption coming back to enforcing when using the Ported Team LR TWRP 3.3
Did not have trouble yet with OMFG-Mod version.
Also @ghost45 has made a build of twrp 3.3.1 for F1. It works good as well
https://forum.xda-developers.com/showpost.php?p=79651368&postcount=49
--- all versions give trouble of loosing IMEI when using the remove force encryption patch I suggest below. Left logs with @Zackptg5 .
**May need more testing**
-decryption is broken
-MTP is working
-ADB is working
****--Advanced menu items are not correctly on 3.2 version.
-- Some of the advanced menu was fixed in 3.3.(install root is working)
- Advanced menu has extra features.(all from source twrp)
-- install magisk (currently has V17 on OMFG V19 on LR TEAM)
-- patch dm-verity and force encrypt remove.zip. ( personally I prefer the universal dm-removal patch from xda)
-- Remove system password, (from original dev, I have not tested)
--
--Install (basic directions only)--details may be added later if needed
Open zip and fastboot flash the recovery image if bootloader is unlocked.
or
Open zip , then open scatterfile (scatter file in test 1 has issue, updating it in next test )with sp-flashtool , select download
--First boot into TWRP will give errors for unable to mount /data. This is from the force-encryption.
- When boot into TWRP, select wipe -> format type 'yes' to format data
- When format is done, return to TWRP home page, select reboot -. recovery
--Now Patch device so no longer forces encryption
-- Use built in feature from 'Advanced Menu' or use the following directions--Fails to unpack boot. (current zip used is not compatible with system-as-root boot.img)
-To remove this I use 'Disable_Dm-Verity_ForceEncrypt' from
-- https://github.com/Zackptg5/Disable_Dm-Verity_ForceEncrypt -- currently based on magisk V19.2
-Download from the "Clone or Download" button on the above linked Github Page.
-Unzip the downloaded file. You will have a folder with same name as the zip package. Browse inside this folder, select all files and zip them.
-Put this new zip file onto your phone. ( Hay notice the MTP function on this TWRP works)
- in stall the zip like any normal twrp package.
--Next Install Magisk
--Use Built in Root Option from 'Advanced Menu' to use Magisk V19 or the following direction
- Goto the releases page of magisk github page. ==>LINK
- Download latest Magisk zip , Put file to phone, Install.
-- Download Folder For TWRP Ported from OMFG-Mod
https://www.androidfilehost.com/?w=files&flid=294886
-Screenshots.
- Ported OMFG-MOD gold Button TWRP V3.2
- Ported Team LR TWRP 3.3 standard Button
Attached Below
--Thanks --Mentions
recovery source from [LR TEAM] MIUI
http: //www.miui.com/forum.php?mod=viewthread&tid=19006123&page=1&mobile=2#pid257831639
link is newer version from ported recovery. They updated recently. Next port may use newer base as well.

hello @ColtonDRG. Long time.
I see you posted in umidigi forum that bootloader is not checking signature. So you CAN flash images with flashtool without unlocking. Is that correct.?
I have based the above install guide on that fact that you CAN.
But the first twrp posted by "ghost45" says no it must be unlocked.
edit:
I should be able to verify later today or this weekend, when my order arrives.
OK, verified, when i used flash tool and put twrp on phone before unlocking bootloader, on reboot I was stuck in "RED" status for boot loader. So must unlock

Flash this zip to remove the AdupsFota app
this is the update app. You will not be able to install OTA when rooted and twrp anyway, And if an OTA comes you will get stuck in recovery bootloop. So this flash file will rename the 2 apk related to OTA download and Force reboot that supposed to install that update.

Reserved
Will keep this post for working on issues .
Right now , I discovered after playing with the built in dm verity patch and root install lead imei's getting erased.
Restored the full rom with flash tool fixed, will update process as necessary
Restarted from the top again.
--1 Full stock rom flashed with sp flash tool.
--2 Twrp flashed in flash tool
--3 format /data, reboot recovery
--4 use mtp to copy Disable_Dm-Verity_Forceencrypt to phone
--5 flash the decrypt zip. And at the end of flash the output log showed 'failed to mount /nvdata file not exist'
*** Waiting for input from the Patch dev. Others on his xda thread with MTK have had similar trouble***
--6 use mtp , put stock recovery file on phone. Image flash stock recovery, reboot recovery, do factory reset in stock recovery. This fixed the /nvdata error.
--7 sp flash twrp again, use built in 'install root' option from advanced menu.
Bam all done

New Umidigi f1 recovery 3.3.1 test2 is pubblished.
Test this one if all is corrected...
http://www.mediafire.com/file/1emy4tk1gvnkj96/recovery-twrp-3.3.1_Umidigi_F1_test_2.rar/file

ghost45 said:
New Umidigi f1 recovery 3.3.1 test2 is pubblished.
Test this one if all is corrected...
http://www.mediafire.com/file/1emy4tk1gvnkj96/recovery-twrp-3.3.1_Umidigi_F1_test_2.rar/file
Click to expand...
Click to collapse
Thank you, this one has no displayed errors.
I have question though.
Do you know how to make system be mounted as /system instead of /system/system ?

Hey, buddy. Good to see you on the forums again. When I picked up this device I wondered if anyone from the R1 HD days would also be on it. I seem to have misplaced mine but I'll find it eventually, send me a DM if you wanna talk about it. I'm not 100% sure about this, but the bootloader verifying signatures might have been patched in because I don't remember mine doing that when they first came out. Of course even if it does, SPFT is still useful for unbricking and downgrading, but I really doubt UMIDIGI will patch out the unlock option like BLU did.

Hello again, all. I've been working on my UMIDIGI F1 again and after flashing the most recent firmware update using SPFT and trying to flash TWRP again I realized that something that changed in the latest firmware update has broken all of the existing TWRP images. Now the bootloader screen hangs for a while, sometimes a green bar appears at the top of the screen briefly, and then the phone reboots into Android. It is perhaps worth noting that when I tried to flash the upgrade in download only mode it just complained about the partition layout or something like that and then bailed, telling me to use the Format and Download option instead. I didn't do that because UMIDIGI told me not too and instead opted to try the Firmware Update option, which did work. I'm going to try to downgrade (hopefully I don't get bricked from downgrading preloader, efuses, etc) but I am a bit concerned about what has changed. Stock recovery still boots OK so it would seem to me that the bootloader isn't just completely borked, but either way it's a bit alarming that an OTA caused the custom recoveries we have to go kerplooie.

ColtonDRG said:
Hello again, all. I've been working on my UMIDIGI F1 again and after flashing the most recent firmware update using SPFT and trying to flash TWRP again I realized that something that changed in the latest firmware update has broken all of the existing TWRP images. Now the bootloader screen hangs for a while, sometimes a green bar appears at the top of the screen briefly, and then the phone reboots into Android. It is perhaps worth noting that when I tried to flash the upgrade in download only mode it just complained about the partition layout or something like that and then bailed, telling me to use the Format and Download option instead. I didn't do that because UMIDIGI told me not too and instead opted to try the Firmware Update option, which did work. I'm going to try to downgrade (hopefully I don't get bricked from downgrading preloader, efuses, etc) but I am a bit concerned about what has changed. Stock recovery still boots OK so it would seem to me that the bootloader isn't just completely borked, but either way it's a bit alarming that an OTA caused the custom recoveries we have to go kerplooie.
Click to expand...
Click to collapse
There is a newer twrp that has been released on 4pda.net that supposed to work on newest firmware release.
And downgrading with flashtool should work. Again need to use firmware upgrade option.

mrmazak said:
There is a newer twrp that has been released on 4pda.net that supposed to work on newest firmware release.
And downgrading with flashtool should work. Again need to use firmware upgrade option.
Click to expand...
Click to collapse
Downgrading worked. I couldn't find the newer TWRP version you were referring to and the website you mentioned redirects to a bunch of scammy crap.

ColtonDRG said:
Downgrading worked. I couldn't find the newer TWRP version you were referring to and the website you mentioned redirects to a bunch of scammy crap.
Click to expand...
Click to collapse
We have the twrp file copied to telegram group also. I'm stuck on mobile, or I would just copy the twrp here.
UMIDIGI
UMIDIGI unofficial TG group
https://t.me/UMIDIGI

Disable_Dm-Verity_ForceEncrypt failed
Hello, I'm trying to patch my F1 using the Disable_Dm-Verity_ForceEncrypt, but am stuck with an error "Dumping/splitting image failed. Aborting..." This occurs when I try using the Install from twrp. Has anyone encountered this issue before? I have done a wipe, and also tried installing Magisk (which installs fine).

Need to upgrade but have questions

Hi guys. I rooted my phone after purchase about two years ago using https://forum.xda-developers.com/mate-9/how-to/guide-how-to-root-mate-9-decrypt-data-t3569986
I am still running the same version now
Twrp
Model: MHA-L29
Build: MHA-L29C567B183
EMUI: 5.0
Android Version: 7.0
Any one got suggestions and steps to get to a newer version. I think I need to switch back to Erecovery etc but if someone had some exact steps and a good version to move to would be great. I had thought about installing magisk but my main concern is being able to run games like Pokemon go or Mario kart and they seem to be detecting my root. Not even sure having root is worth it anymore.

I installed stock recovery and did ota updates.. working like a champ!

mpencexda said:
Hi guys. I rooted my phone after purchase about two years ago using https://forum.xda-developers.com/mate-9/how-to/guide-how-to-root-mate-9-decrypt-data-t3569986
I am still running the same version now
Twrp
Model: MHA-L29
Build: MHA-L29C567B183
EMUI: 5.0
Android Version: 7.0
Any one got suggestions and steps to get to a newer version. I think I need to switch back to Erecovery etc but if someone had some exact steps and a good version to move to would be great. I had thought about installing magisk but my main concern is being able to run games like Pokemon go or Mario kart and they seem to be detecting my root. Not even sure having root is worth it anymore.
Click to expand...
Click to collapse
Did you really flash TWRP to eRecovery? It is possible but people usually (specially if not installing Magisk on EMUI 9) flash TWRP to (EMUI) Recovery - which is not the same as eRecovery
So, do two tests:
- switch off
a) disconnect any USB
- press and keep pressing Vol+
- boot by Pow
In test b), do the same but with the phone connected to charger.
If it boots to TWRP in case a), then you flashed TWRP (as usual) to EMUI Recovery.
But if it boots to TWRP in case b), then you really flashed TWRP to eRecovery
If you have stock eRecovery, then in case b), once booted to eRecovery, do not accept Install latest or Factory reset, just Reboot or Shutdown
---
If you rooted by SuperSU, find an option like Full Unroot, or google for and find a zip for TWRP for unrooting - do unroot
Maybe, there are similar options for unrooting from phhSuperUser
Do not accept any OTA yet - if it comes
---
Install Firmware Finder app (from Playstore or from its thread on XDA).
Open, it will show firmwares for your MHA-L29C567
Scroll to the bottom to find your b183. Must be FullOTA-MF or FullOTA-MF-PV (2017.03.22)
Download its update.zip file, copy to PC, unzip to get update.apk - open it by Huawei Firmware Extractor (find its thread on XDA, read how to use it)
Extract Recovery.img (if you need to restore stock Ramdisk) or Recovery2.img (if you really need to restore stock eRecovery)
Extract also Boot.img
Flash Boot.img to Boot and Recovery.img to Recovery (if restoring Recovery), from TWRP or from Fastboot (similarly as you flashed TWRP from Fastboot back then)
Or, flash Boot.img to Boot and Recovery2.img to eRecovery, if you need to restore eRecovery
Now you should have stock Recovery and stock eRecovery - both tests a) and b) must not boot to TWRP
Also, you should have stock Boot - boot to system, check with RootChecker - there must be no more root
----
Have a proper SIM card and WiFi connection, go to Settings, System, Update, go to its menu and take the option to get Full OTA package
If it doesn't give you OTA update, boot to eRecovery (option b) as above, phone connected to the charger) and take Install latest firmware and recovery. Follow by Factory reset, only then boot to system
If eRecovery also fails to update from b183, you can try to update by HiSuite - it has also an option to choose installing a firmware
---
If it still fails to update, you can download by Firmware Finder b190 FullOTA-MF-PV (2017.10.31)
Download both zip files, do not unzip, copy them as downloaded to DLOAD folder on SD card (not Internal memory)
Switch off, press and keep pressing both Vol+ and Vol-, then boot by Pow
It should update to b190, and hopefully you will start receiving OTA updates for Oreo and Pie (must have SIM card)
If not - to be cont.