yashsingh1/xdaforums huggingface dataset:
[Xperia Z2 Tablet Q&A, Help & Troubleshooting] corbeau56:
See my experiences here.

Well, I finally rooted my SGP511 (bought in Germany, no branding, KitKat 4.4.4, no official OTA Lollipop update available so far) and everything went fine. For other noobs, I'll write my experiences.

As I could not make a nandroid backup before (no custom recovery yet) I finally did a backup only by Helium and Google app sync. I knew this is not comparable to a nandroid, but I finally did not have too much work to reinstall missing apps etc. Most of the work was to remanage my homescreeens and setup of e-Mail accounts.

Then I did the following steps (you can find all of them by using search function):

- All windows drivers on my PC worked properly before, so I did not change anything.

- I took off my external SD-Card, as I did not know if it will be formatted. Charged tablet battery to >90%.

- Downgraded from firmware 23.0.1.A.4.30 (KitKat 4.4.4) to 17.1.A.0.402 (KitKat 4.4.2) by flashing sgp511_17.1.A.0.402_generic DE.ftf with flashtool V0.9.18.5. No problems at all, tablet booted exactly like on first start after unboxing.

- Rooted the tablet using Easy Root Tool V12.4. This seemed to hang up after message "cleaning up", but when I hit Ctrl-C and answered the question "Cancel batch job ?" with "N", I got the message that the tablet was rooted.

- Installed SuperSU by chainfire via Play Store, no problems.

- Installed ES File Explorer via Play Store (to test root), activated Root-Explorer. Got a SuperSU message ("Allow root access?"), so root was ok.

- Backed up my TA Partition with Backup TA V9.11. I do not intend to unlock my bootloader, but this was recommended, and it just takes a minute. After backup, I tried a "restore dry-on" and got the message that the backup is working.

- Installed XZDualRecovery 2.8.15 (TabZ2-lockeddualrecovery2.8.15-RELEASE.installer.zip from http://nut.xperia-files.com/), no problems. Booted automatically to TWRP 2.8.6.0 after installation. After rebooting the system one time to finish installation I went back to TWRP and made a full backup of my rooted firmware 17.1.A.0.402 (just for security reasons).

- Installed newest prerooted firmware 23.1.A.1.28 from this thread using TWRP. This upgraded my tablet to Lollipop 5.0.2. I was not sure if this firmware would be ok for my german tablet (as it is Customized NCB) , but kulvertti (Thanks for your work!) wrote that region doesn't matter for WiFi-only tablets. I can confirm this, I can't see a difference to generic DE firmware.

- Tablet booted normally to Lollipop, installed most of my apps via Google sync etc.

I was really surprised how easy all this was. I now have a rooted tablet, upgraded to Lollipop and a custom recovery which allows me easily to make nandroid backups or use Titanium Backup. It's just great!

P.S. After installation of XZDualRecovery, and while I was still on firmware 0.402, my tablet announced an OTA update (back to 4.30). As far as I know, this can only be installed with stock recovery. I don't know what would happen, so better do not accept this.
[Xperia Z2 Tablet Q&A, Help & Troubleshooting] jullebarge:
Thanks a lot for this detailed post, it helped me a lot to root my Lollipop tablet ;)

