I'm on LMY47i on a sprint nexus 6.
Is there a way to downgrade the bootloader so I can flash xposed?
The boo loader isn't the issue, its 5.1 itself. The SDK changed along with some other things. Rovo is working on it.
The only way to run xposed is to use 5.0 or 5.01.
memekmek said:
I'm on LMY47i on a sprint nexus 6.
Is there a way to downgrade the bootloader so I can flash xposed?
Click to expand...
Click to collapse
Do not downgrade your bootloader from 5.1. If you do that, and then eventually try to upgrade to 5.1 again, you will brick your device.
Also xposed is not released for general consumption. It is an alpha test, for experienced users only. Please don't take this the wrong way (I mean no offense) but if you thought this issue is bootloader related, you're probably not experienced enough to be using such experimental software.
rootSU said:
Also xposed is not released for general consumption. It is an alpha test, for experienced users only. Please don't take this the wrong way (I mean no offense) but if you thought this issue is bootloader related, you're probably not experienced enough to be using such experimental software.
Click to expand...
Click to collapse
I appreciate it, i'm definitely not the most tech savvy but I try to read everything I can and learn. And I literally just got this phone last friday so I'm trying to catch up from the m8. From what I've been reading, I see that xposed isnt compatable with the latest OTA updates in 5.1. But I was also reading that you can't just flash a 5.0.2 rom and expect xposed to work because of the OTA update.
memekmek said:
I appreciate it, i'm definitely not the most tech savvy but I try to read everything I can and learn. And I literally just got this phone last friday so I'm trying to catch up from the m8. From what I've been reading, I see that xposed isnt compatable with the latest OTA updates in 5.1. But I was also reading that you can't just flash a 5.0.2 rom and expect xposed to work because of the OTA update.
Click to expand...
Click to collapse
You can flash any 5.0.2 AOSP ROM with your current bootloader and xposed will work. You cannot install an older factory image because that will overwrite (thus break) the bootloader.
Related
Ok, hope I don't get too much heat over this, my old device was a Samsung with unlocked bootloader, so everything was easily flashed.
Anyway, as to the best order of things, I'm still on AT&T 4.2.2 pre camera update, so I easily rooted with with pwnmymoto. I have Xposed installed with a few modules.
For the unlock steps -looks like this is the best guide: http://forum.xda-developers.com/showpost.php?p=51363645&postcount=394 and using: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-c
Q: Is my recovery from pwnmymoto "stock" as it needs to be for unlocking process?
Can I just uncheck/disable the modules I have with xposed, or do I need to delete the framework? (which sounds like the only way is to use RSD to install the original ROM?)
Should I also unfreeze any files? (I think I only froze the one's related to motorola OTA)
My intent is to get to 4.4.2, and I know it's optimal to remove things from pwnmymoto (I know unlocking will wipe everything but my ROM), so probably after I've installed TWRP and rooted, to flash the file for AT&T 4.4.2 http://forum.xda-developers.com/moto-x/general/-t2688009 or does it need to be incremental, as I'm on 4.2 (i.e flash 4.2 camera update, then 4.4, etc.) -sorry if I seem a bit confused
Thanks in advance! any and all help is very much appreciated!
Hopefully not too many questions -if any has the best suggestion for any, would be great
M973 said:
Hopefully not too many questions -if any has the best suggestion for any, would be great
Click to expand...
Click to collapse
Just to be clear if you eant 4.4.2 stock use the xposed framework disabler, it said leaving the modules was ok according to the link you posted. I don't know personally.
But honestly if your unlocking the bootloader then just go to 4.4.2 first then unlock since you'll lose everything. I believe bootloader unlock wipes the system parition too. I don't know for sure.
drago10029 said:
Just to be clear if you eant 4.4.2 stock use the xposed framework disabler, it said leaving the modules was ok according to the link you posted. I don't know personally.
But honestly if your unlocking the bootloader then just go to 4.4.2 first then unlock since you'll lose everything. I believe bootloader unlock wipes the system parition too. I don't know for sure.
Click to expand...
Click to collapse
I think 4.4.2 isn't fully released yet OTA for AT&T, so it would be flashing to stock and taking each OTA in sequence to 4.4 I think? I believe the framework disabler is a zip that needs to be flashed, so that would only be after I have a custom recovery.
I just don't want to mess up anything, want to make sure I have the right recovery for unlocking, and that I've disabled anything that could cause an issue.
Edit: from the pwnmymoto thread, Jcase writes: "In the process we remove stock recovery, so OTAs will not be a worry."
I guess that means i don't have stock recovery?
Edit: I was thinking I needed stock recovery, I guess I just need fastboot which is what I have?
I just want to make sure, if anyone has unlocked from pwnmymoto
Thanks
M973 said:
I think 4.4.2 isn't fully released yet OTA for AT&T, so it would be flashing to stock and taking each OTA in sequence to 4.4 I think? I believe the framework disabler is a zip that needs to be flashed, so that would only be after I have a custom recovery.
I just don't want to mess up anything, want to make sure I have the right recovery for unlocking, and that I've disabled anything that could cause an issue.
Edit: from the pwnmymoto thread, Jcase writes: "In the process we remove stock recovery, so OTAs will not be a worry."
I guess that means i don't have stock recovery?
Edit: I was thinking I needed stock recovery, I guess I just need fastboot which is what I have?
I just want to make sure, if anyone has unlocked from pwnmymoto
Thanks
Click to expand...
Click to collapse
np problem bro, happy rooting! may the flash be ever in your favor
I'd like to start this thread as a "what to not do to brick your device" discussion. I've noticed a lot of people bricking randomly with the 5.1 update and not a lot of people talking about what causes it. Is it random? Did you flash certain files from a certain ROM or Google? Did you mix 5.0.1 boot/radio with a 5.1 ROM? Can we find a solution to fix bricked devices?
Any insight here to help others avoid this problem will be appreciated!
read carefully and follow instructions, and all will be fine.
I bricked mine by flashing older CM 12 ZIP which flashed 5.0.1 bootloader over 5.1 one, so I think that's the cause - the bootloader doesn't like being downgraded. Might even be a "security feature", now that I think about it - because "fastboot flash bootloader" won't even let you flash older bootloader than you already have.
simms22 said:
read carefully and follow instructions, and all will be fine.
Click to expand...
Click to collapse
That's rather deceiving, don't you think?
Tasssadar said:
I bricked mine by flashing older CM 12 ZIP which flashed 5.0.1 bootloader over 5.1 one, so I think that's the cause - the bootloader doesn't like being downgraded. Might even be a "security feature", now that I think about it - because "fastboot flash bootloader" won't even let you flash older bootloader than you already have.
That's rather deceiving, don't you think?
Click to expand...
Click to collapse
whats deceiving? that somethings are messing things up in cm? what can i tell you, stay away from cm. i do. just because cm is messing things up? cm isnt android in general, its cm. they do things differently than aosp or stock android. i personally decided to stay as far away from cm years ago. anyways, i flashed 5.1, then reflashed 5.0.2, then flashed 5.1 again, all on the old bootloader, no issues. as long as you read about whats going on, and follow instructions properly, all will be alright.
adoublearonn said:
I'd like to start this thread as a "what to not do to brick your device" discussion. I've noticed a lot of people bricking randomly with the 5.1 update and not a lot of people talking about what causes it. Is it random? Did you flash certain files from a certain ROM or Google? Did you mix 5.0.1 boot/radio with a 5.1 ROM? Can we find a solution to fix bricked devices?
Any insight here to help others avoid this problem will be appreciated!
Click to expand...
Click to collapse
When you upgrade to 5.1 the OEM Unlock (under dev options) automatically gets switched off (due to new security which prevents stealing a device and just flashing it bypass the security code). Where people are running into trouble is they are upgrading to 5.1 and the latest radio having OEM Unlock unchecked and then flashing CM which includes the old radio and bootloader, at this point you are stuck. Can't flash a custom recovery because your bootloader is locked, can't unlock the bootloader because you have to boot into an os and check the OEM Unlock, and you can't do a system restore because you cannot access recovery.
Sent from my Nexus 6 using XDA Free mobile app
For me. I came from a 5.0.2 ROM. Flashed the newest radio and boot for 5.1 and flashed a 5.1 ROM. I DO SHOW an unchecked OEM unlock. So am I to assume if I wished to flash a 5.0.2 ROM to check OEM unlock? I don't think I will "downgrade"...but just curious. Thank you.
Sent from my Nexus 6 using XDA Free mobile app
I am currently on 5.1 but work for at&t. I just put my work email on my phone that also requires a monitoring service called mobile iron that monitors my phone. My company now thinks my phone i rooted because I have "prerelease" software on my phone and am in danger of getting in some pretty serious trouble. I talked it over with my manager and they're giving me time to fix it, but I need to get off 5.1 as fast as possible.
I can't root and I can't unlock bootloader but I need to get off 5.1.... can i just flash a 5.0.1 ota zip? Really not sure what to do but don't want my company phone taken from me. all my clients know this number.
Thanks in advance
pokedroid said:
I am currently on 5.1 but work for at&t. I just put my work email on my phone that also requires a monitoring service called mobile iron that monitors my phone. My company now thinks my phone i rooted because I have "prerelease" software on my phone and am in danger of getting in some pretty serious trouble. I talked it over with my manager and they're giving me time to fix it, but I need to get off 5.1 as fast as possible.
I can't root and I can't unlock bootloader but I need to get off 5.1.... can i just flash a 5.0.1 ota zip? Really not sure what to do but don't want my company phone taken from me. all my clients know this number.
Thanks in advance
Click to expand...
Click to collapse
I think the only way to downgrade the version is to flash through the bootloader or flash a custom rom but you can't do either, but 5.1 is officially out so its no longer pre release software.
You have to unlock the bootloader to flash anything. No you cannot flash an older ota (ota patch existing files to new versions, not replace entire files) and as mentioned l, 5.1 is not pre-release.
How did you get 5.1 in the first place?
ac3theone said:
I think the only way to downgrade the version is to flash through the bootloader or flash a custom rom but you can't do either, but 5.1 is officially out so its no longer pre release software.
Click to expand...
Click to collapse
At&t hasn't approved the software I guess, so by their standards it's considered prerelease. I honestly don't see why it's even an issue, we use the exact same images that gpe versions get so it shouldn't matter. Not sure what to do at this point.
rootSU said:
You have to unlock the bootloader to flash anything. No you cannot flash an older ota (ota patch existing files to new versions, not replace entire files) and as mentioned l, 5.1 is not pre-release.
How did you get 5.1 in the first place?
Click to expand...
Click to collapse
I just installed it as an update.zip using adb. No unlock required.
pokedroid said:
At&t hasn't approved the software I guess, so by their standards it's considered prerelease. I honestly don't see why it's even an issue, we use the exact same images that gpe versions get so it shouldn't matter. Not sure what to do at this point.
I just installed it as an update.zip using adb. No unlock required.
Click to expand...
Click to collapse
FYI, AT&T have no control over the update process. The update comes directly from Google, for all carriers. As long as you didn't install M or I, you're fine. There is nothing that AT&T could do to prevent anyone getting the update. Except maybe sending a memo out to a staff saying "you'll receive an update from Google. Please, please, please don't accept it"
pokedroid said:
At&t hasn't approved the software I guess, so by their standards it's considered prerelease. I honestly don't see why it's even an issue, we use the exact same images that gpe versions get so it shouldn't matter. Not sure what to do at this point.
I just installed it as an update.zip using adb. No unlock required.
Click to expand...
Click to collapse
Id say get a tmobile sim card and use that and that way they cant say your on lre release software since tmo just pushed the 5.1 update.
ac3theone said:
Id say get a tmobile sim card and use that and that way they cant say your on lre release software since tmo just pushed the 5.1 update.
Click to expand...
Click to collapse
Again, the carriers don't push the updates. They all come from google. Its not the same as other OEMs like Samsung
rootSU said:
Again, the carriers don't push the updates. They all come from google. Its not the same as other OEMs like Samsung
Click to expand...
Click to collapse
Can't you root and go back to 5.0 and relock bootloader and reinstall the mobile iron app?
ac3theone said:
Can't you root and go back to 5.0 and relock bootloader and reinstall the mobile iron app?
Click to expand...
Click to collapse
Doesn't need root. He could unlock the bootloader, willing the device and then flash the system.img and ROM.img for a 5.0 ROM. Then relock
But its pointless. 5.1 has been released to both versions on the nexus 6. The north American one and the international one. AT&T do not.control updates going to their "branded" nexus 6 device. They're coming from Google directly.
Edit..
Hmm maybe I'm wrong...
http://www.phonearena.com/news/Turn...akes-a-little-extra-effort--heres-how_id67599
Maybe like tmo, Google will be releasing a different 5.1 for at&t. This is disappointing news for nexus devices.
So yeah, unlock BL and flash system.img and boot.img from 5.0
rootSU said:
Doesn't need root. He could unlock the bootloader, willing the device and then flash the system.img and ROM.img for a 5.0 ROM. Then relock
But its pointless. 5.1 has been released to both versions on the nexus 6. The north American one and the international one. AT&T do not.control updates going to their "branded" nexus 6 device. They're coming from Google directly.
Edit..
Hmm maybe I'm wrong...
http://www.phonearena.com/news/Turn...akes-a-little-extra-effort--heres-how_id67599
Maybe like tmo, Google will be releasing a different 5.1 for at&t. This is disappointing news for nexus devices.
So yeah, unlock BL and flash system.img and boot.img from 5.0
Click to expand...
Click to collapse
Its not a different 5.1, but they delay the updates. As soon as the update is apppved it won't be considered "prerelease" and everything will be fine. It's a complete formality. But, it is what it is. I guess I'm going to just pull my email off my device and hope the "trackability" breaks. Not willing to risk boot loader unlock as I'll have to give the device back at some point. Again, as long as I don't put any "at-risk" firmware on the device and relock it shouldn't make any difference, but it does.
*sigh*
pokedroid said:
Its not a different 5.1, but they delay the updates. As soon as the update is apppved it won't be considered "prerelease" and everything will be fine. It's a complete formality. But, it is what it is. I guess I'm going to just pull my email off my device and hope the "trackability" breaks. Not willing to risk boot loader unlock as I'll have to give the device back at some point. Again, as long as I don't put any "at-risk" firmware on the device and relock it shouldn't make any difference, but it does.
*sigh*
Click to expand...
Click to collapse
You can unlock the bootloader and relock it (so long as you check it boots first). There isn't a flag or trip or anything that they will see.,
rootSU said:
You can unlock the bootloader and relock it (so long as you check it boots first). There isn't a flag or trip or anything that they will see.,
Click to expand...
Click to collapse
Oh, I was thinking the boot loader status would show "relocked" when in fastboot
Hey I really want to get a Droid Turbo and I'm aware it just recieved root. I was wondering if anyone knows if the phone will be able to update to Lollipop with root. I just dont want to buy the phone now, root it and then not be able to update to Lollipop. Thanks
You can just flash stock then take the OTA when it comes.
Harry44 said:
You can just flash stock then take the OTA when it comes.
Click to expand...
Click to collapse
but then will I still be able to root? I'd like to have root and Lollipop
billymaloney3 said:
but then will I still be able to root? I'd like to have root and Lollipop
Click to expand...
Click to collapse
We don't know that yet as lollipop isn't out yet. As long as moto doesn't patch the mofo system image flash method, we will still be able to cook up a lollipop image with root.
No one knows yet if you take the OTA for Lollipop when that day comes, root will stay or not, or be disabled, or stay enabled. We gotta stay on 4.4.4 until it's confirmed.
savagebunny said:
No one knows yet if you take the OTA for Lollipop when that day comes, root will stay or not, or be disabled, or stay enabled. We gotta stay on 4.4.4 until it's confirmed.
Click to expand...
Click to collapse
Theoretically, even if this method doesn't work for Lollipop, we should still be able to upgrade to Lollipop with root. Given the image files for the new update, we should be able to fastboot flash each individual partition and then mofo the a 5.1 rooted system image. We shouldn't have trouble flashing the correctly signed portions of the update that we need to allow us to maintain a fully matching system.
pjsockett said:
Theoretically, even if this method doesn't work for Lollipop, we should still be able to upgrade to Lollipop with root. Given the image files for the new update, we should be able to fastboot flash each individual partition and then mofo the a 5.1 rooted system image. We shouldn't have trouble flashing the correctly signed portions of the update that we need to allow us to maintain a fully matching system.
Click to expand...
Click to collapse
You cannot flash the kernel...
You cannot flash custom roms or any other android version because you CAN ONLY FLASH SYSTEM not kernel, not aboot, not bootloader, nothing. End of thread. 99% of this forums wouldnt exist if people just read and/or searched instead of starting a new thread for every thought they have.
When I first got the N6 in June I immediately unlocked the bootloader and flashed CyanogenMod 12. Now I remember reading beforehand that if you updated your device to 5.1 via the factory images or OTA, that the bootloader cannot be downgraded anymore. I made sure to not do this so my N6 is on the very first bootloader still and I haven't had any issues.
Now, I feel like I read that there was a reason to want to downgrade and a reason for not wanting this new bootloader but I can no longer find any information on this whole topic, other than people saying yo ucannot downgrade.
I'm asking if there are potentially issues if I do update or if it's ok to stay on my current old bootloader when I update to 6.0 soon?
admiralspeedy said:
When I first got the N6 in June I immediately unlocked the bootloader and flashed CyanogenMod 12. Now I remember reading beforehand that if you updated your device to 5.1 via the factory images or OTA, that the bootloader cannot be downgraded anymore. I made sure to not do this so my N6 is on the very first bootloader still and I haven't had any issues.
Now, I feel like I read that there was a reason to want to downgrade and a reason for not wanting this new bootloader but I can no longer find any information on this whole topic, other than people saying yo ucannot downgrade.
I'm asking if there are potentially issues if I do update or if it's ok to stay on my current old bootloader when I update to 6.0 soon?
Click to expand...
Click to collapse
You couldn't downgrade from a 5.1 bootloader to a 5.0 bootloader, because the 5.1 bootloader brought some new security features in. I don't know of any reason why you would want to downgrade the bootloader.
There is no reason to not upgrade it either, though as far as I am aware, 6.0 will work with a 5.1 BL, just don't think it will work with a 5.0 one.
I see, thank you!