Develop Bugs

[Q] Lose GSM signal and does not regain (ACRO S)

Hi there,
I have an Acro S and absolutely love the hardware couldn't wish for any better. :good:
However I have an issue I am struggling with right now. At my workplace I get patchy signal with my carrier (Orange/EE in the UK). I'm ok with this but lately when I go to a part of the building where I lose signal, the phone never recovers signal again, it just shows "Emergency Calls Only" and needs either re-booting or airplane mode on and off again to recover signal.
Is this something anyone else has seen and is it likely to be a software issue or a hardware issue?
I've looked in the settings and I am running software version 6.1.A.2.50 which I think is the latest.
Anyone have any suggestions on how to fix as my wife is pregnant and I'd hate to miss an important phone call because of this!

In my view, this problem must be connected to which ROM you are using
with refrence to my experience, I get so many issuses like this..
Firmly suggest you change your ROM and try again XD

cyx2009cjw said:
In my view, this problem must be connected to which ROM you are using
with refrence to my experience, I get so many issuses like this..
Firmly suggest you change your ROM and try again XD
Click to expand...
Click to collapse
Thanks for the advice, however I am using the standard Sony ROM and there doesn't appear to be an update available. I'm tempted to root the phone and install one of the ROMs in the development section here but I use the Barclays Mobile app and find it very useful and that won't work on a rooted phone.
Do you have an Acro S if so which ROM are you using?

pajd100 said:
Thanks for the advice, however I am using the standard Sony ROM and there doesn't appear to be an update available. I'm tempted to root the phone and install one of the ROMs in the development section here but I use the Barclays Mobile app and find it very useful and that won't work on a rooted phone.
Do you have an Acro S if so which ROM are you using?
Click to expand...
Click to collapse
You can do a Repair using PC Companion...But before you do, backup all your settings/apps in the internal memory as it will factory reset your phone all the way back...So just do full backup using " Backup & Restore " first, then connect to pc and hit Repair using PCC

wajahebat said:
You can do a Repair using PC Companion...But before you do, backup all your settings/apps in the internal memory as it will factory reset your phone all the way back...So just do full backup using " Backup & Restore " first, then connect to pc and hit Repair using PCC
Click to expand...
Click to collapse
So via PC companion I have now installed the latest firmware 6.1.A.2.55. Let's see if this fixes it. Hopefully it will otherwise it's a reset and re-install of everything (Painful!)

pajd100 said:
So via PC companion I have now installed the latest firmware 6.1.A.2.55. Let's see if this fixes it. Hopefully it will otherwise it's a reset and re-install of everything (Painful!)
Click to expand...
Click to collapse
Well that's a good thing....You also have installed to the latest firmware....:good:

Mi 5s stuck on start - cant login nor activate MI account

Hi guys, it looks xda is my last chance resort to save the phone.
Once purchased a week ago I still cant use the phone by now.
The phone seem to be attached to some account which I did not create and thus cant access.
The phone is locked/bootloader/ and not activated /MI account verification/, neither I can restore any password by loggin with my phone number - Xiaomi does not send me any verification text SMS back.
I tried recovery and Fastboot and while recovery allows me to flash with chineese MISuite back and forth with 8.0.3/android show errors-stopped processes/ and 7.5.XX,
fastboot does not allow anything-Flash xbl error.
Anybody-anything? Because ./except my numerous reclaiming in Xiaomi and the shop/ I am out of ideas by now ??
Cheers,

Looks like a stolen phone. If you bought it via paypal/credit card request a refund/charge back.

pr0x2 said:
Looks like a stolen phone. If you bought it via paypal/credit card request a refund/charge back.
Click to expand...
Click to collapse
May be. But I bought it from Gearbest.com. Are they prone to such cases?
Good idea w/charge back.

Usually not, but I would return it anyway, just to be sure. If it has been used, there is no saying how the battery will perform or if it's full of viruses and spyware.

If you wont solve the problem, maybe I'll be willing to rebuy i from you. Depends on the price. Im looking for bricked mi5s

zsolarewicz said:
Hi guys, it looks xda is my last chance resort to save the phone.
Once purchased a week ago I still cant use the phone by now.
The phone seem to be attached to some account which I did not create and thus cant access.
The phone is locked/bootloader/ and not activated /MI account verification/, neither I can restore any password by loggin with my phone number - Xiaomi does not send me any verification text SMS back.
I tried recovery and Fastboot and while recovery allows me to flash with chineese MISuite back and forth with 8.0.3/android show errors-stopped processes/ and 7.5.XX,
fastboot does not allow anything-Flash xbl error.
Anybody-anything? Because ./except my numerous reclaiming in Xiaomi and the shop/ I am out of ideas by now ??
Cheers,
Click to expand...
Click to collapse
I had the same problem when trying to install Miui again after installing LOS. But I had already unlocked my bootloader.
If you use a special cable, http://en.miui.com/thread-324300-1-1.html, you can flash a Miui developer ROM and unlock your bootloader. There are plenty of manuals on the internet.

