Related
Is it possible to run Android Market on SDK 1.5?
It works on 1.1 with installing the 4 files: vending.apk, talk.apk, gtalkservice.apk, setupwizard.apk
anybody knows how to make it work in 1.5?
Thanks
you have to download the google developer phone images (system.img userdata.img) from the HTC site and overwrite them in the emulator image directory (don't remember exactly where it is)
find image files
do you know where can i find custom rom images ? the system.img userdata.img etc
Thanks
zceep24 said:
do you know where can i find custom rom images ? the system.img userdata.img etc
Thanks
Click to expand...
Click to collapse
Try to use the search function .... http://www.google.at/search?hl=de&s...r+phone+images+inurl:htc.com&btnG=Suche&meta=
This search will lead you to http://www.htc.com/www/support/android/google-io-device.html
I can boot the Ion ROM image, but it refuses to use the LAN (emulator pass-through) connection so Marked is not really a possibility after all.
I can use it without any modification
It's the same for me: with the files (recovery.img, system.img and ramdisk.img) from the HTC package, the emulator works well but the network connection is missing. What's your procedure?
I wonder if we can just pull out the proper .apk's and .odex files from the Ion ROM image and install/replace on the stock Cupcake image in the emulator. I did this with the Amazon application but have thus far not been successful with the marked.
I got it to work by doing following:
1) Downlaoded and installed the android SDK.
2) Run the command prompt and go to the tools dir in the SDK.
3) Greated an avd with 1.5 as target with the a default hardware profile. ('android list target' get a list of targets, 'android create avd -n enhanced -t 2' creates the avd as target 2)
4) Download and unzip this image file. update-cm-3.6.5-signed.system.img.zip extracted it and put the system.img in the enhanced.avd folder.
5) Opened the emulator through a project in eclipe. But can be done as command as well 'emulator -avd enhanced'.
6) When android is running i first went to market and it seemed to work fine except that the downloads never started. So i tryed to install the MarketEnabler.apk and everything worked fine.
The system image is a developer image, and loading android on the emulator first time took quite a while.
So finally i can get the apps from Android market on the non-google branded mobile
ddms file explorer does not work
Wow, market now works on my emulator.
However when i tried to pull the apk from the emulator, the ddms's file explorer does not work.
How do you pull apps ?
please help.
thanks
can't pull apk files
the same here ....
I got he emulator working with Android Market - apps are downloading fine
... but how do you get to those apk files downloaded to emulator AVD - so that you can then install them on non-google branded Sapphire device ?
many thanks
has anyone got the gps emulator working with update-cm-3.6.5-signed.system.img.zip ? Would really like to test out gps apps and keep market apps enabled. I can only get geo fix to work with GSM disabled.
konop13 said:
the same here ....
I got he emulator working with Android Market - apps are downloading fine
... but how do you get to those apk files downloaded to emulator AVD - so that you can then install them on non-google branded Sapphire device ?
many thanks
Click to expand...
Click to collapse
Didn't have any problems making pull from my emulator, havent really messed around with it for a while cause i got the perfect SPL downgraded on my Magic so got Hero, google apps and everything i need on the mobile now.
Does the adb list the emulator device ? "adb devices"
sorry i also hv same problem...
i cant pull apk from the emulator... hav someone get pull the soft from the emulator??? if yes... please tell the steps...
Is this possible on 2.1 now or is it just for 1.5 still?
And if so where can i find the img file?
I would love to know if this work with 2.1 as well.
I made a Android 2.2 system.img with market,
su and busybox for Android SDK AVD, that you can download here: http://www.ehalm.at/avd-2-2-market.php?l=en
There is also an installation guide.
Please read them through so does the Market correct.
This video will explain again how to make the market work:
Thanks Ehalm, your system.img helped me a great deal because I have a Velocity Micro Cruz Tablet without the Android Market. After a few days of tinkering I was able to get the Market and protected apps on a SDK AVD under Linux Lubuntu!!!
Here's a link to a thread I started in Slatedroid forum to help Cruz Tablet Owners.
http://www.slatedroid.com/index.php?topic=14771.msg119065#msg119065
AVD 4.3 with Play Store, SuperSU and more.
New version with Android 4.3 available!
Android 4.3 system.img with Play Store, SuperSU (root) and more for Android SDK AVD (Android Virtual Device).
Google Apps (Google Play Store, Google Sync, Gmail, ...) included.
Rooted, SuperSU and BusyBox included.
ES File Explorer (can be used as root-explorer) and Titanium Backup included.
Here you can download it: http://www.ehalm.at/avd-4.3-gapps.php?l=en
Download link: MT3GV1.5_NBN1.5.zip
MD5:
1c962a4767659f86776fe6daf3052cf7 MT3GV1.5_NBN1.5.zip
This is the result of the work/messing around I did in this thread.
I started with the T-Mobile OTA stock ROM available here:
signed-opal-ota-150449.95700137.zip
I then:
1. Rebuilt the kernel with the same config as the ROM, except with the addition of the netfilter features required for tethering. (Kernel source is slightly newer than in the ROM as yesterday there were a few security related patches added to the repo.) The wlan.ko driver was rebuilt to match the new kernel as well.
2. Added the Superuser app and the Tethering app.
3. Removed the T-Mobile recovery and radio images. They are redundant at best, bricks waiting to happen at worst.
4. Re-packed and re-signed the ROM. (Only the ROM zip was signed so it would install via our recovery images. The internal apks were left alone.)
The result should be an experience identical to the stock software you had out of the box, but with the possibility of running apps that require root as well as tethering. Speed is the same, features are the same, apps are the same, etc.
There are plenty of great custom ROMs here if you're looking for more, but this will work if you're going for simple with no surprises.
UPDATE: Donut /1.6 update is on page 3.
UPDATE: Donut /1.6 DMD64 update is on page 4.
Is this for 32B or 32A?
This is for 32B.
awesome
hey man great job this is exactly what i want!!! great job!!!
atomtom, thank you for doing that. It's been working great the last 24 hours, no hidden gotchas or surprises from the updated kernel/wifi driver.
Thank you!!!...This is EXACTLY what I was looking for ..expecially for my friends who want root for wifi tether!!
Clean and Stock
Thanks for this ROM. I like clean and simple builts and this fullfill my tethering needs with my Viliv S5. I installed it today on MyTouch 3G.
Hi there
I installed this rom last night and by morning the phone was complaining about memory and had a bunch of processes force close.
Is there a mem leak or anything with this rom?
Not that I know of, but I only tested it for a few hours and then went on to Cyanogen for my daily use. Considering how similar this is to the stock ROM I would be very surprised if there was a memory leak.
Standard debugging questions: What SPL and radio are you running? Did you do a wipe before installing? Do you have a log we could look at?
I'll put this ROM back on my phone and see how well it's doing tomorrow.
Noticed an issue. The SU you are using isn't ideal. With tethering it was fine but as soon as I typed Su in terminal emulator, it starts the superuser permissions app, but it comes up blank. If I go back, its stuck waiting for Su permission. Zenthought.org has/had one I used, its from the JF and cyanogen builds. If u decide to use it make sure u change the Su binary too.
atomtom said:
Not that I know of, but I only tested it for a few hours and then went on to Cyanogen for my daily use. Considering how similar this is to the stock ROM I would be very surprised if there was a memory leak.
Standard debugging questions: What SPL and radio are you running? Did you do a wipe before installing? Do you have a log we could look at?
I'll put this ROM back on my phone and see how well it's doing tomorrow.
Click to expand...
Click to collapse
Hi there
I am running SPL 2005 (aman_ra mytouch root guide)
32B radio from htc site for google ion 2.22.19.26I
recovery 1.2.0G (aman_ra)
I have been going back and forth trying to find the rom that works best for me so yes i have done the format/wipe. Also since i want to be sure i might even run the following ontop of the format/wipe
fastboot erase system -w
fastboot erase boot
I dont erase recovery since i dont think i need to.
Please let me know.
Also - I would LOVE it if you could provide the same rom but with HTC keyboard/dialer.
flamingblue8z said:
Noticed an issue. The SU you are using isn't ideal. With tethering it was fine but as soon as I typed Su in terminal emulator, it starts the superuser permissions app, but it comes up blank. If I go back, its stuck waiting for Su permission. Zenthought.org has/had one I used, its from the JF and cyanogen builds. If u decide to use it make sure u change the Su binary too.
Click to expand...
Click to collapse
Yeah, the one that is available stand-alone is older than the one that comes with other ROMs. When I tried installing the newer apk pulled from Cyanogen 4.0.1 it would fail due to the key used to sign the ROM internals.
adb install Superuser.apk:
Code:
159 KB/s (14979 bytes in 0.091s)
pkg: /data/local/tmp/Superuser.apk
Failure [INSTALL_FAILED_UPDATE_INCOMPATIBLE]
adb logcat:
Code:
E/PackageManager( 58): Package org.zenthought.android.su has no signatures that match those in shared user android.uid.system; ignoring!
W/PackageManager( 58): Package couldn't be installed in /data/app/org.zenthought.android.su.apk
If anyone knows how to sort this out let me know and I'll update it.
That said, su still worked perfectly when I installed Better Terminal Emulator. (Of course, Better Terminal Emulator doesn't work to begin with. Try typing in a number.)
hmm interesting. when I was using just the stock ROM, then used 1click root, went into CM-recovery, followed by your directions, adb mount -a, then adb push the SU in reference, zenthought's, I had no issue. I then pushed the wlan.ko you put up, and flashed boot.img, rebooted, and finally installed the Superuser.apk, and I had NO issues whatsoever. i've got a nandroid backup of that system setup, in case there is anything of interest in there. I would have to boot back into it and remove my txts/mms/contacts, but i'd gladly share it for analysis.
I noticed the myTouch NBH appeared earlier, im going to try downloading that on my WinMo Wing (it connects to the wifi at the college im at but my G1 and myTouch won't.) i'll try flashing the NBH then your ROM, see what happens... oh and yes, I obviously wiped before installing ur ROM.
ROM has Superuser Permissions and Superuser Whitelist? Whats the difference and are they both needed?
Superuser Whitelist is the name of the apk that manages which app gets root access, su is the command line tool that actually performs the actions requested as root.
speedyls91 said:
Hi there
I installed this rom last night and by morning the phone was complaining about memory and had a bunch of processes force close.
Is there a mem leak or anything with this rom?
Click to expand...
Click to collapse
After last night and today of normal use, and leaving it on overnight, I haven't seen any behavior out of the ordinary.
I spent the last hour or so playing around with the donut update, but there are problems.
I downloaded the COC10 to DRC92 update zip and looked through it. Appears to be a new boot.img, a handful of files, and a bunch of binary patches. I made the following changes:
1. New kernel with the netfilter features enabled, but otherwise same sources and config.
2. Replaced the wlan.ko patch with the full file that goes with the new kernel since the one we're upgrading isn't the original and the patch won't apply.
3. Changed the update script to not try to patch the wlan.ko and skip over the version/key checks.
The update (applied manually via the recovery image) went fine, but there are problems with one of or both of WiFi Tether and Superuser. When attempting to start tethering there is just a general failure error but nothing bad in the log screen. In addition the Superuser app no longer honors the "always yes" setting. There are newer versions of both apps so I'll check those out later tonight/tomorrow.
Wow, doesn't sound good. Maybe leave out Wifi tether? I have been using a better su whitelist app, I think u may want to use it. I am using stock Donut at the moment, runs GREAT, so if I can help this would be great. What I am going to do is load my nandroid backup, clear out some garbage, and if you want I can send u my system.img and u can pick it apart appropriately to take a look at the SU I have along with the whitelist app. Perhaps that will solve the problems.
Wifi Tether is kinda the whole point so leaving it out isn't an option (or rather, having the user install it manually won't help). I think getting the new Superuser app working is a higher priority though. Unfortunately a system image of a stock ROM won't do any good. The problem is that the Superuser app ties in to the system in a way that requires them to be signed with the same key (or a shared key, something I haven't looked in to yet.)
Code:
I/PackageManager( 78): /system/app/Superuser.apk changed; collecting certs
E/PackageManager( 78): Package org.zenthought.android.su has no signatures that match those in shared user android.uid.system; ignoring!
My guess that the system is signed with T-Mobile's production key but Superuser is signed with a test key that is used on the fully custom builds. So it works fine with stock Android, Cyanogen, etc., but not here since I only changed the kernel, not the keys.
Obviously I can't re-sign Superuser.apk with T-Mobile's key so I have to re-sign the system with the test key. Unfortunately I have no idea 1) which file this is specifically, or 2) how to do it even if I knew.
Any suggestions are of course appreciated.
You mentioned that before. But even on the stock COC10 ROM, I pushed THAT su (from the last JF ROM,1.51) into /system/bin and then installed the apk into /data/app and it worked previously. If you wouldn't mind, plz send the new boot.img and I'll try flashing it through fastboot, as well as cm-recovery so I can use the root access adb to push the su into the stock donut. Which spl has fastboot enabled? I'll PM u my email.
So.
As i was slowly preparing DSC v2.0 i met a hard decision: what root tool to include
Both Superuser and SuperSU are nice, but quite heavy
I decided to take my own way - rewrite su executable itself to suit my vision:
I've aknowledged that i have not modified my root access list for half a year. I don't need and don't want a separate Java process to control root access. I want a simple way to allow root access for application (via whitelist), but block unwanted (i.e. all not in list). Still, it should allow end-user to install either SuperSU or Superuser.
In short - ideal su solution for myself that should also work good for depersonalized custom ROM (with predefined access list), leaving it to end-user to decide which app he will install for superuser access.
And i didn't find a ready solution, so decided to write my own.
Here it is (attached):
SimpleSU
Simplest and lightest superuser solution (with access control)
How it's done:
Same as usual SU for Linux with control access list read from /system/etc/dsc.su_list
dsc.su_list structure is very simple:
One line per android app (case sensitive), windows and unix line breaks should be supported fine.
Current proposed list for DSC 2.0 (and an example):
dsc.SimpleSU.acl
dsc.settings
dsc.uv
dsc.levels
dsc.mugen
jackpal.androidterm
ru.org.amip.ClockSync
eu.chainfire.supersu
eu.chainfire.supersu.pro
com.ryosoftware.adbw
com.googlecode.droidwall.free
com.noshufou.android.su
de.schaeuffelhut.android.openvpn
de.schaeuffelhut.android.openvpn.installer
com.elsdoerfer.android.autostarts
com.speedsoftware.rootexplorer
com.geeksoft.screenshot
com.rerware.android.MyBackupPro
com.ghostsq.commander
ws.plattner.cifsmanager
mobi.pruss.superdim
com.force.timezonefixer
com.bigtincan.android.adfree
Caller process tree is walked till init, if match is found, access is granted.
How to install?
Via adb shell:
Code:
adb push su /system/xbin/
adb shell chmod 6755 /system/xbin/su
adb push dsc.su_list /system/etc
adb shell chown root.root /system/etc/dsc.su_list
adb shell chmod 644 /system/etc/dsc.su_list
Note that you have to manually add entries to white list (/system/etc/dsc.su_list) to grant root access in form of app full Java class name. For example, it's com.keramidas.TitaniumBackup for Titanium Backup.
As pointed by dr911, works in multiuser environment (being a linux binary).
Currenly SimpleSU supports two command formats:
Usual: su -c 'make me a sandwich'. Note that only "-c" works now. Seems to be enough though. Command simply passed to the shell.
Legacy (as seen in Google/Android su source): su username make me a sandwich. Shell is not executed in this case, so no environment variables right now in this format.
Have fun,
Sergei.
Changelog:
02.04.2013: v0.7. ":service" suffix granted root access for already granted app, more logging on reject. (0.6 had only more logging)
27.11.2012: GUI updated - forgot about remounting /system in rw mode. Attached to this post.
21.11.2012: GUI done. http://forum.xda-developers.com/showpost.php?p=34439975&postcount=41
14.11.2012: v0.5. LD_LIBRARY_PATH fixup (taken from ChainsDD), pointed by Rupert Rawnsley. Also some legacy format command-line handling changed. Also, insecure version added (no checks made, asked=granted).
11.11.2012: v0.4. Code cleanup, no longer beta, revised and fixed code with potential string overflows.
09.11.2012: v0.3b. Code changed to allow legacy format command execution.
09.11.2012: v0.2b. Fixed call with multiply parameters. OpenVPN installer works. Dynamic linking, so very small binary. Logging to system log.
07.11.2012: Fixed segmentation fault on reject, added version and build date, removed debug info.
A request:
If somebody owns Pro/Elite/other commercial Superuser or SuperSU - would you provide it's full Java class name?
For example, it's
eu.chainfire.supersu
com.noshufou.android.su
for free versions.
eu.chainfire.supersu.pro
Sent from my Amazon Kindle Fire using Tapatalk 2
Can I avoid these little delays (the appearing popup of SuperSU or Superuser) with this alternative?
And if I have Superuser preinstalled can I delete it and are there other files which belongs to it and can be deleted?
Thank you for sharing your work
com.noshufou.android.su.elite for Superuser Elite
Hi
Have you noticed any improvement in terms of speed etc? Is superuser really that heavy? How much RAM can i get by using this and ditching the superuser app? We can use this in our Galaxy 3 forum !
Get the list of all android activities from here
http://activities.droidicon.com/
Androidmarketuser said:
Can I avoid these little delays (the appearing popup of SuperSU or Superuser) with this alternative?
And if I have Superuser preinstalled can I delete it and are there other files which belongs to it and can be deleted?
Thank you for sharing your work
Click to expand...
Click to collapse
Delete system/xbin/su and uninstall your superuser app from the system.
Oh. Looks SimpleSU got in news
Androidmarketuser said:
Can I avoid these little delays (the appearing popup of SuperSU or Superuser) with this alternative?
And if I have Superuser preinstalled can I delete it and are there other files which belongs to it and can be deleted?
Thank you for sharing your work
Click to expand...
Click to collapse
You won't experience any delays - but in cost of manually editing the list. And no popups, it's simply a linux binary. After replacing su binary you may uninstall Java part.
Shree_Jamdar said:
Have you noticed any improvement in terms of speed etc? Is superuser really that heavy? How much RAM can i get by using this and ditching the superuser app? We can use this in our Galaxy 3 forum !
Click to expand...
Click to collapse
I did experience lags when using Superuser and SuperSU. I don't think modern device would benefit from SimpleSU. I expect to free 15-20MB. Good for Streak with 512MB.
I may eventually write a list editor, but most probably won't.
Again, this tool would do as preinstalled SU solution in Custom ROM (though i can't test >2.3 compatibility):
Grant predefined (and included in ROM) apps the superuser rights.
Allow end-user to choose and install he's preffered SU solution right from Play Store.
--
Have fun,
Sergei
_n0p_ said:
You won't experience any delays - but in cost of manually editing the list. And no popups, it's simply a linux binary. After replacing su binary you may uninstall Java part.
I did experience lags when using Superuser and SuperSU. I don't think modern device would benefit from SimpleSU. I expect to free 15-20MB. Good for Streak with 512MB.
I may eventually write a list editor, but most probably won't.
Again, this tool would do as preinstalled SU solution in Custom ROM (though i can't test >2.3 compatibility):
Grant predefined (and included in ROM) apps the superuser rights.
Allow end-user to choose and install he's preffered SU solution right from Play Store.
--
Have fun,
Sergei
Click to expand...
Click to collapse
Exactly what I searched, thanks :good:
I will test it on my old Desire with Android 4.1, I can tell you whether it's compatible or not.
nice tool...very lite. i m using this in extreme barebone roms for my galaxy mini. really nice, but the problem is only some apps r being granted permissions, some denied.
i hope u increase the list of activities. then this is a hit for me
good luck..
Android_United said:
nice tool...very lite. i m using this in extreme barebone roms for my galaxy mini. really nice, but the problem is only some apps r being granted permissions, some denied.
i hope u increase the list of activities. then this is a hit for me
good luck..
Click to expand...
Click to collapse
Can you provide an example of app you have added to the access list, but it didn't work?
i looked in the op and still dont understand how to install?? flash the simple SU zip in recovery.. then what???
evo401 said:
i looked in the op and still dont understand how to install?? flash the simple SU zip in recovery.. then what???
Click to expand...
Click to collapse
if you couldnt read/understand the OP, then your probably better off sticking with SuperSU or SuperUser...
Heres my non-developer understanding (potentially flawed):
Its a binary, with manual entry's (IE text editing) of pre-approved apps, it doesnt have a frontend/gui like SuperSU or SuperUser which allow you to graphically chose what to allow and what to deny...
OP: I like it so far, as for your thoughts on a graphical editor, I for one would love to see one, and before I get jumped for saying then whats the difference between the other options, an editor would be short and sweet, open, edit list, close, ram once again free (since that is the concern), instead of having it stay resident in RAM...
On that note, if I may, there are tools like Rays Toolbox and Android Tuner (formerly system tuner), that I would like to put in a feature request for them to add an editor in the app (Android Tuner already has a few editor's, adding a SimpleSU editor would just add to the overall completeness of the toolkit) to edit the list for SimpleSU, with your permission of course!
Thanks again!
Latest version working on Galaxy fit !!! It really imporves performance on low ram(We got 256mb) devices maybe OP might consider sharing it by moving thread to a more general location on xda rather than on a device forum my thoughts.
Dark Passenger said:
Latest version working on Galaxy fit !!! It really imporves performance on low ram(We got 256mb) devices maybe OP might consider sharing it by moving thread to a more general location on xda rather than on a device forum my thoughts.
Click to expand...
Click to collapse
Yes, exactly.. it works on galaxy y duos and galaxy yseries.. its better to move it to android app development section may be? as it will get more support there i feel.. Please do consider op.. And thanks for this cool app.. Its awesome. And i dont think it needs an editor, as we can have editors from many apps .. i have around 4-5 apps which has editors.. surely users who use this app will be bit advanced users..
and i bet all of them will have file editors.. and all file explorer apps comes with editors nowadays.. well , just my thoughts.. but if you can keep the file browser to bare minimum and keep size of apk less.. then i would surely like to see it too
i am hoping to use this from now on.. so i will give review for new updates.. have you pushed it to play store? i think you should do that.. many will like this idea!
Thanks again..
As far as i understood we can edit it to add new apk names to give permission.. Because Android_united kinda confused me.. So, asked this again.. i did use it and it did worked.. its just may be he didnt see that?
Works like a charm! The only problem I had is that I was doing this through Terminal Emulator, and for some reason, when i did all this, superuser perrmisions were not granted for Terminal Emulator. After a little digging i found that i have to add this line
Code:
jackpal.androidterm2
and leave the one that's there by default
Code:
jackpal.androidterm
to the dsc.su_list
Now it works, i have SU for Terminal Emulator, Adfree, and i added SetDNS (Impossible to use Google play on CM7.2 without it )
I like the idea of this but be extra careful to only whitelist activities you really use.
I could imagine a malware somehow managing to enter your system and masquerading as one of the prepopulated entries in dsc.su_list, though of course no such vulnerability exists so far.
Thank you for feedback.
--
I cannot publish it on Play Store - it's not an Android app. To publish it, i need to write SimpleSU Installer, or something like that (see below).
--
Regarding editor - it would be nice if someone else would write it I really don't expect to have enough free time required.
--
A 0.4 version i consider as stable (revised potentially bad code with possible string overflows) attached to first post.
--
Malware that could act as Java class - i thought of several scenarios, but any requres root access beforehand. And if you install an app - it's your responsibily to be careful.
--
Have fun,
Sergei
_n0p_ said:
Can you provide an example of app you have added to the access list, but it didn't work?
Click to expand...
Click to collapse
titanium backup, es-file explorer. i tested wit only these 2. as these 2 weren't gaining root access, so i stopped using this. if u want me to test wit more apps, i can help u out.
will be using this surely once it receives more updates :good:
:good: gud luck..
Hi all.
I have a new ZTE V975 and i have it root and with gapps but i have a problem with Play Store compatibility. "Financial" apps aren´t compatible with the phone. I think that it is a location problem in build.prop
The problem is that i dont know modify it.... can someone see this build.prop archive to see if can change it to improve compatibility?
If someone want to see it i can upload it.
Thx.
gargamelxda said:
Hi all.
I have a new ZTE V975 and i have it root and with gapps but i have a problem with Play Store compatibility. "Financial" apps aren´t compatible with the phone. I think that it is a location problem in build.prop
The problem is that i dont know modify it.... can someone see this build.prop archive to see if can change it to improve compatibility?
If someone want to see it i can upload it.
Thx.
Click to expand...
Click to collapse
Hi gargamelxda,
I've got the same phone and noticed the same thing with certain apps on the play store. Basically what I found was the device was missing a bunch of Google support files that were in GAPPS zip. Now I wasn't able to flash the GAPPS.zip file through the built in recovery as it wasn't signed correctly for this phone and there is no custom recovery available yet.
What I ended up doing is extracting the GAPPS zip file to my SD card then used the root explorer function in ES File Explorer to mount /system as RW and move the majority of the extracted /system files to the same location in the device root /system folder. Couple of things to remember though:
1) Don't overwrite anything that's already there (there was only 2 or 3 files already there by memory)
2) If the folder already exists don't copy the whole folder but rather all the files under that folder as you may either stuff up the folder permissions or create a new folder as the android file are case sensative (eg the folder "Apps" is different to "apps")
3) There are some apk files you won't want to copy like the "onetimeinitializer.apk" file as it will run the google first time initialization next time you reboot which may stuff up your settings (although if you're planning on doing a factory reset after doing this it should be OK and all the changes you've made will stick as they're in the /system folder). I also found that if I copied "LatinIMEDictionaryPack.apk" and "GoogleTTS.apk" they would constantly crash after the reboot.
4)Make sure you set the permissions after you're done copying to "-rw-r-r--" for the files and "drwxr-xr-x" for any new folders you create. you can do this individually with ES File Explorer but if you're ok with linuix command line you can do it in batches (eg all files with the apk extension) via the Android Terminal Emulator app or ADB Shell over a USB connection to a PC. I don't remember the exact command lines I used but if you do some searching on this forum you'll find them easy enough.
After a reboot the apps should now be available to install (at least they were for me) via the Play Store.
Usual disclaimer - If you stuff this up you may brick your device and I'm in no way responsible for it.
Hope that helps
Cheers
Browney
I spent a few days trying to install Google Play the cyanogenmod way, following instruction on a spanish site similar to what other's have posted here. The idea is to mount the readonly systemfolder using the bootloader and insert/write systemapps into system/apps
I succeeded but for some reason launching google play was killed instantly by some resident app on the phone.
On the MIUI forum somebody called Eric Xiang built a google play apk that kills the resident blocker and installs googleplay !
xttp://en.miui.com/thread-3998-1-1.html
I now have a fully operational V975 (4.2.2) with the latest official build B06 and google play.
Out of the box the phone is unlocked but not rooted.
To root it, install xttps://dl.dropboxusercontent.com/u/15286951/update.zip using the bootloader (vol+ and power on, when v975 wakes up release power but keep vol+ pressed for a few seconds more, then browse to update.zip. Obviously you preloaded the zip on a sdcard.
If ZTE release firmware B08, you'll have to root it again.
Battery life is excellent, as well as speed, camera, GPS fix is instant. I had a iocean X7 that i killed trying to get the gps working, but v975 feels a lot faster vs the X7's MTK 6589 quadcore 1.5ghz. Granted there's less pixels to move around.
One caveat : iCoyote does not install because of binary incompatibility ? This is an x86 device.
I also discovered the existence of AmazonMarket. Not as complete as GAPPS, but a nice fallback market. And most of the google stuff is installable by apk anyway, so living without GAPPS was not as bad as it looked.
Thx to Eric Xiang, his app prolly opens up all androidphones to googleplay, chinese phones can flood the rest of the world now
the above was two days of research guys, enjoy it !
GlennRunciter said:
I spent a few days trying to install Google Play the cyanogenmod way, following instruction on a spanish site similar to what other's have posted here. The idea is to mount the readonly systemfolder using the bootloader and insert/write systemapps into system/apps
I succeeded but for some reason launching google play was killed instantly by some resident app on the phone.
On the MIUI forum somebody called Eric Xiang built a google play apk that kills the resident blocker and installs googleplay !
xttp://en.miui.com/thread-3998-1-1.html
I now have a fully operational V975 (4.2.2) with the latest official build B06 and google play.
Out of the box the phone is unlocked but not rooted.
To root it, install xttps://dl.dropboxusercontent.com/u/15286951/update.zip using the bootloader (vol+ and power on, when v975 wakes up release power but keep vol+ pressed for a few seconds more, then browse to update.zip. Obviously you preloaded the zip on a sdcard.
If ZTE release firmware B08, you'll have to root it again.
Battery life is excellent, as well as speed, camera, GPS fix is instant. I had a iocean X7 that i killed trying to get the gps working, but v975 feels a lot faster vs the X7's MTK 6589 quadcore 1.5ghz. Granted there's less pixels to move around.
One caveat : iCoyote does not install because of binary incompatibility ? This is an x86 device.
I also discovered the existence of AmazonMarket. Not as complete as GAPPS, but a nice fallback market. And most of the google stuff is installable by apk anyway, so living without GAPPS was not as bad as it looked.
Thx to Eric Xiang, his app prolly opens up all androidphones to googleplay, chinese phones can flood the rest of the world now
the above was two days of research guys, enjoy it !
Click to expand...
Click to collapse
Some Qs about this phone,
Does is sync. with google server ? for example does the gmail contacts sync. ok to the phone ?
Did anyone tried to install an email apk (like touchdown) and sync. with exchange server ?
popular apps like whatapp & waze works fine ? any issues with other apps ?
Does the phone has a notification Led ? can it be configured by app. to indicate with desiered color per incoming event ?
thanks!
google play
GlennRunciter said:
I spent a few days trying to install Google Play the cyanogenmod way, following instruction on a spanish site similar to what other's have posted here. The idea is to mount the readonly systemfolder using the bootloader and insert/write systemapps into system/apps
I succeeded but for some reason launching google play was killed instantly by some resident app on the phone.
On the MIUI forum somebody called Eric Xiang built a google play apk that kills the resident blocker and installs googleplay !
xttp://en.miui.com/thread-3998-1-1.html
I now have a fully operational V975 (4.2.2) with the latest official build B06 and google play.
Out of the box the phone is unlocked but not rooted.
To root it, install xttps://dl.dropboxusercontent.com/u/15286951/update.zip using the bootloader (vol+ and power on, when v975 wakes up release power but keep vol+ pressed for a few seconds more, then browse to update.zip. Obviously you preloaded the zip on a sdcard.
If ZTE release firmware B08, you'll have to root it again.
Battery life is excellent, as well as speed, camera, GPS fix is instant. I had a iocean X7 that i killed trying to get the gps working, but v975 feels a lot faster vs the X7's MTK 6589 quadcore 1.5ghz. Granted there's less pixels to move around.
One caveat : iCoyote does not install because of binary incompatibility ? This is an x86 device.
I also discovered the existence of AmazonMarket. Not as complete as GAPPS, but a nice fallback market. And most of the google stuff is installable by apk anyway, so living without GAPPS was not as bad as it looked.
Thx to Eric Xiang, his app prolly opens up all androidphones to googleplay, chinese phones can flood the rest of the world now
the above was two days of research guys, enjoy it !
Click to expand...
Click to collapse
Hey
I'm going to get this phone in the next few days. As far as I know, for 99%, I'm not going to have Google Play on it.
What is the easiest way to install Google Play on it?
I already downloaded B06 since I want to have the latest build.
New ROM´s
Hi, i aplied root, instaled recovery and now search custom ROM´s, Where are thete?
help
Hi... how to root zte v975?
Please help..
So... here I will share 2 scripts I made to fix permissions for ViPER4Android running with enforced SELinux.
Why 2 scripts?
I like to keep everything open-source. Here I like to notice, Cyanogenmod is taking the wrong direction in my point of view. Every update takes out something of the customization possibilities of the user, so I am thinking of choosing new ROM. I faced real nightmare with SELinux permissions (well... SELinux is good, but Cyanogenmod doesn't provide any tool or way to manage those permissions). The more funny part is that with branch 13.0 of cyanogenmod there is no more init.d. Before someone corrects me - yeah... there is init.d, but SELinux blocks any script from executing at boot time, so don't use it. You will get your logs spammed by error messages. So... I've tried to enable init.d again, but there is no way to manage init.d to work as before. I've tried lots of different fixes from other posts, but nothing seems to work anymore, because of SELinux restrictions. I didn't managed to find any way to run scripts on boot time with root permissions in a suitable way... without messing with other system files or rebuilding build.img... so I came with those 2 solutions:
ViPER4Android (OpenSource) This is the solution I recommend to all of you. It is full open source. It doens't mess with you current system and it should work on any device/ROM. The zip file contains ViPER4Android app and driver, sepolicy-inject tool from setools-android so we can set permissions for ViPER4Android to work with enforced SELinux and Universal Init.d.
sepolicy-inject is open source equivalent to supolicy tool of Chainfire's SuperSU. I strongly recommend sepolicy-inject over supolicy, because every root closed source app should be threaten as security risk as the code can't be examined. I don't trust it esepcially when it is part of your android root manager
Universal init.d is just a application - it simulates init.d function. Imagine it like init.d on the user side... sadly enough you need to be pre-rooted to get it running.
ViPER4Android (Legacy) Maybe more of you will like this solution as it is more automated and it doesn't require any user action after installing the zip. This zip will do the same as the one above - it will install ViPER4Android removing all other DSP apps, but here come the difference - THIS SCRIPT WILL INSTALL CHAINFIRE'S SUPERSU in order to set SELinux policies for ViIPER4Android. Chainfire's SuperSU uses supolicy-tool - it let you manage SELinux policies on boot time. Chainfire's SuperSU will run everything in /system/su.d/ so again... you have init.d support - this is the real pain in the ass.
Before you download and flash, please read:
Both scripts WILL REMOVE other DSP apps from your device and will install ViPER4Android 2.4.0.1. I STRONGLY RECOMMEND TO USE SOLUTION 1 AS IT IS FULL OPEN SOURCE! Support open source software!!!
INSTRUCTIONS
ViPER4Android (OpenSource) - IN ORDER TO WORK, YOUR DEVICE MUST BE ROOTED! (Your device need to be rooted as Unversal Init.d needs root permissions in order to simulate init.d functionality)Download the .zip; Flash and reboot; Open Universal Init.d and grant root permission if asked; Reboot once more in case it don't work!
Sometimes Universal init.d is not fully initialized and needs some root permissions. That's why you need to reboot second time - then everything works. No further actions needed.
ViPER4Android (Legacy) - Just flash and reboot... but once more - SUPPORT OPEN SOURCE AND CHOOSE SOLUTION 1!!!!
For Samsung devices - if the scripts above doesn't work for you, check this post. Thx to Viper4713 for the instructions and voshchronos for solving the issue!!!
Hope to make someone happy
PS: If u want to make me happy with some beer, here you can donate a small amount. Thank you for your support.
Can i flash it on android one device running on 6.0.1
Yes. If you have any issues, please let me know!
rpangelov said:
Yes. If you have any issues, please let me know!
Click to expand...
Click to collapse
Hi, i tried to install the open source version on my kltedv running resurrection remix 6.0.1 however it is still not working. The init.d shows the kernel doesnt support init.d, and v4a drivers status is abnormal. It is also cause screen freeze and random restart. Any ideas? Your kind input would be very much appreciated. Thanks.
hiropandaz said:
Hi, i tried to install the open source version on my kltedv running resurrection remix 6.0.1 however it is still not working. The init.d shows the kernel doesnt support init.d, and v4a drivers status is abnormal. It is also cause screen freeze and random restart. Any ideas? Your kind input would be very much appreciated. Thanks.
Click to expand...
Click to collapse
I've just readed some info about the ROM you use. As it is based on Cyanogenmod I assume there is root manager builded in. Maybe it is disabled as CM root access is disabled by defaults? Look at: Settings -> Developer Options -> Root Access - turn in on by "Apps only".
Then just follow this steps:
1. Start Universal Init.d
2. Turn it off from the toggle button
3. Run test from the button on the bottom of Universal Init.d
4. If ask for root permissions, grant them!
5. Turn Universal Init.d ON from the toggle (step 2 you turned it off)
6. Restart your device and check once more!
If you still have any issues, please let me know!
Greetz,
Angelov
---------- Post added at 10:44 PM ---------- Previous post was at 10:42 PM ----------
rpangelov said:
I've just readed some info about the ROM you use. As it is based on Cyanogenmod I assume there is root manager builded in. Maybe it is disabled as CM root access is disabled by defaults? Look at: Settings -> Developer Options -> Root Access - turn in on by "Apps only".
Then just follow this steps:
1. Start Universal Init.d
2. Turn it off from the toggle button
3. Run test from the button on the bottom of Universal Init.d
4. If ask for root permissions, grant them!
5. Turn Universal Init.d ON from the toggle (step 2 you turned it off)
6. Restart your device and check once more!
If you still have any issues, please let me know!
Greetz,
Angelov
Click to expand...
Click to collapse
Hi Angelov, many thanks for your helpful instruction. I couldnt get it work with open source version. However it is working now after i install V4A legacy version. Many Thanks once again.
hiropandaz said:
---------- Post added at 10:44 PM ---------- Previous post was at 10:42 PM ----------
Hi Angelov, many thanks for your helpful instruction. I couldnt get it work with open source version. However it is working now after i install V4A legacy version. Many Thanks once again.
Click to expand...
Click to collapse
You are welcome! As I mentioned in the instructions - the legacy script will work always, but I don't like the implementation of it. I am working on new version of the opensource script, so there won't be any issues of that kind. When I am ready I will upload it here after updating my first post.
Greetz,
Angelov
This "universal" fix has been shared several months ago on XDA and a simple root shell is enough to use V4A in enforcing mode.
FYI init.d is deprecated now but it's not related to CM. Use su.d instead.
Primokorn said:
This "universal" fix has been shared several months ago on XDA and a simple root shell is enough to use V4A in enforcing mode.
FYI init.d is deprecated now but it's not related to CM. Use su.d instead.
Click to expand...
Click to collapse
Can you provide me a link to this universal fix you are talking about?
PS: init.d is deprecated in AOSP, i get that. Please read my first post once more, obviously isn't clear enough. Using su.d will result in using closed source tools to manage your Selinux policy's. As I mentioned it above - please support open source software. Every closed source root app has to be threaten as security risk. My opinion...
rpangelov said:
Can you provide me a link to this universal fix you are talking about?
PS: init.d is deprecated in AOSP, i get that. Please read my first post once more, obviously isn't clear enough. Using su.d will result in using closed source tools to manage your Selinux policy's. As I mentioned it above - please support open source software. Every closed source root app has to be threaten as security risk. My opinion...
Click to expand...
Click to collapse
Check the official V4A thread for instance. Others have opened threads in device specific forums or in the App & Games forum.
Have a look at this thread, it might interest you: http://forum.xda-developers.com/android/software-hacking/wip-selinux-capable-superuser-t3216394
FYI I do support open-source free/libre softwares, as much as I can.
Primokorn said:
Check the official V4A thread for instance. Others have opened threads in device specific forums or in the App & Games forum.
Have a look at this thread, it might interest you: http://forum.xda-developers.com/android/software-hacking/wip-selinux-capable-superuser-t3216394
FYI I do support open-source free/libre softwares, as much as I can.
Click to expand...
Click to collapse
I've seen phh's SuperUser but I didn't tried it - this is one of my tasks for this/next week.
As I've tried the most scripts, I didn't liked all the actions needed to be taken before running the .zip script in order to get viper working. I compile my own Cyanogenmod and I don't use gapps. Almost all apps I use on my device are opensource as I use F-droid as my only market (well... I need whatsapp, but I download it just from the website). Anyway... Cyanogenmod has it's own root manager builded in.... so why I need to install one more, which contains closed source tools in it? That is also the reason I don't advice people to use it... and I don't see that as solution to my problem. AOSP is opensource, but nowadays it is very dependent on some closed-source elements and I want to wipe them all out and use open source alternatives for. I hope you understand why using su.d isn't solution in this case. You just make your self and others dependent on one more closed source app, so I don't get where is the support for open source? I think that opensource script is good solution to the problem without using any closed source tool.
To make it easy as possible - just flash the .zip and you are ready to go, I included the latest version of Chainfire's SuperSu in the legacy script, so you don't need to install it before running the .zip. It looks easier to me....
Actually it is very stupid because the result of using the scripts (doesn't matter which one) you will end up with rooted device anyway (if it isnt already), but in order to get opensource script working your device has to be rooted before running the .zip, but if your device is already rooted, you just flash the zip and you are ready to go.
rpangelov said:
I've seen phh's SuperUser but I didn't tried it - this is one of my tasks for this/next week.
As I've tried the most scripts, I didn't liked all the actions needed to be taken before running the .zip script in order to get viper working. I compile my own Cyanogenmod and I don't use gapps. Almost all apps I use on my device are opensource as I use F-droid as my only market (well... I need whatsapp, but I download it just from the website). Anyway... Cyanogenmod has it's own root manager builded in.... so why I need to install one more, which contains closed source tools in it? That is also the reason I don't advice people to use it... and I don't see that as solution to my problem. AOSP is opensource, but nowadays it is very dependent on some closed-source elements and I want to wipe them all out and use open source alternatives for. I hope you understand why using su.d isn't solution in this case. You just make your self and others dependent on one more closed source app, so I don't get where is the support for open source? I think that opensource script is good solution to the problem without using any closed source tool.
To make it easy as possible - just flash the .zip and you are ready to go, I included the latest version of Chainfire's SuperSu in the legacy script, so you don't need to install it before running the .zip. It looks easier to me....
Actually it is very stupid because the result of using the scripts (doesn't matter which one) you will end up with rooted device anyway (if it isnt already), but in order to get opensource script working your device has to be rooted before running the .zip, but if your device is already rooted, you just flash the zip and you are ready to go.
Click to expand...
Click to collapse
I mentioned su.d because that's a solution with newer Android versions but I didn't say it's the best one. Using FLOSS softwares is a good move but you are using proprietary codes with CM.
Hi everyone, i flashed both of the zips with TWRP but i got an error code : 255. Any idea how to fix it ? Please help me. I'm using an x86 phone btw
trongtin64 said:
Hi everyone, i flashed both of the zips with TWRP but i got an error code : 255. Any idea how to fix it ? Please help me. I'm using an x86 phone btw
Click to expand...
Click to collapse
I think it's because your phone architecture... anyway - I will look at it today and I will let you know if I find a solution for your problem. Can you tell me which phone exactly you own ? Thank you.
Greetz, Angelov
rpangelov said:
I think it's because your phone architecture... anyway - I will look at it today and I will let you know if I find a solution for your problem. Can you tell me which phone exactly you own ? Thank you.
Greetz, Angelov
Click to expand...
Click to collapse
i'm using a zenfone 5 (A501CG) with resurrection remix mm 5.6.7
trongtin64 said:
i'm using a zenfone 5 (A501CG) with resurrection remix mm 5.6.7
Click to expand...
Click to collapse
You have a x86 architecture and this zip is probably for arm only. I guess you need the updater-binary for x86 and place it into the zip in META-INF/com/google/android.
Primokorn said:
You have a x86 architecture and this zip is probably for arm only. I guess you need the updater-binary for x86 and place it into the zip in META-INF/com/google/android.
Click to expand...
Click to collapse
Ok so i need an updater-binary for x86 right? Can i copy it from other zip to your zip? Will it work?
trongtin64 said:
Ok so i need an updater-binary for x86 right? Can i copy it from other zip to your zip? Will it work?
Click to expand...
Click to collapse
AFAIK you can use the one from a custom rom. You need a compatible custom recovery of course.
Primokorn said:
AFAIK you can use the one from a custom rom. You need a compatible custom recovery of course.
Click to expand...
Click to collapse
I'll use the one from my custom rom . Thank you for helping me :good:
It works great. thanks.
my bad for not following the instructions.