What's new
DroidForums.net | Android Forum & News

This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

MattyP's .215 Leak Classroom

It will not revert to anything prior to x.215. The purpose of a hard reset (factory reset) is to wipe any user data, settings, and other changes to the phone. It put's the phone in an out-of-the-box state. On most Android devices it does not wipe network provisioning which is a good thing. But it will not revert you to any previous software version or settings of a previous version...It simply reverts you back to x.215 with none of your user data/settings.

That being said, if it ain't broke, don't fix it.If you are having no problem whatsoever, then you should probably leave well enough alone.

Trust me, I have 2 posts. lol :D

Matty, Josh, Aintmy guys| Is this true:
Maybe we should note the indicator that Motorolla has now? Once you root, they will know. A lot of people may not know you can't just reflash a stock image if you need to send it back.
 
helron said:
Matty, Josh, Aintmy guys| Is this true:

It is true. When you boot into stock recovery, next to the android there is an indicator it will read qe0/0 for unrooted, qe1/1 for rooted and qe 0/1 for once was rooted but it's no longer. I have confirmed this myself. Let me note that updating to .215 will not change this without rooting

Sent from my XT912 running Scalpel CM10 jelly bean
 
Which file should I use to flash back to .211 file? I am wanting to go back to .211 in case a new OTA update comes available. I am running the .215 leak right now.
 
Redsnk95 said:
Which file should I use to flash back to .211 file? I am wanting to go back to .211 in case a new OTA update comes available. I am running the .215 leak right now.

Option 1 on Matt's utility

Sent from my XT912 running Scalpel CM10 jelly bean
 
I just got a new tablet, it came with ICS on it. Updated it to Jelly Bean immediately out of the box. You can actually download a "unlocker tool" from the ASUS website to unlock the bootloader on it. You also have to agree to the terms of service which states it voids your warranty by unlocking it, and bla bla bla ... so I did it, and rooted it less than an hour out of the box. I paid for it, I really don't care if they know I rooted it. Same with my phone. It's mine, I'll do what I want with it. :D
 
It is true. When you boot into stock recovery, next to the android there is an indicator it will read qe0/0 for unrooted, qe1/1 for rooted and qe 0/1 for once was rooted but it's no longer. I have confirmed this myself. Let me note that updating to .215 will not change this without rooting

Sent from my XT912 running Scalpel CM10 jelly bean

Now I am totally confused. I'm a great investigator and always look for WHAT IFs, but golly! I just don't understand the last sentence of Josh post: longer. "I have confirmed this myself. Let me note that updating to .215 will not change this without rooting" So is rooting and returning to stock ok as far as Moto return or upgrade is concerned. Thx.
 
helron said:
Now I am totally confused. I'm a great investigator and always look for WHAT IFs, but golly! I just don't understand the last sentence of Josh post: longer. "I have confirmed this myself. Let me note that updating to .215 will not change this without rooting" So is rooting and returning to stock ok as far as Moto return or upgrade is concerned. Thx.

I'm sorry, what I'm trying to say is updating to .215 is not rooting. Neither is fastbooting back to stock. I can't confirm that fastbooting will not change the "qe" status since I had rooted before I ever fastbooted back, but I don't believe it does. What I can confirm is that updating doesn't change it.

Sent from my XT912 running Scalpel CM10 jelly bean
 
I'm sorry, what I'm trying to say is updating to .215 is not rooting. Neither is fastbooting back to stock. I can't confirm that fastbooting will not change the "qe" status since I had rooted before I ever fastbooted back, but I don't believe it does. What I can confirm is that updating doesn't change it.

Sent from my XT912 running Scalpel CM10 jelly bean

Josh thank you. I understand that updating to .215 is not routing, and niw Iuderstand that fastboiting back to stock ismnit routing. I'm fuzzy with the following scenario: let's assume I root my phone and it is running 215. A month later motorolan OTA release of JELLYBEAN.
1. Am I correct to assume that I will have to fastboot back to stock via Mattys 181 Utility?
2. Will I be able to do so?
3. Will Moto somehow block something causing me to screw up the up phone, cause I rooted it.
This is getting kind of deep, so I am concerned and trust your opinion.
 
helron said:
Josh thank you. I understand that updating to .215 is not routing, and niw Iuderstand that fastboiting back to stock ismnit routing. I'm fuzzy with the following scenario: let's assume I root my phone and it is running 215. A month later motorolan OTA release of JELLYBEAN.
1. Am I correct to assume that I will have to fastboot back to stock via Mattys 181 Utility?
2. Will I be able to do so?
3. Will Moto somehow block something causing me to screw up the up phone, cause I rooted it.
This is getting kind of deep, so I am concerned and trust your opinion.

No one knows for sure if you will have to fastboot back to receive future updates. We won't know until that day comes. Rooting will not stop you from receiving ota updates. You can temporarily unroot with voodoo, or if you have to fasboot back that will unroot you. Rooting will however void your warranty.

Sent from my XT912 running Scalpel CM10 jelly bean
 
Being rooted does not typically cause issues with any updates. Custom recoveries on the other hand do cause issues with stock updates, and often you can not OTA-update with a custom recovery.. Luckily, there is always a way to go back to stock everything. The most common issue for root users when updating is that it often patches a root exploit and you need to root again. Sometimes a new root method is not available right away, but as I understand motos are not usually a problem. For HTC and other devices, there is often some delay. Usually a root user will wait for a rooted stock rom to be released in order to manually update if they want to be stock-rooted.

All of that being said, as stated above there is no telling if the leaked x.214/x.215 will be able to update, or if you will have to go back to x.211 to update.

I have worked in wireless for more than six years. Motorola is one of the best manufacturers when it comes to standing behind their equipment. Even if you have rooted a device, I could not see moto charging you to fix any hardware issue that might arise. The point of voiding the warranty is to save moto from millions of devices coming in each year for issues caused by users rooting and "bricking" their own devices. This happens more often than you can imagine and would add a huge repair/replacement overhead for moto and the carriers that sell their devices.

The sad truth is that most people that "customize" their phones have no idea what they are doing. I mean that in a literal sense. They do not understand what is actually happening on the device as they follow a guide in some forum post that tells them to run a software utility, replace this, and modify that. And more often than not, they don't read the entire post, instructions, or even follow them in order.
 
Last edited:
Help! All was fine, then battery started dying.

I did the .215 update a few weeks ago and my phone was great. I also callibrated the battery. But last week everything changed. Instead of ending the day with 65 or 70 percent of my battery left, after 7 hours I'm down to 25 percent. Nothing on my phone changed, and have no idea why this is happening. The phone is also getting really hot. I don't see any apps misbehaving & eating power. I did a factory data reset last weekend, and it did not improve things at all. I talked to Verizon and they are willing to replace my phone, but I'm not sure that will fix things. If anybody has any good suggestions of what to try, please let me know.
 
Check to see that it is not set too global data... settings --->more... (under data usage) ---> mobile networks ---> network mode ---> select LTE/CDMA.
 
Back
Top