It is the information I get below:
Baseband version:
MSM8960PRO_BP_2323.011.75.00R
Kernel Version:
3.4.4.2-xline-gfd1a699-00157-gfb2f8fc [email protected] #1 Thu Jul 18 22:37:58 CDT 2013
System Version:
139.7.26.ghost_row.AmericaMovil.en.PR
Build number:
13.9.0q2.x-116-LCX-26
Is it actually the same as the AT&T one? But I try to install motoroot and it can't be installed.
Please help!
Unlock here:
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Flash recovery, upon rebooting from recovery it will ask if you want to root.
mentose457 said:
Unlock here:
Flash recovery, upon rebooting from recovery it will ask if you want to root.
Click to expand...
Click to collapse
Is it possible to use PWNmymoto or Motoroot to do the root stuff?
And is it possible to flash t-mobile version on it?
I would do a search in the pwnmymoto root thread about routing it that way.
Sent from my Moto X.
There is no need in using pwnmymoto, especially because there is no pwnmymoto for PR phones - definitely the unlock bootloader thing from motorola is more stable. After it's unlocked, flashing the recovery is very easy. Having a PR phone myself, I can confirm CWM Recovery working and SuperSU root as well after the official bootloader unlock.
rchik said:
There is no need in using pwnmymoto, especially because there is no pwnmymoto for PR phones - definitely the unlock bootloader thing from motorola is more stable. After it's unlocked, flashing the recovery is very easy. Having a PR phone myself, I can confirm CWM Recovery working and SuperSU root as well after the official bootloader unlock.
Click to expand...
Click to collapse
Thank you very much. Have you tried to flash AT&T's rom on it? It seems like the same.
What if I want to do the update/flash stock image after unlocked? Is there any source for PR phone?
chrisjenho said:
Thank you very much. Have you tried to flash AT&T's rom on it? It seems like the same.
What if I want to do the update/flash stock image after unlocked? Is there any source for PR phone?
Click to expand...
Click to collapse
You should be able to flash the AT&T ROM without any problems, I have flashed mine with the T-Mobile ROM.
If you want to go back to the AmericaMovil.PR stock ROM, u can find it here:
http://sbf.droid-developers.org/ghost_rcica/list.php
mschumacher69 said:
You should be able to flash the AT&T ROM without any problems, I have flashed mine with the T-Mobile ROM.
If you want to go back to the AmericaMovil.PR stock ROM, u can find it here:
http://sbf.droid-developers.org/ghost_rcica/list.php
Click to expand...
Click to collapse
PR rom is pre-camera OTA. You can not flash back to that if you flashed any post-camera OTA roms as the bootloader can not be downgraded.
yghrv said:
PR rom is pre-camera OTA. You can not flash back to that if you flashed any post-camera OTA roms as the bootloader can not be downgraded.
Click to expand...
Click to collapse
Afaik, if u've unlocked ur bootloader, you can flash whatever u want including downgrading...
People have also managed to downgrade from 4.4 to 4.2.2 on locked bootloader phones...
mschumacher69 said:
Afaik, if u've unlocked ur bootloader, you can flash whatever u want including downgrading...
People have also managed to downgrade from 4.4 to 4.2.2 on locked bootloader phones...
Click to expand...
Click to collapse
You should be noted that they downgrade from 4.4 to 4.2.2 post-camera OTA roms as they have the same bootloader. Try downgrade to pre-camera OTA rom may cause the phone bricked. Have seen several threads talking about this.
yghrv said:
You should be noted that they downgrade from 4.4 to 4.2.2 post-camera OTA roms as they have the same bootloader. Try downgrade to pre-camera OTA rom may cause the phone bricked. Have seen several threads talking about this.
Click to expand...
Click to collapse
Again, this is if your bootloader is locked.
If you have an unlocked bootloader, you should be able to flash any ROM including downgrading to pre-camera OTA ROM.
mschumacher69 said:
Again, this is if your bootloader is locked.
If you have an unlocked bootloader, you should be able to flash any ROM including downgrading to pre-camera OTA ROM.
Click to expand...
Click to collapse
yes I'm talking about unlocked bootloader. not continue to the debate, u can try it out but I it's my opinion that u might brick the phone.
yghrv said:
yes I'm talking about unlocked bootloader. not continue to the debate, u can try it out but I it's my opinion that u might brick the phone.
Click to expand...
Click to collapse
I don't think so. What's the point in unlocking your bootloader if u can't downgrade??
mschumacher69 said:
I don't think so. What's the point in unlocking your bootloader if u can't downgrade??
Click to expand...
Click to collapse
check this out
http://forum.xda-developers.com/showthread.php?t=2548867
I've seen several guys bricked the phone as they tried to downgrade to pre camera OTA 4.2.2 from 4.4.
of coz with unlocked bootloader.
yghrv said:
check this out
http://forum.xda-developers.com/showthread.php?t=2548867
I've seen several guys bricked the phone as they tried to downgrade to pre camera OTA 4.2.2 from 4.4.
of coz with unlocked bootloader.
Click to expand...
Click to collapse
This guy didn't brick because he downgraded back to pre camera OTA, he successfully downgraded back to pre-camera OTA but he bricked after installing the OTA.
Why? Because he did all sorts of things to his phone before installing the OTA including installing custom recovery, rooting, installing a custom logo and all sorts of other things and he didn't even flash the full stock ROM before taking the OTA.
We all know that you shouldn't take an OTA unless you go back to 100% stock first
mschumacher69 said:
This guy didn't brick because he downgraded back to pre camera OTA, he successfully downgraded back to pre-camera OTA but he bricked after installing the OTA.
Why? Because he did all sorts of things to his phone before installing the OTA including installing custom recovery, rooting, installing a custom logo and all sorts of other things and he didn't even flash the full stock ROM before taking the OTA.
We all know that you shouldn't take an OTA unless you go back to 100% stock first
Click to expand...
Click to collapse
You can see from the thread. The old bootloader can not be flashed and he skipped that step. I think this is actually why get bricked after trying to OTA.
Erased from XML files the following lines BECAUSE RSD LITE SHOWED ERROR ACCORDING TO THIS LINES:
“step operation=”getvar” var=”max-download-size”
<step operation="flash" partition="partition" filename="gpt.bin" MD5="A_LOT_OF_NUMBERS_HERE" />
<step operation="flash" partition="motoboot" filename="motoboot.img" MD5="A_LOT_OF_NUMBERS_HERE" />
yghrv said:
You can see from the thread. The old bootloader can not be flashed and he skipped that step. I think this is actually why get bricked after trying to OTA.
Erased from XML files the following lines BECAUSE RSD LITE SHOWED ERROR ACCORDING TO THIS LINES:
“step operation=”getvar” var=”max-download-size”
<step operation="flash" partition="partition" filename="gpt.bin" MD5="A_LOT_OF_NUMBERS_HERE" />
<step operation="flash" partition="motoboot" filename="motoboot.img" MD5="A_LOT_OF_NUMBERS_HERE" />
Click to expand...
Click to collapse
Probably, as I said, you should never take an OTA if u're not 100% stock.
yghrv said:
You should be noted that they downgrade from 4.4 to 4.2.2 post-camera OTA roms as they have the same bootloader. Try downgrade to pre-camera OTA rom may cause the phone bricked. Have seen several threads talking about this.
Click to expand...
Click to collapse
Yes you are correct, you can not downgrade to the per camera firmware, regardless if you are running a unlocked boot loader, gpt.bin failure , I tried and failed and under no circumstance remove the gpt. bin line in the XML file as you will hard brick your device 100% guaranteed
Sent from my A2109A using Tapatalk 4
flashallthetime said:
Yes you are correct, you can not downgrade to the per camera firmware, regardless if you are running a unlocked boot loader, gpt.bin failure , I tried and failed and under no circumstance remove the gpt. bin line in the XML file as you will hard brick your device 100% guaranteed
Sent from my A2109A using Tapatalk 4
Click to expand...
Click to collapse
Yes. That's what I'm talking about. Bootloader downgrade not supported for this model, even unlocked bootloader. @mschumacher69
I think for latin America XT1058s, can be flashed to stock with ATT or Rogers post camera OTA 4.2.2 sbf from 4.4 instead using the original one which are most pre camera OTA.
flashallthetime said:
Yes you are correct, you can not downgrade to the per camera firmware, regardless if you are running a unlocked boot loader, gpt.bin failure , I tried and failed and under no circumstance remove the gpt. bin line in the XML file as you will hard brick your device 100% guaranteed
Click to expand...
Click to collapse
So that's why he bricked, because he didn't flash gpt.bin not because he attempted to downgrade to pre-ota 4.2.2. Attempting to flash the pre-ota 4.2.2 might fail, but it will not brick, correct?
Related
I noticed on an unlocked bootloader, I can't downgrade the bootloader or gpt.bin (these are the only ones i checked once i read in another post about this). Can anyone explain why or how to do this? What is gpt.bin???
Kind of related - if the AT&T and Verizon locked BL 4.4 versions can downgrade, why can't I with an unlocked BL? It makes me feel cheated.. unless I'm not understanding something correctly...
mohlsen8 said:
I noticed on an unlocked bootloader, I can't downgrade the bootloader or gpt.bin (these are the only ones i checked once i read in another post about this). Can anyone explain why or how to do this? What is gpt.bin???
Kind of related - if the AT&T and Verizon locked BL 4.4 versions can downgrade, why can't I with an unlocked BL? It makes me feel cheated.. unless I'm not understanding something correctly...
Click to expand...
Click to collapse
actually, after playing with it for a while now, i was able to downgrade from 4.4 to 4.2 (camera update) using RSD Lite and the leaked firmware. using fastboot commands themselves doesn't work. it's weird.
i'd still love to know why we can't downgrade the bootloader and some other files on unlocked dev editions.
mohlsen8 said:
actually, after playing with it for a while now, i was able to downgrade from 4.4 to 4.2 (camera update) using RSD Lite and the leaked firmware. using fastboot commands themselves doesn't work. it's weird.
i'd still love to know why we can't downgrade the bootloader and some other files on unlocked dev editions.
Click to expand...
Click to collapse
you can. end of story. don't know what you read or what you are personally doing wrong that isn't allowing you to downgrade your device. but you most definitely can do this. there is nothing that you can't do with an unlocked bootloader.
jayboyyyy said:
you can. end of story. don't know what you read or what you are personally doing wrong that isn't allowing you to downgrade your device. but you most definitely can do this. there is nothing that you can't do with an unlocked bootloader.
Click to expand...
Click to collapse
This is absolutely correct!
jayboyyyy said:
you can. end of story. don't know what you read or what you are personally doing wrong that isn't allowing you to downgrade your device. but you most definitely can do this. there is nothing that you can't do with an unlocked bootloader.
Click to expand...
Click to collapse
there's a couple places i've seen this. and my bootloader is unlocked, and i can't downgrade, for instance, to the bootloader from the original t-mobile software (4.2.2 pre-camera) - this file, just to clarify (from sbf droid developers): TMO_XT1053_4.2.2-13.9.0Q2.X-116-X-17-6_CFC.xml.zip. i take the motoboot.img out and use "fastboot flash motoboot motoboot.img". i get:
(bootloader) Preflash validation failed
phone display says:
Failed to hab check for tz: 0x4e
?
while we're discussing, motorola says these can be relocked. in all of my screwing around this morning i was trying this too. i followed all directions and still cannot lock the phone. i use "fastboot oem lock" and it tells me:
(bootloader) FAIL: Please run fastboot oem lock begin first!
ok, so i use "fastboot oem lock begin". now it gives me:
(bootloader) Ready to flash signed images
ok, try "fastboot oem lock" again and then it gives me:
(bootloader) Re-Lock Failure. See Display
display says "No valid PIV block in SP for system piv validation failed (system) Re-lock failure".
i've tried many times to flash all stock files back to the phone using fastboot, as well as RDS Lite, and it's been successful each time, but it won't re-lock. i've also tried "fastboot oem lock begin" then flashing all the stock files, then "fastboot oem lock". still, no dice. what's up with this?
The updated bootloader isn't let you flash older files. If you flash a full package it will downgrade the bootloader first and then you can flash the other older files. If you use a program such as rsdlite it will handle it all for you.
Steve-x said:
The updated bootloader isn't let you flash older files. If you flash a full package it will downgrade the bootloader first and then you can flash the other older files. If you use a program such as rsdlite it will handle it all for you.
Click to expand...
Click to collapse
so if i flashed the entire 4.2.2 pre-camera file through RSD Lite, it would downgrade the bootloader as part of that? why am i not allowed to do this in fastboot manually?
mohlsen8 said:
so if i flashed the entire 4.2.2 pre-camera file through RSD Lite, it would downgrade the bootloader as part of that? why am i not allowed to do this in fastboot manually?
Click to expand...
Click to collapse
Yes, it would downgrade the bootloader.
You can do it with fastboot manually but you need to do it in the proper sequence is all.
Steve-x said:
Yes, it would downgrade the bootloader.
You can do it with fastboot manually but you need to do it in the proper sequence is all.
Click to expand...
Click to collapse
really? i had no idea that sequence mattered. why would that matter if i have an unlocked bootloader and want to flash an older one onto the device?
i just tried running the 4.2.2 pre-camera file through rsd lite (after removing the getvar line as usual) and it fails on 2/16 (flashing gpt.bin). screen says "downgraded security version. update gpt_main version failed. preflash validation failed for GPT".
i don't understand why it won't work for me and i really would love to understand all of this.
mohlsen8 said:
really? i had no idea that sequence mattered.
i just tried running the 4.2.2 pre-camera file through rsd lite (after removing the getvar line as usual) and it fails on 2/16 (flashing gpt.bin). screen says "downgraded security version. update gpt_main version failed. preflash validation failed for GPT".
i don't understand why it won't work for me and i really would love to understand all of this.
Click to expand...
Click to collapse
to me happens the same, shouls we first downgrade bootloader and recovery before using GPT, maybe our version of RSD lite is not the same?
beelzebu said:
to me happens the same, shouls we first downgrade bootloader and recovery before using GPT, maybe our version of RSD lite is not the same?
Click to expand...
Click to collapse
i have 6.14. going to install 6.15 now and try.
edit: 6.15 does the same thing. won't flash 4.2.2 pre-camera through RSD Lite because of the downgraded security error on GPT.bin.
mohlsen8 said:
i have 6.14. going to install 6.15 now and try.
edit: 6.15 does the same thing. won't flash 4.2.2 pre-camera through RSD Lite because of the downgraded security error on GPT.bin.
Click to expand...
Click to collapse
Had the same issue with downgrading from the camera ota to the pre camera sbf file, rsdlite wouldn't flash got.bin failed, I think it possibly the ota that prevents downgrading, but if you flash from one sbf file and downgrade you're OK, I haven't tried it, just a thought
Sent on my Moto X
flashallthetime said:
Had the same issue with downgrading from the camera ota to the pre camera sbf file, rsdlite wouldn't flash got.bin failed, I think it possibly the ota that prevents downgrading, but if you flash from one sbf file and downgrade you're OK, I haven't tried it, just a thought
Sent on my Moto X
Click to expand...
Click to collapse
Are you saying you were able to flash the pre-camera sbf? edit: sorry - didn't read you right at first. i have tried it through rsd lite and no go.
I don't actually want to go back to that.. just want to know what the deal is with my "unlocked" bootloader. what i think is that the bootloader cannot be downgraded (and then gpt.bin and stuff subsequently cannot be). Someone pulled an oopsie with the 4.4 update because even the AT&T/Verizon versions can downgrade, so we can downgrade that but not to the pre-camera one.
I'm just used to nexuses where i can fastboot flash whatever i want whenever i want. i would just love clarification just to know what the deal is.
mohlsen8 said:
Are you saying you were able to flash the pre-camera sbf? edit: sorry - see you said you didn't try this. i have tried it through rsd lite and no go.
I don't actually want to go back to that.. just want to know what the deal is with my "unlocked" bootloader. what i think is that the bootloader cannot be downgraded (and then gpt.bin and stuff subsequently cannot be). Someone pulled an oopsie with the 4.4 update because even the AT&T/Verizon versions can downgrade, so we can downgrade that but not to the pre-camera one.
I'm just used to nexuses where i can fastboot flash whatever i want whenever i want. i would just love clarification just to know what the deal is.
Click to expand...
Click to collapse
No I couldn't flash the pre camera sbf firmware after accepting the camera fix through ota, I believe flashing the ota flashes something that's prevents you from downgrading. You could try inserting the camera fix gpt.bin file into the pre camera sbf file and see if it flashes ?don't know if it will work
Sent on my Moto X
flashallthetime said:
No I couldn't flash the pre camera sbf firmware after accepting the camera fix through ota, I believe flashing the ota flashes something that's prevents you from downgrading. You could try inserting the camera fix gpt.bin file into the pre camera sbf file and see if it flashes ?don't know if it will work
Sent on my Moto X
Click to expand...
Click to collapse
at that point i could easily just flash everything other than gpt.bin and motoboot. i was hopping around on some of them today just to check it out. it's those two that are the issue.
mohlsen8 said:
at that point i could easily just flash everything other than gpt.bin and motoboot. i was hopping around on some of them today just to check it out. it's those two that are the issue.
Click to expand...
Click to collapse
now that's interesting. figured i'd try it anyway, so in the pre-camera SBF file i replaced gpt.bin with the post-camera gpt.bin and it flashes fine through rsd lite, motoboot and all. what the hell.
I think you can downgrade to any version. Check out the xml file for the order of operations. You will see some of them flash a few parts, then reboot the phone, and then continue with the flashing process. Others flash everything one partition after the other. I believe that reboot is vital for certain downgrades.
Steve-x said:
I think you can downgrade to any version. Check out the xml file for the order of operations. You will see some of them flash a few parts, then reboot the phone, and then continue with the flashing process. Others flash everything one partition after the other. I believe that reboot is vital for certain downgrades.
Click to expand...
Click to collapse
i thought that as well and compared the two 4.2.2 xml's and did not find any real differences like that. not to mention gpt.bin is the first thing flashed and it fails when it tries to flash it. i'd like to know if anyone is or was able to directly flash 4.2.2 pre-camera without replacing the gpt.bin or motoboot.
mohlsen8 said:
i thought that as well and compared the two 4.2.2 xml's and did not find any real differences like that. not to mention gpt.bin is the first thing flashed and it fails when it tries to flash it. i'd like to know if anyone is or was able to directly flash 4.2.2 pre-camera without replacing the gpt.bin or motoboot.
Click to expand...
Click to collapse
i would assume that your issue is coming from flashing OTAs that are not specific for dev phones (don't even know if dev phone OTAs are available). Im not certain of all of this, but when you flash the same OTA that a non-dev phone uses, it will still impliment the security checks to not let you downgrade even though your bootlader is unlocked. Perhaps you may need to unlock the bootloader again (even though it says it is unlocked). Again, i don't actually know this to be true, but I would assume that there is an error somewhere in some code that is relocking (or something like that) a dev phone that flashes the OTAs that are coming out. A nexus wouldn't ahve this problem because none of their OTAs are ever locked anyway (i believe). So the problem is probably with Verizon not releasing a different OTA for unlocked dev phones as opposed to consumer editions.
Im just speculating. Im sure you can find the answer on google if you read up about what unlocking the bootloader actually means.
jayboyyyy said:
i would assume that your issue is coming from flashing OTAs that are not specific for dev phones (don't even know if dev phone OTAs are available). Im not certain of all of this, but when you flash the same OTA that a non-dev phone uses, it will still impliment the security checks to not let you downgrade even though your bootlader is unlocked. Perhaps you may need to unlock the bootloader again (even though it says it is unlocked). Again, i don't actually know this to be true, but I would assume that there is an error somewhere in some code that is relocking (or something like that) a dev phone that flashes the OTAs that are coming out. A nexus wouldn't ahve this problem because none of their OTAs are ever locked anyway (i believe). So the problem is probably with Verizon not releasing a different OTA for unlocked dev phones as opposed to consumer editions.
Im just speculating. Im sure you can find the answer on google if you read up about what unlocking the bootloader actually means.
Click to expand...
Click to collapse
is that a dig? you don't have to be a jerk. i'm not some idiot pressing buttons over here. just asking if anyone knows why this is.
this is for t-mobile. but i have a gsm dev edition, same model as t-mobile etc. even the official firmware files for the GSM Developer Edition, that i downloaded directly from Motorola themselves, are labeled "T-MOBILE RETAIL..". i don't think the dev edition ever had the pre-camera version (it shipped with the update applied). so maybe you're right about that. i dunno. i'm not the only one who's reporting this. i was just really curious to know why this is.
I have rooted every phone i've had and for some reason the MOTO X is confusing me! The phone is a bone stock developers Ed. 4.2.2 pre camera.
I am confused as to which jcase method to use or if there is another option.
I am guessing PwnMyMoto 1.4.3 verizon. but i'm not sure.
Any help would be fantastic.
Thanks,
J
ejason said:
I have rooted every phone i've had and for some reason the MOTO X is confusing me! The phone is a bone stock developers Ed. 4.2.2 pre camera.
I am confused as to which jcase method to use or if there is another option.
I am guessing PwnMyMoto 1.4.3 verizon. but i'm not sure.
Any help would be fantastic.
Thanks,
J
Click to expand...
Click to collapse
PwnMyMoto and jcase's methods are for locked bootloaders. You first need to unlock your bootloader. Then you need to decide if you want to take the OTA to 4.4 or not because once you upgrade to 4.2.2 post-camera, you can never downgrade to 4.2.2 pre-camera without bricking your device.
If you want to upgrade to 4.4, here are the instructions to unlock and gain root:
[STEP-BY-STEP INSTRUCTIONS] Unlocking and Rooting a Dev Ed Moto X Running Kit Kat
I have read of others who kept the 4.2.2 bootloader and other partitions and just selectively flashed those partitions they wanted as each new upgrade's sbf firmware was released. I don't know what advantages there are to doing that.
ejason said:
I have rooted every phone i've had and for some reason the MOTO X is confusing me! The phone is a bone stock developers Ed. 4.2.2 pre camera.
I am confused as to which jcase method to use or if there is another option.
I am guessing PwnMyMoto 1.4.3 verizon. but i'm not sure.
Any help would be fantastic.
Thanks,
J
Click to expand...
Click to collapse
It's a Developer Edition. Take all the updates available (4.2.2 camera update, 4.4 and now 4.4.2). Get the unlock code from Motorola and unlock your bootloader. Once that is done, flash twrp recovery and then install root via twrp.
Very simple on Dev Editions just because you can unlock the bootloader and flash an alternate recovery (twrp, cwm, etc..).
I agree. Unlock your bootloader (Doesn't void warranty on Developer Edition), flash TWRP recovery, then boot to TWRP and install/flash SuperSU. And it doesn't matter what ROM version you're running. (there is a TWRP for 4.2.2 and one for 4.4/4.4.2).
As mentioned, the bootloader included in the android versions can prevent you from downgrading the rom version. (i.e. bootloader in 4.4.2 prevents you from downgrading to any previous ROM). Why would you want to downgrade? If you have a locked bootloader, you'd want to downgrade to be able to use the root processes needed when you have a locked bootloader. But if you have an unlocked bootloader, because you can flash an alternate recovery (not possible with locked bootloader) and root no matter what ROM version you have installed, the only reason to downgrade would be if you encounter a bug you can't deal with that isn't present in the older roms.
because 4.4.2 fixes the exchange and bluetooth issues, and doesn't introduce anything new, its suggested you update to 4.4.2 if you have an unlocked boot loader (4.4.2 isn't rootable on locked bootloaders and may not be, so its recommended that those with locked bootloaders who want to root stick with 4.4).
KidJoe said:
I agree. Unlock your bootloader (Doesn't void warranty on Developer Edition), flash TWRP recovery, then boot to TWRP and install/flash SuperSU. And it doesn't matter what ROM version you're running. (there is a TWRP for 4.2.2 and one for 4.4/4.4.2).
I didn't know there was a different TWRP for 4.2.2.
As mentioned, the bootloader included in the android versions can prevent you from downgrading the rom version. (i.e. bootloader in 4.4.2 prevents you from downgrading to any previous ROM). Why would you want to downgrade? If you have a locked bootloader, you'd want to downgrade to be able to use the root processes needed when you have a locked bootloader. But if you have an unlocked bootloader, because you can flash an alternate recovery (not possible with locked bootloader) and root no matter what ROM version you have installed, the only reason to downgrade would be if you encounter a bug you can't deal with that isn't present in the older roms.
because 4.4.2 fixes the exchange and bluetooth issues, and doesn't introduce anything new, its suggested you update to 4.4.2 if you have an unlocked boot loader (4.4.2 isn't rootable on locked bootloaders and may not be, so its recommended that those with locked bootloaders who want to root stick with 4.4).
Click to expand...
Click to collapse
From what i have read 4.4.2 isn't rootable at all. Even if you have an unlocked bootloader. Is that correct?
Great info, thanks.
I thought that the Verizon DE already had an unlocked bootloader? Or is it like an HTC where i have to go the the MOTOROLA webite and get a code?
I did something like that for an HTC ONE i have on straight talk. I unlocked the bootloader from the HTC website, then installed TWRP, and then rooted and its running a 4.4.2 ROM that is great.
ejason said:
From what i have read 4.4.2 isn't rootable at all. Even if you have an unlocked bootloader. Is that correct?
Click to expand...
Click to collapse
Incorrect. You can do whatever you want with the DE, regardless of what version of Android you're on.
Sent from my Moto X
ejason said:
I thought that the Verizon DE already had an unlocked bootloader? Or is it like an HTC where i have to go the the MOTOROLA webite and get a code?
Click to expand...
Click to collapse
There are directions on a 1 page pamphlet that came with your VZW DE on how to unlock the bootloader.
Sent from my Dev Edition Moto X
ejason said:
I thought that the Verizon DE already had an unlocked bootloader? Or is it like an HTC where i have to go the the MOTOROLA webite and get a code?
Click to expand...
Click to collapse
It is all in that step-by-step link I gave you above.
Ok, so i have my phone unlocked, updated to 4.4 and for some reason i can not flash the TWRP.
I get the error (bootloader) variable not supported!
Any ideas.
I have tried both mfastboot and fastboot and i get nothing.
I also moved all files into another folder and CD into that folder and still the same error.
Can i install the TWRP with goo manager?
ejason said:
Ok, so i have my phone unlocked, updated to 4.4 and for some reason i can not flash the TWRP.
I get the error (bootloader) variable not supported!
Any ideas.
I have tried both mfastboot and fastboot and i get nothing.
I also moved all files into another folder and CD into that folder and still the same error.
Can i install the TWRP with goo manager?
Click to expand...
Click to collapse
did it finish flashing? mine says that when i flash a recovery also, but it flashes.
after you flash it dont reboot, just go into recovery (volume down to move the selection, volume up to execute)
then select reboot system, and it will ask if you want to root.
ejason said:
ok, so i have my phone unlocked, updated to 4.4 and for some reason i can not flash the twrp.
I get the error (bootloader) variable not supported!
Any ideas.
I have tried both mfastboot and fastboot and i get nothing.
I also moved all files into another folder and cd into that folder and still the same error.
Can i install the twrp with goo manager?
Click to expand...
Click to collapse
ok, thanks for everyones hellp. Done and done..
My Moto X won't boot, and it's 4.4.2 so the stock 4.4 image from Motorola won't flash. I get some type of gpt downgrade warning.
What can I do? I don't care about preserving data.
Thanks
fbiryujin said:
My Moto X won't boot, and it's 4.4.2 so the stock 4.4 image from Motorola won't flash. I get some type of gpt downgrade warning.
What can I do? I don't care about preserving data.
Thanks
Click to expand...
Click to collapse
flash this 4.4.2 SBF file for verizon
http://sbf.droid-developers.org/download.php?device=0&file=841
enjoy
dray_jr said:
flash this 4.4.2 SBF file for verizon
http://sbf.droid-developers.org/download.php?device=0&file=841
enjoy
Click to expand...
Click to collapse
Thanks. I will give that a shot tonight.
I don't understand why you believe you can't flash 4.4 over 4.4.2 with dev edition with an unlocked bootloader. That only applies to locked bootloaders.
nhizzat said:
I don't understand why you believe you can't flash 4.4 over 4.4.2 with dev edition with an unlocked bootloader. That only applies to locked bootloaders.
Click to expand...
Click to collapse
sorry you are wrong there that applies to all Moto X's
you can not flash 4.4 before the bootloader will not downgrade you will get a error when it tries.
the only upside to having a unlocked bootloader is that you can root any version of android by just installed a custom recovery then installing the SuperSU flashable zip file.
Today
07:10 PM
by poda13
Replies: 1
Views: 76
Go to first new post
hope that helps
dray_jr said:
sorry you are wrong there that applies to all Moto X's
you can not flash 4.4 before the bootloader will not downgrade you will get a error when it tries.
the only upside to having a unlocked bootloader is that you can root any version of android by just installed a custom recovery then installing the SuperSU flashable zip file.
Click to expand...
Click to collapse
You're right. The 4.4.2 bootloader can't be downgraded regardless of model.
nhizzat said:
You're right. The 4.4.2 bootloader can't be downgraded regardless of model.
Click to expand...
Click to collapse
The 4.4.2 bootloader can't be downgraded; but I think the 4.4 system image and kernel could flashed just fine on an unlocked unit even if the bootloader has been upgraded for 4.4.2. You would need to flash the 4.4 manually so that it doesn't try and flash the 4.4 bootloader though.
jasoraso said:
The 4.4.2 bootloader can't be downgraded; but I think the 4.4 system image and kernel could flashed just fine on an unlocked unit even if the bootloader has been upgraded for 4.4.2. You would need to flash the 4.4 manually so that it doesn't try and flash the 4.4 bootloader though.
Click to expand...
Click to collapse
This is what I had to wind up doing as the other image I had wouldn't flash. I edited the xml to skip the gpt and bootloader, and it flashed 4.4 back. Updated again and I'm all good
fbiryujin said:
This is what I had to wind up doing as the other image I had wouldn't flash. I edited the xml to skip the gpt and bootloader, and it flashed 4.4 back. Updated again and I'm all good
Click to expand...
Click to collapse
please dont do that if you need to flash the 4.4.2 for verizon. please grab it from SBF they have added the 4.4.2 SBF package for verizon on the website. i do not recommend editing the XML file for the chance or bricking your phone.
Can we update phone's software via ota even after unlocking the boot loader and installing custom recovery
Nooooooooooooooooo
No, Not even in your dreams,
From what I've learned from my own Issue
http://forum.xda-developers.com/moto-x/moto-x-qa/totally-screwed-updating-rooted-x-4-4-4-t2896292
Never update phone's software via ota, while you are on Custom Recovery.
Patel21 is correct, you can't with a custom recovery.
You need stock recovery to take the OTA, then you can reinstall a custom recovery
m.ryuu said:
Can we update phone's software via ota even after unlocking the boot loader and installing custom recovery
Click to expand...
Click to collapse
Yes you can as long as you flash back to stock recovery before accepting the OTA. Once done, flash custom recovery and root if lost.
m.ryuu said:
Can we update phone's software via ota even after unlocking the boot loader and installing custom recovery
Click to expand...
Click to collapse
OTA will not install when you have a custom recovery on your phone. Instead you'll be stuck in a bootloop if you have tried to install an OTA with a custom recovery.
Rather than my retyping everything... Please see -> http://mark.cdmaforums.com/MotoX-OTA.html
I've flashed ota updates via custom recovery, you just have to know what you're doing. Also, the Moto boot loader won't relock as far as I know after an update. It doesn't on the Dev edition, not sure about unlocked retail or devices that have been unlocked with sunshine.
Sent from my Moto X
Since all unlocked devices are the same as the dev edition....the same would be true.
KJ said:
Since all unlocked devices are the same as the dev edition....the same would be true.
Click to expand...
Click to collapse
The only thing I want sure of was sunshine. If you unlocked via a code, then yes, all of them act the same.
Sent from my Moto X
imnuts said:
I've flashed ota updates via custom recovery, you just have to know what you're doing. Also, the Moto boot loader won't relock as far as I know after an update. It doesn't on the Dev edition, not sure about unlocked retail or devices that have been unlocked with sunshine.
Sent from my Moto X
Click to expand...
Click to collapse
I don't completely understand how Sunshine works, so I can't say for sure, however based on reading the thread, my understanding is it wont relock.
But if you unlock via mfastboot oem unlock {YourUniqueCode} your bootloader will not relock itself. This holds true for developer and non-developer alike.
Someone pls post a Link to stock recovery
m.ryuu said:
Someone pls post a Link to stock recovery
Click to expand...
Click to collapse
It's in the sbf for your phone/carrier/version.
4.4.4 version Asia retail not there
m.ryuu said:
4.4.4 version Asia retail not there
Click to expand...
Click to collapse
Have you checked -> http://www.filefactory.com/folder/dd05c058d3ff8dbe/?sort=created&order=DESC&show=25 too?
Is it possible to get custom roms on xperia play r800i locked boot loader. Running gin2kat android 2.3.7.
I have unlocked bootloader, flashed Custom Recovery TWRP to my Moto G2 XT1068 and rooted on 4.4.4 stock, while waiting for the official lollipop updates.
So does this break the OTA, and if so how to enable it again?!
Yes you don't get official Lollipop OTA if you unlock your bootloader. For getting official OTA you have to unroot ur phone and relock the bootloader
sumit227 said:
Yes you don't get official Lollipop OTA if you unlock your bootloader. For getting official OTA you have to unroot ur phone and relock the bootloader
Click to expand...
Click to collapse
Okay, understood. thanks mate
And a few threads along the road you will read:Just do a full unroot and reflash stock recovery,unlocked bootloader is no problem for capturing OTA.
I don't know.....
Sent from my XT1068 using XDA Free mobile app
Rooting didnt affect OTA with my old moto g upgrading from 4.4.2 to 4.4.4 and probably wont affect the new moto g too
epivitor said:
Rooting didnt affect OTA with my old moto g upgrading from 4.4.2 to 4.4.4 and probably wont affect the new moto g too
Click to expand...
Click to collapse
No. You will receive ota but you can't install it. For root to work, /system has to be modified. The OTA-package will recognize this and refuses to install.
sumit227 said:
Yes you don't get official Lollipop OTA if you unlock your bootloader. For getting official OTA you have to unroot ur phone and relock the bootloader
Click to expand...
Click to collapse
Also not true. OTA does not require a relock. Only unroot and stock-recovery is required.
Wolfcity said:
And a few threads along the road you will read:Just do a full unroot and reflash stock recovery,unlocked bootloader is no problem for capturing OTA.
I don't know.....
Sent from my XT1068 using XDA Free mobile app
Click to expand...
Click to collapse
Yes, because it is a fact.
doppelhelix said:
Also not true. OTA does not require a relock. Only unroot and stock-recovery is required.
Click to expand...
Click to collapse
Wolfcity said:
And a few threads along the road you will read:Just do a full unroot and reflash stock recovery,unlocked bootloader is no problem for capturing OTA.
I don't know.....
Click to expand...
Click to collapse
Oh my bad sorry, for OTA we don't need to relock I think relock is for regain the warranty correct me if I'm wrong.
Thanks for the answers guys.
Now why the heck i can't relock the bootloader whatever i do?! did anyone successfully relocked the bootloader before, and if so. how?!
i've followed all the guides around and it always give me errors and i can't flash rom!!
and in fact isnt really any useful to relock it?!
solly84 said:
it always give me errors and i can't flash rom!!
Click to expand...
Click to collapse
That's a bit vague. Please post exactly the output on your screen.
doppelhelix said:
That's a bit vague. Please post exactly the output on your screen.
Click to expand...
Click to collapse
sure!
seems like i cant relock my bootloader, whenever i do all the sequence of flashing the stock rom without the "oem lock begin" everything goes smoothly and i can restore to stock image.
as soon as i put "oem lock begin" i got a error in boot.img:
bootloader preflash validation failed
bootloader invalid signed image
and it doesn't continue...
solly84 said:
bootloader preflash validation failed
bootloader invalid signed image
Click to expand...
Click to collapse
Maybe the rom currently installed and the rom you try to flash and lock are not the same. Or, at one point you installed a rom that had a version above your current one. There are some partitions that can't be downgraded, like gpt and motoboot (which is the bootloader). Subsequently the lock will fail. Anyway, locking the bootloader is absolutely not necessary. There is no benefit in doing so.
doppelhelix said:
Maybe the rom currently installed and the rom you try to flash and lock are not the same. Or, at one point you installed a rom that had a version above your current one. There are some partitions that can't be downgraded, like gpt and motoboot (which is the bootloader). Subsequently the lock will fail. Anyway, locking the bootloader is absolutely not necessary. There is no benefit in doing so.
Click to expand...
Click to collapse
Yeah, i had tried a lot of Roms, so maybe that is why. And now i am on Custom Lollipop Rom (Titan)...
but eventually as you said, its not necessary, so i will just forget about it.
Thanks man.