Database Info

[Q] Can't update after downgrade to ICS

hi, i just got my tablet back from repairs and i asked them to install ICS if they had to reset the firmware, and they did. now my problem is that i want to update to the 4.2 JB that came out (while my ASUS was in repairs for 3 WEEKS) but i can't. when i try to update, it just says "no update found". i have already talked to their "experts" and he just kept saying "oh, it come to your tablet when it ready" I have also tried to download the update from their site, but then when it tells you what version you need by looking at the build number, i noticed mine was IML74K.WW_epad-9.4..... and shouldn't it be something more like US_epad-9.4.....? i tried to install it anyways but it never detected it on the sd card. so then i tried to just use fastboot and flash it to the device, but when i entered the boot menu, THERE WAS NO OPTION!! In fact, there was only 2 options, wipe data, and boot android. there was no usb or RCK (or whatever it was) option. i also have several other problems, but i'll leave them for another day and another post, sense they may be related
Any help would be awesome sense it's obvious I'm not going to get much help from ASUS. Let me know if you need any other info too!
Thanks in advanced!!
Jake

Snakester15 said:
hi, i just got my tablet back from repairs and i asked them to install ICS if they had to reset the firmware, and they did. now my problem is that i want to update to the 4.2 JB that came out (while my ASUS was in repairs for 3 WEEKS) but i can't. when i try to update, it just says "no update found". i have already talked to their "experts" and he just kept saying "oh, it come to your tablet when it ready" I have also tried to download the update from their site, but then when it tells you what version you need by looking at the build number, i noticed mine was IML74K.WW_epad-9.4..... and shouldn't it be something more like US_epad-9.4.....? i tried to install it anyways but it never detected it on the sd card. so then i tried to just use fastboot and flash it to the device, but when i entered the boot menu, THERE WAS NO OPTION!! In fact, there was only 2 options, wipe data, and boot android. there was no usb or RCK (or whatever it was) option. i also have several other problems, but i'll leave them for another day and another post, sense they may be related
Any help would be awesome sense it's obvious I'm not going to get much help from ASUS. Let me know if you need any other info too!
Thanks in advanced!!
Jake
Click to expand...
Click to collapse
The stock 4.2 (10.6.1.8) has an assert that will only allow it to be installed from 10.4.2.20. If memory serves me correctly ICS does not have the usb icon until unlocked. Also the new 4.2 bootloader only has three icons - no usb.
Are you unlocked? Most units that come from repair are not and can't be unlocked.
With all the unresolved issues on 4.2 I would not put it on my tablet at this time. There are many bricks waiting for a resolution.

thanks, that helped fix it!
tobdaryl said:
The stock 4.2 (10.6.1.8) has an assert that will only allow it to be installed from 10.4.2.20. If memory serves me correctly ICS does not have the usb icon until unlocked. Also the new 4.2 bootloader only has three icons - no usb.
Are you unlocked? Most units that come from repair are not and can't be unlocked.
With all the unresolved issues on 4.2 I would not put it on my tablet at this time. There are many bricks waiting for a resolution.
Click to expand...
Click to collapse
I downloaded the 4.1 firmware and it detected it and installed it right away. I don't know why they couldn't tell me that when I called, but it fixed the problem. And I know you said not to, but I installed 4.2 anyways because I was too curious, and I have personally found no problems and like the new features.

Issue since cm11,4.4.4, es manager and usb not recognized

My 959V is rooted, had plenty of roms,ect over the last 3 years decided to do Gremlin remover and update it...,
Couple days ago upgraded to the "909" download of CM11,4.4.4, but every site I get it from gives me 908 (even though they all say 909) (last 3 digits of download version). The 908 will not recognize on my Win 7 laptop, but was fine up to now with previous cm11 same phone..
I have used the same cable for the last year for both my Galaxy and 2 Sidekicks phones, data and charging, now the Galaxy only charges, Windows detects but wont recognize, does on the sk4g's
Also (908) will not allow me to paste into sys/media with a " read only issue", although up to now swapped 15 different bootani without problems. Tried 3 different root file managers,same outcome.
Is the driver for the phone firmware windows looks for(on the phone itself) replaceable from sdcard? Im guessing its a bootloader issue and the 908 is the one not to of put on my phone.
Whats the probability I am getting the 909 but the 908 will not allow it to surpass it. Goes through the whole flash and on reboot I have to reenter emails,playstore apps,ect, but on 908 still in settings.
I can/ have been able to swap 1 rom via twrp and sdcard on 908 ( to slimkat4.4.4 and back to 909, but comes up 908) any other roms error before flash(and slimkat does not recognize on usb either).
is it a Kernel fix, and can it be flashed via sdcard? Bootloader via sdcard? Bad usb port? Does charge, and the drivers/ cable verified.
Thank you for any help, been 3 days now, redone my laptops (2) from scratch, everything ,c++,java,netframework,samsung,zadig 2.0, and more.