I was a complete noob on Z2 flashing and so on (coming from Nexus 4, it's really different) but this step by step guide is really helpfull.

I had a problem on the first step because I was using official Sony flashtool and you need to use this one: http://www.flashtool.net/index.php

Another thing for noobs like me: to boot to TWRP, you need to hit Volume key at boot when led is green, for more info look here :http://xdaforums.com/showthread.php?t=2785598
[Xperia Z2 Tablet Q&A, Help & Troubleshooting] corbeau56:
Hi there,

my rooted tablet works fine with kulverttis prerooted stock rom, but now I would like to make a next step and try a CM custom rom. Here are some questions about that:

- Do I need to unlock my bootloader via Sony developer site as described on CM website? Or is this not necessary (as my tablet is rooted yet) and can I directly flash the zip file downloaded from CM?

- If I would like to go back to prerooted stock rom, will I only have to restore my TWRP nandroid backup or will there be other steps to do (like relocking bootloader or anything else)?
[Xperia Z2 Tablet Q&A, Help & Troubleshooting] rcstar6696:
You need to unlock your bootloader to flash Custom Roms like Cm or Pac. Don't flash it on your device with looked bootloader this will softbrick your device.

If you want back to stock and you havn't a nandroid backup you need to do a factory reset and reinstall all apps

but if you have a nandroid backup you have to restore the backup only. You don't need to relock bootloader or and any other things
[Xperia Z2 Tablet Q&A, Help & Troubleshooting] corbeau56:
Well I tried to unlock my bootloader, but I don't get access to my tablet with fastboot commands. That's strange as I don't have any problem to get access with adb commands. My PC drivers seem to work properly.

But when I put the tablet in fastboot mode (LED is blue), I get "waiting for device" on every fastboot command. What 's my mistake?

Additional question: the unlocking will erase my internal memory incl. Dualrecovery, right? So after the unlock, I will have to flash TWRP first via fastboot, then boot to recovery and restore my nandroid?
[Xperia Z2 Tablet Q&A, Help & Troubleshooting] corbeau56:
Found it by myself when trying to unlock via Flashtool:

Flashtool showed "Root access denied" and on my tablet I shortly saw a message that superSU had denied rights to adb shell. I went to Apps - superSU and accorded rights to adb shell. After that unlocking procedure of Flashtool worked properly!
[Xperia Z2 Tablet Q&A, Help & Troubleshooting] corbeau56:
P.S. Dualrecovery was not erased by the unlocking procedure, so for the moment I could restore my nandroid backup of prerooted stock ROM. I'll try CM12.1 one of these days.
[Xperia Z2 Tablet Q&A, Help & Troubleshooting] corbeau56:
Installed CM and it runs great. On my internal SD, used space is 3.0 GB now compared to 6.8 GB on stock ROM! That's what I call a lean system.
[General Questions and Answers] ILikeMahTomatoes:
With Google's "Now On Tap" in mind: Does the concept of using what's currently on screen to provide context for better voice to text recognition make sense? Could an engine that processes audio use visual context to increase recognition accuracy?
[Galaxy S6 General] ricecake2000:
Just wanted to point out that the stock tw clock icon shows correct time and if you swipe around the drawer the second hand moves. That's pretty cool and not sure if anyone else noticed.
[Galaxy S6 General] Jrhoop:
Unfortunately this only works on stock launcher.
[Galaxy S6 General] genetichazzard:
Not really useful otherwise. The stock alarm clock is terrible too. You can't change the snooze duration, which you could do with the s4 and s5.

I use Timely for my alarm clock app now. Used to be a premium app until Google bought it and made it free.
[Galaxy S 4 Q&A, Help & Troubleshooting] mrqwerty123456:
Hi guys, I wanted to ask what would happen if installed lollipop on my s4 that wasn't from the same network. I bought my s4 from Amazon unlocked, so if I get the firmware off sammobile and if I get an EE(EE is a mobile network) firmware, does that mean my phone will work with EE network only? I am thinking of getting the BTU version. http://www.sammobile.com/firmwares/database/GT-I9505/BTU/

Another question, does xposed work well with lollipop? I currently have it installed and use snapshare and snapsave, greenify etc...
[Galaxy S 4 Q&A, Help & Troubleshooting] Strephon Alkhalikoi:
In your case, since the S4 is unlocked there are no restrictions on what firmware you can install. In addition, the SIM will work in the S4 regardless of which firmware you installed, as the S4 is unlocked. However, for best results you should stick to using unbranded firmware such as BTU. While one benefit is the lack of bloatware in the unbranded firmware, using an unbranded firmware in your device ensures that any carrier modifications made to the firmware don't wreak havoc on your phone.

Xposed is working to an extent. Check out the Xposed thread for details.
[Galaxy S 4 Q&A, Help & Troubleshooting] mrqwerty123456:
Thank you, if I dont like lollipop, is it possible to easily downgrade back to kitkat?
[Galaxy S 4 Q&A, Help & Troubleshooting] Strephon Alkhalikoi:
You shouldn't have much trouble with downgrading if you don't like Android 5.x.
[Nexus 6 Q&A, Help & Troubleshooting] imablackhat:
Anyone else ???
[Nexus 6 Q&A, Help & Troubleshooting] bill3508:
Mine is at 9%.
[Nexus 6 Q&A, Help & Troubleshooting] imablackhat:
how did you pull that off?!
[Nexus 6 Q&A, Help & Troubleshooting] simms22:
first battery cycle with m, it was high, and my phone never slept. second battery cycle, and it only reached 1% battery drain, and I had 4+ hours sot at 61% battery. btw, I'm using the permissions option, and am not allowing location for any of my apps that dont need it. also, I disabled background data for google play services.
[Moto G Q&A, Help & Troubleshooting] thatdad1992:
Will we ever get it done or is Verizon going to continue to screw us over on root and bootloader unlock?

Is anyone even attempting to work on the xt1028 or is it a useless endeavor?
[Moto G Q&A, Help & Troubleshooting] AndyYan:
If you're THAT eager, just pay for Sunshine, tried and true. Better grab a painkiller rather than let the pain kill you.

Sent from Google Nexus 4 @ CM12.1

[WARNING: XDA Premium 4.0.13+ lacks Signature function - do not update]
[Moto G Q&A, Help & Troubleshooting] thatdad1992:
Don't you have to root before you can use it though?
[Moto G Q&A, Help & Troubleshooting] jacobas92:
Doesn't work on 4.4.4. Most if not all the last 1028's came with 4.4.4 pre-installed afaik
[Moto G Q&A, Help & Troubleshooting] thatdad1992:
When I ran the apk it said it would work, however I needed root, which of course there is none
[Moto G Q&A, Help & Troubleshooting] autoprime:
root? never ever ever... :angel:

no eta for release. would prefer to skip right to bootloader unlock if possible.
[Moto G Q&A, Help & Troubleshooting] thatdad1992:
I agree, we need this bootloader cracked asap

Sent from my XT1028
[Moto G Q&A, Help & Troubleshooting] classic757:
My xt1028 is unlocked from last year through a middleman that I had to pay but no doubt this will help everyone with an xt1028 on lockdown. Hope [MENTION=2684188]autoprime[/MENTION] is able to get it done.
[Moto G Q&A, Help & Troubleshooting] jacobas92:
I can't wait, you might end up making me keep this thing haha.
[Moto G Q&A, Help & Troubleshooting] thatdad1992:
Any progress on bootloader unlock?

Sent from my XT1028
[Moto G Q&A, Help & Troubleshooting] autoprime:
progress in learning more about what's going on, yes. but no successful unlock yet.

and I am now working on the LG G4 so my time with the xt1028 will be limited. :-/
[Moto G Q&A, Help & Troubleshooting] thatdad1992:
Well I could imagine just how hard it can be, thanks for working on it for us:)

