[Q] First-time flasher (ha), what am I doing wrong? - Nexus 6 Q&A, Help & Troubleshooting

I finally decided to take advantage of having a Nexus 6 and flash a factory image. I downloaded Wug's NRT and commenced to flashing. I also wanted to disable forced encryption and Wug's NRT has an option to apply this during the flashing process. It appears to go through the process but when the phone boots back up, I'm still on the same build as when I started. What am I doing wrong?
Phone - Nexus 6, bought directly from Motorola
Carrier - Verizon
Toolkit - Wug's NRT 2.0.5
Build - LMY47D
Android version - 5.1
Goal - flash LMY47Z to get to 5.1.1 and no forced encryption
NRT says it can talk to my phone in all modes, has all the files it needs, etc. I've got to be missing something; just don't know what I'm doing wrong. Thanks in advance!

Lucky Armpit said:
I finally decided to take advantage of having a Nexus 6 and flash a factory image. I downloaded Wug's NRT and commenced to flashing. I also wanted to disable forced encryption and Wug's NRT has an option to apply this during the flashing process. It appears to go through the process but when the phone boots back up, I'm still on the same build as when I started. What am I doing wrong?
Phone - Nexus 6, bought directly from Motorola
Carrier - Verizon
Toolkit - Wug's NRT 2.0.5
Build - LMY47D
Android version - 5.1
Goal - flash LMY47Z to get to 5.1.1 and no forced encryption
NRT says it can talk to my phone in all modes, has all the files it needs, etc. I've got to be missing something; just don't know what I'm doing wrong. Thanks in advance!
Click to expand...
Click to collapse
what are you doing wrong? well thats an easy one, youre a first time flasher, what are you doing using a root toolkit? did you learn anything from it? did you learn how to flash the factory image the right way? no. that's your issue. it takes less than 5 minutes to flash a factory img the right way.
if you know how to do things properly, then its alright to use a toolkit. if you have no idea jow to do things right, a toolkit wont show you how.

Does NRT tell you it was successful? Usually there are quite a lot of messages...
To get a grip on what simms22's taking about, check out the faq thread:
http://forum.xda-developers.com/nexus-6/help/nexus-6-frequently-questions-t3106029

Didgeridoohan said:
Does NRT tell you it was successful? Usually there are quite a lot of messages...
To get a grip on what simms22's taking about, check out the faq thread:
http://forum.xda-developers.com/nexus-6/help/nexus-6-frequently-questions-t3106029
Click to expand...
Click to collapse
right, thats what i was trying to say

Thanks for the replies, guys. I was able to figure it out. I didn't have the bootloader unlocked. I know, noob mistake. I've got LMY47Z and no encryption now. Sure hope this fixes the jank I've been experiencing, which was the whole purpose of this little experiment.
But to answer your question, I used a tool because it automates the commands and makes the experience easier. Yes, I ran into trouble at first but I figured it out. In my defense, I did read that thread before posting that recommended issuing commands rather than using a tool. I was already vested in NRT so I figured I'd see it through.

Guess the joke is on me. Not only did my efforts NOT fix the lag and stutter I'm experiencing, but the internal storage was reported at 32GB rather than 64GB. So I ran through the tool again but this time I chose the "post-flash factory reset" option which wipes the user cache. The storage is now correct, I'm on LMY47Z, and no encryption. I only installed the Google apps and still had the lag.
This is a replacement device from Motorola (first one developed battery issues). I might do that again. At least I figured out what was wrong with the flashing process. Thanks again everyone!

Lucky Armpit said:
Guess the joke is on me. Not only did my efforts NOT fix the lag and stutter I'm experiencing, but the internal storage was reported at 32GB rather than 64GB. So I ran through the tool again but this time I chose the "post-flash factory reset" option which wipes the user cache. The storage is now correct, I'm on LMY47Z, and no encryption. I only installed the Google apps and still had the lag.
This is a replacement device from Motorola (first one developed battery issues). I might do that again. At least I figured out what was wrong with the flashing process. Thanks again everyone!
Click to expand...
Click to collapse
personally, the way that google sets up the cpu makes me unhappy. it does lag a bit at times. what i always do, and have done with every nexus, is unlock the bootloader, flash a custom recovery, and supersu. then when i boot up, i adjust the cpu my own way. only then does any remnant of lag disappear. i set up my cpu to have all cores online all the time(as of 5.1, google did this as well), i disable mpdecision(hate that google sh*t), and i use ondemand/dwadline