DId you do a clean upgrade (did a factory reset) before you installed CM11? If you didn't, go into TWRP and do a full backup (/system, /data) and do a factory reset, then boot up the phone and see if your computer will recognize it.

FBis251 said:
DId you do a clean upgrade (did a factory reset) before you installed CM11? If you didn't, go into TWRP and do a full backup (/system, /data) and do a factory reset, then boot up the phone and see if your computer will recognize it.
Click to expand...
Click to collapse
Yes, cashe,factory and davlik, before and after flash. I also have a 2nd motherboard,swapped them out and seen that it also is the 908 download but does recognize and allows me to ES Explorer swap boot animation. Im guessing I somehow erased the driver from the phone itself.
Ive done some Iphone jailbreaking unlocking for friends and found that a certain baseband (if I remember right 5.13.xx or 5.16.xx) would basically lock the phone unable to downgrade or upgrade and was to be avoided. Wondered if this a similar issue. (screwing up my bootloader)
What does windows look for via usb in the phone, adb,? Is it in the kernel and reflashable via sd?
I read also that the mini usb port can get bent over time and needs centering, tried that, cord fits better but not the issue.
Tried to zagdig the 2nd motherboard (worked) for drivers, but the 1st one still has error,device malfunctioned and cant be recognized by windows (7).
If i can get the Anton basic with a twist (no rom just the cm,I have it for Oden but wonder if Its possible cm flash)., Im good I believe,thats how I first rooted and got 4.3 cm,then 4.4.4, 908. Dunno,willing to try anything, not worried about it as I have a 2nd motherboard.
The rom is awesome, with no isuues except the battery stats vary. It says 3 hrs left then dies 10 min later, tried to erase the battery cashe in recovery but doesnt change anything. (related via usb?)
Thank you.

Floridasun said:
Yes, cashe,factory and davlik, before and after flash. I also have a 2nd motherboard,swapped them out and seen that it also is the 908 download but does recognize and allows me to ES Explorer swap boot animation. Im guessing I somehow erased the driver from the phone itself.
Ive done some Iphone jailbreaking unlocking for friends and found that a certain baseband (if I remember right 5.13.xx or 5.16.xx) would basically lock the phone unable to downgrade or upgrade and was to be avoided. Wondered if this a similar issue. (screwing up my bootloader)
What does windows look for via usb in the phone, adb,? Is it in the kernel and reflashable via sd?
I read also that the mini usb port can get bent over time and needs centering, tried that, cord fits better but not the issue.
Tried to zagdig the 2nd motherboard (worked) for drivers, but the 1st one still has error,device malfunctioned and cant be recognized by windows (7).
If i can get the Anton basic with a twist (no rom just the cm,I have it for Oden but wonder if Its possible cm flash)., Im good I believe,thats how I first rooted and got 4.3 cm,then 4.4.4, 908. Dunno,willing to try anything, not worried about it as I have a 2nd motherboard.
The rom is awesome, with no isuues except the battery stats vary. It says 3 hrs left then dies 10 min later, tried to erase the battery cashe in recovery but doesnt change anything. (related via usb?)
Thank you.
Click to expand...
Click to collapse
I didnt do a backup, if thats an issue , can I backup 2nd motherboard and apply to the first?

