[ROM] BarePapA - ZVA

[cabbieBot]

It must be. But don't install it! You'll risk losing root/unlock!

LISTEN TO THE MAN! Do NOT install it! I've never even heard of an OTA -not- eliminating root. Just seeing that OTA notification freaks me out, I treat it like a live bomb that could blow up in my hand.

To be on the safe side, we need to wait for @autoprime to have a look at it. Or come up with either the tot/img files.

How is this done, by the way? I'd like to take a look at it.

---------- Post added at 12:48 PM ---------- Previous post was at 12:45 PM ----------

So is this a new update for our phones?

This link will tell you what you need to know. The update I got (and which you'll be getting soon enough) is basically an emergency hotfix for a nasty lil security hole in the Android OS. Don't expect new features or anything except maybe some minor bug fixes . . . this is 99.99% a security patch.

Vast Majority Of Android Devices Are Vulnerable To 'Stagefright' Exploit That Can Be Executed Via Text Message, According To Researchers

 

[engine95]

How is this done, by the way? I'd like to take a look at it.

---------- Post added at 12:48 PM ---------- Previous post was at 12:45 PM ----------



This link will tell you what you need to know. The update I got (and which you'll be getting soon enough) is basically an emergency hotfix for a nasty lil security hole in the Android OS. Don't expect new features or anything except maybe some minor bug fixes . . . this is 99.99% a security patch.

Vast Majority Of Android Devices Are Vulnerable To 'Stagefright' Exploit That Can Be Executed Via Text Message, According To Researchers

I don't know what to look for, but autoprime is part of the root team. He seems to be our link to them. And I trust him wholeheartedly.

There are ways to avoid the issue which are posted all over the web. So for me, I'm not that concerned. And I'm in no hurry for the update.

I'll put a stock rom together when we get the tot/img. Unless someone else does it before I get the time.

 

[cabbieBot]

I gotcha. Are you getting one of the new Nexus devices being announced in a few days, or stickin with ol LS990? I'm probably moving on myself . . . I sort of got stuck with the G3 because I lost my Nexus 5 and have been waiting to get back into the sweet motherland "fastboot oem unlock". LG's double-tap to wake and rear volume buttons/cameras have really spoiled me, I'm going to miss those a lot. But f-u-c-k bumped bootloaders, I want the pure stuff in my veins. Regardless, your ROMs and kernels have made it a fun detour so thank you, sir, for providing me many hours of fun tinkering over the past year. My only regret is that I never did find a foolproof way to completely defeat the LG Cliptray, much to my dismay and shame. God I hate that thing with the heat of a thousand suns. It's always baffled me how you folks seem okay with that crapware. If for some reason the fates decide to torture me, and something similar to the cliptray ends up being an unremovable part of stock Marshmallow, I'm just going to say eff it and get a Palm Pre. ¸¸♬·¯·♩¸¸♪·¯·♫¸¸WebOS, I'm comin home to you.¸¸♬·¯·♩¸¸♪·¯·♫¸¸

 

[engine95]

Thank you.
Palm Pre!? I LOVED that phone! I wish I still had it, many a time. To bad HP couldn't use WebOs properly.

I've still got a few months left, so ill see what comes out then. I'm actually pretty happy with this phone as I have old eyes. As for the clip tray, I just deal with it, but it has been handy a time or two.

 

[geeksmurf]

Former Palm Pre'er also. I miss that little thing so much. But my eyes sure don't miss how small it was. I'm kinda excited by the new Android BlackBerry.

 

[autoprime]

It must be. But don't install it! You'll risk losing root/unlock!

To be on the safe side, we need to wait for @autoprime to have a look at it. Or come up with either the tot/img files.

thanks for the heads up.

after a quick look.. it looks like it was mainly for stagefright. I can confirm that anti-rollback has not been used in this update (like flex 2 and g4) so people who take this ZVB update will be able to downgrade or use the ZVA TOT etc without any worry.

can't confirm if the current root method is blocked or not BUT Codefire has adapted a newer method that we use on the G4.. still using download mode to root. I am positive that the G4 method will work to root the device (worst case). It's possible the current method y'all are using would still work but hard to say without actually poking around on the device.

after some more poking around.. seems the old root method isn't going to work. I could make a hybrid root method that uses the newer Sprint g3 1-click... and incorporating some elements from our G4 method... could be risky... but it depends.

Using the current G4 method as is... it'd require someone dump the ZVB system.img.. root it using Linux.. then uploading it for all to use. Then the users would flash the pre-rooted system.img thru download mode (our current g4 method).
Here's our root thread - http://forum.xda-developers.com/g4/orig-development/root-tmo-vzw-intl-variants-soon-root-lg-t3164765

but since no anti-rollback is being used... I'd say this is a safe update. downgrading is possible via TOT. But there won't be a root method for a lil bit.

Let me test some things and see if I can get around needing a pre-rooted .img.

also thanks to @cabbieBot for pulling the update.zip. it's always nice not to have to hunt around for the update myself.

 

[engine95]

@autoprime. Do you think the way we've been keeping root for ZV8, ZVB will still work? Just using the img files from the. tot? As that's just a bootloader workaround, right?

Thank you for looking into this. VERY MUCH APPRECIATED!!

 

[autoprime]

@autoprime. Do you think the way we've been keeping root for ZV8, ZVB will still work? Just using the img files from the. tot? As that's just a bootloader workaround, right?

Thank you for looking into this. VERY MUCH APPRECIATED!!

how were u previously "keeping root" ? by just flashing the system.img thru twrp then flashing supersu zip or having twrp root you? instead of taking the OTA? if that's what you mean then yes it should work still.

if not.. can you explain? I've been living in G4 world trying to keep up with LG.. so not sure what G3 users are doing anymore. All I've done was take a look at the modded script people were using for ZVA which looked like it was flashing a downgraded download mode (laf) while in download mode.. then flashing a root script in the downgraded download mode. But that seems to not work anymore.

 

[engine95]

how were u previously "keeping root" ? by just flashing the system.img thru twrp then flashing supersu zip or having twrp root you? instead of taking the OTA? if that's what you mean then yes it should work still.

if not.. can you explain? I've been living in G4 world trying to keep up with LG.. so not sure what G3 users are doing anymore. All I've done was take a look at the modded script people were using for ZVA which looked like it was flashing a downgraded download mode (laf) while in download mode.. then flashing a root script in the downgraded download mode. But that seems to not work anymore.

Something like that. Honestly, I can't remember for sure until I sit down and do it. And I've done it 3 times now. Lol I do it all on my phone, then pull the system.img.
I'm pretty sure I'm using the .tot to do it though.
I need to go through all my messages and see how I've explained it to others in the past. Getting old sucks.

I understand about the G4 stuff. I've been reading on it. So no need to apologize.

 

[autoprime]

Something like that. Honestly, I can't remember for sure until I sit down and do it. And I've done it 3 times now. Lol I do it all on my phone, then pull the system.img.
I'm pretty sure I'm using the .tot to do it though.
I need to go through all my messages and see how I've explained it to others in the past. Getting old sucks.

I understand about the G4 stuff. I've been reading on it. So no need to apologize.

if you already have twrp installed on the phone... then yes you could flash the ZVB system.img as well as a bump'd ZVB boot.img.. while staying on the older bootloader.

but for those who update to ZVB via OTA or some other method.. they will need to either downgrade and use a proper root method for the downgraded sw version... or wait for new root method (g4 method.. just needs some tweaks for sprint g3).

I'm assuming there are still some LS990 users who want root.. but do NOT want TWRP.. so they will be the ones who most likely want a new method. while anyone already on twrp just needs to wait for system + bump'd boot. There are some other ways to go about it.. but they can get a little more risky and it's not worth the trouble.

gonna watch a little tv and relax for a bit.. but I'll get the updated root method sorted.. along with something for the current users already on twrp... and yourself so you have a new rom to tweak. :good:

I have some thing's I want to test first.. but as long as nothing goes wrong in my tests I should have something late tonight or early tomorrow.

*update*
Got TWRP installed. Things seem to be going as planned. Still work to be done... but this is good new of course.

*update 2*
Methods for stock ZVB users and those already with TWRP all finished... just waiting on some Codefire server updates before I can upload the files. New thread in the Sprint G3 Development section coming soon.

 

[engine95]

Thanks @autoprime I was just working on modifying the update.zip to see if I could get it to work. I'm sure I'll still try it.
But at least you've got a sure-fire way.
Thanks again.

 

[engine95]

ZVB should be out tonight if all goes well. With some sugar added. But should I keep the name? BarePopB? BarePapB? BareBarb? Suggestions?????

V1 will be totally stock, but with....
Init.d support
busybox
increased mixer paths
sd card fix
LG Backup to /data
Sprint VoiceMail to /data

So far.

 

[cabbieBot]

And that "someone" just happens to be ME!
So, I got a wild hair up my butt this morning and said "I wonder if somehow xposed has anything to do with this problem" despite the fact that a friend of mine is running the stock OS that he has ONLY rooted and installed xposed on, and he could install Android Pay without issue.
Anyways, I decided to give it a try...
I went to the Xposed for Lollipop thread and got the xposed-uninstaller-20150831-arm.zip.
Put that on the root of your internal SD.
I uninstalled the Xposed app itself (Settings<Apps<all) just in case, though Im not sure if you even need to. I just did so that I know I was 100% "Xposed-free".
Next I uninstalled Android Pay, so that I could start with a fresh install when going thru the setup, so no past gremlins could possibly be hanging around.
I also went in SuperSU and unchecked the box for 'Enable Superuser' and 'Mount Namespace Seperation'...again, not sure if this is needed, but It was known to cause issues with others so I figured if I'm going thru the trouble to try this one last thing, I may as well uncheck/disable/etc ALL THE THINGS lol!

After that, reboot to recovery, flash the xposed-uninstaller-20150831-arm.zip and reboot.. The update/uninstall will take a bit, so let it do its thing
Now, once you're booted, install Android Pay and go thru the setup.... aaaaaaaaaand IT WORKS!
I then went thru THESE steps to reinstall Xposed and everything still works. Since I didn't uninstall tweaksbox all of my settings and everything were still there so as soon as I rebooted after fully installing Xposed everything was back the way I had it before, and also android pay still open and seems to run as it should....
I haven't actually attempted to tap and pay yet, since I'm at work, but I see no real reason why it won't work.


**UPDATE**
So, when I went thru the setup, since I used the Old Google Wallet previous, it still had my cards stored... all I had to do was put in the security codes from the back of the cards and all was well.
Well, Yesterday I got a replacement debit card to replace one of the cards already on my Google wallet (card was expiring soon). So, I removed the old card, and then went thru the steps to add the new card and...it says "This card can't be use. Your bank doesn't support Android Pay yet"
Ummmmmmmm.... how can that be true?
I had two debit cards on my Google Wallet....both TCF Bank. I removed one TCF card, and tried to replace it with a new TCF card for the SAME account as the one I just deleted...and it says my bank doesn't support Android Pay lol...
Not sure if the Card the that is still on there/it let me add will maybe not work when I actually attempt to use it to pay (since it's supposedly "Not supported" lol) but yeah...
Sadly the card that is still on Android pay is the one to a secondary account that I don't generally use, and the one it won't let me add is my everyday use account... so, even though I now have working Android Pay, it's really of no use to me lmao!
I'm going to leave it installed just so I can go make a test pay to confirm that it's working and report back, but then I think I'm going to end up rolling back my Android Services again and reinstall the Old Wallet app so I can still use both my cards till whenever my bank gets "officially added" haha

I got it figured out as well and so here's my method. I honestly think, though, that its every man for himself out there on this and that what works for one is unlikely to work for another.

Mine does not use XPosed, I don't have it installed. Requires use of SuperSU as your superuser manager and be currently rooted. I am running BarePapA-TE_V3 and NavelA-V1.6.

Download RootCloak Plus (Cydia) and Cydia Substrate from the Play Store.

1. Open Substrate. It tells me "Note: something about your device made it impossible for Substrate to perform its internal safety check; can you please contact saurik via e-mail?". Doesn't seem to effect anything.
   
2. Open RootCloak Plus (Cydia). Here you are going to be adding apps to a list of ones you don't want knowing you have root. There are a bunch of defaults already which you can leave. Add AndroidPay (com.google.android.apps.walletnfcrel). Now beyond that, I went ahead and added a number of other Google Apps and be certain any of them are required, but its what I did. I added the new Wallet app, Google Play Services, Play Store, Google Partner Setup, Google Account Manager, and Google Services Framework. Basically, my reasoning was that given the commitment to blocking rooted devices from using AndroidPay, it'd be useful to cloak any of the other financial apps and core GAPPS as well . . . because who knows how they are checking for root?
   
3. Reboot device.
   
4. Open SuperSU and uninstall superuser.
   
5. Reboot device. AndroidPay now works, buy yourself an Oreo McFlurry with your phone you clever hacker.

Obviously, your rooted apps won't work. So, if you want them back you will have to open SuperSU and reinstall superuser. That is going to break AndroidPay. Each time you want to use it again, you have to repeat the last two steps. So, there's the compromise . . . you can either leave your phone unrooted or have to reboot every time you want to use it.

This was a real PITA to figure out. It took me two days of going into Walgreens, trying to buy something with AndroidPay, it failing, but not wanting to be a total **** I bought it anyway. Then I'd go to my car for about a half hour, tweak things, and go back in for another try. Took about nine to ten tries for it to work, and I now have enough chapstick to last the winter. I've tested it successfully half a dozen times at Walgreen's and McDonald's so far and it is reliable (for me). Annoyingly, I am certain that this won't work on the Nexus 6P I'm getting next month, but I just love you guys that much And it also really really pisses me the **** off when someone tells me I can't do something I want to do with my phone. Shout out to the good folks of Walgreen's for not asking me to leave or calling the police due to my weird and shady behavior.

I want to know if anyone else tries this method. If you do, please post a reply saying whether or not it worked.

 

[memnochlv]

I followed the above instructions and I do have Xposed, still can not verify my cards. Going to try removing Xposed as well. BTW, when you say remove superuser, you mean uncheck it being enabled in SuperSU? I added all the same apps to both RootCloak the app as well as the Xposed module.

 

[memnochlv]

I tried with Xposed removed and still I can't add any cards. Also, I'd read there may be a problem with "unlocked" bootloaders. Would TWRP count / read as an unlocked bootloader?

 

[Srambo217]

I'd go with 'BarePapB' simply for legacy's sake. Changing the name entirely may throw off user who run this as a daily driver but don't visit the boards often.

 

[stopeject]

Is it possible to remove the OTA notification without doing the upgrade?

 

[engine95]

Is it possible to remove the OTA notification without doing the upgrade?

I can't remember how now. But if you look through some of the older rom threads, you'll probably find some suggestions towards the end of the threads.

 

[stopeject]

Found this video https://youtu.be/bUGOKsyb0I8 It worked.

 

[Ripley22]

Alright, I'm begrudingly accepting this. Does the Dialer reset just tend to automagically make things better when all else fails or do we know what it's doing? It would be cool if I could nandroid up, do the reset, and restore the /data partition.

I'm sort of curious if it fixes the other nagging problem I've always had with this phone, across all ROM's including stock. For whatever reason, Google location services likes to think I'm in a town about an hour and a half north of me. I've considered it possibly to be a defective GPS but maybe the dialer reset will sprinkle its fairy dust on the chipset and make that work properly as well. It can be pretty persistent too., as in, I can open Maps looking for quick directions, and I have to do a combination of keeping the app open and toggling the grey 'find me' target until it locks in where I am instead of 70 miles away.

Do you have location set to device only? I had the same problem and changed that to improved location access and magically have pinpoint accuracy. Good luck cabbieBot.

Sent from my LG-ls990 using Tapatalk