Lucky Armpit said:
Guess the joke is on me. Not only did my efforts NOT fix the lag and stutter I'm experiencing, but the internal storage was reported at 32GB rather than 64GB. So I ran through the tool again but this time I chose the "post-flash factory reset" option which wipes the user cache. The storage is now correct, I'm on LMY47Z, and no encryption. I only installed the Google apps and still had the lag.
This is a replacement device from Motorola (first one developed battery issues). I might do that again. At least I figured out what was wrong with the flashing process. Thanks again everyone!
Click to expand...
Click to collapse
To fix your storage issue, either factory reset or fastboot format userdata.

Evolution_Tech said:
To fix your storage issue, either factory reset or fastboot format userdata.
Click to expand...
Click to collapse
or just format the cache.

simms22 said:
personally, the way that google sets up the cpu makes me unhappy. it does lag a bit at times. what i always do, and have done with every nexus, is unlock the bootloader, flash a custom recovery, and supersu. then when i boot up, i adjust the cpu my own way. only then does any remnant of lag disappear. i set up my cpu to have all cores online all the time(as of 5.1, google did this as well), i disable mpdecision(hate that google sh*t), and i use ondemand/dwadline
Click to expand...
Click to collapse
Well, the joke's on me x 2, actually. There's all around UI lag (which isn't terrible, but it seems that it's worse than my original Nexus 6), with the biggest hesitation in the Messenger app. Reading the reviews of Messenger shows that I am not alone. That was definitely a smack-my-forehead moment as I didn't realize until then is that Messenger is the worst culprit. So I probably could have saved myself a lot of frustration, but it was a good exercise to go through. I know what to do (and what not to do) next time around.
You have some excellent suggestions, thank you very much! As far as the tuning you mentioned (cores, mpdecision), is that achieved with something like Kernel Tuner from the Play Store once I'm rooted?

Evolution_Tech said:
To fix your storage issue, either factory reset or fastboot format userdata.
Click to expand...
Click to collapse
simms22 said:
or just format the cache.
Click to expand...
Click to collapse
Sorry, didn't see this until after I replied. I formatted the userdata and that fixed the storage issues. I'm back to 64GB. Thanks!

Lucky Armpit said:
Well, the joke's on me x 2, actually. There's all around UI lag (which isn't terrible, but it seems that it's worse than my original Nexus 6), with the biggest hesitation in the Messenger app. Reading the reviews of Messenger shows that I am not alone. That was definitely a smack-my-forehead moment as I didn't realize until then is that Messenger is the worst culprit. So I probably could have saved myself a lot of frustration, but it was a good exercise to go through. I know what to do (and what not to do) next time around.
You have some excellent suggestions, thank you very much! As far as the tuning you mentioned (cores, mpdecision), is that achieved with something like Kernel Tuner from the Play Store once I'm rooted?
Click to expand...
Click to collapse
yea, any kernel/cpu control app should do. some have more features, some have less, but it would only matter if the kernel included those features. good luck

simms22 said:
yea, any kernel/cpu control app should do. some have more features, some have less, but it would only matter if the kernel included those features. good luck
Click to expand...
Click to collapse
Personally, I think the elementalX kernel tuner is the best. Trickster won't keep all of my settings stick after boot (like disabled mp-decision). When I had the elementalX app that worked great...that was a couple.months ago but when I wiped my phone the app wasn't available anymore lol I think the dev had to remove it from play. That was 4 bucks out the window and no working kernel tuner app... Haha

JNMM said:
Personally, I think the elementalX kernel tuner is the best. Trickster won't keep all of my settings stick after boot (like disabled mp-decision). When I had the elementalX app that worked great...that was a couple.months ago but when I wiped my phone the app wasn't available anymore lol I think the dev had to remove it from play. That was 4 bucks out the window and no working kernel tuner app... Haha
Click to expand...
Click to collapse
i still have the old elementalx app, and im still using it as my cpu control app :angel:

Related

[Q] Should I try Stock Andoroid before CM12?