Floridasun said:
Yes, cashe,factory and davlik, before and after flash. I also have a 2nd motherboard,swapped them out and seen that it also is the 908 download but does recognize and allows me to ES Explorer swap boot animation. Im guessing I somehow erased the driver from the phone itself.
Ive done some Iphone jailbreaking unlocking for friends and found that a certain baseband (if I remember right 5.13.xx or 5.16.xx) would basically lock the phone unable to downgrade or upgrade and was to be avoided. Wondered if this a similar issue. (screwing up my bootloader)
What does windows look for via usb in the phone, adb,? Is it in the kernel and reflashable via sd?
I read also that the mini usb port can get bent over time and needs centering, tried that, cord fits better but not the issue.
Tried to zagdig the 2nd motherboard (worked) for drivers, but the 1st one still has error,device malfunctioned and cant be recognized by windows (7).
If i can get the Anton basic with a twist (no rom just the cm,I have it for Oden but wonder if Its possible cm flash)., Im good I believe,thats how I first rooted and got 4.3 cm,then 4.4.4, 908. Dunno,willing to try anything, not worried about it as I have a 2nd motherboard.
The rom is awesome, with no isuues except the battery stats vary. It says 3 hrs left then dies 10 min later, tried to erase the battery cashe in recovery but doesnt change anything. (related via usb?)
Thank you.
Click to expand...
Click to collapse
You can flash new kernels via recovery but it sounds like your issues are bigger than that. The fact that the 2nd motherboard is recognized via USB but not the 1st suggests that there's some kind of hardware issue. The drivers on your computer are working fine since the 2nd mobo is recognized, and so is your USB cable.
Why not just keep using your 2nd mobo? Is there something wrong with the 1st?

FBis251 said:
You can flash new kernels via recovery but it sounds like your issues are bigger than that. The fact that the 2nd motherboard is recognized via USB but not the 1st suggests that there's some kind of hardware issue. The drivers on your computer are working fine since the 2nd mobo is recognized, and so is your USB cable.
Why not just keep using your 2nd mobo? Is there something wrong with the 1st?
Click to expand...
Click to collapse
O.K., so Ive been playing with the second mobo just to test different angles.
1) E.S. File manager is the culprit, swapped out for a paid app Ive used with Sidekick 4g, Root Explorer, and boot ani. goes fine, on both mobos.
2) The latest gapps (cm 11 w/ gaps 4.4.x) was giving me a "Google servers cannot be reached" error on both mobos, used the gapps for cm 10.1 (jb 4.3) and all is working, both mobos.
3) Was reading that possibly the adb driver is in the kernel, and thats what windows is looking for? Ive tried but can only sd card flash at this point so, giving up. I can bluetooth,wifi share or email files to myself if need be. Im guessing its a hardware issue beings that the 2nd mobo was reflashed identical to to the first. (with exception of one click 2.3.6,and w/a twist oc/uv on the 2nd),1st one will not downgrade at all below 4.4.4 by sd, I was trying to ics a rom guessing the foundation might overwrite any missing stuff then upgrade back to 4.4.4.
One post mentioned that the mtd/bml cross flash is a no-no, could that mess up usb driver identity on the phones side?
Not a big deal, both phones/ roms are working great and have no issues (except 1 doesnt connect to a computer for file transfer). Thank you for your help.
Little early to ask but are you going to be in this forum long enough for lollipop to be ported? I would send you this phone for devving if you think you can get it to transfer files. Also need to get a lcd/digitizer, i have the rest of the phone.
Also, the phone was working fine up to about a month ago, it was recognized by the computer, only difference I made was trying apps, off playstore, five fingers for ebay,different weather apps for widgets,silver/gold prices apps. Thats when it started not recognizing.

I was getting the same error about the google servers, then I tried a earlier version of gapps. Connects now.

Floridasun said:
Little early to ask but are you going to be in this forum long enough for lollipop to be ported? I would send you this phone for devving if you think you can get it to transfer files. Also need to get a lcd/digitizer, i have the rest of the phone.
Click to expand...
Click to collapse
I have no plans to try a Lollipop port, this phone is almost 4 years old now. You might be better off sending the phone to @bhundven since I recently got two dev phones donated to me.
As far as the phone itself goes, the phone should be recognized even if there is no driver for it installed on your computer. You can use this software to verify that
http://www.nirsoft.net/utils/usb_devices_view.html
I don't believe you can even edit anything on the phone to make the USB device not be recognized when plugged in short of bricking your phone, so if there isn't even a USB connection being made, as I mentioned before, it looks like a hardware issue is causing your problems.
In that case, it'll be hard to flash anything without going through a lot of hassle since all the reliable recovery methods we have need that you are able to use your USB port on the phone.
EDIT
If you do still have TWRP available on the phone, flashing any ROM will reflash a kernel, but be careful because the recovery is tied to the kernel and some ROMs have a non-working recovery, so if you happen to flash some of these you'll be stuck with a nice paperweight . The latest CM11 I have posted does have a working kernel/recovery but I still don't think it'll fix your issue.