Everythings ok now, Xiaomi support helped effectively )). Thread to be closed.

What solution did they have for you?
Sent from my MI 5s using XDA Free mobile app

wim69 said:
What solution did they have for you?
Sent from my MI 5s using XDA Free mobile app
Click to expand...
Click to collapse
I did not receive verification SMS from Xiaomi to reset the password.
I had to sent them IMEI, phone no, invoice copy etc.
After all it succedeed.

Randomly system_ui has stopped crash

so, i keep getting this problem. the system_ui randomly stopped and crash my phone. i don't know what triggering it. sometime when charging, sometime when browsing, sometime when play games, sometime even when i don't touch my phone for hours.
but, i remember when it start. it was when i browse the web a lot with opera mini. it is uninstalled of course.
fix i tried? i used the xperia companion, it was the third time this problem keep return. and sony keep telling me to use the companion even though i tell them i did and the problem return. please help and thank you.
xperia m5 e5663
30.2.B.1.21 (marshmellow)

So just a factory reset doesn't work?

ih8redsn0w said:
So just a factory reset doesn't work?
Click to expand...
Click to collapse
nope, after few hours with only whatsapp installed and update all the default apps, system_ui crashdd again.

I could only suggest downgrading

ih8redsn0w said:
I could only suggest downgrading
Click to expand...
Click to collapse
i have considered that, and want to avoid that. but i guess no other way then.. thanx fos helping.

I think there is a problem with system partition. So you should system repair by Xperia Companion.
If you have rooted device firstly relock bootloader before system repair otherwise Companion wouldnt accept device to repair.
Or you can flash stock rom by using Flashtool. but be careful about FSC scripts.

baalzebuub said:
I think there is a problem with system partition. So you should system repair by Xperia Companion.
If you have rooted device firstly relock bootloader before system repair otherwise Companion wouldnt accept device to repair.
Or you can flash stock rom by using Flashtool. but be careful about FSC scripts.
Click to expand...
Click to collapse
They said they've already used Xperia companion and even if you click no on using the fsc script it will refuse to flash

ih8redsn0w said:
They said they've already used Xperia companion and even if you click no on using the fsc script it will refuse to flash
Click to expand...
Click to collapse
Which version of Flashtool that say dude ? I'm always feelin' anxious while using flashtoolI because of that script issue.
I think im usin' 0.9.23.X. I'll check it when arrived home.

baalzebuub said:
Which version of Flashtool that say dude ? I'm always feelin' anxious while using flashtoolI because of that script issue.
I think im usin' 0.9.23.X. I'll check it when arrived home.
Click to expand...
Click to collapse
0.9.23.1 is the one that doesn't work 0.9.23.2 works

I could solve it removing the notification site from Chrome, from menu setting Chrome, web site setting, Notifications and bloqued all sites except Google, then the issue will desapire
Regards

getting "your device is corrupt and cannot be trusted pixel"