My Nexus 6 has finally shipped! It should be here Friday!
This is my first Nexus and I have never rooted, unlocked, flashed, etc. any of my previous phones.
I have been doing a lot of research and have been considering running CM12.
My question is, should I run my Nexus 6 with stock android for a few weeks and then try CM12? Or should I just root, unlock, and flash CM12 as soon as I get it?
I know that if I wait then I will need to back up all my data because it will factory data reset but I am not worried about that... I understand it is easier to do it right out of the box because you don't have to worry about loosing anything but I can just back my info/apps up so that isn't a big deal.
Also, would you guys suggest something over CM12? Right now I am planning on using CM12 and just getting it setup how I like it then leaving it. I don't plan on always flashing and making changes but I might get sucked into it lol
Thanks everyone!
Has CM moved to 5. 1 yet?
What version android came your phone?
Depending on those two answers you have to ask yourself if you want to downgrade your phone. At least version wise
Sent from my Google N6 on VZ
DebianDog said:
Has CM moved to 5. 1 yet?
What version android came your phone?
Depending on those two answers you have to ask yourself if you want to downgrade your phone. At least version wise
Sent from my Google N6 on VZ
Click to expand...
Click to collapse
Good point! I don't know if CM is on 5.1 yet. I just assumed it was but I will look into it. This is all new to me so thanks for pointing that out, didn't even think about that!
I won't know what version is on the phone until Friday. But even if it is on 5.0 I am sure it will notify me that 5.1 is ready to download as soon as I boot up the phone.
On my other phones I usually got rid of the stock and was on a custom ROM a pretty quick. I have tried a few ROMs on this phone as well. in my experience if you want to be on 5 .1 currently the best way to go is stock with debloating . Or use one of the clean/vanilla ROMs. Of course I did not test them all there are so many out there. Good luck with your new toy.
I will try CM after its been out a few weeks on 5 .1
Sent from my Google N6 on VZ
I'd recommend updating to 5.1 if it doesn't ship with 5.1. Then, I'd run stock for at least a few days to get a baseline for comparison. I think this is useful especially for bugs. That way you can get an idea of the issues that exist in stock 5.1 before using a custom ROM.
DebianDog said:
On my other phones I usually got rid of the stock and was on a custom ROM a pretty quick. I have tried a few ROMs on this phone as well. in my experience if you want to be on 5 .1 currently the best way to go is stock with debloating . Or use one of the clean/vanilla ROMs. Of course I did not test them all there are so many out there. Good luck with your new toy.
I will try CM after its been out a few weeks on 5 .1
Sent from my Google N6 on VZ
Click to expand...
Click to collapse
Okay, thanks for the info!
Since I ordered my phone directly from Google, do I need to debloat? Or is that just for carrier versions?
mlin said:
I'd recommend updating to 5.1 if it doesn't ship with 5.1. Then, I'd run stock for at least a few days to get a baseline for comparison. I think this is useful especially for bugs. That way you can get an idea of the issues that exist in stock 5.1 before using a custom ROM.
Click to expand...
Click to collapse
Another great point! I knew you guys were the people to ask! lol
What about rooting and unlocking? Would you suggest waiting on that as well? Is there really any reason to unlock and root if I won't be running CM? I was going to root so that I could decrypte but it sounds like the lag from encryption is fixed in 5.1.
Well I would guess you WILL want to unlock and root because who does want to be able to run a root level ad blocker? Who wants to wait on OTA for an update? Not me.
I got mine from Google, as well, and heres what I did:
Played with the phone in stock form for like an hour saw it was still on 5.01 even after updating
Decided this is not for me. I wanted my root apps and I wanted to copy all the stuff off my old phone with Titanium backup to the Nexus
Looked on the interwebs for the easiest way to get root
Found a tool from my old buddy WugFresh (I knew him in the Droid X days)
Prepared myself for a giant PITA night. Download, drivers, and programs, reading various sites, etc, etc, etc
Was freaking SHOCKED that the tool did ALL THIS for me. I mean I literally plugged in my phone and it collected and set up everything. (It also has a console if you feel the need to type in adb commands)
Was unlocked, upgraded, rooted with a custom recovery with all my apps copied over in less than an hour
Sent Wuggy some $$$ and a thank-you note
You only need to decrypt, IMO, if you are running high end games that demand that level of performance. I have not seen any lag myself. Again this is my own personal experience. Your results may vary. 5.1 has optimized out many of the issues I heard about in 5.01 or so I have been told.
CFrance said:
Another great point! I knew you guys were the people to ask! lol
What about rooting and unlocking? Would you suggest waiting on that as well? Is there really any reason to unlock and root if I won't be running CM? I was going to root so that I could decrypte but it sounds like the lag from encryption is fixed in 5.1.
Click to expand...
Click to collapse
I unlocked and rooted right away, mainly for the ability to use Titanium Backup to setup my phone and in the event that I installed a custom ROM. Outside of TB, I haven't really needed or used root, but it sure is nice to have. I played with a few custom ROMs before 5.1 came out but mostly felt that I preferred the stock experience. I downloaded the MCR modpack found here: http://forum.xda-developers.com/showpost.php?p=58019266&postcount=1 but have yet to install it. If/when I do, root will become more of a requirement for my uses.
I came from a Verizon Note 4 which could not be rooted. I got used to not playing with my phone and just using the stock experience. Its nice that the stock experience on the N6 is so fantastic and stable. It makes it easy to just use the phone without worry of fixing, modding, and adding features, though I still enjoy those aspects too which is why I'll likely use MultiROM next time I decide to install something custom.
Dude are you somehow tied up with this Tool Kit? You`re promoting it on so many threads i`am starting to get the impression you`re not quite objective about it There is no harm in using toolkits by xperienced users and i`am sure its well build, but for newbies its very dangerous because they`re lost if something should go wrong.
gee2012 said:
Dude are you somehow tied up with this Tool Kit? You`re promoting it on so many threads i`am starting to get the impression you`re not quite objective about it There is no harm in using toolkits by xperienced users and i`am sure its well build, but for newbies its very dangerous because they`re lost if something should go wrong.
Click to expand...
Click to collapse
Which is exactly why I'm promoting it it is almost bulletproof. what's the alternative loading all the different tools and drivers they need and following some instructions found on the internet.
And as I explained in my post you can just download the tool to make sure you have all the drivers and connections. use it to get the proper files you need and then run the command line like a power user if you want to feel better about yourself.
Sent from my Google N6 on VZ
DebianDog said:
Which is exactly why I'm promoting it it is almost bulletproof. what's the alternative loading all the different tools and drivers they need and following some instructions found on the internet.
And as I explained in my post you can just download the tool to make sure you have all the drivers and connections. use it to get the proper files you need and then run the command line like a power user if you want to feel better about yourself.
Sent from my Google N6 on VZ
Click to expand...
Click to collapse
I will never use/promote a Toolkit even if it seems very good for the reason i posted earlier. Flashing manualy in fastboot doesn`t take more time and makes users more aware about their phone and knowledge of it and gives you control over whats happening Just my 2 cents.
My two cents. I don't think you've dealt with enough newbies. on another forum it was me and a group of others that would help people get their phones out of boot loops and soft bricks. I have literally helped hundreds of people get their phone back.
even if you look here on XDA you'll see people trying to flash the wrong files download files that are not even for their phone, are following a dated instruction or don't really understand how directories work.
Sent from my Google N6 on VZ
DebianDog said:
Well I would guess you WILL want to unlock and root because who does want to be able to run a root level ad blocker? Who wants to wait on OTA for an update? Not me.
I got mine from Google, as well, and heres what I did:
Played with the phone in stock form for like an hour saw it was still on 5.01 even after updating
Decided this is not for me. I wanted my root apps and I wanted to copy all the stuff off my old phone with Titanium backup to the Nexus
Looked on the interwebs for the easiest way to get root
Found a tool from my old buddy WugFresh (I knew him in the Droid X days)
Prepared myself for a giant PITA night. Download, drivers, and programs, reading various sites, etc, etc, etc
Was freaking SHOCKED that the tool did ALL THIS for me. I mean I literally plugged in my phone and it collected and set up everything. (It also has a console if you feel the need to type in adb commands)
Was unlocked, upgraded, rooted with a custom recovery with all my apps copied over in less than an hour
Sent Wuggy some $$$ and a thank-you note
You only need to decrypt, IMO, if you are running high end games that demand that level of performance. I have not seen any lag myself. Again this is my own personal experience. Your results may vary. 5.1 has optimized out many of the issues I heard about in 5.01 or so I have been told.
Click to expand...
Click to collapse
Thanks for the info! I actually had just downloaded this program over the weekend and was planning on using it once I do decide to root... which I am thinking will be as soon as I get the phone. lol other than that I think I am going to run it on stock for a while at first and wait until CM is on 5.1 for a while....
mlin said:
I unlocked and rooted right away, mainly for the ability to use Titanium Backup to setup my phone and in the event that I installed a custom ROM. Outside of TB, I haven't really needed or used root, but it sure is nice to have. I played with a few custom ROMs before 5.1 came out but mostly felt that I preferred the stock experience. I downloaded the MCR modpack found here: http://forum.xda-developers.com/showpost.php?p=58019266&postcount=1 but have yet to install it. If/when I do, root will become more of a requirement for my uses.
I came from a Verizon Note 4 which could not be rooted. I got used to not playing with my phone and just using the stock experience. Its nice that the stock experience on the N6 is so fantastic and stable. It makes it easy to just use the phone without worry of fixing, modding, and adding features, though I still enjoy those aspects too which is why I'll likely use MultiROM next time I decide to install something custom.
Click to expand...
Click to collapse
Thanks! I am planning on rooting and unlocking right away for TB and maybe a couple other little things like lightflow just for fun. Being the nerd that I am, I have a feeling that once I start playing with the whole rooting, unlocking, and flashing stuff I am going to really enjoy it.
gee2012 said:
I will never use/promote a Toolkit even if it seems very good for the reason i posted earlier. Flashing manualy in fastboot doesn`t take more time and makes users more aware about their phone and knowledge of it and gives you control over whats happening Just my 2 cents.
Click to expand...
Click to collapse
Thanks for the reply! I see what you are saying, I had already come across Wug's toolkit over the weekend and was planning on using that because it seemed so simple.
However, seeing how I still have two and a half days until my phone will be here, maybe I will look into the manual way a little more to decide which route I want to go.... Any suggestions on where to start? Threads, videos, etc?
Thanks!
Boot into download mode, Unlock bootloader, reboot, boot back into download mode, fastboot twrp recovery, boot into recovery, reboot via recovery and install su when prompted. When you boot into android you will be prompted to update su. You now are rooted. Only other thing I would think about when you first get your device is if you want forced encryption. You will be required to wipe SD data if you decide to go with non forced encryption.
I loved cm on my previous touchwiz devices because I like stock/asop style. I find cm has bugs in early os update releases. I would only install cm if i took advantage of themes which I don't.
CFrance said:
Any suggestions on where to start? Threads, videos, etc?
Thanks!
Click to expand...
Click to collapse
You can waste a lot of time while you're waiting for your phone in this thread http://forum.xda-developers.com/showthread.php?t=2992769
ROM Reviews (5.1) + Nexus 6 Hacking: NRT · Apps · Utilities [3.22.15]
Sent from my Google N6 on VZ

