Database Develop

Andoid 4.3 Discussion

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

[Q] Moto X Not Booting after trying to root PLEASE HELP

I just got my Moto X 2014 Pure Edition in the mail yesterday and now I've gone and tried to root it.
I had already unlocked the bootloader and then being giddy I installed android 5 since I wanted to try it out. From here, I messed up. I tried to root it using the Superboot method. Unfortunately, I didn't realize this was for the 4.4.4 build.
After flashing the image, I was able to get back into the OS, but I wasn't able to install apps or get to the home screen. I could still browse still open chrome windows, but I couldn't get to home. Next, I tried CF Auto Root, as that was built for 5.0. Executed just fine, but when I got back into the phone, I kept having the same problem. Now when I boot, It gets past the moto animations and then sits on the moto logo that looks like water. It just stays there.
If I try to turn off the phone, it just repeats this. If I put it into fastboot mode, it can act in there just fine. So I tried getting into recovery, but when I got back to the android on it's back saying "NO COMMAND.", I tried holding down up and power, just like everyone says. Doing this, though, reboots the phone normally and it goes back to the same problem as it was before!
If anyone has any suggestions, I'd really appreciate it. I'm having a mild breakdown right now

afran646 said:
I just got my Moto X 2014 Pure Edition in the mail yesterday and now I've gone and tried to root it.
I had already unlocked the bootloader and then being giddy I installed android 5 since I wanted to try it out. From here, I messed up. I tried to root it using the Superboot method. Unfortunately, I didn't realize this was for the 4.4.4 build.
After flashing the image, I was able to get back into the OS, but I wasn't able to install apps or get to the home screen. I could still browse still open chrome windows, but I couldn't get to home. Next, I tried CF Auto Root, as that was built for 5.0. Executed just fine, but when I got back into the phone, I kept having the same problem. Now when I boot, It gets past the moto animations and then sits on the moto logo that looks like water. It just stays there.
If I try to turn off the phone, it just repeats this. If I put it into fastboot mode, it can act in there just fine. So I tried getting into recovery, but when I got back to the android on it's back saying "NO COMMAND.", I tried holding down up and power, just like everyone says. Doing this, though, reboots the phone normally and it goes back to the same problem as it was before!
If anyone has any suggestions, I'd really appreciate it. I'm having a mild breakdown right now
Click to expand...
Click to collapse
Easiest thing to do is to go to:
https://accounts.motorola.com/ssoau...edirect/standalone/bootloader/recovery-images
and log in then find the right link for Moto X Pure Edition and click the "Request Firmware" link. When you get the email giving you access to the link then following the instructions for flashing it via fastboot.

crpalmer said:
Easiest thing to do is to go to:
and log in then find the right link for Moto X Pure Edition and click the "Request Firmware" link. When you get the email giving you access to the link then following the instructions for flashing it via fastboot.
Click to expand...
Click to collapse
Thank you so much for this! I had eventually found a fix through a lot of tinkering, but thank you for replying with the link for the firmware. I was looking everywhere for it!

I had the same issue. I have no idea what I did to cause it. Eventually I found a fix somewhere to fastboot into twrp recovery from the computer, and fix the file system. Then I flashed kitkat and updated from there.
Sent from my Nexus 5 using XDA Free mobile app

Recovery image or fix?
can you guys post your fixes? I am stuck with the same issue and have been waiting for over an hour for Moto to send me the recovery image. Thanks!

Xtchico..look at solartrans guide to get on lollipop. You basically have to downgrade to 4.4.4...then you'll get the 5.0 ota ..then use the tools to unlock..root and install recovery.
That's what worked for me. I was stuck on the water ripple M .
Sent from my XT1095 using XDA Free mobile app

fastercon said:
Xtchico..look at solartrans guide to get on lollipop. You basically have to downgrade to 4.4.4...then you'll get the 5.0 ota ..then use the tools to unlock..root and install recovery.
That's what worked for me. I was stuck on the water ripple M .
Sent from my XT1095 using XDA Free mobile app
Click to expand...
Click to collapse
This is exactly the guide that I used and the fix action which worked for me. Thank you sir for finding it! I'd been trying to find it to give him credit. It works wonders and I haven't had an issue since.
Rooted my phone, loaded my applications and tweaked it to my liking. Now all that's left is to activate it.

[Q] [XT1064] Is it possible to convert XT1064 to GPE (Google Play Edition)?

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

Phone Won't Boot After Root - Please help!

