Hello All,
I am at the end of my rope with trying to fix my phone. The back story is I successfully rooted my Mate 10 Pro using TWRP and Magisk from a guide I found here. I didn't even want to root this phone until I saw a cool video on mirroring your rooted phone with Android Auto. When that didn't end up working I decided to unroot my phone and return it to factory condition. Unfortunately when I did this my phone would not boot into stock and I lost TWRP of course so it will now only boot into Erecovery and fails to download the update package. I have since paid for FunkyHuawei and also DC-Phoenix. My bootloader is unlocked but the FPR is locked and I was able to flash firmware files using DC-Phoenix. However, it still will not boot up without wanting to go through eRecovery first. I can't find 8.0.0.119 firmaware so I tried 8.0.0.112. Maybe I need to try 8.0.0.110 or another one? It doesn't seam to me that should matter... I also cannot create a DNS because I have stupid Comcast internet and my router doesn't have that option. Am I screwed!?
androidstereoman said:
Hello All,
I am at the end of my rope with trying to fix my phone. The back story is I successfully rooted my Mate 10 Pro using TWRP and Magisk from a guide I found here. I didn't even want to root this phone until I saw a cool video on mirroring your rooted phone with Android Auto. When that didn't end up working I decided to unroot my phone and return it to factory condition. Unfortunately when I did this my phone would not boot into stock and I lost TWRP of course so it will now only boot into Erecovery and fails to download the update package. I have since paid for FunkyHuawei and also DC-Phoenix. My bootloader is unlocked but the FPR is locked and I was able to flash firmware files using DC-Phoenix. However, it still will not boot up without wanting to go through eRecovery first. I can't find 8.0.0.119 firmaware so I tried 8.0.0.112. Maybe I need to try 8.0.0.110 or another one? It doesn't seam to me that should matter... I also cannot create a DNS because I have stupid Comcast internet and my router doesn't have that option. Am I screwed!?
Click to expand...
Click to collapse
So you successfully flashed a full firmware with DC-Phoenix but still doesn't boot? Which version did you flashed and which version were you on.
Also, which method did you used with Phoenix, fastboot with your own firmware?
Tried a factory reset after flashing with Phoenix.
I'm asking all this questions because if Phoenix flashed everything successfully, then it should've worked.
Pretoriano80 said:
So you successfully flashed a full firmware with DC-Phoenix but still doesn't boot? Which version did you flashed and which version were you on.
Also, which method did you used with Phoenix, fastboot with your own firmware?
Tried a factory reset after flashing with Phoenix.
I'm asking all this questions because if Phoenix flashed everything successfully, then it should've worked.
Click to expand...
Click to collapse
I was on BLA-A09 8.0.0.119 before I bricked it. I could not find that version so I flashed it with the closest one I could find, BLA-A09 8.0.0.112. I used DC-Phoenix and opened the Update.APP and flashed in fastboot. I tried a factory reset after flashing and the phone still boots into eRecovery and fails to download the package.
androidstereoman said:
I was on BLA-A09 8.0.0.119 before I bricked it. I could not find that version so I flashed it with the closest one I could find, BLA-A09 8.0.0.112. I used DC-Phoenix and opened the Update.APP and flashed in fastboot. I tried a factory reset after flashing and the phone still boots into eRecovery and fails to download the package.
Click to expand...
Click to collapse
***UPDATE*** I got home and tried flashing BLA-A09 8.0.0.110 using DC-Phoenix and then factory reset the phone after and it worked! I was then able to update to BLA-A09 8.0.0.125 using HiSuite. Success!
Related
I installed RROS on my honor 9 (STF-L09C432 from 3 UK) a few weeks ago, however due to many issues with it I decided to go back to EMUI. I eventually managed this using the rebrand guide, but just flashing without rebrand. I flashed B120 firmware as many people said this is the only rom where the torch and capacitive keys work if you are flashing from a non-EMUI OS.
The flash went perfectly and everything works, except I cannot OTA, software update is listing me as being on the latest firmware, but I know it isnt from firmware finder. If I try to upgrade via firmware finder, it all works till the phone restarts, then the recovery just throws an error, and says it can't be installed.
Fastboot says FRP and bootloader are unlocked onscreen however trying to flash anything, or run the rebrand script on a newer firmware just gets command not allowed. I suspect I need to try unlocking the bootloader again, however I don't want to factory reset, as while I can backup app data with huawei backup I preferably need as little downtime as possible
Although the phone passes safety net, I get a error message saying device can't be verified on boot, and huawei apps warn my my phone is insecure.
Does anyone have any other ideas to get it to update, as especially as oreo is rolling out I would like OTA to work?
killmeplease69 said:
I eventually managed this using the rebrand guide, but just flashing without rebrand. I flashed B120 firmware (...) If I try to upgrade via firmware finder, it all works till the phone restarts, then the recovery just throws an error, and says it can't be installed.
Click to expand...
Click to collapse
From C432B120 without ota working I've be able to update straight to 'B183 full ota approved by imei' with Firmware Finder.
I then normal updated with ota from C432B183 to B360.
Tough, it was just a downgrade I did to get back to B120, not a rebrand.
After the downgrade my phone and frp status were both locked.
I think I unlocked them again only once on B183 and thet stay that way after updated to B360. Flash and capacitives button are still working.
oslo83 said:
From C432B120 without ota working I've be able to update straight to 'B183 full ota approved by imei' with Firmware Finder.
I then normal updated with ota from C432B183 to B360.
Tough, it was just a downgrade I did to get back to B120, not a rebrand.
After the downgrade my phone and frp status were both locked.
I think I unlocked them again only once on B183 and thet stay that way after updated to B360. Flash and capacitives button are still working.
Click to expand...
Click to collapse
Thank you, I'm now running B183, I was trying to upgrade one by one by OTA in firmware finder because my internet is appallingly slow, but doing a full B183 flash worked. Just waiting for approved B360 now
Hello!
I have updated to pie .161 using the erecovery method via FF. Now if i use the erecovery normally on my phone it just say "Getting package info failed".
This isnt normalt right? There should always be a possibility to restore my phone via this erecovery right? Whats going on?
Have I messed up my phone now?
Cloudstrife said:
Have I messed up my phone now?
Click to expand...
Click to collapse
Erecovery can not mess up your phone.
Erecovery can only recover to the latest available firmware. I guess one reason why you used erecovery is because you have not received the official ota yet. Obviously it cannot recover to Emui 8 easily and emui9 is not officially pushed to your device yet. Result: erecovery cannot find a firmware to recover yet. Though it should be able to discover the 161 build later. It should be the point of time when you would have received the official ota if you had not upgraded yet manually.
The irony :laugh:
Cloudstrife said:
Hello!
I have updated to pie .161 using the erecovery method via FF. Now if i use the erecovery normally on my phone it just say "Getting package info failed".
This isnt normalt right? There should always be a possibility to restore my phone via this erecovery right? Whats going on?
Have I messed up my phone now?
Click to expand...
Click to collapse
The very same thing happened with me when i update my phone through FunkyHuawei. Erecovery stopped working. Then i roll back to Oreo and then install OTA update. Everhthing is working perfectly fine again. Always use the offcial method.
Same thing happened to me but I used the hicare method so it should be official ota but still broke kt
eyeb said:
Same thing happened to me but I used the hicare method so it should be official ota but still broke kt
Click to expand...
Click to collapse
You cannot break the phone by using either FF or erecovery (if your phone is (re)locked and you install approved firmware). That is a fact.
Erecovery is like official OTA. If the firmware is faulty not approved or otherwise not meant to be installed it will only download but fail to verify and install.
It has been reported by fh though that a factory reset on emui 9 beta builds stopped erecovery from working. That is why they came up with the hisuite method for downgrading/updating on emui9.
0alfred0 said:
You cannot break the phone by using either FF or erecovery (if your phone is (re)locked and you install approved firmware). That is a fact.
Erecovery is like official OTA. If the firmware is faulty not approved or otherwise not meant to be installed it will only download but fail to verify and install.
It has been reported by fh though that a factory reset on emui 9 beta builds stopped erecovery from working. That is why they came up with the hisuite method for downgrading/updating on emui9.
Click to expand...
Click to collapse
I downgraded using hisuite, :/ guess I'm back on android 8, but I don't mind so much since I didn't like android 9 that much. I didn't see any improvements overall so going back to 8 was something I thought about before. Now I have a reason to fix this erecovery thing
Found this interesting, after downgrade to 8, I kept the wireless projection function from Android 9 after I restored the backup.
Edit NVM it was the mirrorcasting
I am using Android 9 on my SM-T860. It is rooted. I am using TWRP.
I would like to upgrade to Android 10 with Odin and then re-root the tablet with Magisk using TWRP, is that possible? I think I read someplace that Magisk, Tab S6 and Android 10 were not fully compatible?
Assuming it was okay, do I need to flash WETA kernel and flash Disable_Dm-Verity_ForceEncrypt in TWRP again before Magisk like I did when I first got the Tab and unlocked bootloader and flashed TWRP?
I also had to hard reboot the tablet while it was building cache (it seemed to freeze and that was described in the root guide I followed) the very first time is booted up after all this rooting, would that be necessary again?
My tablet is one that has crashed several times, I hope that it's a software issue and installing new Android will fix it.
Also, why does my PC spell checker not pick up typos like on some other forum post websites? Why isn't there a red squiggly line under errors for my to right click and correct?
Hello i have an tab s6 from tmobile too i want to know if anybody has flaahed it with uk firmware or any other internatiinal firmware and it runs fine or any links to root and unlock it since i been for more than 10 month with the big T and they dont know how to unlock it any info is apreciated thanks
Actually, I think that if I flash my UK WiFi firmware then I will loose TWRP?
Aid777 said:
Actually, I think that if I flash my UK WiFi firmware then I will loose TWRP?
Click to expand...
Click to collapse
Yes. You will lose TWRP. It will be replaced with stock recovery.
I was trying to install a custom rom and was not aware that you can only unlock the bootloader by paying, which is fine but I can't afford it at the moment but by then I downgraded my rom.
I returned to version 9 on my phone OS and was hoping to get updates afterwards through official updates as I was restoring back to stock but I made a mistake and downloaded and installed ANE-LGRP2-OVS 9.1.0.200 which was not the correct one.
I have tried a few roms, copied to SD card in the dload folder but no matter what I try it keeps failing. No matter what I try downgrades and upgrades won't work anymore.
It seems similar to this: https://forum.xda-developers.com/t/downgrade-ane-lx3-ane-lgrp2-ovs-pie-to-oreo.3944399/
Everything does seem to work fine on my phone except the update system and google pay is not happy and not enabling contactless (which I use all the time)
Is there anything I can do to fix my dumbness
How does the dload method fail? Or is it successful in installing a different firmware yet the official update service is still broken?
Have you tried the forced dload method and did a factory reset/wipe data immediately after installation in recovery?
lemon567 said:
How does the dload method fail?
Click to expand...
Click to collapse
for several reasons .
In this specific case it is due to installing the wrong FW (ANE-LGRP2-OVS ). With this build number it is impossible to install another full stock FW or update system via OTA.
I totally forget to mention on here that I solved it. I managed to get hold of a version 8 stock rom and installed it to the SD card, then it was happy to update itself from there all the way up to current version.
I don't know why it worked at that point as I'm pretty sure I tried that same thing several times before but sometimes there are things I cannot explain, it just randomly worked all of a sudden
Hi. I had rooted a galaxy s10 lite, android 11 of a friend of mine. He doesn't need root any more. If i go to settings and search for an official update, it gives me, "phone is running an unofficial firmware and can't be updated" or something like this. Phone is running official firmware but rooted actually.
So if i factory reset from settings I'll obviously loose root. Phone will boot i suppose, if nothing have changed resentlly. Will update then works? He doesn't have a PC. Or because bootloader will be unlocked, will still make update not working?
Thanks,
sosimple said:
Hi. I had rooted a galaxy s10 lite, android 11 of a friend of mine. He doesn't need root any more. If i go to settings and search for an official update, it gives me, "phone is running an unofficial firmware and can't be updated" or something like this. Phone is running official firmware but rooted actually.
So if i factory reset from settings I'll obviously loose root. Phone will boot i suppose, if nothing have changed resentlly. Will update then works? He doesn't have a PC. Or because bootloader will be unlocked, will still make update not working?
Thanks,
Click to expand...
Click to collapse
hello colleague
First of all, back up your information.
You will have to restore the s10 lite with the system from odin.
the bootloader will still be unlocked (if you previously unlocked it)
once restored from odin, you will be able to install updates over wifi.
you can try
restoring from system, but I'm not sure if it will work.
if it has twrp.
If you decide to restore from system and it works for you, you can share your experience, for future reference.
having the bootloader unlocked does not affect ota updates
Thanks.. Yes i know how to do it in odin. That's what i want to pass as I'll probably factory reset his phone without a pc to a coffee shop for example.. When I'll do it, ill post, although i think i won't do it very soon.