Nexus 6 Reboot/Optimize Apps after 5.X update

Hey there,
I got quite a serious problem. Since i updated to 5.1 my phone sometimes suddenly restarts, followed by a message which says "optimizing apps", which ranges from 30 to 150 apps. At first, it was no big problem, now it occures nearly every 10 minutes, so currently i can't really use my phone.
What i tried to do:
Factory reset, reflash 5.0 - 5.1.1 (every single image available)
The problem is still there.
Now my question, is it a Softwareproblem, which will be updated soon (should i try Android M (what about the warranty?))?
Or is it quite a serious hardwareproblem (i read somewhere that it could be because of overused RAM modules)?
I tried to use the searchengine, but i didnt find a specific thread in this subforum.
The optimising is a software issue caused by a random reboots. The reboot itself could be caused by anything though
danarama said:
The optimising is a software issue caused by a random reboots. The reboot itself could be caused by anything though
Click to expand...
Click to collapse
Thank you for your quick reply. I continued reading and as it seems there are quite a number of users with the same problems as me. Although no one has gotten a solution till now. It doesn't matter if it's a Nexus 4, 5 or 6 but all the Nexusphones seem to be affected once updated to 5.1 or newer.
Unluckily sending it in to repair is not a good solution because they told me it would take 2-4 weeks which is not possible for me... How can Google not release a proper update after 5.1.1 which fixes it? Are they so focused about Android M? I still can't overcome myself to install the Android M because i fear to lose my warranty.
Haabiii said:
Thank you for your quick reply. I continued reading and as it seems there are quite a number of users with the same problems as me. Although no one has gotten a solution till now. It doesn't matter if it's a Nexus 4, 5 or 6 but all the Nexusphones seem to be affected once updated to 5.1 or newer.
Unluckily sending it in to repair is not a good solution because they told me it would take 2-4 weeks which is not possible for me... How can Google not release a proper update after 5.1.1 which fixes it? Are they so focused about Android M? I still can't overcome myself to install the Android M because i fear to lose my warranty.
Click to expand...
Click to collapse
Dude, it's a Nexus. Warranty isn't an issue as long as you return to stock and relock before a warranty claim.
If flashing a factory image didn't fix it, either you're not wiping or formatting the cache correctly or you have a hardware issue.
Don't be so quick to blame Google when thousands of others, myself included, have taken the update without issue.
Evolution_Tech said:
Dude, it's a Nexus. Warranty isn't an issue as long as you return to stock and relock before a warranty claim.
Click to expand...
Click to collapse
Thanks, I didn't know that.
Evolution_Tech said:
If flashing a factory image didn't fix it, either you're not wiping or formatting the cache correctly or you have a hardware issue.
Click to expand...
Click to collapse
I did the factoryreset via fastboot, also i used the nexus toolkit to do a proper stock reset so i don't quite get how it could be an incorrectly done reset. So the hardware just breaks during the updateprocess?
Evolution_Tech said:
Don't be so quick to blame Google when thousands of others, myself included, have taken the update without issue.
Click to expand...
Click to collapse
I am usually quite quick in blaming others if there are also many people with excactly the same problem, sudden reboots with app optimization right after the update to 5.1 or 5.1.1, some even before at 5.0 or 5.0.1.
I'm going to try the Android M Update, maybe that will help.
Haabiii said:
Thanks, I didn't know that.
I did the factoryreset via fastboot, also i used the nexus toolkit to do a proper stock reset so i don't quite get how it could be an incorrectly done reset. So the hardware just breaks during the updateprocess?
I am usually quite quick in blaming others if there are also many people with excactly the same problem, sudden reboots with app optimization right after the update to 5.1 or 5.1.1, some even before at 5.0 or 5.0.1.
I'm going to try the Android M Update, maybe that will help.
Click to expand...
Click to collapse
Personally, I'd boot to bootloader and do:
fastboot format cache
Evolution_Tech said:
Personally, I'd boot to bootloader and do:
fastboot format cache
Click to expand...
Click to collapse
Already done and i also reflashed the whole cache image. I hope the Android 6 Update will help solve my issues. The problem is, that i usually get really upset about little stuff like that just because i don't get why it's happening.
I updated monday evening to the Android M Preview, for now it only restarted once to, as it said, install a update (?), since then no reboot at all. It worked like a charm yesterday. I really hope the problem is fixed that way.
Just wanted to let you know if you have a same problem.

