Related
My activesync just stopped to work since some day, it is just keeping connecting, but never succeed. I've tried to reinstall activesync several times but no luck. Now the version is 4.5, and my rom is a custom made one from the forum (xplode_7.00 6.10.00.WWE). I don't have a clue as it just suddenly stopped to work. Some thing that may be useful for troubleshooting:
1. when connected to pc (winxp), no device showed under " USB controller" in device manager, instead a "windows mobile based device #16" showed up under "Network adapter"
2. When just hooked, a connecting icon will show up at connectivity status(top of the screen) for about one second, then replaced to "two arrows with a cross ".
3. I have Rogers blocked my data service... could that be a reason? (seems not quite likely)
That's all what I could think about so far. I've looked through posts regarding similar issues but still could find a solution. I appreciate any input/insight.
----
Another question, does any one know how to have the youtube app working with wifi. It just showed " Error, Connection problem. Failed to initialize...."
Thanks a lot
your data service theoretically could be the issue, but since you said it worked before, and your device manager says #16, i guess, this will help you:
i don't know if you use the cradle with a pc or maybe a usb cable that is not permanently connected, but it seems, the driver is just installed many times now, so try the following to clean that up:
1. disconnect the cable/cradle
2. on the pc, right click "my computer" or "computer" (depending on whether you use xp or vista/7), and click 'properties'
3. go to the advanced system settings
4. click "environment variables"
5. make a new variable by clicking the upper "New" button
5.1 the name must be "DEVMGR_SHOW_NONPRESENT_DEVICES" without ""
5.2 the value must be "1" without ""
5.3 close all open windows with OK
6. restart the pc
7. start the device manager again, e.g. by right clicking "my computer" or computer and clicking "manage"
8. click "View" and then "Show hidden devices"
9. now you see a lot of new greyed out devices, all devices that were ever connected to the pc.
10. now you can start cleaning up:
10.1 go to "Universal Serial Bus controllers"
10.2 all the greyed out entries named "Unknown device", "USB Mass Storage device", "USB root hub" can be right-clicked and uninstalled, but just the greyed out ones!
10.3 go to the tree "Portable devices" and uninstall anything like BlueAngel, PocketPc and stuff like that.
10.4 go to the tree "mobile devices" and uninstall them all.
10.5 close the device manager
11. connect the cable and the device again.
12. since all the old drivers are uninstalled, it will start searching for new hardware and then connect the device again. if you are in fact using xp and the driver is not found disconnect the device again, uninstall active sync, restart the pc and re-install it. it brings the driver and on the next connect, the "new" hardware will be found.
ok, it seems like a lot of work, but it will seriously speed up all your usb connections, because all the dead links and drivers are cleaned up. if, for any reason, this was not the solution to your problem, at least enjoy the faster usb, you're welome
in that very case, you should use pimbackup from my thread in my signature (the "read first" one) and make a backup of all your pim data and perform a hard reset, that could also help.
btw. when you are in my thread already, there is also a youtube app there, that works extremely well with wi-fi and is a lot faster than the official one.
Thank you very much for this detailed procedure. I've tried it through, but still no luck. I'll see if I could find solution before "a necessary hard reset". One odd thing is I didn't see any "blueangel related item" under Portable devices, and I even don't have "mobile devices" tree..
I also downloaded youtubeplay. I will give it a try later. Also, isn't myphone usable through wifi either?
Thanks a lot for the help.
myphone should also work fine via wi-fi, maybe you should check your connection status there as well, i could imagine one situation, where no change at all could also screw that up. if you have an incredibly bad connection or your dhcp encountered a conflict, you might get stuck with an APIPA ip address, something like 169.254.x.x, your wi-fi shows up as connected but there will be no data transfer. in that case, assign a manual ip address or check on your access point or router.
if all other programs work, except for those two, you should think about a hard reset. by the way, if you are a person, that does not like hard resets because of all the programs you need to install and set up again afterwards, you should think about trying spb backup, which can create full backups of your system state before a hard reset. it's pretty neat and due to the fact, that you make a hard reset afterwards, you can use the free trial version.
little warning though:
- never plan on restoring a backup on another rom! this app backs up your complete system, including registry and stuff, and that can vary from rom to rom, after you restored a backup from another rom or device, your device will behave odd, if it will even start, and you probably have to re-flash the rom.
- if you are hard resetting because you screwed up something software or registry related, don't hard reset and restore the backup, the screw-up will be restored as well only make backups of running systems and for last minute backups of pim data, use pim backup.
oh, and with the "portable devices" tree, my bluangel probably shows up there, alongside with card readers and usb flash drives, because i am using windows 7. the mobile devices tree might also have a different name, something like windows ce devices or something like that, basicly you were to delete everything with a pda icon at least, especially that "windows mobile based device #16" and its 15 possible predecessors, so that windows could search the device again.
in a very last attempt to determine whether it is the device to blame or the pc/active sync, you could also try connecting it to another pc. if it is actually just your pc, maybe you don't have to make a hard reset after all. you know, if you get that wi-fi issue out of the way...
Chef_Tony said:
myphone should also work fine via wi-fi, maybe you should check your connection status there as well, i could imagine one situation, where no change at all could also screw that up. if you have an incredibly bad connection or your dhcp encountered a conflict, you might get stuck with an APIPA ip address, something like 169.254.x.x, your wi-fi shows up as connected but there will be no data transfer. in that case, assign a manual ip address or check on your access point or router.
if all other programs work, except for those two, you should think about a hard reset. by the way, if you are a person, that does not like hard resets because of all the programs you need to install and set up again afterwards, you should think about trying spb backup, which can create full backups of your system state before a hard reset. it's pretty neat and due to the fact, that you make a hard reset afterwards, you can use the free trial version.
little warning though:
- never plan on restoring a backup on another rom! this app backs up your complete system, including registry and stuff, and that can vary from rom to rom, after you restored a backup from another rom or device, your device will behave odd, if it will even start, and you probably have to re-flash the rom.
- if you are hard resetting because you screwed up something software or registry related, don't hard reset and restore the backup, the screw-up will be restored as well only make backups of running systems and for last minute backups of pim data, use pim backup.
oh, and with the "portable devices" tree, my bluangel probably shows up there, alongside with card readers and usb flash drives, because i am using windows 7. the mobile devices tree might also have a different name, something like windows ce devices or something like that, basicly you were to delete everything with a pda icon at least, especially that "windows mobile based device #16" and its 15 possible predecessors, so that windows could search the device again.
in a very last attempt to determine whether it is the device to blame or the pc/active sync, you could also try connecting it to another pc. if it is actually just your pc, maybe you don't have to make a hard reset after all. you know, if you get that wi-fi issue out of the way...
Click to expand...
Click to collapse
This is why history is important... you learn from it
Here is an extract from xplode's thread (first post)
R7 Release (this does not mean that this is windows mobile 7)
-------------------------------------------------------------------------------
Rapidshare: R7 ROM
Ziddu: R7 ROM
[highlight]Known bug with it , does not want to sync ... (or maybe it is my pc error i will look into this, but now it is 4 AM and i am going to bed[/highlight]
Click to expand...
Click to collapse
I have a simpler solution.... get PIM backup to save any important things out of your phone, flash a newer rom . Remember, xplode's latest version was 7.1 and not 7... and that is for a very special reason... bugs (activesync being one of them). More than likely, you will have to either HR or change roms. I would personally go with the latter since I am gonna have to reinstall everything anyways.
BTW, Chef.... awesome guide!
yeah, i remembered that xplode had some sync issues with some past roms, but i always thought that it if it hit you, sync wouldn't work at all but it seems to have worked before, which is why i didn't blame the rom first. that usb driver issue is trouble though, it could have been the solution this time, since it isn't i will use this to link on, the next time it might be
but i agree, in this case, changing the rom should clear all issues.
I finally fixed the problem in a way like what egzthunder1 suggested... And now I am trying out wm6.5. Here is what I've been through
1. Spb backuped my PIMs. Restored to my previous backups ( which I am sure worked well with Activesync )... Sync still not working.
2. Hard reset, sync works. Restored to any previous backups... sync not working
So I decided to flash a rom, now that I have to hard reset it anyway. So, I HRed the phone, restored PIM, and synced with my PC and MS' myphone account, downloaded a new WM6.5 rom, and flashed the phone...
bling..everything works now
I don't think it's old ROM's fault for not ActiveSync, it must be something I did to the system which is weirdly not restore-able. Anyway, starting over is always an effective solution, just takes a lot of time to get everything back to work again.
Thank you guys for great guides and insights.
java218 said:
I finally fixed the problem in a way like what egzthunder1 suggested... And now I am trying out wm6.5. Here is what I've been through
1. Spb backuped my PIMs. Restored to my previous backups ( which I am sure worked well with Activesync )... Sync still not working.
2. Hard reset, sync works. Restored to any previous backups... sync not working
So I decided to flash a rom, now that I have to hard reset it anyway. So, I HRed the phone, restored PIM, and synced with my PC and MS' myphone account, downloaded a new WM6.5 rom, and flashed the phone...
bling..everything works now
I don't think it's old ROM's fault for not ActiveSync, it must be something I did to the system which is weirdly not restore-able. Anyway, starting over is always an effective solution, just takes a lot of time to get everything back to work again.
Thank you guys for great guides and insights.
Click to expand...
Click to collapse
There are things that get backed up with 3rd party software (such as Sprite Backup), which will mess things up in the device. It is usually recommended not to use these softwares to back your things up. Instead, you should always try to either use AS, or try PIM Backup, which for some reason doesn't mess things up.
Glad it worked out
same issue with ELF0 100 i can't figure out :-(
Tried to post this in the developers forum in the correct thread but I'm restricted - sorry mods but if you could move this post, that would be ace?
I've tried following the instructions for using the r2: Superboot process to root my phone, but having trouble with it.
I've installed the drivers that came in the zip - with the phone switched on as normal, Windows recognises it no problem, as does ADB. When I put the phone into the bootloader, Windows doesn't recognise it - showing in device manager as "Android 1.0" and making a funny beep as the USB is plugged in. Neither ADB or Fastboot recognise the phone as being attatched.
Just bought the phone today, sim free, in the UK, so possibly a different hardware or software version to those who've got it working?
When running normally, "About Phone" shows as Android version 4.0.1, Kernel 3.0.1-ge2433f2 [email protected] #1 and Build number ITL41D.
In the bootloader it shows Fastboot Mode, Product Name - tuna, Varient - magura, HW Version 9, Bootloader Version - PRIMEKJ10, Signing - production, Lock State - locked.
Anyone got any ideas where to go from here?
Thanks
Make sure you turn on ADB Debugging from the settings menu and plug it into your pc.
Then run:
adb devices
See if its there. If so, continue
You need to force the drivers to install in fastboot mode first. Download the 'drivers' files from *THIS* forum and try them it worked for me (make sure you are in fastboot mode when you install them). You will also need to unlock the bootloader first which will wipe your phone including sdcard so make sure you have any files you need backed up first.
Mark.
Ah, fella, you're a superstar!
Done it now, can tweak my phone just how I want it now.
Thanks so much for your help
mskip said:
You will also need to unlock the bootloader first which will wipe your phone including sdcard so make sure you have any files you need backed up first.
Mark.
Click to expand...
Click to collapse
I have been assuming that 'wipe your phone' means wipe it of anything the user has put on it, but that the OS remains; is that correct?
Yeh, it resets it to the same state as when you first get the phone, wiping any personal data and any changes you've made to the system
Have to say I'm impressed though, it remembered by Wifi password and downloaded all my apps again without me doing anything! I'm liking ICS so far!
scooby359 said:
Yeh, it resets it to the same state as when you first get the phone, wiping any personal data and any changes you've made to the system
Have to say I'm impressed though, it remembered by Wifi password and downloaded all my apps again without me doing anything! I'm liking ICS so far!
Click to expand...
Click to collapse
The Wifi password and app restoration is all in the cloud just pointing that out lol
scooby359 said:
Yeh, it resets it to the same state as when you first get the phone, wiping any personal data and any changes you've made to the system
Have to say I'm impressed though, it remembered by Wifi password and downloaded all my apps again without me doing anything! I'm liking ICS so far!
Click to expand...
Click to collapse
Your passwords and all your list of apps from the market are stored under your google account so when you sign back in on a new phone (or wiped one) and synch with your phone all your market apps under that account are re-downloaded and certain information is restored.
Mark.
I don't remember that happening on my old Desire.. that just something I've missed or new to ICS?
I've noticed ICS brings up my bookmarks from Chrome on my PC, that's deffinately a new trick!
scooby359 said:
I don't remember that happening on my old Desire.. that just something I've missed or new to ICS?
I've noticed ICS brings up my bookmarks from Chrome on my PC, that's deffinately a new trick!
Click to expand...
Click to collapse
Could be you didn't enable personal data backup, or Sense doesn't do that (my guess)
And the Chrome bookmark sync is one of the things I'm definitely looking forward to with ICS I know I can do it with some apps right now but having features be native is always nice
Hi,
I am having a very strange problem. I have my HD7 unlocked w/Chevron and am able to load apps BUT cannot get either of the above mentioned apps installed. It just gives back error message saying somethign to the nature of make sure phone is connected OR that the phone is unlocked.
Now i know that my phone is connected, zune is running and i can install any other xap without any problems. Any ideas?
Seems your device is interop-locked bro...
Sent from my Custromized HD7 using XDA Windows Phone 7 App
Try to install those apps on another PC, it hepls in my case. I think this is happening becouse of cluttered registry (on PC ofcourse)
Disclaimer: I am extremely illiterate when it comes to Android terminology, so you will most likely have to talk to me like I'm a child. I will try to explain my problems as best as I can, and will of course answer any questions. I also might over-explain, so I apologize for any length/redundancy issues.
Phone: XPERIA Play R800at, Android 2.3.3, Rooted with su and rom manager
My previous Play's touch screen stopped working, so the warranty granted me this new one. It's only two or three weeks old. The first problem I noticed was that I tried and could not delete anything off of my SD card. I tried formatting it a number of times, both in-phone (In Settings, as well as ES File Manager) and on Windows (both default formatter and a specific SD card formatter), but it would always revert back to what it's previous state would be. After researching a bit, I concluded it's probably faulty or failing, so I've ordered a new one that should get here within the week.
The second problem rose out of the first, I'm sure: My computer now doesn't recognize the sd card anymore. In SMC or MTP mode, it will not pop up on my computer and could not be recognized in PC Companion. On phone, the usual options you get in the notification bar (*dis*connect phone, etc.) do not show up. When connecting, the MTP USB Device driver attempts to install, but never succeeds. This is with USB debugging off and on, and every permutation I could think of.
Now, the most recent problem has been that the Home button doesn't work and there is no lock screen. Using the Terminal Emulator, I've attempted the popular fix (su -> echo -n ON > /efs/imei/keystr -> sync -> reboot) but I get the message /efs/imei/keystr directory nonexistent. I've factory reset my phone a number of times, reset settings, gone into recovery mode and reset things there, as well as caches, but all to no avail.
This could probably easily be remedied by just reflashing Android, or an older version or something, I'm sure, but given that my SD card is currently unreachable, I was wondering if anyone would know of a way I can fix these problems, or at least one of them. Thanks in advance.
If I've left anything out, please tell me and I will expound as best I can.
Other notes that might be of importance:
- It seems my *system* or whatever it would be is read-only, which seems like it could definitely be a problem. How do I fix this or do I even need to?
- I don't have the Setup Guide on my phone; I saw a thread that posited that this was a cause of the no lock screen problem.
Thanks again.
Driver install issue
Hello!
I'm not sure how to fix all of your problems. However, I have the same issue with my MTP drivers not installing when I connect the device. I've tried installing with various tools and the standard sony ericsson software. I believe I have the problem with the driver sorted out. I noticed that the drivers are, for some unknown reason, attempting to install to a TEMP folder. I would assume they are then being dumped from the TEMP folder after only a few seconds because when I install the driver it continues to ask me to install even when I click "finished."
You might try making sure the drivers are installing to the proper location if you haven't already. That might help with some of the issues.
On the same topic, do you know where the drivers are SUPPOSED to go in Windows XP? I'm fairly new to all of this stuff so I'm not sure exactly which folder in C:/WINDOWS the MTP driver for the Experia Play is supposed to go.
I hope this helps!
-Zot-
So I bought a new phone since my old Onyx (One+ X) died (cracked screen and charging port is getting iffy). And finally I decided on this one, a cheap Chinese docomo branded one off Ebay.
I was so exited when it arrived, the UPS truck was at my gate when I got home that day, ready to leave, but the driver was nice enough to wait and give me my package then and there. Pheew.
Well, now to my, bootloader unlocking, recovery flashing, after market os installation and rooting story...
Bootloader:
The phone was supposed to be unlocked, and I guess that only meant SIM unlocked, because the service menu read "Bootloader unlock allowed: no". Damn.
A few Duckduckgo searches later, turned up I needed the "S!Unlock tool" which I found a copy off online, but username/password fields needed to be filled in, and I think I found a pirated s/n which didn't seem to work, (might have if I had tried harder).
But since it was just over £22 at https://networkunlocking.com/ I thought I could spare that on the off chance it worked. I was very surprised when it finally did, truth, I needed a few tries. And it actually did turn that service menu's pesky "no" to a thumbs-up "yes". Yay!
So now, pulling the cable, holding "volume up" and inserting cable for that blue light goodness, and running the "flashtool.exe -i 0x???? oem unlock bootloader 0x????????????" comand.
Not so fast, that doesnät work with newer flashtool versions...
Finding the old one from my Xperia Arc days and runnning it again, Yay!
(Wish I had read ahead and done that temporary root trick to rip my DRM codes off my phone first. But I don't plan to revert to stock, and I gather (might be wrong) that the DRM is only needed for stock roms, and not Lineage OS and such.)
Recovery (TWRP):
Now the problems start for real, getting into recovery was a **** and a half. Most guides for the phone says to push "volume up" multiple times during the boot-process. This turns out to be plain wrong. The actual button combo is holding "volume down" and "power" button together atleast until the screen goes blank after the unlocked bootloader warning.
Now, I wanted 17.1 on the phone and the recommended TWRp is 3.1.1 or something, and this works to install lineage fine, but don't forget to erase /data partition as I did. Stupid mistake that made wifi fail miserably, and probably a lot of other stuff, that I never tried before noticing my mistake.
However trying to get my own set of ringtones on the phone turned out to be another issue, going back into recovery when I noticed my ringtone.zip had failed. Obviously the media folder had moved since los 15.1,so no wonder right? Turns out it wasn't the only problem. TWRP 3.1.1 (or something) failed to unencrypt the root partition, so changing anything via recovery was a lie. fortunately the latest recovery, 3.5.2_9 did. So after installing that everything was rosy peaches.
Rooting:
SuperSU? forget it.
Magisk? yeah, but how? No really good step by step guide out there, except download from the github page, but what version?
A little trial and error, tried with the arm64 version and it turned out to be the right one. (Sometimes you just get it right on the first try...)
Renamed the apk to .zip put it on the phones memory, entered recovery and installed the zip, et voi effing la, Magisk root installed.
Root checker verifies root status, TitaniumBackup and RootExplorer works. Yes, my phone is playing ball.
Final notes:
This above looks simple right? In fact this was a two day process since the guides are surely lacking for this phone, a lot of trial and error, the greatesthurdle was getting into Recovery, until I found the right button combo I accidently managed to enter it once making me believe I had the right combo and something was wrong with the phone. 4 hours or so wasted trying different versions rebooting and flashing. Getting back my Viber messages turned out to be a problem to, TitaniumBackup got the messages back, but the db had references to my old images on my old phone, and probable pointed at the wrong directory so trying to send images either from gallery or take new photos crashed the app. Solution, backup the messages to my google account, uninstall and reinstall viber and restore from that backup. TitaniumBAckup is good but no magic bullet, it's a ***** that we have to rely on Google for backups though, I am allergic to the cloud, something about it makes my skin crawl.
Otherwise I like the phone, it says docomo on the back, something I can live with. The Chinese vendor even supplied one glass screen protector for the phone and a clear soft plastic case, in case I wanted some extra protection. I only wish there was a screen protector that had the same surface as the one that was on the phone in the box, that slightly opaque cloudy feel was so nice on my finger.
Can I recommend this phone? Nah, if noone writes a step by step guide that will cut down the time I spent on making this phone palpatable, I can't. But if you, like me, don't mind to tinker and don't want a phablet or spend way too much for the privilege to get a screen size you don't want, then sure. But why do we have to get them from China?
My trusty xz1 compact is slowly dieing on me and i am looking for a replacement how much did you pay for yours and is a really new or just refurbished ?
"Final notes:
This above looks simple right? In fact this was a two day process since the guides are surely lacking for this phone, a lot of trial and error, the greatesthurdle was getting into Recovery, until I found the right button combo I accidently managed to enter it once making me believe I had the right combo and something was wrong with the phone"
This Phone is in the mobile Sphere already ancient. Don't expect to get any help here or newer hot to guides.
my biggest problem is the fastboot recognition of my Windows. If this would work reliable i could better flash the phone but getting the right driver is a kind of roulette for this phone.
muhschaf said:
my biggest problem is the fastboot recognition of my Windows. If this would work reliable i could better flash the phone but getting the right driver is a kind of roulette for this phone.
Click to expand...
Click to collapse
Also had a non-connecting fastboot issue on Windows until I ran into this guide showing me it was not about a driver but an installation method:
How to install Sony Xperia Drivers Manually (Super Easy Guide)
Step-by-Step guidelines to install Sony Xperia Drivers Manually (this method can be used on Windows XP, Vista, Windows 7, Windows 8, 8.1 and Windows 10).
xperiausbdriver.com
4qx said:
Also had a non-connecting fastboot issue on Windows until I ran into this guide showing me it was not about a driver but an installation method:
How to install Sony Xperia Drivers Manually (Super Easy Guide)
Step-by-Step guidelines to install Sony Xperia Drivers Manually (this method can be used on Windows XP, Vista, Windows 7, Windows 8, 8.1 and Windows 10).
xperiausbdriver.com
Click to expand...
Click to collapse
Handy cannot boot now anyway so i would probably not able to recover anyway.
muhschaf said:
cannot boot now anyway so i would probably not able to recover anyway.
Click to expand...
Click to collapse
The phone completely refuses to boot?
Do you have recovery installed? If not, are you able to install it via fastboot on linux?
4qx said:
The phone completely refuses to boot?
Do you have recovery installed? If not, are you able to install it via fastboot on linux?
Click to expand...
Click to collapse
okay i will explain.
i had this common issue with this running out of internal space (13GB pictures i could not find, only 300MB left) and after looking into it i figured, that, due to my constant app installing and deinstalling, i had literrally thousends of little images (thumbnails, icons, you name it) that got not deintalled for whatever reason and clogged up my internal memory. So i made a Backup and decided to completly wipe and flash the newest lilac from Modpunk (18.1) and did a big Mistake here. i go into recovery and wiped EVERYTHING...without checking that recovery is untouched. then during the same session i installed the ROM and rebooted...so far all nice and dandy. Setting up the Phone, then get the newsest Gapps and then try to reboot into recovery to install them...well did i mentioned that i had wiped EVERYTHING? Well, there was no recovery anymore. Not my first rodeo i headbutt myself into the desk and spun up ADB/fastboot...only to run into the same problem i run everytime due to improper intalled driver i forgot already about. Longs story short: after some time handy refused to boot also into system.
Phone is now unbootable into any state, but Black screen fastboot over hardware buttons...
i COULD still try to make a blind fastboot flash after following the driver install instruction from above, but consider my lucky or clumsyness i will **** this up too and only waste time. and due to my current covid recovery i have not the energy nor the patient to diddle around with this sorry excuse of an absolute restrictive Phone and rather get me a S5 mini or something else that has no bootlock whatsoever and let you flash it from the very start.
i am plain running out of patient with sonys harassment.
/€: Also the constant "cannot get root" on a rooted phone is plain BS³. having permanent trouble to install adaway or use my sdcard proper is so friggin annoying that i now will search for a android version that got rid of this bull**** and will buy any phone that is suported by that ROM.
It is MY phone, and not Goolge nor the the phone company will dictade what i can or cannot install on it. i decide and i carry the risk, period. and the biggest security reason holds the phone anyway.
@muhschaf okay so it doesn't seem bricked. Pretty sure you just need to flash the recovery through fastboot and flash a ROM. Try that on Windows with the driver method; if that fails boot a Linux distro e.g. EndeavourOS, even from a USB without installing no adb/fastboot driver is necessary for Linux, it just works. You can do it.
4qx said:
@muhschaf okay so it doesn't seem bricked. Pretty sure you just need to flash the recovery through fastboot and flash a ROM. Try that on Windows with the driver method; if that fails boot a Linux distro e.g. EndeavourOS, even from a USB without installing no adb/fastboot driver is necessary for Linux, it just works. You can do it.
Click to expand...
Click to collapse
i known, the question is more "i really want that?" like i said i struggle with this phone ever since. and i realized yesterday the problem is not the phone itself, it's the bull**** of androids security architecture. Google seems to be very prone to make sure that they can shove any amount of advertisements down your throat. Given that they earn their money with ad network it doesn't surprise me.
i came to the conclusion that in reality i want to have a reliable way to install ad away on any given phone i own. i archive similar things on my desktop with Firefox and umatrix and ublock. And what can is say: Having Advertisment fee Internet is a bliss and i not care a bit about "but the free stuff" and i incrisingly fury about my inability to archive similar things on my phone i rely quite a bit.
@muhschaf I get it but you know what they say: good things require effort. But I find that once I set my Android up, I'm happy to have done it.
In regards to ads, you can actually install uBO on Android Firefox now, and many other addons also.
So i gave it a try again and the result was that it detects now a "?" under fastboot but ADB can't see anything failing sucsequently to flash recovery. i am also seemingly unable to get even into hardware fastboot anymore. But could be quite possible that the battery is already drained again. so i recharge it the night.
4qx: i was going away from uBO several years ago. Wonder that he has survived the drain after his "whitelist" decision, but it seems like.
Adaway block advertisement in apps and this is mainly the feature i wanted, see advertisment have gotten out of the browser itself into the Base/apps systems (Android, Windows) and therefore the Adblocker have to go with it. under windows i can control the System itself pretty easy and throughoutly with Powershell and package debloating scripts or regedit. under Android i haven't this option and have to rely on app like adaway. This shortcoming is pretty frustraing for an "Open Source" OS
After nearly a Year i stumble upon something windows related and now i have finally my xz1c back:
Windows USB Hubs of ANY kind (Monitor USB Hubs, Powers external USB Hubs, hell sometimes even the PCH, that is technical also a USB Hub), can and sometime WILL prevent proper lowlevel access to devices like...USB Headsets (Logitech Pro X) and Mobile Phones in fastboot mode (xz1c).
To circumvent this you have to connect the phone to a USB Port on the Back of your PC Motherboard DIRECTLY. every other Port can have an USB Hub in between that alters your write or readout and therefore failed the flashing.