• 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

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

How do I do this without root access?:(

We need a flashable zip file to fix root.
 
tdm said:
Does anyone know what happened to Superuser by ChainsDD? It seems to be outdated and unmaintained.
Click to expand...

I think that development on it was stopped partly because of the rising popularity of SuperSU and partly because Koush decided to help integrate Superuser into CM.

Also, what build parameters are you using when you start compiling? Are you setting it as a user-debug or a regular build? I haven't actually been able to mess with this so that's why I ask.

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

How do I do this without root access?:(

We need a flashable zip file to fix root.
Click to expand...

You may be able to do this with adb from recovery. I could be wrong though. Unfortunately, I'm not going to have access to a PC this weekend or I would test it myself.
 
ortrigger said:
Also, what build parameters are you using when you start compiling? Are you setting it as a user-debug or a regular build? I haven't actually been able to mess with this so that's why I ask.
Click to expand...
I just got the device trees up and I'll be adding them to the manifest shortly.

You will need to init with the groups option, using groups "-g all,-notdefault,vs920" (I think that's right). The target will be full_vs920-userdebug.


ortrigger said:
You may be able to do this with adb from recovery. I could be wrong though. Unfortunately, I'm not going to have access to a PC this weekend or I would test it myself.
Click to expand...

Yes you can do it from recovery or from adb. Either way, pull the file, edit it, and push it back.

Or just wait a bit .. I"m preparing an updated ROM right now with built-in support for starting the superuser daemon. It should work with both chainfire and koush versions.
 
Also I hope I'm not coming off pushy...I just wanted to make you aware of any odd happenings if I notice them before others :)

BTW I love everything all you guys have done
 
  • Like
Reactions: tdm
Monkeyzluck said:
Also I hope I'm not coming off pushy...I just wanted to make you aware of any odd happenings if I notice them before others :)

BTW I love everything all you guys have done
Click to expand...

Not at all. The goal is to have a smooth experience so let me know what you see. I an particularly in the dark about radio stuff because I don't have vzw service.
 
So just FYI... the superuser zip is the current supersu with a modified installer that doesn't do the install-recovery hack.
 
Great work on this ROM TDM. As many others have said, 4G worked out of the box and I probably would have stayed on it except for the SU issue and me being at work at the time. I look forward to flashing this SU fixed version.
 
  • Like
Reactions: tdm
Does not compute...

After taking a full nandroid and wiping everything but sdcard, I install beta2 then the 8/13 gapps. When I reboot 4g is good, but no market, no gmail, etc. Reboot recovery reflash gapps same thing. Fix perms same. Checked md5s and everything is fine. Ideas? Also, flashing the supersu.zip gives me an error regarding executing the contained binary

More fuel for the fire... Restoring my nandroid fails on /system every time. Fwiw, I'm running twrp 2.6.0. Anyone else have this working with twrp? What version? Everyone using cwm?

Thoughts? Sound familiar to anyone?
 
nathanhaywood said:
Does not compute...

After taking a full nandroid and wiping everything but sdcard, I install beta2 then the 8/13 gapps. When I reboot 4g is good, but no market, no gmail, etc. Reboot recovery reflash gapps same thing. Fix perms same. Checked md5s and everything is fine. Ideas? Also, flashing the supersu.zip gives me an error regarding executing the contained binary

More fuel for the fire... Restoring my nandroid fails on /system every time. Fwiw, I'm running twrp 2.6.0. Anyone else have this working with twrp? What version? Everyone using cwm?

Thoughts? Sound familiar to anyone?
Click to expand...

Don't know that's really weird. Check the md5 for everything.

I dirty flashed beta2 then gapps then superuser and rebooted. Worked here, but can't speak for data of course.
 
I'm hoping beta2 is fairly stable and complete now. And the sources should all be synced and buildable for you ROM hax0rz.

So now it's time to start thinking about the plus version. Get your votes in for favorite features and I'll try to oblige. But I won't do anything too intrusive like halo or pie or ribbons. First up is going to be a density setting, custom power menu, quick toggle pull down. Other requests?
 
Beta2 works great. Rooted too!!! Thank you. If Gapps doesn't take, wipe all and reflash ROM and Gapps. It will eventually work.
 
  • Like
Reactions: tdm
FYI: Used the e2fsck commands from Neph's TWRP post and found out that both blk27 and blk28 (/cache and /data, I believe) were corrupted. Tried to use the e2fsck commands, cleaned 26 and 27, but 28 seems to be so far gone that TWRP reboots mid-repair. Tried to mkfs and reflash but still misbehaving.

Going back to the LG Mobile Support tool to cab flash. Been a while since I've had to unlock/root from stock. Anything change lately on that front? Wish me luck!

If all goes well, I'll be unlocked, CWMed (or TWRPed), and back to flash beta2 ASAP.

PS: Noticed the old T-Mo carrier label was back while I was briefly up on beta2. Was that a corruption issue on my part or a reversion from CM in your build, TDM? I think I remember your old unlocked bootloader/kernel having the same issue (maybe fixed), but definitely fixed in CM 10.x
 
nathanhaywood said:
FYI: Used the e2fsck commands from Neph's TWRP post and found out that both blk27 and blk28 (/cache and /data, I believe) were corrupted. Tried to use the e2fsck commands, cleaned 26 and 27, but 28 seems to be so far gone that TWRP reboots mid-repair. Tried to mkfs and reflash but still misbehaving.

Going back to the LG Mobile Support tool to cab flash. Been a while since I've had to unlock/root from stock. Anything change lately on that front? Wish me luck!

If all goes well, I'll be unlocked, CWMed (or TWRPed), and back to flash beta2 ASAP.

PS: Noticed the old T-Mo carrier label was back while I was briefly up on beta2. Was that a corruption issue on my part or a reversion from CM in your build, TDM? I think I remember your old unlocked bootloader/kernel having the same issue (maybe fixed), but definitely fixed in CM 10.x
Click to expand...

I thought the carrier label was resolved long ago. I'd chalk it up to the corrupted partitions. Let us know how it goes after the cab flash...
 
Beta2 works fine and flashed fine for me. I'm on TWRP 2.6.0.0 also. Once root was resolved, I put on V6 Supercharger script using SManager Free apk, Baseband ZV8 zip, Crossbreeder zip without issues. Beta2 is my daily driver and I was on call as a GI physician without issues. 4G/3G works flawlessly. Wifi is strong without issues. ROM is light and fast once optimized. I also use DxTools 3.3.5 and SuperManager to keep RAM optimized. I usually have 400-500 MB RAM free on the phone. All major apps seem to work fine (Amazon App store, few games that I tried, Pandora, Google Music, Google play store, Maps, GPS, Rebooter, screen off apps, Startel Secure Messaging, Iodine Secure Messaging and Hospital access app, regular SMS and MMS texting, phone calls, speaker phone, No frills CPU manager (running 384 min, 1080 max, noop/conservative for battery life), Touch2Dial, on Extended batteries (charges fine for 2 chinese 3800 mAH batteries--one orange/white label and one black/white label). I love it. Stable as CM10.1 nightly I was using before. No FC's, no freezes, just smooth sailing. Thank you for reviving this oldy but goody phone. I'm stuck with this phone until 2/14 contract on Verizon (I bought 2 on Ebay). Drowned my HTC Rezound in toilet :)
 
  • Like
Reactions: tdm
Able to get up and running after cab flash and pwnage. Also wiped sdcard (and repartitioned in twrp) and redownload all zips. Still got a "warning: no file contexts" during pace install, but reports success. Able to install gapps and supersu and both worked when I rebooted.

For some reason, carrier label was still showing the T-Mobile label. Wiped and flashed back to cm 10.1.3 and the carrier label is back to Verizon Wireless. I did go straight from stock V8 to pwnage to PACE beta 2. Can anyone with VZW service confirm their carrier label and what they flashed from?
 
nathanhaywood said:
Able to get up and running after cab flash and pwnage. Also wiped sdcard (and repartitioned in twrp) and redownload all zips. Still got a "warning: no file contexts" during pace install, but reports success. Able to install gapps and supersu and both worked when I rebooted.

For some reason, carrier label was still showing the T-Mobile label. Wiped and flashed back to cm 10.1.3 and the carrier label is back to Verizon Wireless. I did go straight from stock V8 to pwnage to PACE beta 2. Can anyone with VZW service confirm their carrier label and what they flashed from?
Click to expand...

The file contexts warning is normal but harmless. I haven't implemented selinux (and don't know if I will).

The carrier label is controlled by the eri. xml file, I believe, and I'm using the same one as ever. Maybe I can poke around Monday to see if I can figure out your problem.
 
Has the battery life issue been fixed in 4.3? The phone not going into deep sleep properly?

I switched back to icy fusion from CM a while back, and I am getting the best battery life I've ever had. Maybe 3% drop overnight. Wondering if it's worth going back to a non-stock rom.
 
Everything is looking pretty cool. I'm going to have to flash this when I get home tomorrow night. I recently dumped Big Red though so I won't be much help in debugging any issues with data.
 
Clean flash, 4G came on during setup, didn't have to reboot. Everything is working great, no problems with root or SU, do miss the quick toggles though!
 
tdm said:
So now it's time to start thinking about the plus version. Get your votes in for favorite features and I'll try to oblige. But I won't do anything too intrusive like halo or pie or ribbons. First up is going to be a density setting, custom power menu, quick toggle pull down. Other requests?
Click to expand...

Definitely the quick toggle pull down, and I like the brightness slider on the status bar, or in the pulldown would be OK.
 
I vote for advanced power menu and quick toggle buttons in the pull down menu. Maybe built in wifi tether if that's easily do able.
 
You must log in or register to reply here.
Back
Top Bottom