Search results

Thanks for this! Works like a charm dual-booting between Lineage and the stock OS for Nethunter. My apologies if this has been asked/answered before, but is there any way to update Lineage using the built-in updater without installing the Lineage recovery or would I have to re-flash this...

Yep, you'd need to flash TWRP via that fastboot command and boot to recovery by holding vol up/power. I put the ROM and gapps files on a MicroSD card which was picked up by TWRP. I had similar problems with the ROM not being compatible after the first failed flash, you should be able to modify...

Sorry it took me so long to see this, but I had similar problems as you initially. It turns out you actually have to install TWRP to the tablet for it to mount /system properly, booting into it from fastboot doesn't work for some reason - that was what fixed it for me at least. It may be...

I haven't heard anything about root, but according to the official forums the bootloader unlock tool should arrive mid-December, so I'd expect we'll see more action around then. https://www.asus.com/zentalk/thread-186959-1-1.html Looking forward to what we can do with this phone rooted.

I purchased this one from Amazon: https://www.amazon.com/gp/product/B074379C84/ Also attached a screenshot of the firmware/radio it's running. I agree though that you're probably better getting one with proper US warranty/support if you can.

I'm actually not sure there's an NA specific firmware for the unlocked model, mine came with the WW firmware and they only have WW and JP listed on the support page. I am picking up LTE bands that they only have support listed for on the "NA" model so I think it may just be a case of poor...

These are from the Unlocked 8GB/128GB model from Amazon running the WW firmware.

I was able to get service on 4 and 13 for Verizon, and 2 and 12 for Cricket/AT&T. It may support more, but I'm not aware of any apps that will let me scan for service on all bands. LTE Discovery mentioned a "Potential eCSFB issue" with the Verizon SIM which is likely because there was no CDMA...

From my testing, the unlocked version will pick up Verizon LTE bands but calls fail since there is no VoLTE option on the phone. Did not pick up any of their 3G signals, and their system would not accept my IMEI as a compatible device. So it may work if you can convince Verizon to add the...

Nope, unfortunately I don't have the setup to easily root these right now. I mainly put these together in the hopes that someone else would be able to do it, or if you just want tethering enabled since that's a simple build.prop tweak.

Here are the files for the AT&T XT1097. Stock package (needed to update): https://mega.co.nz/#!bN0BjKbI!zzq5b9wZBo-XFGNkcWtgw7mnXZgC5BWrEC-GZcGLELo Mofo 5.1 image (stock): https://mega.co.nz/#!mAEBBSiS!L9Q1Z6tHRSczGKB7uqpyn9SVgGFInn45OpGjL7UoaRc Mofo 5.1 image (stock w/tether)...

Here's a mirror of the XT1097 AT&T file :) https://mega.co.nz/#!bN0BjKbI!zzq5b9wZBo-XFGNkcWtgw7mnXZgC5BWrEC-GZcGLELo

It looks like the AT&T package is out, I'm downloading it now but whoever uploaded these things to filefactory is sadistic. Should have an image up tomorrow at some point.

It seems that the XT1097 image I found isn't for the AT&T version, so no go there. If anyone's able to find it I'll extract a base image but not much I can do until then :(

I can put together a base image for the XT1097 with/without tether, someone else will have to root it though since I don't have the setup to do that easily.

Thanks JulesJam for your help in getting everything set up! I finally was able to update last night and so far so good. I'm running mikeoswego's Root/BB/SQLite image with the hosts file tweaked. I did a factory reset and then updated everything including recovery, and still ran into the same...

Yeah, it's most of the necessary files iirc except system.img is in sparsechunks. I have no idea if it will work or not though which is why I mentioned you'd have to be brave :p

Yes, it's a 5.1 image with the build.prop edited. You'll need to flash everything else from the update minus motoboot.img and gpt.bin for this to work, there's a full update package from another thread for our phones but it's not the FXZ version. I'd try it myself but I'm away for the weekend :(

This image should work with Mofo on the XT1096 if anyone is brave enough to try selectively updating and then flashing. I used the utility from here to extract system.img and then dd to convert it to a flashable ext4 file...

Yeah :( My current plan is to flash everything except motoboot.img and gpt.bin from the new update and see if it boots in order to preserve the ability to root. I've been checking MDM (finally got it to work!) though and they haven't pushed it out yet.

We need the FXZ in order to get the full system.img to use with mofo. Right now the OTA only patches the existing one.

Did you do anything in particular to get the status back to official? I tried this on mine last night with no luck.

Some things early in the boot process like boot animations may not work depending on when the kernel mounts external partitions (I believe it's the init process), but there's only one way to find out :)

Thanks for fixing it, I'm not sure how the original image got corrupted since all I did was mount/unmount it after making changes. I guess this is what MD5s are for :o I can confirm this works. If anyone wants to do this you'll need to: 1. Mount the image in linux for editing 2. Rename the...

Flashed it on my phone, everything is working great. Now development can finally open up :)

I'm at work and can't upload it right now, but I'd prefer not to post it publicly since having superuser default to grant is not very secure. If I don't make any progress in the near future however, I'll send it out via PM or something. I've actually tried both 2.46 and the 2.48 beta with the...

This is where I'm at right now: -Image boots after flashing with Mofo -Need to open SuperSU and set default permissions to Grant -Close/reopen SuperSU and update binary without rebooting -Change default back to Prompt and everything works Of course it goes back to not working after reboot. I...

I'd prefer not to share that link since it's incomplete. I've made some progress though, I picked up mofo and have been testing images on my device. After fixing a few minor mistakes (something something stupid permissions :o) I've gotten root to work. It complains that the binary needs to be...

Fixed, my bad :)

