After upgrade to Android 10, GPS is having issues. It takes long time to fix a location. Tried all kind of solutions suggested on forums. Tried many apps for clearing, updating AGPS data. Nothing worked permanently.
Did anyone else faced similar issues on A2020U pro?
Also, sometimes notifications from app stopped showing. After I turn off Wifi and when data switches to LTE, I see all older notifications pop up.
I believe it's issue with Android 10. Is there possibility of rollback to its stock Android 9. I saw another thread where OP mentioned that it can be rolled back using the system update, but for that I need to have stock image on sdcard.
For rollback from stock 10 to stock 9, do I need to root/unlock bootloader/or install TWRP?
ccraze said:
After upgrade to Android 10, GPS is having issues. It takes long time to fix a location. Tried all kind of solutions suggested on forums. Tried many apps for clearing, updating AGPS data. Nothing worked permanently.
Did anyone else faced similar issues on A2020U pro?
Also, sometimes notifications from app stopped showing. After I turn off Wifi and when data switches to LTE, I see all older notifications pop up.
I believe it's issue with Android 10. Is there possibility of rollback to its stock Android 9. I saw another thread where OP mentioned that it can be rolled back using the system update, but for that I need to have stock image on sdcard.
For rollback from stock 10 to stock 9, do I need to root/unlock bootloader/or install TWRP?
Click to expand...
Click to collapse
I had a minor issue with my wifi after updating to A10, was fighting with my router. Googled it and basically A10 in general has issues... some people said they were resolved by clearing the dalvik cache. I never got around to trying it and over time the issue seems to have gone away.
Anyhow, the best way to downgrade currently is the EDL tool and firmware package I put together (for exactly this reason). You don't need to root/unlock.
Here's the tools: https://forum.xda-developers.com/t/...ded-edl-tools-new-fixes-general-tips.4174667/
And here's the Android 9 firmware: https://forum.xda-developers.com/t/rom-stock-stock-firmware-packages-for-expanded-edl-tools.4194045/
Make sure you do a full backup of your phone, then install the firmware (to make it easy, just install it to both A and B partitions). More detailed instructions are on the tools thread, ask if you have any questions.
bobthenormal said:
I had a minor issue with my wifi after updating to A10, was fighting with my router. Googled it and basically A10 in general has issues... some people said they were resolved by clearing the dalvik cache. I never got around to trying it and over time the issue seems to have gone away.
Anyhow, the best way to downgrade currently is the EDL tool and firmware package I put together (for exactly this reason). You don't need to root/unlock.
Here's the tools: https://forum.xda-developers.com/t/...ded-edl-tools-new-fixes-general-tips.4174667/
And here's the Android 9 firmware: https://forum.xda-developers.com/t/rom-stock-stock-firmware-packages-for-expanded-edl-tools.4194045/
Make sure you do a full backup of your phone, then install the firmware (to make it easy, just install it to both A and B partitions). More detailed instructions are on the tools thread, ask if you have any questions.
Click to expand...
Click to collapse
I tried clearing the dalvik cache after resetting all apps settings. That also didn't work.
Thanks for the links. I will give it a try to downgrade to previous release and will post how it goes.
Thanks @bobthenormal for the image and EDL tool. I finally tried to flash with EDL and A9 image. I could see the GPS working perfectly fine. Also tested various OTA updates, GPS problem actually starts with 1.13 A9 last security update and not with A10 (2.09). Then I reflashed again to the A9 image and have GPS working.
Now, I am having issues with sensors.
Fingerprint sensor is working but other sensors like Acclerometer, Magnetic, Gyro, Light etc are not working.
If I do the Sensor Test in EMODE with code *983*0# I could see All sensors shows "CTS Fail". Is there any mod or any patch that I can use to get sensors working?
ccraze said:
Thanks @bobthenormal for the image and EDL tool. I finally tried to flash with EDL and A9 image. I could see the GPS working perfectly fine. Also tested various OTA updates, GPS problem actually starts with 1.13 A9 last security update and not with A10 (2.09). Then I reflashed again to the A9 image and have GPS working.
Now, I am having issues with sensors.
Fingerprint sensor is working but other sensors like Acclerometer, Magnetic, Gyro, Light etc are not working.
If I do the Sensor Test in EMODE with code *983*0# I could see All sensors shows "CTS Fail". Is there any mod or any patch that I can use to get sensors working?
Click to expand...
Click to collapse
I think you're past what I know... I can only guess. Do you have a backup of your phone before installing any ROMs/firmware changes?
The other thing I would try is flashing the stock bootloader (you'll get that annoying warning on boot is the only downside). A pretty desperate leap of an idea, but I did have a problem that was only resolved by doing this. Sorry I can't be of more help!
Thanks for getting back. I am able to recover. After updating to v1.11 and v1.13 via OTA, sensors started working. But after sometime GPS again started giving issue. So I had to reflash again. Strange thing noticed that when I flash first to Partition B and then A, I see the issue of sensors not working. If I flash B later then it is working. I had to disable auto update otherwise it was updating automatically via OTA to A10. Because of that I re-flashed almost 3-4 times.
To disable auto update I had to stop all networks otherwise it downloads OTA and does not show settings menu. Sometimes it went into boot loop, but setting the correct bootable partition using your tool helped. Finally I am on A9 v1.10 and managed to disable auto update and everything is working fine. GPS is locking in 3-5 secs and no issues with notifications getting stuck when on Wifi. I have kept a backup_all after things are setup, in case required in future.
Your tool is amazing, thank you for sharing and providing detailed steps.
@ccraze I just ran into the same issue with the sensors myself. The last time I re-flashed, I only flashed partition B, because - from earlier experiences = I learned that partition B is the one that matters. So I skipped writing to partition A.
Just to be clear, what you did was this:
1. Run Load Programmer.ps1 - phone should now be connected
2. Ran Write Firmware v1.1.0 to A.ps1 <-- THIS
3. Ran Write Firmware v1.1.0 to B.ps1
4. Ran Set Bootable Partition0 Slot B.ps1
Is that right?
karlovac said:
@ccraze I just ran into the same issue with the sensors myself. The last time I re-flashed, I only flashed partition B, because - from earlier experiences = I learned that partition B is the one that matters. So I skipped writing to partition A.
Just to be clear, what you did was this:
1. Run Load Programmer.ps1 - phone should now be connected
2. Ran Write Firmware v1.1.0 to A.ps1 <-- THIS
3. Ran Write Firmware v1.1.0 to B.ps1
4. Ran Set Bootable Partition0 Slot B.ps1
Is that right?
Click to expand...
Click to collapse
@karlovac The sequence you mentioned is correct. But later I noticed that there is no set sequence which can cause this issue and no specific sequence which can fix it. After my previous post, I tried installing OTA and sensors worked. Then I reflashed it and it worked again. Later by mistake I took the OTA again and saw GPS issues. So reflashed, and then ran into sensor issue again. Again reflashing worked and AFAIK it was not in the sequence mentioned above in your post.
I would say just a matter of luck, I couldn't find exact sequence which can cause this issue. Just try flashing again, most probably you will not see sensor issues. If you still see sensor issues then try installing all OTA till your system is back to A10, meanwhile checking if the sensors are back after every OTA. If you see sensors working, then no need to install all OTAs and reflash with this image to go back to A9 and disable auto updates. Good Luck!
Thanks @ccraze . I already did *one* OTA system update to see if that fixed it but it didn't. My build number is now GEN_NA_A2020U_PROV.1.11
The way I'm testing the sensors is:
1. Open dialer
2. Enter *983*673636# -> this enables EMODE
3. Enter *983*0# -> this opens the testing app
4. Go to sensor test
They all say CTS Fail. (I got that from this thread BTW).
Do you happen to know how many OTA updates there were before you get to the "bad" A10 one? I know the bad build is GEN_NA_A2020U_PROV2.09.
@ccraze success! I did the following:
1. Wiped the cache partition. See this video. It did *NOT* fix the sensors. But apparently it's a good thing to do.
2. Did an OTA update to the next A9 build . My build number is now GEN_NA_A2020U_PROV1.13
After that, my sensors worked again. Thanks for the tips.
karlovac said:
Thanks @ccraze . I already did *one* OTA system update to see if that fixed it but it didn't. My build number is now GEN_NA_A2020U_PROV.1.11
The way I'm testing the sensors is:
1. Open dialer
2. Enter *983*673636# -> this enables EMODE
3. Enter *983*0# -> this opens the testing app
4. Go to sensor test
They all say CTS Fail. (I got that from this thread BTW).
Do you happen to know how many OTA updates there were before you get to the "bad" A10 one? I know the bad build is GEN_NA_A2020U_PROV2.09.
Click to expand...
Click to collapse
Even that is not consistent. Once, I have seen it worked fine till I got all A9 updates. But in one run GPS went bad in first OTA itself. Definitely A10 is bad, but there something else wrong with the A9 OTAs also which mess up the drivers. I would recommend to not take any OTA after flashing with this image.
karlovac said:
@ccraze success! I did the following:
1. Wiped the cache partition. See this video. It did *NOT* fix the sensors. But apparently it's a good thing to do.
2. Did an OTA update to the next A9 build . My build number is now GEN_NA_A2020U_PROV1.13
After that, my sensors worked again. Thanks for the tips.
Click to expand...
Click to collapse
Great! just make sure that OTA is not messing up GPS again. otherwise you might need to reflash and disable auto updates immediately after booting.
@ccraze how did you disable OTA updates exactly? My phone was fine for the last few days, but then it installed the A10 update last night again! I haven't restarted it yet, but it's definitely the A10 one.
I really don't know what else to do. I disabled "automatic system updates" in developer options, *and* I removed the permissions from the system update app.
Is there a different place you disabled OTA updates?
karlovac said:
@ccraze how did you disable OTA updates exactly? My phone was fine for the last few days, but then it installed the A10 update last night again! I haven't restarted it yet, but it's definitely the A10 one.
I really don't know what else to do. I disabled "automatic system updates" in developer options, *and* I removed the permissions from the system update app.
Is there a different place you disabled OTA updates?
Click to expand...
Click to collapse
After you flash the OS, immediately turn off all data (Mobile + Wifi). Then go to Settings->System->System Update->Click 3dots on the top right -> Settings -> Disable all options.
Its easy to see those options if you have all data sources turned off. It will download and will show that update is ready to install but will not install automatically.
I think I did what you're describing, right after I flashed:
However, the update still downloaded, and it sounds like if I reboot the phone, it will automatically install:
I'm afraid to reboot now since I can't afford to lose GPS reliability now.
karlovac said:
I think I did what you're describing, right after I flashed:
View attachment 5338875
However, the update still downloaded, and it sounds like if I reboot the phone, it will automatically install:
View attachment 5338877
I'm afraid to reboot now since I can't afford to lose GPS reliability now.
Click to expand...
Click to collapse
You are not following the menu items that I mentioned before. You should see following screens. Developer options system update is different setting.
Oh man, that's confusing that there are *two different* places to disable auto updates. Very frustrating!
Unfortunately now that the update is downloaded, I can't go into the System Update settings any more. The System Update app is in a state where I can't get to the ... menu. I haven't restarted my phone for 2+ weeks, since I've been traveling, and I couldn't afford for GPS to break.
Do you know if there's a way I can delete the downloaded update, so it doesn't install, using the tools?
karlovac said:
Oh man, that's confusing that there are *two different* places to disable auto updates. Very frustrating!
Unfortunately now that the update is downloaded, I can't go into the System Update settings any more. The System Update app is in a state where I can't get to the ... menu. I haven't restarted my phone for 2+ weeks, since I've been traveling, and I couldn't afford for GPS to break.
Do you know if there's a way I can delete the downloaded update, so it doesn't install, using the tools?
Click to expand...
Click to collapse
Your phone seems to have A/B partition.
So the update is written into the inactive slot.
Check which slot it's using and which slot is inactive.
Then purposely corrupt the inactive slot which contains the update. Make backup of what you change though in case you targeted the wrong stuff.
So the update will fail and the update in the inactive slot will not boot.
Then it will return back to the previous active slot with the old system.
Risk it yourself though. I never had an A/B slot, so can't make sure if it works.
pl1992aw said:
Check which slot it's using and which slot is inactive.
Then purposely corrupt the inactive slot which contains the update. Make backup of what you change though in case you targeted the wrong stuff.
Click to expand...
Click to collapse
Thanks for the feedback! When you say "purposely corrupt the inactive slot", I take it you mean that I should manually corrupt a ROM and then flash it to the inactive partition, right? I've been using the tools here to flash, so there are two scripts - one to write to partition A and one to write to partition B. Do you have any specific suggestions on what I should do to corrupt it - specific file(s) I should delete perhaps, that would guarantee it fails?
Also, to check which slot is inactive, according to this doc, it seems I should run:
fastboot getvar all | grep “current-slot”
Do I have to put my phone in EDL mode to do that, or can I run fastboot without EDL mode. I'm worried that if I put my phone in EDL mode, when I exit out of it, it will reboot. So I'll be past the point of no return.
karlovac said:
Thanks for the feedback! When you say "purposely corrupt the inactive slot", I take it you mean that I should manually corrupt a ROM and then flash it to the inactive partition, right? I've been using the tools here to flash, so there are two scripts - one to write to partition A and one to write to partition B. Do you have any specific suggestions on what I should do to corrupt it - specific file(s) I should delete perhaps, that would guarantee it fails?
Also, to check which slot is inactive, according to this doc, it seems I should run:
fastboot getvar all | grep “current-slot”
Do I have to put my phone in EDL mode to do that, or can I run fastboot without EDL mode. I'm worried that if I put my phone in EDL mode, when I exit out of it, it will reboot. So I'll be past the point of no return.
Click to expand...
Click to collapse
I never had ZTE phones, so can't really be sure about the flashing process.
You don't need to corrupt the whole ROM, you can rather just corrupt the boot partition of the inactive slot with update. Or even just flash a wrong version of boot partition into that inactive slot can corrupt it as well.
Either
Code:
fastboot flash boot_a wrong_boot_file.img
Or
Code:
fastboot flash boot_b wrong_boot_file.img
The corrupt can be done with root or in fastboot, EDL should be not needed.
About which slot is inactive, since your case is complicated that it's going to do an update, the fastboot command to check inactive slot is hard to distinguish.
You may need to use rather command
Code:
fastboot getvar all
It will show like this:
With this, you will be able to see the system version.
eg. ro.build.version (find the correct one yourself, I don't know this phone.)
Before power off, you first find out your current version, so then in fastboot, you check if it's the same as read from fastboot.
Related
I cannot change the date and time on my phone, in the setting nor shell commands.
Date and TIme selections are selectable, but will not change on apply.
On TWRP 2.7.10 Recovery shows a correct date and time.
But was it rebooted to operation system, it show my date and time back in December 31, 1969.
I have tried restore back to stock 4.4 rom and recovery. Still no luck on changing it.
And I cannot downgraded with HouseOfMoto to 4.1.x. Will get a boot loop.
Any help!?
Thank You
Also, When I check all the system files ./. They are dated back in 1969-1970
Any Idea? Its the phone or software?
saranay said:
I cannot change the date and time on my phone, in the setting nor shell commands.
Date and TIme selections are selectable, but will not change on apply.
On TWRP 2.7.10 Recovery shows a correct date and time.
But was it rebooted to operation system, it show my date and time back in December 31, 1969.
I have tried restore back to stock 4.4 rom and recovery. Still no luck on changing it.
And I cannot downgraded with HouseOfMoto to 4.1.x. Will get a boot loop.
Any help!?
Thank You
Click to expand...
Click to collapse
what did you use to restore back to stock?
bweN diorD said:
what did you use to restore back to stock?
Click to expand...
Click to collapse
I used both RSD and DROID_RAZR_HD_Utility_1.41 KK to restore back to 4.4
saranay said:
I used both RSD and DROID_RAZR_HD_Utility_1.41 KK to restore back to 4.4
Click to expand...
Click to collapse
sorry, im not able to help you.
i just wanted to be sure you weren't using a backup to restore.
you mentioned flashing back to JB and having issues. i posted a [guide] in the general forum. there is an edited JB file in there near the bottom that will flash with rsd if you want to try that.
i dont expect it to fix your issue though.
Yes I have tried that and get a bootloop. cleared cache, reset everything. Couldn't get pass bootloop.
Now am back on CM11 4.4
Try to set RTC, "hwclock or date" commands
It shows RTC_SET_TIME: Invalid argument
Because of the date and time is offset. Now I cannot login or access on any google services on my phone.
Problem solved*
I use Windows 7, and USB driver is not update or installed correctly. I can't get a connection to USB 2.0+ on any ports.
Switched to my family computer and reflash. Got the phone boots up normal and Date & Time is corrected.
I want to update this post for anyone who might have the same issue.
If you have updated your phone to 4.4 KK and is showing incorrected date and time for more than 24 hours.
Then try to flash back to 4.1 JB stock. To see you can boot up your phone and change your date and time back to normal.
But if you get a bootloop and restart.
Then you might having a hardware/sensor failure somewhere on your phone.
Usually is an approximate sensor, or light sensor on the front housing of the phone.
This will cause a chain reaction to your phone.
Are you sure about this? Because my phone (xt925) has the proximity sensor broken and don't have date/time issues
DorianX said:
Are you sure about this? Because my phone (xt925) has the proximity sensor broken and don't have date/time issues
Click to expand...
Click to collapse
I have a front housing with 2 broken sensor; proximity and light sensitivity. Tested on 3 phones of my family
Are you on KK or JB?
Try to flash back to JB and then KK on sbf stock.
Edit: I figured out the problem. I was reading other posts on the web and one person said they had similar issue when they replaced the screen. So there is only two ribbons that attach to main board, I took it apart again and reset the cables. Powered on and date was set correctly. Big sigh of relief as I thought i would have to send the board back. :good:
its strange, I get this problem after doing a mainboard swap. It did a bootloop when I first started it, thought it may of been a corrupt system so just did the kitkat update, was able to root and unlock the bootloader on the new board and that is when I noticed the date. flashed back to JB with house of moto universal script and I get the same bootloop. My phone worked fine with the old mainboard. I just changed it because the sim card reader would go out. Either I got a bad board or something. I'll continue to investigate but any input would be appreciated.
yujikaido79 said:
its strange, I get this problem after doing a mainboard swap. It did a bootloop when I first started it, thought it may of been a corrupt system so just did the kitkat update, was able to root and unlock the bootloader on the new board and that is when I noticed the date. flashed back to JB with house of moto universal script and I get the same bootloop. My phone worked fine with the old mainboard. I just changed it because the sim card reader would go out. Either I got a bad board or something. I'll continue to investigate but any input would be appreciated.
Click to expand...
Click to collapse
Go download this app "Test Your Android", to test the hardware on your phone.
please how do we correct thid issue of time and date moving far behind to 1970's ?
thanks
thank you so much I had tried every solution on here for other devices also and then when I saw your post I took off the screen and replaced the front camera/earpiece/sensor assembly, put the screen back on and the clock resetted right away with the correct time and date..it seems the one I was using was damaged ..so it was the sensor ..I hope this helps others with this problem
I am helping a friend to get his One Plus One 64GB to work again after an OTA update broke it.
Initial Problem
Two days ago she started an OTA update which made the phone reboot constantly before even android started. Basically it showed the logo for about 6s then vibrated and restarted again. I later found /o/Android/data/com.cyngn.fota/cache/cm-12.0-YNG1TAS17L-bacon-signed.zip so I assume that this was what was installed.
The phone is completely untouched otherwise. She has no computer knowledge whatsoever and says she didn't give it to anyone.
My attempt
I was able to install cm-11.0-XNPH33R-bacon-signed.zip and cm-11.0-XNPH22R-bacon-signed.zip via sideloading. The phone started ok but was crashing all the time. I am not able to get into settings to activate developer settings (adb) because the crash notifications hinder navigation and after about 10s the whole gui crashes and I see the black screen with the hexagon loading logo. The latter firmware is worse meaning it crashes at a higher frequency.
The Problem
She didn't expect any problems and does not have a backup of her data. Thus I can't do a factory reset or use fastboot.
Question
Did I use the wrong ROM? There seem to be many variants. I haven't found any information which explains the differences.
Could I maybe flash a minimal ROM that would not crash to backup the data and than do a factory reset?
Is there any way to activate adb access without having to navigate to settings?
I've experienced your issues as well when helping another friend out, try using a newer version of cm11s, something like 44S /44R (i dont remember what it is) or 05Q, those should not have the issue and everything should work fine
Jst flash a newer modem in recovery
mugoftee said:
I am helping a friend to get his One Plus One 64GB to work again after an OTA update broke it.
Initial Problem
Two days ago she started an OTA update which made the phone reboot constantly before even android started. Basically it showed the logo for about 6s then vibrated and restarted again. I later found /o/Android/data/com.cyngn.fota/cache/cm-12.0-YNG1TAS17L-bacon-signed.zip so I assume that this was what was installed.
The phone is completely untouched otherwise. She has no computer knowledge whatsoever and says she didn't give it to anyone.
My attempt
I was able to install cm-11.0-XNPH33R-bacon-signed.zip and cm-11.0-XNPH22R-bacon-signed.zip via sideloading. The phone started ok but was crashing all the time. I am not able to get into settings to activate developer settings (adb) because the crash notifications hinder navigation and after about 10s the whole gui crashes and I see the black screen with the hexagon loading logo. The latter firmware is worse meaning it crashes at a higher frequency.
The Problem
She didn't expect any problems and does not have a backup of her data. Thus I can't do a factory reset or use fastboot.
Question
Did I use the wrong ROM? There seem to be many variants. I haven't found any information which explains the differences.
Could I maybe flash a minimal ROM that would not crash to backup the data and than do a factory reset?
Is there any way to activate adb access without having to navigate to settings?
Click to expand...
Click to collapse
The problem here is that you flashed an older build, going backwards like that is what's causing the crashes. Grab the latest build from here:
https://www.androidfilehost.com/?fid=24052804347802356
Flash that and hopefully you'll be ok.
PivotMasterNM said:
I've experienced your issues as well when helping another friend out, try using a newer version of cm11s, something like 44S /44R (i dont remember what it is) or 05Q, those should not have the issue and everything should work fine
Click to expand...
Click to collapse
That won't help, flashing an older build than what was previously installed without wiping properly will cause problems.
KURDKiNG said:
Jst flash a newer modem in recovery
Click to expand...
Click to collapse
Modem has nothing to do with this.
Well mines did like it was at lockscreen and wen i tried to unlock it rebooted so i jst flash a modem and booted fine
KURDKiNG said:
Well mines did like it was at lockscreen and wen i tried to unlock it rebooted so i jst flash a modem and booted fine
Click to expand...
Click to collapse
Most likely pure coincidence.
Thanks your reply!
Heisenberg said:
The problem here is that you flashed an older build, going backwards like that is what's causing the crashes. Grab the latest build from here:
https://www.androidfilehost.com/?fid=24052804347802356
Flash that and hopefully you'll be ok.
Click to expand...
Click to collapse
Actually this is what I did in the very first beginning but I encountered the same rebooting symptoms like after the OTA update. Since it didn't seem to change anything I didn't mention it. I used cm-12.1-YOG4PAS1N0-bacon-signed.
Any other ideas? I am about to unlock it with fastboot but really would prefer not to delete all user data.
mugoftee said:
Any other ideas? I am about to unlock it with fastboot but really would prefer not to delete all user data.
Click to expand...
Click to collapse
I don't think you have any other option unfortunately.
1. I can only get into phone manager or permission manager when phone is in airplane mode? Strange lol Otherwise it will open for .5 second and close. No toast notification though
2. My memory usage. Normal? Screenshot should be added.
Sorry. 6x rooted L24 model ? using a p9 lite theme
tre717 said:
1. I can only get into phone manager or permission manager when phone is in airplane mode? Strange lol Otherwise it will open for .5 second and close. No toast notification though
2. My memory usage. Normal? Screenshot should be added.
Click to expand...
Click to collapse
Try clearing the app data for phone manager and see.
tre717 said:
1. I can only get into phone manager or permission manager when phone is in airplane mode? Strange lol Otherwise it will open for .5 second and close. No toast notification though
2. My memory usage. Normal? Screenshot should be added.
Click to expand...
Click to collapse
Yes. Memory usage is fine. See mine
shashank1320 said:
Try clearing the app data for phone manager and see.
Click to expand...
Click to collapse
Yes this works, too. But what would make it mess up again? Seems like something is corrupt or something
tre717 said:
Yes this works, too. But what would make it mess up again? Seems like something is corrupt or something
Click to expand...
Click to collapse
These things happen sometimes...so dont worry buddy
Update: On my Phone Manager force closing by its self. Airplane Mode- Works perfectly. Data on Wifi on- force closes.. Data on Wifi-OFF-- works perfectly. Weird? With wifi on it will not work. Also, my wifi is called WLAN?
tre717 said:
Update: On my Phone Manager force closing by its self. Airplane Mode- Works perfectly. Data on Wifi on- force closes.. Data on Wifi-OFF-- works perfectly. Weird? With wifi on it will not work. Also, my wifi is called WLAN?
Click to expand...
Click to collapse
Do you have a phone which is a China varaiant? Because I konw only in China, Wifi is called WLAN due to local regulations...
Since you're rooted I assume you have either a custom ROM, or at the very least, a custom recovery. My personal preference is TWRP.
1. In <insert your custom recovery name here, such as TWRP>, do a full NAND / System backup. (This is a long process but bear with me)
2. Look here on the forums for a "stock" rom in flashable .zip form (NOTE: You will want it to be in .zip as opposed to some sanctioned Huawei/Honor package as that will remove your root). When found , download it and stick it on your MicroSD card somewhere
3. Flash the "stock" rom.
4. Wipe Cache / Davlik / system partitions (Usually this is recommended, but in this case I'd argue it's required)
5. Boot into your stock software
6. Now see if the same exact issue persists. If it does, then you know at least its not hardware or software related and its something in the Honor ROMs. If the issue is gone, then it's "something" in your setup. Once you've at least identified this, you now know what to do next.
7. Boot back into <insert your custom recovery name here, such as TWRP>, and restore the backup you snapped in step 1 (This will bring you back nicely to where you were)
Purpose of this exercise: To determine if your issue exists stock-software in a "factory reset" condition, or if it's something funky with how you setup our phone / software / apps / etc.
I know this is long-winded, but it should clarify a few things for you.
"I'm just here so I won't get fined.....errr so I can 'participate' in the Honor 6x sweepstakes"
jerryhou85 said:
Do you have a phone which is a China varaiant? Because I konw only in China, Wifi is called WLAN due to local regulations...
Click to expand...
Click to collapse
Here is the thing.
Phone, boot looped first time unlocking it. So I downloaded a update zip and extracted the update.app and flashed the stock.img
Then I did the same with the firmware for my model L24 (because it wasn't out there at first)
So it seems something didn't get "wiped" when I flashed the image from the L24?
tre717 said:
Here is the thing.
Phone, boot looped first time unlocking it. So I downloaded a update zip and extracted the update.app and flashed the stock.img
Then I did the same with the firmware for my model L24 (because it wasn't out there at first)
So it seems something didn't get "wiped" when I flashed the image from the L24?
Click to expand...
Click to collapse
...That's too complex...maybe you should try to get your phone to flash all the files from a same ROM
So I went back and downloaded the L24C900B110 from the honor.ru site. And still it shows WLAN?
Another thing I noticed. Using Zooper widget, the location is India?? Maybe that firmware isn't for the bln-l24? But I thought that was the US version, not the India version.
My oneplus 6 A6000 is always crashing when something new is opened. Random apps make the phone freeze and it randomly reboots from boot animation and in splash screen. I cant update my software via local it always fails. I cant update my software via OTA it is says signature failure at 95%
my phone was recently bricked with a RED warning "your phone is corrupted...." I fixed the warning with MSM downloader tool. I am out of options.
I tried to flash a custom ROM but I Am stuck in step 1 that to flash OOS it says error 28
Updated via MSM tool Tried to go to 10.3.0 it crashes from Welcome Logo
via MSM tool Tried to go to 9.0.8 it crashes too
I also notice some lines in the screen. I had a chance to take a screenshot of it and it shows in the screenshot. it means its not an LCD problem.
please help me developers
Ok, so feels like you have some unofficial oos or firmware installed...can you tell me more about your situation?
What OOS you are using?
Are your bootloader unlocked?
Do you have root?
What firmware installed with MSM tool?
When in MSM tool you wiped everything or only data?
What twrp you are using?...
Please provide some info...and if you can, upload that screenshots so we can see that lines....maybe you phones battery is dead or maybe something with hardware i guess...
It all started when I updated to 9.0.9 pie it is stable version. I flashed oxygen os 5.1.5 via msm tool to remove the red warning. The only twrp I tried is for Android Q ( I updated my system to 10.3.0 via MSM tool). Yes I tried to unlock bootloader and try to flash a ROM I got stuck in a step where I need to flash an OOS the version is right. I dont know what causes the error. Pls ignore the 2nd error in screenshot I accidentally pressed that. Thank you I will get back to you for the screen DIAGONAL lines it is small I also notice if something new appear to the screen the phone freezes and restart.
Ok, what twrp version you are using?...and pls...try to format data withing twrp and then enable mtp and flash latest oxygen again...but your zip is not the latest one...it should be Oneplus6oxygen os 042...but format everything when it says type yes...try this and talk back...
And feels like it is hardware problem...
Here is the screenshot of lines appearing randomly.
I tried that nothing happend. Still that warning yes it is 042 and i am using EvolutionX rom it reboots but Not too much
Twrp is 3.3.1-17 Q
Did you try to format your phone?
PecanTastic said:
My oneplus 6 A6000 is always crashing when something new is opened. Random apps make the phone freeze and it randomly reboots from boot animation and in splash screen. I cant update my software via local it always fails. I cant update my software via OTA it is says signature failure at 95%
my phone was recently bricked with a RED warning "your phone is corrupted...." I fixed the warning with MSM downloader tool. I am out of options.
I tried to flash a custom ROM but I Am stuck in step 1 that to flash OOS it says error 28
Updated via MSM tool Tried to go to 10.3.0 it crashes from Welcome Logo
via MSM tool Tried to go to 9.0.8 it crashes too
I also notice some lines in the screen. I had a chance to take a screenshot of it and it shows in the screenshot. it means its not an LCD problem.
please help me developers
Click to expand...
Click to collapse
Sometimes issues like that occur when I change some things in mine and don´t wipe the data [Mine is an A6003]
Yes I did try to format data. I tried to install TWRP in. 8.1 oreo OOS 5.1.11 Blu spark twrp 3.2.3-x. "fastboot boot twrp.img" and it completes but stuck in oneplus logo fast boot mode.
I had only access to twrp in Q 10.3.0 twrp version 3.3.1-17-Q ( this is the only Custom recovery worked )
I tried pie 9.0.8 flash twrp "fastboot boot twrp.img" it is also stuck in oneplus logo fastboot mode
Maybe this will help? The package box of my phone
Problem started after Pie OTA update. Black screen and random reboots
it was sold with OxygenOS installed
Bump
Read and write speed
My read and write speed is 749mbps(read)
0mbps(write) any way to fix this? Maybe this is the problem
If those problems are purely software-related, and I think there's a good chance they are, I'd say one of the more critical partitions on your phone got corrupted at some point, somehow. Using MSMDownloadTool to fix this is a bit of an overkill imo, and the method below has always worked for me when I messed something up while switching between OOS and custom ROMs so I reckon it's pretty good. Also, full-proof. Essentially just do as follows:
0. Make a backup. Always!
1. Download the newest OOS version from this thread (direct link to 10.3.1)
2. Unpack the zip to whichever location on your PC suits you best.
3. One of the files inside will be an archive (also .zip if I recall correctly) with all the partition images. Unpack all its contents to the main directory where the rest of the files are.
4. There will also be a folder with different .bat files corresponding to what partitions you'd like to flash (as per the flasher advanced guide section in the thread from point 1) - grab the one named flash-all-partitions.bat and copy it to the main folder as well.
5. Boot the phone into fastboot mode and connect it to PC, and finally
6. Launch the script from point 4, agree to the data wipe, and wait. Flashing the whole thing will take a while, but hopefully it'll solve your problems
Hello, I followed all the steps still no luck. Random apps cause the phone to crash systemUi. Which leads to boot from bootanimation Anyone please help me too sad oneplus has no emergency download tool
PecanTastic said:
Hello, I followed all the steps still no luck. Random apps cause the phone to crash systemUi. Which leads to boot from bootanimation Anyone please help me too sad oneplus has no emergency download tool
Click to expand...
Click to collapse
MSMDownloadTool is the emergency download tool. Anyway, what you did is you literally just reflashed all of your phone's partitions, on both slots, so either the issue is hardware, or...I don't know. What happens when you boot your phone in safe mode (hold the reboot, err, icon that appears after holding the power button for a few seconds, until a popup with info about safe mode appears)? Do apps still crash?
Oh, one more thing (blind guess really, but yeah) - are you, by any chance, a beta tester for the Android System WebView app or Google Play Services? If you are, switch back to stable channel via Play Store and update the respective apps. Tell me, if that changed anything. (Also, if you could check the WebView implementation version in the settings, that would be great (just use search)).
Edit: out of curiosity, what happens when you try to update the phone via the local update function (to 10.3.1, just download the full OTA zip this time instead of the fastboot-compatible one)? Does it work without issues or not really?
One thing I noticed is writing speed is instant e.g. sending
OKAY [19.294]
Write[0.000]
Sometimes it is [-0.000]
i need a tool to reset internal partition or anything main slot for boot is "b"
It does not update via local.
I will try that playstore thing but I doubt it
McAwesomePL said:
MSMDownloadTool is the emergency download tool. Anyway, what you did is you literally just reflashed all of your phone's partitions, on both slots, so either the issue is hardware, or...I don't know. What happens when you boot your phone in safe mode (hold the reboot, err, icon that appears after holding the power button for a few seconds, until a popup with info about safe mode appears)? Do apps still crash?
Oh, one more thing (blind guess really, but yeah) - are you, by any chance, a beta tester for the Android System WebView app or Google Play Services? If you are, switch back to stable channel via Play Store and update the respective apps. Tell me, if that changed anything. (Also, if you could check the WebView implementation version in the settings, that would be great (just use search)).
Edit: out of curiosity, what happens when you try to update the phone via the local update function (to 10.3.1, just download the full OTA zip this time instead of the fastboot-compatible one)? Does it work without issues or not really?
Click to expand...
Click to collapse
Apps don't crash when Im in safe mode but i can only access system apps. Thank you for helping dude.
Maybe this will explain something?
PecanTastic said:
One thing I noticed is writing speed is instant e.g. sending
OKAY [19.294]
Write[0.000]
Sometimes it is [-0.000]
i need a tool to reset internal partition or anything main slot for boot is "b"
It does not update via local.
I will try that playstore thing but I doubt it
Click to expand...
Click to collapse
Some partitions are fairly small, so they should be transferred to the device pretty much instantly, although I'm not sure if the time should show null ([-0.000]).
If OTA still doesn't work however, then the problem seems to be somewhere else entirely, so the Playstore thing probably won't help, yes.
PecanTastic said:
Apps don't crash when Im in safe mode but i can only access system apps. Thank you for helping dude.
Click to expand...
Click to collapse
Heeeey, we're getting somewhere!
-------------------------------------------
Edit: wait, are the user apps the only ones crashing (when not in safe mode)? Or are system apps crashing too?
-------------------------------------------
The safe mode is designed in such a way that no services other than system ones can run while using it - it's mostly for troubleshooting, same as e.g. in Windows. Not sure where that leads us, but there is a chance one of your apps/widgets/whatever might be causing this issue in that case, although I'm not sure how an app would impact the OTA functionality. Regardless, what you can check is whether you're able to perform a local update while in safe mode. You can also download the OTA zip again just to be sure it's not corrupted and that if the installation fails, it's not the update package's fault (and remember to use the full 1.something GB zip, not just the delta package!).
One other thing to try if the above fails is to reflash the critical partitions using the fastboot-compatible update zip and an appropriate script from within it. No idea if that's going to help, especially considering the fact those partitions should have been reflashed along with the rest using the script I mentioned a few posts earlier, but I reckon it's worth a try if everything else fails - troubleshooting is a trial-and-error process, all in all.
...also, np - hope you manage to fix your phone's issues eventually!
---------- Post added at 02:26 PM ---------- Previous post was at 01:59 PM ----------
PecanTastic said:
Maybe this will explain something?
Click to expand...
Click to collapse
Not really, no, unfortunately - if I understand the information from the photo correctly, the only reasons for your device powering off were holding the power button [1] and using the keypad [3] (tapping the power off icon from the power menu?), which is, well, a normal way to turn a device off.
Pls just use MSMDownload tool insted....i can give you a link if you want but you can just google it
James Blode said:
Pls just use MSMDownload tool insted....i can give you a link if you want but you can just google it
Click to expand...
Click to collapse
He used it actually, as mentioned in the OP, but to no avail.
So I updated to 11.0.08.14.KB05BA.
I then rooted using the guide here, via Magisk
Rooted, everything works, except:
My wifi connection will not turn on (let alone connect).
I hit the wifi icon, it "turns on" and then "turns off"
I go to the wifi settings and hit the bar to turn it on. it stays red, but no wifi connections are made.
I tried to reset the wifi, mobile, data setting under systems, nothing changed
I tried to reflash the patched boot file without any change.
so my question is, can I fix it by:
A. flashing the stock modem.img? and if so what is the correct adb text (fastboot flash modem modem.img?)
tried it, no change, so I guess I have my answer
B. reflashing stock everything and starting a new root with Magisk and hope it works a second time (i.e. start over)
Yup. Problem that the stock version on the OP website is not the same file as Oxygen Updater "Stock version". No clue. Got the boot from the Oxygen updater version and will try it with it now.
Fixed: all good now. I will delete this this post in a moment.
Thanks @parakleet
With my thanks,
Etterbeek
I am guessing you flashed something that was modified or possibly images for a different model.
I think the only solution sure to resolve your issue is to return to the stock image of your device.
anyone know how to delete a thread?
Etterbeek said:
anyone know how to delete a thread?
Click to expand...
Click to collapse
Don't delete it. You're journey will help others avoid the problem or help them get out of it if they do the same thing you did.
BillGoss said:
Don't delete it. You're journey will help others avoid the problem or help them get out of it if they do the same thing you did.
Click to expand...
Click to collapse
as he gave me a thumbs up I assume he MSM'd his way back to stock images
But I agree knowledge gained would be helpful
Etterbeek said:
So I updated to 11.0.08.14.KB05BA.
I then rooted using the guide here, via Magisk
Rooted, everything works, except:
My wifi connection will not turn on (let alone connect).
I hit the wifi icon, it "turns on" and then "turns off"
I go to the wifi settings and hit the bar to turn it on. it stays red, but no wifi connections are made.
I tried to reset the wifi, mobile, data setting under systems, nothing changed
I tried to reflash the patched boot file without any change.
so my question is, can I fix it by:
A. flashing the stock modem.img? and if so what is the correct adb text (fastboot flash modem modem.img?)
tried it, no change, so I guess I have my answer
B. reflashing stock everything and starting a new root with Magisk and hope it works a second time (i.e. start over)
Yup. Problem that the stock version on the OP website is not the same file as Oxygen Updater "Stock version". No clue. Got the boot from the Oxygen updater version and will try it with it now.
Fixed: all good now. I will delete this this post in a moment.
Thanks @parakleet
With my thanks,
Etterbeek
Click to expand...
Click to collapse
Im having the same issue but idk how to fix it