There is simply no play store. I've had my rooted Lg P500 for a while now and it was running CM9 fine, except allot of apps crashed and it was rather slow as well as no camera, so i returned it to my backup of Gingerbread (Stock). Everything was going well, and then i got bored of GB, so i re-flashed CM9 With GApps. I noticed that their was no play store however, even after re-flashing GApps which didn't really bother me at the time.
After doing this, i found that CM10 had been released, which allot of people said was allot more stable and the camera actually worked (even though its a bad camera, i still use apps which use the camera as a background, and it gets rather annoying with just black). I loved it for a while and then i realised that there was no play store (and possibly other android apps which i don't really care about), however there was Gmail. I Flashed GApps (the correct one) and then i tried re flashing it. I did this about 20 times, just constantly re flashing everything and occasionally trying to restore back to GB (Which does have the play store) and then re-flashing CM10, BUT NOTHING WORKS :S!!!!
I then learned that this was a common problem amongst many people, but i cant seem to find an answer. I've tried setting up adb to push a playstore.apk file through, but for some reason, my computer decided it wouldn't recognize my device unless in mass storage mode, so when i do the adb thing i get this message;
"No device found"
I've also tried flashing ICS GApps, and that didn't work. I've tried everything and i cant find anything :'( .
I've also connected to wi-fi and my google account and left it for a while to check if it would update, but it still wont work :/
This is the thread where i got my ROM from and GApps download. (P.S if you read the downloads, i've tried using the mine GApps thing but that didnt work :/ )
http://forum.xda-developers.com/showthread.php?t=1811325&page=198
If anybody can help me ill be forever grateful
Cheers
Ok, i've been messing around with adb trying to push play store through and i'va managed to get my device recognised, however when i try to remount my phone i get "permission denied", yet i know my phone is rooted as when i type
adb shell
su
i get the $.
if it is possible to do this, can someone please assist me by doing it this way? well not assist, just get over this permission denied thing?:cyclops:
also, i wanted to edit my other post and say that this probably is in the wrong thread, and if it is can you please move it
thanks
Ive got adb to work except when attempting to remount, i get permission denied yet when i type
adb shell
su
it works :/
GoodPie said:
Ive got adb to work except when attempting to remount, i get permission denied yet when i type
adb shell
su
it works :/
Click to expand...
Click to collapse
simply try to get the apk file and install it as any app
Just download the apk from the first post and download it like any other app.
http://forum.xda-developers.com/showthread.php?t=1836057
Sent from my #Motofail... No further Plans coming...
tatperson said:
Just download the apk from the first post and download it like any other app.
http://forum.xda-developers.com/showthread.php?t=1836057
Sent from my #Motofail... No further Plans coming...
Click to expand...
Click to collapse
He is right. But, to ensure that the Play Store app is on your phone, search for it. Secondly, depending on the Rom, you might have to use TB or a related app to uninstall the apk store, since you won't be able to reinstall it if it IS in your Rom as a system app
GoodPie said:
Ok, i've been messing around with adb trying to push play store through and i'va managed to get my device recognised, however when i try to remount my phone i get "permission denied", yet i know my phone is rooted as when i type
adb shell
su
i get the $.
if it is possible to do this, can someone please assist me by doing it this way? well not assist, just get over this permission denied thing?:cyclops:
also, i wanted to edit my other post and say that this probably is in the wrong thread, and if it is can you please move it
thanks
Click to expand...
Click to collapse
Are you sure you're rooted? You should be seeing # if you're rooted, not $. You should also be seeing superuser or superSU pop up requesting permissions on your phone.
Open terminal emulator on your phone (assuming you have it, since you said you're running cm9) you should see $ here. Type su and hit enter - make sure superuser/superSU pops up and you grant permission. If you don't see superuser/superSU or get permission denied, you probably aren't rooted.
Sent from my One X
Related
So I just flashed Axura 2.2.5.9 and have kernel version 2.6.32.9 and well I wanted to use visual voicemail from Tmobile, but it won't let me install the newest version. So I tried to uninstall the older version that came with the rom and it won't let me.
The uninstall button is grayed out.
When I try to download the newer version from the market it says, "duplicate provider authority."
Thanks
vahdyx said:
So I just flashed Axura 2.2.5.9 and have kernel version 2.6.32.9 and well I wanted to use visual voicemail from Tmobile, but it won't let me install the newest version. So I tried to uninstall the older version that came with the rom and it won't let me.
The uninstall button is grayed out.
When I try to download the newer version from the market it says, "duplicate provider authority."
Thanks
Click to expand...
Click to collapse
easiest way is through Root Explorer, simply delete the .apk file from /system/app
or, if you have ADB on your PC, access your device through adb, and type the following commands:
adb shell
su
mount -o rw,remount /system
cd /system/app
rm nameof.apk
reboot
hope this helps
Well, using the app "Super manager" as my root explorer didn't work, so I ended up purchasing "SystemApp Remover" from the market and it worked well. As for the other method you described above was above my tech level and knowledge so I figured I'd find an easier method with keeping that as a last case scenario.
I got rid of Voicemail notifier, google voice and visual voicemail. Worked like a charm.
vahdyx said:
Well, it didn't work, but I ended up purchasing "SystemApp Remover" from the market and it worked well.
I got rid of Voicemail notifier, google voice and visual voicemail. Worked like a charm.
Click to expand...
Click to collapse
yes thats a good app....but the above methods undoubtedly work. did you even try them? if they didnt work, which method did you try, and what part of it didnt work? they are two of the original ways of removing system apps, theyve been around almost as long as root access for Android was discovered....good things to know and learn
if someone is trying to help you, dont just say the methods dont work.......either admit that you didnt even try, or post what went wrong, cause it couldve been something you did...because if another person who has this same problem sees this thread, they will automatically think these things dont work and will lose solutions to their problem.
^^^this goes for any situation, not just this one
Okay my apologies,
I went to the market and tried to find a root explorer but couldn't find a free one so I downloaded "Super Manager" app
I went into system file and long pressed on the file and tapped delete, the file just sat there. I did it again and it wouldn't delete. I restated my phone and it still didn't work.
So it wasn't necessarily the above method that didn't work it was the app that didn't work. I'll correct the post above as well.
I had a problem with system app remover before as I think it didnt just delete the apk but core processes linked to the apk I had a unbelievable flurry of fc maybe that was just my experience but root explorer is indisputably the easiest way to delete apk's cause you don't need anything other than the phone to do so
Yeah, ditto that @wills, I would advise to just freeze the process in titanium and go from there. I wouldn't remove it.
Don't blame me, blame my keyboard's autocorrection algorithm.
I deleted about 10 apps from system/app using root explorer. Not sure why a lot of the bloat was left in/inluded in the latest axura... I wish apps that can be grabbed for free from the market could be left out. ESPECIALLY the bloat from samsung.
I mean, why include samsung widgets when you removed touchwiz?
When using Honeycomb v04 sometimes the market will cease to work after a restart. This is due to a Google authentication issue. The normal fix to this would be to reformat the data partition. However; this will sometimes also erase root. The fix is to perform the following commands in a terminal emulator of your choice. Root is required.
Update2:I have added two lines of code to clear the dalvik-cache. This seems to help produce more positive results. I also have noticed that the script or (these commands) work, its just that for some reason the script has to sometimes be applied twice in a row for it to completely work. It might take a up to a minute for an app to install (rare cases).
Updated Script: http://www.multiupload.com/PSGAMTFBD0
Update: After messing around I have discovered that deleting the accounts database does not always work. Furthermore, it requires one to log back into the Google servers each and every single time.
A better way to go about fixing the market is deleting some data in the data partition. To fix the market do the following:
su
rm -r /data/data/com.android.email/
rm -r /data/data/com.android.providers.contacts/
rm -r /data/data/com.android.vending/
rm -r /data/data/com.google.android.gm
rm -r /data/data/com.google.android.syncadapters.contacts/
cd /data/dalvik-cache
rm -r *
reboot
I have made a script that automates this process. It is my suggestion that instead of restarting the device with the power button, run this script. That way the market fixes itself each reboot.
The script has to be run in a terminal emulator or over ssh (what I use). I do not know if it will work over ADB.
Script: http://www.multiupload.com/5IIM0UQXP1
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
The method below is old and might not work. Let me know the results you guys have so I can come up with a possible fix that lasts longer than these.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++.
+
su
rm /data/system/accounts.db
rm /data/system/accounts.db-journal
reboot
After typing these commands your system will reboot and your will have to login to your Google account on your device. This will not affect any apps or data on your system. It simply resets your Google credentials without requiring a factory reset.
If you have any questions let me know.
Dude. Awesome...this worked. I am on froyo, as well. Finally installed Angry Birds from the market!
Sent from my NOOKcolor
I'm having the same problem. It seems to be in conjunction with the error "Google Talk Authentication Failed".
I used your method and it worked the first time, but the market issue started again. When I tried this method a second time, it didn't work.
The other coincidence is that I was buying apps in both cases. The first time, the app was purchased. Now the second app (Beautiful Widgets), is stuck in "Authenticating".
Any ideas?
Yeah there is issues with the market. I am not sure why authentication fails. This fix only seems to work temporarily. Like I tried it 5 times and it worked but the market still breaks down even without a restart. I say try this method again, then reformat the cache partition. Remember, you have to reboot your system for this to take effect. The old method might work for you, it worked for me for a little while, but then I found this method which seems to work better. I dont think it has anything to do with you purchasing apps. Its more of a timing issue. Also what you might want to try is apply this fix, but then instead of using the market, use the web portal market.android.com and choose to install it on your nook. This might also help. Let me know how it goes.
mrschmitz said:
Dude. Awesome...this worked. I am on froyo, as well. Finally installed Angry Birds from the market!
Sent from my NOOKcolor
Click to expand...
Click to collapse
Glad to hear it worked for you.
The web market fails with this message:
There are no android phones associated with this account. Please sign in with a different account.
I do not wish to make another account and fail to see how that changes anything. When I made the account there was no question that referred to a phone model.
HELP!
market does not download
I tried the fixes so far .. maybe just keep trying?
market downloads somethings sometimes, but never Angry Birds ...
thanks
Robyn
Does angry birds even show on teh device? If not then the reason the market does not download angry birds is that it is due to the market not recognizing the device and therefore hiding certain apps from the device. This was most prevalent in the switch from 2.1 to 2.2. The fix was to replace the fingerprint in the build.prop file. If you really want angry birds that bad, I suggest you just download it from 4shared.com. It is less trouble than trying the fix the market seeing apps. BTW what version of android are you running? 2.2 or 3.0?
When you use the web portal the correct name for the device should be zoomlogic pd or something along those lines. Don't know why the web portal is not working.
The way I fixed it was the same way I used to fix a similar but different prob with droid 2. Simply create a 2nd gmail act add that to your gmail app and sync it. Voila! your first act is now recognized
Worked PERFECTLY A+ Man!
what command do i use to run the script?
when google talk authentication fail , maybe u can try this way.
uninstall one of apps u ever downloaded from market before, then immediately reinstall that app again and also install the apps u want to install.
it worked for me.
KingLo said:
The way I fixed it was the same way I used to fix a similar but different prob with droid 2. Simply create a 2nd gmail act add that to your gmail app and sync it. Voila! your first act is now recognized
Click to expand...
Click to collapse
Confirmed. Adding a second gmail account fixed this problem for me, too.
sj8570 said:
when google talk authentication fail , maybe u can try this way.
uninstall one of apps u ever downloaded from market before, then immediately reinstall that app again and also install the apps u want to install.
it worked for me.
Click to expand...
Click to collapse
Booya, this worked perfectly for me. Thanks!
Interesting...worked for a couple of dl's.
ovar said:
Booya, this worked perfectly for me. Thanks!
Click to expand...
Click to collapse
I was pleasantly surprised that uninstalling one app I had previously downloaded then immediately reinstalling it from the Market did actually enable me to start downloading and installing some other apps. I got 2-3 installed that had been failing moments earlier. But now it seems to have stopped again and uninstalling an app and retrying to install it is no longer working.
I'm back to the same thing I was getting earlier, which is that trying to download and install any app would result in the the little blurb saying "your item will be downloaded" but the download bar comes up only for a few seconds and then closes. It never completes the install and leaves the name of the app sitting in the list of 'My Apps' waiting to be selected and installed.
Anyone come up with a permanent fix for downloading from the Market?
-JTT
drewzee said:
what command do i use to run the script?
Click to expand...
Click to collapse
using terminal emulator:
type su
then type sh /location/to/script/. Replace location to script with the actual location on your device where the script is saved. for example: if its saved on the sd card then type sh /sdcard/script.
I just saw this on the XDA home page. Its a new super user app. As we know, the SU app on CM7 is a little buggy and doesnt always give super user permissions. Maybe this app will work better for us. Im going to be trying it out soon.
http://forum.xda-developers.com/showthread.php?t=1538053
UPDATE: So I installed it and tested all my root apps. Seems to work well. I will give it a day or two and see if I have any of the apps fail to get root permissions. If this works and fixes the SU problems we have, then this is a great thing for us CM7 users.
jsgraphicart said:
I just saw this on the XDA home page. Its a new super user app. As we know, the SU app on CM7 is a little buggy and doesnt always give super user permissions. Maybe this app will work better for us. Im going to be trying it out soon.
http://forum.xda-developers.com/showthread.php?t=1538053
UPDATE: So I installed it and tested all my root apps. Seems to work well. I will give it a day or two and see if I have any of the apps fail to get root permissions. If this works and fixes the SU problems we have, then this is a great thing for us CM7 users.
Click to expand...
Click to collapse
Since I am very familiar with ADB and the command line, I tore apart the apk in the linked thread OP to make sure I understood what was happening during the install. I moved the original su binary and Superuser.apk to my emmc (internal memory card), manually pushed the new files out to my phone, and then rebooted.
Once CM7DX2 came all the way up, I started doing some testing and noticed the the original Superuser APK was still showing up in my app drawer. If DOESN'T appear to be conflicting with the new SuperSU APK, but I'm not sure. I have had a few times of the SuperSU app stop responding and asking to either force close or wait. After hitting wait a few times, I ended up just FCing the app.
Once everything smoothed out, the SuperSU seems to have worked, bu, I was still receiving "not responding" messages from the SuperSU app when apps were asking for Root access.
I am going to also cross-post this to the linked OP thread and see if Chainfire wants more digging into this.
Also, as a side note, I think the reason the CM7DX2 Superuser APK was still appearing is that it MAY be installed as part of 2nd-init. I'm not 100% sure about this.
So, in conclusion, for CM7DX2, I think this needs more digging in to and I will offer to work with Chainfire to see what we can do.
Ciao!
Moon Shadow - NM said:
Since I am very familiar with ADB and the command line, I tore apart the apk in the linked thread OP to make sure I understood what was happening during the install. I moved the original su binary and Superuser.apk to my emmc (internal memory card), manually pushed the new files out to my phone, and then rebooted.
Once CM7DX2 came all the way up, I started doing some testing and noticed the the original Superuser APK was still showing up in my app drawer. If DOESN'T appear to be conflicting with the new SuperSU APK, but I'm not sure. I have had a few times of the SuperSU app stop responding and asking to either force close or wait. After hitting wait a few times, I ended up just FCing the app.
Once everything smoothed out, the SuperSU seems to have worked, bu, I was still receiving "not responding" messages from the SuperSU app when apps were asking for Root access.
I am going to also cross-post this to the linked OP thread and see if Chainfire wants more digging into this.
Also, as a side note, I think the reason the CM7DX2 Superuser APK was still appearing is that it MAY be installed as part of 2nd-init. I'm not 100% sure about this.
So, in conclusion, for CM7DX2, I think this needs more digging in to and I will offer to work with Chainfire to see what we can do.
Ciao!
Click to expand...
Click to collapse
Thanks Moon Shadow. The only time I had it hang on "asking for root access" is with Titanium Backup. I think that had to do with the SuperSU app freezing though when trying to get into the settings tab in the app. It just freezes up when selecting that and I had to go into application seetings and manually force stop the app. After that, everything worked fine. I think its just that settings tab for some reason.
The way I installed it was installed SuperSU from the market, then uninstalled the old Super User through the market. I then opened SuperSU and it asked to update so I did. After that, I went through all my root apps and the new SuperSU prompt popped up for all and I granted access. I too see the old SU in the app drawer. Opening that though shows that the only thing that its granting root access to is the new SuperSU app. It doesnt seem to be conflicting with anything so far.
Moon Shadow - NM said:
Since I am very familiar with ADB and the command line, I tore apart the apk in the linked thread OP to make sure I understood what was happening during the install. I moved the original su binary and Superuser.apk to my emmc (internal memory card), manually pushed the new files out to my phone, and then rebooted.
Once CM7DX2 came all the way up, I started doing some testing and noticed the the original Superuser APK was still showing up in my app drawer. If DOESN'T appear to be conflicting with the new SuperSU APK, but I'm not sure. I have had a few times of the SuperSU app stop responding and asking to either force close or wait. After hitting wait a few times, I ended up just FCing the app.
Once everything smoothed out, the SuperSU seems to have worked, bu, I was still receiving "not responding" messages from the SuperSU app when apps were asking for Root access.
I am going to also cross-post this to the linked OP thread and see if Chainfire wants more digging into this.
Also, as a side note, I think the reason the CM7DX2 Superuser APK was still appearing is that it MAY be installed as part of 2nd-init. I'm not 100% sure about this.
So, in conclusion, for CM7DX2, I think this needs more digging in to and I will offer to work with Chainfire to see what we can do.
Ciao!
Click to expand...
Click to collapse
Kind of random but Moon, you are a goddamn machine. The moment something great releases you take it apart and make it better. Good **** man, good ****.
Just including my experience...
SuperSU is working like a champ, but had major issues until I removed Superuser completely.
Here's how I installed:
- Install SuperSU from market
- Uninstall Superuser from settings > applications
- Launch SuperSU and allow it to update it's binary
- Delete superuser.apk from system/apps (use root explorer, es file explorer, terminal, etc...)
- Reboot
Since changing over to SuperSU, I haven't seen a single hang while an app is requesting su permissions.
xawen said:
Just including my experience...
SuperSU is working like a champ, but had major issues until I removed Superuser completely.
Here's how I installed:
- Install SuperSU from market
- Uninstall Superuser from settings > applications
- Launch SuperSU and allow it to update it's binary
- Delete superuser.apk from system/apps (use root explorer, es file explorer, terminal, etc...)
- Reboot
Since changing over to SuperSU, I haven't seen a single hang while an app is requesting su permissions.
Click to expand...
Click to collapse
Same here. This new SU seems to fix the issue we had with the old one. The only problem is that damn settings tab. It freezes the app.
Sent from my MB870 using Tapatalk
i find this relevant to my interest any one else test
Xb0i said:
i find this relevant to my interest any one else test
Click to expand...
Click to collapse
Follow xawen's directions and you'll be fine. It works like a charm.
Sent from my MB870 using xda premium
cant uninstall superuser from settings- applications. doesnt give the option
Xb0i said:
cant uninstall superuser from settings- applications. doesnt give the option
Click to expand...
Click to collapse
Did you go Settings> Applications> Manage Applications and hit the app? If you dont see that option, go into Titanium Backup (an app you have no excuse not having) and uninstall it. Then go into Root explorer and follow the above directions to totally remove it. Then reboot. It may seem like it isnt totally gone cause you may see the icon somewhere, but it likely is gone and a reboot is needed in order to confirm.
yea got the tiBu. but i tried force stopping and clearing data and uninstall never popped up. thought about removing in TiBu buts thats not what it said in the instructions.
Xb0i said:
yea got the tiBu. but i tried force stopping and clearing data and uninstall never popped up. thought about removing in TiBu buts thats not what it said in the instructions.
Click to expand...
Click to collapse
Its what I did. Its a bit of a deviation but it got the job done and thats what matters, ya know?
wow pretty bizzare i cant find superuser in TiBu! whats goin on lol
Xb0i said:
wow pretty bizzare i cant find superuser in TiBu! whats goin on lol
Click to expand...
Click to collapse
Did it disappear after you rebooted? If you have root explorer, go into system/app and see if SU is still gone. If so, you're in good shape.
to clarify
before i even started i backed up original superuser.apk to a folder on sdcard from root explorer, then
i downloaded supersu from market.
went to settings-app-manage apps- etc no choice to uninstall. force stopped- cleared data, still no uninstall option.
went into titanium backup to uninstall from there and superuser wasnt even listed in the apps! (ok weird)
only option left is to just delete from root explorer then continue continue to launch supersu, update binaries and reboot but im holding off.
Lowend was supersuper listed in titanium for u? y isnt it showing up in my list. i find it odd
Xb0i said:
to clarify
before i even started i backed up original superuser.apk to a folder on sdcard from root explorer, then
i downloaded supersu from market.
went to settings-app-manage apps- etc no choice to uninstall. force stopped- cleared data, still no uninstall option.
went into titanium backup to uninstall from there and superuser wasnt even listed in the apps! (ok weird)
only option left is to just delete from root explorer then continue continue to launch supersu, update binaries and reboot but im holding off.
Lowend was supersuper listed in titanium for u? y isnt it showing up in my list. i find it odd
Click to expand...
Click to collapse
I can't find superuser in TB either... it is kind of weird...
i believe u cant delete superuser from tibu cus u need superuser for root access so its like a paradox. i dunno y instructions were as someone showed cus it seems the only way to get this to work properly is delete from root explorer. but im gunna hold off till someone confirms this more legit
I don't understand why you're holding off...if SuperSU is active, go for the reboot and see if the old superuser app clears.
Sent from my MB870 using xda premium
id rather not have a headache if it messes something up.
this thread however gives some detail on supersu
looks like sum apps look for the presence of superuser.apk in data/app and possibly system/app.
a dummy file looks like it can resolve issues. ill switch when more testing is done on CM7dx2.
forum.xda-developers.com/showthread.php?t=1538053
Xb0i said:
id rather not have a headache if it messes something up.
this thread however gives some detail on supersu
looks like sum apps look for the presence of superuser.apk in data/app and possibly system/app.
a dummy file looks like it can resolve issues. ill switch when more testing is done on CM7dx2.
forum.xda-developers.com/showthread.php?t=1538053
Click to expand...
Click to collapse
It's odd that you guys don't see the uninstall option for it... Do you see it in Market (err...Google Play, stupid name)? That's another way to get the uninstall done. If it doesn't show up there, you should be able to use root explorer and delete it from /data/apps and /system/apps.
When we installed CM7, the instructions had us update Superuser from market. That would have installed it in /data/apps, so it just needs to be yanked from there. Uninstall via market, tibu, settings>apps or manual through root explorer should all do the same thing. Then you can delete the built in one from system.
Also, if for some reason the whole process breaks down on you...there's a flashable version of the original Superuser that will probably get you going again. I haven't tried it on CM7 though...
jsgraphicart said:
Same here. This new SU seems to fix the issue we had with the old one. The only problem is that damn settings tab. It freezes the app.
Click to expand...
Click to collapse
The most recent update (pushed yesterday) fixed this for me.
I'm in need of some kinda urgent help and advice regarding a phone i have just purchased for my mother.
I've bought her a cheap Daxian TD888 on the MTK6589 chipset and i'm afraid i have been a silly boy and not done my research before purchasing - I was under the impression that it came with the Play Store installed etc and sadly, it comes with a hard to use chinese ROM.
Mothers being mothers, mine isn't anywhere near tech/phone friendly and this is her first smartphone (upgrade from a 6 year old Nokia/symbian brick) so i was wanting to get her onto a nice and simple stock android 4.1 or 4.2 or even a CMxx that i can just help her along with.
After some very panic based searching today, i'm not seeing much that can help me... infact... nothing regarding this phone at all.
So... have I been a dumbass and bought her a lemon or is there anyone that can help me out with advice or pointers on how to get a normal android ROM on this thing?
I'm not massively experienced with rooting but have managed it a couple fo times in the past on my old Nexus One.
Any help would be greatly appreciated.
scottmeister said:
I'm in need of some kinda urgent help and advice regarding a phone i have just purchased for my mother.
I've bought her a cheap Daxian TD888 on the MTK6589 chipset and i'm afraid i have been a silly boy and not done my research before purchasing - I was under the impression that it came with the Play Store installed etc and sadly, it comes with a hard to use chinese ROM.
Mothers being mothers, mine isn't anywhere near tech/phone friendly and this is her first smartphone (upgrade from a 6 year old Nokia/symbian brick) so i was wanting to get her onto a nice and simple stock android 4.1 or 4.2 or even a CMxx that i can just help her along with.
After some very panic based searching today, i'm not seeing much that can help me... infact... nothing regarding this phone at all.
So... have I been a dumbass and bought her a lemon or is there anyone that can help me out with advice or pointers on how to get a normal android ROM on this thing?
I'm not massively experienced with rooting but have managed it a couple fo times in the past on my old Nexus One.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
I could probably help you get it rooted and that would allow you to install Play store on it as well as delete any chinese apps that sometimes come on the MT65XX devices if interested. As far as the rom goes, is there not an option in settings to change language to English? I have bought a few MediaTek devices directly from china, when I received the phone it had english on it already but when I reset the phones I would have to go into Settings and change chinese language back to english.
Motochopper should root your phone:
http://forum.xda-developers.com/showthread.php?t=2252248
One thing with these phones is that the android version is not always what is shown in Settings > About phone. Try using this tool from the first post of this thread:
http://forum.xda-developers.com/showthread.php?t=2160490&styleid=18
make sure you enable USB debugging on your phone first and it will help tell which version of android you are really running. If kernel say 2.6.xx you are on GB 2.3, if it is 3.0.xx then you are on ICS and if it says 3.4.xx then you are JB. I bought a MT6575 that said android version 4.0 in settings, it said gingerbread 2.2 on the box (I know 2.2 is Froyo), then on bottom of box it said Froyo 2.2!
Thanks Klown80 -
I'm just into work now so I'll have to hook it up to my own PC and root when i get home later... i'm just in full on panic mode over this (its a time sensitive issue as she's due to be in hospital for an extended period and i want to get this right for her before then)
Regarding the language settings in the current/stock rom, it has english US selected and while a lot of the language is in english, pretty much ALL popup dialogs are in chinese and the browser is unusable (all chinese text based) so... hence the panic.
I was (foolishly) thinking it would just be a simple enough flash to CM or stock android and hey presto - full english ROM.
I hate it when i don't do my homework first.
So... you recommend the root first, check exact android version number and go from there?
Even if it turns out to be an older 2.1/2.2/whatever version, i'd be happy enough to get something stock and full english based on there if its possible.
As she's never had a smart phone, it will all seem super smooth and flashy to her anyway.
I have now rooted (i think..) however, the superuser app comes up with an error upon opening -
superuser binary (su) must be updated
and i now i'm kinda stuck.
I have downloaded and tired various versions of the play store and while the at first allow me to enter google accounts details, it always crashes after that.
Every time i open the play store app, it just closes again.
Any suggestions on where i might be going wrong?
scottmeister said:
I have now rooted (i think..) however, the superuser app comes up with an error upon opening -
superuser binary (su) must be updated
and i now i'm kinda stuck.
I have downloaded and tired various versions of the play store and while the at first allow me to enter google accounts details, it always crashes after that.
Every time i open the play store app, it just closes again.
Any suggestions on where i might be going wrong?
Click to expand...
Click to collapse
Sounds like you need to update the binary then, if it allows you. If not then the root did not correctly root your device and we will have to go back a step and get that fixed first. As for Play Store, it usually takes more than just the Play.apk file to put Play Store on your device if it did not come with it stock. You also need (I am going off top of my head, I can give you exact names later) Google services framework.apk, Google login services.apk, Google Play services.apk. You need to have root to to this because you will need to move the vending.apk to /system folder and possibly change permissions on the apk before you install it. Once we can confirm root I can help you install a working Play Store if you like.
aphotaW are
Klown80 said:
Sounds like you need to update the binary then, if it allows you. If not then the root did not correctly root your device and we will have to go back a step and get that fixed first. As for Play Store, it usually takes more than just the Play.apk file to put Play Store on your device if it did not come with it stock. You also need (I am going off top of my head, I can give you exact names later) Google services framework.apk, Google login services.apk, Google Play services.apk. You need to have root to to this because you will need to move the vending.apk to /system folder and possibly change permissions on the apk before you install it. Once we can confirm root I can help you install a working Play Store if you like.
Click to expand...
Click to collapse
I've no idea how to update the binary so I guess i'm looking at a re-root.
I have had the usual issues of drivers not wanting to work (the Motochopper root process getting stuck at the daemon starting point) but I've manged to get the process to work twice so far.
(I've tried 4 different driver packages and they have all given the same results)
Could you possibly advise on how to update the binary file for superuser? I've just tried the root again and it skipped installing superuser as it was already found on the phone.. i haven't felt this noobllike in some time!
scottmeister said:
I've no idea how to update the binary so I guess i'm looking at a re-root.
I have had the usual issues of drivers not wanting to work (the Motochopper root process getting stuck at the daemon starting point) but I've manged to get the process to work twice so far.
(I've tried 4 different driver packages and they have all given the same results)
Could you possibly advise on how to update the binary file for superuser? I've just tried the root again and it skipped installing superuser as it was already found on the phone.. i haven't felt this noobllike in some time!
Click to expand...
Click to collapse
Sounds like the same prob with my.mtk device,
With motochopper i.get to update binary, but thats not possible.
You can try some of the roottools in my.acer811 thread.
I get many tipps from clown80.
scottmeister said:
I've no idea how to update the binary so I guess i'm looking at a re-root.
I have had the usual issues of drivers not wanting to work (the Motochopper root process getting stuck at the daemon starting point) but I've manged to get the process to work twice so far.
(I've tried 4 different driver packages and they have all given the same results)
Could you possibly advise on how to update the binary file for superuser? I've just tried the root again and it skipped installing superuser as it was already found on the phone.. i haven't felt this noobllike in some time!
Click to expand...
Click to collapse
Try uninstalliong Superuser or SuperSU and try again. Su binary should ask you if you want to update when you first open SuperSU, if you have Superuser, then you will need to open the app and go into settings to update binary.
meconte cutstones
Klown80 said:
Try uninstalliong Superuser or SuperSU and try again. Su binary should ask you if you want to update when you first open SuperSU, if you have Superuser, then you will need to open the app and go into settings to update binary.
Click to expand...
Click to collapse
It was aksing to try and update etc but its chashed every time - I was thinking that the root hadn't worked properly or something... anyway, I've uninstalled Superuser and reinstalled from a newer apk file (v3.2) i downloaded.
Its now running ok. Now that superuser is working... whats next?
scottmeister said:
It was aksing to try and update etc but its chashed every time - I was thinking that the root hadn't worked properly or something... anyway, I've uninstalled Superuser and reinstalled from a newer apk file (v3.2) i downloaded.
Its now running ok. Now that superuser is working... whats next?
Click to expand...
Click to collapse
Ok, is it just Superuser and not SuperSU correct? Can you go into settings in Superuser and towards the bottom there should be an option to update su binary. If it is SuperSU it will ask to update on its own when you open it. either way make sure it lets you update binary. Once binary is updated download and install any app that asks for root acces, so we can see if superuser request pops up.
Once we have confirmed root we can move onto installing Play Store. To do this you will need to be able to install a file explorer like ES file explorer so we can install the files we need for working Play Store.
Klown80 said:
Ok, is it just Superuser and not SuperSU correct? Can you go into settings in Superuser and towards the bottom there should be an option to update su binary. If it is SuperSU it will ask to update on its own when you open it. either way make sure it lets you update binary. Once binary is updated download and install any app that asks for root acces, so we can see if superuser request pops up.
Once we have confirmed root we can move onto installing Play Store. To do this you will need to be able to install a file explorer like ES file explorer so we can install the files we need for working Play Store.
Click to expand...
Click to collapse
In the superuser settings, there isn't anything apparent for trying to update the su binary.
the list reads as follows:
Security
Apps List
Log (on)
Notifications (on)
Backup apps/preferences
To anyone with this same device, this is method Scottmeister used to root his device. (Thanks Scott for being the tester! :good: )
http://forum.xda-developers.com/showpost.php?p=43163569&postcount=7&styleid=18
nuiryou food
HUGE thanks to Klown80 for the advice and patience!
For anyone else in a similar situation with an MTK6589 cheapo phone, and had issues with the Motochopper root method (the root getting stuck at 'daemon started successfully' etc etc.....
Klown80's chinese root tool works a treat. You will have a chinese superuser app that may be a little annoying (you might be able to swap it for SuperSU or something but I had issues doing that so i've kept the chinese one) but the root works perfectly and the instructions given by Klown80 in the linked thread are very easy to follow.
I still had some issues with getting google services installed so you may want to look for a play store installer workaround - I know there is a cheeky little chinese mod apk that can be used to get the play store working, but i can't post it here.
Should anyone come across this thread and know of a good, stock english rom that I might be able to use, please leave a comment!
Klown80 said:
To anyone with this same device, this is method Scottmeister used to root his device. (Thanks Scott for being the tester! :good: )
http://forum.xda-developers.com/showpost.php?p=43163569&postcount=7&styleid=18
Click to expand...
Click to collapse
Hello!
I have to a Daxian XY100 smart phone, Not a bad handy, but I try everything, and I can't root,
Can anybody help me?
petz765 said:
Hello!
I have to a Daxian XY100 smart phone, Not a bad handy, but I try everything, and I can't root,
Can anybody help me?
Click to expand...
Click to collapse
OK ! Nobody!:crying:
SRY for my bad englis
petz765 said:
OK ! Nobody!:crying:
SRY for my bad englis
Click to expand...
Click to collapse
I'm not a lucky guy!
Nobody answer to me.
Realy bad luck.
Sry for my bad englis.
I'm currently rooted and restoring my apps, however it seems like with each new version of Android the external SD gets trickier and trickier. A lot of apps these days use the round about method of having you choose the card to write to via the file manager, unfortunately not all apps do this and one of them looks to be the ever popular Tasker. am I missing the option or am I screwed and have to rewrite all my tasks to write to the internal storage?
another issue is with Secure Settings mainly used in conjunction with Tasker... when I start it up it fails to recognize su and never prompts me via SuperSU for permissions to grant. anyone have any workarounds or fix for this?
lastly, is BusyBox still usable under Marshmallow? i loaded it up and everything seemed fine, but after a reboot Google Play Services, Amazon, Youtube and some others kept crashing.
My observations:
MyProfiles Pro not able to turn data ON/OFF with ROOT permissions even if the root permission is there for the app.
One Power Guard battery app works, but cannot tweak the profiles, it says root needed. I seriously doubt if it really is working.
njaustin123 said:
My observations:
MyProfiles Pro not able to turn data ON/OFF with ROOT permissions even if the root permission is there for the app.
One Power Guard battery app works, but cannot tweak the profiles, it says root needed. I seriously doubt if it really is working.
Click to expand...
Click to collapse
what I've realized is that SuperSU is running in systemless mode, which is causing some issues for outdated apps that were hardcoded to find 'su' in /system. some workarounds are putting a dummy file named su in /system or getting SuperSU to run in /system.
dimm0k said:
I'm currently rooted and restoring my apps, however it seems like with each new version of Android the external SD gets trickier and trickier. A lot of apps these days use the round about method of having you choose the card to write to via the file manager, unfortunately not all apps do this and one of them looks to be the ever popular Tasker. am I missing the option or am I screwed and have to rewrite all my tasks to write to the internal storage?
another issue is with Secure Settings mainly used in conjunction with Tasker... when I start it up it fails to recognize su and never prompts me via SuperSU for permissions to grant. anyone have any workarounds or fix for this?
lastly, is BusyBox still usable under Marshmallow? i loaded it up and everything seemed fine, but after a reboot Google Play Services, Amazon, Youtube and some others kept crashing.
Click to expand...
Click to collapse
I learned this the hard way in updating from LP to MM; do NOT restore your apps from a backup under LP. I did that, and was having nothing but issue after issue. Best bet, backup everything not an app, go back to the google play store, and reinstall everything from there. Any apk's you had you installed, install them fresh. I was literally to the point of shipping the phone back to T-Mobile and going to an S7 it was such a pain in the neck. After I learned after the 4th factory reset from LG Bridge, I've never had any issues since.
chernabog88008 said:
I learned this the hard way in updating from LP to MM; do NOT restore your apps from a backup under LP. I did that, and was having nothing but issue after issue. Best bet, backup everything not an app, go back to the google play store, and reinstall everything from there. Any apk's you had you installed, install them fresh. I was literally to the point of shipping the phone back to T-Mobile and going to an S7 it was such a pain in the neck. After I learned after the 4th factory reset from LG Bridge, I've never had any issues since.
Click to expand...
Click to collapse
Whenever you do a clean fresh flash Rom at the setup most rooms let you restore all your previous apps from google, no need to go to the play store it does it automatic. If you made a backup just restore the data.
Sent from my LG-H901 using XDA-Developers mobile app
dimm0k said:
what I've realized is that SuperSU is running in systemless mode, which is causing some issues for outdated apps that were hardcoded to find 'su' in /system. some workarounds are putting a dummy file named su in /system or getting SuperSU to run in /system.
Click to expand...
Click to collapse
Thanks. But can you give me little bit more details on that. How can I get SuperSU to run in /system? I checked settings of SuperSU app, but could not find.
Also I tried to create a new file called su in /system with Root Browser of ROM Toolbox, but it says 'failed'
chernabog88008 said:
I learned this the hard way in updating from LP to MM; do NOT restore your apps from a backup under LP. I did that, and was having nothing but issue after issue. Best bet, backup everything not an app, go back to the google play store, and reinstall everything from there. Any apk's you had you installed, install them fresh. I was literally to the point of shipping the phone back to T-Mobile and going to an S7 it was such a pain in the neck. After I learned after the 4th factory reset from LG Bridge, I've never had any issues since.
Click to expand...
Click to collapse
I have witnessed this, mainly with Google apps. after restoring the app with data the app would randomly crash... removing the app and installing it from Google fixes it, but I have not experienced this with non-Google apps. I'll keep this in mind the next go around when restoring my stuff.
njaustin123 said:
Thanks. But can you give me little bit more details on that. How can I get SuperSU to run in /system? I checked settings of SuperSU app, but could not find.
Also I tried to create a new file called su in /system with Root Browser of ROM Toolbox, but it says 'failed'
Click to expand...
Click to collapse
you won't be able to change SuperSU to be in systemless mode within SuperSU... look here for the non-systemless root method that you'll need to flash in TWRP. realize that if you do this flash that it most likely will break Android Pay. not sure if you need to mount /system as rw in Root Browser before you can create files there or if Root Browser does it for you automatically?
I am having issues with the camera in manual mode it keeps force closing
Sent from my LG-H901 using XDA-Developers mobile app
after doing some research and from my understanding, the bad news is that it looks like it's up to devs to add the feature of writing to the external SD via the Storage Access Framework (SAF). unfortunately it doesn't look like an easy task, as the developer of Tasker mentioned that he won't be implementing this since the number of external SD users are far and few =( and would revisit it if that number changes.
the good news for those of us smart and brave enough to root our devices, this is solvable via editing packages.xml and adding in one line for each app you want to "fix". this is documented here
justice26 said:
I am having issues with the camera in manual mode it keeps force closing
Sent from my LG-H901 using XDA-Developers mobile app
Click to expand...
Click to collapse
works fine for me here... are you using stock ROM?
dimm0k said:
you won't be able to change SuperSU to be in systemless mode within SuperSU... look here for the non-systemless root method that you'll need to flash in TWRP. realize that if you do this flash that it most likely will break Android Pay. not sure if you need to mount /system as rw in Root Browser before you can create files there or if Root Browser does it for you automatically?
Click to expand...
Click to collapse
I don't want to break stuff like Android Pay though I am not using it right now.
And about putting the file, in ROM Toolbox it says rwxr-xr-x for /system. Doesn't that mean write is there?
njaustin123 said:
I don't want to break stuff like Android Pay though I am not using it right now.
And about putting the file, in ROM Toolbox it says rwxr-xr-x for /system. Doesn't that mean write is there?
Click to expand...
Click to collapse
I believe non-systemless root only breaks Android Pay because of the way Android Pay is designed, as I believe it needs /system to be "pure". just want you to know that I have not done anything and have left everything as is, systemless root. seems like the only app I had that needed root was Secure Settings, which doesn't look like it will ever be updated anytime soon so I'm trying to ween myself away from that and do everything via Tasker without that plugin. as for you, if you're lucky, write to the apps you're having issues with and have them update it for systemless root. the issue is that their apps were looking for root specifically in /system, but with systemless root the su binary is now in /su/bin. as for putting a dummy su file in /system, I'm not entirely sure that would make your apps work and if it would break Android Pay if you did so. regardless, it doesn't hurt to try as you can simply remove the dummy su file to revert back to systemless. I believe those permissions you've listed for /system does does mean it can be written to, however it has to also be mounted as rw. check that via a terminal by issuing "mount | grep /system". you will probably see a ro in parenthesis or simply try to put a file in there.
dimm0k said:
I believe non-systemless root only breaks Android Pay because of the way Android Pay is designed, as I believe it needs /system to be "pure". just want you to know that I have not done anything and have left everything as is, systemless root. seems like the only app I had that needed root was Secure Settings, which doesn't look like it will ever be updated anytime soon so I'm trying to ween myself away from that and do everything via Tasker without that plugin. as for you, if you're lucky, write to the apps you're having issues with and have them update it for systemless root. the issue is that their apps were looking for root specifically in /system, but with systemless root the su binary is now in /su/bin. as for putting a dummy su file in /system, I'm not entirely sure that would make your apps work and if it would break Android Pay if you did so. regardless, it doesn't hurt to try as you can simply remove the dummy su file to revert back to systemless. I believe those permissions you've listed for /system does does mean it can be written to, however it has to also be mounted as rw. check that via a terminal by issuing "mount | grep /system". you will probably see a ro in parenthesis or simply try to put a file in there.
Click to expand...
Click to collapse
OK, so here is it: I was able to mount /system as rw with the terminal emulator in ROM toolbox and then create a dummy file named su. Rebooted the phone, both the apps still fail. I will write to the developers. For the time being, I am OK turning data on/off manually along with using MyProfiles for other things. And for the One Power Guard, I believe freezing many of the T-Mobile and LG junk using Titanium and having SetCPU with a little bit under-clocking have already made the battery better. So I can wait. Am also evaluating Craig's Root Battery App instead of OPG. Thank you anyways.