Dead Turbo?

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.[/QUO​TE]
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.[/QUO​TE]
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.

Android Pay Unable To Verify; Stock 6.0, Nonrooted, Bootloader Locked

So I loaded up TWRP and Despair Kernel yesterday and rooted my N6 yesterday. There's not much going on yet as far as I understand because Xposed still isn't ready for Marshmallow and the new OS has a lot of great features I don't feel like I really need root, unless for adblocking. Anyways, so I refreshed back to stock through Fastboot, however now Android Pay states it cannot verify the system as if I was still rooted, which I am not. Has anyone experienced this?
Is it possible that the system partition is still R/W? I looked for a way to wipe the device completely and start back up from scratch, meaning erasing partitions, recreating them, etc. but could not find any information on it. Any help would be great as I have a horrible memory and constantly forget my wallet, so Android pay would do a great deal of good as far as I am concerned. Thanks guys.
Nooblet said:
So I loaded up TWRP and Despair Kernel yesterday and rooted my N6 yesterday. There's not much going on yet as far as I understand because Xposed still isn't ready for Marshmallow and the new OS has a lot of great features I don't feel like I really need root, unless for adblocking. Anyways, so I refreshed back to stock through Fastboot, however now Android Pay states it cannot verify the system as if I was still rooted, which I am not. Has anyone experienced this?
Is it possible that the system partition is still R/W? I looked for a way to wipe the device completely and start back up from scratch, meaning erasing partitions, recreating them, etc. but could not find any information on it. Any help would be great as I have a horrible memory and constantly forget my wallet, so Android pay would do a great deal of good as far as I am concerned. Thanks guys.
Click to expand...
Click to collapse
fastboot a factory image, thats the only way.
simms22 said:
fastboot a factory image, thats the only way.
Click to expand...
Click to collapse
Already have done that, still not working. After looking at reviews it seems to be an on going problem.
Sent from my Nexus 6 using Tapatalk

