Search results

If one takes the P stock ota does that update the radio, vendor, bootloader for us?

Because the latest supersu modifies the bootimage for root. So just remember to re-bump it: MR_Boot.zip - all credits to dadi11

Try this: rm prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.15-4.8/x86_64-linux/bin/ld ln -s /usr/bin/ld.gold prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.15-4.8/x86_64-linux/bin/ld

ice.modding that doesn't seem like an error specific to Arch Linux, looks more like an error syncing & lunching. Not sure you can build on Arch right now without some major work arounds as I get this...

Is the 2nd post still up to date & correct even on mm roms? Since I saw mm has its own support for layers has that changed which commits are needed, for example I want to build omnirom-6.0 with layers are all of those still required?

Did I read the op wrong or atm this is so new the bumped twrp setup we were using on prior versions can softbrick your device atm if one flashes this and then tries to switch to another mm rom?

Sorry if this has already been said/explained but is this meant to be flashed over stock rom or by itself?

there was a fstab issue with external sdcards, the fix has been merge already though.

I'm on windows 8 / arch linux and I couldn't get the rsa adb pop-up on my phone until I had verizon's g3 drivers, and the latest android-sdk installed. With the phone in ptp-mode adb saw it and connected normally.

Be sure to flash an older firmware if you're on an vzw G3 or else it'll just sit at the verizon logo after rooting and rebooting. Edit just manually flash the LP firmware: http://forum.xda-developers.com/verizon-lg-g3/general/vzw-vs985c01-kdz-t3077799 then flash if your still on stock to avoid a...

Tried purpledrake on arch linux with a verizon G3, it failed and here's the output. Press [enter] to continue... Waiting for device... . Found device! ./assets/linux64//adb: /usr/lib/libcrypto.so.1.0.0: no version information available (required by ./assets/linux64//adb) ./assets/linux64//adb...

Any chance of a LG flashtool for linux?

If we recently purchased our LG G3 don't we/I still need to downgrade the software to root and unlock? As my software .v is KVT49L.VS98512B. Their latest kk build.

edit nevermind sorry for necroposting

Hello, I smashed my razr @ work so I'm back on my xperia play as a backup for a bit. But I can't seem to boot into jb pa or cm9 from this cwm http://forum.xda-developers.com/showthread.php?t=1493996. Am I just using an incompatible cwm recovery?

Could someone mirror the fastboot diver files for me? I can't seem to DL them from 4shared.

A little curious why you just have the option to backup to pc and not backup to internal or external sd card? Or is that just an older picture I'm seing? Looks good though.

Hmm I guess not.. I don't know how I never uploaded older builds of jbbl or I must of removed them to not clog storage on drdevs.. Sorry about that but I guess not :(. All the more reason to be extra descriptive of bugs you find and I'l try to fix 'em.

Yeah I'll proably make another build for both for kk. But it'll be the last one now that lollipop is out. And yeah I'll be trying to keep msm8960 and msm8960_jbbl up to lollipop once the merges have been merged (don't hold your breath it'll take a while). Edit- new kitkat builds are up on...

*** *** Can't find default configuration "arch/arm/configs/cyanogenmod_endeavoru_defconfig"! ***

On mobile you need to have + use mega's app to download (didn't know that or I wouldn't have used the website but its free atferall). And I re-did the mega links so it points to the msm8960 or msm8960_jbbl builds.

Nope, card recents and dsb are both still private to pa so you'll need an official build to use those features. Once they're released to the public they'll be on aospa-legacy's github and then they're be in both types of builds.

The OP obviously :P also made it clear which ones are built by the team (official) or me (unofficial).

The mega.nz.co link has more builds for _jbbl devices btw. But I should have a new build going up for both tonight/ tmr morning (note Quiet hours & QuickSettings swipe to switch are changes made by me DON'T ask or expect them to get merged into official builds cause they won't.)

I made a new kernel rebased from cm's I felt as many of my changes were un-needed NOT for jbbl users its fresh outa the oven. Not sure if it'll make a difference on battery life (probably not if I had to say).

They should be fixed in both, I need to find out why my builds on the newer bootloader doesn't have the fcs the jbbl builds are.

