Related
Can anyone tell me how to use Cyanogens latest CM6 for the Evo? I have my phone rooted via unrevoked and I have rom manager. Do I just use rom manager with Cyanogens file he released? I have posted in the 135 page thread with no help so I figured this would be the best place. Also what about gapps?
I'd like to know as well. I have never put a custom Rom on a phone before and am waiting for Cyanogen's release before trying it out for the first time.
My EVO is rooted with Unrevoked 3 which uses ClockworkMod recovery. I have rom manager as well.
Any step by step instructions for us newbies would be great. I don't like bricks.
thanks
gapps is a basket of applications that the phone uses for basic google integration, including the market. you'll need it for accessing several things, including the market.
gapps = google apps
right now the only cm build is a nightly, which means it isn't perfect, and may not have all of the functionality you want.
timothydonohue said:
gapps is a basket of applications that the phone uses for basic google integration, including the market. you'll need it for accessing several things, including the market.
gapps = google apps
right now the only cm build is a nightly, which means it isn't perfect, and may not have all of the functionality you want.
Click to expand...
Click to collapse
I'm really not that worried. He has all the basic things I NEED. Can I just get a how to or something here?
Eric-1987 said:
Can anyone tell me how to use Cyanogens latest CM6 for the Evo? I have my phone rooted via unrevoked and I have rom manager. Do I just use rom manager with Cyanogens file he released? I have posted in the 135 page thread with no help so I figured this would be the best place. Also what about gapps?
Click to expand...
Click to collapse
Doesn't take much to read through the Dev. threads (most of the guides there consists of ROM flashing tutorials).
Regardless, nobody is going to answer your question if you posted in the CM6 thread since it is about the ROM...not about how to install it.
Anyways..dumbed down, drag/drop ROM into sd card root, "install rom from sd card" in rom manager, find rom, backup current rom if you want, clear/wipe cache/data, flash gapps (same way as rom).
I tried that but it gave me error 7 when I tried to do that. Then it asked me for update.zip. Gave some weird error then.
Eric-1987 said:
I tried that but it gave me error 7 when I tried to do that. Then it asked me for update.zip. Gave some weird error then.
Click to expand...
Click to collapse
Are you fully rooted? I'm not aware if Unrevoked unlocks nandroid.
I dont know if it gives me full root. Probably not if im having that problem. How do I unlock nand?
http://forum.xda-developers.com/showthread.php?t=701004
Have fun.
Might be a easier way now, but you'll have to search if there is one.
Main Version Older! Error. Dunno what that is.
I searched the forums for a solution to this problem - I found that using Titanium Backup to download a new version of busybox would correct this issue, but it's still failing when I try to fix permissions from ROM Manager Premium.
When I used TiB to install busybox, it installed to /system/xbin/busybox...I put the phone in recovery mode, and from adb I pulled busybox down, and pushed it back to /system/bin
Still no luck....
From ROM Manager, I'm not able to fix permissions. This is happening after I applied someone's patch (I forgot which one) that replaces superuser with version 2.1 that's supposed to be more compatible with this 2.2 leaked build (3.16.605.0 CL203589 release-keys)
Any ideas how I can correct this issue?
I tried clearing superuser permissions 2.1's data, and when I try to fix permissions, I clicked allow, and remember. Still no luck.
Has anyone seen this issue, and been able to correct it? Perhaps I'm not using the right version of superuser permissions? If not, where can I find the correct version?
Well, I guess I've resolved the issue by reverting to an earlier backup from Monday.
Lesson learned - always make backups!
jp43 said:
Well, I guess I've resolved the issue by reverting to an earlier backup from Monday.
Lesson learned - always make backups!
Click to expand...
Click to collapse
Glad the backup solved the issue. The su 2.1 works fine btw, I don't know why someone would have a patch? Its just a zip that you flash through recovery....anyway glad you got everything worked out.
Sent from my Incredible using XDA App
Here is the 2.2.11 market.
Install with ADB, the command are:
adb remount
adb push (download location)/Vending.apk /system/app/Vending.apk
exit
Click to expand...
Click to collapse
Use the Vending.apk for gingerbread, and the vending2.2.11-signed.apk for froyo.
Usual disclaimer: It's your phone, if something bad happens don't blame me, if it ends up being better than yeah, I did that.
Update:
Thanks to Powers88, c3k, kellinwood, and phrozen87 we can install this on froyo!
AWESOME!!
Works flawlessly, here! +1
Nice find but FC's for me on cm 6.1.1
FC on CM 6.1.1
mejorguille said:
I found this app on another forum site. It seems to work better than 2.2.7 for me, and it got rid of a bug I was experiencing where sometimes an app would fail to download until the second or third try.
I don't know where it was taken from so I cannot 100% verify its integrity, but I use it with no problems.
Install with ADB, the command are:
I've tested this on Gingervillain 1.4 and crackflashers CM7 build#51. I have not tested this yet on any froyo builds.
Usual disclaimer: It's your phone, if something bad happens don't blame me, if it ends up being better than yeah, I did that.
Click to expand...
Click to collapse
It`s included in the latest CM7 Gingerbread gapps
from here:
http://goo-inside.me/gapps/
Can you flash the Gingerbread version of gapps on CM 6.1.1? I tried installing this newest Market version, and it constantly FCs on me. I tried installing it via Root Explorer and adb... neither worked.
Found the original article here: SOURCE.
You can download the .apk there and also there's a .zip file you can download there if you want to flash from recovery.
dustrho said:
Can you flash the Gingerbread version of gapps on CM 6.1.1? I tried installing this newest Market version, and it constantly FCs on me. I tried installing it via Root Explorer and adb... neither worked.
Click to expand...
Click to collapse
Just tried, and nope. yay for nandroid!
BookCase said:
Found the original article here: SOURCE.
You can download the .apk there and also there's a .zip file you can download there if you want to flash from recovery.
Click to expand...
Click to collapse
Does the link work for 6.1.1 I want the new market for 6.1.1 but havnt found one
Sent from my HTC Vision using XDA App
I am running CM 6.1.1 and can't get any new markets to work. I currently have version 1.8.2 and have tried 2.2.6, 2.2.7, .10, and .11. I have tried flashing via recovery, pushing via ADB and even tried Root Explorer. Every time I get a force close. Could anyone shed some light onto something I'm missing?
Thanks in advance!
Sent from my T-Mobile G2
jdh2001 said:
I am running CM 6.1.1 and can't get any new markets to work. I currently have version 1.8.2 and have tried 2.2.6, 2.2.7, .10, and .11. I have tried flashing via recovery, pushing via ADB and even tried Root Explorer. Every time I get a force close. Could anyone shed some light onto something I'm missing?
Thanks in advance!
Sent from my T-Mobile G2
Click to expand...
Click to collapse
+1
error is:
Code:
E/DatabaseUtils( 333): java.lang.SecurityException: Permission Denial: writing com.google.android.gsf.settings.GoogleSettingsProvider uri content://com.google.settings/partner from pid=1202, uid=10044 requires com.google.android.providers.settings.permission.WRITE_GSETTINGS
Same issue here on 6.1.1. I was getting FC's at first, tried fixing permissions, rebooting all that didnt work. Restored backup with titanium I made of 2.2.6 and it still says 2.2.11 but it doesnt FC anymore so idk
Edit: Reboot started FCing again
solution found!
here's how i've upgrade from 1.8.2 to 2.2.11 on cm 6.1.1 on n1:
- downloaded "zipsigner" (from market, of course)
- select the new market apk (the one that didn't install and fc if flashed througt zip file)
- select "platform" as key/mode
- sign the file
the result apk can be finally installed (no flash, just launch)
all the credits goes to phrozen87 and to kellinwood (zipsigner author)
c3k said:
solution found!
here's how i've upgrade from 1.8.2 to 2.2.11 on cm 6.1.1 on n1:
- downloaded "zipsigner" (from market, of course)
- select the new market apk (the one that didn't install and fc if flashed througt zip file)
- select "platform" as key/mode
- sign the file
the result apk can be finally installed (no flash, just launch)
all the credits goes to phrozen87 and to kellinwood (zipsigner author)
Click to expand...
Click to collapse
Thanks!!! Worked for me! G2 running CM6.1
Heres the signed apk so the rest of you can have it easy
c3k said:
solution found!
here's how i've upgrade from 1.8.2 to 2.2.11 on cm 6.1.1 on n1:
- downloaded "zipsigner" (from market, of course)
- select the new market apk (the one that didn't install and fc if flashed througt zip file)
- select "platform" as key/mode
- sign the file
the result apk can be finally installed (no flash, just launch)
all the credits goes to phrozen87 and to kellinwood (zipsigner author)
Click to expand...
Click to collapse
Thanks!! Now the Android Market Webstore works for my phone!!
Hazzah!!! The posted signed app works flawlessly.
still need to test the web-market store and the updated appbrain.
I added the froyo market to the OP and credited you guys. Good work!
Powers88 said:
Heres the signed apk so the rest of you can have it easy
Click to expand...
Click to collapse
Thank you =D. Worked great
themikeg said:
Hazzah!!! The posted signed app works flawlessly.
still need to test the web-market store and the updated appbrain.
Click to expand...
Click to collapse
it works for me, very cool!
Thank you.
Hi guys, I made a mistake while playing with Smelkus (Ra-supersonic-v4.3-smelkusMOD).
While in recovery, I went into the Developer Menu and entered on the "Install eng (unguarded) su" option, which after rebooting, disabled root access from my EVO. Now, every time I try to get root access I get a segmentation fault error.
I'm using MazWoz 4.2.1 Jelly Bean B4.
Short of re-flashing the ROM, Is there anything I can do to regain root access? I really got it working the way I want it, so I don't want to wipe everything if I can avoid it.
Thanks! Oh, by the way, I made no back up ...(I know, my mistake).
Have done the same thing trying to get SU to work properly with a rom. Easiest way is just to restore a nandroid backup.
Edit: Sorry, earlier it was in the dev section.
connman said:
Have done the same thing trying to get SU to work properly with a rom. Easiest way is just to restore a nandroid backup.
Click to expand...
Click to collapse
Unfortunately, I did not make a nandroid backup for this ROM (been using it for only 2 days!).
Anyway, here's what I did so far:
1)I "Pushed" the Superuser.apk found on the MozWoz Rom to my EVO using "adb."
And it did not work. The superuser application installed properly on my device because I can launch it fine from the app drawer, but it does not give me root privileges.
Any other suggestions?
There's gotta be a way to solving this. Exactly, what does the "Install eng (unguarded) su" option on Smelkus do anyway? Does anybody know?
Krazy4evo said:
Unfortunately, I did not make a nandroid backup for this ROM (been using it for only 2 days!).
Anyway, here's what I did so far:
1)I "Pushed" the Superuser.apk found on the MozWoz Rom to my EVO using "adb."
And it did not work. The superuser application installed properly on my device because I can launch it fine from the app drawer, but it does not give me root privileges.
Any other suggestions?
There's gotta be a way to solving this. Exactly, what does the "Install eng (unguarded) su" option on Smelkus do anyway? Does anybody know?
Click to expand...
Click to collapse
http://androidsu.com/superuser/
Download the ARM zip, flash in recovery. You also need the binary and not just the apk. That's why it still didn't work. If it still fails after this then clean wipe and flash ROM again.
Sent from my Galaxy Nexus using xda premium
the.emilio said:
http://androidsu.com/superuser/
Download the ARM zip, flash in recovery. You also need the binary and not just the apk. That's why it still didn't work. If it still fails after this then clean wipe and flash ROM again.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I flashed the ARM zip files with varying results, but none gave me root access.
Anyway, the only way I gained access was to reflash the ROM....
I hope this saves time for any one who's ran into this issue. Nothing but flashing the ROM seemed to work.
Krazy4evo said:
I flashed the ARM zip files with varying results, but none gave me root access.
Anyway, the only way I gained access was to reflash the ROM....
I hope this saves time for any one who's ran into this issue. Nothing but flashing the ROM seemed to work.
Click to expand...
Click to collapse
Glad that you got it figured out.
Like the.emilio said, there are two parts to the SU. You had just downloaded the apk (the app) but that needs the binary (instructions) to work.
I would have thought that the ARM files would have done this.
At any rate, you're back and working, so that's good news. My advice would be to now go make a nandroid backup. That way as you discover and play with this new rom, if you break something, you can easily return to a known "good" state without too much hassle.
Saved my bacon more than once over the years.
connman said:
Glad that you got it figured out.
Like the.emilio said, there are two parts to the SU. You had just downloaded the apk (the app) but that needs the binary (instructions) to work.
I would have thought that the ARM files would have done this.
At any rate, you're back and working, so that's good news. My advice would be to now go make a nandroid backup. That way as you discover and play with this new rom, if you break something, you can easily return to a known "good" state without too much hassle.
Saved my bacon more than once over the years.
Click to expand...
Click to collapse
I barely ran the ROM for 2 days before realizing I had not made a backup -lol!
My guess is that Smelkus was intended to be used with GB, so it created ROM root privileges that were different from later version of su? Maybe Smelkus needs to do a kernel check before enabling certain options?
Anyway, it's great to be back. And yes, I made a backup shortly after getting everything to work.
Krazy4evo said:
I barely ran the ROM for 2 days before realizing I had not made a backup -lol!
My guess is that Smelkus was intended to be used with GB, so it created ROM root privileges that were different from later version of su? Maybe Smelkus needs to do a kernel check before enabling certain options?
Anyway, it's great to be back. And yes, I made a backup shortly after getting everything to work.
Click to expand...
Click to collapse
Hmm. I'm running Smelkus in Provision/Jellyvision, which is a JB rom (great rom, by the way and very stable on our Evo). In fact, smelkusmod was recommended by the developer of Provision/Jellyvision as the recovery. It's based on AmonRA, so should be pretty compatible regardless.
Install unguarded su installs some old superuser hack as the su binary. Not sure what it was for, but it had a purpose at some point. The regular "Install or fix su & superuser" choice installs a normal (but quite old) version of the superuser.apk and binary and sets their permissions. Both should be avoided at this late stage of Evo use. I think Diablo updated to SuperSU on his version, but if you need to install Superuser (koush), SuperSU, or SuperUser it would be better to use the latest version of their respective flashable zips.
Recovery is entirely separate from the ROM and kernel you are running, so it doesn't matter if you have Jelly Bean, ICS, GB or even Android at all for that matter. All recoveries - stock, CWM, TWRP, RA, etc - are basically a mini-OS with their own kernel and init. It boots and runs the program, recovery. Recovery then executes built in commands and scripts included with it. When a ROM developer recommends a recovery, they are just promoting what they like. Any recovery can do the job in their own manner.
In your case, after installing that unguarded su, you could have done any of the following steps to recover:
Flashed a current Superuser zip if it was already on your phone
adb pushed one and flashed
Booted up the ROM, downloaded one, go back to recovery and flash
Flashed the ROM and gapps again, wiped cache and dalvik and rebooted
Restored backup if available
I've been trying to get Viper4Android driver installed but it keeps failing.
I've tested CM11 and Stock but no go when I hit install driver. I'm guessing it may have something to do with SE Linux as I have to set it to permissive but haven't had any luck with trying to change it as apps do not detect it.
Just looking to see if anyone else had any luck with the app on their Fire Phone?
I had it working without problems on CM-11. SELinux is disabled on that ROM, so no drawback here, no need to change anything...
Before I annoy you with more stories, tell us which file you used exactly to install V4A on your device.
I had to use SELinuxModeChanger on other devices (they used "enforcing") because they didn't offer a setting to change the SELinux mode.
Bingo Bronson said:
I had it working without problems on CM-11. SELinux is disabled on that ROM, so no drawback here...
Before I annoy you with more stories, tell us which file you used exactly to install V4A on your device.
Click to expand...
Click to collapse
I've reviewed the following thread
http://forum.xda-developers.com/showthread.php?t=2191223
I've tested 2.4.0.1 & 2.3.4.0 but can't install the driver. I have BusyBox Pro installed and running and reviewed the logs in SuperSU but i have no idea whats going on when I try the driver install.
Screenshot of Super SU Log: http://postimg.org/image/wdhvthr73/
I am currently back on CM-11 if you have any steps for me to try...
Kerrona said:
I have BusyBox Pro installed and running [...] I am currently back on CM-11 if you have any steps for me to try...
Click to expand...
Click to collapse
Hm, well that's interesting... I also used Stericson's busybox (non pro) and it worked right away... (I also used "ViPER4Android_FX_v2401_A4.x-A6.x.apk")
Maybe reinstall busybox... why isn't it able to find the "toolbox" / why is it calling the path with failsafe?
I see you have some security / privacy / permission tools running... can't really vouch for a hassle free install in such an environment.
You could try to flash this zip from safestrap recovery, this worked for me on other devices and the driver is already integrated, no need for a separate install from within the app.
This has something to do with superSU Binaries updated from normal method, if you have updated super su from playstore then you have to wipe the system partition reflash the rom and latest superSU zip. Otherwise you can flash the pre-build V4a zip as suggested above.
Thanks guys.
I got the driver installed and enabled now with the flash version.
Will probably wipe and start fresh and try the apk again.