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 :-(
So, I have tried all methods posted here. I have not gotten a new sdcard, so that could be it, but if you sift through all these threads, many people have gotten root with the card that came from verizon. Also, would it help to wipe out my phone? Not exactly sure how to do it, but would it help? Also, I hear my phone connect with the usb sounds, but it seems like sometimes I get a quick 3 tones and it doesn't connect. Not sure what that means either.
If anyone can please help, I would appreciate it!
if your not sure if it connected right, open the device manager and see if it is appearing on there.
As far as i know wiping your phone probly won't really help much either.
rstandi said:
So, I have tried all methods posted here. I have not gotten a new sdcard, so that could be it, but if you sift through all these threads, many people have gotten root with the card that came from verizon. Also, would it help to wipe out my phone? Not exactly sure how to do it, but would it help? Also, I hear my phone connect with the usb sounds, but it seems like sometimes I get a quick 3 tones and it doesn't connect. Not sure what that means either.
If anyone can please help, I would appreciate it!
Click to expand...
Click to collapse
There are about 10 threads on adb shell/rooting difficulties already. Why didn't you just bump an older one?
When you connect the usb to the phone what mounting setting did you select? It needs to be on charge only.
So, I have tried all methods posted here.
Click to expand...
Click to collapse
I have rooted two phones using various methods. The Easiest method? Who knows, but this is what I did, I in NO way take credit for this method. This is a culmination of various methods I found on various forums. Thank you to everyone here and on androidforums. Give it a shot.
1. Uninstall HTC sync and PDAnet (If installed)
2. Install drivers as specified for re-flash recovery from revoked team (HTML file has instruction in recovery zip - unrevoked.com/recovery/android-usb-driver.zip
3. Restart PC
4. Install PDANet - junefabrics.com/android/
5. Make sure to complete all steps for PDANet
6. Make default connection on phone, "Disk Drive" AND Turn on "USB Debugging"
7. Shut down the phone
8. Unclick the card
9. Volume down + Power into bootloader
10. Run adb shell in cmd prompt as loop(loop.bat)
11. Start recovery and wait .5 - 1 second after you hear the disconnect sound to click in your card.
12. You should see error device not found change to the other message IF LUCKY.
13. IF NOT,
- Let loop.bat continue to run
- Pull battery, unclick SD card
- Vol down + Power
- Recovery
- Listen for 2 tones (Count aloud..it helps)..
Quick - Insert card right after/during second (Change timing up slightly between tries)
Keep trying, my second root didn't take as long as my first but was easier. I think the unrevoked bootloader drivers with the PDANet usb drivers really make this easier. The other great thing is after you get root, you are set up to do the flash immediately using this method. Its just one more method that worked for me, hope this method helps you succeed. Good luck.
can anyone definitively explain to me which type of usb connection (e.g. "charge only", "disk drive") is necessary to get into shell and why? I have looked at what the various threads have to say about this. In fact that's the problem--I have found contradicting opinions posted on this matter. In my admittedly inexperienced mind, it seems like I should be fine either way, as long as adb recognizes my device.
davisbs999 said:
can anyone definitively explain to me which type of usb connection (e.g. "charge only", "disk drive") is necessary to get into shell and why? I have looked at what the various threads have to say about this. In fact that's the problem--I have found contradicting opinions posted on this matter. In my admittedly inexperienced mind, it seems like I should be fine either way, as long as adb recognizes my device.
Click to expand...
Click to collapse
I used disk drive the first time, and can not recall what I used on my second device. I see that it is contradicting throughout. I really do not think it even makes a difference because you are doing a battery pull and it never reaches that step on the phone. The important thing in my opinion are the drivers and timing.
Studmf said:
I used disk drive the first time, and can not recall what I used on my second device. I see that it is contradicting throughout. I really do not think it even makes a difference because you are doing a battery pull and it never reaches that step on the phone. The important thing in my opinion are the drivers and timing.
Click to expand...
Click to collapse
I rooted my cousin's Droid Incredible and I had Disk Drive enabled. I just want to say THANK YOU Studmf!!!!! I was stuck because I had HTC Sync installed and was stuck forever trying to root the Incredible. The instructions that I WAS following left that detail out.
Hi guys and girls.
New to XDA but not to Android.
I need some help big time as I'm totally stuck and I'm about to send my phone to "will it blend".
Long story short my memory card will not read when inside the phone all I get under phone storage is "unavailable" with mount being greyed out.
HTC DESIRE HD 2.3.3 (Not Rooted)
Things I have tried:
Factory reset soft/hard both through phone and through power + vol down.
Tried two different mem cards both coming up in storage as "unavailable" the general fix seems to be formatting in fat32 on desktop pc I have done that for both cards (which are both readable on PC) and have even tried formatting through command prompt still no luck.
read alot in ADB/fastboot as it is something I'm abit unfamiliar with saw that users where able to restore sd card function by installing adb then running command prompt: "fastboot oem enableqxdm 0" I get a message saying it was successful I reboot guess what...same problem. One thing I have noticed is if I type "adb shell" I get "Daemon started on port 5079". (I have enable debugging) followed by device not found. have tried two diff usb cables both work with my S2 on either media faceplate or backplate usb ports still no luck. Trust me on this one guys I have searched far and wide and I'm just about read to quit on this. I'm at a dead end any advice would be awesome.
I've tried to resolve the adb method by installing various drivers (running windows 7pro 64bit) the issue I seem to get is that windows doesnt like the drivers Im trying to assign so im forced into have to update them manually through "let me choose a driver from location" blah blah blah...
There is a system update available which may possibly fix my issue however suprise suprise I can't download the update without having an sd card. I have even tried downloading a HTC sdmount widget whether Im downloading the wrong one I dont know? I have got HTC sync installed as others claimed this helped windows detect the correct drivers but then technically speaking its not an ADB interface?? just like to point out that both of the sd cards work flawlessly in my s2. anyone who can help me will get paypal'd a beer!
Thanks
Seb.
OK, I had same problem with my Desire S. I'm running Win7 64bit as well. I un-installed HTC sync, including the drivers. Control Panel>Programs & Features. I then download the latest HTC sync. Went back to Programs & Features and un-installed HTC sync but, left the drivers. Rebooted PC and Win7 picked up Desire S.
Hope this helps
How old is your phone? Depending in which country you are in you may still be under warranty.
Try cleaning the contacts?
Not too sure if you can mount the sd card on phones that are not rooted, or if you have the hboot option/recovery. Fastboot turned off, phone off, then press and hold the down volume button and while pressing it down, press the power button.
If you are not sure what you are looking at do not play around with those options, and it may not work. Not sure if you get those options if you are not rooted.
Do not root your phone, it is improbable it will help, and chances are, it may cause more problems than help.
First option, find out about the warranty.
Edit: just noticed you can boot into hboot. Not too sure if you have the option for recovery and even less if you get the option to mount sd card through there.
2nd edit: I'm not responsible for bad advice. I still haven't had my second cup of coffee
3rd edit: to find out if the adb is working properly and you got the htc sync installed type in whatever the command is in adb to see if it detects your device.
However, try cleaning the contacts and find out about the warranty.
Sent from a dream.
eloquence intshe
Thanks for the reply.
Hehe dont worry you can have some of mine I'm on the 4th cup thats how stressed I am getting with this. Just trying Taysider's method for trying to re-enable the sd card function. I have disabled fastboot using your method so is there a way of mouting sd in recovery? because Im sure I may have tried that already and all I got was an icon of a phone with a red exclamation mark infront of it?
thanks
3rd edit: to find out if the adb is working properly and you got the htc sync installed type in whatever the command is in adb to see if it detects your device.
However, try cleaning the contacts and find out about the warranty.
Sent from a dream.[/QUOTE]
How do I clean the contacts on the sd reader? it doesnt look very accessible unless I remove part of the housing? also what command prompt do you recommend I try first? like I said I tried "adb shell" and got no device found I'll update in a second as soon as I have tried this I have just uninstalled htc sync now all I need to do is assign driver to "android 1.0" in device manager then I'll take it for a spin.
Thanks dude
Ironman MarkV said:
Thanks for the reply.
Hehe dont worry you can have some of mine I'm on the 4th cup thats how stressed I am getting with this. Just trying Taysider's method for trying to re-enable the sd card function. I have disabled fastboot using your method so is there a way of mouting sd in recovery? because Im sure I may have tried that already and all I got was an icon of a phone with a red exclamation mark infront of it?
thanks
Click to expand...
Click to collapse
Re-read my previous post, there' another edit.
Thing is, Im not too sure what options you get nor l, well, anything related to non rooted phones. Do not root your phone as I mentioned previously. Mainly because first you ought to find out if you are still under warranty. If you are, send it to them.
Exclamation mark? Do a search, there were a few threads talking about that a few weeks back, but I believe it was about something else entirely, people effen up their phones trying to root.
From here on, the best advice I can give you is step back, take a break, continue later. There is probably too much info in your head right now.
1- see if adb can detect your phone.
2- try cleaning the contacts, do a search cause I can't remember if the cleaning of contacts was also for the sd card or only the wifi antenna.
3- Check your warranty, I can't stress this enough.
4- Coffee is kicking in
5- Check if you can detect the sd card through recovery. My assumption is that recovery works something like safe mode in windows, only an assumption.
6- Wait till someone more knowledgable than myself joins in. Chances are it would either be darunion, gleviatan or some chap who's nick I cant remember but starts with an M.
@guyinthecorner: you can skip this one - and I'm still waiting for that flashable zip.
Sent from a dream.
Teichopsia said:
Re-read my previous post, there' another edit.
Thing is, Im not too sure what options you get nor l, well, anything related to non rooted phones. Do not root your phone as I mentioned previously. Mainly because first you ought to find out if you are still under warranty. If you are, send it to them.
Exclamation mark? Do a search, there were a few threads talking about that a few weeks back, but I believe it was about something else entirely, people effen up their phones trying to root.
From here on, the best advice I can give you is step back, take a break, continue later. There is probably too much info in your head right now.
1- see if adb can detect your phone.
2- try cleaning the contacts, do a search cause I can't remember if the cleaning of contacts was also for the sd card or only the wifi antenna.
3- Check your warranty, I can't stress this enough.
4- Coffee is kicking in
5- Check if you can detect the sd card through recovery. My assumption is that recovery works something like safe mode in windows, only an assumption.
6- Wait till someone more knowledgable than myself joins in. Chances are it would either be darunion, gleviatan or some chap who's nick I cant remember but starts with an M.
@guyinthecorner: you can skip this one - and I'm still waiting for that flashable zip.
Sent from a dream.
Click to expand...
Click to collapse
Lol, already saw your username and was like 'Yup, problem solved ;-)'
Flashable zip is being a pain in the rear, should have it soon (reading a crap-ton of tutorials to help me)
Sent from my Desire HD using Swype beta for Android!
Challenge / Background:
I recently rooted my Sprint HTC 10 to Viper v10 3.5.0 with SuperUser v2.74-2. This was my second root and I had a couple hiccups along the way that required me to re-flash during the process to make sure I did it right....ended up being something different. Everything works though as expected with the exception that I noticed tonight that my Windows 7 laptop does not recognize my phone. After multiple tries trying to update drivers on my laptop (can see it in device manager, but error) and that type of thing, I gave up and tried to work the problem from my phone. But, the only solution I could find online was regarding ensuring that the USB tethering option was on. Additionally, when booted to TWRP v3.0.2-6 I also was unable to mount my phone as a USB storage device.
Temporary work around:
I will still be looking for a permanent solution, and if anyone has ideas please let me know, but if others have this problem, an option that worked for me was utilizing "USB Tethering" in lieu of "(USB) File Transfers". In order to do this, I downloaded the below app from Google Play and followed the instructions. Its a little slow moving from folder to folder, but works as a temporary solution for the moment, or until I try to reflash again in case I mistakenly selected the wrong option in Viper.
I utilized the MTP-Alternative USB Drive application by ClearEvo located in the store for free.
Hope this helps.
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.