• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [ROM] PACE 4.3: Pure Android, CAF/CM Enhanced

tdm

Android Expert
Announcing PACE and PACE Plus for vs920.
PACE

This is pure AOSP plus with just enough CAF/CM enhancements to get it to run on a variety of hardware.

Download:

Beta 2:
pace43-vs920-beta2.zip
md5=1cf5d44b92c191b6dded83c93cc538dc

Superuser (SuperSU):
superuser.zip

PACE Plus

This includes a few enhancements:

* Built-in SuperSU
* Gesture (swipey) keyboard
* Custom boot animation
* Theme support
* Density (DPI) changer
* Built-in adfree hosts
* Quick settings pulldown
* ... more to come ...

Download:

Beta 1:
paceplus43-vs920-beta1.zip
md5=fb98f8093c2faf09725bb848239e23c7

Known Issues:
* LTE only turns on after reboot.
* LGE logo appears briefly after first time setup.
* Baseband version is unset due to lack of busybox.

Source:
github.com/pacerom
 
I am coming from the latest CM nightly (cm-10.1-20130922-NIGHTLY). I wiped everything and flashed this along with the latest GAPPs. My 4g works!
Thank you, tdm!
 
I am coming from the latest CM nightly (cm-10.1-20130922-NIGHTLY). I wiped everything and flashed this along with the latest GAPPs. My 4g works!
Thank you, tdm!

Gaaaah! I'm soooo confused now lol.

I'll need to diff the cm10.2 and pace43 telephony files to see if I can figure this out.
 
OK, I have found one problem so far. It doesn't seem to want to take any pictures. I activate the camera and everything seems normal until I actually take the picture. Nothing happens. Back button won't take me out - gotta hit the home button to get out of it.
 
OK, I have found one problem so far. It doesn't seem to want to take any pictures. I activate the camera and everything seems normal until I actually take the picture. Nothing happens. Back button won't take me out - gotta hit the home button to get out of it.

Okay thanks, I'll look into it.

Edit: works fine for me, both front and back cameras. Anyone else having camera issues?
 
Gaaaah! I'm soooo confused now lol.

I'll need to diff the cm10.2 and pace43 telephony files to see if I can figure this out.
Diffing those two wouldn't do anything as he was coming from CM10.1, not CM10.2. He did the exact thing we've all done which is get the telephony.db built and then flash over the system. In all honesty, it may just be easier to build an update.zip that creates a proper telephony.zip for VZW customers until CM gets their CDMA issue fixed.
 
when I originally went from 10.1 to 10.2, I lost the 4g. so I assumed it would happen again this time. in both instances, I did the full wipe prior to flashing. I am really not trying to be difficult! :-)
 
Can you guys think of any reason why I might have lost my root?

What do you mean by lost root? There is a su binary in the ROM (and it works) but no super user app. If you have installed a super user app and it doesn't work, I can look into that.
 
when I originally went from 10.1 to 10.2, I lost the 4g. so I assumed it would happen again this time. in both instances, I did the full wipe prior to flashing. I am really not trying to be difficult! :-)
OK, now I'm really lost. So you're saying you have CM10.1 , Wiped and did not leave recovery or rebooted your phone, but immediately flashed PACE and LTE worked? I ask, because if you rebooted CM10.1 at all, even if you did not enter any info in, it would create the telephony.db .
 
Long time lurker. First time poster. Decent experience with android flashing on tabs and Verizon type phones. This rom made me lose root also. Can't use any root requiring apps like Rebooter (to go into recovery mode), ES File Explorer (in root mode to delete system apps), Busybox, etc.

Camera works front and back fine for me with photos taken without issues or FC's. 4G LTE/3G/CDMA can be obtained with reboot after initial signal loss. Rom works fine and stable otherwise. I came from 10.1 9/22 nightly. Thank you for your hard work. I'm using TWRP 2.6.0.0 with 4.3 Gapps
 
  • Like
Reactions: tdm
Did you guys install a super user app? I will definitely put one into the plus version.
 
Oh and I think sources are all up except device and vendor. I'll get those up tomorrow and then start in on the plus version. But some time soon I'll need to redo the telephony repo... it's missing exynos support and others will want that.
 
What do you mean by lost root? There is a su binary in the ROM (and it works) but no super user app. If you have installed a super user app and it doesn't work, I can look into that.

Downloaded superuser(chainsdd) and still no root. Says binary not found.

Was on aokp(wasn't using gapps) wiped all 3 and 4g has worked flawless. Hasn't dropped to 3g any. battery life seems decent so far..

Camera when taking a picture to post in the facebook app makes the screen look like the old video bug. But goes away only when hitting the home button. Dunno if that's phone or Facebook related
 
  • Like
Reactions: tdm
Sorry for not reposting right away... I've been reinstalling the ROM and doing everything I can think of. I'm on the same boat as bones... I had superuser installed when I last posted, I just kept getting that error that I didn't understand so I'm glad he could actually explain it.

I just need it to run seeder and ROM toolbox .
 
I downloaded the file from the link above again just to check and no dice.... Still says the binary can't be found

I do have full 4g as is reported by others
 
For Superuser, the easiest way to get that back would be to flash the SuperSU zip from Chainfire located here. Just flash it from recovery and you'll have root back automagically.
 
For Superuser, the easiest way to get that back would be to flash the SuperSU zip from Chainfire located here. Just flash it from recovery and you'll have root back automagically.

Thanks for the link, just what we need. Unfortunately, that seems to rely on install-recovery.sh, which isn't called.

To fix, tack this on to the end of /system/etc/init.qcom.post_boot.sh:

Code:
if [ -x "/system/xbin/daemonsu" ]; then
    /system/xbin/daemonsu --auto-daemon &
fi

That is specific to SuperSU. Koush's superuser doesn't have a separate daemon binary, the main su binary has the daemon functionality built-in. So you would do this instead:

Code:
if [ -x "/system/xbin/su" ]; then
    /system/xbin/su --daemon &
fi

Does anyone know what happened to Superuser by ChainsDD? It seems to be outdated and unmaintained.
 
A few times the status bar has got stuck about 1/4-1/2inch from the top and the carrier label changes to "311480". And sometimes after a reboot the number stays there.
 
For Superuser, the easiest way to get that back would be to flash the SuperSU zip from Chainfire located here. Just flash it from recovery and you'll have root back automagically.

After flashing that this is what I get when opening supersu
 

Attachments

  • uploadfromtaptalk1380315110615.jpg
    uploadfromtaptalk1380315110615.jpg
    77 KB · Views: 176
Back
Top Bottom