Has any one got, or could make, a fully signed GPE Rom?
Not yet.
Surely the official GPE Firmware image (KOT49H.M004) here is signed:
http://sbf.droid-developers.org/phone.php?device=14
lost101 said:
Surely the official GPE Firmware image (KOT49H.M004) here is signed:
http://sbf.droid-developers.org/phone.php?device=14
Click to expand...
Click to collapse
Many have problems with that on non gpe. I don't think it is signed.
denzel09 said:
Many have problems with that on non gpe. I don't think it is signed.
Click to expand...
Click to collapse
I haven't been following the flashing thread, but I had no issues flashing it on a XT1032 non-GPE GB handset.
lost101 said:
I haven't been following the flashing thread, but I had no issues flashing it on a XT1032 non-GPE GB handset.
Click to expand...
Click to collapse
No no buddy, i am talking to relock bootloader. I think for this he asked about signed.
lost101 said:
Surely the official GPE Firmware image (KOT49H.M004) here is signed:
http://sbf.droid-developers.org/phone.php?device=14
Click to expand...
Click to collapse
I have a stock 4.4.2 ROM which using mfastboot will install with no errors or warnings.
the KOT49H.M004 ROM has several warnings and one system image is stated to be unsigned.
robin0800 said:
I have a stock 4.4.2 ROM which using mfastboot will install with no errors or warnings.
the KOT49H.M004 ROM has several warnings and one system image is stated to be unsigned.
Click to expand...
Click to collapse
I'm more inclined to believe the errors arise from flashing the official GPE firmware onto a non-GPE device. KOT49H.M004 came from a Motorola / Google server, it's not just hacked together.
lost101 said:
I'm more inclined to believe the errors arise from flashing the official GPE firmware onto a non-GPE device. KOT49H.M004 came from a Motorola / Google server, it's not just hacked together.
Click to expand...
Click to collapse
Would it be logical to assume the GPe stock rom can only be flashed onto an XT1032 ? I would like to go the other way, from GPe to the Motorola version, so I can try out some roms. ANyone try this?
I bought a GPe because I thought there would be more custom than the Motorola... turns out the opposite is true. For now, at least.
lost101 said:
I'm more inclined to believe the errors arise from flashing the official GPE firmware onto a non-GPE device. KOT49H.M004 came from a Motorola / Google server, it's not just hacked together.
Click to expand...
Click to collapse
Its on sbf-droid and is supposedly a leaked firmware from Motorola. It is not officially released by Motorola and does not come from a Motorola or Google server.
It could contain alterations if one of the system images is not signed.
scott_doyland said:
Its on sbf-droid and is supposedly a leaked firmware from Motorola. It is not officially released by Motorola and does not come from a Motorola or Google server.
It could contain alterations if one of the system images is not signed.
Click to expand...
Click to collapse
It's hard to say anything for sure. I only said what I did because of this comment from a 'Firmware Team' member:
I use Filefactory because I can remotely upload files to my account directly from Motorola's servers using Filefactory's bandwidth, which is considerably faster than I can upload from my PC.
Click to expand...
Click to collapse
[source]
EDIT:
These are original and official source files from Motorola's server.
Click to expand...
Click to collapse
[source]
@dgauze, try flashing this and let us know: (Before flashing, replace the recovery file included with a custom one (i.e CWM Advanced))
Android 4.4.2 - Blur_Version.172.44.4.falcon_umts.Retail.en.US
US_retail_XT1032_KXB20.9-1.8-1.4_CFC.xml.zip
http://sbf.droid-developers.org/phone.php?device=14
Also perhaps to be extra safe, delete or don't flash the motoboot.img included. Maybe you should start a new thread on this.
Related
I want to get the 4.4 update on my new Moto G. But also i want to avoid unlocking the bootloader. I read somewhere that the system will let you flash a signed image without unlocking the bootloader, but i want to be sure, so i don't end with a soft bricked phone and have to unlock it anyways.
Can you help me?
EDIT: You can! Just flash the upgrade via fastboot and your phone will have the last iteration of Android witthot unlocking anything.
tatazeuz said:
I want to get the 4.4 update on my new Moto G. But also i want to avoid unlocking the bootloader. I read somewhere that the system will let you flash a signed image without unlocking the bootloader, but i want to be sure, so i don't end with a soft bricked phone and have to unlock it anyways.
Can you help me?
Click to expand...
Click to collapse
you don't have to unlock it if you are updating it through the update option inside the phone itself.
digitalmahdi said:
you don't have to unlock it if you are updating it through the update option inside the phone itself.
Click to expand...
Click to collapse
I know, but the phone comes with a carrier firmware that will take some time to roll the update, and I want to replace it.
tatazeuz said:
I know, but the phone comes with a carrier firmware that will take some time to roll the update, and I want to replace it.
Click to expand...
Click to collapse
then the answer is no, in order to load any custom rom you have to unlock your bootloader.
digitalmahdi said:
then the answer is no, in order to load any custom rom you have to unlock your bootloader.
Click to expand...
Click to collapse
But I'm not trying to load a custom ROM, I'm trying to load an official firmware.
Which is a ROM itself
Sent from my XT1032 using xda app-developers app
Faruko said:
Which is a ROM itself
Sent from my XT1032 using xda app-developers app
Click to expand...
Click to collapse
But certainly isn't custom, and its signed.
tatazeuz said:
But certainly isn't custom, and its signed.
Click to expand...
Click to collapse
I think you should refer to this video - http://youtu.be/-L44JqysUy8
It shows how to flash a rom without unlocking the bootloader. There are retail ROMS available from http://sbf.droid-developers.org/phone.php?device=14
voosh710 said:
I think you should refer to this video - http://youtu.be/-L44JqysUy8
It shows how to flash a rom without unlocking the bootloader. There are retail ROMS available from http://sbf.droid-developers.org/phone.php?device=14
Click to expand...
Click to collapse
Thanks!
I flashed retail.GB over my tesco firmware without unlocking bootloader
Motorola Moto G (XT1032), Android 4.4.2
Is Android Lollipop out for Moto G (1st) GPE? or still not? (bought mine from Google's website)
daniel1112333 said:
Is Android Lollipop out for Moto G (1st) GPE? or still not? (bought mine from Google's website)
Click to expand...
Click to collapse
Have you got it?
No?
Guess what......ITS NOT OUT
eemgee said:
Have you got it?
No?
Guess what......ITS NOT OUT
Click to expand...
Click to collapse
sorry if this is a stupid question, but if i've already unlocked the bootloader, and installed root and recovery but i didnt change/modify the original/official ROM 4.4.4 from my moto G, in order to get the lolipop update, i just need to install the original "stock" recovery or i will need to flash everything (firmware/radio/originalrom, etc) again? thanks in advance folks, im just new with moto g.
If you have stock recovery and unmodified system you should be fine with the ota, when it comes.
rickastillo said:
sorry if this is a stupid question, but if i've already unlocked the bootloader, and installed root and recovery but i didnt change/modify the original/official ROM 4.4.4 from my moto G, in order to get the lolipop update, i just need to install the original "stock" recovery or i will need to flash everything (firmware/radio/originalrom, etc) again? thanks in advance folks, im just new with moto g.
Click to expand...
Click to collapse
Listen to mw, if you dont wanna have trouble with the ota, flash entire firmware! Do that and you will see there will be no problem... Restore entire firmware before updating via ota.
Afaik you can also use CWM to update
MarckozZ said:
Listen to mw, if you dont wanna have trouble with the ota, flash entire firmware! Do that and you will see there will be no problem... Restore entire firmware before updating via ota.
Click to expand...
Click to collapse
Oh ok, well i guess i will have to do that, my motog is the dualsim type XT1033, i bought it on amazon, i asume it is the "brazilian" one nor the asian , but it would be any problem if it happens to be the asians one? or there is any different between these two? i guess i did the wrong thing (unrooting and install a custom recovery) days before loli pop update T_T
I guess the OTA notification still will show up even if it's recovery was modified
I guess the question is answered so we can close this one
---> Thread closed
I'm currently on a custom 5.1 ROM with the new bootloader and radio. I read about issues when flashing the CM12 ROM with this setup. Is this still a problem? Do I have to go back to the 5.0 stock android (with full wipe) before flashing CM12?
Would like to know something similar of the sort, also have the 5.1 boot loader and radio and am on resurrection remix 5.1. Would like to go to CM12 if possible.
Solution found:
http://forum.xda-developers.com/showthread.php?t=2958222
I already installed CM12 after flashing the 5.0 bootloader and radio from the thread without any problems.
daniel.1983 said:
Solution found:
http://forum.xda-developers.com/showthread.php?t=2958222
I already installed CM12 after flashing the 5.0 bootloader and radio from the thread without any problems.
Click to expand...
Click to collapse
So what was the process you wnet through? Flash the 5.1 radio and bootloader, then CM12, then gapps? I thought downgrading the bootloader would result in a hard brick? Also did you flash the latest CM12 nightly?
KentuckyGuy447 said:
So what was the process you wnet through? Flash the 5.1 radio and bootloader, then CM12, then gapps? I thought downgrading the bootloader would result in a hard brick? Also did you flash the latest CM12 nightly?
Click to expand...
Click to collapse
I flashed the zip file from post one with the 5.0 bootloader (https://www.androidfilehost.com/?fid=95916177934545628). Afterwards I flashed the latest CM12 nightly and the Gapps on top. I'm not sure about which action/configuration could brick the device. I have seen much positive feedback in the other thread, so I tried this too.
KentuckyGuy447 said:
I thought downgrading the bootloader would result in a hard brick?
Click to expand...
Click to collapse
Think. Why would Google still make available older factory images, if downgrading (which would include the bootloader) bricked a updated device?
beekay201 said:
Think. Why would Google still make available older factory images, if downgrading (which would include the bootloader) bricked a updated device?
Click to expand...
Click to collapse
It is more of a concern you know. My knowledge is very limited as all this is new to me. I don't have money to throw around for a new device but thanks! I'm taking this as its safe to. Just hard bricking would permenatly destroy a device so don't wanna do that you know...
EDIT: Tested and Confirmed Woking! Big thanks to Daniel!
I'm currently in CM 14.1 it's working really good for me but I need to go back to stock for a few days, I have a backup made with TWRP of stock marshmallow rom. The question, as the title says, can I restore from this backup on TWRP recovery? Is it safe? Or is it mandatory to to flash through fastboot the original recovery and then the image of the original ROM? I'm sorry to bother you guys, but I looked through the forum and didn't find any answers. Thanks in advance
Yeah, you can. TWRP will happily restore any backup made by it. TWRP just dumps the backed-up partitions into respective hardware partitions on the emmc chip so it doesn't matter whether the ROM is stock or a custom one
Broadcasted from Zeta Reticuli
Thanks I'll do it that way then
I need the stock backup file how could i restore
Where can i get the stock rom for moto g3 xt1550
vijethjjogi said:
Where can i get the stock rom for moto g3 xt1550
Click to expand...
Click to collapse
The stock ROM is not a TWRP backup, it is raw partition data that is written with fastboot, there is a factory firmware thread in the General Discussion section.
Any KitKat based roms for g3
vijethjjogi said:
Any KitKat based roms for g3
Click to expand...
Click to collapse
No, the first ROM for this phone was Lollipop. Developers don't go backwards in Android version without a good reason and there isn't one for this device.
acejavelin said:
No, the first ROM for this phone was Lollipop. Developers don't go backwards in Android version without a good reason and there isn't one for this device.
Click to expand...
Click to collapse
OT, but would you know of a case in which that has actually happened? (ROM for an older version than the one the device was released on) I've always been curious about that.
nARMstrong20 said:
OT, but would you know of a case in which that has actually happened? (ROM for an older version than the one the device was released on) I've always been curious about that.
Click to expand...
Click to collapse
I can't think of one actually, it would be very unusual since there wouldn't be kernel source for earlier versions of Android for the device.
hi guys i'm brasilian and my english is pretty poor but lets try. i was flash 4.4.4 rom br retail. and i update via ota for lollipop.. and brick .. i search in forums here ... and i go it to put in boot loader without robot.. already try many ways to recovery my boot loader but always get error remote failure.. and already used 6.0.1 stock .. maybe i need to files atualy for this? i'm very sad my maxx is dead .. someone give me light .. help me fix this ... thank you guys
Is your bootloader locked or unlocked?
ChazzMatt said:
Is your bootloader locked or unlocked?
Click to expand...
Click to collapse
unlocked
kenedi jr said:
unlocked
Click to expand...
Click to collapse
Good.
What version Android was your phone on before the problem?
Were you on stock (factory) or on custom ROM?
Surely you weren't on Kitkat for almost 3 years?
ChazzMatt said:
Good.
What version Android was your phone on before the problem?
Were you on stock (factory) or on custom ROM?
Surely you weren't on Kitkat for almost 3 years?
Click to expand...
Click to collapse
I was in a custom rom and went to 4.4.4 and tried to upgrade via ota .. and brinck so I was able to make boot loader appear more without the robot
kenedi jr said:
I was in a custom rom and went to 4.4.4 and tried to upgrade via ota .. and brinck so I was able to make boot loader appear more without the robot
Click to expand...
Click to collapse
When you downgrade back to lower stock, you have to omit gpt.bin command. Because you have a newer bootloader.
This is also why you can't take OTA. Because it tries to install a different bootloader (which is probably still older than what you had with custom ROM). If you wanted stock 5.0.2 again, you have to flash full stock image and omit the gpt.bin command.
Are you able to use volume and power button to the bootloader screen?
ChazzMatt said:
When you downgrade back to lower stock, you have to omit gpt.bin command. Because you have a newer bootloader.
This is also why you can't take OTA. Because it tries to install a different bootloader (which is probably still older than what you had with custom ROM). If you wanted stock 5.0.2 again, you have to flash full stock image and omit the gpt.bin command.
Are you able to use volume and power button to the bootloader screen?
Click to expand...
Click to collapse
So I'm stuck on the bootloader. If I connect charger or pc it will already pro boot loader without the robot. I have already tried to pass stock 4.4.4 and 6.0 and more etc always from the failure remote failure in bootloader appears in the log something with gt bin downgrade
ChazzMatt said:
When you downgrade back to lower stock, you have to omit gpt.bin command. Because you have a newer bootloader.
This is also why you can't take OTA. Because it tries to install a different bootloader (which is probably still older than what you had with custom ROM). If you wanted stock 5.0.2 again, you have to flash full stock image and omit the gpt.bin command.
Are you able to use volume and power button to the bootloader screen?
Click to expand...
Click to collapse
My question is if I crashed from 4.4.4 trying to upgrade to 5.1 which version files do I need to adapt to my bootloader that seems to be corrupted?
kenedi jr said:
My question is if I crashed from 4.4.4 trying to upgrade to 5.1 which version files do I need to adapt to my bootloader that seems to be corrupted?
Click to expand...
Click to collapse
Before this trouble, were you ever on stock Marshmallow 6.0.1? If so, you can flash back to full firmware of that, but needs to be the very latest. I'll find a link for you.
Also, do you have TWRP installed and did you have a backup you can restore?
ChazzMatt said:
Before this trouble, were you ever on stock Marshmallow 6.0.1? If so, you can flash back to full firmware of that, but needs to be the very latest. I'll find a link for you.
Also, do you have TWRP installed and did you have a backup you can restore?
Click to expand...
Click to collapse
Yes before this problem I was in the latest 6.0.1 and the stock I have here when I installed had a security update
ChazzMatt said:
Before this trouble, were you ever on stock Marshmallow 6.0.1? If so, you can flash back to full firmware of that, but needs to be the very latest. I'll find a link for you.
Also, do you have TWRP installed and did you have a backup you can restore?
Click to expand...
Click to collapse
I do not have twrp backup and I can not even install the recovery stock
kenedi jr said:
Yes before this problem I was in the latest 6.0.1 and the stock I have here when I installed had a security update
Click to expand...
Click to collapse
OK, then that's the bootloader you were on and will always be on. You need to reflash that latest version (with the security update) to repair. Just reflash the entire full firmware.
There's a link to it here in this forum. I'll find it when I get home, if you don't have it.
Then in the future, if you try to downgrade, you always have to flash full stock version EXCEPT you omit the gpt.bin file. Whether 4.4.4 Kitkat or 5.0.2 Lollipop.
And you can never take OTA.
Because you really have 6.0.1 bootloader.
ChazzMatt said:
OK, then that's the bootloader you were on and will always be on. You need to reflash that version to repair. Just reflash the entire full firmware.
Click to expand...
Click to collapse
This is the most likely because all the methods say so old and not one was and when I try to pass any old stock also will not always get that error in the bootloader in the gptbin downgrade logs
ChazzMatt said:
OK, then that's the bootloader you were on and will always be on. You need to reflash that latest version (with the security update) to repair. Just reflash the entire full firmware.
There's a link to it here in this forum. I'll find it when I get home, if you don't have it.
Then in the future, if you try to downgrade, you always have to flash full stock version EXCEPT you omit the gpt.bin file. Whether 4.4.4 Kitkat or 5.0.2 Lollipop.
And you can never take OTA.
Because you really have 6.0.1 bootloader.
Click to expand...
Click to collapse
thanks bro you saved me
kenedi jr said:
This is the most likely because all the methods say so old and not one was and when I try to pass any old stock also will not always get that error in the bootloader in the gptbin downgrade logs
Click to expand...
Click to collapse
You can not flash any older gpt.bin files. You have to omit (leave out) that flash command.
Your gpt.bin file is 6.0.1, and you cannot downgrade. Even on 4.4.4, trying to accept the 5.0.2 OTA update is still older gpt.bin file in that OTA than your 6.0.1.
ChazzMatt said:
OK, then that's the bootloader you were on and will always be on. You need to reflash that latest version (with the security update) to repair. Just reflash the entire full firmware.
There's a link to it here in this forum. I'll find it when I get home, if you don't have it.
Then in the future, if you try to downgrade, you always have to flash full stock version EXCEPT you omit the gpt.bin file. Whether 4.4.4 Kitkat or 5.0.2 Lollipop.
And you can never take OTA.
Because you really have 6.0.1 bootloader.
Click to expand...
Click to collapse
i don't have link .. i will wanting you so
kenedi jr said:
i don't have link .. i will wanting you so
Click to expand...
Click to collapse
https://forum.xda-developers.com/showthread.php?p=72846593
ChazzMatt said:
https://forum.xda-developers.com/showthread.php?p=72846593
Click to expand...
Click to collapse
I was a bit confused with this link which is the last one? I discovered because I am Brazilian and my English was developed only by playing
http://ftpeil.eil.com.br/vip/motoro...S24.107-70.2-7_cid12_subsidy-DEFAULT_CFC.xml/
ChazzMatt said:
http://ftpeil.eil.com.br/vip/motoro...S24.107-70.2-7_cid12_subsidy-DEFAULT_CFC.xml/
Click to expand...
Click to collapse
Face first you're a myth. I just passed gpt.bin and got the bootloader ... I'm very happy. Do I need to pass the entire rom ??
:good::laugh: