I am new to custom roms
I have moto g XT1032 locked to telus canada
i have unlocked bootloader
i have rooted the phone
i have flashed TWRP v2.8.6.0 recovery
and sucessfully installed CM 12.1
now i want to install Stock GPE 5.1 on my device
before installing CM12.1 i was on stock 5.0.2 lollipop (un rooted)
I have purchased network u nlock code from ebay but i did not unlocked my phone yet..
could anyone explain me the procedure how can i install GPE on my device
Related
I am using Moto g (1st gen) Asian version (XT1033) with Android kitkat 4.4.4. When I tried to upgrade to lollipop (Asian sock test) using OTA, it returns an error that my current build is not
Code:
motorola/falcon_asia_ds/falcon_umtsds:4.4.4/KXB21.14-L1.40/34:user/release-keys
but
Code:
motorola/falcon_asia_ds/falcon_umtsds:4.4
History: My moto g originally comes with Android 4.3 and I upgraded to 4.4.4 via OTA(official) update. After release of Lollipop Brazilian OTA, I flashed my device with Brazillian 4.4.4 stock Rom and successfully upgraded to Lollipop 5.0 using OTA. After couple of days I found 5.0.1 (Brazillian OTA) and try to upgrade but for some issues(network) I tried to downgrade to 5.0 and accidentally flash Brazillian 4.4.4 again. As a result my device was soft bricked(Hang on Boot). I managed to fix the brick using Android GPE and successfully installed kitkat 4.4.4(Asian stock edition). After the soft brick I can't flash any other Rom because it failed on gpt.bin and motoboot.img. So i can't upgrade to Lollipop again using Brazillian stock rom. Currently I am using Asian kitkat 4.4.4 stock Rom without any problem.
I checked build.prop file but it shows the exact fingerprint version that Asian lollipop OTA (sock test) asked for. Where is actually the fingerprint file and how can I change it?
Code:
ro.build.description=falcon_asia_ds-user 4.4.4 KXB21.14-L1.40 34 release-keys
ro.build.fingerprint=motorola/falcon_asia_ds/falcon_umtsds:4.4.4/KXB21.14-L1.40/34:user/release-keys
shantanucse18 said:
I am using Moto g (1st gen) Asian version (XT1033) with Android kitkat 4.4.4. When I tried to upgrade to lollipop (Asian sock test) using OTA, it returns an error that my current build is not
Code:
motorola/falcon_asia_ds/falcon_umtsds:4.4.4/KXB21.14-L1.40/34:user/release-keys
but
Code:
motorola/falcon_asia_ds/falcon_umtsds:4.4
History: My moto g originally comes with Android 4.3 and I upgraded to 4.4.4 via OTA(official) update. After release of Lollipop Brazilian OTA, I flashed my device with Brazillian 4.4.4 stock Rom and successfully upgraded to Lollipop 5.0 using OTA. After couple of days I found 5.0.1 (Brazillian OTA) and try to upgrade but for some issues(network) I tried to downgrade to 5.0 and accidentally flash Brazillian 4.4.4 again. As a result my device was soft bricked(Hang on Boot). I managed to fix the brick using Android GPE and successfully installed kitkat 4.4.4(Asian stock edition). After the soft brick I can't flash any other Rom because it failed on gpt.bin and motoboot.img. So i can't upgrade to Lollipop again using Brazillian stock rom. Currently I am using Asian kitkat 4.4.4 stock Rom without any problem.
I checked build.prop file but it shows the exact fingerprint version that Asian lollipop OTA (sock test) asked for. Where is actually the fingerprint file and how can I change it?
Code:
ro.build.description=falcon_asia_ds-user 4.4.4 KXB21.14-L1.40 34 release-keys
ro.build.fingerprint=motorola/falcon_asia_ds/falcon_umtsds:4.4.4/KXB21.14-L1.40/34:user/release-keys
Click to expand...
Click to collapse
Finally I figure out the problem. Custom recovery or other recovery except stock ROM can't update lollipop OTA. You have to flash the recovery of stock ROM. After flashing the stock recovery (4.4.4) everything is working just fine.
i, i installed asian rom 5.0.2 but it considered my phone as a dua sim and it was very annoying, so i decideted to come back to gpe (originally was gemarma retail), so i installed via fastboot 4.4.2 and i update by official ota update to 4.4.4, but when it was installing it the screen turned off and now the phone doesn't boot up, neither the bootloader.. why? what can i do to fix it?
My Boost Mobile Moto G won't install any ROMs. I had issues running PA 5.1 with the phone locking up so I wiped and tried to install the stock 4.4.4 Rom. In TWRP it says it won't install because the phone is a xt1032. Any idea how to correct this.
I never updated the bootloader, I just edited the 5.1 installer to skip the bootloader check.
I have a Moto G 2013 with a unlocked bootloader. German Retail and the Android Version was 5.0.2. I hate the look of lollipop. Because of this reason i flashed the 4.4.2 KitKat version via fastboot. After flashing I stucked at the "Unlocking Bootloader Screen". Then i read in many forums, that you can't downgrade because the bootloader versions are differnt. Now I installed TWRP via fastboot and right now i am using cm12.1. While i am wipping this device the recovery says that he can't mount system and other partitions. After searching the Lollipop Stock Rom i flashed the Lollipop version and the same problem. I would return to Stock Rom.
Thanks for all answers
Hello i have Motorola Moto G LTE XT1045 US AT&T ( Unlocked Network WorldWide )
i want to update firmware but.........
it has 4.4.4 stock firmware
i never touch it i always use it for calls or wifi
when i go system update it says that device has last version system but it has support for 5.1.1 official lollipop
now i want to update it manually
i need install Official stock ROM manually can u help me? please i need full tutorial
it does not have unlocked bootloader and is not rooted
have stock recovery too pleasee
You need to flash a custom recovery.Need to flash the TWRP 2.8.7.0 version and after flash manually the Lollipop stock Rom that is available here.I am giving you a optimized that is bloatware free but the choice is yours!
http://forum.xda-developers.com/devdb/project/dl/?id=14229
I don't think that the at&t model allows bootloader unlocking. If you can't unlock it, then you're stuck on 4.4.4 until they release it for that variant, which hasn't happened yet.