I have an SCH-i800 that I have CM9 (p1c 9.1.0) installed on. I have been using it for several weeks with no problem. Since I am planning on going on a trip, I decided to active pre-paid Verizon service for the tablet. At first, I attempted to activate the device. It went through the phone call but after a minute, it just sat at activating. That is when I noticed that the radio state in the status bar had an X on it. I rebooted the tablet to try again and got "com.android.phone has topped unexpectedly". I re-flashed CM9 (at the time I was using 9.0.0) and it worked again. Activation was not necessary. After a day, the error came up again and radio state went to off with an X. I tried 9.1.0, same problem after a day. I even tried a nightly CM10, same problem. Reboots, cache wipes, permission fixes do not make it work. The error persists until a re-flash of CM. I see on the Support Downloads for the Verizon Tablet, there are two modem files. My baseband version is currently S:I800.0.3V.EI04. I have attempted to "flash" these both via Odin (which failed after a couple minutes) and ZIP (which looked like it worked) to the EC02 on the site, but my baseband doesn't seem to change.
So my first question is, is there a how-to on flashing as I have searched high and low on one for the Verizon Tab specifically, and have yet to find one. Is there a ZIP file that is specifically meant for the i800? I am almost certain this is my problem and that a downgrade (this tablet when stock was updated to the latest Verizon image).
My second question is, has anyone else experienced this? Is there someone that is using a CM9 Verizon tab with EI04 baseband and not have this problem?
Is there a way I can track down what crashed the program? I have tried logcat, but it doesn't appear to give me much detail other than to tell me that it stopped.
And if you ask, no I did not use the Verizon service with this tablet before putting CM9 on it, so I wouldn't know if it worked before.
Any input that someone could provide would be useful. Thanks!
So I finally took the plunge today and rooted. I flashed the most recent Sprint version of ViperROM, and everything was going just fine and dandy, I was all giddy setting up my MoDaCo UI mods, etc, until I tried to send a text. Tried to send for 5 minutes, got the fail message. Well, that's weird. What about 3G data? Nope, nothing. Maybe the ROM is bad? I flashed the stock ROM by viperboy, also didn't work. Same problems. So now I'm stuck with no cellular connection and I need it soon. How do I fix it? (Note that I followed my tutorials step by step and everything works except cellular connection. Also note that it says I have service and that data is going in/out, but it's not actually sending/receiving anything. It seems that I need something called an RUU, but I have no idea what that is or where to get a correct one and how to flash it.
Please give me a step by step (I'm using TWRP if that matters), as this is my first time rooting or doing anything more advanced with my phone past advanced themes in Nova Launcher. I'll need links if you have them, or at least where to look. Please help me, because don't want to go back to stock after getting all my awesome tweaks already!
And yes, I have updated my PLR and Profile in the system updates menu, same results.
EDIT: I fixed it, yay! I tried clicking UICC unlock in the software update menu. It said no profile update available, and then it started working (it's actually faster than normal! ) It may have been the profile update that did it and it took a second to update, but it works now! Yay! I even rebooted to make sure it was going to stay after a shutdown, etc, and it did! I guess I should check all option before posting a thread next time... (If you can't tell I'm extremely happy it works!)
EDIT 2: It stopped working again :'(. Now I'm constantly losing the 3G connection that I "had" and messages and data only work about 10% of the time they say they're connected. Wifi still works. When I try updating the profile, it says it could not be updated and to try again later (this is after several tries and a reboot). I try to update the PLR and I get error code 1233. Apprently this is an HTC specific error with no know fix? I try to do the UICC unlock, and it gives me the same error as the profile message.
EDIT 3: It seems Sprint is having issues in my area, I will update again if they resolve it or reply to my tweet.
EDIT 4: They told me to go restart the booster thingy I have in my house, and now my connection is working for now...
My new P20 Pro (Canadian Telus) is having issues updating to CLT-L04 8.1.0.109(C792) from CLT-L04 8.1.0.107(C792).
The Problem is that the device simply will not update no matter the method.
My device is unrooted at this point.
What Happens.
When going through each of the scenarios,
1) The firmware is downloaded,
2) The phone then boots into firmware installation mode,
3) Firmware supposedly is updated
4) Phone Boots
5) Upon checking in phone status the phone is still on CLT-L04 8.1.0.107(C792)
Methods I have Used to Update
A) OTA Update (result: not updated)
B) Factory reset the device and then trying to OTA Update. (result: not updated)
C) Update via HiSuite (result: not updated)
At this point, I am unsure why this is happening and how I can update to the new firmware.
Any advice or guidance is greatly appreciated!
Did you factory reset? After the last attempt? Is your bootloader unlocked? Have you tried eRevovery?
I have the same issue: new P20 Pro from Koodo (single SIM version), out of the box it prompted me to update, after I did this, I had for example a corrupted Settings app (name was a mix of letters and numbers and same name corruption with Chinese characters within). After this happened I did a factory reset, was back on 107 and was prompted to update again in the morning, which I did. Same outcome as above, after apparently successful installation and restart, I was still on 107 ...
Just got off a chat with Huawei Canada and apparently technicians are aware of the issue and are working on a hot fix that should resolve the update issue.
ccwestcliff said:
I have the same issue: new P20 Pro from Koodo (single SIM version), out of the box it prompted me to update, after I did this, I had for example a corrupted Settings app (name was a mix of letters and numbers and same name corruption with Chinese characters within). After this happened I did a factory reset, was back on 107 and was prompted to update again in the morning, which I did. Same outcome as above, after apparently successful installation and restart, I was still on 107 ...
Click to expand...
Click to collapse
You issues are very similar to mine.
I also had a corrupted settings app as well (mix of letters and numbers with Chinese characters)
Still no fix for the 107 to 109 update to report on.
So I had a chat session with a rep on Huawei Canada's site, he mentioned that my phone was 'Not Ready' for the update and hence why it was not updating.
I opted into an email notification through the rep for when the update becomes available.
I would recommend anyone else with this issue to bring it up to Huawei Canada and opt into a notification when the issue is resolved.
aglbz said:
So I had a chat session with a rep on Huawei Canada's site, he mentioned that my phone was 'Not Ready' for the update and hence why it was not updating.
I opted into an email notification through the rep for when the update becomes available.
I would recommend anyone else with this issue to bring it up to Huawei Canada and opt into a notification when the issue is resolved.
Click to expand...
Click to collapse
Well, given the corrupted Settings app that I (and seemingly others) had, I would say that "not ready" is rep speak for "we screwed up, please wait until we fix it" ...
Was delighted to see that CLT-L04 8.1.0.111(C792) showed up as update on my phone this morning and I hit the install button right away. Sadly (and really really annoyingly) the behaviour is the same as with the 109 update: the update seems to work but after restart the Settings app is corrupted and system shows still to be on 107. Immediately after the restart I was told to update to 111 which I tried once more, only to got a "Update couldn't be installed" fail message.
I then downloaded 111 again, wiped the cache partition and tried another installation. This time, the installation happened a lot faster (given the amount of update data, unrealistically fast) and I got the Update success message again. However, upon restart, I was still on 107 - this is pathetic!
Just to add to this story, I had to send my phone in for repair and apparently (according to repair report) the mainboard was replaced?! I am on .111 now and sincerely hope that future updates will perform as intended ...
ccwestcliff said:
Just to add to this story, I had to send my phone in for repair and apparently (according to repair report) the mainboard was replaced?! I am on .111 now and sincerely hope that future updates will perform as intended ...
Click to expand...
Click to collapse
Why u had to send it to repair?? is it because of the 'Update' not really updating issue? If you got any further solution for this,please let me know. I am also having the same problem.
Has anyone had any success with updates yet? I am still stuck on 107 and it say 114 is ready but always goes back to 107. No updates have installed, had the Telus p20 pro since July .
I haven't had any success yet. This is my last phone from them
Hello everyone,
Yesterday I flashed my moto g5s plus with flashable android oreo update. Later I found out that the network drops frequently. So I tried to downgrade to Nougat 7.1 and was successful doing so. Then I was amazed to get the official OTA of oreo 8.1 but due to unlocked bootloader I couldnt install that as it eventually gave me an error. So I tried to relock bootloader but failed to do so due to the clear warning of bootloader downgrade(that was because I updated to oreo and downgraded to Nougat). Later I tried locking the bootloader using the oreo files i.e. the extracted files from oreo firmware, althought I was on Nougat but was successful. But the network started to drop frequently and was unable to use the network services. So I rushed to moto service centre where I was first said there could be a problem with the motherboard lol. But I told them to just flash the firmware as I thought it was a s/w issue. The firmware flashing resolved the problem of network droping but the new issue arrised, which was, when I place a call the receiver gets the call but cannot hear anything same goes to my device. Even i couldnt hear anything. The service centre advices to replace an IC, which they say is damaged and he added that my device is showing "fake network".
Can anyone please help me with this?
Thank you!
Give the phone to SC and ask them to do the necessary things as they suggested.
Has anyone had problems with your phone's hotspot after updating to Android 13 on ZenFone 8?
I also did a factory reset, but it didn't help.
The signal is very weak and even if you connect another device, this then can not navigate because it is internet not available.
Back to Android 12 the problem disappears.
Did you have the same problem and how did you solve it? Thank you.
LineOFire said:
Has anyone had problems with your phone's hotspot after updating to Android 13 on ZenFone 8?
I also did a factory reset, but it didn't help.
The signal is very weak and even if you connect another device, this then can not navigate because it is internet not available.
Back to Android 12 the problem disappears.
Did you have the same problem and how did you solve it? Thank you.
Click to expand...
Click to collapse
I just updated to Android 13 on my Zenfone 8 today, and the hotspot settings just disappeared (at least if I navigate through the settings). If i search all settings, I can find them, but trying to turn it on does nothing.
I wonder if this is an Asus problem or an AT&T (my carrier) problem.
tbessie said:
I just updated to Android 13 on my Zenfone 8 today, and the hotspot settings just disappeared (at least if I navigate through the settings). If i search all settings, I can find them, but trying to turn it on does nothing.
I wonder if this is an Asus problem or an AT&T (my carrier) problem.
Click to expand...
Click to collapse
I did all the tests, even the hard reset, nothing to do. I also tried to change mobile operator sim. It's just a bug in Android 13.
I asked Asus support, but they didn't give any answer.
Downgraded to Android 12 and that's the only way it works.
LineOFire said:
I did all the tests, even the hard reset, nothing to do. I also tried to change mobile operator sim. It's just a bug in Android 13.
I asked Asus support, but they didn't give any answer.
Downgraded to Android 12 and that's the only way it works.
Click to expand...
Click to collapse
Two questions...
1. How did you try to get help from Android support? I was thinking of trying their phone support.
2. How did you downgrade? Is there a way to do with without wiping my phone and without rooting? I found a few guides about it online and they all seemed to require wiping the phone.
LineOFire said:
I did all the tests, even the hard reset, nothing to do. I also tried to change mobile operator sim. It's just a bug in Android 13.
I asked Asus support, but they didn't give any answer.
Downgraded to Android 12 and that's the only way it works.
Click to expand...
Click to collapse
Oh, and also it's now taking about 7 minutes to register on the at&t network (as opposed to instantly in Android 12). How could they possibly have let this release into the wild?
tbessie said:
Two questions...
1. How did you try to get help from Android support? I was thinking of trying their phone support.
2. How did you downgrade? Is there a way to do with without wiping my phone and without rooting? I found a few guides about it online and they all seemed to require wiping the phone.
Click to expand...
Click to collapse
Write to Asus support, you can find it on the official page. If you have registered your product, put all the data related to model and serial, only then they will move to find a solution to this bug.
For downgrade, you will always find in the support page for your model the firmware to download. Once downloaded, enter it in the internal folder of the phone and you will see that the update notification appears above.
Click and install. Obviously you lose all the data, because it resets to the factory state.
LineOFire said:
Write to Asus support, you can find it on the official page. If you have registered your product, put all the data related to model and serial, only then they will move to find a solution to this bug.
For downgrade, you will always find in the support page for your model the firmware to download. Once downloaded, enter it in the internal folder of the phone and you will see that the update notification appears above.
Click and install. Obviously you lose all the data, because it resets to the factory state.
Click to expand...
Click to collapse
Thanks for the info. It wasn't obvious to me about the phone resetting - for all i knew, Asus might have an intelligent downgrade process that preserved the user data. Too bad they don't.
tbessie said:
Thanks for the info. It wasn't obvious to me about the phone resetting - for all i knew, Asus might have an intelligent downgrade process that preserved the user data. Too bad they don't.
Click to expand...
Click to collapse
Zenfone 8｜Phones｜ASUS Global
A new compact powerful choice: Flagship 5G processor · 120Hz AMOLED display · 4000mAh battery · Pro-grade dual rear and front camera · IP68 water resistant
www.asus.com
I also had this issue of the hotspot function disappearing after the Android 13 update. I followed the step to downgrade to 12. This worked, but before I could finish setting up my phone again, it was already automatically updating to 13. I reinstalled 12, and waited to connect to wi-fi to get things restored. Shortly after connecting to wi-fi again, the 13 update started again. I paused the update and then enabled developer options and disabled automatic system updates there, but I am not able to disable auto-updates in the regular system update settings. Is root required to disable this menu option? I have not rooted my phone and would prefer not to, if possible. Any suggestions?
Edit: So far, the phone hasn't resumed the auto-update overnight or following a couple restarts of the phone. The notification remains and I occasionally get prompts to continue the paused update, but I am able to ignore them. I guess I can live with it as is, but if anybody has any other ideas, please share. Thanks.
Edit: Today, I woke to find that the 13 update has downloaded and will install on reboot. I rebooted and let it complete the update to 13. Then, I downgraded to 12 once again. This time around, the option to disallow automatic updates was not greyed-out in system update settings. I disallowed auto-updates. The notification saying the update to 13 is available remained, this time, I was able to dismiss it. I don't know what to think about the previous issues I had, but it seems to have resolved it now.
b.a.w said:
I also had this issue of the hotspot function disappearing after the Android 13 update. I followed the step to downgrade to 12. This worked, but before I could finish setting up my phone again, it was already automatically updating to 13. I reinstalled 12, and waited to connect to wi-fi to get things restored. Shortly after connecting to wi-fi again, the 13 update started again. I paused the update and then enabled developer options and disabled automatic system updates there, but I am not able to disable auto-updates in the regular system update settings. Is root required to disable this menu option? I have not rooted my phone and would prefer not to, if possible. Any suggestions?
Edit: So far, the phone hasn't resumed the auto-update overnight or following a couple restarts of the phone. The notification remains and I occasionally get prompts to continue the paused update, but I am able to ignore them. I guess I can live with it as is, but if anybody has any other ideas, please share. Thanks.
Edit: Today, I woke to find that the 13 update has downloaded and will install on reboot. I rebooted and let it complete the update to 13. Then, I downgraded to 12 once again. This time around, the option to disallow automatic updates was not greyed-out in system update settings. I disallowed auto-updates. The notification saying the update to 13 is available remained, this time, I was able to dismiss it. I don't know what to think about the previous issues I had, but it seems to have resolved it now.
Click to expand...
Click to collapse
I didn't see the Andorid 13 update even before the downgrade, I searched for it and installed it if I wanted it.
Adding to my posts above from February 18:
I was able to remain on Android 12, retaining the Wi-Fi hotspot functionality, until this morning. I awoke to find a software update notification message, giving two options: update or later. The message also stated that if I pressed later, it would continue with the update in 30 minutes. I rebooted the phone, and the update notification returned, however, lacking the 30 minute warning. A short while later, the phone began to automatically download the update, despite the option in settings disallowing auto-updates being ticked. I force-stopped the system update app, and it stopped downloading the new update. After a short while, it completed the android 13 system update download anyway. I decided to give the 13 update a try again, seeing that there was a smaller update added to the Asus Bios and Firmware download page on March 16th. I proactively backed up my data, knowing that I would likely need to downgrade to 12 again shortly to regain hotspot functionality. I rebooted to apply the base 13 update; no hotspot functionality, as expected. I then downloaded and applied the March 16th (WW-33.0210.0210.269) update OTA; still no hotspot functionality. I plan to downgrade again to Android 12, but I question how long I will be able to use it before another automatic update to 13 is forced upon me by Asus. Does anyone have any advice as to how to activate the hotspot on 13 or a way to guarantee that 12 will not be auto-updated to 13?
Edit: For anyone who might be having the same issue, here is what I have tried and so far, seems to be working. After downgrading to 12, I did not connect to internet during the initial phone setup process. When I did, the phone would already start automatically downloading the 13 update even before the setup process was finished. After setup, I immediately disabled automatic updates both in the regular system settings and in developer options (after enabling these, of course). I find it interesting that before, even with these two settings to disallow automatic updates in use, the automatic update would begin. The only other step I took this time was to disable my system app for system updates per the following method. https://www.xda-developers.com/disable-system-app-bloatware-android/
I understand that this method is likely used more for added bloatware than for system apps, and I questioned at first if it would even work for a system app. Still, after disabling the system update app, it shows "disabled" under its entry in the complete app list in settings, and the system update options in the settings menu are not visible anymore. The main "system" header in the settings menu does show a red dot with "1" indicating that there is something available within the submenu, but as stated there is nothing within pertaining to system updates since disabling the system update app. So far, there have been no other notifications for the 13 update as before. This system update app is easy to reenable, as shown in the link above, so if I want to download the system update later on, it is no problem. I will add to this post if this method fails, but so far, so good.