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 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.
Is there any method to unlock the bootloader without activating the system developer option? I'm stuck on the boot screen and I can't unlock. ANDROID 5.1
Christian Correia said:
Is there any method to unlock the bootloader without activating the system developer option? I'm stuck on the boot screen and I can't unlock. ANDROID 5.1
Click to expand...
Click to collapse
Can you get into bootloader mode? And if not, what have you tried to get into bootloader mode?
JulesJam said:
Can you get into bootloader mode? And if not, what have you tried to get into bootloader mode?
Click to expand...
Click to collapse
Yes. Enter the RECOVERY and FASTBOOT normally. Actually I don't know what is bootloader mode, more goes into recovery and fastboot
Christian Correia said:
Yes. Enter the RECOVERY and FASTBOOT normally. Actually I don't know what is bootloader mode, more goes into recovery and fastboot
Click to expand...
Click to collapse
bootloader mode = fastboot
If a full system.img of 5.1 is not available for your device, I would get into bootloader mode and try to flash the 5.0 stock system using fastboot or mfastboot. Then see if you can unlock the bootloader. It may not work if you have upgraded your bootloader to 5.1 and please note - you cannot safely downgrade either the bootloader or partition table so don't even try.
What model device do you have? I am assuming that there is no 5.1 system.img available.
JulesJam said:
bootloader mode = fastboot
If a full system.img of 5.1 is not available for your device, I would get into bootloader mode and try to flash the 5.0 stock system using fastboot or mfastboot. Then see if you can unlock the bootloader. It may not work if you have upgraded your bootloader to 5.1 and please note - you cannot safely downgrade either the bootloader or partition table so don't even try.
What model device do you have? I am assuming that there is no 5.1 system.img available.
Click to expand...
Click to collapse
Unfortunately I can't downgrade. And the BOOTLOADER has been updated to version 60.16. The way it's going to be wait the full image (XT1097 5.1 23.11.14 current)
Christian Correia said:
Unfortunately I can't downgrade.
Click to expand...
Click to collapse
Why can't you downgrade just the system partition? If you get the official copy or the fxz, it is a signed image and so you can flash it using fastboot or mfastboot even with a locked bootloader. You may need to flash the 5.0 boot.img too.
What model do you have?
JulesJam said:
Why can't you downgrade just the system partition? If you get the official copy or the fxz, it is a signed image and so you can flash it using fastboot or mfastboot even with a locked bootloader. You may need to flash the 5.0 boot.img too.
What model do you have?
Click to expand...
Click to collapse
I tried to pass the 5.0 system image, plus the error. I do not know what to do. Precise image 5.1 23.32-14 which is what I was before the brick
Christian Correia said:
I tried to pass the 5.0 system image, plus the error. I do not know what to do. Precise image 5.1 23.32-14 which is what I was before the brick
Click to expand...
Click to collapse
What model phone do you have? Brazilian XT1097?
JulesJam said:
What model phone do you have? Brazilian XT1097?
Click to expand...
Click to collapse
Yes
Christian Correia said:
Yes
Click to expand...
Click to collapse
I think this is the official 5.0 firmware for it.
http://forum.xda-developers.com/moto-x-2014/development/rom-retail-br-firmware-t2995818
I would download it, then extract the system file(s). I don't know if they will be in sparsechunks or a single file, but if they are in sparsechunks, you can use regular fastboot to flash them. If the system is a single file system.img, you will have to use mfastboot version 2 to flash it.
I would try just flashing the system partition and then see if it boots. If not, then I would flash the 5.0 boot.img.
You also could try downgrading to 4.4.4 system, I know others have done it successfully.
Just do NOT take any OTAs - people are bricking when they downgrade and then take an OTA. You must wait for the 5.1 firmware to be released to flash it. Don't take an OTA.
JulesJam said:
I think this is the official 5.0 firmware for it.
http://forum.xda-developers.com/moto-x-2014/development/rom-retail-br-firmware-t2995818
I would download it, then extract the system file(s). I don't know if they will be in sparsechunks or a single file, but if they are in sparsechunks, you can use regular fastboot to flash them. If the system is a single file system.img, you will have to use mfastboot version 2 to flash it.
I would try just flashing the system partition and then see if it boots. If not, then I would flash the 5.0 boot.img.
You also could try downgrading to 4.4.4 system, I know others have done it successfully.
Just do NOT take any OTAs - people are bricking when they downgrade and then take an OTA. You must wait for the 5.1 firmware to be released to flash it. Don't take an OTA.
Click to expand...
Click to collapse
Friend didn't work. Gave Error DOWNGRADED VERSION SYSTEM
Christian Correia said:
Friend didn't work. Gave Error DOWNGRADED VERSION SYSTEM
Click to expand...
Click to collapse
The only other thing you could do and I don't know if the dev would agree to this, is use a software tool we have called MoFo - it allows you to flash unsigned files as long as they are in the ext4 format.
The developer is @maiko1 and I will ask on the MoFo thread if he would consider opening up the tool for this purpose. It costs $20 USD for the software. It would allow you bypass the bootloader signature check and force flash any unsigned file you want to the system partition.
http://forum.xda-developers.com/general/paid-software/mofo-root-turbo-t3064404
JulesJam said:
The only other thing you could do and I don't know if the dev would agree to this, is use a software tool we have called MoFo - it allows you to flash unsigned files as long as they are in the ext4 format.
The developer is @maiko1 and I will ask on the MoFo thread if he would consider opening up the tool for this purpose. It costs $20 USD for the software. It would allow you bypass the bootloader signature check and force flash any unsigned file you want to the system partition.
http://forum.xda-developers.com/general/paid-software/mofo-root-turbo-t3064404
Click to expand...
Click to collapse
Works even with the locked bootloader? I am not spending money for nothing? Sure it works? Where can I get these images ext4?
Christian Correia said:
Works even with the locked bootloader? I am not spending money for nothing? Sure it works? Where can I get these images ext4?
Click to expand...
Click to collapse
Let me download the 5.0 image for your device and see if I can flash it to my XT1096 first using mofo.exe. I have a locked bootloader.
Since your bootloaders are unlockable, there is the possibility that maiko1 would discount it for you, idk, but you could ask since really it would just be a one time repair tool.
Also, do you know if someone who is still on the 5.1 soak can pull the 5.1 image from their device and make it flashable by mfastboot? Or would it fail the signature check? I don't know enough about that to know.
The other potential issue is that your boot.img is now 5.1 and maybe that would not boot with the 5.0 system.img. It should but you would need someone with an unlocked bootloader to try it and see if the 5.1 boot.img can run with the 5.0 system.
JulesJam said:
Let me download the 5.0 image for your device and see if I can flash it to my XT1096 first using mofo.exe. I have a locked bootloader.
Since your bootloaders are unlockable, there is the possibility that maiko1 would discount it for you, idk, but you could ask since really it would just be a one time repair tool.
Also, do you know if someone who is still on the 5.1 soak can pull the 5.1 image from their device and make it flashable by mfastboot? Or would it fail the signature check? I don't know enough about that to know.
Click to expand...
Click to collapse
I'm going to be standing by then. If it works I will buy
Christian Correia said:
I'm going to be standing by then. If it works I will buy
Click to expand...
Click to collapse
The dev has to agree to open it up for your model and I added this to my last post:
The other potential issue is that your boot.img is now 5.1 and maybe that would not boot with the 5.0 system.img. It should but you would need someone with an unlocked bootloader to try it and see if the 5.1 boot.img can run with the 5.0 system.
You would need to get someone with an unlocked bootloader XT1097 to see if the 5.1 boot.img will boot the 5.0 system.img. I think it should but it would be better to have someone test it.
JulesJam said:
The dev has to agree to open it up for your model and I added this to my last post:
The other potential issue is that your boot.img is now 5.1 and maybe that would not boot with the 5.0 system.img. It should but you would need someone with an unlocked bootloader to try it and see if the 5.1 boot.img can run with the 5.0 system.
You would need to get someone with an unlocked bootloader XT1097 to see if the 5.1 boot.img will boot the 5.0 system.img. I think it should but it would be better to have someone test it.
Click to expand...
Click to collapse
Thank you. I'm awaiting any news
Christian Correia said:
Thank you. I'm awaiting any news
Click to expand...
Click to collapse
And I guess the other potential issue is whether the 5.1 bootloader will unlock when running the 5.0 system.img - it may not. But at least your phone would work until the 5.1 firmware is released.
I am downloading the Brazilian XT1097 5.0 firmware file now and will flash it if it is flashable by mofo.exe - it will take me about an hour or so if everything goes smoothly.
---------- Post added at 04:42 AM ---------- Previous post was at 03:55 AM ----------
Christian Correia said:
Thank you. I'm awaiting any news
Click to expand...
Click to collapse
Ok, the image is broken down into sparse chunks like the AT&T XT1097. I will enlist the help of someone who was able to make the AT&T image into a single file ext4 file that could be flashed by mofo.exe but it is late my time so it won't be until tomorrow. It takes linux to do that and I don't use linux.
Also, there is the possibility that the exploit that mofo.exe relies on is patched in the 5.1 bootloader. I doubt it since 5.1 was out before mofo.exe was released. Maybe maiko1 would let you test it for free since we only know for sure that it works on the 5.0 and 5.0.2 bootloaders.
Christian Correia said:
Thank you. I'm awaiting any news
Click to expand...
Click to collapse
I have made the single file image but now I need another poster here to remove the footer and the header using a hex editor. Once that is done I can flash it to my device using mofo.exe to see if it flashes.
JulesJam said:
I have made the single file image but now I need another poster here to remove the footer and the header using a hex editor. Once that is done I can flash it to my device using mofo.exe to see if it flashes.
Click to expand...
Click to collapse
I'm waiting eagerly. Because it's been more than 1 week without my dear appliance. And I've tried everything to resuscitate him. And from what I've seen, the only way is to have a system image :fingers-crossed:
I am from China. My xt1079 is locked. I used the rsd to flash 6.0 XT1079_THEA_RETASIA_DS_6.0_MPB24.65-34_cid7_subsidy-DEFAULT_CFC.xml.zip But it failed in flash boot and not can flash the 5.02. I need help.
fastboot in phone had pink words:version downgraded for primary_gpt. How can i deal this?
kenny2016 said:
I am from China. My xt1079 is locked. I used the rsd to flash 6.0 XT1079_THEA_RETASIA_DS_6.0_MPB24.65-34_cid7_subsidy-DEFAULT_CFC.xml.zip But it failed in flash boot and not can flash the 5.02. I need help.
fastboot in phone had pink words:version downgraded for primary_gpt. How can i deal this?
Click to expand...
Click to collapse
That's because the firmware you downloaded IS NOT the one for your region. The only way to fix it is to unlock the bootloader and then flash 6.0 again.
I guess you can't downgrade to 5.0.2 since your bootloader is already updated to 48.86 which is meant for 6.0.
Chefry22 said:
That's because the firmware you downloaded IS NOT the one for your region. The only way to fix it is to unlock the bootloader and then flash 6.0 again.
I guess you can't downgrade to 5.0.2 since your bootloader is already updated to 48.86 which is meant for 6.0.
Click to expand...
Click to collapse
I not can boot My phone now. It always in factory. I try to select Normal powerup.But It say version downgraded for boot failed to validate boot image. I try to unlock Myphone. This is oem not allow. I not know why It failed in boot in flash 6.0. Thank you to reply me.
Chefry22 said:
That's because the firmware you downloaded IS NOT the one for your region. The only way to fix it is to unlock the bootloader and then flash 6.0 again.
I guess you can't downgrade to 5.0.2 since your bootloader is already updated to 48.86 which is meant for 6.0.
Click to expand...
Click to collapse
I see bl version is 0.5 and version- bl is 4821
So, as the title says, I had a Moto X XT1058 from AT&T.
I updated a long time ago to Lollipop and the phone worked perfectly fine until yesterday, when suddenly shutted down and when I restarted, got stuck on M logo.
I restarted to bootloader(?) pressing power off and vol down buttons.
The version that shows me is 30.BE
The device wasn't unlocked or rooted, because I was happy with the stock ROM, so it says Device is LOCKED ans Status Code 0.
I tried every option on this menu and everyone says (in red):
"No valid PIV block in SP for system
piv validation failed (system)
Boot up failed"
I tryed with abd, fastboot, mfastboot and RSDLite to flash gpt.bin and motoboot.img and every time I do it I get a error, and the operation fails.
For what I've read in tooooooo many posts, it's probably death, but I resist to this idea, so I came here to ask for advice.
THE PHONE IS NOT IN WARRANTY ANY MORE.
Thanks in advance and sorry for my english (not my native language).
why dont you try twrp recovery ?
just flash it
fadyrox said:
why dont you try twrp recovery ?
just flash it
Click to expand...
Click to collapse
Can I do it if my phone isn't rooted? The bootloader it's locked!
Flash full stock att 5.1 rom, it will be fine.
Salik Iqbal said:
Flash full stock att 5.1 rom, it will be fine.
Click to expand...
Click to collapse
Flashing via fastboot mode will be okay !
do search here you will get details !
fadyrox said:
Flashing via fastboot mode will be okay !
do search here you will get details !
Click to expand...
Click to collapse
But I never flashed any ROM on this phone. I got Lollipop from a OTA update. My phone was stock. Never rooted, never unlock bootloader. I didn't find any tutorial to do it with this characteristics.
And it's an AT&T xt1058
MatiCepe said:
But I never flashed any ROM on this phone. I got Lollipop from a OTA update. My phone was stock. Never rooted, never unlock bootloader. I didn't find any tutorial to do it with this characteristics.
And it's an AT&T xt1058
Click to expand...
Click to collapse
first you need to unlock your bootloader .. otherwise you wont be able to recover your device
Please do a search regarding unlocking bootloader !
fadyrox said:
first you need to unlock your bootloader .. otherwise you wont be able to recover your device
Please do a search regarding unlocking bootloader !
Click to expand...
Click to collapse
The bootloader of the XT1058 from AT&T is'nt unlockable.... That's the big trouble. I've read that it can be done if it's no 4.2.2, but not if the version is newer.
MatiCepe said:
The bootloader of the XT1058 from AT&T is'nt unlockable.... That's the big trouble. I've read that it can be done if it's no 4.2.2, but not if the version is newer.
Click to expand...
Click to collapse
Download rsd lite for windows, get latest stock rom for att, reboot your phone into fastboot, flash stock rom and you are done.
Salik Iqbal said:
Download rsd lite for windows, get latest stock rom for att, reboot your phone into fastboot, flash stock rom and you are done.
Click to expand...
Click to collapse
I searched and the lastone is ATT_XT1058_5.1.0_LPA23.12-21.7_cid1_CFC.xml.zip. I try to flash it on my phone via RSD and the process showsme this error:
Failed flashing process. 4/18 flash motoboot "motoboot.img" -> Phone returned FAIL.
MatiCepe said:
I searched and the lastone is ATT_XT1058_5.1.0_LPA23.12-21.7_cid1_CFC.xml.zip. I try to flash it on my phone via RSD and the process showsme this error:
Failed flashing process. 4/18 flash motoboot "motoboot.img" -> Phone returned FAIL.
Click to expand...
Click to collapse
Is your phone is charge enough? Search 5.1.1 att xml zip
can anybody give a solution for this problem because i am also with a xt1058 at&t, The device wasn't unlocked or rooted and the version that shows me is 30.BE too
sorry my english
What's up with your device any screen shot?
Hi, i have the same problem, my device is locked by AT&T and i cant flash the firmware< i have a unlock code from the AT&T company, how I can introdce that code manually? Thanks!
Thank you
H3c4rtr1 said:
Hi, i have the same problem, my device is locked by AT&T and i cant flash the firmware< i have a unlock code from the AT&T company, how I can introdce that code manually? Thanks!
Click to expand...
Click to collapse
You can help how you got the code, give details.
Thank you