FBis251 said:
I have no plans to try a Lollipop port, this phone is almost 4 years old now. You might be better off sending the phone to @bhundven since I recently got two dev phones donated to me.
Click to expand...
Click to collapse
I'm currently looking into it, as well as fixing some issues with cm11. I have an SGS4G, so no need to send a phone.
Not just is it a 4 year old phone, but I am not sure how many people even use this as a daily driver anymore.

bhundven said:
I'm currently looking into it, as well as fixing some issues with cm11. I have an SGS4G, so no need to send a phone.
Not just is it a 4 year old phone, but I am not sure how many people even use this as a daily driver anymore.
Click to expand...
Click to collapse
I still use two of them. Great little phones really. I see no need or use for 5.0 I think running this CM11 from you guys is about the end of the road for these phones. A great ride indeed. Ill be sticking around regardless just to see what happens. Thanks guys☺

[Q] Which unlock tool to unlock v4.1.1?

Hello I am still dealing with a weird problem that I posted on this forum over a year ago that was never resolved. Basically my tablet is stuck running Android version 4.1.1 (Build JRO03C.US_epad-10.4.4.25-20121228) because if I upgrade to any new versions (whether I do it as OTA or via micro USB) my wifi card stops functioning (it does not see any networks). Anyways I even went so far as to RMA it and Asus said they fixed it, shipped it back to me, but in reality all they did was roll me back to 4.1.1, saw the wifi was working and shipped it back to me saying they "fixed" it. Well of course the second I got it back I installed the OTA and wifi broke again... So I just rolled back to 4.1.1 and said screw it, I just won't update it anymore. Well this week I figured I'd try installing the latest OTA and hoped that this version would not kill my wifi, unfortunately the same exact issue has occurred and thus I have once again rolled back to v4.1.1 and my wifi works perfectly...
TLDR; Anyways apologize for the rant/story but basically I am stuck with using version 4.1.1 of Android and am considering flashing a custom rom to try and resolve some issues I am having with the stock rom's wifi, however the official bootloader unlock tools only say they work on version 4.0 (ICS) or version 4.2 (JB). I'm stuck on v4.1.1 so which tool should I use (or am I out of luck)? Thanks

v7 worked your JB version, but I think v8 will work as well. Just try them both - it's just an app. Either it works or not....
But that is the weirdest thing I've heard in a while (reg. WiFi).
What have you done on your router side? I cannot believe this is a problem with the tablet's wifi card.
Is this 'wifi not working' consistent on any router, any network?
Did you reset the router, change the channel?
Do you have possible interference: microwave, bluetooth speakers, bluetooth enabled or any other device that uses radio waves anywhere in the vicinity of the tablet?

