Related
Hello folks.
I'm on a bit of a limbo. Can you help me?
Fist of all i should state that i was a former Galaxy S3 owner, so even if I have some experience with the underworld of rooting and flashing, bootloader issues are a bit alien for me.
The problem:
My Brazilian Moto X with unlocked bootloader was on 4.4, and after receiving the OTA update, i thought that i could update it if I removed root and etc (after all i was not using Xposed and ETC, so no deep modifications at /system that i know).
Of course i was wrong, and as greeted with a nice bootloop by my moto X. No problem, I got the 4.4.2 UK and flashed it thought RSD lite. After the flashing, I dit not liked the modifications the UK 4.4.2 retail have (like carrier name on bar, etc etc) and just flashed Philz and recovered my nandroid.
All is nice, but now i can't update to 4.4.2 Brazilian because i can't install 4.4 Retail Brazilian trought RSD lite, since the Moto X just detects that it haves 4.4.2 bootloader and not let me downgrade! I'm in a Limbo \o/
What now? There is any way to downgrade the bootloader? There is any one who have a full Brazilian 4.4.2 image (or a image without carrier name on the bar) for unlocked bootloaders? Any 4.4.2 flashable update using CWM or TWRP?
Oh god, so many questions. Thanks for your atention!
brunodmjr said:
Hello folks.
I'm on a bit of a limbo. Can you help me?
Fist of all i should state that i was a former Galaxy S3 owner, so even if I have some experience with the underworld of rooting and flashing, bootloader issues are a bit alien for me.
The problem:
My Brazilian Moto X with unlocked bootloader was on 4.4, and after receiving the OTA update, i thought that i could update it if I removed root and etc (after all i was not using Xposed and ETC, so no deep modifications at /system that i know).
Of course i was wrong, and as greeted with a nice bootloop by my moto X. No problem, I got the 4.4.2 UK and flashed it thought RSD lite. After the flashing, I dit not liked the modifications the UK 4.4.2 retail have (like carrier name on bar, etc etc) and just flashed Philz and recovered my nandroid.
All is nice, but now i can't update to 4.4.2 Brazilian because i can't install 4.4 Retail Brazilian trought RSD lite, since the Moto X just detects that it haves 4.4.2 bootloader and not let me downgrade! I'm in a Limbo \o/
What now? There is any way to downgrade the bootloader? There is any one who have a full Brazilian 4.4.2 image (or a image without carrier name on the bar) for unlocked bootloaders? Any 4.4.2 flashable update using CWM or TWRP?
Oh god, so many questions. Thanks for your atention!
Click to expand...
Click to collapse
you can't downgrade the bootlaoder sorry
as for the carrier name in the bar someone will make a xposed mod to remove it.
i would either stay with 4.4 if that makes you happy or flash the correct 4.4.2 firmware for your device and tweak it to your liking.
Unfortunately you cannot downgrade the bootloader from 4.4.2 to 4.4.
Is it so dificult to do a 4.4.2 flashable update or we just lack devs?
brunodmjr said:
Is it so dificult to do a 4.4.2 flashable update or we just lack devs?
Click to expand...
Click to collapse
If you find the factory 4.4.2 image for your device, then you manually flash the 4.4.2 files.
Mr. Orange 645 said:
If you find the factory 4.4.2 image for your device, then you manually flash the 4.4.2 files.
Click to expand...
Click to collapse
I can only find the UK one. There is no 4.4.2 factory image for Brazilian Moto X, and i really don't want to install Xposed to remove the carrier name from the bar, since i play Square Enix titles.
brunodmjr said:
I can only find the UK one. There is no 4.4.2 factory image for Brazilian Moto X, and i really don't want to install Xposed to remove the carrier name from the bar, since i play Square Enix titles.
Click to expand...
Click to collapse
Well...then you are at an impasse. Sorry.
Mr. Orange 645 said:
Well...then you are at an impasse. Sorry.
Click to expand...
Click to collapse
So bad. Know any way to convert the OTA update to a CWM flashable zip? Any guide or something?
brunodmjr said:
So bad. Know any way to convert the OTA update to a CWM flashable zip? Any guide or something?
Click to expand...
Click to collapse
No. I, like you, depend on the hard work of developers here for that kind of thing.
Mr. Orange 645 said:
No. I, like you, depend on the hard work of developers here for that kind of thing.
Click to expand...
Click to collapse
I'm a dev too. Let's research.
The full image will probably be available in a few days to a week, so you should probably just wait for it since your phone is working.
Boot loaders are number differently that's why everyone who has flash, or just about everyone who has flashed a new firmware has had issue evedn though the firmwares are 4.4.2, morale . Flash only your specific carrier firmware and all this craziness would stop, my 2 cents
Sent on my Lenoto A2109 tablet
flashallthetime said:
Boot loaders are number differently that's why everyone who has flash, or just about everyone who has flashed a new firmware has had issue evedn though the firmwares are 4.4.2, morale . Flash only your specific carrier firmware and all this craziness would stop, my 2 cents
Sent on my Lenoto A2109 tablet
Click to expand...
Click to collapse
It certainly seems Motorola has changed the game with 4.4.2, flashing other carriers firmware at this time seems quite risky. As you said I wouldn't recommend it right now until more is known and all full flash images of 4.4.2 are released.
Steve-x said:
It certainly seems Motorola has changed the game with 4.4.2, flashing other carriers firmware at this time seems quite risky. As you said I wouldn't recommend it right now until more is known and all full flash images of 4.4.2 are released.
Click to expand...
Click to collapse
Someone should start a thread with all info and have it stickied, getting stupid here, miss info, assuming have a unlocked boot loader will prevent hard bricks.
Sent on my Lenoto A2109 tablet
flashallthetime said:
Boot loaders are number differently that's why everyone who has flash, or just about everyone who has flashed a new firmware has had issue evedn though the firmwares are 4.4.2, morale . Flash only your specific carrier firmware and all this craziness would stop, my 2 cents
Sent on my Lenoto A2109 tablet
Click to expand...
Click to collapse
OP's issue was that he wanted to downgrade to 4.2 -- not that he was trying to change the carrier version of the 4.4.2 bootloader. Are there any threads about someone having an issue trying to flash a different carrier's version of 4.4.2?
piccit said:
OP's issue was that he wanted to downgrade to 4.2 -- not that he was trying to change the carrier version of the 4.4.2 bootloader. Are there any threads about someone having an issue trying to flash a different carrier's version of 4.4.2?
Click to expand...
Click to collapse
Threads no but multiple threads about issues, stay away from flashing another carriers 4.4.2 firmware at this point in time, I'm trying to get boot loader numbers for all carrier firmware , so far all north american and south american boot loaders are the same but T-Mobile and AT&T have yet to be released, European boot loaders are not yet posted
Sent on my Lenoto A2109 tablet
Every issue that I've read about is from people trying to downgrade. I haven't seen anyone have an issue about trying to side-grade
piccit said:
Every issue that I've read about is from people trying to downgrade. I haven't seen anyone have an issue about trying to side-grade
Click to expand...
Click to collapse
Boot loaders numbers are different
Sent on my Gummy running Lenoto X
That's the risk of being impatient and flashing things in a hurry when they drop....that weren't made for our particular phone.
Remember ...good things come to those who wait.......and bad things for those who are too impatient.
Sent from my Moto X cellular telephone...
Just find the Brazilian full 4.4.2 file and rsdlite it or mfastboot flash. I believe it was floating around somewhere.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Hi,
I own a Moto X Developer Edition, so a XT1053 device.
After some issue, I decided to return to full stock, 4.4.2, and possibly changing the locale to get a full French support.
I followed the instructions from this thread to return to stock. And instead of choosing the original firmware, I took the French one from this list.
Everything run smoothly without any issue, except one annoying problem for a phone, the radio doesn't work, so no GSM connectivity. The phone says the radio is unactivated.
I think there is a way to "mix" some img files from the original Dev Edition and the FR one to get things working, but I don't know exactly. Any help would be greatly appreciated.
Thanks.
Hi,
Really need some help on this one because as I didn't get any answer, I decided to reflash the official 4.4 firmware to get my radio back. But as the Moto X has been flashed with the French 4.4.2 rom, it refuses to be downgraded to 4.4.
Any idea? Thanks.
Please please please please read up on these things before you end up flashing!
I'm glad I could answer before you ended up hard bricking your phone, your current bootloader is based on the 4.4.2 rom, so it is impossible to downgrade to previous images. If you were stubborn and skipped this information, you would have tried to manually flash the 4.4 image with mfastboot commands and just purposely left out the bootloader, if you did this, then as soon as you got the 4.4.2 OTA to update and accepted it, you would have hard bricked your phone.
Now with all that said, it may be possible to take the NON-HLOS.bin and fsg.mbn from the 4.4 SBF T-Mobile/Dev Edition image and try to flash that radio/modem to your phone. I would make a backup before doing this though. just follow the fastboot commands for the modem and you should be okay. Remember to follow them exactly.
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
I am not entirely sure that you can use the 4.4 modem with a 4.4.2 rom. There may have been some firmware changes that prevent this from working, but you are welcome to try, I would personally wait until a T-Mobile/Dev Ed SBF 4.4.2 image appears and try the same procedure with that instead, but you are welcome to "chance" it
Thanks for the help.
In the meantime, I've read this thread and this one. So, I tried to flash the Rogers Canada 4.4.2 image. Everything runs fine, but still no radio.
But, I currently run the instructions from here to return to stock, and so I didn't know I had to flash NON-HLOS.bin file. I'm going to try this right now.
Thanks again.
Just tried to flash the NON-HLOS.bin file by following your instructions. Tried with both Rogers Canada sbf and with the Official 4.4 image. Same, no radio.
Wait for the official Developer Edition 4.4.2 or I'll contact Motorola. Does somebody know if an there is some ETA from this official image?
Thanks.
romut said:
Thanks for the help.
In the meantime, I've read this thread and this one. So, I tried to flash the Rogers Canada 4.4.2 image. Everything runs fine, but still no radio.
But, I currently run the instructions from here to return to stock, and so I didn't know I had to flash NON-HLOS.bin file. I'm going to try this right now.
Thanks again.
Click to expand...
Click to collapse
Just to give you a heads up, the NON-HLOS.bin file is where most of the modem actually is (all 50-60MB of it), I'll send a PM to the topic creator, because it's not giving the community the right information, they are missing that critical piece.
Be careful with your bootloader, the FR version may be the same as the UK bootloader (30.B3), the Rodgers version is (30.B4) meaning you would no longer be able to flash the whole SBF for the FR version because it would have a lower bootloader. However, you would be safe by just flashing the system image, but I would recommend not taking any OTA updates if you flash it.
Also remember that radios require a reset/power down, because it needs to get the information from the SIM card to use the particular radio frequencies. Also make sure the APN is correctly configured, this may also cause an issue.
There may be another Developer Edition 4.4 image directly from Moto that you could try, I think it takes 24 hours for them to get back with you giving you the link to their google drive though, however, it may be the same as the T-Mobile one on SBF.
You could also attempt getting the patched files from a 4.4.2 OTA image and merging it with a 4.4 radio (basically over-writing some of the files in the 4.4 version), I am unsure if this would work, but in theory it should, since that's what is happening during the update. However, I don't know if there are checks or anything, don't brick your phone because of me
Thanks for your message.
I've tried to flash the modem part only, then switch off/on the phone. No way, no radio. As I flashed the Rogers firmware, yes, my bootloader has been upgraded to 30B4.
Only way now is to wait for the official Developer Edition 4.4.2 zip, or to contact Motorola.
romut said:
Thanks for your message.
I've tried to flash the modem part only, then switch off/on the phone. No way, no radio. As I flashed the Rogers firmware, yes, my bootloader has been upgraded to 30B4.
Only way now is to wait for the official Developer Edition 4.4.2 zip, or to contact Motorola.
Click to expand...
Click to collapse
Stuck between a rick and a hard place , been trying to warn folks not to flash the new 4.4.2 sbf firmware, the list gets bigger and bigger by the day if people who either hard brick or have no radio signal. I actually tried to just have a warning sticky for this reason and was denied by the moderators. All.I can suggest is flash the modem for south american variants as there 4.4.2 sbf firmware is available, also flash the fsg.mbn file too
Sent on my Gummy running Lenoto X
flashallthetime said:
Stuck between a rick and a hard place , been trying to warn folks not to flash the new 4.4.2 sbf firmware, the list gets bigger and bigger by the day if people who either hard brick or have no radio signal. I actually tried to just have a warning sticky for this reason and was denied by the moderators. All.I can suggest is flash the modem for south american variants as there 4.4.2 sbf firmware is available, also flash the fsg.mbn file too
Sent on my Gummy running Lenoto X
Click to expand...
Click to collapse
He wouldn't have been able to flash a 4.4 image anyways because he used the 4.4.2 FR image. The only reason to upgrade via OTA/SBF is if you are certain that your phone matches the SBF. Otherwise there are too many possible complications to list here. His best bet is the NON-HLOS and fsg from that 4.4.2 version since it has the 4.4 modem and the fixes/modifications of the 4.4.2 as well. Or he could try to "manually" update the T-mobile 4.4 SBF modem, by copying the T-mobile 4.4.2 OTA modem patches and overwriting the select few files in the SBF, then flashing the new image.
However, in reality, it's probably best to wait for the "official" SBF anyways.
mastarifla said:
He wouldn't have been able to flash a 4.4 image anyways because he used the 4.4.2 FR image. The only reason to upgrade via OTA/SBF is if you are certain that your phone matches the SBF. Otherwise there are too many possible complications to list here. His best bet is the NON-HLOS and fsg from that 4.4.2 version since it has the 4.4 modem and the fixes/modifications of the 4.4.2 as well. Or he could try to "manually" update the T-mobile 4.4 SBF modem, by copying the T-mobile 4.4.2 OTA modem patches and overwriting the select few files in the SBF, then flashing the new image.
However, in reality, it's probably best to wait for the "official" SBF anyways.
Click to expand...
Click to collapse
No just wait for the sbf firmware
Sent on my Gummy running Lenoto X
flashallthetime said:
Stuck between a rick and a hard place , been trying to warn folks not to flash the new 4.4.2 sbf firmware, the list gets bigger and bigger by the day if people who either hard brick or have no radio signal. I actually tried to just have a warning sticky for this reason and was denied by the moderators. All.I can suggest is flash the modem for south american variants as there 4.4.2 sbf firmware is available, also flash the fsg.mbn file too
Sent on my Gummy running Lenoto X
Click to expand...
Click to collapse
I know you're doing a dawn good job at warning people :good: I should have read some threads before flashing, my stupidity ! :laugh:
I'll try to contact Motorola and see what can be done. Problem is this is a DE bought in USA, and I'm in France. Not the best case.
romut said:
I know you're doing a dawn good job at warning people :good: I should have read some threads before flashing, my stupidity ! :laugh:
I'll try to contact Motorola and see what can be done. Problem is this is a DE bought in USA, and I'm in France. Not the best case.
Click to expand...
Click to collapse
Your screwed, the European boot loader is 30.b3 and America is 30.b4, the modem aren't compatible, you can't run European modems with american boot loader and visa versa , call moto
Sorry for your situation. Have you tried flashing the French firmware?
Sent on my Gummy running Lenoto X
flashallthetime said:
Your screwed, the European boot loader is 30.b3 and America is 30.b4, the modem aren't compatible, you can't run European modems with american boot loader and visa versa , call moto
Sorry for your situation. Have you tried flashing the French firmware?
Sent on my Gummy running Lenoto X
Click to expand...
Click to collapse
Yes that's what I wrote, I've seen the bootloader has been upgraded. As the official ROM for the Moto X DE already includes the french, it's not a big deal for me to get stuck with the ghost.en.US ROM. But as I've already flashed a 4.4.2 (the french one), I need the official 4.4.2 which is not yet available.
I've read in another thread, Motorola has accepted to exchange some phones in that case, I cross my fingers.
Hi,
I had a chat yesterday with the Motorola Service. This issue can be covered by the warranty only for Developer Edition. Now my problem is the cost to send the Moto from France to the US, but I think this may be interesting for people with the same issue.
Or we have to wait for the official release of the T-Mobile 4.4.2 ROM, but I couldn't get an ETA.
stock 4.4.2 boot.img
i flashed faux123 custom kernel and was not aware it was for 4.4 the updater app allowed me to install it
now my phone is screwed up
does anyone know where I can find the stock kernel image for 4.4.2 on unlocked xt1053 dev edition
I updated my Motorbike X XT1058 for 4.4.4 (KXA21.12 VZW_XT1060_4.4.4-KXA21.12-L1.26_1FF) and it wanted to do the DOWNGRADE for 4.4.3 or 4.4.2. Some way for that?
The GPT.BIN in 4.4.4 is different from 4.4.3, which is different from 4.4.2, which is different from 4.4.0's.
Motoboot.img is different between 4.4.3 and 4.4.2. 4.4.2's is different from 4.4.0.
These will prevent a complete, successful and safe downgrade of the rom version.
If you've seen all the "don't downgrade or you'll brick" warnings, this is what its talking about.
This ^^^
But a better question is WHY would you want to downgrade?
I did not like because of the modification Verizon
Christian Correia said:
I did not like because of the modification Verizon
Click to expand...
Click to collapse
Well, you really can't downgrade without great risk.
So better to live with it, or try the Chinese seller and unlock your bootloader for a fee. Then you can root, and change things that you can't change without root. Here is a long thread about the unlock code seller...
http://forum.xda-developers.com/showthread.php?t=2751177
Otherwise, there isn't much you can do.
Darth said:
Well, you really can't downgrade without great risk.
So better to live with it, or try the Chinese seller and unlock your bootloader for a fee. Then you can root, and change things that you can't change without root. Here is a long thread about the unlock code seller...
http://forum.xda-developers.com/showthread.php?t=2751177
Otherwise, there isn't much you can do.
Click to expand...
Click to collapse
Actually you can do something that is risk because everything is a risk you can take and you never know what can happen but here it is: you can flash the 4.4.3 or 4.4.2 or 4.4.0 update over the 4.4.4 by using minimal adb flash tool and then just flash the 4.4.2 or desired version over but DO NOT FLASH THE gpt.bin!!!!!!!!That will screw up everything so after you flash everything but the gpt.bin you should do a cmd to reboot then you will be on the downgraded version!!! I'm not responsible for any bricked phones OK I tried this and the it worked for me so yea its a working procedure that YeS is a risky task so be careful!!!!:laugh:
DROID_4_UsEr said:
Actually you can do something that is risk because everything is a risk you can take and you never know what can happen but here it is: you can flash the 4.4.3 or 4.4.2 or 4.4.0 update over the 4.4.4 by using minimal adb flash tool and then just flash the 4.4.2 or desired version over but DO NOT FLASH THE gpt.bin!!!!!!!!That will screw up everything so after you flash everything but the gpt.bin you should do a cmd to reboot then you will be on the downgraded version!!! I'm not responsible for any bricked phones OK I tried this and the it worked for me so yea its a working procedure that YeS is a risky task so be careful!!!!:laugh:
Click to expand...
Click to collapse
First this is an old thread...
Next, skipping gpt.bin and/or motoboot.img(or its components) HAS been a cause for bricks, and when it didn't brick, it caused extra bugs (like trying to go App Drawer -> Settings -> Security kicks you back to settings menu... and some having issues toggling wifi on/off... and some who tried skipping gpt/motoboot when applying the 5.1 update also had speaker phone issues).
For more, see the link in my signature on downgrading..
KidJoe said:
First this is an old thread...
Next, skipping gpt.bin and/or motoboot.img(or its components) HAS been a cause for bricks, and when it didn't brick, it caused extra bugs (like trying to go App Drawer -> Settings -> Security kicks you back to settings menu... and some having issues toggling wifi on/off... and some who tried skipping gpt/motoboot when applying the 5.1 update also had speaker phone issues).
For more, see the link in my signature on downgrading..
Click to expand...
Click to collapse
My mistake you need to flash the 4.4.4 gpt.bin over the 4.4.2 gpt.bin so the device thinks your flashing a 4.4.4 firmware but in reality your flashing the 4.4.2 firmware..I think its easier to use RSD lite to flash the firmware but you need to do a couple of modifications to the 4.4.2 firmware.All you got to do is move the 4.4.4 gpt.bin to the 4.4.2 firmware then flash it if you get the moto.bin error just do the same step as said above with the gpt.bin but with the moto.bin file..Hopefully it worked out for you ?
DROID_4_UsEr said:
My mistake you need to flash the 4.4.4 gpt.bin over the 4.4.2 gpt.bin so the device thinks your flashing a 4.4.4 firmware but in reality your flashing the 4.4.2 firmware..I think its easier to use RSD lite to flash the firmware but you need to do a couple of modifications to the 4.4.2 firmware.All you got to do is move the 4.4.4 gpt.bin to the 4.4.2 firmware then flash it if you get the moto.bin error just do the same step as said above with the gpt.bin but with the moto.bin file..Hopefully it worked out for you ?
Click to expand...
Click to collapse
Not sure why you are quoting me saying "hopefully it worked out..." as I'm not the one trying to downgrade.
I can assure you... mixing GPT.BIN/Motoboot.img parts from one Stock rom, with the GPT.BIN/Motoboot.img of another STOCK rom is not a good idea.. it has been cause for bricks and/or features not working correctly.
To suggest otherwise, without acknowledging the risks, is irresponsible, especially if you take some time to search the forums and see all the posts of people who have either soft or hard bricked their device while trying various processes to downgrade. And especially if you are someone willing to help those who have bricked following your advice.
I did try but no succes
KidJoe said:
Not sure why you are quoting me saying "hopefully it worked out..." as I'm not the one trying to downgrade.
I can assure you... mixing GPT.BIN/Motoboot.img parts from one Stock rom, with the GPT.BIN/Motoboot.img of another STOCK rom is not a good idea.. it has been cause for bricks and/or features not working correctly.
To suggest otherwise, without acknowledging the risks, is irresponsible, especially if you take some time to search the forums and see all the posts of people who have either soft or hard bricked their device while trying various processes to downgrade. And especially if you are someone willing to help those who have bricked following your advice.
Click to expand...
Click to collapse
How can you downgrade from 4.4.4 to 4.4.2? I did try to downgrade the XT1060 Verizon,but it cannot be done,did try all options cut a line here ,edit a line there but still end up with the same 4.4.4 version.The idea i have is to downgrade to 4.4.2 and the use the sunshine to unlock the bootloader and after that to flash any ROM out there ,but never upgrade back to 4.4.4...Any help would be helpful...
Best Regards!
DejanPet said:
How can you downgrade from 4.4.4 to 4.4.2? I did try to downgrade the XT1060 Verizon,but it cannot be done,did try all options cut a line here ,edit a line there but still end up with the same 4.4.4 version.The idea i have is to downgrade to 4.4.2 and the use the sunshine to unlock the bootloader and after that to flash any ROM out there ,but never upgrade back to 4.4.4...Any help would be helpful...
Best Regards!
Click to expand...
Click to collapse
It all depends on what rom you wanna flash if you flash cyanogenmod 12.1 you'll get the Lollipop update if you flash Cyanogenmod 11 you'll get back to kit-kat.
---------- Post added at 05:23 PM ---------- Previous post was at 05:20 PM ----------
DROID_4_UsEr said:
It all depends on what rom you wanna flash if you flash cyanogenmod 12.1 you'll get the Lollipop update if you flash Cyanogenmod 11 you'll get back to kit-kat.
Click to expand...
Click to collapse
But you should know Sunshine developers charge a fee of 25 bucks to unlock and it works but you need to have a pay pal account and enough money for it
DejanPet said:
The idea i have is to downgrade to 4.4.2 and the use the sunshine to unlock the bootloader and after that to flash any ROM out there ,but never upgrade back to 4.4.4...Any help would be helpful...
Best Regards!
Click to expand...
Click to collapse
its documented in the sunshine thread that once 4.4.4 is on your phone its too late. even if you manage to downgrade it without bricking, the parts sunshine relies on will already have been patched and cant be downgraded. so downgrading wont help you to get sunshine to work
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 !
?
Okay, I have to ask. Has anyone successfully downgraded a 4.4.4 KitKat Moto X (2013) to a previous firmware version?
I have the XT1058 "ghost" if that matters.
Seriously? This has only been covered nearly everyday since 4.4.2 became available. In other words, the answers are out there if you simply open your eyes or search.
No not possible to downgrade from 4.4.4
Yes, but for every one that claim they did.... 10 others have bricked.
And the ones that say they downgraded OK, may be in for a bad surprise next time they take an ota.
So, don't... Unless you are able to replace it if you need to. ?
Darth said:
Yes, but for every one that claim they did.... 10 others have bricked.
And the ones that say they downgraded OK, may be in for a bad surprise next time they take an ota.
So, don't... Unless you are able to replace it if you need to. ?
Click to expand...
Click to collapse
This is the info I wanted. Thanks.
Hi, my phone is xt1056, BL unlocked, I was fully flashed (enabled all the options in the xml file) the ghost_sprint-user-4.4.4-KXA21.12-L1.28-28-release-keys-cid9.xml with rsd to upgrade 4.4.4 once.
Then I fully flashed my xt1056 with the xt1060 rom (VZW_XT1060_4.4.2-KXA20.16-1.25.2_CFC_1FF.xml) in rsd. Now the phone is 4.4.2 and no signal, but it is 4.4.2, I can get my SPC with the app SPCUtility.apk.
After get my SPC, I was fully flashed the xt1056 (ghost_sprint-user-4.4.4-KXA21.12-L1.28-28-release-keys-cid9.xml with rsd to upgrade 4.4.4) again and works well (need to unlock the network again).
It really doesn't help me that you have the Sprint version. The AT&T bootloader can't be unlocked. At least not to my knowledge.
Downgrading with an unlocked bootloader is no different than locked... Extremely dangerous.
And the poster above who downgraded, then upgraded again... I would not take any OTA's going forward. Or you might get an unfortunate surprise.
DarkWolffe said:
It really doesn't help me that you have the Sprint version. The AT&T bootloader can't be unlocked. At least not to my knowledge.
Click to expand...
Click to collapse
If you have 4.4.4 on an ATT device, right its bootloader can not be unlocked at this point.
As for flashing, as many have said IT IS NOT SAFE to downgrade, unlocked and locked bootloader included.
There are parts that are included with 4.4.2 and up that prevent downgrading. Because of this, under certain circumstances when trying to downgrade (like from 4.4.2 to 4.4 or lower, or 4.4.4 to 4.4.2 or lower), you could either brick your phone, or set it up to brick in the future when you take an upgrade.
In the case of some who have bricked by downgrading, flashing the latest (4.4.4 currently) SBF via mFastboot commands, with a few extra steps, has been enough to revive the phone. Other times, not.
For as many stories you might see of "its safe" or "I've done it", a future OTA will likely get them. Plus there are many more who have created "I bricked when trying to downgrade, HELP!!" threads.
A few Examples of bricked while downgrading:
http://forum.xda-developers.com/moto-x/moto-x-qa/xt-1053-to4-4-4-to-4-4-3-prob-wit-t2967182
http://forum.xda-developers.com/moto-x/moto-x-qa/expert-opinion-to-stock-t2944721
http://forum.xda-developers.com/moto-x/moto-x-qa/totally-bricked-t2952064
http://forum.xda-developers.com/moto-x/general/load-os-moto-x-t2942785
(keep looking in the Q&A section, or General section, you'll see lots more of them!)
And why do you think this thread exists? -> http://forum.xda-developers.com/moto-x/general/how-to-resurrecting-bricked-moto-x-t2629057
I'll quote myself from another thread (in reply to someone that had an Unlocked bootloader)...
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
Again, this info applies whether you have an unlocked or locked bootloader.
So it is suggested you just stick with what is on your phone once you get on 4.4.2 or newer.
KidJoe said:
If you have 4.4.4 on an ATT device, right its bootloader can not be unlocked at this point.
As for flashing, as many have said IT IS NOT SAFE to downgrade, unlocked and locked bootloader included.
There are parts that are included with 4.4.2 and up that prevent downgrading. Because of this, under certain circumstances when trying to downgrade (like from 4.4.2 to 4.4 or lower, or 4.4.4 to 4.4.2 or lower), you could either brick your phone, or set it up to brick in the future when you take an upgrade.
In the case of some who have bricked by downgrading, flashing the latest (4.4.4 currently) SBF via mFastboot commands, with a few extra steps, has been enough to revive the phone. Other times, not.
For as many stories you might see of "its safe" or "I've done it", a future OTA will likely get them. Plus there are many more who have created "I bricked when trying to downgrade, HELP!!" threads.
A few Examples of bricked while downgrading:
http://forum.xda-developers.com/moto-x/moto-x-qa/xt-1053-to4-4-4-to-4-4-3-prob-wit-t2967182
http://forum.xda-developers.com/moto-x/moto-x-qa/expert-opinion-to-stock-t2944721
http://forum.xda-developers.com/moto-x/moto-x-qa/totally-bricked-t2952064
http://forum.xda-developers.com/moto-x/general/load-os-moto-x-t2942785
(keep looking in the Q&A section, or General section, you'll see lots more of them!)
And why do you think this thread exists? -> http://forum.xda-developers.com/moto-x/general/how-to-resurrecting-bricked-moto-x-t2629057
I'll quote myself from another thread (in reply to someone that had an Unlocked bootloader)...
Again, this info applies whether you have an unlocked or locked bootloader.
So it is suggested you just stick with what is on your phone once you get on 4.4.2 or newer.
Click to expand...
Click to collapse
Perfect answer. Thank you for the clarity.