Related
Hi all,
I've been flashing a lil' during the last day. Until then no problem BUT, from this morning, I can't reach the market any more. I've installed several 2.1 and even went back to MCR 3.2, but no way. The installation is ok, I've wiped all, even partitioned the SD (and performed a repair stuff). My account's syncing ok, but everytime I launch the market, I have a server error. 3G or WiFi, nothing.
Plesae help, I can't download anything...I'm lost.
I'm french and have and suscribed over Virgin.
Many many thanks in advance for your help guyz.
Same here. Flashed Chpoubs 4.2 Slide port yesterday, everything was working fine.
And since this morning I can open the market, see the 15 apps on the welcome page, but I can not search an app or check the updates (server connection error).
I tried restoring a Kimera 1.8 backup but to no avail I got the same connection error.
I am in France and my carrier is SFR. Hope my phone has not been "blacklisted" or something like that ?
Hey guys,
Do a factory reset from the settings menu and make sure you sync your Google account on first set up. I've had this issue before and this has resolved it.
I'm giving it a try, thx.
Anguished I am....
okdac said:
I'm giving it a try, thx.
Anguished I am....
Click to expand...
Click to collapse
Nope, didn't work, still the same error message...
I wiped again, waited until google sync was over, opened the market, accepted the rules, and then got the error message... i'm stuck.
Same for me. Can't access the market.
EDIT : seems we are not alone : http://www.google.com/support/forum/p/Android+Market/thread?tid=7d3b2db29b96d592&hl=en&start=80
Google account back on market...
DarkAdrien said:
Same for me. Can't access the market.
EDIT : seems we are not alone : http://www.google.com/support/forum/p/Android+Market/thread?tid=7d3b2db29b96d592&hl=en&start=80
Click to expand...
Click to collapse
Woooow, Google annoucement : It's back...
no one knows why it was off, no one knows why it's back...
But, everything is back now.
Strange, isn't it ?
Hello everyone.
I recently purchased ATT Samsung Galaxy S 2 and a week ago rooted it using ODIn and tools in the guide on this website. For some reason tonight I am not able to connect to WiFi. It worked just fine this evening and I havent messed around with anything that I know of.
The error I keep getting is:
"the process Tethering Manager (process com.tecace.tethering manager) has stopped unexpectedly. Please try again" Force Close.
Now I am kinda a noob with anything related to Android. My previous phones being all symbians (Nokia's)
SO need some help from everyone.
Thank you
Are you attempting to create a wifi hotspot from your phone, or just connect to an existing wifi network?
just connecting to regular WiFi - nothing fancy.
Anyways I solved the problem at 3 am in the morning last night by going back to the stock ROM by just resetting from the ATTGalaxyS2Unroot using ODIN.
The thing is it obviously reset my whole phone which I really did not want to do. So I am hoping to find out the reason for this problem so that it can be avoided the next time I root a phone
Hi all,
Just had my new S3 for a few days and loving it so far apart from 1 thing.
I updated the firmware the other day via Kies but now the MTP driver fails to install.
I've uninstalled Kies, drivers, downloaded it again and reinstalled but nothing. Cable is fine and its only happened since the update 2 days ago.
Any ideas as i cant connect the damn thing to my PC now to take pics off, put music on
Cheers
Anyone?
neo6776 said:
Hi all,
Just had my new S3 for a few days and loving it so far apart from 1 thing.
I updated the firmware the other day via Kies but now the MTP driver fails to install.
I've uninstalled Kies, drivers, downloaded it again and reinstalled but nothing. Cable is fine and its only happened since the update 2 days ago.
Any ideas as i cant connect the damn thing to my PC now to take pics off, put music on
Cheers
Click to expand...
Click to collapse
wiered
have you tried some other pc ??
I've had the same problems, and seem to have narrowed it down. I originally had work email on my phone and it caused my phone to not connect to the PC due to security policies. I removed the email and it started working again. However at some point it stopped working again. I had rooted my phone and so I thought maybe that had something to do with it. After trying everything, I found a thread that mentioned factory reset may help. I tried this and sure enough it came back. Until the next day. It stopped working again. I did a factory reset once more, and it started working again. This time I skipped google login (restore). I installed an app at a time and reset the phone. All working still, After a while I got the confidence to restore everything and so far, all working.
My best guess, is the google backups was backing up and restoring something that was causing the MTP driver to fail. It's definitely something on the phone that causes this problem (in my case at least). Since I went through a clean backup / restore cycle now, it doesn't seem to be happening.
Hope this helps!
try on another usb port,off/on usb debugging again,reboot phone ,troubleshoot connection error on kies ,then connect to try , make sure to use original data cable
pblagay said:
I've had the same problems, and seem to have narrowed it down. I originally had work email on my phone and it caused my phone to not connect to the PC due to security policies. I removed the email and it started working again. However at some point it stopped working again. I had rooted my phone and so I thought maybe that had something to do with it. After trying everything, I found a thread that mentioned factory reset may help. I tried this and sure enough it came back. Until the next day. It stopped working again. I did a factory reset once more, and it started working again. This time I skipped google login (restore). I installed an app at a time and reset the phone. All working still, After a while I got the confidence to restore everything and so far, all working.
My best guess, is the google backups was backing up and restoring something that was causing the MTP driver to fail. It's definitely something on the phone that causes this problem (in my case at least). Since I went through a clean backup / restore cycle now, it doesn't seem to be happening.
Hope this helps!
Click to expand...
Click to collapse
This workded for me!!!!! I had tried everything for 2 days but only this worked and I didnt loose root...
Hello XDA,
Here is the deal. Today, i see some google apps updates. They include: Telegram, AndroDumpper, and (i think) most importantly Busybox. I let google play update them and i leave the phone. When i come back, i see my phone was rebooting.
Phone turns on>Cyanogenmod Logo appears>Lock screen appears. I can unlock it. The message: "Trebuchet has stopped working" continuously pops up and there's nothing i can do until it finally goes back to Cyanogenmod Logo. I tried turning it off, going to recovery and clearing cache and dalvik.
I don't know if this has to do with busybox. I don't even know if it updated before the problem started. I would like a solution that doesn't involve a total wipe and reinstall of my rom. If i have to do it, i will do it; but it has been some time since i last did it, so i will have to search for everything again (how to do backups and installing new rom).
My phone is a Moto G XT1032. I don't know how can i search my cyanogenmod version without turning my phone on :/
Any help appreciated.
Thanks
Update: Now my phone doesn't force the soft restart. I can go to the settings. If i try to go to the main screen, the message keeps popping up saying that trebuchet has stopped working. Going to Settings>Applications also shows the message "Settings has stopped working"
Does xda exist now? Pls can I get badoo premium for free? Pls help
Deeni131 said:
Pls can I get badoo premium for free? Pls help
Click to expand...
Click to collapse
It exist hacked versions. GIYF ...
So I bought a new Poco F1 few days ago. And since I've been using it, I've been facing bugs.
So when I got the device it had Miui 9.6.14 installed on it. And I just wanted to unlock it and root it asap. As you know you have to wait 3 days to unlock it. But as soon as I put in the unlock request i.e by going to fastboot and on mi unlock it shows 99% complete then it says you have to wait for this much time.
As soon as I did that, I faced the first bug. That was related mobile network settings/usb tethering/*#*#4636#*#* code (engineering mode IDK). So when I clicked on usb tethering, turned off mobile data/wifi, or the phone lost signal, it rebooted, from boot splash (not boot logo). Maybe this was the ROM's way of preventing any big bugs why do I think that? I'll explain later. So after rebooting I could turn on/off usb tethering but not mobile data or wifi. I can turn them off as soon as the phone boots but if I do it later i.e. after unlocking the phone, it rebooted.
So this is one of the bugs that has been consistent, the one that never got away. Well sometimes it did went away but not for long. Like sometimes if I haven't turned off the internet in a long time or restarted the phone properly, the data turning on/off doesn't reboots the device, IF the device isn't connected in usb tethering. Like few days ago I discovered that usb debugging could fixed it, but that didn't lasted long either. Sometimes turning off usb tethering then mobile data very quickly afterwards worked, but didn't lasted long or only sometimes it would work.
So the advice I got earlier was that, just flash a new software. While I didn't technically flashed the new software, I flashed the similar software, deleting all user data & everything, but that didn't helped. As it seemed in the beginning, that bugs weren't there but they started appearing later on. Now IDK if I used a locked un-rooted device, these bugs wouldn't appear, not too sure about that.
And you maybe saying, well you didn't flashed the newer version of the rom, then that's the problem, Well IMO it isn't. Here's why - So when I flashed the same rom, the phone got locked cause I forgot to select the "clean all" option in MI flash instead of "clean all and lock". So I unlocked it again, flashed twrp and as you may know that when booting twrp for the first time it asks you two options, "allow system modifications" & "read only". And the last time I flashed it I chose the read only option. But this time it didn't asked me. Now do you understand? As I'm not an expert in this, the guy who gave me this solution said maybe the device tree wasn't cleared. So how does flashing a new version is gonna make a difference if all of the files don't get deleted? If it's not gonna start fresh? I also used the command "fastboot erase recovery" (as suggested by that fella), that didn't helped either, just an FYI.
So I decided to install other roms, thinking maybe that could help. It seemed like working in the beginning but soon it started to fall down. First OS I installed, Pixel Experience, didn't had such bugs earlier, but there was a little one. If I disconnected the phone while it was in usb tethering mode, it would reboot the same way it did with miui. If you turned usb-teth off first, it didn't rebooted. So I thought I could live with that. But later more bugs started to appear. The same thing, turn off the internet and the phone restarts.
Remember when I first said maybe it was OS's way of not having bigger bugs, So that happened this time. New bugs like when I try to get into an app's info, the settings would crash (stopped working). BTW you could getting into an app's info if you are able to find the said app, by going into storage, then to apps. Moreover sometimes when I'd try to open the camera it would just show blank, or very dark image of the environment, not moving though, and sometimes, it would just work.
Then I installed Lineage OS. Didn't find such bugs, but I'm pretty sure if I do all this usb tethering stuff in there as well, I'm gonna find these bugs.
Now you might be thinking that how am I installing all these roms, well that's cause of MultiROM. And if anyone here is gonna say well that's the problem. STOP! Stop right there. These bugs were present there before I even used MultiROM.
Some other bugs I'm facing RN in Miui -
Auto Rotate not working. If I want to go landscape, I'd have to open an app/game that opens in landscape and switch from there, cause it gets stuck, vice versa for portrait. And you can only view it in default position i.e. you can't rotate to other landscape position if you wanted.
Camera not working, showing "can't connect to camera" error.
When I play offline games while these bugs occur. When I connect the headphones, the audio also comes out of the speakers. After I restart the phone properly, that stops. (This bug was also present in earlier stages when MultiROM wasn't used)
When going into second space, I created a txt file in mixplorer and when I try to open it, the system reboots. And I just checked by installing a root checker in second space, it says not rooted, wow!
When going to default file manager and tapping on storage, it said "disconnected" and few seconds later saying something like "couldn't add error 10000". This used to happen before but not now, neither I use the default file manager anymore. Though if I'm too quick and unlock the phone, open a file manager or any app that uses storage, it would go blank. Don't know if the storage crashes or something else. But after a restart, it's fine.
One thing, after the phone restarts when these bugs happen, "Find My Device stopped working" or something similar always appear, I don't remember the exact message.
[*]There are somethings Gcam related but I don't think they're 100% bugs related. Cause I installed the latest version on Lineage OS and it works as far as I used it even features like Night Sight and Slo Motion. Now those errors could be related to older android versions or something else IDK. Things like camera lagging in picture mode not in video mode and some version just straight up not working even when they're supported by older android 8.1.
Now could it be a hardware problem, IDK as I said I'm not an expert. These other bugs could've appeared cause of MultiROM or me flashing a new firmware over older rom version in order to install PE, again IDK.
Fair warning : If you're just gonna come here and say, Oh! this all cause of MultiROM or cause you didn't installed newer miui, then don't waste your time, cause I'm not gonna read any arrogant answers. Neither if you say, try to do this or that. I'm not here for that either. Cause if I wanted to do hit and trial, I could've done it myself
But if you understand the situation and can provide expert help, then only please reply. So if you're willing to help & understand properly, and you want anything from me, like logs etc. just tell me how to do it, I'll provide. Or if you know some way to do proper fresh install, only if that can fix the bugs so that I don't have to deal with them anymore, I'm looking forward to your reply.