Related
Just flashed ViperOne 3.1.0 and since then my Google Wallet Tap to Pay hasn't worked. In the Settings - About it says "Unavailable (NfcPaymentSetupFailure: 1)" I've hard reset and reflashed, but I have not reflashed a different ROM, and since nobody else in the ROM thread seems to be having (or have noticed) this issue, I was looking for some sort of guidance.
Fatmouse said:
Just flashed ViperOne 3.1.0 and since then my Google Wallet Tap to Pay hasn't worked. In the Settings - About it says "Unavailable (NfcPaymentSetupFailure: 1)" I've hard reset and reflashed, but I have not reflashed a different ROM, and since nobody else in the ROM thread seems to be having (or have noticed) this issue, I was looking for some sort of guidance.
Click to expand...
Click to collapse
I tried to roll back the update by installing a previous version, then updating.I have the same problem though, I sent an email regarding that to google. I should find out if there is a fix from them in a few days. Im assuming it will be fixed in the next update. Bummer for sure, Cool rom though!
GravyD said:
I tried to roll back the update by installing a previous version, then updating.I have the same problem though, I sent an email regarding that to google. I should find out if there is a fix from them in a few days. Im assuming it will be fixed in the next update. Bummer for sure, Cool rom though!
Click to expand...
Click to collapse
I'm pretty sure the newest firmware is required for it to work. I had it working before flashing to the ViperONE Rom and since then the tap to pay has failed to setup, yet, others in the ViperONE forum say that it works fine for them, but they are on the newest firmware as well.
I'm looking for a link and am going to flash it to see, I'll report back here and the Fiper forum when I'm done with my findings.
EDIT: Nope, firmware didn't matter. My NFC chip si working, I've tested that. But I even unlinked my phone, uninstalled Wallet and re-installed and I get the same error.
EDIT 2 GOT IT WORKING: For anyone else having this issue I seem to have fixed it.
For whatever reason my build.prop wasn't quite right. There is suppose to be a ro.product.model and a ro.product.brand but mine was a little wonky and showed 2 ro.product.brands, under one of them is suppose to be htc but the other said "htcro.product.model=HTCONE" I edited this one using Root tool box to be ro.product.model and changed it's value to HTCONE. rebooted and google wallet doesn't show the error anymore. going to the google wallet website also reflects the fix. Instead of showing a device as "unknown" it shows it as "HTCONE" Now time to go test it.
Can't thank you enough. Fix worked for me
im pretty happy with kk, but i do want to be on 5.0, so i just wanted to make a few thing clear first.
1. if anything goes wrong with flashing a captured ota, how to restore my kk as it is now? will simply restoring a twrp backup do the trick on any stock rom?
2. where can i find the stock rom? the motorola site links arent working for me.
3. the quicksettings panel. is there a way/mod/app/ that will let me pull down quicksettings with one swipe like on cm and with gravitybox?
4.i really like to be able to customize the quicksettings, is that possible?
5. are there any bugs that seriously affect most users?
i am planning to root immediately so root only mods are fine.
im on a rooted unlocked bootloader xt1063,
thanks for your time,!
1. Just flash the stock ROM via fastboot.
2. I guess are some links on the Development section.
3. in 5.0, unfortunately not.
4. I guess no :/
5. Only a bootloop that happens with the newest versions of SuperSU (the only versions that works with 5.0), no major bugs..
Sent from my XT1063 using XDA Free mobile app
thanks for your fast response
is there a fix for said bootloop yet? can you show me a link?
Kobro said:
thanks for your fast response
is there a fix for said bootloop yet? can you show me a link?
Click to expand...
Click to collapse
When I ran into that problem I just hard reset (hold power button until it reboots) then let it run the course. After another reboot it came up to the lock screen and all was well. I have not had any issues since.
That said, I suspect if I had just left it for a few minutes without the hard reset it would have been fine. My tendency (as is the case with most people in these forums) is to be impatient, and jump the gun before things are completed.
The first reboot after installing Lollipop takes a while so don't get impatient.
I am using an XT1063.
pastorbob62 said:
When I ran into that problem I just hard reset (hold power button until it reboots) then let it run the course. After another reboot it came up to the lock screen and all was well. I have not had any issues since.
That said, I suspect if I had just left it for a few minutes without the hard reset it would have been fine. My tendency (as is the case with most people in these forums) is to be impatient, and jump the gun before things are completed.
The first reboot after installing Lollipop takes a while so don't get impatient.
I am using an XT1063.
Click to expand...
Click to collapse
lol im no noob to flashing roms and updates, i am new to lollipop
thanks so much for your info, it is very helpful.
Kobro said:
lol im no noob to flashing roms and updates, i am new to lollipop
thanks so much for your info, it is very helpful.
Click to expand...
Click to collapse
I wasn't implying you were a noob, just sharing my experience with you since you asked the question. Every device has its own quirks and idiosyncrasies. And I have seen posts from people with apparent considerable experience that displays much impatience.
Kobro said:
3. the quicksettings panel. is there a way/mod/app/ that will let me pull down quicksettings with one swipe like on cm and with gravitybox?
4.i really like to be able to customize the quicksettings, is that possible?
Click to expand...
Click to collapse
Try pulling down with two fingers instead of one- I've heard that this is the shortcut for the quick settings. (I don't have a device w/ 5 to try.) I think Google has also made the tiles in the quick settings dynamic and "smart" based on what you use most often. I tend to prefer having a static view and knowing exactly which ones are present (and in the same place!), but I won't know until I actually use it more.
I have the US GSM variant (XT1064) which came preloaded with 21.11.23. The OTA I've found only applies to 21.11.17 (the original release), and I've not had any luck downgrading. Good luck in your Lollipop quest!
Flash custom rom and enjoy lollipop
pastorbob62 said:
I wasn't implying you were a noob, just sharing my experience with you since you asked the question. Every device has its own quirks and idiosyncrasies. And I have seen posts from people with apparent considerable experience that displays much impatience.
Click to expand...
Click to collapse
your right for stating everything clearly, my bad
anomalyconcept said:
Try pulling down with two fingers instead of one- I've heard that this is the shortcut for the quick settings. (I don't have a device w/ 5 to try.) I think Google has also made the tiles in the quick settings dynamic and "smart" based on what you use most often. I tend to prefer having a static view and knowing exactly which ones are present (and in the same place!), but I won't know until I actually use it more.
I have the US GSM variant (XT1064) which came preloaded with 21.11.23. The OTA I've found only applies to 21.11.17 (the original release), and I've not had any luck downgrading. Good luck in your Lollipop quest!
Click to expand...
Click to collapse
yes that works, and has been since 4.3, on my custom rom devices it just is not so comfortable on a 5" device i was thinking more of something like pull down from right.
these responses motorola about the model xt1068
Catherine: Hi, my name is Catherine. How may I help you?
ENRICO: good morning
are to hold model xt1068, I wanted to know when will the update to Android 5
Catherine: Hi, at the moment we do not have a release date for Lollipop in Europe. It is currently going through testing before release but we are working hard to get it out as soon as possible. You can find the latest information at http://www.motorola.com/updates
ENRICO: thanks
Catherine: No problem, is there anything else that I can help you with?
ENRICO: no thanks
Catherine: Ok, have a nice day!
ENRICO:
pastorbob62 said:
When I ran into that problem I just hard reset (hold power button until it reboots) then let it run the course. After another reboot it came up to the lock screen and all was well. I have not had any issues since.
That said, I suspect if I had just left it for a few minutes without the hard reset it would have been fine. My tendency (as is the case with most people in these forums) is to be impatient, and jump the gun before things are completed.
The first reboot after installing Lollipop takes a while so don't get impatient.
I am using an XT1063.
Click to expand...
Click to collapse
just wanted to let you know, i have successfully flashed lollipop, rooted with twrp, run into the bootloop, found a solution in the general forum, (wipe cache and dalvik) and voila rooted 5.0
thanks for all your input.
Kobro said:
just wanted to let you know, i have successfully flashed lollipop, rooted with twrp, run into the bootloop, found a solution in the general forum, (wipe cache and dalvik) and voila rooted 5.0
thanks for all your input.
Click to expand...
Click to collapse
Don't need it now, but good to know should I have to reflash in the future. Thanks for the info. :good:
Q&A for N6-Shamu-LMY48I-DEODEXED-ROOTED v1.0 08/10/2015
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for N6-Shamu-LMY48I-DEODEXED-ROOTED v1.0 08/10/2015. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Hello friends...
First, thank you for your efforts. We certainly appreciate them out here (I sure do).
I have a question about this ROM. First some background on my current Nexus 6 setup ...
Recently, I installed a pre-rooted Stock ROM from developer 'danvhd'. The exact version and features are mentioned at the top of this article: http://www.ibtimes.co.uk/how-instal...-1-1-lollipop-lmy47z-firmware-nexus-6-1503624).
So that is my current ROM and configuration: LMY47Z; Stock; Rooted; Unencrypted.
(Q1) If I now update to this LMY48I ROM (provided by 'fhem' - thank you), will I essentially end up with the same configuration as above (i.e.stock, root unencrypted), except that StageFright and other fixes/enhancements will be included? Just double checking.
(Q2) Looking at the instructions provided by 'fhem', it looks like I need to (1) first backup my 'Data & settings', then (2) wipe everything twice, then (3) install this new ROM, and finally, (4) restore my 'Data & settings' from backup. Is this sequence correct? I don't want to lose my application, data and settings. (P.S. I'll be using TWRP for all of this).
Thank you in advance!
nyceyes said:
Hello friends...
First, thank you for your efforts. We certainly appreciate them out here (I sure do).
I have a question about this ROM. First some background on my current Nexus 6 setup ...
Recently, I installed a pre-rooted Stock ROM from developer 'danvhd'. The exact version and features are mentioned at the top of this article: http://www.ibtimes.co.uk/how-instal...-1-1-lollipop-lmy47z-firmware-nexus-6-1503624).
So that is my current ROM and configuration: LMY47Z; Stock; Rooted; Unencrypted.
(Q1) If I now update to this LMY48I ROM (provided by 'fhem' - thank you), will I essentially end up with the same configuration as above (i.e.stock, root unencrypted), except that StageFright and other fixes/enhancements will be included? Just double checking.
(Q2) Looking at the instructions provided by 'fhem', it looks like I need to (1) first backup my 'Data & settings', then (2) wipe everything twice, then (3) install this new ROM, and finally, (4) restore my 'Data & settings' from backup. Is this sequence correct? I don't want to lose my application, data and settings. (P.S. I'll be using TWRP for all of this).
Thank you in advance!
Click to expand...
Click to collapse
Sounds like you got it right. I would not restore data until after I updated all the Goolge apps from the play store after your first. FYI. This rom is deodexed not sure what you running now. I would also update your bootloader. I'm currently using 71.11 from M preview MPZ79M. It is backward compatible. Hope this helps let us know how you make out. Good luck.
Thank you! I don't know which bootloader I'm running. I never explicitly updated that and, assuming that the installation of TWRP or my use of Nexus Root Toolkit (NRT) didn't somehow update it in the past, it's probably whatever came with the phone? I'm guessing.
I'll report back my update results. Fingers crossed. XxX. Thanks again.
Hi @fhem... Just to report back that I successfully upgraded my phone to your ROM, using the procedure I outlined above, with a little tweak to allow Google Play and stock apps to update on first boot (per your advice). As you mentioned, that part took a little coaxing (I even had to reboot once), but it eventually updates. After that, I re-entered recovery (again all of this is done via TWRP), and restored my DATA backup. It all worked flawlessly. Now, the little StageFright checker app from our friends at 'Lookout', reports that there is no vulnerability.
My phone works on Sprint (via Ting MVNO), so others can know.
Thank you again very much for this ROM.
nyceyes said:
Hi @fhem... Just to report back that I successfully upgraded my phone to your ROM, using the procedure I outlined above, with a little tweak to allow Google Play and stock apps to update on first boot (per your advice). As you mentioned, that part took a little coaxing (I even had to reboot once), but it eventually updates. After that, I re-entered recovery (again all of this is done via TWRP), and restored my DATA backup. It all worked flawlessly. Now, the little StageFright checker app from our friends at 'Lookout', reports that there is no vulnerability.
My phone works on Sprint (via Ting MVNO), so others can know.
Thank you again very much for this ROM.
Click to expand...
Click to collapse
Im glad it worked for you. Thanks for letting us know. Enjoy
You're welcome. When I get to a browser, I'll find the little Thanks button and click it. I actually typed all of this on Tapatalk via my upgraded phone. LOL
nyceyes said:
You're welcome. When I get to a browser, I'll find the little Thanks button and click it. I actually typed all of this on Tapatalk via my upgraded phone. LOL
Click to expand...
Click to collapse
np the thx button is always appreciated ---- enjoy,
Why is data wipe necessary?
Hi, I just downloaded the ROM and installed as described. What I did differently: I did not wipe data. The result seems to be perfectly fine from what I can tell. Is there a reason why data wipe is described as part of the procedure? Might there be something wrong now without me noticing it?
Thanks
abseitsderwege said:
Hi, I just downloaded the ROM and installed as described. What I did differently: I did not wipe data. The result seems to be perfectly fine from what I can tell. Is there a reason why data wipe is described as part of the procedure? Might there be something wrong now without me noticing it?
Thanks
Click to expand...
Click to collapse
If all works Ok should be good to go. I always wipe just to eliminate potential issues caused by dirty flash. I personally prefer clean flashes when I'm installing/testing --- easier to chase down problems if you start clean. You should be good no worries.
abseitsderwege said:
Hi, I just downloaded the ROM and installed as described. What I did differently: I did not wipe data. The result seems to be perfectly fine from what I can tell. Is there a reason why data wipe is described as part of the procedure? Might there be something wrong now without me noticing it?
Thanks
Click to expand...
Click to collapse
Data wipes are only usually necessary when changing rom bases. As this is stock and you are coming from stock should be no problem. If was coming from like AOSP I would probably wipe data.
Still vulnerability?
Hi, after installing this ROM Stagefright Detector by Zimperium stills reports vulnerability CVE-2015-3864 whereas the lookout mobile security detector reports nothing. What's going on?
Anybody with an idea?
abseitsderwege said:
Hi, after installing this ROM Stagefright Detector by Zimperium stills reports vulnerability CVE-2015-3864 whereas the lookout mobile security detector reports nothing. What's going on?
Anybody with an idea?
Click to expand...
Click to collapse
Did you update your Zimperium. Original was borked. 2nd version showed not vulnerable. It is all besides the point as they found a another vulnerable point not patched that won't be out till next security update. Remove the tin foil hat and rest assured no one is currently exploiting the vulnerability and other security measures in Android make most hacks inoperable. Those that are decrypting their devices are putting themselves at more risk than this exploit.
Question... I noticed (after upgrading to this ROM) that Advanced Task killer (or any of the alternatives) can no longer see tasks to kill. Now I don't use it much actually, and I also don't have any auto-kill stuff setup. So it's not a big deal. I simply have it installed only for when it's necessary to kill a non-responsive app (which happens rarely). Anyway, is the nature of this deodexed ROM such that you can't see running tasks in tasks killers? Just curious to understand why I can't see them anymore. No big deal. Thanks.
nyceyes said:
Question... I noticed (after upgrading to this ROM) that Advanced Task killer (or any of the alternatives) can no longer see tasks to kill. Now I don't use it much actually, and I also don't have any auto-kill stuff setup. So it's not a big deal. I simply have it installed only for when it's necessary to kill a non-responsive app (which happens rarely). Anyway, is the nature of this deodexed ROM such that you can't see running tasks in tasks killers? Just curious to understand why I can't see them anymore. No big deal. Thanks.
Click to expand...
Click to collapse
Those old apps no longer work with latest updates.
prdog1 said:
Those old apps no longer work with latest updates.
Click to expand...
Click to collapse
Ah, okay. Thank you.
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.
hey guys hope all is well
so i may have somewhat softbricked my g4 dont really know how but i will explain what i did
hopefully someone can point out where i went wrong and how to fix it
Step #1
got root using this guide previously used the guide to get root on my ATT LGG4 worked fine
so got root, was successful everything worked fine
step #2
installed flashify
granted root access; all good
installed TWRP via flashify; all good
step #3 backup via TWRP all good
step #4 flashed G4H811 10N xTreme ROM v2.0 from this via TWRP; All good
step #5 attempt to install xposed framework 64bit from xposed respository via TWRP
supposedly installed fine but thats where the problems started to occur
random crashes of main apps system apps touch screen stops responding android.system crashes etc
step#6 try to flash back to prior TWRP backup
flashed back but same problems still occur
#step 7 flashed back to xtreme rom still same problems
#step 8 flashed to H811 10N stock Restore found herehttp://forum.xda-developers.com/tmobile-g4/development/rom-g4-h811-10n-stock-restore-t3191756
still same problems even though twrp and root are now gone because "clean install of stock rom"
did i **** up during the xposed install? how do i fix this
thanks a ton guys
-ben
armadilloben said:
hey guys hope all is well
so i may have somewhat softbricked my g4 dont really know how but i will explain what i did
hopefully someone can point out where i went wrong and how to fix it
Step #1
got root using this guide previously used the guide to get root on my ATT LGG4 worked fine
so got root, was successful everything worked fine
step #2
installed flashify
granted root access; all good
installed TWRP via flashify; all good
step #3 backup via TWRP all good
step #4 flashed G4H811 10N xTreme ROM v2.0 from this via TWRP; All good
step #5 attempt to install xposed framework 64bit from xposed respository via TWRP
supposedly installed fine but thats where the problems started to occur
random crashes of main apps system apps touch screen stops responding android.system crashes etc
step#6 try to flash back to prior TWRP backup
flashed back but same problems still occur
#step 7 flashed back to xtreme rom still same problems
#step 8 flashed to H811 10N stock Restore found herehttp://forum.xda-developers.com/tmobile-g4/development/rom-g4-h811-10n-stock-restore-t3191756
still same problems even though twrp and root are now gone because "clean install of stock rom"
did i **** up during the xposed install? how do i fix this
thanks a ton guys
-ben
Click to expand...
Click to collapse
Did you flash the bootstack for 10N?
I did NOT flash the bootstack for 10n because the guide said not to if you were already on 10n
I was on 10h, rooted with TWRP.
I then installed Exposed.
After a couple of days, I flashed 10N when it was made available by MicroMod777.
Even though everyone was running smoothly with 10N, I was having:
- touchscreen issues where one of every two touches weren't recognized.
- lag up the wazoo while scrolling, etc.
I was like, wow, this ain't good.
So I uninstalled Exposed, and I was still having the issues.
Then I was going to flash my 10h Nandroid, where I wasn't having zero issues.
But then I figured I'd let 10N settle in, so to speak.
After several hours without any further changes, 10N was running like clockwork without any issues. Smooth as butter.
I mention this as it may pertain to you.
You've made the many changes, so now just let things settle down and see how it goes.
I know that sometimes things just have to settle in. Why for some and not for others? I don't know.
It just is.
You got twrp to work on att?
Sent from my LG-H811 using Tapatalk
I really hope that the issues will disappear its more than the touchscreen is unresponsive every other touch its like not working at all then it will work randomly. Also the power button doesnt seem to open the power menu either.
So as i stand rn im back on the custom room rooted twrp but no xposed. Still the same problems but i have twrp installed which hopefullyis a good thing.
I hope it resolves itself after time but that most likely wont work
And no this is a tmobile g4 i moved over to tmo the other day. Im talking on my att g4 and trying to fix the tmo g4
armadilloben said:
I really hope that the issues will disappear its more than the touchscreen is unresponsive every other touch its like not working at all then it will work randomly. Also the power button doesnt seem to open the power menu either.
So as i stand rn im back on the custom room rooted twrp but no xposed. Still the same problems but i have twrp installed which hopefullyis a good thing.
I hope it resolves itself after time but that most likely wont work
And no this is a tmobile g4 i moved over to tmo the other day. Im talking on my att g4 and trying to fix the tmo g4
Click to expand...
Click to collapse
Do a kdz restore to 10N.
Sent from my LG-H811 using Tapatalk
---------- Post added at 09:51 PM ---------- Previous post was at 09:50 PM ----------
http://forum.xda-developers.com/showthread.php?t=3107848
Sent from my LG-H811 using Tapatalk
is there a guide to do that? i cant seem to find it on here at all
armadilloben said:
is there a guide to do that? i cant seem to find it on here at all
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3107848
Sent from my LG-H811 using Tapatalk
so i did the KDZ restore booted up the phone play services crashes the power or volume buttons still dont work and the touchscreen/general ui are still extremely unresponsive and system.ui crashes like crazy
wtf is causing this i thought the KDZ restore was like a full wipe?
Just thinking out loud.
Was this device possibly plugged into an outlet and received a power surge?
Or did moisture get to it somehow?
Or something similar to the above scenarios?
I'm thinking it may be a hardware issue affecting the software, as compared to strictly a software issue.
Or maybe things just have to settle in for up to 48 hours.