berndblb said:
v7 worked your JB version, but I think v8 will work as well. Just try them both - it's just an app. Either it works or not....
But that is the weirdest thing I've heard in a while (reg. WiFi).
What have you done on your router side? I cannot believe this is a problem with the tablet's wifi card.
Is this 'wifi not working' consistent on any router, any network?
Did you reset the router, change the channel?
Do you have possible interference: microwave, bluetooth speakers, bluetooth enabled or any other device that uses radio waves anywhere in the vicinity of the tablet?
Click to expand...
Click to collapse
Thanks appreciate the reply - I just wasn't sure if using the wrong unlocker could brick my device... I'll give 8 a try first then 7 if necessary. The ironic part is that it requires a network connection to complete the unlock operation (I guess so Asus can cross your S/N forever off of their list of devices under warranty).
I agree that this is a strange problem as I have not seen anyone else report it. Basically I tried resolving this about 13 months ago with the help of this board and as mentioned I finally had to RMA it, but ASUS just rolled the version back instead of fixing anything and at that point I just wanted to enjoy using my tablet more than I wanted to fight with ASUS's customer service reps who effed up the first RMA job (the language barrier was also apparent in my interactions with them)...
Since over a year has gone by since the last time I tried an OTA, I hoped that the latest update would not have the same issues but alas, I'm not that fortunate.
As far as what I've tried - I have tried connecting to different networks and changing router channels and checking for interference, but the thing is, I'm quite certain the problem is with the tablet. When I first had the problem I lived in an apt building where I could 'see' 10+ wifi networks at any given time on all different channels with different routers/security settings etc. As soon as I applied the OTA the tablet could no longer 'see' any of them (even as I sat with my laptop/phone connected to wifi right next to it). I now live in a house (and have a different ISP, and a different router) and tablet works perfectly when on version 4.1.1. I don't have as many wifi networks visible from my house, but can still see a few of my neighbor's wifi networks both on the tablet (v4.1.1) and on other devices. But the second that I upgrade, all of them disappear from the tablet's view (but continue to be visible/work on other devices). I have turned wifi on/off, turned airplane mode on/off, tried connecting via wifi direct, rebooted, cold booted, booted into recovery, factory reset all data, etc. but nothing works because the tablet cannot see any wifi networks. And the second that I rollback to version 4.1.1 the wifi works perfectly... I have upgraded and rolled back probably at least 6 times and it is always the same result.
I do also get another weird side affect when I upgrade - the tablet refuses to turn off when I'm on any version higher than 4.1.1. So if I press "Shut Down", the tablet displays "shutting down" and the screen goes black and becomes non-responsive (as do the buttons, just as you would expect when turning off), but it does NOT actually shut down because if I come back 30 mins, an hour, 2 hours later I can feel it running very hot. The only way to truly shut it down is to let the battery drain...
So maybe a better question on my part would have been, do you think installing a custom ROM will even help resolve this issue? Or should I continue using 4.1.1 and not risk making the situation worse with custom ROMS?

WiFi problems are often kernel related..... Did you always take the update OTA?
Did you ever try to flash the latest firmware version manually? OTA updates do go wrong sometimes....
Although repeatedly???? It's weird. Maybe the server your tablet pulled the OTA from hosts a bad copy????
If you do not want to unlock, manually flashing the firmware would be one thing to try. OTA's patch the existing system, replace old files with new ones where necessary. Manually flashing the firmware replaces everything - a totally new installation of everything: bootloader, recovery, kernel, system and data.
But you cannot make it worse by flashing a custom rom. You unlock, flash a custom recovery (which does not change anything else on your system), then you make a nandroid (backup) of your current 4.1.1 system before you flash a rom. So you would always be able to go back to where you are now. On a custom rom you could even try out different kernels, which often are the root cause of wifi problems..
The thing is: If you want to flash a current custom rom like CROMi-X, based on Asus JB 4.2.2, or CROMBi-KK/CM11 which are KK roms, you always have to update your bootloader first. Your .25 bootloader is too old for any current rom.
You can easily do it once you have a custom recovery installed, but even easier would be to update to the latest Asus firmware 10.6.1.14.10 (after unlocking), then flash the custom recovery (TWRP 2.8.1.0), then flash a rom of your choosing.
Downside of this route would be you wouldn't have that 4.1.1 nandroid I mentioned earlier.....
Nahhh - thinking about it, I would recommend you go this route:
Unlock,
flash an older version of TWRP compatible with your current bootloader (TWRP 2.6.1.0 is ok)
make a nandroid of your current system
do a full wipe of cache, Dalvik and data in recovery
flash the 10.6.1.14.10 bootloader in recovery (I can talk you through it)
flash TWRP 2.8.1.0
flash a rom of your choice
Check out my guide, link in my signature, and let me know if you have questions