About to wipe and 're-build' N6. Couple of Q.

Couple of quick (probably stupid) questions about wiping and rebuilding the phone:
I haven't done a "flash-all.bat" in quite a few iterations of Android updates. I keep hearing from different people how smooth and how fast and bug free their phone is after doing a "Flash-all.bat" on it.
Is this true or do you all think it's just a placebo effect?
I've already done a Titanium Backup of my apps. Do you all recommend doing it that way or, re-installing the apps and re-set everything up from the Play Store all over again?
I've backed up my "userdata" folder to my PC. Is there a way, after wiping the phone to completely erase the SD card and/or check for errors? Or, not necessary?
I've seen some discussion that people are no longer using Chainfire's SU any more and have moved on to something else (the other SU name escapes me at the moment)?
An unlocked Bootloader now trips SafetyNet? So there is no real reason to try and install "SUHide" and the like in order to get Android Pay working? I've not messed around
with trying to bypass the SafetyNet and just resigned myself to never being able to use A.P. Should I even mess with all of that?
Anything else you all might recommend on a "restart" of a device, I'd be eager to hear!
Thanks all!
1. FlashAll is way too drastic. It deletes every single file you had on your emmc. Doing factory reset from TWRP only deletes the apps and settings and leaves all your photos, documents, downloads, etc.
2. I let Google install my apps after a new setup and then let TB restore the data for those that Google couldn't. Since MM even Google manages to restore some data too.
3. Unless you want to sell it, there's no need to wipe it completely.
4. PHH's superuser is completely open source and more and more people use it.
5. Yep, you need a custom kernel for SafetyNet if your bootloader is open. There is one already for 7.0 too
Sent from my Nexus 6P running Nougat DP 7.1 using Tapatalk
istperson said:
1. FlashAll is way too drastic. It deletes every single file you had on your emmc. Doing factory reset from TWRP only deletes the apps and settings and leaves all your photos, documents, downloads, etc.
2. I let Google install my apps after a new setup and then let TB restore the data for those that Google couldn't. Since MM even Google manages to restore some data too.
3. Unless you want to sell it, there's no need to wipe it completely.
4. PHH's superuser is completely open source and more and more people use it.
5. Yep, you need a custom kernel for SafetyNet if your bootloader is open. There is one already for 7.0 too
Sent from my Nexus 6P running Nougat DP 7.1 using Tapatalk
Click to expand...
Click to collapse
1) Ok, so I will just do a "factory reset" in TWRP then.
2) I will have to take a look at the TB Backup, I've only done "Backup all user apps". I'll check if there is just a setting for "Data for user apps" then.
3) Ok. Point taken. Just thought wiping the internal storage might get rid of any "ghosts in the system" so to speak.
4) Thank you for refreshing my memory. Forgot the name of the other SU.
5) I'll check to see if Franco Kernel has that, or plans on implementing it. I've been using F.K. forever so hopefully he will get around to releasing one.
** Unrelated note: Your 6p, in hindsight, was it worth the upgrade from the 6? Since the new Pixels are out, I'm assuming the 6P are going to start dropping in price at this point **
Thanks again for the suggestions / help
usafle said:
** Unrelated note: Your 6p, in hindsight, was it worth the upgrade from the 6? Since the new Pixels are out, I'm assuming the 6P are going to start dropping in price at this point **
Thanks again for the suggestions / help
Click to expand...
Click to collapse
This was indeed worth it, it was a store display model activated for a couple of months, I got it for half price.
But I needed a daily device while I develop Nougat for my N6. Then switch them and develop it for the 6P.
But as a device I'm very pleased with it, it's faster, the camera is better, and the 7.1 DP is already better than the official 7.0.
Sent from my Nexus 6P running Nougat DP 7.1 using Tapatalk

Categories

Resources