Hello all,
I have a rooted (with CWM) Mate7 TL10 EMUI 3.0 (4.4.2) B131, (Middle East) and need to update it to Marshmallow, can I do it directly? or do I have to update to Lollipop first? either way, please guide me on how to do it, I have been looking online for days for B131, but couldn't find anything for it.
thank you in advanced
M.Maany said:
Hello all,
I have a rooted (with CWM) Mate7 TL10 EMUI 3.0 (4.4.2) B131, (Middle East) and need to update it to Marshmallow, can I do it directly? or do I have to update to Lollipop first? either way, please guide me on how to do it, I have been looking online for days for B131, but couldn't find anything for it.
thank you in advanced
Click to expand...
Click to collapse
I just had this problem a month ago, same build number and barely any help. But, I was able to find helpful posts in the end. So I'm here to help... and yes. First Lollipop then Marshmallow update.
As you probably know, BACKUP what you need before proceeding.
Then you need to:
1- Unroot your phone if you have root.
2- Have EMUI's stock recovery. You can reinstall it in case you've installed a custom recovery on the phone.
3- Factory reset your device (HIGHLY ADVICE to do but not mandatory).
4- Download Lollipop update (to B326) from here: http://ministryofsolutions.com/2016/02/huawei-mate-7-lollipop-511-upgrade-for.html
5- After you finish the download, extract the "UPDATE.APP" file from it (no need to extract anything else from the archive), create a folder called "dload", and put "UPDATE.APP" in that folder.
6- Once you've done that, you should go to updater in your settings, select "local update". This time, the phone should detect the file "UPDATE.APP".
7- Next, attempt to update. The device should restart and attempt to install the update.
From my experience, the update took about 30 minutes to install, since I didn't factory reset before update. So, I don't know if it'll take less time with a clean device.
To update to marshmallow AFTER you've installed lollipop, simply find the OTA update online, download it, and repeat steps 5 to 7.
If anything of what I said was unclear, missing files to download, or you have any questions, feel free to post again here and I'll try to reply back.
Hopefully everything goes well with you, and have a good day.
Credit goes mostly to Mutahhar Bashir for posting the above site of the update.
EDIT:
P.S.: For bootloader re-lock, I personally don't think it's a must, since it worked updating ota with unlocked bootloader for me.
Highly appreciated my friend
Thank you so much for the help, quick question though, where from can I get the correct stock recovery for my device? Is there a chance I would brick it if I try to install an incompatible recovery?
Again, thank you so much for the help.
M.Maany said:
Thank you so much for the help, quick question though, where from can I get the correct stock recovery for my device? Is there a chance I would brick it if I try to install an incompatible recovery?
Again, thank you so much for the help.
Click to expand...
Click to collapse
Found it on another site. This should be it: http://forum.android.com.pl/topic/2...recovery-sterowniki-mt7-l09-mt7-tl10/?page=27
Sorry I took long, had difficulty finding the file. Install the recovery version that you are CURRENTLY in. The file is called "Recovery mate7 mobopx v2.2". You'll find it on a specific reply on that page.
Keep me up-to-date with your progress for me to see if I can help.
Thanks mate, I really appreciate this, however, you kinda lost me when you said "Install the recovery version that you are CURRENTLY in", I'm not sure I get what you meant, u mean reinstall the same recovert I already have? Or check what version of CWM I have and install the same version of the TWRP recovery?
M.Maany said:
Thanks mate, I really appreciate this, however, you kinda lost me when you said "Install the recovery version that you are CURRENTLY in", I'm not sure I get what you meant u mean reinstall the same recovert I already have? Or check what version of CWM I have and install the same version of the TWRP recovery?
Click to expand...
Click to collapse
Oh I was unclear. Sorry.
What I meant is, that the stock recovery you want to install should be the same as the android version of your phone currently. As in you are currently on Kitkat, then choose to install the kitkat stock recovery from the application.
I hope it's clear right now.
unable to install stock recovery
hey bro, sorry for being away, I keep getting this error when trying to install stock recovery
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
cscl.6te.net/Capture.JPG
any idea how to fix it?
by the way, i used kingroot to root my device, don't know if that's related.
Uhm... Just a few suggestions.
M.Maany said:
hey bro, sorry for being away, I keep getting this error when trying to install stock recovery
any idea how to fix it?
Click to expand...
Click to collapse
Uhm... just a few suggestions:
-Install adb drivers
-Install hisuite (It contains drivers for the mate 7)
-Enable usb debugging (which I'm pretty confident you've enabled)
Universal ADB drivers can be found on the official Clockworkmod website. Hisuite should be available on Huawei's site. Also bootloader must be unlocked (which I'm also confident you have already) if it's not.
Other than what I said above, I still can't think of any other way to try and fix it... Sorry if I couldn't help.
iDoFatalities said:
Uhm... just a few suggestions:
-Install adb drivers
-Install hisuite (It contains drivers for the mate 7)
-Enable usb debugging (which I'm pretty confident you've enabled)
Universal ADB drivers can be found on the official Clockworkmod website. Hisuite should be available on Huawei's site. Also bootloader must be unlocked (which I'm also confident you have already) if it's not.
Other than what I said above, I still can't think of any other way to try and fix it... Sorry if I couldn't help.
Click to expand...
Click to collapse
I may have forgotten to mention that it's still rooted , still trying to figure out how to unroot
M.Maany said:
I may have forgotten to mention that it's still rooted , still trying to figure out how to unroot
Click to expand...
Click to collapse
Stock recovery with root installed is no problem. You can do that after installation. When you get to the OTA update part, uninstall root before so. So, you're not forced to as long as you are still at this step.
ugggg
iDoFatalities said:
Stock recovery with root installed is no problem. You can do that after installation. When you get to the OTA update part, uninstall root before so. So, you're not forced to as long as you are still at this step.
Click to expand...
Click to collapse
i uninstalled kingroot and this unrooted my device, installed adb drivers from clockworkmod site, installed hisuite from huawei site, already have usb debuggine enabled, but still getting same error
any alternative way to restore stock recovery?
can do the update.app manual update without restoring stock recovery?
uggggg
uninstalled kingroot, this unrooted my device, BUT still getting same error, installed adb from clockworkmod , installed hisuite from huawei site, still same error.
can I do the UPDATE.APP manually without restoring the stock recovery??
any alternative method to restore stock recovery?
M.Maany said:
uninstalled kingroot, this unrooted my device, BUT still getting same error, installed adb from clockworkmod , installed hisuite from huawei site, still same error.
can I do the UPDATE.APP manually without restoring the stock recovery??
any alternative method to restore stock recovery?
Click to expand...
Click to collapse
if I lock the bootloader then unlock it again, would that help? if yes, how do i re-lock it
M.Maany said:
uninstalled kingroot, this unrooted my device, BUT still getting same error, installed adb from clockworkmod , installed hisuite from huawei site, still same error.
can I do the UPDATE.APP manually without restoring the stock recovery??
any alternative method to restore stock recovery?
Click to expand...
Click to collapse
You MUST have stock recovery for OTA updates. Sorry.
You can try relock then unlock. But i specifically dont know how to. I think there is an app you can find on the tools/utilities tab of this device for utilities for the Mate7, which i think has a relock bootloader option, and many more utilities.
Other than that, I don't know yet how to help you man. For the meantime, surf the internet if you can find anything that can help.
I apologize.
EDIT: Doesn't your phone reboot into bootloader when trying to install? And have you made sure if the recovery has changed?
thanks man for all the help, yes my device reboots into bootloader and it says device unlocked in red on that screen, and yes i'm still on CWM recovery.i even tried
-adb reboot recovery
-fastboot flash recovery d:\recovery.img
but still get the same error, i think the bootloader lock might be the problem, will look around for that utility you've mentioned and let you know how it goes.
M.Maany said:
thanks man for all the help, yes my device reboots into bootloader and it says device unlocked in red on that screen, and yes i'm still on CWM recovery.i even tried
-adb reboot recovery
-fastboot flash recovery d:\recovery.img
but still get the same error, i think the bootloader lock might be the problem, will look around for that utility you've mentioned and let you know how it goes.
Click to expand...
Click to collapse
Unlock your bootloader again and it might fix the problem. Also you can check out DC Unlocker.
If there is a TWRP for KitKat you can use the terminal to flash your stock recovery or you can use Flashify with root.
YAYYYY !!!!
erayrafet said:
Unlock your bootloader again and it might fix the problem. Also you can check out DC Unlocker.
If there is a TWRP for KitKat you can use the terminal to flash your stock recovery or you can use Flashify with root.
Click to expand...
Click to collapse
FINALLY !!!, tried unlocking bootloader again and it worked, although it took forever to get the unlock code.
anyway, now I have stock EMUI recovery, will remove root and do the OTA and let you know how it goes.
ON lollipop
Alright, thanks to your help and thorough instructions, I am now on lollipop, next step please on the way to Marshmallow?
oh oh, one question though, will i still be able to root after updating to marshmallow?
M.Maany said:
Alright, thanks to your help and thorough instructions, I am now on lollipop, next step please on the way to Marshmallow?
oh oh, one question though, will i still be able to root after updating to marshmallow?
Click to expand...
Click to collapse
Yes.
AWESOME
Awesome !! now do you have a link for me to download the UPDATE.APP for Marshmallow?
or does it need to be updated in some other way?
Related
Does anyone know or have a copy of a working EMUI3.0 CWM or TWRP recovery for the Honor 6 Plus (6x) PE-TL10
Boot loader unlocked but no root. Tried normal root tools but none yet seems to work, so I was looking to changing the recovery to CWM /TWRP and then flash SU and root that way, returning to stock 3.0 extracted recovery from the latest ROM.
Any assistance appreciated please.
http://forum.xda-developers.com/android/general/huawei-honor-6-plus-root-tutorial-t2991788
Thanks but tried that, recovery does not work on the 6 Plus and the proc may be good for a mate7 but not for the 6Plus. It was just as well I had extracted a stock 3.0 recovery to go back to. I think that this proc may have been written for 2.0 not 3.0, that may be why I get a blank screen on boot in to recovery.
So still waiting...
Sathelp said:
Thanks but tried that, recovery does not work on the 6 Plus and the proc may be good for a mate7 but not for the 6Plus. It was just as well I had extracted a stock 3.0 recovery to go back to. I think that this proc may have been written for 2.0 not 3.0, that may be why I get a blank screen on boot in to recovery.
So still waiting...
Click to expand...
Click to collapse
Hello, I have it running smoothly on my Honor 6 Plus PE-UL00.
If you have bootloader open just puts the recovery with:
fastboot flash recovery recovery_en.img
I leave you with attachment
To flash can also be used Honor 6 MultiTool modifying the bat or renaming the recovery_en.img by the recovery that you download the program
Sorry for my poor English
BoRoU said:
Hello, I have it running smoothly on my Honor 6 Plus PE-UL00.
If you have bootloader open just puts the recovery with:
fastboot flash recovery recovery_en.img
I leave you with attachment
To flash can also be used Honor 6 MultiTool modifying the bat or renaming the recovery_en.img by the recovery that you download the program
Sorry for my poor English
Click to expand...
Click to collapse
Thanks you but the recovery file you attached is only 128bytes bytes big and not a valid file. can you please attach the full recovery file please? I will then try to flash it.
Sathelp said:
Thanks you but the recovery file you attached is only 128bytes bytes big and not a valid file. can you please attach the full recovery file please? I will then try to flash it.
Click to expand...
Click to collapse
I managed to use the Multitool and its recovery_en, so no worry, all done, but here if anyone else is looking for instruction on how I done it, here they are:
I used the Honor 6 Multi-tool from this thread in the XDA pages.
I am not sure if the bootloader unlock works or not, so if you can get it unlocked as above or try this tool.
The tool is for the 6 not especially the 6Plus but using the install CWM recovery works, then I used the boot to recovery and then selected root by sidelobe (install zip/install zip by sidelobe menus). SU was installed permissions set. As I wanted to ensure that the correct stock recovery was used (my EMUI3.0 extracted before) I selected to reboot the phone by exiting the (recovery) and it then asked me if I wanted to fix root, I selected yes, rebooted the phone. Checked that root was working and then went back to bootloader and fastboot flash recovery (my recovery) to get it back to stock.
Sathelp said:
I managed to use the Multitool and its recovery_en, so no worry, all done, but here if anyone else is looking for instruction on how I done it, here they are:
I used the Honor 6 Multi-tool from this thread in the XDA pages.
I am not sure if the bootloader unlock works or not, so if you can get it unlocked as above or try this tool.
The tool is for the 6 not especially the 6Plus but using the install CWM recovery works, then I used the boot to recovery and then selected root by sidelobe (install zip/install zip by sidelobe menus). SU was installed permissions set. As I wanted to ensure that the correct stock recovery was used (my EMUI3.0 extracted before) I selected to reboot the phone by exiting the (recovery) and it then asked me if I wanted to fix root, I selected yes, rebooted the phone. Checked that root was working and then went back to bootloader and fastboot flash recovery (my recovery) to get it back to stock.
Click to expand...
Click to collapse
Thanks in advance for this tutorial My 6 Plus is on its way from China.
What's funny though... I also once owned an Eten X500 and my previous phone was a ZTE V987
My GF is now using it with MIUI v5, but I'll give here my ZTE V5 when my Honor 6 Plus arrived
Aren't you also active on this UK Cloud iBox satbox forum?
No not me. I am on several forums but mainly phones or tablets ( heavy on what was the Eten forum with Bruno Martin who now works here on Gravity Box or on satellite TV forums. I think a lot of us old dual sim users had a near similar list of phones as they developed.
BTW, the Honor 6 plus multi tool has my recovery added, so you can use that now too.
Just for anyone finding or searching and coming on to this thread, I have posted the tools needed at this link.
It has CWM and stock recovery files as well as the SuperSU and install bat file.
Sathelp said:
I used the Honor 6 Multi-tool from this thread in the XDA pages.
I am not sure if the bootloader unlock works or not, so if you can get it unlocked as above or try this tool.
Click to expand...
Click to collapse
You can get unlock code from the site given in Multi-Tool.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If the CWM/TWRP for H6 doesn't work on H6Plus i can add custom recoveries that work on your device.
UPDATE: I add "recovery_en" in Multi-Tool. Can anyone tell me what version of CWM is?
VirusPlus said:
You can get unlock code from the site given in Multi-Tool.
View attachment 3124925
If the CWM/TWRP for H6 doesn't work on H6Plus i can add custom recoveries that work on your device.
UPDATE: I add "recovery_en" in Multi-Tool. Can anyone tell me what version of CWM is?
Click to expand...
Click to collapse
As we don't have any custom ROMs, how do we update to latest version when Huawei do release (especially when they release Lillipop)?
ksekhar said:
As we don't have any custom ROMs, how do we update to latest version when Huawei do release (especially when they release Lillipop)?
Click to expand...
Click to collapse
You can always revert back to stock recovery. The tool for Mate 7 from Anzhi BBS forum works great.
I have already done this three times when there has been a new OTA updates.
Sathelp said:
Just for anyone finding or searching and coming on to this thread, I have posted the tools needed at this link.
It has CWM and stock recovery files as well as the SuperSU and install bat file.
Click to expand...
Click to collapse
Maybe I didn't understand your instructions 100% correct, but without getting an unlock code from the Emui site to unlock the Bootloader I wasn't getting anywhere.
So I got the Unlock code from the site and then went through all the steps from VirusPlus tool and that all worked perfectly
In the end I think I would have got exactly the same result with your 6-Plus-only tool.
Anyhow, from within the MultiTool I did the following:
I installed the Universal ADB drivers, got the bootloader unlocked, installed CWM, installed SuperSU, installed Stock recovery... reboot. Winning.
Thanks all for your excellent work
Flow said:
Maybe I didn't understand your instructions 100% correct, but without getting an unlock code from the Emui site to unlock the Bootloader I wasn't getting anywhere.
So I got the Unlock code from the site and then went through all the steps from VirusPlus tool and that all worked perfectly
In the end I think I would have got exactly the same result with your 6-Plus-only tool.
Anyhow, from within the MultiTool I did the following:
I installed the Universal ADB drivers, got the bootloader unlocked, installed CWM, installed SuperSU, installed Stock recovery... reboot. Winning.
Thanks all for your excellent work
Click to expand...
Click to collapse
yes, The VirusPlus tool was updated and works fine now with the recovery and CWM I sent him that I used. There was a small problem at the start but he has corrected it. Glad your all sorted now. I noticed a small update today for the 6 Plus, nothing much but you need to be back on stock recovery to update it. Easy now though to go back to CWM whenever you want to.
Sathelp said:
yes, The VirusPlus tool was updated and works fine now with the recovery and CWM I sent him that I used. There was a small problem at the start but he has corrected it. Glad your all sorted now. I noticed a small update today for the 6 Plus, nothing much but you need to be back on stock recovery to update it. Easy now though to go back to CWM whenever you want to.
Click to expand...
Click to collapse
I reflashed back to stock recovery after installing supersu, do you need to reinstall CWM and supersu after an OTA update or doesn't it affect root?
Flow said:
I reflashed back to stock recovery after installing supersu, do you need to reinstall CWM and supersu after an OTA update or doesn't it affect root?
Click to expand...
Click to collapse
It does depend on the update. Most times (minor updates) it will be fine and survive the OTA update but at least you have the tools to put it back on if it does after a major update or re-flash of the ROM. There is a setting in SuperSU about updates, may be worth checking it out but I think one of the settings is only available on the Pro or donated version.
Sathelp said:
yes, The VirusPlus tool was updated and works fine now with the recovery and CWM I sent him that I used. There was a small problem at the start but he has corrected it. Glad your all sorted now. I noticed a small update today for the 6 Plus, nothing much but you need to be back on stock recovery to update it. Easy now though to go back to CWM whenever you want to.
Click to expand...
Click to collapse
Can this CWM make a full back up? I didn't found any backup files after mention successful backup.....
Did anyone already try the EMUI 3.1 (Android 5.1) ROM on the H6+ and succesfully got Root with this tool?
Android 5.1 ROM: http://www.emui.com/cn/plugin.php?id=hwdownload&mod=detail&mid=125
Mirror: https://mega.nz/#!5ox3wByI!ajcv6SvTnymYH2g4hnpMI1Li0nj80i7NZyATwiHMa0w
Edit:
Warning: Only install the EMUI 3.1 ROM when you have Stock Recovery!
Mine was rooted as well, that was not a problem.
I did loose root after installation though.
Managed to install it and then rooted (SuperSU) with TWRP for EMUI 3.1
Flow said:
Did anyone already try the EMUI 3.1 (Android 5.1) ROM on the H6+ and succesfully got Root with this tool?
Edit:
Warning: Only install the EMUI 3.1 ROM when you have Stock Recovery!
Mine was rooted as well, that was not a problem.
I did loose root after installation though.
Managed to install it and then rooted (SuperSU) with TWRP for EMUI 3.1
Click to expand...
Click to collapse
after you rooted, can it downgraded to emui 3.0 again?
afikri6 said:
after you rooted, can it downgraded to emui 3.0 again?
Click to expand...
Click to collapse
I don't understand your question.
Why would I want to downgrade back to EMUI 3.0 and what does it have to do with root?
My advice in general when installing a complete ROM:
Install Stock Recovery.
Download complete ROM package (inclusing the dload/UPDATE.APP file).
Install as Local update using the Updater app.
I'm not sure if this would work the same with downgrading.
Hiya People,
Just wanted to share my journey and my TWRP backups with you all.
I have a M8sw (dual-SIM) mec_dugl which many thanks and :highfive: and respect to DutchDanny, I converted it to a M8sw Europe/UK version running near stock Lollipop 5.0.2 Sense 6 RUU 2.33.401.6.
When I saw the Marshmallow update, I was over the moon and decided to download it straightaway but as I had TWRP as recovery, the phone was rooted and had xposed installed, I knew I didn't have much of a chance.
So guess what? The Marshmallow update downloaded OK and then tried to go into recovery but since it was TWRP, it failed. So I took the OTA zip file from the phone's downloaded folder and extracted out the recovery.img from the firmware.zip and replaced TWRP. I then uninstalled xposed and turned off SuperSU. This time round, I go a similar message as http://forum.xda-developers.com/one-e8/help/help-htc-e8sd-mm-update-install-error-t3345406
So I decided to follow a mixture of DutchDanny's [REMODEL][S-OFF NEEDED] M8SW China Remodel to M8SW EU and yourmate's guide get OTA updates.
To cut the already long story short, I went back to L5 Stock 2.33.401.3 then use OTA updates to L5 Stock 2.33.401.6 and then finally to the part 1 of the Marshmallow update L5 Stock 2.33.401.8 and at each stage, I reflash TWRP, wipe and then backup and then reflash the OTA recovery.img in readiness for the next OTA
So I have the last Lollipop 5.0.2 Stock HTC Sense 6 Europe 2.33.401.8 factory reset TWRP backup AND Marshmallow 6.0.1 Stock HTC Sense 7 Europe 3.07.401.1 factory reset TWRP backup in all its glory with bloatware and all.
Enjoy!
I have remodeled my phone following the DutchDanny guide. I rooted the phone and installed xpose. BUT to install marshmallow I first install the lolipop RUU from hboot. then enter to system update to marshmallow without any problem. finally I flash TWRP and then flash supersu and that all for me.
bro help
i have same porblem and i kinda even forgot how to i rooted phone.. man i have rooted it before and i hate twrk recovry.. i also had super user.. and bootloader minu says s on.. i clocked super user and chose unroot and it did.. then i cant find twrk any more.. and i wanna install andriod 6 s bad please tell me how to do it
generalugh28 said:
Lollipop 5.0.2 Stock HTC Sense 6 Europe 2.33.401.8 factory reset TWRP backupAND https://drive.google.com/open?id=0B1qf0eVpKmagUENyOXFxdWgtTEU"]Marshmallow 6.0.1 Stock HTC Sense 7 Europe 3.07.401.1 factory reset TWRP backup in all its glory with bloatware and all.
Enjoy!
Click to expand...
Click to collapse
both no wifi, driver is missing, any fix? everything else works just fine.
good day sir, that is a Marshmallow TWRP backup right? if i restore the file with my M8sw (dual-SIM) mec_dugl, will it work and give me an MM firmware? coz mine just got recovery loop after i updated with MM and is it converted to EU version already? Thanks!
I have downloaded your "Marshmallow 6.0.1 Stock HTC Sense 7 Europe 3.07.401.1 factory reset TWRP backup" and recover it in twrp but after the recovery it just stuck in bootloop. What must I do to make it working?
smiter said:
both no wifi, driver is missing, any fix? everything else works just fine.
Click to expand...
Click to collapse
I also had the same problem after upgrading to MM.... my guess is that it's the kernel module for wifi which need to be updated.... seems like HTC isn't putting much effort to implement the new update...
I went back to lollipop with a twrp backup.
sanijsnj said:
I also had the same problem after upgrading to MM.... my guess is that it's the kernel module for wifi which need to be updated.... seems like HTC isn't putting much effort to implement the new update...
I went back to lollipop with a twrp backup.
Click to expand...
Click to collapse
how to install his file? I have downloaded his "Marshmallow 6.0.1 Stock HTC Sense 7 Europe 3.07.401.1 factory reset TWRP backup" and recover it in twrp but after the recovery it just stuck in bootloop. What must I do to make it working?
I actually has stock rom with no modification that will cause bootloop when upgrading.. I only had to unroot.. Flash stock boot and recovery and let OTA do the rest
I haven't tried the twrp backup on this thread.
sanijsnj said:
I actually has stock rom with no modification that will cause bootloop when upgrading.. I only had to unroot.. Flash stock boot and recovery and let OTA do the rest
I haven't tried the twrp backup on this thread.
Click to expand...
Click to collapse
thanks, I guess I just need to download OTA. also for safer update. though its the chinese version, really having a hard time with its store.
Jon_Nel said:
thanks, I guess I just need to download OTA. also for safer update. though its the chinese version, really having a hard time with its store.
Click to expand...
Click to collapse
Keep in mind that you'll need an unmodified stock ROM for OTA to be a success... Being rooted or having xposed framework causes bootloops.
As for the Chinese store.. You can easily replace it with Google apps.... Just follow the direction in this video.. You can skip it to 1:50mins....
http://https://youtu.be/doyMXI2AFM8
sanijsnj said:
Keep in mind that you'll need an unmodified stock ROM for OTA to be a success... Being rooted or having xposed framework causes bootloops.
As for the Chinese store.. You can easily replace it with Google apps.... Just follow the direction in this video.. You can skip it to 1:50mins....
http://https://youtu.be/doyMXI2AFM8
Click to expand...
Click to collapse
Thank you so much for your reply. I tried to update(OTA) my kitkat[1.21.1402.11] rom to lollipop last night but when I woke up there's this error saying that I should have unmodified rom in order to download the OTA. this ROM that im using is the stock RUU from this link. I dont know why it says that it is modified. does it something to do with my location? because im in the Philippines and this is phone is from China. Hmm, really having a problem updating to MM. Sorry I'm new in HTC's because I'm a Samsung user from the past.
Jon_Nel said:
Thank you so much for your reply. I tried to update(OTA) my kitkat[1.21.1402.11] rom to lollipop last night but when I woke up there's this error saying that I should have unmodified rom in order to download the OTA. this ROM that im using is the stock RUU from this link. I dont know why it says that it is modified. does it something to do with my location? because im in the Philippines and this is phone is from China. Hmm, really having a problem updating to MM. Sorry I'm new in HTC's because I'm a Samsung user from the past.
Click to expand...
Click to collapse
I'm not sure what might be causing this error...but it's definitely not because of your location...you should ask from the other thread, they might be able to assist you.
Fail to load wifi driver on marshmallow twrp rom
Hello
My device is a HTC e8 Chinese version that is remodeled to EU version.
After upgrading to Marshmallow with twrp, everything seemed to be OK but Wi-Fi persists to be in OFF situation and it couldn't be ON.
And then I put the phone on Airplane mode and then I start Wi-Fi again, when I did it, a notification appeared that it told me:
"Fail to load driver, reason: Module is not compatible (8)."
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Does anyone have any idea about fixing e8 Wi-Fi driver?
.
chatrood said:
Hello
My device is a HTC e8 Chinese version that is remodeled to EU version.
After upgrading to Marshmallow with twrp, everything seemed to be OK but Wi-Fi persists to be in OFF situation and it couldn't be ON.
And then I put the phone on Airplane mode and then I start Wi-Fi again, when I did it, a notification appeared that it told me:
"Fail to load driver, reason: Module is not compatible (8)."
Does anyone have any idea about fixing e8 Wi-Fi driver?
.
Click to expand...
Click to collapse
It seems that mostly everyone with the china unicom is facing this issue... It has something to do with the kernel or kernel module for WiFi... Unless a developer is able solve this problem... We're gonna have to wait for HTC to fix this via an OTA update.
tldr: The /data partition got corrupted and I had to wipe everything and remove TWRP. Now I have the stock recovery working but every time I try to flash an official bios with the dload method it gives an error in chinese that says "upgrade package version number verification failed please re download"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I tried several international and chinese roms I found on weird websites without success, is there any mirror for the real stock roms?
Tried some of these without success (remove spaces): h ttps: //boycrac ked .com/2017/ 02/14/official -huawei-p8-max-dav-703l-stock-rom-firmware/
Thanks in advance, my phone is a brick right now and I can't even power it off :/
I tried flashing with the dload method all these roms, only the first one "worked" but there are files outside the UPDATE.APP and the flash was super quick, then the phone didn't boot or anything so it never really worked..
The only rom that didn't give an error and started flashing has these files and UPDATE.APP is only 62mb...:
Huawei P8 Max DAV703 Android 6.0 EMUI 4.0
If you were on Android 6 previously, then flash TWRP and install an official Android 6 firmware with TWRP. After that do a factory reset.
erayrafet said:
If you were on Android 6 previously, then flash TWRP and install an official Android 6 firmware with TWRP. After that do a factory reset.
Click to expand...
Click to collapse
Thanks for your reply!! Yes I was on android 6, installed TWRP and tried all the 6.0 roms I could find without success...
One of them, Aroma ROM, starts ok but then gets frozen and doesn't move, I left the phone for an hour and it didn't install anything:
The other roms just fail before starting..
Any ideas? I'm starting to think the phone won't work again
newfulluser said:
Thanks for your reply!! Yes I was on android 6, installed TWRP and tried all the 6.0 roms I could find without success...
One of them, Aroma ROM, starts ok but then gets frozen and doesn't move, I left the phone for an hour and it didn't install anything:
The other roms just fail before starting..
Any ideas? I'm starting to think the phone won't work again
Click to expand...
Click to collapse
You need TWRP V3+.
You can also install the ones for Huawei Mate S but try with v3.1.1-0.
Don't forget to flash a FULL-OTA package because you're flashing OTA's. Also this old version of TWRP works only on Android 5 firmware.
Another method is to extract the STOCK RECOVERY partition with Huawei Update Extractor, flash it in fastboot, then install the UPDATE.APP with dload method, but it might give you the incompatibility message because of the CUST difference.
erayrafet said:
You need TWRP V3+.
You can also install the ones for Huawei Mate S but try with v3.1.1-0.
Don't forget to flash a FULL-OTA package because you're flashing OTA's. Also this old version of TWRP works only on Android 5 firmware.
Another method is to extract the STOCK RECOVERY partition with Huawei Update Extractor, flash it in fastboot, then install the UPDATE.APP with dload method, but it might give you the incompatibility message because of the CUST difference.
Click to expand...
Click to collapse
THANKS FIRST OPTION WORKED!!!
Installed latest version of TWRP for the P8, seems to work just fine on the P8MAX.
Flashed aroma rom successfully!!
I am so happy right now, I have my phone back!!!
Thanks i really appreciate your help!
newfulluser said:
THANKS FIRST OPTION WORKED!!!
Installed latest version of TWRP for the P8, seems to work just fine on the P8MAX.
Flashed aroma rom successfully!!
I am so happy right now, I have my phone back!!!
Thanks i really appreciate your help!
Click to expand...
Click to collapse
You're welcome!
newfulluser said:
tldr: The /data partition got corrupted and I had to wipe everything and remove TWRP. Now I have the stock recovery working but every time I try to flash an official bios with the dload method it gives an error in chinese that says "upgrade package version number verification failed please re download"
I tried several international and chinese roms I found on weird websites without success, is there any mirror for the real stock roms?
Tried some of these without success (remove spaces): h ttps: //boycrac ked .com/2017/ 02/14/official -huawei-p8-max-dav-703l-stock-rom-firmware/
Thanks in advance, my phone is a brick right now and I can't even power it off :/
I tried flashing with the dload method all these roms, only the first one "worked" but there are files outside the UPDATE.APP and the flash was super quick, then the phone didn't boot or anything so it never really worked..
The only rom that didn't give an error and started flashing has these files and UPDATE.APP is only 62mb...:
Huawei P8 Max DAV703 Android 6.0 EMUI 4.0
Click to expand...
Click to collapse
Hope this works
chaschas said:
Hope this works
Click to expand...
Click to collapse
Thanks!! I eventually found a russian stock ROM and used the phone until it died.
newfulluser said:
Thanks!! I eventually found a russian stock ROM and used the phone until it died.
Click to expand...
Click to collapse
My Hauwei P8 max is bricked as well, tried all the ones you have. Could I have a look at the site you have(Russian) as my Hauwei uses emui to upload. Bought it for $30 on ebay as is(bricked)
Sorry I didn't keep the phone or the ROM files... Phone would freeze it's memory every 3 months and I had to reflash to keep it running. I have had 3 different phones after that one so I didn't think to keep the roms
I have one more firmware but not dload. Its still p8 bht not max, do not know if it good for anything Having a bit of ----uploading it!
chaschas said:
I have one more firmware but not dload. Its still p8 bht not max, do not know if it good for anything
Click to expand...
Click to collapse
Do not risk it with p8, p8max had different rom
newfulluser said:
Do not risk it with p8, p8max had different rom
Click to expand...
Click to collapse
Ok
TMHAKIM said:
can you still access eRecovery? try restoring EMUI though that
Click to expand...
Click to collapse
My hauwei p8 max still has emui.
The person I bought it off has TWRP installed he put a rom on then bricked it.
Just have to find the right firmware
chaschas said:
My hauwei p8 max still has emui.
The person I bought it off has TWRP installed he put a rom on then bricked it.
Click to expand...
Click to collapse
then your only option is to removing all the partitions and use testpoint to restore the partitions
it is not worth it to do this just savage the parts of it and get a refurbished huawei p10 lite phone those phones have a lot of rom support
TMHAKIM said:
then your only option is to removing all the partitions and use testpoint to restore the partitions
Click to expand...
Click to collapse
But how when it is bricked
chaschas said:
But how when it is bricked
Click to expand...
Click to collapse
so it does not even turn on?
TMHAKIM said:
so it does not even turn on?
Click to expand...
Click to collapse
All the firmware 730l that i use goes to emui only 5% then goes back to logo.
I think that TWRP he put on might interfere with it?
Process to install security updates on rooted Nokia 8
Download the Nokia 8 OTA zip files on your Computer from this link in the OTA folder https://bit.ly/nokia-nb1 (it's usually up to date)
Download the Nokia 8 latest FULL ROM OTA zip file on your Computer from this link in the OTA folder https://bit.ly/nokia-nb1 (usually with size above 1 GB, currently it is: NB1-5150-0-00WW-B03-update.zip 1.52 GB)
Connect the phone to the PC using the USB cable and enable USB debugging (after enabling developer options)
Verify connection and drivers are correct on your computer by using the following ADB/Fastboot command(minimal adb fastboot can be found here https://forum.xda-developers.com/showthread.php?t=2317790):
adb devices
Click to expand...
Click to collapse
If you see your device and ID then all good so far
Use the following adb command on your Computer
adb reboot bootloader
Click to expand...
Click to collapse
Alternative to the previous step, you can select ADB sideload from the stock recovery menu after booting into stock.
when the device reboots into bootloader / or ADB sideload is selected from recovery use this command on your computer:
adb sideload path_to_zip/FULL_ROM_OTA.zip
Click to expand...
Click to collapse
Once loaded, reboot using the command
adb reboot
Click to expand...
Click to collapse
Sideload the OTA updates you have downloaded in step 1 using the same process as before OR Update normally through android system settings. Keep updating and restarting until you have the latest update
Download the latest Nokia 8 Stock boot image file on your phone from this link in the STOCK BOOT folder https://bit.ly/nokia-nb1 (it's usually up to date)
Make sure you have the correct Stock boot image file for the the software version you have. (if you have May update, use May image, June update then use June Image, etc....)
Use magisk manager to root the boot image you just downloaded. Use the second option like in the photo below
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Transfer the patched image file to your computer
Get back to bootloader (download mode) using any method or the below code (USB debugging on)
adb reboot bootloader
Click to expand...
Click to collapse
When in download mode, use the following command on your computer and take note of the result (in case something goes wrong)
fastboot getvar current-slot
Click to expand...
Click to collapse
Use the following command:
fastboot flash boot path_to_zip/patched_boot.img
Click to expand...
Click to collapse
Reboot
Enjoy
Wait one more month
Repeat
Tested scenarios:
Working on TA-1012 to get the Pie May 2019 update from April update
Working on TA-1012 to get the June 2019 update from May update
Working on TA-1012 to get back to latest rom (NB1-5150-0-00WW-B03-update) from April update
Working on TA-1012 to get back to latest rom (NB1-5150-0-00WW-B03-update) from May update
Working on TA-1012 to get back to latest rom (NB1-5150-0-00WW-B03-update) from June update
Screenshot, showing update using system settings to May update, after sideloading full ROM (NB1-5150-0-00WW-B03-update) from a rooted device on May update, proving downgrading works fine.
June files have been updated to the link: https://bit.ly/nokia-nb1
Thanks to Dorian Stoll
Well I got nowhere. The moment I reboot into bootloader, the device isn't visible in adb anymore, but only under "fastboot devices", so "adb sideload path-" fails because it can't find the device. What gives?
VonZigmas said:
Well I got nowhere. The moment I reboot into bootloader, the device isn't visible in adb anymore, but only under "fastboot devices", so "adb sideload path-" fails because it can't find the device. What gives?
Click to expand...
Click to collapse
Boot into recovery and select "apply update from adb" as shown in the photo below (not mine)
Kiwironic said:
Boot into recovery and select "apply update from adb" as shown in the photo below (not mine)
Click to expand...
Click to collapse
I'm still on TWRP at this stage. I can't get past step 7.
Hi guys,
is it necessary to sideload OTA updates? Can I just update the system in settings and then flash a rooted boot image corresponding to the update version?
VonZigmas said:
I'm still on TWRP at this stage. I can't get past step 7.
Click to expand...
Click to collapse
This is for people like me who are not able to run twrp on their phones. If you have twrp you should be able to flash the zip file easy. This guide assumes you have stock recovery
Update: confirmed working for July update as well.
I'm sorry if this seems dumb, but I'm kinda new to all of this. I have TWRP and now I want the July patch, how can I do it?
Update: I gave up and flashed stock recovery.
helscarthe said:
I'm sorry if this seems dumb, but I'm kinda new to all of this. I have TWRP and now I want the July patch, how can I do it?
Update: I gave up and flashed stock recovery.
Click to expand...
Click to collapse
In twrp it should be straight forward to flash a zip file which includes the update. Another option or if this fails, start sideload from twrp like in the following photos
Hi, links no longer working. Does anyone have working links for V5.15D ? I need stock boot image and OTA update to sideload. Thanks.
Unfortunately the phone has been abandoned by the developers. I have got myself a xiaomi 9t.
I'm sorry
Kiwironic said:
Unfortunately the phone has been abandoned by the developers. I have got myself a xiaomi 9t.
I'm sorry
Click to expand...
Click to collapse
It's ok thanks for your work on it!
Kiwironic said:
Unfortunately the phone has been abandoned by the developers. I have got myself a xiaomi 9t.
I'm sorry
Click to expand...
Click to collapse
Oh man, can you still get stock images or whatnot anywhere? I only need the least that will get me back to stock before I turn it in for warranty but not sure where to start.
Sorry man I relied on the other developer's repository so much that I can't offer any tools nor files. I can help you get to stock easy. As Nokia offers the original Rom on their website officially. I believe it can be found here
https://www.nokia.com/phones/en_int/betalabs
Register for beta labs then de register and download the latest firmware they offer you
Kiwironic said:
Sorry man I relied on the other developer's repository so much that I can't offer any tools nor files. I can help you get to stock easy. As Nokia offers the original Rom on their website officially. I believe it can be found here
https://www.nokia.com/phones/en_int/betalabs
Register for beta labs then de register and download the latest firmware they offer you
Click to expand...
Click to collapse
Hey, sorry for the late reply. I attempted to get back to stock via NOST and the 5150 image he provided https://forum.xda-developers.com/no...re-nokia-to-stock-t3867646/page3#post80627823 , but turns out I don't have critical unlocked and seem to have misplaced the unlock key. What can I do next?
VonZigmas said:
Hey, sorry for the late reply. I attempted to get back to stock via NOST and the 5150 image he provided https://forum.xda-developers.com/no...re-nokia-to-stock-t3867646/page3#post80627823 , but turns out I don't have critical unlocked and seem to have misplaced the unlock key. What can I do next?
Click to expand...
Click to collapse
Try unlocking again using the Nokia unlock Web page
Kiwironic said:
Try unlocking again using the Nokia unlock Web page
Click to expand...
Click to collapse
The web page requires a validation code that you get from the unlock app from your phone and as we know the app gives a nice "Device not support" if you try running it on Pie. Tested myself just in case.
Kiwironic said:
Try unlocking again using the Nokia unlock Web page
Click to expand...
Click to collapse
In the end I've decided to just go for it and see what happens. Shouldn't make things worse. Flashed the stock boot image for my security patch right on top of TWRP. The phone booted, but I still couldn't install updates. Tried flashing the next update (May) from both ADB and the SD card - failed with the same download state initialization error. Figured I may as well try the same but with the full .zip of my current OS version (April) and while it took pretty long, it finished with no issues and OTA's started rolling in without a hiccup. Surprisingly I didn't even lose any of my data in the process, which I was preparing for. I guess all that's left is to lock the bootloader?
Anyway thanks for the help!
Today I will be giving a tutorial on how to root the Huawei P20 Lite using STOCK ROM (ANE-LX1 ANE-L01 ANE-L21)
If you need bootloader unlock code
----------------------------------------
You can use dc-unlocker but, only if you can rollback to 8.0.0.146 or lower (i was on 8.0.0.46 when i used dc-unlocker).
You can try to use PotatoNV, but that will require testpoint access (haven't tested yet).
You can use HCU client with a 3day account pass, which is quite expensive (I have not actually tested this yet).
Rollback EMUI 9 to EMUI 8
-----------------------------
This is where my frustrations with this phone began.
You can try to use dload method, but in my experience this DOES NOT WORK when you're on EMUI 9.
It will just give you an error about incompatible version, every time.
Forced dload was also a complete bust for me, 24 hours wasted
I was finally able to rollback from HiSuite 11. I was on 9.1.0.200 when I had the option to rollback and it rolled me back to 8.0.0.163.
From 8.0.0.163 I could use normal dload to rollback further until I could use dc-unlocker.
I made the mistake of upgrading to EMUI 9 after I unlocked my bootloader. My advise: if you can manage to get to 8, stay there. It's less bloated and feels smoother. I have not received the option to rollback after I re-upgraded to 9 since. And I have not found AANNYY method to rollback to 8 since then, I pretty much gave up and stayed on EMUI 9.
EMUI 8
---------
copy magisk23.zip to sdcard
flash twrp to recovery_ramdisk.img
Code:
fastboot flash recovery_ramdisk "twrp-3.2.1-0.img"
EDIT: ***NEW official TWRP version*** TWRP 3.6.2.0_9-0
Code:
fastboot flash recovery_ramdisk "twrp-official-3.6.2_9-0-anne.img"
Code:
fastboot reboot recovery
Once in twrp install the magisk23.zip file.
This will patch the boot.img from recovery_ramdisk.img with magisk v23
Reboot -> System
Once in android you will get the usual magisk app, open and allow to perform additional tasks like installing the manager app.
Pretty straight forward
EMUI 9
---------
While still on stock firmware, update your android to the highest possible firmware (HiSuite or on phone -> Settings -> System ....)
1. When your back in android power off phone.
2. Go into fastboot (USB cable plugged in -> Power + Vol Down)
3. Flash twrp into recovery_ramdisk
Code:
fastboot flash recovery_ramdisk twrp-3.2.1-0.img
Code:
fastboot reboot recovery
Now In TWRP
4. Install Image -> twrp-3.2.1-0.img into eRecovery partition
5. Install Image -> magisk23_patched-ane.img into Recovery Partition
6. Reboot -> Recovery
Note: So booting into recovery mode gives you a ROOTED environment and System Mode gives you NON-ROOTED.
EDIT: *** With the new TWRP 3.6.2.0_9-0 you will have to boot into recovery (by holding Vol Up + Power till the screen comes on) every time you boot the phone or it will boot into normal system where the root environment isn't present ***
That's it. Now you should have root access.
You can still use twrp, but you have to access it like you would access eRecovery. So from power off (coldstart) -> Hold Vol Up while plugging in the USB Cable, continue to hold Vol Up, till you get the twrp logo.
Caution: This overwrites eRecovery, this can be dangerous, as eRecovery is the only thing standing between you can a hard brick if twrp wont boot anymore. This is due to fastboot not being able to flash eRecovery. You can only flash eRecovery from twrp. This is particularly dangerous if your data partition gets corrupted, this can happen when formatting data through twrp 3.4.0 and above. When your data partition is corrupt, twrp will freeze on the loading logo, leaving you no way to flash the original eRecovery.
Note: I think you can flash the eRecovery_ramdisk.img over the normal recovery_ramdisk in case of a brick situation. Though I haven't tested that idea yet, im just planning on going that route if I run into such a scenario. The eRecovery is particularly usefull as it can recover almost any situation by using wifi to download a stock rom and full flash that entire rom.
This way is robust, no need for key combo's when restarting the device etc.
All Downloads (GDrive):
Gdrive
After the root, you might find yourself needing safetynet attest pass.
This can be achieved by:
1. Open Magisk and setup MagiskHide ( Search on XDA if you don't know how to do this )
2. Magisk Modules -> Install Riru
3. Magisk Modules -> Install from storage -> Select safetynet-fix-v2.1.0.zip
note: If PropsConfig is installed, remove it first and reboot
If you need to use Smali then it's once again kinda straight forward.
1. Copy /system/framework to sdcard (anywhere u can copy it from)
2. Copy the framework folder onto pc
3. Open SmaliPatcher.exe -> Select the framework folder -> select patch options and patch
4. Copy the created magisk module zip file onto sdcard
5. Install magisk module -> Magisk -> Modules -> Install from storage
Hope you have a smooth experience rooting this device.
External links:
Tested custom recoveries from -Alf-
Source of rooting and flashing information by -Alf-
Credits:
@-Alf- for the magisk patched image. I only repatched his recovery_ramdisk from magisk v21 to v23
And also for the twrp recovery 3.2.1-0 GAGUGA Edition
RESERVED
gh0stza said:
And I have not found AANNYY method to rollback to 8 since then,
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/losq-lir-lineageos-17-1-18-1-unofficial-gsi.4219291/post-85379393
gh0stza said:
eRecovery is the only thing standing between you can a hard brick if twrp wont boot anymore
Click to expand...
Click to collapse
there is one more thing - Service ROM aka 'full stock ROM' & dload method
gh0stza said:
your data partition gets corrupted, this can happen when formatting data through twrp.
Click to expand...
Click to collapse
Can happen only with TWRP 3.4.0 and above.
Regards
No matter what I did, dload failed, I must have downloaded 30 roms and tried every which way with dload. Nothing worked!!!!!
dload only worked on same EMUI. So nope sorry dude dload was a no go for me. Maybe it works for someone else, which is why I mentioned it.
And yes, TWRP 3.4.0 and above. I was using a twrp(3.5.2_9-0) from official twrp repository for ANE-LX1 when I formatted my data partition. However, that's not the point.
Someone else is absolutely BOUND to fall into this trap too, and as I said that TWRP came from the official chain.
So my only intention is to warn the next guy who might just be using that version or for whatever other reason twrp doesn't start anymore. I'm just saying - BE CAREFUL
gh0stza said:
No matter what I did, dload failed, I must have downloaded 30 roms and tried every which way with dload. Nothing worked!!!!!
dload only worked on same EMUI. So nope sorry dude dload was a no go for me. Maybe it works for someone else, which is why I mentioned it.
And yes, TWRP 3.4.0 and above. I was using a twrp(3.5.2_9-0) from official twrp repository for ANE-LX1 when I formatted my data partition. However, that's not the point.
Someone else is absolutely BOUND to fall into this trap too, and as I said that TWRP came from the official chain.
So my only intention is to warn the next guy who might just be using that version or for whatever other reason twrp doesn't start anymore. I'm just saying - BE CAREFUL
Click to expand...
Click to collapse
this is why we have this article here: https://forum.xda-developers.com/t/recommended-and-tested-twrp-recovery.4199099/
-Alf- said:
this is why we have this article here: https://forum.xda-developers.com/t/recommended-and-tested-twrp-recovery.4199099/
Click to expand...
Click to collapse
Shiet dude, 3 full days rooting this device and I didn't come upon this post once. Now I'm gonna have to try to downgrade again with HuRUpdater and that twrp.
That's a nice post - thanks
gh0stza said:
Shiet dude, 3 full days rooting this device and I didn't come upon this post once. Now I'm gonna have to try to downgrade again with HuRUpdater and that twrp.
That's a nice post - thanks
Click to expand...
Click to collapse
What is your regional variant?
-Alf- said:
Oreo and Pie Stock & Custom ROMs:
3.2.1-0 by pretoriano80 (data decryption on Android 8 ) - on Pie use this TWRP e.g. if you want to downgrade to Oreo via HuRupdater.
https://mega.nz/#!Fgd0xa4R!1o5ejzDnkLJLG2tAZG-STtlJ4nnNCHfwwZdOlmOkrVw
Click to expand...
Click to collapse
Are you saying I should try to use this TWRP to use HuRUpdater to downgrade to 8?
I plan on using the HiSuite downloaded firmware ANE-LX1 8.0.0.163(C185) with HuRUpdater.
Current folder stucture:
ANE-LX1 8.0.0.163(C185)\full\update.zip
ANE-LX1 8.0.0.163(C185)\full\ANE-L01_hw_meafnaf\update_full_ANE-L01_hw_meafnaf.zip
Planned folder structure after renames:
ANE-LX1 8.0.0.163(C185)\full\update.zip
ANE-LX1 8.0.0.163(C185)\full\update_all_hw.zip
ANE-LX1 8.0.0.163(C185)\full\HuRUpdater_0.4.zip
Then flash HuRUpdater_0.4.zip in twrp 3.2.1-0 by pretoriano80 like the quoted text suggests?
Am I getting this right?
PS: The twrp I am using now -> 3.2.1-0 GAGUGA Edition (Also the one in my download hyperlink)
EDIT: I am on 9.1.0.355(C185) now. But, it is still trying to give me OTA update of the exact same build, so dunno what thats about
gh0stza said:
The twrp I am using now -> 3.2.1-0 GAGUGA Edition (
Click to expand...
Click to collapse
Read carefully bro: https://forum.xda-developers.com/t/losq-lir-lineageos-17-1-18-1-unofficial-gsi.4219291/post-85380241
You need 3 .zip files - update, hw and data
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
gh0stza said:
Are you saying I should try to use this TWRP to use HuRUpdater to downgrade to 8?
Click to expand...
Click to collapse
Bingo!
Then I have a problem.
Not one single downloaded firmware anywhere gave me 3 files. It's always just the update.zip (or update_sd.zip for dload) and the hw update.
How can HiSuite flash that firmware then? I just need to flash this 163 rom. But nothing works
***EDIT***
Know what, doesn't matter. I'm pretty fed up with this phone and how Huawei implemented this phones partitioning style and just everything.
I mean where is Odin for Huawei? And just how they withdrew support to get unlock code, limited fastboot command etc.
Just everything about huawei....
I got my ANE-LX1 to a stable root with everything I need working perfectly, so Imma call it a win and move on.
But, you've been great dude and basically almost all useful information I got either came from you ( @-Alf- ) or XDA, so thnx everyone
gh0stza said:
Then I have a problem.
Not one single downloaded firmware anywhere gave me 3 files. It's always just the update.zip (or update_sd.zip for dload) and the hw update.
How can HiSuite flash that firmware then? I just need to flash this 163 rom. But nothing works
***EDIT***
Know what, doesn't matter. I'm pretty fed up with this phone and how Huawei implemented this phones partitioning style and just everything.
I mean where is Odin for Huawei? And just how they withdrew support to get unlock code, limited fastboot command etc.
Just everything about huawei....
I got my ANE-LX1 to a stable root with everything I need working perfectly, so Imma call it a win and move on.
But, you've been great dude and basically almost all useful information I got either came from you ( @-Alf- ) or XDA, so thnx everyone
Click to expand...
Click to collapse
Try this way out...
Flash via dload
https://androidhost.ru/1lsA
and try downgrade via HiSuite.
-Alf- said:
Try this way out...
Flash via dload
https://androidhost.ru/1lsA
and try downgrade via HiSuite.
Click to expand...
Click to collapse
Ok, download started
First thing tomorrow morning, even though I just got everything just right with EMUI 9.
You think it's worth it?
gh0stza said:
I made the mistake of upgrading to EMUI 9 after I unlocked my bootloader. My advise: if you can manage to get to 8, stay there.It's less bloated and feels smoother.
Click to expand...
Click to collapse
gh0stza said:
You think it's worth it?
Click to expand...
Click to collapse
dunno how to respond to that....
I'll keep it in my back pocket, when i'm bored some time this week I might try it.
Else screw it, to hell with you huawei.
PS: Still better then the LG G6, which is unrootable (short of opening it up) due to the total inablility to get unlock code.
so do we run this to keep the stock eRecovery?
Install Image -> twrp-3.2.1-0.img into eRecovery partition
coz i got stuck in a situation where the phone would boot to twrp only and nothing else, somehow managed to get back to stock
khal_nayak said:
Install Image -> twrp-3.2.1-0.img into eRecovery
Click to expand...
Click to collapse
this is only necessary if you want to have both Magisk root and TWRP on board at the same time. (on EMUI 9.1 ramdisk is
included in the recovery_ramdisk).
If you don't need TWRP, just flash magisk_patched_recovery in fastboot mode.
ok but i was trying to remove bloatware i caused the rom to bootloop and then tried factory reset from twrp and now other than twrp nothing boots, where can i get factory image from to get it back to working?
all i need is root with magisk and want to keep the stock erecovery.
if there are better custom roms with volte etc all working then im willing to try it out
khal_nayak said:
tried factory reset from twrp
Click to expand...
Click to collapse
That was not a good idea. On Huawei phones, you can only perform a factory reset from stock recovery.
khal_nayak said:
where can i get factory image from to get it back to working
Click to expand...
Click to collapse
Depends on your build number - model, EMUI version, region variant (Cxxx). What is your b.number?
khal_nayak said:
custom roms with volte etc all working
Click to expand...
Click to collapse
All Treble GSI ROMs on Huawei have common bugs - no VoLTE, no offline charging, no native call recording...
since now i can only boot to twrp and fastboot mode how do i know the model and region?
i bought the phone as nova3e in UAE and currently was on emui 9.1, if i can just get the erecovery back then can make it download the firmware and flash it