So after a few months of using my google pixel 2 xl, while I was using it I randomly got a black screen with the message:
"Your device is corrupt. It can't be trusted and may not work properly.
Visit this link on another device: g.co./ABH
PRESS POWER BUTTON TO CONTINUE".
Now it happens every time I turn on my phone. :/
I Have tried doing a factory reset and it still appears.
My phone is not rooted, I have the official OS that I got it with it (updated it through the phone's updater).
The phone was purchased directly from the us google online store.
I've tried to contact their support but they didn't have a solution.
Please help me!!

almogsad said:
So after a few months of using my google pixel 2 xl, while I was using it I randomly got a black screen with the message:
"Your device is corrupt. It can't be trusted and may not work properly.
Visit this link on another device: g.co./ABH
PRESS POWER BUTTON TO CONTINUE".
Now it happens every time I turn on my phone. :/
I Have tried doing a factory reset and it still appears.
My phone is not rooted, I have the official OS that I got it with it (updated it through the phone's updater).
The phone was purchased directly from the us google online store.
I've tried to contact their support but they didn't have a solution.
Please help me!!
Click to expand...
Click to collapse
Sounds like one of those non harmful, annoying messages at boot up. Is your bootloader still locked I assume? If so, have you tried side loading the March OTA. I think sometimes during the OTA updater process that some files don't always make it to the system, which is why you get those messages. Is your phone still functioning properly??

Badger50 said:
Sounds like one of those non harmful, annoying messages at boot up. Is your bootloader still locked I assume? If so, have you tried side loading the March OTA. I think sometimes during the OTA updater process that some files don't always make it to the system, which is why you get those messages. Is your phone still functioning properly??
Click to expand...
Click to collapse
First of all thanks for the response!
yes my bootloader is still locked.
Badger50 said:
have you tried side loading the March OTA
Click to expand...
Click to collapse
How do I do that? ^^
and it seems like the phone still functions properly, but I guess only time will tell

almogsad said:
First of all thanks for the response!
yes my bootloader is still locked.
How do I do that? ^^
and it seems like the phone still functions properly, but I guess only time will tell
Click to expand...
Click to collapse
Just follow these instructions if you want to side load an OTA. It's really not that hard ??
https://developers.google.com/android/ota

Badger50 said:
Just follow these instructions if you want to side load an OTA. It's really not that hard
Click to expand...
Click to collapse
Thanks! I'll try that...
Do you think it might fix the problem?
Edit:
it says in the guide:
"find the appropriate driver for your device from the OEM drivers"
but I don't know which one is mine ^^

almogsad said:
Thanks! I'll try that...
Do you think it might fix the problem?
Edit:
it says in the guide:
"find the appropriate driver for your device from the OEM drivers"
but I don't know which one is mine ^^
Click to expand...
Click to collapse
Once you choose the proper OS version for your pc, and install SDK, when you plug your phone in, it should automatically update your device drivers :good:
And yes, there's a good chance it'll fix your problem. Never any guarantees with this tech stuff though

Badger50 said:
Once you choose the proper OS version for your pc, and install SDK, when you plug your phone in, it should automatically update your device drivers :good:
And yes, there's a good chance it'll fix your problem. Never any guarantees with this tech stuff though
Click to expand...
Click to collapse
Hey! It seems like it worked!!!! Thanks!!
I only wish I hadn't listened to the google support team , and hadn't done a factory reset to phone before lol they don't seem to understand too much about their phones, the guy told me he thinks it's just an add
Thanks again man!

almogsad said:
Hey! It seems like it worked!!!! Thanks!!
I only wish I hadn't listened to the google support team , and hadn't done a factory reset to phone before lol they don't seem to understand too much about their phones, the guy told me he thinks it's just an add
Thanks again man!
Click to expand...
Click to collapse
Oh sweet! Glad to hear it my friend, well done. Now you can help others out with the same issue if it comes up :good: Yeah, the Google folks are kinda funny sometimes. The factory reset is their standard MO! And right, an add on the boot up screen....yeah that's funny! I'd be willing to bet most of them use iPhones!!??????

Badger50 said:
Oh sweet! Glad to hear it my friend, well done. Now you can help others out with the same issue if it comes up :good: Yeah, the Google folks are kinda funny sometimes. The factory reset is their standard MO! And right, an add on the boot up screen....yeah that's funny! I'd be willing to bet most of them use iPhones!!
Click to expand...
Click to collapse
How ironic! lol ???

Badger50 said:
Sounds like one of those non harmful, annoying messages at boot up. Is your bootloader still locked I assume? If so, have you tried side loading the March OTA. I think sometimes during the OTA updater process that some files don't always make it to the system, which is why you get those messages. Is your phone still functioning properly??
Click to expand...
Click to collapse
Thanks!! I also had this issue and following your suggestion to sideload the latest OTA, it appears to have fixed the problem.

I've been getting the same corrupt error on reboots on my xl 2(also not rooted), but I have not been able to get the latest OTA to sideload. It nearly completes but aborts last second and gives a Status 1 error. I'm not sure what I'm doing wrong here. Any help will be appreciated.
Got a similar run-around with Google support. When the factory reset was unsuccessful, they've recommended replacing the phone since it's under warranty, however they think replacing my virtually brand new phone with a refurbished phone is appropriate.

Apsel said:
I've been getting the same corrupt error on reboots on my xl 2(also not rooted), but I have not been able to get the latest OTA to sideload. It nearly completes but aborts last second and gives a Status 1 error. I'm not sure what I'm doing wrong here. Any help will be appreciated.
Got a similar run-around with Google support. When the factory reset was unsuccessful, they've recommended replacing the phone since it's under warranty, however they think replacing my virtually brand new phone with a refurbished phone is appropriate.
Click to expand...
Click to collapse
Are adb/fastboot tools the very newest?

Apsel said:
I've been getting the same corrupt error on reboots on my xl 2(also not rooted), but I have not been able to get the latest OTA to sideload. It nearly completes but aborts last second and gives a Status 1 error. I'm not sure what I'm doing wrong here. Any help will be appreciated.
Got a similar run-around with Google support. When the factory reset was unsuccessful, they've recommended replacing the phone since it's under warranty, however they think replacing my virtually brand new phone with a refurbished phone is appropriate.
Click to expand...
Click to collapse
Unlock then re-lock your bootloader(/s) maybe?

Great job guys, this solution with sideload latest OTA worked for me too with no need to unlock bootloader! :good::good::good:

I can confirm this working again. Pixel 2 XL with 9.0 and November security update.

Thanks!
I just had the corrupt message pop up (bootloader locked), and the sideload ota update seems to have worked!

michaelbsheldon said:
Are adb/fastboot tools the very newest?
Click to expand...
Click to collapse
I'm experiencing the same problem as Apsel, yes the adb/fastboot are the latest.
Error applying update: 15 (ErrorCode : kNewRootfsVerificationError)
E:Error in /sideload/package.zip (status 1)

Badger50 said:
Just follow these instructions if you want to side load an OTA. It's really not that hard ??
https://developers.google.com/android/ota
Click to expand...
Click to collapse
I know this is an old post but I'm having the same issue. Also cannot connect to pc due to, I'm assuming daughterboard issue this and previous pixel models have. I have been rooting phones since the S3 and am no virgin to the sdk. I tried to take it to ubreakifix which was a 4 hour round trip for me. I was told I would have to sign a waiver since the screen is glued to the phone and that was the only way to get to the internals. When I arrived I watched 4 bozos poke at the charging port for 20 min and then contradicting what I was told the night before over the phone that they were not comfortable doing the repair and then they tried to sell me a new device. I just got off chat with google and they want to charge me 270 dollars to fix even though I went to an authorized service center when it was in warranty. Will fastboot work over wifi?

Toolmighty said:
Will fastboot work over wifi?
Click to expand...
Click to collapse
'fraid not. Both the bootloader and recovery have stripped down hardware support, limited essentially to the display and storage. Neither has WiFi support that I know of, thus you have to use a USB cable.

I figured it out after I figured out how to fix the daughterboard issue w/o replacing the daughterboard. Verizon are some sneaky *^&$^s. Thx for the reply tho. I'm sure ur quite busy.

Mi A2 Lite - Stuck on the Android One screen

Hello. What happened was that my Xiaomi Mi A2 Lite gave a very sinister problem, I was using it normal, when it suddenly crashed, I tried to restart it, but when it called it got stuck on the Android One screen and it doesn't leave that screen. I would like to know if there is anything you guys advise me to try to do. I would like some help, the cell phone is very good and I had never locked it. Only it gave this problem.
My bootloader is blocked and the unlock option in the developer settings is disabled. I already tried to flash the latest system using XiaomiMiFlash, MiFlashPro, MiFlashBeta, TOOL ALL IN ONE, among other methods and none makes the phone come back to life. When using XiaomiMiFlash or MiFlashPro, the following error appears: "ack count don't match", and so the flash process does not end. Using MiFlashBeta, this error does not appear, but the process ends and nothing changes. The phone remains locked.

Now we are two, read somewhere you must use Mi Authorized Mi flash, then perform a deepflash.

Strelock07 said:
Now we are two, read somewhere you must use Mi Authorized Mi flash, then perform a deepflash.
Click to expand...
Click to collapse
PHP:
I saw about this authorized account, but I didn't find anything that could circumvent it or an account, I don't know, anything that solved this problem would be very useful

PedrocaLu2004 said:
PHP:
I saw about this authorized account, but I didn't find anything that could circumvent it or an account, I don't know, anything that solved this problem would be very useful
Click to expand...
Click to collapse
On the Mi flash tab look for authentication, sign in with your mi account. Remember to use Mi flash pro.
Same problem as me?
https://www.reddit.com/r/Xiaomi/comments/gluuqk/mi_a2_lite_bcb_failed_to_fsync/

Strelock07 said:
On the Mi flash tab look for authentication, sign in with your mi account. Remember to use Mi flash pro.
Same problem as me?
Click to expand...
Click to collapse
I had already tried to do this procedure that he told me, but it also didn't solve it, it gave the error "ACK don't match". I saw your post on Reddit at this link you sent and apparently we are having problems very close, I also cannot format the device