Related
Hi Guys
Maybe one of you can help me. I unlocked the bootloader flashed twrp and my phone get in trouble with self reboots every 10 minutes. So i flashed the Stock Recovery back and relock the bootloader. Now i can't make a factory reset in recovery. Every time when i boot in recovery i land in eRecovery and get screen on the picture, when i try the first option for download latest version and recovery it doesn't. The phone connect to my WIFI but thats all. The error is Getting package info failded! So what can i do to solve this :fingers-crossed::good:
eRecovery works for China firmware only, MHA-AL00
Thread can be deleted by a MOD problem is solved THX :good:
GraveDigger176 said:
Thread can be deleted by a MOD problem is solved THX :good:
Click to expand...
Click to collapse
Tell us what you did to solve it.
For others who might run into the same problem
ante0 said:
Tell us what you did to solve it.
For others who might run into the same problem
Click to expand...
Click to collapse
I flashed the C432B186 with HWOTA methode. First i Unlock the bootloader in adb, let low factory reset running, after the reboot i boot in bootloader again and start the HWOTA tool and let install the TWRP, then i unplugged my phone and boot in TWRP and choose "Swipe for Modification" (that is nowhere mentioned, because when you choose "Keep read Only" it will failed, at least on my phone, don't know whether it fail on every phone), then i plugged the phone in again and did the steps that HWOTA tool shows me and it works perfect. After the first boot up i boot in Recovery with adb command and the option for factoy reset in eRecovery is back :good:
Alex266 said:
eRecovery works for China firmware only, MHA-AL00
Click to expand...
Click to collapse
I just was able to use eRecovery to go back to stock (and upgrade from B180 to B190 on USA model MHA-L29C567).... so it did work for me.
I had the same problem. Actually it can be solved quite easily. reboot the system with a United States SIM card insert, then shutdown the system, enter eRecovery again, now everything works as perfect as before. I think Huawei judge your location by the SIM card you use.
GraveDigger176 said:
Thread can be deleted by a MOD problem is solved THX :good:
Click to expand...
Click to collapse
hi GraveDigger176 , is there anyway to unlock the bootloader w/o the unlock codes?
I've tried a lot but no success, the new hisuite even flashes the update rom but after reboot it goes back to eRecovery. (Chinese mate9)
thanks.
wheelee said:
hi GraveDigger176 , is there anyway to unlock the bootloader w/o the unlock codes?
I've tried a lot but no success, the new hisuite even flashes the update rom but after reboot it goes back to eRecovery. (Chinese mate9)
thanks.
Click to expand...
Click to collapse
As far as i know you need a unlock code, but Huawei didn't give any code since 1 or 2 month. On the other hand i sold my Mate 9 a couple of days after the Problem was solved :good:
GraveDigger176 said:
As far as i know you need a unlock code, but Huawei didn't give any code since 1 or 2 month. On the other hand i sold my Mate 9 a couple of days after the Problem was solved :good:
Click to expand...
Click to collapse
used DCunlocker spend around 19eu but no go, brought to the shop's here in the middle kingdom & they got it fixed but now No Sound. there was a cloud password so they kinda have a long time to fix it. 1 day.
Oh BT sound is OK.
Hello everyone, By upgrading so many times, and testing every build finally i found the solution for all who didn't get Oreo update till now.
Follow these steps to install oreo beta update manually:
Note: Follow all the instructions carefully, and install all the OTA at your own risk, i m not be responsible for any cause to you phone or if u brick your device.
Step 1: Install MENA firmware from here
Step 2: Reset your phone so you can install everything in clean mode and least number of bugs may appear. For reseting your phone goto System Setting->backup & reset->reset
Step 3: Now download July, August, September, October, only November 13 update and December update [for oreo] from herehttps://forum.xda-developers.com/no...ly-updates-t3733784/post75162860#post75162860
Note: Remember don't download November 29 update from above link.
Step 4:Now Download the Oreo Beta build OTA from here
Step 5:Now Start installing OTA from JULY, AUGUST, SEPTEMBER, OCTOBER, NOVERMBER 13 Update and December update manually via recovery.
Step 6: Now finally install Oreo OTA via recovery menu and wait to finish all setting
Enjoy Oreo into your phone.
Press thanks button if i helped you guys.
Thanks to :
blackpanther0582
qwertysmerty
Akilesh T
harisn
my devices is rooted and i am on 7.1.1 with Android Security Patch Level June 1, 2017
can i use your method to update to Oreo even if my device is rooted?
U can unroot it and follow the steps and can enjoy oreo right now
I first discovered this metod
https://forum.xda-developers.com/showpost.php?p=74926353&postcount=48
And,you don't need to install Oreo via recovery,just right after you finish with December update,the Oreo OTA kick in,if you registered your phone on Nokia Labs.
Marius.Petran said:
I first discovered this metod
https://forum.xda-developers.com/showpost.php?p=74926353&postcount=48
And,you don't need to install Oreo via recovery,just right after you finish with December update,the Oreo OTA kick in,if you registered your phone on Nokia Labs.
Click to expand...
Click to collapse
Your steps didn't mention about to install only November 13 update, also not everyone is getting the OTA on there phone,
when you applied the DECEMBER updates to your phone, your phone might have the build number 00WW_3_70D, thats only the reason that u find OTA, Indian user get different build number after december update, that is 00A0_3_700_SP02, there fore we dont get any OTA after applying manually update...
My method works for all the phone, world wide, u can try this in case u brick ur phone...or want to updte ur phone to oreo manually.
What if i use this method without unrooting my device? Or fiat install updates and after oreo can i root my device?
sargodian2 said:
What if i use this method without unrooting my device? Or fiat install updates and after oreo can i root my device?
Click to expand...
Click to collapse
For installing OTA through recovery, its necessary to be unrooted, because rooting your device cause some error in binary files that stops system to install official OTA on the phone, there for you need to install it in clean mod and in unroot condition.
after oreo update, i will advice you to do not root your phone as its a beta build and could cause your phone with boot looping
so install it without rooting..
press thanks if it was useful to you.
Nokia 6
Hi,I am having Nokia 6 Ta-1000.can I try this on my mobile.
gamez cliq said:
Hi,I am having Nokia 6 Ta-1000.can I try this on my mobile.
Click to expand...
Click to collapse
Ya sure, but only thing i want to advice u is, many people installed this firmware and happy with that , u also can give a try....just be careful during all the steps.. happy flashing :angel:
I have updated oreo via your process. Thanks
Tell me couple of things.
1. I will get official Oreo through OTA right & why am I still uncertified in playstore?
2. When can I revert back to 7.1.2 in case I want?
humankit said:
I have updated oreo via your process. Thanks
Tell me couple of things.
1. I will get official Oreo through OTA right & why am I still uncertified in playstore?
2. When can I revert back to 7.1.2 in case I want?
Click to expand...
Click to collapse
Well i also want to ask few things,
1. Is your phone is chinese varient
2. What is your phone showing you, when you are using play store.
Now answer:
When official Oreo will be available, i will provide the roll back ota too also if your phone is not Chinese version and your imei number and carrier is eligible for oreo beta on nokia beta labz page, then you can request there for roll back ota...
Till as soon as possible i will try to upload the roll back ota to for oreo beta users....
Hit thanks button if this is useful for you..
sltushar said:
Well i also want to ask few things,
1. Is your phone is chinese varient
2. What is your phone showing you, when you are using play store.
Now answer:
When official Oreo will be available, i will provide the roll back ota too also if your phone is not Chinese version and your imei number and carrier is eligible for oreo beta on nokia beta labz page, then you can request there for roll back ota...
Till as soon as possible i will try to upload the roll back ota to for oreo beta users....
Hit thanks button if this is useful for you..
Click to expand...
Click to collapse
Thank you for your answer.
1.I have Nokia 6 TA-1021, I have done all mena and all.
2. Device Certification shows Uncertified.
3. When I tried going in recovery mode, phone displayed a screen with fallen android logo and NO COMMAND written.
4. Nokia Beta Labs has verified my device.
humankit said:
Thank you for your answer.
1.I have Nokia 6 TA-1021, I have done all mena and all.
2. Device Certification shows Uncertified.
3. When I tried going in recovery mode, phone displayed a screen with fallen android logo and NO COMMAND written.
4. Nokia Beta Labs has verified my device.
Click to expand...
Click to collapse
Well oreo beta doesn't contain any recovery menu and though u have nokia TA-1021 Then i would like to suggest u to flash mena firmware and then format it from recovery and then start installing patches as written on the instructions...because clean installation is recommended for oreo
It might certified your phone, because my phone is certified even i m on the oreo, see on the attachment
Hope it will help u
Hit thanks it this helps u
humankit said:
Thank you for your answer.
1.I have Nokia 6 TA-1021, I have done all mena and all.
2. Device Certification shows Uncertified.
3. When I tried going in recovery mode, phone displayed a screen with fallen android logo and NO COMMAND written.
4. Nokia Beta Labs has verified my device.
Click to expand...
Click to collapse
Hey sorry, i also find my device in google play as uncertified and it may be the reason because of beta oreo, may be official oreo can fix this issue....till ask any user who get OTA officially and if he has the certified device in google play store....
Mine showing uncertified
What should we do now? Any idea
humankit said:
What should we do now? Any idea
Click to expand...
Click to collapse
The thing is, everything is running fine and it may be due to beta version of oreo, official version may solve this issue in future till i think we should create a thread over it
Yes, I tried rolling back through beta labs but have not received any updates.
Have you given it a go?
humankit said:
Yes, I tried rolling back through beta labs but have not received any updates.
Have you given it a go?
Click to expand...
Click to collapse
Right now i dont want to rollback, cause if we get rollback ota, then also u will lose all you data and roll back to fresh 7.1.2 with December patch
So i have arround 161 apps installed and re-installing them, it tooks a long time...
Secondly we manually can't rollback as there is no recovery option
So i would suggest u that, use oreo for now, in future when official oreo will be available, i would try to give its all steps, procedure, ota etc to install them.. till happy using oreo beta
Hit thanks if this helps u
Thank you mate.
Mine is certified, received Beta Oreo OTA.
I've bricked my phone while trying to roll back from Oreo update, then used DC Unlocker to unbrick my phone and return everything to normal (including IMEI, SN...) but I don't have initial phone setup after factory reset (first boot). Do you have any suggestions?
aleksp994 said:
I've bricked my phone while trying to roll back from Oreo update, then used DC Unlocker to unbrick my phone and return everything to normal (including IMEI, SN...) but I don't have initial phone setup after factory reset (first boot). Do you have any suggestions?
Click to expand...
Click to collapse
I had been in the same situation as you are to use DC Phoenix to unbrick my phone. If you have successfully boot to nougat (emui 5) then follow these steps;
1. Unlock bootloader,
2. install TWRP
3. Rebrand your device to your original brand
4. install the rollback package by dload method
5. install the OTA updates as received.
Your phone will be back to normal. It worked well for me.
Hi,
Thanks for your reply.
I don't think that you understand the problem that I'm having. I have returned everything back to normal with those same steps that you wrote. The only problem that I have now is the initial setup wizard app. It doesn't start when I factory reset the phone (you know that screen for logging into google account, connecting to wifi, etc...). I was on marshmallow, then I updated to Nougat via official OTA.
aleksp994 said:
Hi,
Thanks for your reply.
I don't think that you understand the problem that I'm having. I have returned everything back to normal with those same steps that you wrote. The only problem that I have now is the initial setup wizard app. It doesn't start when I factory reset the phone (you know that screen for logging into google account, connecting to wifi, etc...). I was on marshmallow, then I updated to Nougat via official OTA.
Click to expand...
Click to collapse
Yes i understand your problem, so insiting on rebranding your device to your brand again. Means if your phone originally is FRD-L02C675 (e.g.) then rebrand to that again and then follow dload method. After installing via dload method do factory reset. This will help you solve the problem and you will have normal startup with initial setup.
But I did that already. My device model is c432, and I managed to install russian firmware without rebranding. When I used dc phoenix and then flashed via dload I didnt have to rebrand because my device was slready c432.
Then i am not sure what could be troubling your phone to run the setup wizard. May some other member could help you to resolve this.
Are you able to login to google services?
Yes, Im able to login and use my phone normally
aleksp994 said:
Yes, Im able to login and use my phone normally
Click to expand...
Click to collapse
you may have installed the firmware badly, before installing it do a wipe of the data partition from the twrp, restart it in recovery and try to install the firmware again..
I know this should be in Rom,kernels,rev. I'm a junior member so I can't post their yet
So I've recently rooted my phone. I got too excited and tried installing a custom boot animation that screwed up my phone and it couldn't shut down only restart.
Then I had an idea to wipe the system through TWRP and I accidentally deleted everything (Wiped internal storage) so download mode was blank. Then I tried installing stock Rom but I extracted it, removed the stock recovery.img.lz4 and replaced it with the TWRP Recovery. For some weird reason the firmware was acting weird with T mobile roaming and stuff that wasn't supposed to be there cause I'm not a t mobile customer. Then I just flashed stock Rom (Augaust security patch) with Odin. Aaand I got RMM Locked again :crying::crying:
I thought flashing combination firmware again would allow me to access the OEM unlock option and flash TWRP again.
When I tried to flash I got an error SW rev check fails device 3 binary 2. If anyone could help me I would really appreciate it. Also if anyone knows why I got the T mobile stuff after I did the TWRP thing (out of curiosity) I would like to know. Please respond.
DeadRatGames said:
I know this should be in Rom,kernels,rev. I'm a junior member so I can't post their yet
So I've recently rooted my phone. I got too excited and tried installing a custom boot animation that screwed up my phone and it couldn't shut down only restart.
Then I had an idea to wipe the system through TWRP and I accidentally deleted everything (Wiped internal storage) so download mode was blank. Then I tried installing stock Rom but I extracted it, removed the stock recovery.img.lz4 and replaced it with the TWRP Recovery. For some weird reason the firmware was acting weird with T mobile roaming and stuff that wasn't supposed to be there cause I'm not a t mobile customer. Then I just flashed stock Rom (Augaust security patch) with Odin. Aaand I got RMM Locked again :crying::crying:
I thought flashing combination firmware again would allow me to access the OEM unlock option and flash TWRP again.
When I tried to flash I got an error SW rev check fails device 3 binary 2. If anyone could help me I would really appreciate it. Also if anyone knows why I got the T mobile stuff after I did the TWRP thing (out of curiosity) I would like to know. Please respond.
Click to expand...
Click to collapse
It seems that your filmware is corrupt.
Which bootloader binary are you on, binary 2 or 3, Nougat or Oreo?
Remember that if you have binary 3 you cannot downgrade to binary 2.
And don't use the combination rom anymore because you have to know what you're doing its risky.
I can advise you to do a fresh install of the official country filmware from out of the box, and after that update to the latest filmware version, and a big chance to get rid of RMM prenormal state, with oem-unlock back.
If you're on binary 2, just flash an official filmware from your country before the August security patch, after that update it again to the latest version.
solamente said:
It seems that your filmware is corrupt.
Which bootloader binary are you on, binary 2 or 3, Nougat or Oreo?
Remember that if you have binary 3 you cannot downgrade to binary 2.
And don't use the combination rom anymore because you have to know what you're doing its risky.
I can advise you to do a fresh install of the official country filmware from out of the box, and after that update to the latest filmware version, and a big chance to get rid of RMM prenormal state, with oem-unlock back.
If you're on binary 2, just flash an official filmware from your country before the August security patch, after that update it again to the latest version.
Click to expand...
Click to collapse
Thanks for responding, I'm currently on binary 3 on android Oreo August security patch.
What do you mean by a fresh install from out of the box. Like Download the latest version from updato?
I apologise if I seem a little clueless lol.
DeadRatGames said:
Thanks for responding, I'm currently on binary 3 on android Oreo August security patch.
What do you mean by a fresh install from out of the box. Like Download the latest version from updato?
I apologise if I seem a little clueless lol.
Click to expand...
Click to collapse
What I meant is the first official filmware you had when the phone was bought,and if you were on binary 2, but that doesn't matter now you're on binary 3.
Now you have to flash the official filmware from your country, it must be a binary 3 filmware because downgrading will not work.
After that you have to do jailtime for 168 hours untill oem unlock is gonna appear again.
Do not restart the phone or disconnect the network at this time.
solamente said:
What I meant is the first official filmware you had when the phone was bought,and if you were on binary 2, but that doesn't matter now you're on binary 3.
Now you have to flash the official filmware from your country, it must be a binary 3 filmware because downgrading will not work.
After that you have to do jailtime for 168 hours untill oem unlock is gonna appear again.
Do not restart the phone or disconnect the network at this time.
Click to expand...
Click to collapse
Do I really need to wait 168 hours lol?
DeadRatGames said:
Do I really need to wait 168 hours lol?
Click to expand...
Click to collapse
Unfortunately you do with the 1 august patch, if you can find a previous official filmware, for example april, may, june or juli patch you can do the trick to set back the date and time 7 days and get oem unlock back.
But this does not work anymore with the august patch or later, that means you have to wait 7 days.
solamente said:
Unfortunately you do with the 1 august patch, if you can find a previous official filmware, for example april, may, june or juli patch you can do the trick to set back the date and time 7 days and get oem unlock back.
But this does not work anymore with the august patch or later, that means you have to wait 7 days.
Click to expand...
Click to collapse
How do I downgrade though?
DeadRatGames said:
How do I downgrade though?
Click to expand...
Click to collapse
At this time its impossible to downgrade from a binary 3 towards 2 or from 2 to 1.
You can only upgrade, Samsung has blocked the downgrading from a higher to a lower binary, therefore it is useless to try it with Odin, it won't succeed.
Maybe someone else knows a way around to downgrade, but I don't.
DeadRatGames said:
I know this should be in Rom,kernels,rev. I'm a junior member so I can't post their yet
So I've recently rooted my phone. I got too excited and tried installing a custom boot animation that screwed up my phone and it couldn't shut down only restart.
Then I had an idea to wipe the system through TWRP and I accidentally deleted everything (Wiped internal storage) so download mode was blank. Then I tried installing stock Rom but I extracted it, removed the stock recovery.img.lz4 and replaced it with the TWRP Recovery. For some weird reason the firmware was acting weird with T mobile roaming and stuff that wasn't supposed to be there cause I'm not a t mobile customer. Then I just flashed stock Rom (Augaust security patch) with Odin. Aaand I got RMM Locked again :crying::crying:
I thought flashing combination firmware again would allow me to access the OEM unlock option and flash TWRP again.
When I tried to flash I got an error SW rev check fails device 3 binary 2. If anyone could help me I would really appreciate it. Also if anyone knows why I got the T mobile stuff after I did the TWRP thing (out of curiosity) I would like to know. Please respond.
Click to expand...
Click to collapse
1. You didn't posted in the wrong section. This one is the correct one, the one where you wanted to post is reserved to ROMs, kernels and other projects.
2. Modifying Official firmwares is a bad idea if you don't know how to do it. Seems also you downloaded the wrong firmware for your phone.
3. Flashing Combination firmware is useless since OEM Toggle is still enabled (you said you were rooted so I suppose yes). RMM flag is still stored in RPMB and doesn't gets resetted by flashing that factory fw, to set RMM back to Normal you need to flash the full stock firmware for your country and wait the classic 168h countdown.
4. The "SW REV. CHECK FAIL (BOOTLOADER) DEVICE: x, BINARY: x" is caused because you're trying to flash a firmware with a lower rev. than the one installed in your phone. You need to flash a firmware with the same or higher rev (In this case, you need a XXU3/XXS3 or higher fw). Forget to flash a fw with a lower rev since RP fuse prevents you to do it (if you force install the bl via TWRP you get an hardbrick)
BlackMesa123 said:
1. You didn't posted in the wrong section. This one is the correct one, the one where you wanted to post is reserved to ROMs, kernels and other projects.
2. Modifying Official firmwares is a bad idea if you don't know how to do it. Seems also you downloaded the wrong firmware for your phone.
3. Flashing Combination firmware is useless since OEM Toggle is still enabled (you said you were rooted so I suppose yes). RMM flag is still stored in RPMB and doesn't gets resetted by flashing that factory fw, to set RMM back to Normal you need to flash the full stock firmware for your country and wait the classic 168h countdown.
4. The "SW REV. CHECK FAIL (BOOTLOADER) DEVICE: x, BINARY: x" is caused because you're trying to flash a firmware with a lower rev. than the one installed in your phone. You need to flash a firmware with the same or higher rev (In this case, you need a XXU3/XXS3 or higher fw). Forget to flash a fw with a lower rev since RP fuse prevents you to do it (if you force install the bl via TWRP you get an hardbrick)
Click to expand...
Click to collapse
Thanks for responding currently I am on stock official firmware for my country and waiting 7 days,6 days left. I appreciate you all for responding. I want to ask one last thing, if I wipe internal storage through TWRP and delete the OS (blank download mode) can I not install a binary 2 boot loader?
DeadRatGames said:
Thanks for responding currently I am on stock official firmware for my country and waiting 7 days,6 days left. I appreciate you all for responding. I want to ask one last thing, if I wipe internal storage through TWRP and delete the OS (blank download mode) can I not install a binary 2 boot loader?
Click to expand...
Click to collapse
Already replied: no. First, there's no relation between bootloader and system (why should a wipe let you flash a lower rev bootloader lol). And as I already explained, Rollback Prevention fuse avoids you to do that: in Odin if you try to flash a lower rev bin it returns an error. If you try to force install it via TWRP, you'll hard brick your device and get a dead phone
BlackMesa123 said:
Already replied: no. First, there's no relation between bootloader and system (why should a wipe let you flash a lower rev bootloader lol). And as I already explained, Rollback Prevention fuse avoids you to do that: in Odin if you try to flash a lower rev bin it returns an error. If you try to force install it via TWRP, you'll hard brick your device and get a dead phone
Click to expand...
Click to collapse
When I say wipe I mean like complete wipe. Delete everything not just date like fully wipe internal storage. But anyway thanks.
Reformat system.
DeadRatGames said:
When I say wipe I mean like complete wipe. Delete everything not just date like fully wipe internal storage. But anyway thanks.
Click to expand...
Click to collapse
Don't take any risks or you will be ending up with a hard brick, like Mesa said!
Just do your time 6 days I think.
solamente said:
Don't take any risks or you will be ending up with a hard brick, like Mesa said!
Just do your time 6 days I think.
Click to expand...
Click to collapse
Ok. Thanks
ok so i have 2 of my a8's that are frp locked right now to the same frikken account and i can't remember what it is now. one is binary 2 and the other 3. both have no oem unlock in combination so i can't bypass... will this work for me? if so how do i know what my original firmware was? or do you mean just original carrier? also when waiting the 7 days where do i let them idle during the wait if i can't get passed google login during install?
both are sm-a530w both on oreo. binary 2 and 3
vibespredah said:
ok so i have 2 of my a8's that are frp locked right now to the same frikken account and i can't remember what it is now. one is binary 2 and the other 3. both have no oem unlock in combination so i can't bypass... will this work for me? if so how do i know what my original firmware was? or do you mean just original carrier? also when waiting the 7 days where do i let them idle during the wait if i can't get passed google login during install?
both are sm-a530w both on oreo. binary 2 and 3
Click to expand...
Click to collapse
same questions
vibespredah said:
ok so i have 2 of my a8's that are frp locked right now to the same frikken account and i can't remember what it is now. one is binary 2 and the other 3. both have no oem unlock in combination so i can't bypass... will this work for me? if so how do i know what my original firmware was? or do you mean just original carrier? also when waiting the 7 days where do i let them idle during the wait if i can't get passed google login during install?
both are sm-a530w both on oreo. binary 2 and 3
Click to expand...
Click to collapse
use this technic and your problem will be solved : youtube/watch?v=WmvjDEk6w4E
amazing. youre the man. cheers.
samalderon said:
use this technic and your problem will be solved : youtube/watch?v=WmvjDEk6w4E
Click to expand...
Click to collapse
omg youre the best. thanks so much.
I have a seemingly stupid but still annoying problem. As many of you know Android 8 + EMUI 8 came out this summer and I have updated my Honor8. Everything works well, even better (especially with regard to the battery) apart from a problem, quite annoying. I have seen that everyone around complains about the same problem, so it is clear that both a build bug and not a local problem.
Basically ... the bluetooth link with the multimedia system of my car doesn't work as it should, while it worked well with the 7.0.
Tracknames, music infos disappears, sometimes it connects regularly, starting the music, sometimes nothing happens, sometimes the music passes from the car speakers to smartphone (!!)... in short, manage the music in the car It has become a big problem!
I tried all possible options; reset pairing, reset bluetooth, clear cache, activate the developer options to control some low-level aspects of bluetooth, and finally installed Bluetooth Auto Connect which also has several advanced options. Nothing works. In the meantime an update of 8.0 has been released (mine is the buiold 521). The update came out in September ... maybe (MAYBE) this update fixes all bluetooth issues (but i don't have any detailed info about). Until today I have not received any updates and normally I check new version regularly every day. At this point I decided to return to Nougat!
And here the adventure begins!
I CANNOT IN ANY WAY do the downgrade.
What I tried:
- through HiSuite. The "back to previous version" option appears random (rarely); normally the program tells me "the system is up to date". Once appeared I tried to run the procedure, but after the decompression it gives me an error "error updating".
- by standard Rollback procedure. Using a microSD and putting the full version of Nougate in the dload folder. The installation starts but stops almost immediately with the same "update cannot be applied" error.
At this point I am desperate. I cannot update Oreo, I can't go back to Nougat and meanwhile the bluetooth still doesn't work with my car. Remember that before Oreo, everything worked very well!
What can I do? Can you help me?
Thank you
hi / i can help u / pls say me this:
your region(Ru/Eu/Cn.......)
your model( FRD-L09/L19/L04........)
Your Build number
and which build you upgrade to emui 8
m2relax said:
hi / i can help u / pls say me this:
your region(Ru/Eu/Cn.......)
your model( FRD-L09/L19/L04........)
Your Build number
and which build you upgrade to emui 8
Click to expand...
Click to collapse
Region: EU
Model: FRD-L09
Build: 8.0.0.521 (C432)
Previous Build: don't remember. It was Nougat, and I've upgraded around the first week of September. From that day I haven't received/applied any patch, because nothing appears until now.
This morning I've tried again with HiSuite. As usual it says I'm running the latest version and it doesn't offer any downgrade option .
Thelothian said:
Region: EU
Model: FRD-L09
Build: 8.0.0.521 (C432)
Previous Build: don't remember. It was Nougat, and I've upgraded around the first week of September. From that day I haven't received/applied any patch, because nothing appears until now.
This morning I've tried again with HiSuite. As usual it says I'm running the latest version and it doesn't offer any downgrade option .
Click to expand...
Click to collapse
dont worry/ do u change region of your phone past?
m2relax said:
dont worry/ do u change region of your phone past?
Click to expand...
Click to collapse
Never. And never jailbroken or rooted...
Thelothian said:
Never. And never jailbroken or rooted...
Click to expand...
Click to collapse
ok / pls do this work step by step :
1-Get Unlock Code for your Phone
2-Unlock your phone with Unlock Code
3-install TWRP recovery
4-after install TWRP notice me to send a file for u ( u must flash it from recovery TWRP )
5-after flashing u most install recovery stock
6-End and your problem is done! :fingers-crossed:
m2relax said:
ok / pls do this work step by step :
1-Get Unlock Code for your Phone
2-Unlock your phone with Unlock Code
3-install TWRP recovery
4-after install TWRP notice me to send a file for u ( u must flash it from recovery TWRP )
5-after flashing u most install recovery stock
6-End and your problem is done! :fingers-crossed:
Click to expand...
Click to collapse
I Heard TWRP doesn't work well on Oreo...
CurlyApple said:
I Heard TWRP doesn't work well on Oreo...
Click to expand...
Click to collapse
no if you use multi tools 8 for install twrp its work perfectly on oero
m2relax said:
no if you use multi tools 8 for install twrp its work perfectly on oero
Click to expand...
Click to collapse
The more you know...
Finally I've decide to try updating to 8.0.0.562. After a month of tries, fails (damn Huawei and his stupid update system), errors and a lot of other stupid things, I was finally able to update my Honor hoping the latest version will fix all the problems. It was a enormous waste of time (searching around internet)... but in the end I found a method described here: https://forum.xda-developers.com/huawei-p20-pro/help/p20-pro-bricked-t3868085#4And if you go ahead you should find the correct firmware link (on a Russian site). Although, IMHO, failing with the classic method was due to the impossibility or some bugs in the update system, to unpack the update files on sdcard. So the solution seems to be to leave both the zip and the unpacked folder.The problems with bluetooth remain, but I hope that now there is not to be crazy applying next updates. ATTENTION: the method above is NOT valid for rollback! If you try, you'll brick your Honor.
And finally I've taken an important decision... for me this is the last Huawei/honor device. Next time I'll go to another brand, with a serious update system.
Hello,
I have the same problem whit my honor, bluetooth lost signal random times, and my battery is faster get low, on android 7 i dont feel thees problems. Anyone have an idea how can i downgrade to nougat or marshmallow? My phone infos:
-FRD-L09 8.0.0.521(C432), I bought it in Hungary (i think its an EU modell), the phone have an unlocked bootloader, and flashed whit TWRP recovery
Who know the solution, pls reply here or, write me an email. Big thanks
scseke said:
Hello,
I have the same problem whit my honor, bluetooth lost signal random times, and my battery is faster get low, on android 7 i dont feel thees problems. Anyone have an idea how can i downgrade to nougat or marshmallow? My phone infos:
-FRD-L09 8.0.0.521(C432), I bought it in Hungary (i think its an EU modell), the phone have an unlocked bootloader, and flashed whit TWRP recovery
Who know the solution, pls reply here or, write me an email. Big thanks
Click to expand...
Click to collapse
flash this file with twrp and install stock recovery and do reset factor / finally use hisuite to rollback