Hi, I just got my new phone yesterday, and I"m having issues actually turning the thing on. Yesterday, everything was going fine. Since I got the pure edition, I went ahead and unlocked the bootloader, and then ran the Auto Root program I found in the general section. After that, I installed some apps that I needed. I downloaded some videos to watch later, I downloaded some music, and then I installed AdAway.
Here's where I probably screwed up big time: I disabled some applications from the app picker (Help, E-Mail, and a few others). I was having some trouble with the Inbox app searching properly, so I re-enabled Gmail at least, but I left the others disabled. Then I connected the phone to my Coolstream Duo, which is a bluetooth audio device, and then went to sleep.
When I woke up, I was able to unlock my phone, but I unlocked it to only the back button available and Google+ on the screen. Nothing functioned, so I force powered off. Now I can't turn the device on, it either is stuck on the "Warning, unlocked bootloader" screen, or gets to the Motorola globe boot screen, playing half the animation before the screen goes black. Once, I booted and it got past all that to the "Android is upgrading" screen, and it optomized 38 apps, but then after it got to the unlock screen, the pattern wouldn't show up. I followed these factory reset instructions: https://motorola-global-portal.cust...detail/a_id/101072/p/30,6720,9197/reg/2380937 and they didn't seem to do anything. I also attempted to download the stock image for Android 4.4.4 but it said I wasn't allowed to access the file.
If anyone could recognize what I did wrong to my phone, that would be great, and if anyone could provide a link to a factory image of the phone so I can attempt to restore it, that would be awesome as well.
Sounds like flashing the 4.4.4 system image may solve your problem. Here is a link where you can grab the fxz without asking for permission from Moto.
https://onedrive.live.com/?cid=227f...20267&ithint=folder,&authkey=!AMWPTB3ICDtezYs
Dark9781 said:
Sounds like flashing the 4.4.4 system image may solve your problem. Here is a link where you can grab the fxz without asking for permission from Moto.
https://onedrive.live.com/?cid=227f...20267&ithint=folder,&authkey=!AMWPTB3ICDtezYs
Click to expand...
Click to collapse
Oddly enough, directly after writing this post, I stepped out of class to find my phone had booted and was on the welcome screen. But if anything bad happens again, I'll be sure to have this link ready! Thanks for the help!
Dark9781 said:
Sounds like flashing the 4.4.4 system image may solve your problem. Here is a link where you can grab the fxz without asking for permission from Moto.
https://onedrive.live.com/?cid=227f...20267&ithint=folder,&authkey=!AMWPTB3ICDtezYs
Click to expand...
Click to collapse
Hi,
can this stock rom get flashed trough fastboot or rsd lite? Maybe you can solve my problem!
incrazyboyy said:
Hi,
can this stock rom get flashed trough fastboot or rsd lite? Maybe you can solve my problem!
Click to expand...
Click to collapse
Either. The only thing with rsd lite is that it does not like USB 3.0. Your computer will need a USB 2.0 slot.
Dark9781 said:
Either. The only thing with rsd lite is that it does not like USB 3.0. Your computer will need a USB 2.0 slot.
Click to expand...
Click to collapse
Great! I would prefer flashing trough fastboot. Could you give me the instructions please?
Greetings,
Just bought a VZW Moto X 2014 loaded with 5.0. Unfortunately, right after I powered it on, it pulled down the 5.1 OTA, though it appears to have deferred the installation, which is good, as I intend to give it the MOFO treatment shortly.
Questions:
1. How can I continue to defer the installation?
2. If I do a factory reset (I still have another phone to use), assuming the 5.1. didn't install yet, will it wipe the download?
3. If I can factory reset and eliminate the 5.1 download, how can I avoid this repeating? With my original Moto X, I was able to freeze the MotoOTA after I rooted it.
TIA,
GG
Garageguy05 said:
Greetings,
Just bought a VZW Moto X 2014 loaded with 5.0. Unfortunately, right after I powered it on, it pulled down the 5.1 OTA, though it appears to have deferred the installation, which is good, as I intend to give it the MOFO treatment shortly.
Questions:
1. How can I continue to defer the installation?
2. If I do a factory reset (I still have another phone to use), assuming the 5.1. didn't install yet, will it wipe the download?
3. If I can factory reset and eliminate the 5.1 download, how can I avoid this repeating? With my original Moto X, I was able to freeze the MotoOTA after I rooted it.
TIA,
GG
Click to expand...
Click to collapse
Same thing. Freeze MotoOTA after rooting and clear your cache to get rid of the OTA file.
Thanks.
Do I need to worry about the update self-executing at some point, similar to what I saw on my HTC One? Or will it stay dormant until it is activated by the user?
GG
Garageguy05 said:
Thanks.
Do I need to worry about the update self-executing at some point, similar to what I saw on my HTC One? Or will it stay dormant until it is activated by the user?
GG
Click to expand...
Click to collapse
Not sure if it will. Best bet is to clear the cache once you freeze MotoOTA that way it will delete the OTA sitting on your device.
So I was running CF 1.3 base for quite a while with no issues. Two days ago my phone shut down on me and would not boot. I wipe everything multiple times. I wiped cache. I did a factory reset, nothing... I wiped again. Nothing.
It gets past the Motorola logo and then just sits at the boot screen. A couple of times it would say updating android, it would finish, but then it would go right back to the boot screen. After about 8 hours it finally booted and I used it all day yesterday. This morning my issue is back. I've flashed different images to see if it has something to do with 1.3. It's all the same. I think I might try to go back to kit kat. It seems to be a software problem, but I am starting to think that something most be wrong with my hardware.
I found this thread: https://forums.motorola.com/posts/b0021413e7
I think my phone is shot... Any ideas?
When I had my Razr Maxx I had an issue that was similar and nothing I tried would fix it. Factory reset cache wipe flashing different roms nothing. Finally I decided to factory restore it with RSD Lite and after that the problem went away and I was able to do everything again like normal. I don't know why a factory reset wouldn't fix it and that did but it did.
Thanks. That is my next step. Do you know where I can find the RSD image?
Is this what I need? http://forum.xda-developers.com/dro...quark-stock-firmware-moto-maxx-droid-t3063470
Do I need to worry about flashing radios and stuff back to 4.4.4?
Seems to be. Honestly I've used it on many Motorolas in the past but I haven't read much about using RSDlite on the turbo. I would just do some googling around I'm sure you'll find it
my2cents said:
So I was running CF 1.3 base for quite a while with no issues. Two days ago my phone shut down on me and would not boot. I wipe everything multiple times. I wiped cache. I did a factory reset, nothing... I wiped again. Nothing.
It gets past the Motorola logo and then just sits at the boot screen. A couple of times it would say updating android, it would finish, but then it would go right back to the boot screen. After about 8 hours it finally booted and I used it all day yesterday. This morning my issue is back. I've flashed different images to see if it has something to do with 1.3. It's all the same. I think I might try to go back to kit kat. It seems to be a software problem, but I am starting to think that something most be wrong with my hardware.
I found this thread: https://forums.motorola.com/posts/b0021413e7
I think my phone is shot... Any ideas?
Click to expand...
Click to collapse
This just happened to me yesterday. Long story short, I have a strong suspicion that something about the recent Moto Actions update is breaking our phones for reasons that I describe here: http://forum.xda-developers.com/droid-turbo/help/complicated-problem-restore-doesnt-help-t3184251. I managed to fix it, but I re-broke it because I'm an idiot and the method I used before isn't working. If you get it fixed and get your 1.3 CF image back up and running, I would strongly recommend against allowing the Moto Actions update. I have a feeling that we're going to be hearing more about this soon from other people.
TheSt33v said:
This just happened to me yesterday. Long story short, I have a strong suspicion that something about the recent Moto Actions update is breaking our phones for reasons that I describe here: http://forum.xda-developers.com/droid-turbo/help/complicated-problem-restore-doesnt-help-t3184251. I managed to fix it, but I re-broke it because I'm an idiot and the method I used before isn't working. If you get it fixed and get your 1.3 CF image back up and running, I would strongly recommend against allowing the Moto Actions update. I have a feeling that we're going to be hearing more about this soon from other people.
Click to expand...
Click to collapse
That makes sense, after I finally got mine going, I updated Moto Actions and all the other apps it crashed again in about 12 hours. If I can finally get it to boot again, I think I am going to test your theory. If you figure out how to get it booted again, please share!
Edit, which rootjunky image did you flash? SU2-12?
my2cents said:
That makes sense. Like an idiot, after I finally got mine going, I updated Moto Actions and it crashed again. If I can finally get it to boot again, I think I am going to test your theory. If you figure out how to get it booted again, please share!
Click to expand...
Click to collapse
I did get it booted again. I flashed the kitkat update (not the stock, stock update 1, which is what you should be on if you're using mofo) file on the firmware thread that was posted here using the version of RSDlite that was posted there. The key is just to wait a really, really long time. Even if the screen goes black, it could potentially still be booting, especially if the back of the phone gets warm. I left it plugged in, let it get to the boot animation and left the house for several hours, and when I got back it appeared to be functional, but things were slow and choppy at times and my home button didn't work. The settings menu from the pull down menu didn't work either. I had to access settings from the app drawer. I tried a factory reset from the settings menu, and that just re-broke everything. So now I'm back at square one. I re-flashed the same image using RSDlite again, and now I've waited about 10 minutes and I'm still looking at the boot screen, which at this point is normal since the problem occurred.
I got a hold of an old copy of the Motorola Sensor Services apk. As far as I can tell, this is the apk that is replaced by Moto Actions, which according to Google Play is only compatible with 5.0 and above. My plan for tonight is to wait until the thing decides to boot, attempt to start the stock Sensor Services app and get it to do the sensor firmware uninstall that I mentioned in my other post. If that doesn't work, I'm going to try to install the apk that I found and see if I have any more luck with that. I'll report back here when I get a chance to do that. Let me know if you figure out a solution.
---------- Post added at 03:48 PM ---------- Previous post was at 03:33 PM ----------
my2cents said:
That makes sense, after I finally got mine going, I updated Moto Actions and all the other apps it crashed again in about 12 hours. If I can finally get it to boot again, I think I am going to test your theory. If you figure out how to get it booted again, please share!
Edit, which rootjunky image did you flash? SU2-12?
Click to expand...
Click to collapse
Yeah, I used SU2-12.
I followed the procedure outlined here to go back to stock. https://www.youtube.com/watch?v=6avEPGWB8E0 I used the SU2-12 file, but I lost everything... Thanks for the help. I hope there is a fix for this soon! I'll test your idea about MOTO Actions and report.
Edit: Well, I thought my phone was booting when I wrote the above, but it has been 30 minutes and it has not booted...
So, I can get it to boot - although it is not easy and it takes me like 30 minutes and I haven't found a full proof method yet, but after it goes to sleep I have to start the process all over. It has been a frustrating 3 days.
TheSt33v said:
This just happened to me yesterday. Long story short, I have a strong suspicion that something about the recent Moto Actions update is breaking our phones for reasons that I describe here: http://forum.xda-developers.com/droid-turbo/help/complicated-problem-restore-doesnt-help-t3184251. I managed to fix it, but I re-broke it because I'm an idiot and the method I used before isn't working. If you get it fixed and get your 1.3 CF image back up and running, I would strongly recommend against allowing the Moto Actions update. I have a feeling that we're going to be hearing more about this soon from other people.
Click to expand...
Click to collapse
I think you are onto something. I'm currently on 4.4.4 and it is bone stock. When I go into the Play Store it shows that I have Moto Actions installed, but when I click on the app it says that it is not compatible with my device. I've tried wiping the data from the app, force closing it, and clearing the cache. None of that has prompted me to uninstall the sensors. By the way, I found the Moto sensors app and tried doing the same thing, no luck.
So, I think I have the 5.1 Moto Actions installed still, which is causing the 4.4.4 image to freak out. I've thought about trying to go official 5.1 and see if that fixes it, but since I have a replacement on the way, think I might just leave it be - unless someone (like you) figures this thing out.
my2cents said:
I think you are onto something. I'm currently on 4.4.4 and it is bone stock. When I go into the Play Store it shows that I have Moto Actions installed, but when I click on the app it says that it is not compatible with my device. I've tried wiping the data from the app, force closing it, and clearing the cache. None of that has prompted me to uninstall the sensors. By the way, I found the Moto sensors app and tried doing the same thing, no luck.
So, I think I have the 5.1 Moto Actions installed still, which is causing the 4.4.4 image to freak out. I've thought about trying to go official 5.1 and see if that fixes it, but since I have a replacement on the way, think I might just leave it be - unless someone (like you) figures this thing out.
Click to expand...
Click to collapse
I ended up getting a replacement from Motorola too. If it has 5.1 on it, I'll sell it and get one with 4.4.4. Thanks a lot for the tip, by the way. I might still work on it just as a hobby, but I'm out of ideas. Of all the many, many devices I've tinkered with, this is the first one that I ever permanently messed up, so I'd like to fix it as a matter of pride, but I now only have 48 hours to do so. After looking at logcats, the partition table of the phone and the androidmanifest.xml of the motorola sensor services apk, I'm pretty much certain that this app writes those sensor drivers to a partition other than the ones that get flashed when we up/downgrade (ie system, boot, recovery, etc.), which is why these processes don't fix the problem. Theoretically, if I knew which partition that was, I could find someone with a working Turbo who could dump that image, and if I get lucky and it's a partition that isn't sig checked by the bootloader (like the radios, for example), I could flash that and be good to go. I have no idea how to figure out which partition that would be, though. The obvious choice was the "firmware" partition, but that partition has a lot of drivers that seem to relate to lots of different important things, so messing with that seems scary. I also don't know anyone who is knowledgeable enough to generate that image (myself included), so it's a moot point.
TheSt33v said:
I ended up getting a replacement from Motorola too. If it has 5.1 on it, I'll sell it and get one with 4.4.4. Thanks a lot for the tip, by the way. I might still work on it just as a hobby, but I'm out of ideas. Of all the many, many devices I've tinkered with, this is the first one that I ever permanently messed up, so I'd like to fix it as a matter of pride, but I now only have 48 hours to do so. After looking at logcats, the partition table of the phone and the androidmanifest.xml of the motorola sensor services apk, I'm pretty much certain that this app writes those sensor drivers to a partition other than the ones that get flashed when we up/downgrade (ie system, boot, recovery, etc.), which is why these processes don't fix the problem. Theoretically, if I knew which partition that was, I could find someone with a working Turbo who could dump that image, and if I get lucky and it's a partition that isn't sig checked by the bootloader (like the radios, for example), I could flash that and be good to go. I have no idea how to figure out which partition that would be, though. The obvious choice was the "firmware" partition, but that partition has a lot of drivers that seem to relate to lots of different important things, so messing with that seems scary. I also don't know anyone who is knowledgeable enough to generate that image (myself included), so it's a moot point.
Click to expand...
Click to collapse
My question is why hasn't anyone else's device gotten borked since the update? I've had it since the update was distributed with no issues and use Moto Actions continuously. Seems like if it really is a combination of writing drivers to a partition that isn't compatible it would be a universal issue. If only 2 people who have a mofo'd 5.1 IMG (out of probably hundreds) experienced issues my bet is on some weird glitch that occured when you initially flashed the updated firmware to get 5.1 working on the mofo'd device, rather than some general driver incompatibility.
GeoFX said:
My question is why hasn't anyone else's device gotten borked since the update? I've had it since the update was distributed with no issues and use Moto Actions continuously. Seems like if it really is a combination of writing drivers to a partition that isn't compatible it would be a universal issue. If only 2 people who have a mofo'd 5.1 IMG (out of probably hundreds) experienced issues my bet is on some weird glitch that occured when you initially flashed the updated firmware to get 5.1 working on the mofo'd device, rather than some general driver incompatibility.
Click to expand...
Click to collapse
I agree. Either it was a corrupt driver installation that worked just well enough for the app not to realize it, or the firmware update happens silently only when requested (similar to Google play services), and we're all one chop chop flashlight away from a phone apocalypse. Hopefully it's the former.
So, I went ahead and updated my device to official 5.1 and the problem is still there. The moto actions app that is installed still says that it is not compatible with my phone. I have cant figure out how to clear it or delete it or anything. And when I think I have it, I let the phone sleep and I can't bring it back to life again without waiting for a 15 min+ boot. Oh well, at least the bootloader says "official" now rather than "modified." So, Motorola should not complain about it. Thanks for trying to figure it out @TheSt33v
my2cents said:
So, I went ahead and updated my device to official 5.1 and the problem is still there. The moto actions app that is installed still says that it is not compatible with my phone. I have cant figure out how to clear it or delete it or anything. And when I think I have it, I let the phone sleep and I can't bring it back to life again without waiting for a 15 min+ boot. Oh well, at least the bootloader says "official" now rather than "modified." So, Motorola should not complain about it. Thanks for trying to figure it out @TheSt33v
Click to expand...
Click to collapse
Good to know. I picked the $25 option specifically because the free one requires an inspection, but I'll probably update it anyway. I'm not surprised that it didn't solve the problem though. When we flash those upgrade/downgrade images, we're basically just doing manually what RSD lite/Verizon upgrade agent does automatically.
ctopher4
TheSt33v said:
This just happened to me yesterday. Long story short, I have a strong suspicion that something about the recent Moto Actions update is breaking our phones for reasons that I describe here: http://forum.xda-developers.com/droid-turbo/help/complicated-problem-restore-doesnt-help-t3184251. I managed to fix it, but I re-broke it because I'm an idiot and the method I used before isn't working. If you get it fixed and get your 1.3 CF image back up and running, I would strongly recommend against allowing the Moto Actions update. I have a feeling that we're going to be hearing more about this soon from other people.[/QUOTE]
you called it! Just spent 2 hours reflashing 1.3 first repeated V4A, then Base. flashing sick Android upon Recovery attempt, FAIL. reflashed radios and such and with different "vol& pwr" sequence was able to get in to wipe cache. Not hat it would help me but i viewed chche Logs and im wondering if, to the right person, it would help to have copies of them?? It's a bunch of pages tho and and not sure if it would help.
My plan it to, in Recovery, Factory wipe, then reboot to Bootloader and attempt to flash base. W/ all sys.img's, then wipe caches again. ihave read the whole thread early yesterday morning but i fell asleep prob 20 times during. it was like 3 ishi think SO, i'll now go re read probably to find that you've already ruled out "my plan"
Click to expand...
Click to collapse
ctopher4 said:
TheSt33v said:
This just happened to me yesterday. Long story short, I have a strong suspicion that something about the recent Moto Actions update is breaking our phones for reasons that I describe here: http://forum.xda-developers.com/droid-turbo/help/complicated-problem-restore-doesnt-help-t3184251. I managed to fix it, but I re-broke it because I'm an idiot and the method I used before isn't working. If you get it fixed and get your 1.3 CF image back up and running, I would strongly recommend against allowing the Moto Actions update. I have a feeling that we're going to be hearing more about this soon from other people.[/QUOTE]
you called it! Just spent 2 hours reflashing 1.3 first repeated V4A, then Base. flashing sick Android upon Recovery attempt, FAIL. reflashed radios and such and with different "vol& pwr" sequence was able to get in to wipe cache. Not hat it would help me but i viewed chche Logs and im wondering if, to the right person, it would help to have copies of them?? It's a bunch of pages tho and and not sure if it would help.
My plan it to, in Recovery, Factory wipe, then reboot to Bootloader and attempt to flash base. W/ all sys.img's, then wipe caches again. ihave read the whole thread early yesterday morning but i fell asleep prob 20 times during. it was like 3 ishi think SO, i'll now go re read probably to find that you've already ruled out "my plan"
Click to expand...
Click to collapse
Damn. I was hoping I was wrong. Yeah, I did what you suggested many, many times. If you end up reflashing 4.4.4 and you see the message to uninstall the sensor firmware, do it and FLASH NOTHING ELSE until a solution is found. If not, it's really easy to get a new one from Motorola.
Click to expand...
Click to collapse
TheSt33v said:
ctopher4 said:
Damn. I was hoping I was wrong. Yeah, I did what you suggested many, many times. If you end up reflashing 4.4.4 and you see the message to uninstall the sensor firmware, do it and FLASH NOTHING ELSE until a solution is found. If not, it's really easy to get a new one from Motorola.
Click to expand...
Click to collapse
O Jeez, xda gave me a " token timed out message" but only after I hit post reply and, it was a novel! I have to get at least 2.5 hours sleep tonight because that been normal lately. Besides setting up Moto functionality, I'm golden and I do have their updates blocked best I can anyway. Hope all is working.
Click to expand...
Click to collapse
ctopher4 said:
TheSt33v said:
O Jeez, xda gave me a " token timed out message" but only after I hit post reply and, it was a novel! I have to get at least 2.5 hours sleep tonight because that been normal lately. Besides setting up Moto functionality, I'm golden and I do have their updates blocked best I can anyway. Hope all is working.
Click to expand...
Click to collapse
Awesome! Well I managed to fix it too, Moto functionality included!!!! I'll explain on my other thread.
Click to expand...
Click to collapse
What was the solution that found? I'm going through the same problem.
First of all, sorry if I'm writing to a wrong forum or thread, it's very difficult to find anything on this forum...
I really need help with my device as I've tried everything available on the Internet and haven't got the desired result.
My device is Motorola Moto G5 Plus XT1685 (Spain) bought from Amazon in December.
I want to root it.
First try failed, and the device got bricked (or whatever you call it, the system was erased).
So I installed this:
POTTER_RETAIL_7.0_NPN25.137-92_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
The system worked normally.
I proceeded with the instructions given on the internet: unlock, flash twrp, format data, flash boot, install the wifi patch, install SuperSu.
Great, it worked, the system loaded, the device was unlocked. BUT! The camera didn't work. I've tried all the solutions offered on the Internet, I really did. I re-rooted it again and found that the camera goes wrong with the boot kernel image.
So I used the image from the aforementioned potter pack. It went well, device rooted, camera works. But there is no wifi modem. Yes, I installed the wifi patch, several times, from the recovery mode.
So, it's either camera and wifi or root... Is there any solution for moto g5 plus xt1685 to have root AND camera and wifi?
Thank you.
PS: Magisk didn't work at all.
Northin said:
First of all, sorry if I'm writing to a wrong forum or thread, it's very difficult to find anything on this forum...
I really need help with my device as I've tried everything available on the Internet and haven't got the desired result.
My device is Motorola Moto G5 Plus XT1685 (Spain) bought from Amazon in December.
I want to root it.
First try failed, and the device got bricked (or whatever you call it, the system was erased).
So I installed this:
POTTER_RETAIL_7.0_NPN25.137-92_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
The system worked normally.
I proceeded with the instructions given on the internet: unlock, flash twrp, format data, flash boot, install the wifi patch, install SuperSu.
Great, it worked, the system loaded, the device was unlocked. BUT! The camera didn't work. I've tried all the solutions offered on the Internet, I really did. I re-rooted it again and found that the camera goes wrong with the boot kernel image.
So I used the image from the aforementioned potter pack. It went well, device rooted, camera works. But there is no wifi modem. Yes, I installed the wifi patch, several times, from the recovery mode.
So, it's either camera and wifi or root... Is there any solution for moto g5 plus xt1685 to have root AND camera and wifi?
Thank you.
Click to expand...
Click to collapse
Northin said:
PS: Magisk didn't work at all.
Click to expand...
Click to collapse
You're right - posting in the wrong forum. Your question belongs here which is where the expertise resides for your device. This is not a SuperSU issue.
How can I ask for help? I cannot post anything on that forum, the system doesn't let me.
Northin said:
How can I ask for help? I cannot post anything on that forum, the system doesn't let me.
Click to expand...
Click to collapse
General and Help sections are open to all; developer/development sections are restricted. As is the case with most device centric forums on XDA.