Related
Good Morning
First please forgive my english if i make some mistakes...
Here is my problem :
i have a RAZR I, I flashed it into a new brazilian rom, , that worked perfectly.http://sbf.droid-developers.org/smi....0R_SCPNMINIIRETBRLA_P024_A031_CFC_fb.xml.zip
... but i cant root with motofailgo.... I tried severy times... then...
I want to back to older version and i give this error in fastboot during the flashing:
i had this failure message :
update gpt_main version failed
preflash validation failed for GPT
When i try to turn it off or on... it doesn't move...
Again I can flash only new version and work perfect...
any ideas to help me fix this !!!
Thanks for taking time to read me and help.!!! :crying:
Hello, if you read this forum, and search a little,you will found that:
-The latest rom are not rootable without unlock the bootloader (i imagine that you have not do it...)
-You could not downgrade a rom.
I imagine that your rom is one of the latest rom?
So if you wan t to root a latest rom, you have to unlock the bootloader and read the post. And you could not roll back to an oldest version.
Burn02 said:
Hello, if you read this forum, and search a little,you will found that:
-The latest rom are not rootable without unlock the bootloader (i imagine that you have not do it...)
-You could not downgrade a rom.
I imagine that your rom is one of the latest rom?
So if you wan t to root a latest rom, you have to unlock the bootloader and read the post. And you could not roll back to an oldest version.
Click to expand...
Click to collapse
Yep is the lastest. I cant back anymore?
I did it when I installing this rom during the flash:
" Unknown fastboot command. (getvar)" I give an error than I removed this line: <step operation="getvar" var="max-download-size" />.
and work perfect but i cant back for old rom. I need root by motofail. :crying: There any problem in future upgrades by OTA?
Thx...
Normally you could not downgrade. but you could flash any rom that are in the same version. So there is no reason that it would be a problem for a future ota update.
As i know and read on xda, there is no other possibility to root on the latest rom, to unlock the bootloader.
Hello,
It had the original rom 4.4 on my XT1058 with root and unlocked bootloader, but was not getting running with 4.4.2 update for the original recovery. So I was going to be able to update and run fasthall.bat back to 4.2.2, but I opened the file and rebooted the machine to backup and forgot that it was open. Result: ****ed me.
I believe I have lost my bootloader, but following the tutorial of Gundabolu SC, unable to enter fastboot again, however, I can not run the sbf or RSD by flashall.bat.
I noticed that my phone with this LOCKED status, though I unlocked it.
To start the fastboot I run the code the tutorial I mentioned above, then it displays the following screen
Code:
[COLOR="Red"]Failed to hab check for gpt_main: 0x4e
CID Read Failure
Invalid CID Status 0x69
CustomerID error. Contact Dealer: 0xdead
No SP Partition found[/COLOR]
[COLOR="DarkOrange"]Fastboot Reason: Invalid CID[/COLOR]
For both methods to recovery, it becomes part of gpt.bin and when arrives at motoboot, of the following error message:
Code:
[COLOR="DarkOrange"]getvar max-download-size
downloading 32768 bytes
done
getvar max-download-size
downloading 1643008 bytes[/COLOR]
[COLOR="Red"]downgraded security version
update aboot version failed[/COLOR]
Can anyone help me?
------------
Problem solved thanks to XDA's amazing users!
feelknOck said:
Hello,
It had the original rom 4.4 on my XT1058 with root and unlocked bootloader, but was not getting running with 4.4.2 update for the original recovery. So I was going to be able to update and run fasthall.bat back to 4.2.2, but I opened the file and rebooted the machine to backup and forgot that it was open. Result: ****ed me.
I believe I have lost my bootloader, but following the tutorial of Gundabolu SC, unable to enter fastboot again, however, I can not run the sbf or RSD by flashall.bat.
For both methods, it becomes part of gpt.bin and when arrives at motoboot, of the following error message:
Code:
downgraded security version
aboot version update failed
Can anyone help me?
Click to expand...
Click to collapse
You can try go to this link Hope it helps
http://forums.androidcentral.com/mo...7371-unroot-unbrick-your-phone-using-sbf.html
---------- Post added at 04:31 PM ---------- Previous post was at 04:18 PM ----------
Did it worked??S i am too not quite sure about this??
manav113 said:
You can try go to this link Hope it helps
http://forums.androidcentral.com/mo...7371-unroot-unbrick-your-phone-using-sbf.html
Click to expand...
Click to collapse
I tried to recover via RSD several times, both with 4.4, as 4.2.2, but both have the same error.
In the RSD panel the following error message:
Code:
Failed flash process. 2/13 flash mootboot "motoboot.img" -> Phone returned FAIL.
quite a different error.NEVER heard of it>Wait let me ask my friends about it..
manav113 said:
quite a different error.NEVER heard of it>Wait let me ask my friends about it..
Click to expand...
Click to collapse
the issue is the bootloader you are trying to install dose not match the one installed so it will fail everytime we have to find the right one to get everything installed correct
so we need to grab the 100% correct firmware package for your phone.
the model you gave me is for the AT&T version
here is the 4.4 AT&T firmware try installing this one
http://sbf.droid-developers.org/download.php?device=0&file=4
let me know the outcome.
dray_jr said:
the issue is the bootloader you are trying to install dose not match the one installed so it will fail everytime we have to find the right one to get everything installed correct
so we need to grab the 100% correct firmware package for your phone.
the model you gave me is for the AT&T version
here is the 4.4 AT&T firmware try installing this one
http://sbf.droid-developers.org/download.php?device=0&file=4
let me know the outcome.
Click to expand...
Click to collapse
I'm downloading and post the result. 202 KB/s
Thank you!
-
dray_jr said:
the issue is the bootloader you are trying to install dose not match the one installed so it will fail everytime we have to find the right one to get everything installed correct
so we need to grab the 100% correct firmware package for your phone.
the model you gave me is for the AT&T version
here is the 4.4 AT&T firmware try installing this one
http://sbf.droid-developers.org/download.php?device=0&file=4
let me know the outcome.
Click to expand...
Click to collapse
Sorry for double post there.
I remember that my device is the XT1058, but Brazil.
I downloaded the sbf, removed the max-download-size and run the RSD, but he brought me the same errors.
Sounds like you need to wait for the full 4.4.2 Brazil image to be posted for download to recover the phone.
Steve-x said:
Sounds like you need to wait for the full 4.4.2 Brazil image to be posted for download to recover the phone.
Click to expand...
Click to collapse
Excuse me, but why do you think?
I did not get to install 4.4.2, I started to run the script flashall.bat 4.2.2 and thinking it would give time, it ended up damaging the bootloader.
Tried the firm indicated that dray_jr and 2 BR's, but it did not work.
I am very worried.
Did you try this, sounds like your trying to flash 4.2.2 firmware over 4.4.2 which won't work http://forum.xda-developers.com/showthread.php?t=2628940
Sent on my Gummy running Lenoto X
Do you get the "downgraded security version" error when trying to flash 4.2.2 and 4.4 ?
flashallthetime said:
Did you try this, sounds like your trying to flash 4.2.2 firmware over 4.4.2 which won't work http://forum.xda-developers.com/showthread.php?t=2628940
Sent on my Gummy running Lenoto X
Click to expand...
Click to collapse
I was going to try and probably would work (I've done this several times and has no secret), but it was not to start. I opened flashall.bat script but forgot to close it, because it was going back up yet, but the script detected the fastboot and started the process.
With seconds I removed the cable, barely gave it to start the first stage (before I left without turning back) and corrupted my bootloader.
I had the Original ROM 4.4 installed with root and unlocked bootloader, but even trying the 4.4 firmware I get the errors I described above.
Would have something to do with the tutorial I follow to start the fastboot?
I am Brazilian and even translating and reading what little I understand, I can not identify a problem as well. I'm scouring all here and trying something, but like I said, I am a layman and do not understand how the bootloader and related work.
Steve-x said:
Do you get the "downgraded security version" error when trying to flash 4.2.2 and 4.4 ?
Click to expand...
Click to collapse
With 2 firmwares I get the same error.
everytime i post here i reread the first thread and i am still not sure what you did.
so im going to ask some questions and see if we can't get some more info on this issue
1. Your device was 4.4 unlocked bootloader and rooted
2. did you try and install the 4.4.2 firmware
3. your device is the AT&T model but from Brazil
because if you are getting the gpt error on both 4.2.2 and 4.4 and it would lead me to think that the 4.4.2 bootloader is installed on your device.
dray_jr said:
everytime i post here i reread the first thread and i am still not sure what you did.
so im going to ask some questions and see if we can't get some more info on this issue
1. Your device was 4.4 unlocked bootloader and rooted
2. did you try and install the 4.4.2 firmware
3. your device is the AT&T model but from Brazil
because if you are getting the gpt error on both 4.2.2 and 4.4 and it would lead me to think that the 4.4.2 bootloader is installed on your device.
Click to expand...
Click to collapse
He removed the cable as it was flashing, can you get to the fastboot screen?
Sent on my Gummy running Lenoto X
dray_jr said:
everytime i post here i reread the first thread and i am still not sure what you did.
so im going to ask some questions and see if we can't get some more info on this issue
1. Your device was 4.4 unlocked bootloader and rooted
2. did you try and install the 4.4.2 firmware
3. your device is the AT&T model but from Brazil
because if you are getting the gpt error on both 4.2.2 and 4.4 and it would lead me to think that the 4.4.2 bootloader is installed on your device.
Click to expand...
Click to collapse
1. Yes, I was running 4.4 with unlocked bootloader and rooted
2. I installed the original recovery to try the OTA update for version 4.4.2, but he returned me error halfway through the update, because my ROM was modified. That's when I thought of going back to 4.2.2 without changes and run the 4.4.2.
3. My device is the XT1058 Retail Brazil.
flashallthetime said:
He removed the cable as it was flashing, can you get to the fastboot screen?
Click to expand...
Click to collapse
Yes, I can start the fastboot via script "qflash.exe with (PORT NUMBER)-ramload MPRG8960.hex-mbn 33 MSM8960_bootloader_singleimage.bin-v-o" with a blank bootloader.
feelknOck said:
1. Yes, I was running 4.4 and unlocked bootloader routed.
2. I installed the original recovery to try the OTA update for version 4.4.2, but he returned me error halfway through the update, because my ROM was modified. That's when I thought of going back to 4.2.2 without changes and run the 4.4.2.
3. My device is the XT1058 Retail Brazil.
Yes, I can start the fastboot via script "qflash.exe with (PORT NUMBER)-ramload MPRG8960.hex-mbn 33 MSM8960_bootloader_singleimage.bin-v-o" with a blank bootloader.
Click to expand...
Click to collapse
ok if i remember well first flash recovery from 4.4 firmware
mfastboot flash recovery recovery.img
after then u ll be able to flash entire image of 4.4.2
could it be that even thou the 4.4.2 update failed that it still installed the new bootloader and that is why nothing else will install.
but either way he could flash the 4.4 firmware without the gpt file and then take the OTA and everything should be fine.
danger2u said:
ok if i remember well first flash recovery from 4.4 firmware
mfastboot flash recovery recovery.img
after then u ll be able to flash entire image of 4.4.2
Click to expand...
Click to collapse
Before having this problem I tried all that.
I installed the original recovery and tried to upgrade to 4.4.2 but it gave error in the middle of the update and restarted the phone saying that the software update was not completed.
dray_jr said:
could it be that even thou the 4.4.2 update failed that it still installed the new bootloader and that is why nothing else will install.
but either way he could flash the 4.4 firmware without the gpt file and then take the OTA and everything should be fine.
Click to expand...
Click to collapse
I will remove the line from gpt and try again.
Earlier I was testing at work and now I'm home. The 4.4 firmware download this lingering: (
you really can't cause anymore problems so this is what i would try because from what i have read if you try to install 4.2.2 or 4.4 you the a gpt.bin verification error. which means that neither 4.2.2 or 4.4 are the right bootloader.
That leaves us with some how the 4.4.2 bootloader got installed because it is the only bootloader that can't go to 4.4 so with that being said.
I would download the correct 4.4 firmware for your phone.
extract it
and use the below adb commands to install it but leave out the gpt.bin flash command
Code:
*leave this one out*fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot reboot
i think everything should install fine and your phone should boot up and from what i have read you should still be able to take the 4.4.2 OTA without bricking your phone
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.
Help me regarding going back to4.4.3... I have the package and everything ( rsd lite stuff) but boot loader seems updated while i did ota to 4.4.4 .. its keep saying downgraded security pre flash vvalidation error while flashing 4.4.3.
4.4.3 was silky smooth. 4.4.4 is stuttery horrible in many apps and also generally to some extent
Theoretically this should be possible right to install old boot loader and then fash 4.4.3??
How and where to get boot loader old one.??.. I mean this is the thing they do in factories no?? Before flashing a firmware...
That would remove security downgrade verification right??
Reason is 4.4.4 is horribly stuttering Feels like a cheap china mobile
Search this forum for "downgrade brick" and see what others have had happen.
Long story short: just. don't. do it.
Problem. Is while doing an it's update after downgrading . which causes different kernel and system IMG to cause problems they say.
Still wonder why no one is into what causes the security check , how to get an old boot loader into the phone ... Wat they do I manufacturing? No phone comes with any software.. They are uploaded into it after emptiness. .. So why not 4.4.3 now .. if its the bootloader that causes problems why can't we install a boot loader that will match 4.4.3 ?? ...
All the forum is full f bricked moto x when there was no 4.4.4 firmware available. Nowthey are available.. So its not much problem now as it used to be.
Pls some one look into it... No one curious enough to decode the way?? I mean is this acceptable ? That we can't match 4.4.3 in a moto x ..
4.4.4 stuttering? User error
The moto x is not a nexus device. Unlike gaining S-off on an HTC phone, unlocking the bootloader on a moto x doesn't disable its security checks.
You can't downgrade got.bin and motoboot.img, or their internal components due to the phone's security checks.
People try downgrade by skipping those, BUT too often people brick when attempting this, or taking an OTA update in this state.
When you have mismatched parts on the phone, things don't work (like the issue of going settings-> security kicking you out) and you are at risk for bricking.
KidJoe said:
The moto x is not a nexus device. Unlike gaining S-off on an HTC phone, unlocking the bootloader on a moto x doesn't disable its security checks.
You can't downgrade got.bin and motoboot.img, or their internal components due to the phone's security checks.
People try downgrade by skipping those, BUT too often people brick when attempting this, or taking an OTA update in this state.
When you have mismatched parts on the phone, things don't work (like the issue of going settings-> security kicking you out) and you are at risk for bricking.
Click to expand...
Click to collapse
The problem is boot.IMG which has the kernel also has the dowbhrade security check error ... So when I falshed 4.4.3 over the 4.4.4 phone , ended up having kernel of 4.4.4 with system of 4.4.3.. ( I had to skip boot.IMG of kernel, motoboot.IMG , and got.bin)
Kernel is where interface comes...
Is there a way to flash the boot.IMG of 4.4.3 ... I would be satisfied with that... No need got.bin and motoboot.IMG flashing...
Also when I see this forum no one mention boot.IMG only motoboot and got.bin are mentioned.. Am I the only one having prob with boot.IMG flashingflashing.. If so pls tell kidjoe, iwould be happy
And AM NOT OTA OR MANUALLY UPDATIG TO LOLLIPOP IF I HAVE 4.4.3...
I HAVE OTA UPDATED 4.4.4 after having 4.4.3 system and 4.4.4 kernel .. To attain full 4.4.4 and it doesn't cause brickig .
Brickin occurs only when u update to next release it seems. 4.4.4 update is easy with the device it seems
nhizzat said:
4.4.4 stuttering? User error
Click to expand...
Click to collapse
Pls help me .. Wats user error.. I mean wat u mean by my error??
govardhan87 said:
Pls help me .. Wats user error.. I mean wat u mean by my error??
Click to expand...
Click to collapse
Most likely something you've modified or installed is causing the stuttering.
govardhan87 said:
The problem is boot.IMG which has the kernel also has the dowbhrade security check error ... So when I falshed 4.4.3 over the 4.4.4 phone , ended up having kernel of 4.4.4 with system of 4.4.3.. ( I had to skip boot.IMG of kernel, motoboot.IMG , and got.bin)
Kernel is where interface comes...
Is there a way to flash the boot.IMG of 4.4.3 ... I would be satisfied with that... No need got.bin and motoboot.IMG flashing...
Also when I see this forum no one mention boot.IMG only motoboot and got.bin are mentioned.. Am I the only one having prob with boot.IMG flashingflashing.. If so pls tell kidjoe, iwould be happy
And AM NOT OTA OR MANUALLY UPDATIG TO LOLLIPOP IF I HAVE 4.4.3...
I HAVE OTA UPDATED 4.4.4 after having 4.4.3 system and 4.4.4 kernel .. To attain full 4.4.4 and it doesn't cause brickig .
Brickin occurs only when u update to next release it seems. 4.4.4 update is easy with the device it seems
Click to expand...
Click to collapse
Most reference only GPT.BIN and MOTOBOOT.IMG because they are the partition table, bootloader, trusted zone, etc. Those two fail with an error that stops RSDlite, and those two error when trying to flash older versions via mFastboot. After getting those errors, that is usually when people start posting their phone is bricked and asking for help.
I've seen some downgrade everything but those two (meaning, yes they did even flash boot.img) using mfastboot (latest being from the 4.4.2 and 4.4.4 dev edition roms). But again, if you get forgetful and take an OTA, or sell it to someone in that state, you could cause a brick later.
You could be able to downgrade parts without bricking, we've seen that happen... In addition, like when people on 4.4.2 downgraded this way to 4.4, we saw features not work (I mentioned the security menu earlier) if they managed to not brick.
In some cases, when in the bricked or non-booting state from attempting to downgrade, flashing the full SBF of the newest version (4.4.4) manually via mFastboot with a few extra commands was enough to recover the phone and get it working. (at least check the phone's bootloader version and flash the SBF for that bootloader or a higher/newer SBF version). On some occasions they've bricked bad enough that they've needed to follow -> http://forum.xda-developers.com/moto-x/general/how-to-resurrecting-bricked-moto-x-t2629057 and other times nothing worked and their phone was dead.
That being said, the many many threads asking for help due to phones not booting, being bricked, etc from attempting to downgrade are why we caution people to not downgrade and why you wont get much help doing it. Its not 100% safe or fool proof. If it goes wrong you could have a lot of work on your hands or a non-usable phone. Just because it has worked for you, doesn't mean it works and others can/should try it. We've seen too many times how people have bricked. For example a while ago there was someone claiming its possible to downgrade the XT1052 without issues, it was 100% safe, he did it without failure so it must be safe. Then XT1052 people who tried it started creating threads that their phone was bricked from following his steps asking for help. The thread was closed/locked.
But its your phone, do what you want. If you advise others to downgrade, or claim its safe to downgrade, make sure you include a clear warning that there are risks!!
govardhan87 said:
Help me regarding going back to4.4.3... I have the package and everything ( rsd lite stuff) but boot loader seems updated while i did ota to 4.4.4 .. its keep saying downgraded security pre flash vvalidation error while flashing 4.4.3.
4.4.3 was silky smooth. 4.4.4 is stuttery horrible in many apps and also generally to some extent
Theoretically this should be possible right to install old boot loader and then fash 4.4.3??
How and where to get boot loader old one.??.. I mean this is the thing they do in factories no?? Before flashing a firmware...
That would remove security downgrade verification right??
Reason is 4.4.4 is horribly stuttering Feels like a cheap china mobile
Click to expand...
Click to collapse
You do realize the ONLY change between 4.4.3 and 4.4.4 is the security fix for ssl right. It was less then 16 meg for the update so your issues are NOT related to 4.4.3 vs 44.4 I would look elsewhere for the cause of your issues before you completely brick your phone
adm1jtg said:
You do realize the ONLY change between 4.4.3 and 4.4.4 is the security fix for ssl right. It was less then 16 meg for the update so your issues are NOT related to 4.4.3 vs 44.4 I would look elsewhere for the cause of your issues before you completely brick your phone
Click to expand...
Click to collapse
dear adm1jtg... Am not a developer in android or even a software guy. I will be unable to see these things or verify that its only security update and will not affect kernel of the os- although they said wat u said..
That's y I posted here. Thanks for replying.
Would be happy if u tell if kernel is same in 4.4.3 And 4.4.4. ( if u know)
govardhan87 said:
dear adm1jtg... Am not a developer in android or even a software guy. I will be unable to see these things or verify that its only security update and will not affect kernel of the os- although they said wat u said..
That's y I posted here. Thanks for replying.
Would be happy if u tell if kernel is same in 4.4.3 And 4.4.4. ( if u know)
Click to expand...
Click to collapse
Kernel is not identical but close as far as i know as the security fix was kernel based. Ok that said instead of trying to change your stock rom i would try a custom kenrel. Which one you ask.... I am currently using zwliew. There is a thread for it in the dev area. You could also try a custom stock based rom like krypton or epsilon (also have threads in dev section).
Downgrading really shoudnt EVER be considered for any reason as you have a very good chance or permanently bricking your phone.
Agree with many here...
Even tho some say they've downgraded OK... Let's see how the next ota works out for them. Oops!
So .... Here's my 2 cents on downgrading........ DON'T !
?
Hey everyone, i recently rooted an old xt1064, and tried to put on CM 12.1, but as soon as i tried to install the zip, i got the "This package supports boot loader: 0x4882 ..." error. So i looked on here and found that i need to upgrade my bootloader. I started going along with this guide (https://forum.xda-developers.com/moto-g-2014/general/bootloader-update-t3060007) but i keep getting "preflash validation failed" when i run fastboot flash partition gpt.bin and fastboot flash motoboot motoboot.img. I tried different computers but still no luck. I looked on here, some more, but i am not sure what exactly is the problem. Am i trying to downgrade, because form what i understand 48.82 is supposed to be the newest version. I tried running differnt roms and some loaded other gave the same error. Any help is greatly appreciated , ill keep searching in the meantime.
flizer said:
Hey everyone, i recently rooted an old xt1064, and tried to put on CM 12.1, but as soon as i tried to install the zip, i got the "This package supports boot loader: 0x4882 ..." error. So i looked on here and found that i need to upgrade my bootloader. I started going along with this guide (https://forum.xda-developers.com/moto-g-2014/general/bootloader-update-t3060007) but i keep getting "preflash validation failed" when i run fastboot flash partition gpt.bin and fastboot flash motoboot motoboot.img. I tried different computers but still no luck. I looked on here, some more, but i am not sure what exactly is the problem. Am i trying to downgrade, because form what i understand 48.82 is supposed to be the newest version. I tried running differnt roms and some loaded other gave the same error. Any help is greatly appreciated , ill keep searching in the meantime.
Click to expand...
Click to collapse
same here with an old xt1068 (titan) and 48.87 bootloader... nothing works
suiller said:
same here with an old xt1068 (titan) and 48.87 bootloader... nothing works
Click to expand...
Click to collapse
I actually was able to get this fixed, it was more simple than i expected.
Credit to this post https://forum.xda-developers.com/showpost.php?p=71956639&postcount=864
https://cloud.tapatalk.com/s/58f97f6fd91d0/Screenshot_20170421-090824.png
It's been a while but ill try to go off of my memory. You have to find the updater-script file in the cm12.1 file and edit it. you need to add the line
getprop("ro.bootloader") == "0x4887" ||
look at the image in the link and make sure it similar. This makes cm12.1 ok with installing on 48.87
neither that worked... it seems that bootloader prevent writing/flashing even if it doesn't give errors
suiller said:
neither that worked... it seems that bootloader prevent writing/flashing even if it doesn't give errors
Click to expand...
Click to collapse
I have this same problem. Bootloader 48.87 - UK dual SIM XT1068 (bought from Tesco originally when it would have been kitkat) - no matter what firmware I try (and I am using the ones that specify MBM Version: 48.87 in the info.txt files) as soon as I get to using mfastboot to flash the boot.img it fails and everything after that fails (gpt.bin, motoboot.img and logo.bin which are flashed first work OK).
Get various errors which point to wrong firmware - but as I can;t get the phone to boot into anything other than the bootloader I have no way to know what firmware it was - or the phone has a fault anyway (it did just stop working with no idea why - never been flashed or modded).