Hi, is been over a week from the ATT 4.4.2 release and i wanted just to ask if someone is working at the full firmware because i really need to flash that after i bad flash an european version without thinking that i had the bootloader locked and an AT&T phone, help! 10 days without and andorid phone!
ATT just started pushing the OTA... it could be a few weeks until we see a full SBF available. Until then, with a locked bootloader there is nothing you can do, because you can't flash files not signed by motorola.
I'm sure as soon as its available it will be posted here -> http://sbf.droid-developers.org/phone.php?device=0
hem, why the firmware isn't out? someone is working at it? i really need the upload because my phone always boot on fastboot for a bad flash, please
Albi.ema23 said:
hem, why the firmware isn't out? someone is working at it? i really need the upload because my phone always boot on fastboot for a bad flash, please
Click to expand...
Click to collapse
Its not out because Moto doesn't release it... we rely on people to gain access and leak the files.. So there is no set time table for them being available.
I'm sure the people who maintain that site are continually trying to grab the latest SBF files. So as soon as they get access to it, it will be posted.
KidJoe said:
Its not out because Moto doesn't release it... we rely on people to gain access and leak the files.. So there is no set time table for them being available.
I'm sure the people who maintain that site are continually trying to grab the latest SBF files. So as soon as they get access to it, it will be posted.
Click to expand...
Click to collapse
ah, so... what i should do? the phone "think" that the last ATT firmware is a downgrade because i tryed to flash the 4.4.2 EU, there is a way or i MUST wait for ATT 4.4.2 firmware?
Albi.ema23 said:
ah, so... what i should do? the phone "think" that the last ATT firmware is a downgrade because i tryed to flash the 4.4.2 EU, there is a way or i MUST wait for ATT 4.4.2 firmware?
Click to expand...
Click to collapse
I would say wait.
Others might suggest flashing say the T-Mobile/GSM DEV XT1053 rom... but I'm not sure how safe that is.
KidJoe said:
I would say wait.
Others might suggest flashing say the T-Mobile/GSM DEV XT1053 rom... but I'm not sure how safe that is.
Click to expand...
Click to collapse
can that be flashed on a XT1058 ATT bootloader locked?
KidJoe said:
I would say wait.
Others might suggest flashing say the T-Mobile/GSM DEV XT1053 rom... but I'm not sure how safe that is.
Click to expand...
Click to collapse
do you think that an motorola service center can do something?
Albi.ema23 said:
can that be flashed on a XT1058 ATT bootloader locked?
Click to expand...
Click to collapse
Locked bootloader? Not sure. And I really hesitate to suggest flashing roms for other models.
Albi.ema23 said:
do you think that an motorola service center can do something?
Click to expand...
Click to collapse
They will likely try and do warranty. But if you flashed with wrong rom, they may not cover it as "under warranty"
Btw, you never really said what rom you tried flashing, and exactly what issues you are having now.
KidJoe said:
They will likely try and do warranty. But if you flashed with wrong rom, they may not cover it as "under warranty"
Btw, you never really said what rom you tried flashing, and exactly what issues you are having now.
Click to expand...
Click to collapse
i tried to flash "Blur_Version.161.44.16.ghost_row.Retail.en.EU" with RDS Lite but the flash has stop at the boot "failed sflashing process. 6/17 flash boot "boot.img" then i tried the same with the adb&fastboot after that i turn on the phone and on the screen there was "Failed to hab check for boot: 0x56 preflash validation failed for boot", Failed to hab check for recovery : 0x56 preflash validation failed for recovery , Failed to hab check for boot: 0x56 PIV block validation for system failed Invalid PIV image: system
then i re flashed the original ATT 4.4 and at the boot in the screen was writen Partition (boot) Security Version Downgraded
Albi.ema23 said:
i tried to flash "Blur_Version.161.44.16.ghost_row.Retail.en.EU" with RDS Lite but the flash has stop at the boot "failed sflashing process. 6/17 flash boot "boot.img" then i tried the same with the adb&fastboot after that i turn on the phone and on the screen there was "Failed to hab check for boot: 0x56 preflash validation failed for boot", Failed to hab check for recovery : 0x56 preflash validation failed for recovery , Failed to hab check for boot: 0x56 PIV block validation for system failed Invalid PIV image: system
then i re flashed the original ATT 4.4 and at the boot in the screen was writen Partition (boot) Security Version Downgraded
Click to expand...
Click to collapse
Yeah, once you get 4.4.2 on there you do NOT want to downgrade.
At this point, you can try reading -> http://forum.xda-developers.com/moto-x/general/tut-resurrecting-bricked-moto-x-corrupt-t2629057 but post #120 implies you need the ATT 4.4.2 SBF to really fix it.
KidJoe said:
Yeah, once you get 4.4.2 on there you do NOT want to downgrade.
At this point, you can try reading -> http://forum.xda-developers.com/moto-x/general/tut-resurrecting-bricked-moto-x-corrupt-t2629057 but post #120 implies you need the ATT 4.4.2 SBF to really fix it.
Click to expand...
Click to collapse
sorry but what does SBF means?
Albi.ema23 said:
sorry but what does SBF means?
Click to expand...
Click to collapse
Its an acronym. I'm not sure what each of the letters stand for exactly...
Basically an SBF file is a completely stock system image. You flash it through the RSDlite tool. It will completely revert your phone back to stock. FXZ was also used at one point when referring to such an image.
For the X, the SBF is actually a packed zip file which contains all the parts, and an XML file which tells RSDLite what to flash, in what order, and some stuff. You could also unzip it and use mFastboot to flash the individual parts instead of using RSDLite.
KidJoe said:
Its an acronym. I'm not sure what each of the letters stand for exactly...
Basically an SBF file is a completely stock system image. You flash it through the RSDlite tool. It will completely revert your phone back to stock. FXZ was also used at one point when referring to such an image.
For the X, the SBF is actually a packed zip file which contains all the parts, and an XML file which tells RSDLite what to flash, in what order, and some stuff. You could also unzip it and use mFastboot to flash the individual parts instead of using RSDLite.
Click to expand...
Click to collapse
so..that mean i must wait for the 4.4.2 ATT anyway? and that motorola center can't do nothing about it?
Albi.ema23 said:
so..that mean i must wait for the 4.4.2 ATT anyway? and that motorola center can't do nothing about it?
Click to expand...
Click to collapse
to fix it yourself, you need to wait. Or you could do more harm than good.
A moto service center may fix it or send you a refurbished phone. And if they do, they might not cover it under warranty since you have a non-developer edition that you tried to flash the wrong rom too which put you in this situation. i.e. the warranty terms cover defects in materials and workmanship, not drops, getting wet, or other damage from improper operation or use. (flashing the rom for another model or carrier would be considered improper operation or use)... So it might cost $$$
If this is your only phone, and you need it working now, then you have no choice but to call Moto (if Moto Maker) or ATT (if retail non-customized) to see about "warranty" and see what happens. Otherwise use another phone temporarily and just wait for the ATT 4.4.2 SBF to leak, as you should be able to fix your phone by flashing it.
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.
My fiance has a VZW Moto X, 16GB. Since mine was a DE, it was simple to get it rooted and whatnot.
So, I tried the guide that was posted to downgrade to the 4.2.2 camera update, got all of the fastboot stuff done successfully and went to reboot it.
NOW... the damn thing won't even turn on. Not even when I plug it into the charger. F*ck.
So... what do I need to do to get this think back up and running? I really don't want to owe her $300 for whatever happened.
triton302 said:
My fiance just got her VZW Moto X, 16GB. Since mine was a DE, it was simple to get it rooted and whatnot.
So, I tried the guide that was posted to downgrade to the 4.2.2 camera update, got all of the fastboot stuff done successfully and went to reboot it.
NOW... the damn thing won't even turn on. Not even when I plug it into the charger. F*ck.
So... what do I need to do to get this think back up and running? I really don't want to owe her $300 for whatever happened.
Click to expand...
Click to collapse
have you tried holding vol/power down for 10+ seconds or more?
triton302 said:
My fiance just got her VZW Moto X, 16GB. Since mine was a DE, it was simple to get it rooted and whatnot.
So, I tried the guide that was posted to downgrade to the 4.2.2 camera update, got all of the fastboot stuff done successfully and went to reboot it.
NOW... the damn thing won't even turn on. Not even when I plug it into the charger. F*ck.
So... what do I need to do to get this think back up and running? I really don't want to owe her $300 for whatever happened.
Click to expand...
Click to collapse
If you are within the 14 day return period, return it.
Otherwise post on the Slap My Moto thread and ask for help.
triton302 said:
My fiance just got her VZW Moto X, 16GB. Since mine was a DE, it was simple to get it rooted and whatnot.
So, I tried the guide that was posted to downgrade to the 4.2.2 camera update, got all of the fastboot stuff done successfully and went to reboot it.
NOW... the damn thing won't even turn on. Not even when I plug it into the charger. F*ck.
So... what do I need to do to get this think back up and running? I really don't want to owe her $300 for whatever happened.
Click to expand...
Click to collapse
Can you access the fastboot screen?
Sent on my Gummy running Lenoto X
I got it. The whole "QHSUSB_DLOAD" thing was the issue. Somehow I bricked it while flashing and rebooting.
Went through the steps, now it's alive. However, it won't boot. It'll go into fastboot, but not the OS. So now I have to figure out how to flash the correct stuff.
Alright so I f*cked up BIG TIME.
Now I'm getting the CID error, it won't let me flash anything now.
Any help would be awesome... now I'm probably going to owe her $300.
I thought it wasn't possible to downgrade if you had a locked bootloader...
Sent from my XT1060 using Tapatalk
I'm simply following the steps listed in the various tutorials for rooting 4.4...
All I care about now is getting 4.4 back up and running, but I'm not sure if that's possible anymore.
You might want to check this thread:
http://forum.xda-developers.com/showthread.php?t=2629057
Already did, that gets me back into fastboot, but the phone is no longer able to flash the OS from there. So basically, I'm stuck.
And I just found out that it is two days past the 14-day return period. Fantastic.
you might want to try this:
http://shop.teamblackhat.info/Factory-Adapters-motadapt.htm
triton302 said:
And I just found out that it is two days past the 14-day return period. Fantastic.
Click to expand...
Click to collapse
Are you flashing your carriers sbf firmware? It also needs to be the exact same version that was originally installed ie 4.4
How did you flash it, rsdlite or fastboot? You should be using mfastboot if you manually flashed the firmware, did you get any errors during flashing ?
Sent on my Gummy running Lenoto X
flashallthetime said:
Are you flashing your carriers sbf firmware? It also needs to be the exact same version that was originally installed ie 4.4
How did you flash it, rsdlite or fastboot? You should be using mfastboot if you manually flashed the firmware, did you get any errors during flashing ?
Sent on my Gummy running Lenoto X
Click to expand...
Click to collapse
I am using mfastboot using the manual method, no dice. Most of the items i'm flashing give me this error in CMD...
Preflash validation failed
FAILED (remote failure)
On the phone, however, it's telling me this...
Failed to hab check for recovery: 0x39
preflash validation failed for recovery
When I tried to flash the system.img, this...
Failed to hab checkfor system: 0x39
PIV block validation for system failed
Invalid PIV image: system
When having to use the manual method to get into fastboot (http://forum.xda-developers.com/showthread.php?t=2629057), this is the first message that pops up...
Failed to hab check for gpt_main: 0x4e
CID Read Failure
Invalid CID status 0x69
CustomerID error. Contact Dealer: 0xdead
No SP partition found
Fastboot Reason: Invalid CID
I have a VZW Moto X that I rooted. The process was fairly complicated, so I wrote a tutorial for myself--based on a reddit thread--with all the files I needed to do it in case I needed to do it, again, in the future. I'm not sure if it will help you, but maybe it will. I'll PM you a link.
Lesson learned before marriage. Leave the wife's phone alone seriously though man I hope you work it out.
Sent from my XT1060 using Tapatalk
triton302 said:
I am using mfastboot using the manual method, no dice. Most of the items i'm flashing give me this error in CMD...
Preflash validation failed
FAILED (remote failure)
Click to expand...
Click to collapse
I am no expert, but this sounds like whatever you are trying to flash may be corrupted. And maybe mfastboot is corrupted, too.
Redownload everything, check the MD5SUMs and try again.
If the CID partition is messed up or it didn't validate anymore then you're done. You will not be able to flash anything to the phone.
Sell the screen as replacement part on eBay. You'll make more money on the parts of you take it apart than selling it as a whole.
sent via tapatalk
triton302 said:
I am using mfastboot using the manual method, no dice. Most of the items i'm flashing give me this error in CMD...
Click to expand...
Click to collapse
instead of fastboot, have you tried flashing the entire ROM via RSDLite?
KidJoe said:
instead of fastboot, have you tried flashing the entire ROM via RSDLite?
Click to expand...
Click to collapse
Rsd lite is your best bet
Sent from my XT1056 using xda app-developers app
Hi
I have been playing around with my Atrix HD for quite a while now, installing almost all custom roms out there for MB866 (Found Gummy and Carbon to be the best, batakang and holoblur never worked for me).
Restored back to stock using RSD Lite many times (after editing the xml file, no problems)
The bootloader was of course unlocked during "all that".
Now here is the problem. After restoring to stock 4.1.1 (98.4.20.MB886.ATT.en.US) using RSD Lite, I updated to 98.5.38.MB886.ATT.en.US (small 6.2 MB Update recently released).Worked fine till here.
Then I downgraded to ICS and it also worked fine. What made things worse was when I checked for updates via About Phone--> System Updates and it prompted for an Update 98.4.20.MB886.ATT.en.US (the same i used to flash via RSD). But when the download finished, the phone is permanently stuck in fastboot mode with the following message:
----------------------------------------------
AP Fastboot Flash Mode (s)
10.9B(*) (sha-2e68372, 2012-11-17 23:33:08)
eMMC Info: Size 8GB
Device is LOCKED. Status Code:0
Battery OK
Transfer Mode: USB Connected
downgraded security version
update gpt_main version failed
Failed to hab check for gpt_backup: 0x35
failed to load GPT
CID Read Failure
Invalid CID Status 0x69
No SP Partition found
Fastboot Reason: Invalid GPT
----------------------------------------------
You can see the phone is locked and RSD Lite doesent work at all giving "phone returmed fail" or " invalid partition error (battery is charged atleast 70%).
Any help in restoring the phone to "something" will be highly appreciated.
One of the problem is that i cannot find stock files for the latest 98.5.38.MB886.ATT.en.US update anywhere
Secondly is there any way to unlock Bootloader in fastboot?
capricorn85 said:
Hi
I have been playing around with my Atrix HD for quite a while now, installing almost all custom roms out there for MB866 (Found Gummy and Carbon to be the best, batakang and holoblur never worked for me).
Restored back to stock using RSD Lite many times (after editing the xml file, no problems)
The bootloader was of course unlocked during "all that".
Now here is the problem. After restoring to stock 4.1.1 (98.4.20.MB886.ATT.en.US) using RSD Lite, I updated to 98.5.38.MB886.ATT.en.US (small 6.2 MB Update recently released).Worked fine till here.
Then I downgraded to ICS and it also worked fine. What made things worse was when I checked for updates via About Phone--> System Updates and it prompted for an Update 98.4.20.MB886.ATT.en.US (the same i used to flash via RSD). But when the download finished, the phone is permanently stuck in fastboot mode with the following message:
----------------------------------------------
AP Fastboot Flash Mode (s)
10.9B(*) (sha-2e68372, 2012-11-17 23:33:08)
eMMC Info: Size 8GB
Device is LOCKED. Status Code:0
Battery OK
Transfer Mode: USB Connected
downgraded security version
update gpt_main version failed
Failed to hab check for gpt_backup: 0x35
failed to load GPT
CID Read Failure
Invalid CID Status 0x69
No SP Partition found
Fastboot Reason: Invalid GPT
----------------------------------------------
You can see the phone is locked and RSD Lite doesent work at all giving "phone returmed fail" or " invalid partition error (battery is charged atleast 70%).
Any help in restoring the phone to "something" will be highly appreciated.
One of the problem is that i cannot find stock files for the latest 98.5.38.MB886.ATT.en.US update anywhere
Secondly is there any way to unlock Bootloader in fastboot?
Click to expand...
Click to collapse
"fastboot oem fb_mode_clear" should get it to stop booting into fastboot mode
The problem is the gpt partition is security locked and one of the fastboot commands thrown is to lock the phone into fastboot mode for every boot until the flashes are done. The command above is the one used to revert the first one (fastboot oem fb_mode_set if you're curious). Your bootloader isn't, or shouldn't I should say, locked again. The RAZR HD does the same thing if you directly flash a fastboot without removing the bad partitions and commands for unlocked phones flashing non-stock fastboots. The bad ones are the gpt partition and the oem fb* commands....there are a lot of guides that explain this and Mythtools (in AHD Developer forums) will do it all for you.
skeevydude said:
"fastboot oem fb_mode_clear" should get it to stop booting into fastboot mode
The problem is the gpt partition is security locked and one of the fastboot commands thrown is to lock the phone into fastboot mode for every boot until the flashes are done. The command above is the one used to revert the first one (fastboot oem fb_mode_set if you're curious). Your bootloader isn't, or shouldn't I should say, locked again. The RAZR HD does the same thing if you directly flash a fastboot without removing the bad partitions and commands for unlocked phones flashing non-stock fastboots. The bad ones are the gpt partition and the oem fb* commands....there are a lot of guides that explain this and Mythtools (in AHD Developer forums) will do it all for you.
Click to expand...
Click to collapse
fastboot oem fb_mode_clear doesnt work, i tried it before as well, mythtools also cannt help as device status is locked and if rsd cannt flash it i believe myth also cannt.and the reason i say its locked is because it does not respond to any oem command.
it probably got locked after the ota which failed
if i could find fxz for 98.5.38.MB886.ATT.en.US, it may be restored otherwise is there any way around to unlock bootloder from fastboot??
these are the only two options i can think of amoungst which later is has the least probability.......
capricorn85 said:
fastboot oem fb_mode_clear doesnt work, i tried it before as well, mythtools also cannt help as device status is locked and if rsd cannt flash it i believe myth also cannt.and the reason i say its locked is because it does not respond to any oem command.
it probably got locked after the ota which failed
if i could find fxz for 98.5.38.MB886.ATT.en.US, it may be restored otherwise is there any way around to unlock bootloder from fastboot??
these are the only two options i can think of amoungst which later is has the least probability.......
Click to expand...
Click to collapse
There isn't an fxz for that update yet. The one I would be able to make wouldn't include the correct gpt partition because I've flashed the Nextel fxz and none of the other gpt partitions from our stock fxz's will flash on my phone (there's a security lock on that partition). Though I know that between two or three of us here on xda, an fxz could be made with all the correct partitions from the update.
If you're positive that you were unlocked then just flash the Bell or Nextel 4.1.2 fxz's. They're not vulnerable to the heartbleed exploit which is the main reason that AT&T released the 98.5 update to begin with.
Have you tried "fastboot continue"? You might get lucky and the phone will at least boot up. And tried booting to recovery? Boot menu?
You can only unlock the bootloader from a rooted, running phone with ADB enabled. Can't do it in recovery or fastboot mode (unless you have a developer edition).
skeevydude said:
There isn't an fxz for that update yet. The one I would be able to make wouldn't include the correct gpt partition because I've flashed the Nextel fxz and none of the other gpt partitions from our stock fxz's will flash on my phone (there's a security lock on that partition). Though I know that between two or three of us here on xda, an fxz could be made with all the correct partitions from the update.
If you're positive that you were unlocked then just flash the Bell or Nextel 4.1.2 fxz's. They're not vulnerable to the heartbleed exploit which is the main reason that AT&T released the 98.5 update to begin with.
Have you tried "fastboot continue"? You might get lucky and the phone will at least boot up. And tried booting to recovery? Boot menu?
You can only unlock the bootloader from a rooted, running phone with ADB enabled. Can't do it in recovery or fastboot mode (unless you have a developer edition).
Click to expand...
Click to collapse
i tried bell's 4.1.2 earlier thinking the same as you said,but didnt work either, wont boot to recovery or boot menu.....
fastboot continue also takes to the old prompt...
capricorn85 said:
i tried bell's 4.1.2 earlier thinking the same as you said,but didnt work either, wont boot to recovery or boot menu.....
fastboot continue also takes to the old prompt...
Click to expand...
Click to collapse
IIRC, the Nextel (Mex Retail) is the highest version we have unless the new AT&T one supersedes it.
I've only seen this issue one other time over at the RAZR HD forums. With the latest KK OTA they had, his failed and the phone booted to a similar screen you have. Nothing has worked for that guy yet that I'm aware of (haven't checked in about a week now).
Have you tried manually flashing an fxz, not with RSD or Myth (though Myth does flash manually via a script but it skips the gpt partition, IIRC). I'd start with the ATT fxz and if it fails manually then I'd flash the Nextel one...after that I'm out of ideas.
skeevydude said:
IIRC, the Nextel (Mex Retail) is the highest version we have unless the new AT&T one supersedes it.
I've only seen this issue one other time over at the RAZR HD forums. With the latest KK OTA they had, his failed and the phone booted to a similar screen you have. Nothing has worked for that guy yet that I'm aware of (haven't checked in about a week now).
Have you tried manually flashing an fxz, not with RSD or Myth (though Myth does flash manually via a script but it skips the gpt partition, IIRC). I'd start with the ATT fxz and if it fails manually then I'd flash the Nextel one...after that I'm out of ideas.
Click to expand...
Click to collapse
Came here after trying all that
Tried manually flashing but the phone returns FAIL on EVERY command, same with myth tools it executes but nothing really happen in the phone, dont know what went so wrong with the OTA
i am just confused if i should let it be or keep trying until i find a solution
COuld battery charge level be the problem, when it all started it was more than 70 percent and i didnt keep it on for long. it says battery ok but dont know whats the exact battery level as fastboot oem battery-status or voltage level are also restricted
Well, it seems that skeevydude told you all I want to say
Solved: Using Nextel (Mex Retail)
Thanks all for your replies
The device is alive now after restoring to Mexican Retail using RSD (editing the xml file and deleting ONLY the two lines having getvar)
Myth Tools never worked, RSD DID!
BTW the mexican retail is much much better than the ATT version because:
It gets rid of the ATT bloatware
SPecially the att address book
Hotspot is working out of the box
its speedier
android version is upgraded (4.1.2 instead of 4.1.1)
provides an option of manually switching to 2g/3g
and much more
thanks skeevydude, nextel was the last option remaining anyway...........and it automatically fixed the gpr issue
capricorn85 said:
Thanks all for your replies
The device is alive now after restoring to Mexican Retail using RSD (editing the xml file and deleting ONLY the two lines having getvar)
Myth Tools never worked, RSD DID!
BTW the mexican retail is much much better than the ATT version because:
It gets rid of the ATT bloatware
SPecially the att address book
Hotspot is working out of the box
its speedier
android version is upgraded (4.1.2 instead of 4.1.1)
provides an option of manually switching to 2g/3g
and much more
thanks skeevydude, nextel was the last option remaining anyway...........and it automatically fixed the gpr issue
Click to expand...
Click to collapse
Isn't it already stated somewhere that if you are going to downgrade or change versions, you need to delete those lines anyways?
palmbeach05 said:
Isn't it already stated somewhere that if you are going to downgrade or change versions, you need to delete those lines anyways?
Click to expand...
Click to collapse
Yes it is, but thats only for upgrade, if downgrading the gpt line also need to be deleted, as i was not downgrading, only those two were required to be deleted which need to be specifically mentioned to avoid confusion
capricorn85 said:
Yes it is, but thats only for upgrade, if downgrading the gpt line also need to be deleted, as i was not downgrading, only those two were required to be deleted which need to be specifically mentioned to avoid confusion
Click to expand...
Click to collapse
I told ya Mex Retail would work....
skeevydude said:
I told ya Mex Retail would work....
Click to expand...
Click to collapse
It is worth a shot for me too!
I have RSDLite and attempted to flash. It gives me error about unknown <getvar>. Deleted those line(s) according to another post I found.
Then everything passes but I am stuck on the Fastboot Flash Mode?
God I will be happy when uncle same gets through with my son so he can help is ole man, lol.
---------- Post added at 06:14 PM ---------- Previous post was at 05:55 PM ----------
PROGRESS! I recalled skeevydude saying to stay alway from front USB ports and moved to back one and I now also have the Mex Retail version working. What a relief.
Now the bearing question is should I move on to another version like carbon or holoblur?
If ok to stay with this version, meaning will NOT get busted out by AT&T by using hotspot?
What do you recommend skeevydude?
Thank you so so so much.
Woody
Mexico Retail link
can someone provide me any link of Mexico Retail stock rom? Please.
ErickST18 said:
can someone provide me any link of Mexico Retail stock rom? Please.
Click to expand...
Click to collapse
http://sbf.droid-developers.org/phone.php?device=7
quasihellfish said:
http://sbf.droid-developers.org/phone.php?device=7
Click to expand...
Click to collapse
Thanks man
Pleas hlep me for alive my set thanks advance
dear i have a working phone MB886 with jellybean 4.1.1 unfortunately i flash the custom ROM of kitkat but set is dead i tired to alive the phone with myth tools rsd lite but no success my phone boot-loader locked i try to unlock the boot loader but nothing please anybody send ma working link of flash file Mexican or any other which are flash with rsd lite easily i am very thankful of that plzzzzzzzzzzz customer on my neck sorry for my bad English
shamshadhashmi said:
dear i have a working phone MB886 with jellybean 4.1.1 unfortunately i flash the custom ROM of kitkat but set is dead i tired to alive the phone with myth tools rsd lite but no success my phone boot-loader locked i try to unlock the boot loader but nothing please anybody send ma working link of flash file Mexican or any other which are flash with rsd lite easily i am very thankful of that plzzzzzzzzzzz customer on my neck sorry for my bad English
Click to expand...
Click to collapse
Please stop whining and being pathetic and actually search for moto sbf files. A new site popped up and comes up very easily. No need to make us die of laughter at someone begging for an sbf like a guy begging to get with a girl b/c he's thirsty. Smh lol
Sent from my ATRIX HD using XDA Free mobile app
need working link of file
i search everywhere but no file found i need file if anybody have so please share with me or upload thanks
quasihellfish said:
http://sbf.droid-developers.org/phone.php?device=7
Click to expand...
Click to collapse
Need 4.1.1..where can I find it? Tyvm
I'm not entirely sure how to troubleshoot this problem, but here goes...
I was charging my phone and it just attempted to reboot itself. I saw it in the corner of my eye and figured "oh well, let it finish". It never finished, and it seems it won't get past the boot screen.
I entered Fastboot mode. Device is still locked. It also states that the charger is connected, regardless of whether it is or isn't. Additionally, I cannot access Recovery or Factory, instead receiving the following error:
No valid PIV block in SP for system
piv validation failed (system)
Boot up failed
Click to expand...
Click to collapse
Anyone know what's going on here? Did my phone really just brick itself?
Edit: I apologize if my first post goes against any of the rules here. I've searched for a similar thread, but mostly found cases in which people failed to root and are receiving this message. I have some minor experience with rooting a Motorola Droid, Verizon Droid Incredible 2 and a Nexus 10. I was hoping to do the same with this phone, but it came with 4.4.2 already installed.
Don't take my word for it, but if you Google no valid piv moto x....it doesn't look good.
Then again if you read through some of the stuff you find, even other phones with issue....perhaps you'll stumble on a fix.
Last moto x thread I read with that error was solved by a replacement unfortunately.
Hope you find a fix, or can send it in. Your warranty should be in tact if its locked and unrooted.
As kj mentioned, seek a replacement under warranty. If you are really looking to fix yourself. Unlock the bootloader and flash the latest stock ROM via fastboot.
I'd only try that if you can't get a warranty replacement cause unlocking the boot loader will kill your warranty unless you have a Dev edition
SymbioticGenius said:
As kj mentioned, seek a replacement under warranty. If you are really looking to fix yourself. Unlock the bootloader and flash the latest stock ROM via fastboot.
I'd only try that if you can't get a warranty replacement cause unlocking the boot loader will kill your warranty unless you have a Dev edition
Click to expand...
Click to collapse
He doesn't need to unlock his bootloader to try to fastboot flash the lastest stock rom...
The Stock rom will flash just fine even locked because it's signed with release keys.
Try it!
samwathegreat said:
He doesn't need to unlock his bootloader to try to fastboot flash the lastest stock rom...
The Stock rom will flash just fine even locked because it's signed with release keys.
Try it!
Click to expand...
Click to collapse
Thanks! I was hesitant to flash anything on this phone because I read people who had 4.4.2 were at risk of bricking their phones... but now that you've said it, it feels so obvious. I'll give this a try. Is there a standard go-to place for the stock ROM?
ed0421 said:
Thanks! I was hesitant to flash anything on this phone because I read people who had 4.4.2 were at risk of bricking their phones... but now that you've said it, it feels so obvious. I'll give this a try. Is there a standard go-to place for the stock ROM?
Click to expand...
Click to collapse
You can find the sbf files (stock rom) here: http://sbf.droid-developers.org/phone.php?device=0
If you were on 4.4.2 before you bricked MAKE SURE you flash the 4.4.2 rom, and not a previous version.
Also remember that aside from a BL unlock, there will be no way of obtaining ROOT after this.
Download the correct file for your carrier and try to flash with RSD lite. Let us know what happens.
EDIT:
You can find a great guide here: http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
Now that guide was made before 4.4.2 so it doesn't warn you not to flash a previous version. You've been warned... If you flash a pre-4.4.2 rom, you'll likely be perma-bricked.
Anyways, try the RSD Lite method. PAY CLOSE ATTENTION TO STEP 4 - editing the xml file
If for some reason that doesn't work, let us know what carrier you are on and we can help you with manual flashing commands for your specific carrier.
Since you ARE able to get into fastboot mode, I'm hopeful that this may work for you.
And finally, if you have problems with RSD lite, make SURE you have the USB drivers installed, and try another USB port if necessary.
Good Luck.
samwathegreat said:
You can find the sbf files (stock rom) here: http://sbf.droid-developers.org/phone.php?device=0
If you were on 4.4.2 before you bricked MAKE SURE you flash the 4.4.2 rom, and not a previous version.
Also remember that aside from a BL unlock, there will be no way of obtaining ROOT after this.
Download the correct file for your carrier and try to flash with RSD lite. Let us know what happens.
EDIT:
You can find a great guide here: http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
Now that guide was made before 4.4.2 so it doesn't warn you not to flash a previous version. You've been warned... If you flash a pre-4.4.2 rom, you'll likely be perma-bricked.
Anyways, try the RSD Lite method. PAY CLOSE ATTENTION TO STEP 4 - editing the xml file
If for some reason that doesn't work, let us know what carrier you are on and we can help you with manual flashing commands for your specific carrier.
Since you ARE able to get into fastboot mode, I'm hopeful that this may work for you.
And finally, if you have problems with RSD lite, make SURE you have the USB drivers installed, and try another USB port if necessary.
Good Luck.
Click to expand...
Click to collapse
Hey, thanks for the effort! Unfortunately, it looks like my phone is completely bricked. I tried with RSD Lite, after making sure to edit the XML, and it failed when trying to flash the first file. "Failed flashing process. 2/17 flash parition "gpt.bin" -> Phone returned FAIL."
Figured I'd try with fastboot, and no luck there either.
Code:
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 1.978s
Looks like I'm gonna have to use my warranty. Thanks for taking the time to reply, though!
I didn't have the same issue but I did just RMA my X for another reason and got a brand new 2014 X, was expecting a refurbished phone and was surprised to get a new one. They shipped it next day air that same day which also surprised me.
ed0421 said:
Hey, thanks for the effort! Unfortunately, it looks like my phone is completely bricked. I tried with RSD Lite, after making sure to edit the XML, and it failed when trying to flash the first file. "Failed flashing process. 2/17 flash parition "gpt.bin" -> Phone returned FAIL."
Figured I'd try with fastboot, and no luck there either.
Code:
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 1.978s
Looks like I'm gonna have to use my warranty. Thanks for taking the time to reply, though!
Click to expand...
Click to collapse
Usually (not always) when it errors out on gpt.bin, its because you're trying to flash a pre-4.4.2 image.
Hate to ask, but are you absolutely sure you downloaded the 4.4.2 rom?
And when you tried the manual method....you are executing the commands one at a time, right? Which part does it fail on? Flashing recovery? Because I see an error right above it - something about failed to erase....but erase what?
Good luck with your exchange if you must send it back...
-samwathegreat
samwathegreat said:
Usually (not always) when it errors out on gpt.bin, its because you're trying to flash a pre-4.4.2 image.
Hate to ask, but are you absolutely sure you downloaded the 4.4.2 rom?
And when you tried the manual method....you are executing the commands one at a time, right? Which part does it fail on? Flashing recovery? Because I see an error right above it - something about failed to erase....but erase what?
Good luck with your exchange if you must send it back...
-samwathegreat
Click to expand...
Click to collapse
100% certain I downloaded the 4.4.2 rom, unfortunately. Flashing manually, it fails from the very first flash attempt. Only setting the oem fb_mode_set goes through without failure. Thanks for your help throughout this whole ordeal, it's very much appreciated
ed0421 said:
100% certain I downloaded the 4.4.2 rom, unfortunately. Flashing manually, it fails from the very first flash attempt. Only setting the oem fb_mode_set goes through without failure. Thanks for your help throughout this whole ordeal, it's very much appreciated
Click to expand...
Click to collapse
Really dumb question but when flashing... Are you using the command fastboot or mfastboot?
I had all kinds of errors and thought I was bricked too until I used mfastboot. Then everything went perfect. Moto uses their own version of fastboot.exe that's included in the sbf/fxz or whatever they are called now. Even the XML file states fastboot as the command but never worked for me. Just a thought.
Problem SOLVED! Android 5.1 stock ROM revived it! Thank you, Motorola and XDA!
Sorry, not sure if it's proper to repeat my cry here. But I'm having a quite similar situation to this post: [SOLVED]Bootloader bricked, recovered, but fail when running firmware
Mine is a XT1058 from CA Rogers. I unlocked the bootloader and played with Brazil stock roms, a CM11 snapshot rom, having no problems.
After I tried RETAIL-GB_GHOST_KLA20.16-2.16_cid7_CFC_1FF_v2.xml (4.4.2, i guess), things went wrong. No signal as I expected, but I screwed up with OTA 4.4.4 installed so I got the same stuck at Fastboot mode:
Code:
BL version: 30.B7
Device is LOCKED.
downgraded security version
update gpt_main version failded
Failed to hab check for gpt_backup: 0x35
CID Read Failure
Invalid CID Status 0x69
CustomerID error. Contact Dealer: 0xdead
No SP Partition found
Fastboot Reason: Invalid CID
I've tried mflash and RSD with 4.4.4 stock roms, but none of them worked, and all failed to write into the phone at Step 2 <step operation="flash" partition="partition" filename="gpt.bin":
XT1058_RCI-CA_4.4.4_KXA21.12-L1.26_59_cid14_CFC_1FF
XT1052_RETAIL-GB_4.4.4_KXA21.12-L1.26_56_cid7_CFC_1FF
XT1052_RETAIL-EU_4.4.4_KXA21.12-L1.26_54_cid7_CFC_1FF
ATT_XT1058_4.4.4-KXA21.12-L1.26_CFC_1FF
Editing XML to skip the step with error didn't work. It failed to flash at every step. Any help will be appreciated!
Try and flash tz and gpt from 4.4.4
mk1129 said:
Sorry, not sure if it's proper to repeat my cry here. But I'm having a quite similar situation to this post: [SOLVED]Bootloader bricked, recovered, but fail when running firmware
Mine is a XT1058 from CA Rogers. I unlocked the bootloader and played with Brazil stock roms, a CM11 snapshot rom, having no problems.
After I tried RETAIL-GB_GHOST_KLA20.16-2.16_cid7_CFC_1FF_v2.xml (4.4.2, i guess), things went wrong. No signal as I expected, but I screwed up with OTA 4.4.4 installed so I got the same stuck at Fastboot mode:
Code:
BL version: 30.B7
Device is LOCKED.
downgraded security version
update gpt_main version failded
Failed to hab check for gpt_backup: 0x35
CID Read Failure
Invalid CID Status 0x69
CustomerID error. Contact Dealer: 0xdead
No SP Partition found
Fastboot Reason: Invalid CID
I've tried mflash and RSD with 4.4.4 stock roms, but none of them worked, and all failed to write into the phone at Step 2 <step operation="flash" partition="partition" filename="gpt.bin":
XT1058_RCI-CA_4.4.4_KXA21.12-L1.26_59_cid14_CFC_1FF
XT1052_RETAIL-GB_4.4.4_KXA21.12-L1.26_56_cid7_CFC_1FF
XT1052_RETAIL-EU_4.4.4_KXA21.12-L1.26_54_cid7_CFC_1FF
ATT_XT1058_4.4.4-KXA21.12-L1.26_CFC_1FF
Editing XML to skip the step with error didn't work. It failed to flash at every step. Any help will be appreciated!
Click to expand...
Click to collapse
Long story short, and if you read that entire thread, and its progression you'll understand the long story, Right now, it would appear the GPT.BIN on your phone is NEWER than the GPT.BIN in any SBF you are trying to flash. Hence your problem.
You will likely have to wait until a newer SBF gets leaked. At this point, it might be after Lollipop SBF's start leaking.
hbenz2008 said:
Try and flash tz and gpt from 4.4.4
Click to expand...
Click to collapse
I tried several 4.4.4 stock ROMs, but no luck at the very beginning on gpt. What's tz, BTW?
Thank you anyway.
KidJoe said:
Long story short, and if you read that entire thread, and its progression you'll understand the long story, Right now, it would appear the GPT.BIN on your phone is NEWER than the GPT.BIN in any SBF you are trying to flash. Hence your problem.
You will likely have to wait until a newer SBF gets leaked. At this point, it might be after Lollipop SBF's start leaking.
Click to expand...
Click to collapse
I guess so... I even want to flash the Moto X 2014 Lollipop stock ROM. But I should be patient wait for my last hope, then.
Thank you!
hbenz2008 said:
Try and flash tz and gpt from 4.4.4
Click to expand...
Click to collapse
It's weird that my reply to your PM cannot be found in my Sent items box and hope you may get my response.
KidJoe said:
Long story short, and if you read that entire thread, and its progression you'll understand the long story, Right now, it would appear the GPT.BIN on your phone is NEWER than the GPT.BIN in any SBF you are trying to flash. Hence your problem.
You will likely have to wait until a newer SBF gets leaked. At this point, it might be after Lollipop SBF's start leaking.
Click to expand...
Click to collapse
How about only flashing the bootloader and partition from RETCA_XT1097_5.0.1_LXE22.46-22_cid14_CFC.xml.zip? Maybe that's crazy
yeah i wouldnt phuk with her like that, prob is gpt
mk1129 said:
I guess so... I even want to flash the Moto X 2014 Lollipop stock ROM. But I should be patient wait for my last hope, then.
Thank you!
Click to expand...
Click to collapse
mk1129 said:
How about only flashing the bootloader and partition from RETCA_XT1097_5.0.1_LXE22.46-22_cid14_CFC.xml.zip? Maybe that's crazy
Click to expand...
Click to collapse
THe 2013 and 2014 X do not use the same parts. I would NOT flash any components of the 2014 X on the 2013 X.
KidJoe said:
THe 2013 and 2014 X do not use the same parts. I would NOT flash any components of the 2014 X on the 2013 X.
Click to expand...
Click to collapse
Agree. I'd wait for the Lollipop SBF, then. Thanks!
I suddenly realized that I encrypted the phone when it's on 4.4.2 before playing with various SBFs, and that may be the reason why I cannot write anything any more....
I had the exact same problem with my XT1053. I was able to fix it by flashing the 5.0.2 GPT. If your variant has a leaked zip, it's in the root directory. I wouldn't recommend using anything but your own variant's, but if that's what you want to do so be it.
thehanutedtubby said:
I had the exact same problem with my XT1053. I was able to fix it by flashing the 5.0.2 GPT. If your variant has a leaked zip, it's in the root directory. I wouldn't recommend using anything but your own variant's, but if that's what you want to do so be it.
Click to expand...
Click to collapse
Thanks for the tips! You''re lucky! BTW, Where did you get the 5.02 GPT? from Brazil XT1058 soak test leak?
And yes, I'm really expecting the full lollipop stock rom to have a final try to save mine. I only heard Brazil XT1058 has the soak test for 5.02 and am wondering if I can leverage that...
Problem SOLVED! Android 5.1 stock ROM (XT1058_GHOST_RCICA_5.1_LPA23.12-15_cid14_CFC_xml) revived it!
Thank you, Motorola and XDA!