Those guides are following mostly the same process I used, except they don't mention changing the SELinux context which is necessary in 5.0 images. If you check out the SuperSU zip, in META-INF/com/google/android there's an update-binary script with instructions for manual installations which...

I was referring to what would be possible with a rooted image, not saying that I had made a working one. I built one and sent it to JulesJam for testing but I'm not sure if it will work given the complexity of embedding root and my lack of experience doing anything like this.

I'm going to attempt to build a rooted system.img based on the instructions in the SuperSU update binary, will send it to JulesJam for testing afterwards. The first two are almost definitely possible, the notification light may be difficult though as IIRC it's only accessible by the system...

I'm glad to help out where I can, I'd like to see a working root on 5.0 as much as you guys. Thank you to maiko1 for the instructions, slogar25 for the image, and JulesJam for testing them. These are the images I created based on the fxz upladed by slogar25 in case anyone wants to give rooting...

The only other thing I can think of at the moment is trying to flash the system.img from the Pure Edition running 5.0, the phones have different radio chips though so I'm not sure what would happen...

Did you by any chance try a factory reset after the rooted image was on the phone? And I tore apart the system files posted on root junkies, the stock and rooted files are exactly the same except where SuperSU files had been inserted in the rooted version, so if anything is causing an issue...

Looks like you can grab the whole package here, although the version number doesn't seem to match. http://rootjunkysdl.com/?device=Moto%20X%202014&folder=Official%20Firmware

Those were good times, even if it was Windows Mobile. Bring it on I say!

You may need to just give it some time, it took a good 10 minutes or so for it to finish anything for me over bluetooth. It just sat at the prompt without giving me status information or anything.

I installed the compass app, it's hardly what I would call accurate but it does seem to get the right direction for the most part. Good find!

Saw this posted on Reddit. Seems to be a full system image but I'm not brave enough to flash it ;) https://mobile.twitter.com/MotoFirmware/status/522902016763633665?s=09

My battery life hasn't really changed at all on my phone. I guess it's possible that the reduced time I use my screen due to the watch makes up for the battery drain from bluetooth?

Agreed... even if you somehow manage to replace it without damaging anything, the watch will almost certainly not be waterproof afterwards. This is why I went with SquareTrade on mine.

I can confirm this. Just checked my receipt (bought in store) and the protection plan is GSP-R which does NOT cover accidental damage. Thank you for the heads up, I just canceled the plan and will be going with squaretrade. They are cheaper anyway with the 40% off coupons that are floating...

I'm pretty sure that after you use the voice command a few times it will go way automatically.

Does anyone know if this is possible, either in Android Wear or on the watch itself? Right now the backlight remains on (but very dim) and drains the battery too much to make it worth using, but I think it would still be visible enough with it off entirely.

I wanted to kill my battery today to calibrate it after getting the watch, so I left ambient mode on. After ~10 hours it was still only at 25%, so I had to resort to running the stopwatch with the brightness on full to kill the rest. Going to give it a real run tomorrow and see how long it lasts.

Mine has two stuck pixels, one at either side of the screen. I'm debating whether or not it's worth doing anything about, definitely no point yet as there's no stock to exchange it with around me. Has anyone made a pixel unsticking tool for Android Wear yet? Maybe that could help.

I tried charging mine while powered off after I got it, but it just kept turning itself back on and draining the battery back down to 0. I basically ended up having to babysit it for an hour or so, every time it turned itself back on (8% or so at a time) I'd shut it right back off again until...

From the iFixit teardown it looks like you can access the USB pins by peeling back the FCC sticker, no disassembly required. Looks like it will be a pain to make a connection to them though.

Looks like you can access the pogo pins by peeling back the FCC sticker: https://d3nevzfk7ii3be.cloudfront.net/igi/BSaCmnUmb3166USa.huge So much for our warranties. Taken from iFixit