Sent from my XT1028
[Moto G Q&A, Help & Troubleshooting] ohlin5:
Saw this after your twitter post, and just wanted to say thanks for working on this! I too picked up a couple of these on fire sale and even if you can't get it done then you still deserve all the thanks in the world, but I will be keeping my eyes peeled out for this! And yes, a BL unlock would be totally amazing! Thanks again!!!
[Moto G Q&A, Help & Troubleshooting] SSVanderbilt:
Awesome man! The sooner we can get this thing rooted and unlocked the better!
[Moto G Q&A, Help & Troubleshooting] groovadelickun:
Yes, thank you autoprime for working on this!
[Moto G Q&A, Help & Troubleshooting] twig123:
Awesome work! We appreciate your time!

Subbing to this thread in hopes of a release!
[Moto G Q&A, Help & Troubleshooting] tweakdeveloper:
If you can send me a copy of your aboot (/dev/block/mmcblk0p4 I think) I can take a look at it
[Moto G Q&A, Help & Troubleshooting] groovadelickun:
Anything special need to be done to grab a copy of it from a stock device? Should be able to copy to another folder or send via email using a file explorer such as root explorer?

I'm not able to copy it to another folder or send via email using root explorer, but maybe I'm not going about it correctly.

Thanks for looking into this.
[Moto G Q&A, Help & Troubleshooting] tweakdeveloper:
Sorry, you have to do something like