Also since your device isn't supported you'll want to add your device to the listed products under vendor/pa. So you may want to create another manifest under .repo/local_manfiests/something.xml and replace pa's vendor with your modified one.

They're not buggy on purpose its probably things from cm that need to be corrected for pa and our device. I was just giving an alternative if official builds aren't stable, as for the twitter bug are you using their official app? Try using another 3rd party one I use tweedle and can't re-produce...

NP Also, if anyone wants to, on my most recent builds on the mega.co.nz mirror I've added the smart dialer from omni. When your in a text convo or a number typed in to the phone dialer and hold it to your ear it will call the number in the dialer or the person your texting. Only with the aosp...

As long as its already in aospa-legacy all you need to do is repo init & then ./rom-build.sh your device's code name. Then it'll pull in the extra repos from its dependencies & build.

If the official legacy 4.6 builds are a little buggy try my builds of 4.6 they don't have the alpha recents and are almost always stable since they only have the most recent public code. Newer msm8960 build should be up later but _jbbl failed for some reason that might have to wait till the...

Have you tried clean flashing it?

The moto_msm8960 builds were meant to be one build that would work on multiple moto devices since they're so similar hardware wise ( op/1st post has link showing what devices this includes). But moto screwed us over when they decided only half the these devices would get updated to 4.4.2.

I just fixed jbbl builds, I derped the vendor files for it when I first uploaded it now its fixed. Also here's an update to the changlog copied from the updated 2nd post: Do note it will take longer to see the latest features as legacy devices take longer to be built cause there's a bit of a...

Yeah I keep forgeting to update the changlog wifi and speakerphone are fixed. And jbbl support is on gerrit waiting to be merged.

Changlog is in the 2nd or first post, though I haven't really been keeping it up to date I should be fixing that later as well as adding support for msm8960_jbbl which will be the builds for the motorola devices that don't yet or won't be getting the 4.4.2 offical update from motorola so they'll...

Atm its only kitkat I think our device tree needs some tweaking before jbbl builds are made. Btw do you guys know it razr m builds are coming out okay?

Really? Before I had an account they would let me download without needing to log in. Let me logout and see what you mean. Edit- Whoops, forgot to use the share link and give the keys with it. Should be okay to DL without signing in now.

Only issues I've had on 3.4 kernel are wifi disconnecting randomly where stock was fine, and a weird poping noise in the rear speaker. The poping noise should be gone as there was a specific commit on the kernel for it idk about wifi as I'm still uploading my build from last night and havn't...

Edit, you guys just need to google harder. and learn to run rm ~/.repopickle_.gitconfig

Building again, should be up & ready by morning hopefully. And please keep remix discussion in the remix thread. I know you're just stating they share issues but I don't want a bunch of people in here talking about remix. I think the wifi and BT issues could be bugs with the new kernel...

The two pa_moto_msm8960-4.41 builds are for the 3.4 kernel/ 4.4.2 bootloader the rest are for the older jb one. The easist way to update is to grab a copy of the 4.4.2 firmware and flash it via rsdlite. Check the general section for links/ guides on it.

Edit- nothing to see here.

Yeah it looks like it, since the 3.4 kernel relies on the newer bootloader.

jblaylock I see a lot of errors about facebook, try rm'ing it or try another app to browse fb as its actually garbaging up your log. Otherwise I would say the gps issue is that the place is stored was changed but not updated in the device config, so use an older version that has it working it...

I would say yes, but when I'm not sure as those patches have yet to show up on cm's git and then they'll be pulled into pa-legacy. Once its confirmed to be added I'll add a heads up to the op since I know they'll be ppl who update and forget to update the bootloader first and wonder what the...

null

And google removed tablet ui so that won't be coming back.

I've added my gerrit username to my local config & sshkeys to the server and I'm trying to figure out why the publickey is being denied: https://gist.github.com/cj360/f091452db409451819b2 (blah blah is not the actual commit info).

rm -rf prebuilts/misc/common/ub-uiautomator as cm has added a prebuilt for it there but now fw-base can build it from source too so it sees the confilct and errors out.