So Motorola just rolled out the Android L 5.1 OTA update. I never rooted my Moto X before, just unlocked the bootloader on Android L 5.1, but i'm having problems booting/flashing custom recovery on fastboot as it shows permission denied. Anyone help?
If fastboot says the permission is denied, then it sounds like you didn't unlock the bootloader properly. Do you have a developer edition or otherwise unlockable device?
Sent from my Nexus 6
imnuts said:
If fastboot says the permission is denied, then it sounds like you didn't unlock the bootloader properly. Do you have a developer edition or otherwise unlockable device?
Sent from my Nexus 6
Click to expand...
Click to collapse
Thanks for the reply but i managed to root it. Seemed like i was using the wrong adb and fastboot files. Anyway i rooted my Moto X 2013 on Android L V5.1 successfully but i'm facing this problem of slow boot time now. Any idea what might causing it? I rooted the stock Android L and installed SuperUser, Xposed Framework etc. i started installing a couple of apps like motox led & Font changer etc. With every reboot the devices keeps on taking longer time to boot to the home screen.
Teejay94 said:
Thanks for the reply but i managed to root it. Seemed like i was using the wrong adb and fastboot files. Anyway i rooted my Moto X 2013 on Android L V5.1 successfully but i'm facing this problem of slow boot time now. Any idea what might causing it? I rooted the stock Android L and installed SuperUser, Xposed Framework etc. i started installing a couple of apps like motox led & Font changer etc. With every reboot the devices keeps on taking longer time to boot to the home screen.
Click to expand...
Click to collapse
This is quite normal and has to do with the RunTime being ART vs Davlik. In KitKat we had a choice between the two but with Lollipop it's only ART now. The thinking is that the device runs more smoothly with ART at the expense of longer boot time.
Related
So finally Android 4.3 has arrived and our Beloved Nexus 7 is Upgradable Now.....
here is the link to the download of factory Image:
https://developers.google.com/android/nexus/images#nakasijwr66v
Follow this Method and flash the New Android OS...
[GUIDE] Flashing a Factory Image with fastboot / return to stock Thanks @comminus for a great Guide...
Report Back with screenShots and new featuers as well as Bugs because new pudates bring New Bugs.....
The update brought a new bootloader version...android 4.2.2 had 4.18 and 4.3 has 4.23.....
hassam_tariq2003 said:
The update brought a new bootloader version...android 4.2.2 had 4.18 and 4.3 has 4.23.....
Click to expand...
Click to collapse
Did you lose boot loader unlock or root when you installed 4.3? I'm assuming you used fastboot to install not OTA? Just curious...I'll be playing tonight when I get home.
tbonezx11 said:
Did you lose boot loader unlock or root when you installed 4.3? I'm assuming you used fastboot to install not OTA? Just curious...I'll be playing tonight when I get home.
Click to expand...
Click to collapse
You lose root but your bootloader remains unlocked.
Has anyone been able to root 4.3? Tried to root and flash custom recovery with the Nexus 7 toolkit, but I don't think it's working.
mhl12 said:
You lose root but your bootloader remains unlocked.
Has anyone been able to root 4.3? Tried to root and flash custom recovery with the Nexus 7 toolkit, but I don't think it's working.
Click to expand...
Click to collapse
haven't tried it (I'm yet to receive the update) but someone referenced this link: https://plus.google.com/u/0/+Chainfire/posts/WqS2E9kkN1L
he is right.....You loose root but bootloader remains unlocked...
i have heard people say that you do not loose root if you use the OTA Method and your bootloader also remains unlocked....So its your choice its either Fastboot or OTA...
Just use OTA Rootkeeper, you'll be fine.
Just remember kids.
You cannot use an OTA if your ROM is modified in ANY WAY.
Yeah OTA wont work for most people, seeing as they probably have a modified ROM. In any sense, chainfire has a root method that works. I can confirm it working, because I installed it using TWRP
khaytsus said:
Just use OTA Rootkeeper, you'll be fine.
Just remember kids.
You cannot use an OTA if your ROM is modified in ANY WAY.
Click to expand...
Click to collapse
When 4.2.2 came out I had problems updating because my ROM was modified. But someone modified OTA not to check for changes in ROM and it worked.
no OpenGL ES 3.0 for us?
according to http://developer.android.com/:
"OpenGL ES 3.0 is an optional feature that depends on underlying graphics hardware. Support is already available on Nexus 7 (2013), Nexus 4, and Nexus 10 devices."
I am running 4.3 unlocked but I did the one click method for root using nexus tool kit and for some reason it did not work, I have to try again tonight.
Want a single click ADB setup? Go to my thread I've made a Tool for that. No need to download the whole SDK it's just 2MB
http://forum.xda-developers.com/showthread.php?t=2374071
What to know how to easily pull ota link with ADB follow my thread.
http://forum.xda-developers.com/showthread.php?t=2270429
For official nexus 7 windows 7 - 8 driver download them from ASUS site. No trickery needed.
Sent from my SPH-L710 using Tapatalk HD
Team SXTP
So, I played around a bit,
First of all, I did a "clean, unrooted and even locked bootloader install".
So I'm 1000% stock, just to avoid stuff like "maybe root caused it"..
(I locked it because I wanted to go 100% stock, just FYI, I know it's normally not necessary...)
The welcome screen was a bit weird... I got asked 2 times to tick or untick boxes for saving passwords and all that stuff.. (I think they mixed up the new and the old "first boot setup"?)
The Apps and widgets in the drawer were kinda confused, took 2 reboots for them to settle... (Icons disappeared and reappeared.. The widget tab in the drawer threw some widgets in and out, and the previews were mixed up, so dots and a weird sign was the result (as a preview of the widget)...
The initial setup was pretty laggy, but after setting stuff up, until now, yes I can say the performance of the nexus 7 is improved..
First I was like "OH HELL NO" but after the setup and the reboot everything was smooth...
Oh, and the back button was destroyed 1 time, blinked up but didn't go back... I pressed the home button and it worked then.
Edit: And sadly, no new wallpapers in stock... ):
Sent from my Nexus 7 using xda premium
I booted it up, restored my Google Play stuff (flashed a factory image, completely wiped everything from it, so it's clean, I think).
It lagged a lot, so I rebooted it and it still isn't 4.2.2 smooth. Maybe it's just me, I'll see.
Is it just me, or does it feel like the only thing that changed for us is the number in settings menu besides Google Apps?
OpenGL ES as it was already said, doesn't appear to be here for us, not to mention the fact that Miracast had never actually worked on N7 until recently when someone had it ported over.
Has anyone managed to find the link for the OTA yet?
SO I flashed the stock 4.3 kernel on a 4.2.2 rom and discovered that the stock android 4.3 kernel breaks wifi and gps on 4.2.2...
Eregoth said:
Has anyone managed to find the link for the OTA yet?
Click to expand...
Click to collapse
I have literally hours working on that.
Flashed the stock image using fastboot, took like 2 minutes to do, flashed the chainfire root patch and rebooted and restored apps, so far everything is pretty smooth no disappearing apps or icons or buttons, the kernel seems to be quicker, opening websites was quite a bit quicker, one thing I noticed while trying out different browsers was ads opening up new tabs automatically, that's something that's never happened before.
ffaiz.m said:
no OpenGL ES 3.0 for us?
according to http://developer.android.com/:
"OpenGL ES 3.0 is an optional feature that depends on underlying graphics hardware. Support is already available on Nexus 7 (2013), Nexus 4, and Nexus 10 devices."
Click to expand...
Click to collapse
Tegra 3 does not support GLES3. Even Tegra 4 won't, because nvidia are still using their old gpu architecture.
What's the performance like? Better than 4.2 or 4.1?
Sent from my GT-I9300 using xda premium
Greetings y'all.
I'm rocking a Moto X from the Canadian carrier Rogers and I'm currently running on Android 4.2, with the well... what was latest version for the Moto X, the update that included the camera fixes. I originally rooted my Moto X with the first root method that became available and then recently I used the new RockMyMoto method and I've experienced a peculiar issue and I was hoping someone would be able to offer me some advice.
After rooting my device with RockMyMoto my device had root working perfectly! The applications that rely on root were working perfectly and then one day... something happened. AdAway failed to install the updated host file, so I went into AdAway and it gave me a warning that said root was required.
I found this to be odd... so I exited the application and tried again. The same dialog came up with the same message. I decided to clear the application data and remove AdAway from SuperSU and then reinstalled the application. The problem persisted. I then rebooted my device and tried again and all of a sudden it worked. Now it appears my device is getting intermittent root?
When I turn my phone on I get a notification from Koush's Superuser (I switched from SuperSU, this might be the issue, at least I thought it might be until I switched back to SuperSU) saying that the binary was outdated and I needed an update, so I updated it and it was working so then I decided to try AdAway and... it worked! Success! or so I thought... a few minutes later I tried again and that same dialog came up.
Herumph! I proclaimed. What is this sorcery? Well... it seems my Moto X is getting an intermittent root or something that's only available once the system starts up again.
I tried running RockMyMoto again but that didn't seem to work, mind you I didn't unroot and then reroot.
My question for you is, well... how can I fix this? I don't want to restore my device to stock Android and I also don't want to do some sort of complex trickery because I'm expecting a 4.4 update sometime soon. Anyways, give me a hand guys!
You may not have root after 4.4 anyway... Some say.
Sent from my Moto X cell phone telephone...
Turbocom said:
Greetings y'all.
I'm rocking a Moto X from the Canadian carrier Rogers and I'm currently running on Android 4.2, with the well... what was latest version for the Moto X, the update that included the camera fixes. I originally rooted my Moto X with the first root method that became available and then recently I used the new RockMyMoto method and I've experienced a peculiar issue and I was hoping someone would be able to offer me some advice.
After rooting my device with RockMyMoto my device had root working perfectly! The applications that rely on root were working perfectly and then one day... something happened. AdAway failed to install the updated host file, so I went into AdAway and it gave me a warning that said root was required.
I found this to be odd... so I exited the application and tried again. The same dialog came up with the same message. I decided to clear the application data and remove AdAway from SuperSU and then reinstalled the application. The problem persisted. I then rebooted my device and tried again and all of a sudden it worked. Now it appears my device is getting intermittent root?
When I turn my phone on I get a notification from Koush's Superuser (I switched from SuperSU, this might be the issue, at least I thought it might be until I switched back to SuperSU) saying that the binary was outdated and I needed an update, so I updated it and it was working so then I decided to try AdAway and... it worked! Success! or so I thought... a few minutes later I tried again and that same dialog came up.
Herumph! I proclaimed. What is this sorcery? Well... it seems my Moto X is getting an intermittent root or something that's only available once the system starts up again.
I tried running RockMyMoto again but that didn't seem to work, mind you I didn't unroot and then reroot.
My question for you is, well... how can I fix this? I don't want to restore my device to stock Android and I also don't want to do some sort of complex trickery because I'm expecting a 4.4 update sometime soon. Anyways, give me a hand guys!
Click to expand...
Click to collapse
I presume you're making changes/updates to SuperSU booting into recovery? I'm not sure, but I know I had some problems, lost root briefly when I updated but wasn't in recovery.
Issue resolved! I wasn't applying the update in recovery. Silly me!
The annoyance I saw was I had to reboot into "recovery" to make it have R/W status. That only lasts until the next reboot.
I ran the new pwnnomo or however its spelt, and don't have to worry about that anymore. And also now have safestrap
Sent from my XT1049 using Tapatalk
It is a Rogers Moto X so you can always make life simple and simply unlock the bootloader, no stopping you from enjoying root then even with the 4.4.x update.
Steve-x said:
It is a Rogers Moto X so you can always make life simple and simply unlock the bootloader, no stopping you from enjoying root then even with the 4.4.x update.
Click to expand...
Click to collapse
Are you using 4.4?
Some games I wanted to play doesn't support 4.4 so I flashed back to Camera update 4.2.2 and tried again games worked. So, I decided to stay on 4.2.2.
I tried rockmymoto again and I get is system is not write protected... executing step 3... nothing happens
toolkit even doesn't work. Any methods to root only 4.2.2? at&t user here...
Thanks in advance!
I believe since you disabled write protection you need to root using slapmymoto 4.4
slapped the sh*t out of my X
LeonKnight12 said:
Some games I wanted to play doesn't support 4.4 so I flashed back to Camera update 4.2.2 and tried again games worked. So, I decided to stay on 4.2.2.
I tried rockmymoto again and I get is system is not write protected... executing step 3... nothing happens
toolkit even doesn't work. Any methods to root only 4.2.2? at&t user here...
Thanks in advance!
Click to expand...
Click to collapse
Root in 3 mins or less
Easy..... Just install recovery twrp 2.6.3.1, it works with 4.2.2 and 4.4. This recovery will ask u if u want to root/install superSU.
Then...when the moto x starts goto playtore and update/install superSU.
omias said:
Root in 3 mins or less
Easy..... Just install recovery twrp 2.6.3.1, it works with 4.2.2 and 4.4. This recovery will ask u if u want to root/install superSU.
Then...when the moto x starts goto playtore and update/install superSU.
Click to expand...
Click to collapse
I think you missed where LeonKnight12 says " at&t user here." so can't install TWRP since ATT can't unlock bootloader, unless I missed something.
U right...... Fk at&t !!!
First time I rooted I made back up and updated I forgot to take that back up into PC :banghead:
Sent from my XT1058 using xda app-developers app
lowvolt1 said:
I believe since you disabled write protection you need to root using slapmymoto 4.4
slapped the sh*t out of my X
Click to expand...
Click to collapse
You are right, I never realized slapmymot 4.4 can be used on 4.2.2 to root. I wasted many hours to find solution. I'm glad I rooted 4.2.2 and staying there.
I'm purchased my Moto X (XT1060) on Verizon when it just came out), it came with 4.2.2 and I rooted shortly after that) then Android 4.4 KitKat came out, so I jumped on that) and now 4.4.2 (and possibly soon 4.4.4), unfortunately since root wasn't available for 4.4.2 I never went to it but I really looking forward to 4.4.4 or Android L.
at the end of the day my Moto X now is running Android 4.4 KitKat and it's rooted using one of @jcase methods.
... and as few others, going to Android 4.4 KitKat unfortunately meant shorten your battery life((
now I'd like to try out following : MOTO X - Clear Cache Partition and even though I'm pretty sure it won't do me any good, I still want to give it a go.
I'm issuing
Code:
adb reboot bootloader
and I end up inside of my bootloader, over there I selecting "recovery" yet my phone just ends up rebooting itself(
What am I doing wrong? How else I can do that? I also tried following:
Code:
fastboot erase cache
... which I'm not sure as it does anything to my phone since after reboot, my phone goes to Android without rebuilding cache normally like it'd do it in any other time I reboot my phone.
If you're battery is the same now as when you first installed 4.4....clearing cache won't change anything.
But if you want to...sorry, unfamiliar with locked root methods....do you have a custom recovery you can clear cache with?
Or....try an app, since you're rooted. There's tonnes on the play store.
Hello, can someone help me convert my Moto G 2014 XT1064 (US) to the Google Play Edition?
I bought the Moto G on sale at Amazon a few days ago, then remembered why I had put off purchasing it previously, all of the Motorola bloatware!! No Motorola, I don't need an additional backup service, and I don't want your services constantly running and pinging home, and I'd like to get updates in a reasonable amount of time. My device said it was up to date but was still on KitKat, which was very disappointing.
So far I've unlocked my bootloader (via the official Motorola method) and I did successfully upgrade to Lollipop but it was the Motorola version.
These are the packages that I have downloaded:
Blur_Version.21.11.17.titan_retuaws.retuaws.en.US.zip (the motorola 5.0 update?)
Blur_Version.22.11.6.titan_retuaws.retuaws.en.US.zip (small update for motorola android 5)
GPE_XT1032_KOT49H.M004_CFC.xml.zip (stuck at Google screen with unlock icon, waited 30 minutes)
One issue is that it seems like both of the main sites that host the stock images have been down for a few days:
- http://sbf.droid-developers.org/phone.php?device=36 (DOWN as of 12/12)
- http://motofirmware.com/files/category/38-titan/ (DOWN as of 12/12)
I also used the MotoToolAioV3.1 with the GPE_XT1032_KOT49H ROM which resulted in a bootloop, I'm guessing this is for the 1st gen Moto G?
Right now I'm back on Motorola KitKat version 21.11.17.titan_retuaws.retuaws.en.US.
Is there a way to make my Moto G XT1064 stock GPE or should I look for a custom ROM that or should I try CyanogenMod 11?
One thing to note is that I was running on less that 50% battery when trying to flash GPE_XT1032_KOT49H with MotoToolAIO, could this have been an issue or is this only to prevent the battery from dying?
Thanks for the help guys!
P.S. It was not worth it saving $70 to get the on-sale version at Amazon rather than the Google Play Edition. I've not even been able to find out for sure if you can get the 2014 version with GPE, which makes this even more frustrating.
Also, which versions are compatible with each other or are none of them compatible unless stated? Will the 1st gen ROMs work on the 2nd gen phone?
there is no GPE edition for Moto G 2ND GEN.......... and 1st gen ROMS wont work in our phones.. flashing dem results results in a BOOTLOOP
ak88900 said:
there is no GPE edition for Moto G 2ND GEN.......... and 1st gen ROMS wont work in our phones.. flashing dem results results in a BOOTLOOP
Click to expand...
Click to collapse
Thanks, it's really disappointing that I can't have stock Android on a Moto G 2014 and have it somewhat easy to update. When is that going to change Google, come on, it's been the same ROM -> Bootloop -> flash -> brick -> hours of ADB and mfastboot for 5 or 6 years. Having 20 Motorola services phoning home and alerting me to signin to Motorola constantly is inexcusable, and makes this otherwise great phone a LEMON.
Is there a tool or method to strip out all of the Motorola junkware?
eeeee
derekm_ said:
Thanks, it's really disappointing that I can't have stock Android on a Moto G 2014 and have it somewhat easy to update. When is that going to change Google, come on, it's been the same ROM -> Bootloop -> flash -> brick -> hours of ADB and mfastboot for 5 or 6 years. Having 20 Motorola services phoning home and alerting me to signin to Motorola constantly is inexcusable, and makes this otherwise great phone a LEMON.
Is there a tool or method to strip out all of the Motorola junkware?
Edit: I don't understand, we have root, we have an unlocked bootloader, why can't this phone be 100% converted to a GPE phone? What's the technical limitation that's preventing this?
Click to expand...
Click to collapse
yeah all u gotta do is Root->install Titanium Backup->uninstall all unwanted bloatware
GPE---- well the gpe edition dosnt exist--
ak88900 said:
yeah all u gotta do is Root->install Titanium Backup->uninstall all unwanted bloatware
GPE---- well the gpe edition dosnt exist--
Click to expand...
Click to collapse
Oh, sweet, thank you so much!
It probably seems like a "duh" but this tip should be a sticky!
I never once have read somewhere that the Moto G 2014 doesn't have a Google Play Edition. Eventually I suspected that it didn't but only after an hour of flashing and bootloops.
So this is not the 2014 version? https://play.google.com/store/devices/details/Moto_G_Google_Play_edition_8GB?id=moto_g_8gb&hl=en Is the model number of the GPE phone I just linked to XT1032?
.
derekm_ said:
Oh, sweet, thank you so much!
It probably seems like a "duh" but this tip should be a sticky!
I never once have read somewhere that the Moto G 2014 doesn't have a Google Play Edition. Eventually I suspected that it didn't but only after an hour of flashing and bootloops.
So this is not the 2014 version? https://play.google.com/store/devices/details/Moto_G_Google_Play_edition_8GB?id=moto_g_8gb&hl=en What's the model number of the GPE phone I just linked to?
Click to expand...
Click to collapse
A varient of XT1032
Man you must be dumb if you think you can flash the moto g 2013 gpe rom to the 2nd generation moto g. It's like me trying to flash a GS5 or Note 4 ROM on my GS4. It will never work and results in a softbrick or worse. Also quit being so dramatic. This motorola rom is as close to stock android as you are gonna get from an OEM. If you want to get rid of the unintrusive motorola services just root and remove the unwanted apps with titanium backup.
ImperiousRex89 said:
Man you must be dumb if you think you can flash the moto g 2013 gpe rom to the 2nd generation moto g. It's like me trying to flash a GS5 or Note 4 ROM on my GS4. It will never work and results in a softbrick or worse. Also quit being so dramatic. This motorola rom is as close to stock android as you are gonna get from an OEM. If you want to get rid of the unintrusive motorola services just root and remove the unwanted apps with titanium backup.
Click to expand...
Click to collapse
It's certainly not obvious at first glance that there is not a GPE version of the 2014 version of the Moto G.
What's the technical reason that I can't flash the rom on a different device? Hardware driver support? Config files?
Is it really that difficult for Android to support having multiple drivers available for different hardware? Windows does it just fine. Linux does it.
I can't seem to root the XT1064, most people seem to end up in bootloops when trying to and so did I, so no Titanium Backup at the moment.
This is as close to stock as many manufacturers offer?? That's very disappointing.
derekm_ said:
It's certainly not obvious at first glance that there is not a GPE version of the 2014 version of the Moto G.
What's the technical reason that I can't flash the rom on a different device? Hardware driver support? Config files?
Is it really that difficult for Android to support having multiple drivers available for different hardware? Windows does it just fine. Linux does it.
I can't seem to root the XT1064, most people seem to end up in bootloops when trying to and so did I, so no Titanium Backup at the moment.
This is as close to stock as many manufacturers offer?? That's very disappointing.
Click to expand...
Click to collapse
dude try the root kernel(thanks to @savoca) and BETA-SUPERSU-v2.38.zip(http://forum.xda-developers.com/moto-g-2014/general/twrp-twrp-backup-t2964330) worked for me/
it takes about 10 minutes to boot...........
ak88900 said:
dude try the root kernel(thanks to @savoca) and BETA-SUPERSU-v2.38.zip(http://forum.xda-developers.com/moto-g-2014/general/twrp-twrp-backup-t2964330) worked for me/
it takes about 10 minutes to boot...........
Click to expand...
Click to collapse
Thanks, I'll try that today.
I tried the xt1064_lollipop_boot.img version yesterday with the 2.16, 2.35, 2.38, 2.39 but I might not have waited long enough on some of them (did wait 15+ minutes with 2.16 with no luck).
What screen was it on while booting? Was it ever a completely black screen (with backlight on) for an extended period of time?
What ROM / OS version were you on when you rooted it?
derekm_ said:
Thanks, I'll try that today.
I tried the xt1064_lollipop_boot.img version yesterday with the 2.16, 2.35, 2.38, 2.39 but I might not have waited long enough on some of them (did wait 15+ minutes with 2.16 with no luck).
What screen was it on while booting? Was it ever a completely black screen (with backlight on) for an extended period of time?
What ROM / OS version were you on when you rooted it?
Click to expand...
Click to collapse
i got the bootlogo for over 15mins.. and finally booted up...
i am using XT1068 Dual sim stock lollipop 22.11.16(XT1064 firmware):silly:
ak88900 said:
i got the bootlogo for over 15mins.. and finally booted up...
i am using XT1068 Dual sim stock lollipop 22.11.16(XT1064 firmware):silly:
Click to expand...
Click to collapse
Are you using the stock Lollipop recovery or TWRP?
How do you get into recovery from Lollipop? I've tried all different combinations of power/volume buttons but cannot get past the Broken Android screen.
By "flash SuperSU" does everyone mean using "adb sideload superSU.zip" from recovery?
derekm_ said:
Are you using the stock Lollipop recovery or TWRP?
How do you get into recovery from Lollipop? I've tried all different combinations of power/volume buttons but cannot get past the Broken Android screen.
By "flash SuperSU" does everyone mean using "adb sideload superSU.zip" from recovery?
Click to expand...
Click to collapse
The rom seems to replace the flashed Recovery with the stock..... I flash the recovery every time I want..... :-/
Place the SuperSU.zip(v2.38 beta worked for me). In your INTERNAL memory and boot into recovery(TWRP) flash it..
ak88900 said:
The rom seems to replace the flashed Recovery with the stock one...... I flash the recovery every time I want..... :-/
Place the SuperSU.zip(v2.38 beta worked for me). In your INTERNAL memory and boot into recovery(TWRP) flash it..
Click to expand...
Click to collapse
I pushed SuperSU 2.38 to /data/local/tmp/ because that's the only place that I could write to as far as I know.
I booted into recovery and installed SuperSU then rebooted (I didn't clear any cache manually).
The phone is on the Warning Bootloader Ulocked screen and rebooting. I'll let it sit for about 20 minutes and see if anything good happens. Thanks for the assistance.
Edit: is mine on the wrong screen? You said yours stayed on the "bootlogo", is that the Motorola splash screen or the "Warning Bootloader Unlocked" screen?
Edit: IT WORKED! Thank you!!
Edit: Looks like it's bootlooping after reboot.
derekm_ said:
I pushed SuperSU 2.38 to /data/local/tmp/ because that's the only place that I could write to as far as I know.
I booted into recovery and installed SuperSU then rebooted (I didn't clear any cache manually).
The phone is on the Warning Bootloader Ulocked screen and rebooting. I'll let it sit for about 20 minutes and see if anything good happens. Thanks for the assistance.
Edit: is mine on the wrong screen? You said yours stayed on the "bootlogo", is that the Motorola splash screen or the "Warning Bootloader Unlocked" screen?
Edit: IT WORKED! Thank you!!
Edit: Looks like it's bootlooping after reboot.
Click to expand...
Click to collapse
Yeah it bootloops at every reboot..... But eventually it'll boot up..... Hope someone comesup with a more stable rooting method