Thanks - I was able to successfully unlock my device with v7 of the unlock tool (v8 wouldn't even install). Thanks too for the advice on how to flash a custom rom safely. I've never flashed a custom rom before (have rooted a different android device before tho), so I appreciate any help.
I downloaded the blob file for TWRP 2.6.1.0 from here (techerrata.com/browse/twrp2/tf700t), but not sure how to proceed next, (also I don't see a link in your signature to your guide, but I am running a bunch of script blocking addins so maybe that's why) seems like all the guides I am finding say I need to get a copy of a fastboot program (but don't provide links), where can I find that? Again, I appreciate the help.

Sorry, my bad, I don't have a signature on XDA - wrong forum. LOL
My thread is here: http://forum.xda-developers.com/showthread.php?t=2688891
Ask any questions you may have in that thread, but it should cover your questions - I hope

USB Issues with Oreo 8.1

Just got the Oreo 8.1 update on my Project Fi Moto X4 (Motorola Version: OPW28.46-13). The phone does not show up in Windows anymore. No MTP, no ADB. It does charge. I've tried it on two different PCs. It was working seconds before applying the update. The cable does work properly with an S8.
Anybody else seeing this?
I'm a professional Android developer and I was using the phone for development before the update. The other issue is that Developer Mode was disabled after update. I re-enabled it after 8.1 and it didn't work. I've disabled/enabled USB Debugging and developer options several times.
Update:
Tried on OS X now too, same issue. OTG does work.
Work-Around:
https://forum.xda-developers.com/showpost.php?p=76430795&postcount=32

No mention in the release notes: https://mobilesupport.lenovo.com/us/en/Solution/MS127386
Can you help us out with getting the OTA via https://forum.xda-developers.com/moto-x4/how-to/androidone-april-ota-t3784442?

Neffy27 said:
No mention in the release notes: https://mobilesupport.lenovo.com/us/en/Solution/MS127386
Can you help us out with getting the OTA via https://forum.xda-developers.com/moto-x4/how-to/androidone-april-ota-t3784442?
Click to expand...
Click to collapse
It takes some days for the update to show on motoota.

The previous two months became available on there as my phone got the OTA notification. I have yet to see someone who has receive the April, verify they attempted Motoota here on XDA or Reddit.

dburckh said:
Just got the Oreo 8.1 update on my Project Fi Moto X4 (Motorola Version: OPW28.46-13). The phone does not show up in Windows anymore. No MTP, no ADB. It does charge. I've tried it on two different PCs. It was working seconds before applying the update. The cable does work properly with an S8.
Anybody else seeing this?
I'm a professional Android developer and I was using the phone for development before the update. The other issue is that Developer Mode was disabled after update. I re-enabled it after 8.1 and it didn't work. I've disabled/enabled USB Debugging and developer options several times.
Update:
Tried on OS X now too, same issue. OTG does work.
Click to expand...
Click to collapse
I am experiencing the same situation with Project Fi Moto X4 32G (Motorola Version: OPW28.46-13). No MTP, no ADB. It does charge OK. I had no such problems before the upgrade from 8.0 to 8.1. I tried on both Linux and OS X. The same issue. And yes, USB OTG works.

I have the exact same issue and fun fact, this means it no longer works with an Android Auto head unit (it worked flawlessly right up until the second the OTA update was installed).

Factory Data Reset did not fix it. Guess we are hosed unless somebody finds a work-around.

dburckh said:
Factory Data Reset did not fix it. Guess we are hosed unless somebody finds a work-around.
Click to expand...
Click to collapse
This makes me not want to take the update now. What bad news.

Folks, I have this too on my Moto G5S Plus after the April security patch for Nougat. No notification shade when I plug into the PC. No way to access MTP, ADB, etc... I also effects my charging. After the MTP interface fails, I have to reboot the phone before it will charge again.
Post in the Moto/Lenovo forum please. It's a HUGE problem.
dburckh said:
Just got the Oreo 8.1 update on my Project Fi Moto X4 (Motorola Version: OPW28.46-13). The phone does not show up in Windows anymore. No MTP, no ADB. It does charge. I've tried it on two different PCs. It was working seconds before applying the update. The cable does work properly with an S8.
Anybody else seeing this?
I'm a professional Android developer and I was using the phone for development before the update. The other issue is that Developer Mode was disabled after update. I re-enabled it after 8.1 and it didn't work. I've disabled/enabled USB Debugging and developer options several times.
Update:
Tried on OS X now too, same issue. OTG does work.
Click to expand...
Click to collapse

Got the OTA, it does not work and we'll never know why.

Just got the OTA. Don't have my OTG cable, but i can can confirm that I see device in fasboot, but not in ADB.

Neffy27 said:
Got the OTA, it does not work and we'll never know why.
Click to expand...
Click to collapse
Motorola just replied to my support request saying that they are going to replace my phone! I'm hoping it doesn't come to that.

dburckh said:
Motorola just replied to my support request saying that they are going to replace my phone! I'm hoping it doesn't come to that.
Click to expand...
Click to collapse
I am confused... Because of a software update broke ADB?

It would seem so. I will probably try to talk them out of it. I would rather have them escalate a fix.

encountered same issue
dburckh said:
Motorola just replied to my support request saying that they are going to replace my phone! I'm hoping it doesn't come to that.
Click to expand...
Click to collapse

Same here, just got 8.1 this morning on A1 moto x4 and android auto does not work anymore when it is connected to my car HU.

I just got the April 1 8.1 update this morning on my Moto X4 OPW28.46-13. Exactly the same thing. Android Auto head unit doesn't recognize the phone (or vice versa), and the USB options are greyed out and say only "not connected" whether plugged into the head unit or a computer. Project Fi support tells me I need to hard reset the phone. I don't have time to do that at the moment, but they tell me that if it doesn't work (and I very much doubt that it will) they'll "check the warranty options." Which I think is a euphemism for "send you a new phone if it's still under warranty".
What aggravates me about this (aside from the huge waste of time of having to deal with it) is - what if the phone were NOT under warranty? After their update breaks my phone, would they then tell me to buy a new phone?

My stupid X4 will download the 8.1 OTA, start installing, then fail halfway through. Guess there's a bright side after all.

dburckh said:
It would seem so. I will probably try to talk them out of it. I would rather have them escalate a fix.
Click to expand...
Click to collapse
Same response from support. I wonder if anyone that is able to create a TWRP backup, and test if a clean reset fixes issue.

jhedfors said:
Same response from support. I wonder if anyone that is able to create a TWRP backup, and test if a clean reset fixes issue.
Click to expand...
Click to collapse
I made full wipe after the update, nothing has changed.

Problems with my Xiaomi Redmi 8A

Hello people of XDA Forum,
Since a couple of years I own a Xiaomi Redmi 8A, which I ordered brand new on AliExpress.
After a couple of failed attempts to install a Custom Rom on the device, I still have an unlocked bootloader
and a "offical" stock firmware on the smartphone installed. Sadly now occurs an other problem,
frequently the screen "freezes" when I want to use the touchscreen. Sometimes when I put the power-button
and pressing it another time the screen responsed to it. But not always, it's getting very frustating when
for example I play "Call of Duty Mobile". My question is that I want to know of the problem is software-
or hardware based? Hopefully you can help me out, thnx

Have you modified anything in your device recently? No? Then it's probably hardware issue.
Do you have any damage to your phone? Then it's even more likely to be hardware issue.

XDHx86 said:
Have you modified anything in your device recently? No? Then it's probably hardware issue.
Do you have any damage to your phone? Then it's even more likely to be hardware issue.
Click to expand...
Click to collapse
Thanks for the reply. Now I have this problem for a couple of weeks sadly... There is no visible damage on the
device, but I have dropped the smartphone a couple of times out my hand... So I have this problem and I thought
that a firmware upgrade might help me out, but the problem still remains.

TrippyBlade said:
Thanks for the reply. Now I have this problem for a couple of weeks sadly... There is no visible damage on the
device, but I have dropped the smartphone a couple of times out my hand... So I have this problem and I thought
that a firmware upgrade might help me out, but the problem still remains.
Click to expand...
Click to collapse
If you think the damage to your phone is significant enough for it to affect your screen then maybe you should send it for a checkup.
Although you can try using different ROM to test if it works since it's probably much cheaper to do so than fixing the screen.
But don't flash an OTA update, flash latest stock ROM manually or flash a custom ROM. That way the settings are reset, you can backup your data with TWRP.

XDHx86 said:
If you think the damage to your phone is significant enough for it to affect your screen then maybe you should send it for a checkup.
Although you can try using different ROM to test if it works since it's probably much cheaper to do so than fixing the screen.
But don't flash an OTA update, flash latest stock ROM manually or flash a custom ROM. That way the settings are reset, you can backup your data with TWRP.
Click to expand...
Click to collapse
Allright, thank you very much for the suggestion. Finally I managed to flash an older Fastboot ROM through
the "MI Flash Tool", which solved my touchscreen problems.