adb shell
$ cd /sdcard
$ dd if=/dev/block/mmcblk0p4 of=aboot
$ exit
adb pull /sdcard/aboot

You might have to be rooted, but I'm not sure.
[Moto G Q&A, Help & Troubleshooting] groovadelickun:
Thanks. I'm thinking it does need to be rooted. I got the following message:

"/dev/block/mmcblk0p4: cannot open for read: Permission denied"

http://gyazo.com/2cbab9dd9960340155d94a30220b9985
[Moto G Q&A, Help & Troubleshooting] tweakdeveloper:
Yeah, that's a root error. I managed to pull one from a firmware file I had laying around, but my disassembler doesn't want to play nice with it so I'm not sure how much I'll be able to get done. :(
[Moto G Q&A, Help & Troubleshooting] groovadelickun:
Bummer... :(

Appreciate you taking the time.
[Moto G Q&A, Help & Troubleshooting] thatdad1992:
Any luck thus far?

Sent from my XT1028
[Moto G Q&A, Help & Troubleshooting] ajeevlal:
I was able to get a temp root using Kingo root om android 4.4.4, with that anyone have any suggestions to acquire boot loader unlock without using sunshine. i dont want to pay 25 dollars for boot loader unlock
[Moto G Q&A, Help & Troubleshooting] PedroRafael8265:
How did you do to temporarily rootearlo?
[Moto G Q&A, Help & Troubleshooting] jakeh9777:
Anyone figured out a free way to unlock and root XT1028 yet?
[Moto G Q&A, Help & Troubleshooting] randalgibbons:
Xt1028 rooted!!

With King Root 4.5

Probably temp ( I haven't rebooted yet. )

But root none the less.
[Moto G Q&A, Help & Troubleshooting] AchillesTheGod:
OMFG!!! my hero did you reboot yet? were you Running 4.4.4?
[Moto G Q&A, Help & Troubleshooting] thatdad1992:
It's temp, but it doesn't break everything like kingo root

Sent from my XT1028
[Moto G Q&A, Help & Troubleshooting] AchillesTheGod:
I tired it and it didn't work at all. Were you running on 4.4.4
[Moto G Q&A, Help & Troubleshooting] Teet1:
I got the file! [MENTION=6560928]tweakdeveloper[/MENTION] Do you want me to send it to you? I used the temp root, then quickly did what you said as su. This is for my Cricket XT1045 variant 4.4.4.

D:\android-sdk-windows\platform-tools>adb shell
shell@peregrine:/ $ su
su
root@peregrine:/ # cd /sdcard
cd /sdcard
root@peregrine:/sdcard # dd if=/dev/block/mmcblk0p4 of=aboot
dd if=/dev/block/mmcblk0p4 of=aboot
1024+0 records in
1024+0 records out
524288 bytes transferred in 0.088 secs (5957818 bytes/sec)
root@peregrine:/sdcard # exit
exit

127|shell@peregrine:/ $ exit
exit

D:\android-sdk-windows\platform-tools>adb pull /sdcard/aboot
3413 KB/s (524288 bytes in 0.150s)

D:\android-sdk-windows\platform-tools>

I feel like we're almost there! I opened aboot with HxD and I found this http://screencloud.net/v/hRHc

Although I do not code and I don't know much hex editing at all, I'm pretty sure this has something to do with locking or unlocking the bootloader, right?

Found more stuff: http://screencloud.net/v/yhn7

I can send you my aboot file for you to look at.
[Moto G Q&A, Help & Troubleshooting] thatdad1992:
Yes, just try it a couple times, it'll work

Sent from my XT1028
[Moto G Q&A, Help & Troubleshooting] Teet1:
I've managed to successfully pull and push the recovery partition (I think it's mmcblk0p32?) so if we manage to develop a working TWRP, we can force push it into the phone while temprooted, perhaps it'll work and we'll have TWRP permaroot? :D sounds too easy and too good to be true, but its worth a try!

Here is the partition layout for peregrine Moto G phones (cricket KK 4.4.4 variant user):

root@peregrine:/ # cat /proc/partitions
cat /proc/partitions
major minor #blocks name

7 0 8348 loop0
7 1 34335 loop1
7 2 11466 loop2
7 3 13545 loop3
7 4 32256 loop4
7 5 17703 loop5
179 0 7634944 mmcblk0
179 1 65536 mmcblk0p1
179 2 512 mmcblk0p2
179 3 32 mmcblk0p3
179 4 512 mmcblk0p4
179 5 200 mmcblk0p5
179 6 400 mmcblk0p6
179 7 32 mmcblk0p7
179 8 512 mmcblk0p8
179 9 2048 mmcblk0p9
179 10 2332 mmcblk0p10
179 11 512 mmcblk0p11
179 12 200 mmcblk0p12
179 13 400 mmcblk0p13
179 14 32 mmcblk0p14
179 15 512 mmcblk0p15
179 16 1052 mmcblk0p16
179 17 1536 mmcblk0p17
179 18 1536 mmcblk0p18
179 19 512 mmcblk0p19
179 20 8 mmcblk0p20
179 21 1536 mmcblk0p21
179 22 1 mmcblk0p22
179 23 8 mmcblk0p23
179 24 1024 mmcblk0p24
179 25 128 mmcblk0p25
179 26 3072 mmcblk0p26
179 27 4096 mmcblk0p27
179 28 4096 mmcblk0p28
179 29 8192 mmcblk0p29
179 30 512 mmcblk0p30
179 31 10240 mmcblk0p31
259 0 10240 mmcblk0p32
259 1 546944 mmcblk0p33
259 2 1130496 mmcblk0p34
259 3 8192 mmcblk0p35
259 4 5791616 mmcblk0p36
179 32 512 mmcblk0rpmb
179 64 15558144 mmcblk1
179 65 15554048 mmcblk1p1
254 0 8347 dm-0
254 1 34335 dm-1
254 2 11466 dm-2
254 3 13545 dm-3
254 4 32256 dm-4
254 5 17703 dm-5

we're almost there boys! we can do this. I'm very excited to make this discovery, be it possible or impossible. I'm no dev, but I think it is possible.
[Moto G Q&A, Help & Troubleshooting] thatdad1992:
Best of luck! And hopefully it'll work on Verizon version too

Sent from my XT1028
[Moto G Q&A, Help & Troubleshooting] Teet1:
Here's the a more detailed layout of the peregrine partitions:

D:\android-sdk-windows\platform-tools>adb shell
shell@peregrine:/ $ su
su
root@peregrine:/ # ls -al /dev/block/platform/msm_sdcc.1/by-name
ls -al /dev/block/platform/msm_sdcc.1/by-name
lrwxrwxrwx root root 1970-03-20 00:35 DDR -> /dev/block/mmcblk0
p3
lrwxrwxrwx root root 1970-03-20 00:35 aboot -> /dev/block/mmcbl
k0p4
lrwxrwxrwx root root 1970-03-20 00:35 abootBackup -> /dev/block
/mmcblk0p11
lrwxrwxrwx root root 1970-03-20 00:35 boot -> /dev/block/mmcblk
0p31
lrwxrwxrwx root root 1970-03-20 00:35 cache -> /dev/block/mmcbl
k0p33
lrwxrwxrwx root root 1970-03-20 00:35 cid -> /dev/block/mmcblk0
p25
lrwxrwxrwx root root 1970-03-20 00:35 clogo -> /dev/block/mmcbl
k0p28
lrwxrwxrwx root root 1970-03-20 00:35 dhob -> /dev/block/mmcblk
0p20
lrwxrwxrwx root root 1970-03-20 00:35 fsc -> /dev/block/mmcblk0
p22
lrwxrwxrwx root root 1970-03-20 00:35 fsg -> /dev/block/mmcblk0
p21
lrwxrwxrwx root root 1970-03-20 00:35 hob -> /dev/block/mmcblk0
p19
lrwxrwxrwx root root 1970-03-20 00:35 kpan -> /dev/block/mmcblk
0p35
lrwxrwxrwx root root 1970-03-20 00:35 logo -> /dev/block/mmcblk
0p27
lrwxrwxrwx root root 1970-03-20 00:35 logs -> /dev/block/mmcblk
0p9
lrwxrwxrwx root root 1970-03-20 00:35 misc -> /dev/block/mmcblk
0p30
lrwxrwxrwx root root 1970-03-20 00:35 modem -> /dev/block/mmcbl
k0p1
lrwxrwxrwx root root 1970-03-20 00:35 modemst1 -> /dev/block/mm
cblk0p17
lrwxrwxrwx root root 1970-03-20 00:35 modemst2 -> /dev/block/mm
cblk0p18
lrwxrwxrwx root root 1970-03-20 00:35 padA -> /dev/block/mmcblk
0p10
lrwxrwxrwx root root 1970-03-20 00:35 padB -> /dev/block/mmcblk
0p16
lrwxrwxrwx root root 1970-03-20 00:35 pds -> /dev/block/mmcblk0
p26
lrwxrwxrwx root root 1970-03-20 00:35 persist -> /dev/block/mmc
blk0p29
lrwxrwxrwx root root 1970-03-20 00:35 recovery -> /dev/block/mm
cblk0p32
lrwxrwxrwx root root 1970-03-20 00:35 rpm -> /dev/block/mmcblk0
p5
lrwxrwxrwx root root 1970-03-20 00:35 rpmBackup -> /dev/block/m
mcblk0p12
lrwxrwxrwx root root 1970-03-20 00:35 sbl1 -> /dev/block/mmcblk
0p2
lrwxrwxrwx root root 1970-03-20 00:35 sdi -> /dev/block/mmcblk0
p7
lrwxrwxrwx root root 1970-03-20 00:35 sdiBackup -> /dev/block/m
mcblk0p14
lrwxrwxrwx root root 1970-03-20 00:35 sp -> /dev/block/mmcblk0p
24
lrwxrwxrwx root root 1970-03-20 00:35 ssd -> /dev/block/mmcblk0
p23
lrwxrwxrwx root root 1970-03-20 00:35 system -> /dev/block/mmcb
lk0p34
lrwxrwxrwx root root 1970-03-20 00:35 tz -> /dev/block/mmcblk0p
6
lrwxrwxrwx root root 1970-03-20 00:35 tzBackup -> /dev/block/mm
cblk0p13
lrwxrwxrwx root root 1970-03-20 00:35 userdata -> /dev/block/mm
cblk0p36
lrwxrwxrwx root root 1970-03-20 00:35 utags -> /dev/block/mmcbl
k0p8
lrwxrwxrwx root root 1970-03-20 00:35 utagsBackup -> /dev/block
/mmcblk0p15
root@peregrine:/ #

KingRoot makes the phone unstable after a while. Everything starts crashing but the root still works. It seems that it's limited. After a long time of not using root, it gets unrooted. It's most likely from write protection. So if we temproot and somehow disable the write protection, we can have perm root as well.
[Moto G Q&A, Help & Troubleshooting] tweakdeveloper:
Please do send that to me! Those are actually strings rather than actual unlocking code, but the fact that they're present anyway is somewhat reassuring. :)
[Moto G Q&A, Help & Troubleshooting] Teet1:
Sent you PM. And yes, I noticed it was just strings. I saw text saying the different status codes and text asking if you wish to unlock the bootloader, during the process, and after the process.
[Moto G Q&A, Help & Troubleshooting] XTheArrowX:
Motorola Moto G (2015) listed accidentally on FlipKart

http://feedproxy.google.com/~r/AndroidNewsGoogleAndroidForums/~3/dsLsLoeVEY8/

Sent via BlinkFeed
[Moto G Q&A, Help & Troubleshooting] thatdad1992:
Forgive me, I don't know much about development and the like.. So I have some questions

1. What do these strings mean, and what are their importance, in relation to unlocking the bootloader and or rooting?

2. Was that an unofficial way to unlock?

And 3. Probably the most important question of all:

Do you see any unlock or root process in the near future?

Sent from my XT1028
[Moto G Q&A, Help & Troubleshooting] Teet1:
I'm not developer at all, however I'm a bit savvy about Android

1. Like tweakdeveloper said, it was reassuring that the text strings for the bootloader unlocking are still present. Going through aboot, I found strings saying the different status codes that read on the bootloader. Status code 0: Device is LOCKED. Status code 1: Devices is UNLOCKED. Status code 2: Device is LOCKED. Status code 3: Devices is UNLOCKED.

2. No, as tweak mentioned this is probably not an unofficial way to unlock

3. Most likely yes. After my months of research on different forums about unlocking the bootloader on the XT1045 variants on 4.4.4, someone asked a cricket representative if bootloader was unlockable. They said it's possible, but wouldn't tell. Asking Motorola won't get you a response, and asking their forums will get you banned from there. Root, that's already possible. But it's only temproot. Just the system protection and locked bootloader won't let us keep it.

I'm tempted to force push a custom recovery into the partition using adb shell. Is it safe to do? Is it possible that the recovery will boot? I'd like a dev on here to let me know. We're so close and I'm growing impatient on what happens next!
[Moto G Q&A, Help & Troubleshooting] thatdad1992:
I meant permroot but okay that makes a lot of sense

I figured we'd find at least something, there's always a way to perm root and unlock bootloader. Let's hope we find a way that is applicable for all moto g

Sent from my XT1028
[Moto G Q&A, Help & Troubleshooting] thatdad1992:
So, I'm assuming nothing new?

Sent from my XT1028
[Moto G Q&A, Help & Troubleshooting] Teet1:
Nothing new. I'm stumped now. The only hope we have is that we find an exploit to gain access and make /system RW like they did with the Moto X
[Moto G Q&A, Help & Troubleshooting] thatdad1992:
Did they patch that one possible exploit with the camera in kitkat?

Sent from my XT1028
[Moto G Q&A, Help & Troubleshooting] Teet1:
I'm not sure. They patched it shortly in an OTA update. The Moto X was on 4.4.2/4.4.3 and we're on 4.4.4 so it's most likely already patched
[Moto G Q&A, Help & Troubleshooting] thatdad1992:
So basically we're most likely not going to get root

Sent from my XT1028
[Moto G Q&A, Help & Troubleshooting] Teet1:
Well hopefully they will find another exploit. But until then the only sliver of hope we have is the ability to temp root with King Root, and how it somehow magically manages to write to /system in order to root
[Moto G Q&A, Help & Troubleshooting] thatdad1992:
It doesn't seem like that many people are to worried about xt1028 :/

Sent from my XT1028