Help me out ..this is what happens when I try to unlock boot loader.. I did factory reset but still the problem persists...
excitedgeek said:
Help me out ..this is what happens when I try to unlock boot loader.. I did factory reset but still the problem persists...
Click to expand...
Click to collapse
Logout and login in that should do
I also face this issue. Did you fix this anyhow?
Kaffer94 said:
I also face this issue. Did you fix this anyhow?
Click to expand...
Click to collapse
Verify your email...
Kaffer94 said:
I also face this issue. Did you fix this anyhow?
Click to expand...
Click to collapse
Verify your email that u used to login your SYNC IT app...
excitedgeek said:
Verify your email...
Click to expand...
Click to collapse
Believe me. I did that. Aswell as a ton of other things but nothing seems to work...
---------- Post added at 11:49 AM ---------- Previous post was at 11:32 AM ----------
excitedgeek said:
Verify your email that u used to login your SYNC IT app...
Click to expand...
Click to collapse
It somehow looks like i can't connect to the lenovo servers. When i check for OTA updates, i get an error saying that i have no network available.
I tried rebooting, logging in and out, even did a factory reset but i'm still somehow unable to unlock my bootloader and now also check for otas..
Kaffer94 said:
Believe me. I did that. Aswell as a ton of other things but nothing seems to work...
---------- Post added at 11:49 AM ---------- Previous post was at 11:32 AM ----------
It somehow looks like i can't connect to the lenovo servers. When i check for OTA updates, i get an error saying that i have no network available.
I tried rebooting, logging in and out, even did a factory reset but i'm still somehow unable to unlock my bootloader and now also check for otas..
Click to expand...
Click to collapse
Then create a new Lenovo id...I hope it works.....I did the same thing & it worked
excitedgeek said:
Then create a new Lenovo id...I hope it works.....I did the same thing & it worked
Click to expand...
Click to collapse
Wow, i just did this and it worked. So strange that it works but it works.
Thank you for your help, i was at loss here!
Kaffer94 said:
Wow, i just did this and it worked. So strange that it works but it works.
Thank you for your help, i was at loss here!
Click to expand...
Click to collapse
Thank my post ..
I've done the same, logged out, factory reset and created a new Lenovo ID but it still isn't working for me
I've done the same, logged out, factory reset and created a new Lenovo ID but it still isn't working for me
Related
Hi,
I have the Canadian LG G4 (LG-H812) with stock rom unrooted and my recent apps button is not working properly. After the phone has been running for several hours the recent apps menu always shows blank. However, if I reboot my phone, it starts functioning normally again but then always goes blank after a few hours of uptime and doesn't repopulate with new apps as I open them until I reboot again. Does anyone know what's going on here and how to fix it?
tia,
Erika
ErikaS91984 said:
Hi,
I have the Canadian LG G4 (LG-H812) with stock rom unrooted and my recent apps button is not working properly. After the phone has been running for several hours the recent apps menu always shows blank. However, if I reboot my phone, it starts functioning normally again but then always goes blank after a few hours of uptime and doesn't repopulate with new apps as I open them until I reboot again. Does anyone know what's going on here and how to fix it?
tia,
Erika
Click to expand...
Click to collapse
no sure what causes that issue. but you can try 2 things..
1. do a factory reset.
2. if it continues. flash stock firmware using LGUP and your H812 KDZ file..
I have the same problem on my nexus 5
Do you use tasker?
Nexus 5 via Tapatalk
varazir said:
I have the same problem on my nexus 5
Do you use tasker?
Nexus 5 via Tapatalk
Click to expand...
Click to collapse
No, I don't use Tasker. I did a factory reset and it still keeps happening. It's really frustrating.
raptorddd said:
no sure what causes that issue. but you can try 2 things..
1. do a factory reset.
2. if it continues. flash stock firmware using LGUP and your H812 KDZ file..
Click to expand...
Click to collapse
Factory reset didn't fix anything and I can't find the stock KDZ file for my Bell LG G4 anywhere.
ErikaS91984 said:
Factory reset didn't fix anything and I can't find the stock KDZ file for my Bell LG G4 anywhere.
Click to expand...
Click to collapse
here it is.. theres telus and videotron.. not sure wich one you should download.
http://storagecow.eu/index.php?dir=Xda/LG+G4/
ErikaS91984 said:
No, I don't use Tasker. I did a factory reset and it still keeps happening. It's really frustrating.
Click to expand...
Click to collapse
Okay, just a thought it could have been something with a voice plugin.
Do you user OK Google ?
---------- Post added at 09:44 PM ---------- Previous post was at 09:43 PM ----------
I have/had the same on my nexus 5 and read that someone with a Samsung had the same problem.
Skickat från min Nexus 5 via Tapatalk
varazir said:
Okay, just a thought it could have been something with a voice plugin.
Do you user OK Google ?
---------- Post added at 09:44 PM ---------- Previous post was at 09:43 PM ----------
I have/had the same on my nexus 5 and read that someone with a Samsung had the same problem.
Skickat från min Nexus 5 via Tapatalk
Click to expand...
Click to collapse
Yes, I do use OK Google.
ErikaS91984 said:
Yes, I do use OK Google.
Click to expand...
Click to collapse
Only common thing I have found then is that it happen when using OK Google.
I use it every day to control my home automation system.
I have the problem right now time for a reboot.
Alright I posted about this on reddit.com/r/googlepixel earlier tonight and thought I fixed my issue. I installed Bully Scholarship Edition and within the first couple minutes of gameplay, my phone froze and some black bars appeared on screen. It rebooted several times then went totally blank. Couldn't get into bootloader/recovery. After putting it on the charger for a little bit, it turns back on. I thought all was good until after a couple hours it does the same thing after just being on the home screen. I consider myself pretty knowledgeable when it comes to smartphones and rooting/roming but am stuck. I tried flashing stock system images and it was okay again for a while but it eventually froze with the black bars on screen and kept rebooting. Is my best bet to RMA it. Any help would be appreciated.
Edit: Ok its officially dead. Screen won't turn on but can hear vibrations from notifications or if I hold power button to get to the power menu. RIP
I personally would try to RMA it, it sounds like a persistent issue. Did you try not installing apps and just run that way for 24 hours?
chapelfreak said:
I personally would try to RMA it, it sounds like a persistent issue. Did you try not installing apps and just run that way for 24 hours?
Click to expand...
Click to collapse
Ya I just got off of chat with Google. They are replacing it
what? dude all you have to do is flash stock boot.img why the hell wasn't that the first thing you tried. sounds like a kernel panic to me
---------- Post added at 04:24 PM ---------- Previous post was at 04:22 PM ----------
not sure why you would ever RMA without trying to first go back to stock firmware and factory reset
diabl0w said:
what? dude all you have to do is flash stock boot.img why the hell wasn't that the first thing you tried. sounds like a kernel panic to me
---------- Post added at 04:24 PM ---------- Previous post was at 04:22 PM ----------
not sure why you would ever RMA without trying to first go back to stock firmware and factory reset
Click to expand...
Click to collapse
I'm not dumb. I did both a factory reset first with no luck then flashed latest factory images. Still same issues persisting. It must be a hardware issue. I should be receiving a new one fairly soon
bdog2015 said:
I'm not dumb. I did both a factory reset first with no luck then flashed latest factory images. Still same issues persisting. It must be a hardware issue. I should be receiving a new one fairly soon
Click to expand...
Click to collapse
okay you didnt mention that
diabl0w said:
okay you didnt mention that
Click to expand...
Click to collapse
From the OP....
I tried flashing stock system images and it was okay again for a while
Click to expand...
Click to collapse
Threadskimmer!
CZ Eddie said:
From the OP....
Threadskimmer!
Click to expand...
Click to collapse
system images don't overwrite anything but the system partition
diabl0w said:
system images don't overwrite anything but the system partition
Click to expand...
Click to collapse
I don't think anyone would be dumb enough to only flash a system.img and not the whole factory image
Sent from my Pixel XL using Tapatalk
A few days ago I flashed on the SM-A520F a random combination file(im dumb i know now) Then every time I try to flash, can't do it unless flashing without BL file in ODIN.
If I flash the stock rom will work but after a while the phone starts to slow until it powers off and stays on bootloop or stuck in samsung logo.
The error flashing shown on the device its
SW Check error(idkr): Device: 3 Binary 2.
Tried Kies, Old Kies, Smart Switch and old Smart Switch with no success. Old ones for the recovery feature.
FRP Off
Cant flash recoveries cause Device: 3 Binary < 3
Cant root.
IMEI shown like "unknown"
Help plz
Thank u
You need to flash the latest Bootloader.
I do not know which country is your rom, but you need to flash the latest firmware from 7.0 with XXU3 version.
Kauris said:
A few days ago I flashed on the SM-A520F a random combination file(im dumb i know now) Then every time I try to flash, can't do it unless flashing without BL file in ODIN.
If I flash the stock rom will work but after a while the phone starts to slow until it powers off and stays on bootloop or stuck in samsung logo.
The error flashing shown on the device its
SW Check error(idkr): Device: 3 Binary 2.
Tried Kies, Old Kies, Smart Switch and old Smart Switch with no success. Old ones for the recovery feature.
FRP Off
Cant flash recoveries cause Device: 3 Binary < 3
Cant root.
IMEI shown like "unknown"
Help plz
Thank u
Click to expand...
Click to collapse
Flash latest firmware for your country/region.
If bootloader locked, wait 168 hours without rebooting to allow bootloader to unlock (Samsung playing games). This will then allow for TWRP to be clashed via Odin and off you go.
moozer said:
Flash latest firmware for your country/region.
If bootloader locked, wait 168 hours without rebooting to allow bootloader to unlock (Samsung playing games). This will then allow for TWRP to be clashed via Odin and off you go.
Click to expand...
Click to collapse
Ok, will try that out, I will then report what is up here.
Also. how do you know about the seven days? kinda curious
Thank you.
Kauris said:
Ok, will try that out, I will then report what is up here.
Also. how do you know about the seven days? kinda curious
Thank you.
Click to expand...
Click to collapse
There's been ideas surrounding RMM state and this has been researched by a few users. RMM state was removed after 7 days, but specifically 168 hours. One user let this extend to 169 hours just to make sure. He was successful. Suggestions have also been to the bootloader unlock to be a similar security measures enforced by Samsung to deter users from circumventing device infrastructures.
There is a script out there to flash to prevent the lockdown. This is for users to flash before updating firmware, so once you are hopefully back up and running, you could flash that to secure the bootloader for the next update (this would have to be repeated for subsequent updates). I can point you to this once everything is back to normal for you.
I sincerely hope it works for you
---------- Post added 14th February 2018 at 12:10 AM ---------- Previous post was 13th February 2018 at 11:52 PM ----------
Kauris said:
Ok, will try that out, I will then report what is up here.
Also. how do you know about the seven days? kinda curious
Thank you.
Click to expand...
Click to collapse
Hi...this post details it all...
https://forum.xda-developers.com/sa...ow-to-root-january-security-patch-sm-t3739225
moozer said:
Hi...this post details it all...
https://forum.xda-developers.com/sa...ow-to-root-january-security-patch-sm-t3739225
Click to expand...
Click to collapse
After reading it all, I thank u a lot, but i still have a question, does unlocking rmm means that the "Device 3 Binary < 3" will never ever appearing again, and i can downgrade it?
Thank u <3
Edit: What I have:
-Bootloop.
-Weirdy coloured messages on top of the screen on loop.
-Device 3 Binary < 3 On download mode, preventing me from flashing.
-IMEI problem.
What I am going to do:
1:Flash XXU3 Stock FirmWare.
2:Check IMEI and RMM.
What I got:
1: For now, flashing XXU3 does not show DeviceBinary problem. (good)
2n loop, not showing any more weirdy coloured messages.
3: Not slowing or restarting. I am getting there, I hope I can end this story good and help some folks later.
Kauris said:
After reading it all, I thank u a lot, but i still have a question, does unlocking rmm means that the "Device 3 Binary < 3" will never ever appearing again, and i can downgrade it?
Thank u <3
Edit: What I have:
-Bootloop.
-Weirdy coloured messages on top of the screen on loop.
-Device 3 Binary < 3 On download mode, preventing me from flashing.
-IMEI problem.
What I am going to do:
1:Flash XXU3 Stock FirmWare.
2:Check IMEI and RMM.
What I got:
1: For now, flashing XXU3 does not show DeviceBinary problem. (good)
2n loop, not showing any more weirdy coloured messages.
3: Not slowing or restarting. I am getting there, I hope I can end this story good and help some folks later.
Click to expand...
Click to collapse
Cool.
So...probably downgrading is not an option. Never a good idea anyway, but pretty sure you can't downgrade from U3 bootloader.
Stick with what you have.
---------- Post added at 09:36 AM ---------- Previous post was at 08:58 AM ----------
moozer said:
Cool.
So...probably downgrading is not an option. Never a good idea anyway, but pretty sure you can't downgrade from U3 bootloader.
Stick with what you have.
Click to expand...
Click to collapse
What have you managed to flash with Odin so far?
moozer said:
Cool.
So...probably downgrading is not an option. Never a good idea anyway, but pretty sure you can't downgrade from U3 bootloader.
Stick with what you have.
---------- Post added at 09:36 AM ---------- Previous post was at 08:58 AM ----------
What have you managed to flash with Odin so far?
Click to expand...
Click to collapse
I gotta wait those seven days, went to download mode, got "RMM State : Prenormal"
Will update then
Kauris said:
I gotta wait those seven days, went to download mode, got "RMM State : Prenormal"
Will update then
Click to expand...
Click to collapse
This is still a positive. Be patient and avoid the temptation to restart. Keep an eye on your up time
moozer said:
This is still a positive. Be patient and avoid the temptation to restart. Keep an eye on your up time
Click to expand...
Click to collapse
Man, I forgot to stay on wifi and went with the phone outside, after getting in wifi range, rebooted and gotta wait again. FML
Anyways, i didn't notice that my SIM it is not recognized, on other phone it did, did change network mode, selected network provider and wiped cache on recovery(Stock Recovery obviously).
Nothing worked.
Help, thank u.
Kauris said:
Man, I forgot to stay on wifi and went with the phone outside, after getting in wifi range, rebooted and gotta wait again. FML
Anyways, i didn't notice that my SIM it is not recognized, on other phone it did, did change network mode, selected network provider and wiped cache on recovery(Stock Recovery obviously).
Nothing worked.
Help, thank u.
Click to expand...
Click to collapse
Have you flashed the FULL firmware in Odin?
Edit: After being a while on stock it asked me for updating the device. I accepted.
moozer said:
Have you flashed the FULL firmware in Odin?
Click to expand...
Click to collapse
All of it bl ap cp and csc no problems on flashing nor booting, ROM from my own region.
Kauris said:
All of it bl ap cp and csc no problems on flashing nor booting, ROM from my own region.
Click to expand...
Click to collapse
Can you switch to 3G network?
moozer said:
Can you switch to 3G network?
Click to expand...
Click to collapse
In network mode i dont get those, i get LTE/WCDMA/GSM
And when selecting GSM the phone kinda tries to get the registering done, but then shows error.
Kauris said:
In network mode i dont get those, i get LTE/WCDMA/GSM
And when selecting GSM the phone kinda tries to get the registering done, but then shows error.
Click to expand...
Click to collapse
Try WCDMA
moozer said:
Try WCDMA
Click to expand...
Click to collapse
I did, same result, well not exactly, it does not even show me any loading, just the error "Unable to connect, try later."
Kauris said:
I did, same result, well not exactly, it does not even show me any loading, just the error "Unable to connect, try later."
Click to expand...
Click to collapse
Try to ignore registering on networks. Just try selecting network type.
Change to GSM. leave it and see what it does.
Reboot. Check.
If no luck....change network type to WCDMA. Wait.
Reboot. Check.
If you notice more response on one, then check APNs.
Make sure APN settings are correct for your provider (your network provider should have information on this on their support site)
I'm on UK time, so will check in with you tomorrow. Post your findings here
Kauris said:
I did, same result, well not exactly, it does not even show me any loading, just the error "Unable to connect, try later."
Click to expand...
Click to collapse
Any luck?
moozer said:
Any luck?
Click to expand...
Click to collapse
Ah Nope, turning on and off airplane mode didnt work either.
Since updating to Pie every once in a while after a reboot the phone wont take my PIN and tells me it's wrong. Rebooting fixes it generally but I'm worried at some point it wont any longer. Has anyone else had this issue?
thenags said:
Since updating to Pie every once in a while after a reboot the phone wont take my PIN and tells me it's wrong. Rebooting fixes it generally but I'm worried at some point it wont any longer. Has anyone else had this issue?
Click to expand...
Click to collapse
Rooted or not? If rooted, what magisk version are you using?
Yes, rooted. I'm using the latest Beta of Magisk due to issues with the stable version. After posting this it happened again so I had to reboot and upon rebooting it started loop booting. I reflashed Pie over itself and that got me out of loop boots and I've already had the wrong pin issue come up again since. I may just wipe today and start fresh.
Sent from my Pixel 2 XL using Tapatalk
thenags said:
Yes, rooted. I'm using the latest Beta of Magisk due to issues with the stable version. After posting this it happened again so I had to reboot and upon rebooting it started loop booting. I reflashed Pie over itself and that got me out of loop boots and I've already had the wrong pin issue come up again since. I may just wipe today and start fresh.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Did you try flashing this version of Magisk.. https://forum.xda-developers.com/showpost.php?p=77240449&postcount=2832
No, I hadn't. I hadn't seen anyone else mention the PIN issue. Granted, I don't look in the Magisk threads very often. Unfortunately, the link he posts isn't working.
praveen6585 said:
Did you try flashing this version of Magisk.. https://forum.xda-developers.com/showpost.php?p=77240449&postcount=2832
Click to expand...
Click to collapse
Sent from my Pixel 2 XL using Tapatalk
thenags said:
No, I hadn't. I hadn't seen anyone else mention the PIN issue. Granted, I don't look in the Magisk threads very often. Unfortunately, the link he posts isn't working.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
I had this issue by rooting with the non-twrp method. I believe it also was caused by not removing all security before rooting...fingerprints and all. Eventually I ended up in the bootloop of death which I recovered only with fastboot flash-all.
I rooted again after all this (needed my substratum) and so far no issues since remembering to disable all security before rooting.
Ya know. I've always removed all security before flashing but read it's no longer necessary and when flashing Pie it was the first time I ever didn't. Wonder if that's related.
Sent from my Pixel 2 XL using Tapatalk
thenags said:
No, I hadn't. I hadn't seen anyone else mention the PIN issue. Granted, I don't look in the Magisk threads very often. Unfortunately, the link he posts isn't working.
Click to expand...
Click to collapse
Bingo. That's your solution :good:
---------- Post added at 12:56 PM ---------- Previous post was at 12:55 PM ----------
thenags said:
No, I hadn't. I hadn't seen anyone else mention the PIN issue. Granted, I don't look in the Magisk threads very often. Unfortunately, the link he posts isn't working.
Click to expand...
Click to collapse
Here ya go if the link isn't working :good:
https://drive.google.com/file/d/106ZiqeQxNYtCHkOEc6niuHRcWiCzG_eA/view?usp=drivesdk
Badger50 said:
Bingo. That's your solution :good:
---------- Post added at 12:56 PM ---------- Previous post was at 12:55 PM ----------
Here ya go if the link isn't working :good:
https://drive.google.com/file/d/106ZiqeQxNYtCHkOEc6niuHRcWiCzG_eA/view?usp=drivesdk
Click to expand...
Click to collapse
Thank you. At the gym right now but will give it a shot when I'm home.
Sent from my Pixel 2 XL using Tapatalk
Does it solve the PIN Incorrect issue in TWRP as well?
JazonX said:
Does it solve the PIN Incorrect issue in TWRP as well?
Click to expand...
Click to collapse
Negative. That's a twrp thing. Which is hit and miss for many. The 3.2.2-0 seems to work better than the 3.2.3-0 version in that regard. However, it's not consistent among all users
Badger50 said:
Bingo. That's your solution :good:
---------- Post added at 12:56 PM ---------- Previous post was at 12:55 PM ----------
Here ya go if the link isn't working :good:
https://drive.google.com/file/d/106ZiqeQxNYtCHkOEc6niuHRcWiCzG_eA/view?usp=drivesdk
Click to expand...
Click to collapse
Just installed it. Hopefully this does it. Thanks for the help :good:
After a sequence of
1 Shutting down the phone
2 rebooting into safe mode
3 shutting down the phone again
and finaly my pin will work.
I believe its something with android P as I had the updated versions of Magisk and TWRP and worked fine on O.
And of course googles solution is to reset everything. That dose not help ever. Only makes me more frustrated.
Holy ____ just got the same issue and was on the verge of resetting. I was able to boot to recovery and sideloaded the Magisk version above, and it fixed the issue! Thanks @Badger50 !
Badger50 said:
Bingo. That's your solution :good:
---------- Post added at 12:56 PM ---------- Previous post was at 12:55 PM ----------
Here ya go if the link isn't working :good:
https://drive.google.com/file/d/106ZiqeQxNYtCHkOEc6niuHRcWiCzG_eA/view?usp=drivesdk
Click to expand...
Click to collapse
WorldOfJohnboy said:
Holy ____ just got the same issue and was on the verge of resetting. I was able to boot to recovery and sideloaded the Magisk version above, and it fixed the issue! Thanks @Badger50 !
Click to expand...
Click to collapse
Scary as **** the first time, eh? I had just got into bed for the night and was ready to sleep and rebooted my phone for some reason. Bam. Wrong PIN. I was like here we go... gonna be a long night.
praveen6585 said:
Did you try flashing this version of Magisk.. https://forum.xda-developers.com/showpost.php?p=77240449&postcount=2832
Click to expand...
Click to collapse
This zip makes my phone bootloop. Is there an updated one? I am failing safetynet today, anyone else?
JazonX said:
Does it solve the PIN Incorrect issue in TWRP as well?
Click to expand...
Click to collapse
Badger50 said:
Negative. That's a twrp thing. Which is hit and miss for many. The 3.2.2-0 seems to work better than the 3.2.3-0 version in that regard. However, it's not consistent among all users
Click to expand...
Click to collapse
Try "adb reboot recovery" next time or switch to a custom kernel. This way you should always be able to enter your pin without the freezing/crashing. I'd recommend flashing @nathanchance's Flash Kernel via Franco Kernel Manager. Just flash and forget.
SirVilhelm said:
This zip makes my phone bootloop. Is there an updated one? I am failing safetynet today, anyone else?
Click to expand...
Click to collapse
There is this one..
https://nathanchance.me/downloads/magisk/Magisk-v16.7(1675006)-gbfac1f1bc28b.zip
Safety net failing is a known issue.. topjonwu has made the change in the code but a new version is not out yet with that change
praveen6585 said:
There is this one..
https://nathanchance.me/downloads/magisk/Magisk-v16.7(1675006)-gbfac1f1bc28b.zip
Safety net failing is a known issue.. topjonwu has made the change in the code but a new version is not out yet with that change
Click to expand...
Click to collapse
Boot loop on this one as well. oh well, the stable version doesnt seem to be having issues for me.
I have installed the firmware 9.1 twice per dload, and even then I am having random reboots, suddenly the mobile freezes and I come back to request the unlock code, someone to know what is the problem?
It happened to me too. I had to downgrade via HiSuite. It seems to be a problem with the system looking for something related to HwWallet.
More info here
https://forum.xda-developers.com/ma...-crashing-randomly-update-9-1-t3943523/page13
aroldan said:
It happened to me too. I had to downgrade via HiSuite. It seems to be a problem with the system looking for something related to HwWallet.
More info here
https://forum.xda-developers.com/ma...-crashing-randomly-update-9-1-t3943523/page13
Click to expand...
Click to collapse
I'm in version 9.0.0.261, I passed it via dload.
The way is to expect an upgrade from 9.1.0.300?
Yes, unless someone finds a workaround for the problem on 9.1.0.300
I have updated normally via ota and no crashing at all.. But icons changed to square.. Ugly... Circles were much nicer
PhoneTechShop said:
I have updated normally via ota and no crashing at all.. But icons changed to square.. Ugly... Circles were much nicer
Click to expand...
Click to collapse
I had returned to 9.0, yesterday my device upgraded to 9.1 via OTA, but kept giving the problem.
ramonbn said:
I had returned to 9.0, yesterday my device upgraded to 9.1 via OTA, but kept giving the problem.
Click to expand...
Click to collapse
I have no issues .. downloaded huawei themes apps and chnged icons back to circle
---------- Post added at 15:35 ---------- Previous post was at 15:34 ----------
ramonbn said:
I had returned to 9.0, yesterday my device upgraded to 9.1 via OTA, but kept giving the problem.
Click to expand...
Click to collapse
I have no issues .. downloaded huawei themes apps and changed icons back to circle
PhoneTechShop said:
I have no issues .. downloaded huawei themes apps and chnged icons back to circle
---------- Post added at 15:35 ---------- Previous post was at 15:34 ----------
I have no issues .. downloaded huawei themes apps and changed icons back to circle
Click to expand...
Click to collapse
I received 9.1.0.300 via OTA, but continued with the same problem. I got to 9.1.0.310 and went through the download today, let's see if the problem will be solved or not.
ramonbn said:
I received 9.1.0.300 via OTA, but continued with the same problem. I got to 9.1.0.310 and went through the download today, let's see if the problem will be solved or not.
Click to expand...
Click to collapse
do factory
PhoneTechShop said:
do factory
Click to expand...
Click to collapse
I did not understand
ramonbn said:
I did not understand
Click to expand...
Click to collapse
Jeez... Do factory reset
Yes. But it continued with the same problem. In 9.1.0.310 solved the problem. For now
PhoneTechShop said:
Jeez... Do factory reset
Click to expand...
Click to collapse
Yes.