Hey guys!
So I really wanted to try out Xposed and get some modules working on my phone. So I unlocked the bootloader by following the directions from Motorola. I then used the moto x 2014 multitool to install twrp recovery and to root (#2 and #7).
I then installed the Xposed apk and flashed the zip file. All Seemed well until I started getting massive amounts of lag if my phone was on for more than 2 minutes. I thought it might be Xposed so I uninstalled it (and the 2 modules that I had installed -- youtube ad blocker and xmultiwindow). That didn't fix it though. So then I thought it might be supersu, so I updated that. That didn't work either.
So then I went back to the multitool and I chose #5... and now it won't boot. It shows the "warning bootloader unlocked" screen and then shows the motorola boot screen for 20 seconds, then shuts off. I also can't boot into fastboot by pressing down the power and volume down buttons.
Any help would be super appreciated!! I'm really not experienced with this stuff but, I had a nexus s with cyanogenmod on it which I loved and then I rooted my note 4 but that's it...
Thank you!!!
EDIT: I can get into fastboot mode, so far I just tried to select 'factory' and it went through the same "bootloader unlocked" then motorola boot for 20 seconds before shutting off...

Maybe try getting to fastboot, selecting recovery, and then wiping cache and dalvik

dictionary said:
Maybe try getting to fastboot, selecting recovery, and then wiping cache and dalvik
Click to expand...
Click to collapse
Ok I actually just got into fastboot and did a factory reset. It put me back on 4.4.4 so I'm updating to 5.1 right now.
What is the proper method to installing Xposed on this phone? I'd really like the multiwindow and adblock modules... but the intense lag that would freeze my phone after 2 minutes was just too much.

HinaPanda said:
Ok I actually just got into fastboot and did a factory reset. It put me back on 4.4.4 so I'm updating to 5.1 right now.
What is the proper method to installing Xposed on this phone? I'd really like the multiwindow and adblock modules... but the intense lag that would freeze my phone after 2 minutes was just too much.
Click to expand...
Click to collapse
For that I don't have an answer. I don't really have a need for Xposed much anymore, so I haven't been following. Sorry

HinaPanda said:
Ok I actually just got into fastboot and did a factory reset. It put me back on 4.4.4 so I'm updating to 5.1 right now.
What is the proper method to installing Xposed on this phone? I'd really like the multiwindow and adblock modules... but the intense lag that would freeze my phone after 2 minutes was just too much.
Click to expand...
Click to collapse
If you're on 5.1:
First, go here http://forum.xda-developers.com/showthread.php?t=3034811
You will need to download the XposedInstaller_3.0_alpha4.apk and the Xposed-v74-sdk22-arm.zip. It wouldn't hurt to go ahead and download the xposed-uninstaller-20150831-arm.zip either, in case you have problems.
Now you need TWRP. Flash it using fastboot by typing fastboot flash recovery (name of recovery image file.img) from a terminal. Or download TWRP Manager from the Play Store and flash it from there.
Finally, flash the Xposed-v74-sdk22-arm.zip in TWRP. Reboot and install the XposedInstaller_3.0_alpha4.apk.

If you already have root, install TWRP from the Play Store. Otherwise, install it by using fastboot.
dictionary said:
For that I don't have an answer. I don't really have a need for Xposed much anymore, so I haven't been following. Sorry
Click to expand...
Click to collapse
Care to share why?

Phoenix232 said:
If you already have root, install TWRP from the Play Store. Otherwise, install it by using fastboot.
Care to share why?
Click to expand...
Click to collapse
I'd used it a lot when I had my htc m7 with sense, and lg g3 with stock. All I used it for were really mods to make it more AOSP like. There were some features that I miss, like FakeWifi, and App Settings, to name two, but overall with AOSP ROMs out, I haven't had as much desire.

Ok... so the update bricked the phone even more I didn't see the threads that said to not do the OTA update from 4.4.4.
I connect it to the computer and see the qhsusb_bulk. I installed the drivers and now I see the qualcomm 9008. I tried using a couple of blankflash files to fix it, but none of them work. Even ones that say they're for the moto x 2014. Is there anything I can do? I can't get it into fastboot mode... I was able to but then I don't know what happened and now I can't.
Can I send it into motorola for a warranty repair? I have a pure edition and I live in the US. I don't know if unlocking the bootloader and rooting will cause motorola to not repair it.

HinaPanda said:
I can't get it into fastboot mode... I was able to but then I don't know what happened and now I can't.
Click to expand...
Click to collapse
Sometimes when your phone is messed up, it can take quite a while for the bootloader to start. If the phone is off, hold down the volume down/power button combo for a long time, like 20-30 seconds before releasing them. Then wait several seconds for the bootloader screen to appear, be patient. If the phone starts to boot, hold the vol down/power combo until the phone shuts off, continue holding for 15-30 seconds and then release, again wait a long time for the bootloader screen to appear. I don't have anything else for you but know that many times I've caused myself grief by not being patient getting into the bootloader/fastboot mode when a problem has arisen!

mikeoswego said:
Sometimes when your phone is messed up, it can take quite a while for the bootloader to start. If the phone is off, hold down the volume down/power button combo for a long time, like 20-30 seconds before releasing them. Then wait several seconds for the bootloader screen to appear, be patient. If the phone starts to boot, hold the vol down/power combo until the phone shuts off, continue holding for 15-30 seconds and then release, again wait a long time for the bootloader screen to appear. I don't have anything else for you but know that many times I've caused myself grief by not being patient getting into the bootloader/fastboot mode when a problem has arisen!
Click to expand...
Click to collapse
Thank you! But I actually did try holding down the power button alone and also the power + vol down for like 2 minutes or 30 seconds, etc. The 2 minutes worked the first time, but now it won't It just blinks a green light. Does that mean it's out of battery? I left it plugged into a wall charger overnight though.. how can I tell it's charging?

It sounds like you have a hard brick. Only way to fix it is to send it to a repair center.
Sent from my XT1095 using Tapatalk

Yeah.. I just called motorola and the rep said they had to check on the unlocked bootloader voiding warranty thing. I told him that because I have the pure edition phone, it shouldn't void the warranty. Plus, it's bricked because of the OTA update from 4.4.4, which I believe is motorola's fault.
Does anyone have any link to a motorola statement saying that unlocking the bootloader on the pure edition does not void warranty? The rep said they'd call me back tomorrow. I tried searching on the 'netz but didn't find much.
Pure edition = developer edition, right?

HinaPanda said:
Yeah.. I just called motorola and the rep said they had to check on the unlocked bootloader voiding warranty thing. I told him that because I have the pure edition phone, it shouldn't void the warranty. Plus, it's bricked because of the OTA update from 4.4.4, which I believe is motorola's fault.
Does anyone have any link to a motorola statement saying that unlocking the bootloader on the pure edition does not void warranty? The rep said they'd call me back tomorrow. I tried searching on the 'netz but didn't find much.
Pure edition = developer edition, right?
Click to expand...
Click to collapse
http://forum.xda-developers.com/moto-x-2014/general/unlocking-bootloader-moto-x-pure-t3004779
Looks like information is all over the place. Bummer. Hope it works out for you, especially since it was an ota. They could be cheats and try to say it failed due to the unlocked bootloader, and if you'd had root, but that would be a lie. If this rep denies you, just call back and speak to someone else.

Attempted UnRooting and seems SoftBricked

I recently pulled my old Note 3 out of the drawer to do some misc tweaks, and think i screwed it all up...LMFAO!!!
Quick specs of phone...
Samsung Galaxy Note III (AT&T SM-N900A) 64gb (yes, i said 64gb and not 32gb)...but NOT why I am posting, so please don't even comment about it.
Steps that led to where I am...
First off I will say the device was originally rooted 4.3 back in 2013, and never updated since. Today I decided I wanted to update the phone to the last OS that worked perfect for a root, no i didn't just update it. I followed SuperSU's & TWRP instructions on first bringing the phone back to stock, didn't work and left me in recovery mode. Again, doubtful but may have been caused by me. So I was left with a wipe/restore because every time I attempted recovery via OneClickBin it would fail. After wipe/restore I was able to reinstall SuperSU and device was still rooted, obviously. So I attempted to completely remove root through SuperSU and it just kept getting stuck on spinning wheel. So then I attempted to reinstall TWRP and now I am stuck at the screen shown below in screen shots. Thanks in advance for any and all assistance, regarding this matter.
-Semper Fi

Oh yeah...and I'm a total and permanent disabled Veteran who doesn't have the ability to "go to AT&T store". So lets please try to fix this without going anywhere. Thanks again in advance.

Wrong forum you want the. A&TT note 3 forum .
Sent from my SM-N930F using XDA-Developers Legacy app

If the phone doesn't have a locked bootloader, you can try flashing back to stock with Odin and then run ota updates until the phone is running the latest stock ROM.

AT&T variant have a locked bootloader. You can't use TWRP or any other custom recovery.
Please follow this guide to fix your softbrick, root and update.

zlazaar said:
AT&T variant have a locked bootloader. You can't use TWRP or any other custom recovery.
Please follow this guide to fix your softbrick, root and update.
Click to expand...
Click to collapse
This was EXACTLY what I needed and worked flawless!! And I am so sorry for not responding sooner, as I have been in the hospital again.

DONE!! Thank You to those that helped!!