Related
http://youtu.be/faSg3puGssQ
download
http://www.mediafire.com/download/3..._recovery_6.13.19,_root,_drivers,_logo_fix.7z
basically this is a one click solution to flash a moto g into GPE, with a custom recovery, and boot logo fixed with every file included
hi, i just made this pack, in order to get an easy GPE rom with fixed logo and philz recovery with everything included for the flash ib 1 click, i just compiled some things so it can be easier for noobs and even no noobs to save time
the original idea came from this:
http://forum.xda-developers.com/showthread.php?t=2646404, but i wanted to add a custom recovery, logo fixed for unlocked devices, and have it all ready in a single package
features:
-4.4.2 rom GPE xt1032 stock
-adb files
-philz recovery falcon gpe philz_touch_6.13.9-falcon_gpe, you can replace the recovery for any other you want (using the same name for recovery) (i 100% recommend to use this included) warning read the last part of post
-supersu compatible with the philz recovery included for root (newer philz recovery does not work in gpe, also newer supersu cannot be flashed in the included recovery, you have to use this 2 versions included, trust me, later you still can update supersu)
-motorola drivers included, MotorolaDeviceManager_2.4.5
-logo fixed for unlocked devices (normal logo without the dumb unlocked blablabla info)
usage:
1)you need a moto g 1032xt with UNLOCKED BOOTLOADER, yes i mean you can use a stock moto g with motorola rom 4.4.2 or even a moto g GPE 4.4.2 if you want to restore the firmware as long as they are 1032xt, i don´t know about other models, my moto G are from amazon USA unlocked global gsm xt1032 16gb, if you are on 4.3 please update to oficial motorola rom 4.4.2, then you can use this
2)you need to install motorola drivers, included MotorolaDeviceManager_2.4.5, connect the phone on and let windows setup drivers, then off, then in bootloader in order to install drivers, if you don´t know what bootloader is, then please get out (ok noobs, bootloader is when the phone is off, press power + vol down for 3 secs and release, that is the bootloader)
3)after drivers, connect the phone in bootloader screen
4)execute in the PC GPE_XT1032_KOT49H.M004_CFC
5)wait............there are some purple lines of text like warnings, ignore them, don´t worry it is normal, wait until the end, unplug and press normal powerup or reboot the phone
6)phone should start into android welcome screen
optional (root)
7)in welcome screen or any other time, plug the phone and copy supersu into phone memory, power off the phone
8)boot into bootloader again, go to recovery, flash supersu (install zip, choose zip from sd card, select supersu.zip, yes install supersu.zip, wait some......................., press any key, reboot system now), restart, download supersu from playstore, done, you are root
WARNING about OTAs updates
no matter what firmware you use, if you have custom recovery, do not update the phone via OTA, i repeat DO NOT UPDATE
flash a stock recovery, then update via OTA, else the phone will be in a boot loop
thanks
dashiell.cano, for discovering that way of flash
Phil3759, for custom recovery
alonsoch, for moto g tool
This isn't a rom, it is just a guide.
thelegendofzeth said:
This isn't a rom, it is just a guide.
Click to expand...
Click to collapse
i was uploading the files
will it work on xt1033?
dark ryder said:
will it work on xt1033?
Click to expand...
Click to collapse
Yes
Could you give a link to the fixed boot logo?
mrbloog said:
Could you give a link to the fixed boot logo?
Click to expand...
Click to collapse
download the entire file and get the logo from the zip
dark ryder said:
will it work on xt1033?
Click to expand...
Click to collapse
i have no idea but some dude said it will
added a little info on OP, corrected text mistakes
Hi I am running SlimRom but want too go to GPE will it delete my music + photos etc?
abell431 said:
Hi I am running SlimRom but want too go to GPE will it delete my music + photos etc?
Click to expand...
Click to collapse
yes, everything is deleted
ive tryed dozons of roms in the last couple of week & mobile date or gps has not works on all of them
but this rom works fine on my uk o2 xt1032 devise just fm radio was missing but added Spirit2 which works fine
thanks
scdsone said:
ive tryed dozons of roms in the last couple of week & mobile date or gps has not works on all of them
but this rom works fine on my uk o2 xt1032 devise just fm radio was missing but added Spirit2 which works fine
thanks
Click to expand...
Click to collapse
there is no radio on any GPE rom
maurocds said:
there is no radio on any GPE rom
Click to expand...
Click to collapse
is there a reason why they dont add it in any GPE rom?
Can you add a link for the stock recovery? Thanks!
please, is it based on 176.44.1 or older???
thanks
myabc said:
please, is it based on 176.44.1 or older???
thanks
Click to expand...
Click to collapse
GPE has only 1 version until now, this is not motorola rom, is GPE like nexus
Ballesss said:
Can you add a link for the stock recovery? Thanks!
Click to expand...
Click to collapse
look the forums, there are 3 custom recovery, i like philz
scdsone said:
is there a reason why they dont add it in any GPE rom?
Click to expand...
Click to collapse
because there are 1000 apps for it on the store, why bother, no ones uses that, listen to ads lol, no way
maurocds said:
look the forums, there are 3 custom recovery, i like philz
Click to expand...
Click to collapse
Yes, but you have said that we can't use the OTA's if we dont have a stock recovery. Where can i found it?
Ballesss said:
Yes, but you have said that we can't use the OTA's if we dont have a stock recovery. Where can i found it?
Click to expand...
Click to collapse
no one can be sure 100% about otas since the GPE has not had none
and sorry, i did not read well, i though you mean custom recoveries
if you want stock GPe or motorola recovery, then download a stock firmware and unzip the files, extract the recovery and you can replace the one i included
sorry, but it is something easy, i dont want to upload that, maybe later
just wanted to say that i updated my phone to 4.4.4 using this but with the stock gpe recovery (i am not sure if philz recovery works), will post on the main post
http://www.mediafire.com/download/hbyk97y9250cuus/recoveries.7z
included
stock 4.4.2 moto g GPe recovery, and latest philz recovery 6477
Please note: I know there are other guides here on XDA but none worked for me, so I'm writing this to help other stuck people.
Disclaimer: I tested this on my XT1032, I don't know if or how it will work on other variants. Following this guide you'll lose all data on your phone, make sure to backup important stuff. I'm not responsible for what you do to your phone following this guide (anyway if you're here probably you have not much to lose...)
Introduction
What happened: a couple of weeks ago I wanted to try GPE rom on my XT1032, so I flashed the appropriate rom for my device (4.4.3 KOT49H.M004) and then applied OTA (4.4.3 KOT49H.M004 to 4.4.4 KTU84P.M003). Today I decided to go back to stock, so I rebooted in bootloader mode and tried to flash stock 4.4.3.
Result: a bunch of fastboot errors, ranging from "wrong size partitions", to "preflash validation failed", to ... well I don't remember all of them, as I said they were a lot..
Then I tried older versions, I tried to reflash 4.4.3 GPE, I tried to follow guides, here on XDA and around the vast internet.. All with no luck. Until I found one and, long story short I did it. I'm back to stock 4.4.4 (flashed stock 4.4.3 and applied OTA)
I'm sharing this what I did to recover from the soft-brick, hoping to help someone. This guide is not a temporary workaround while waiting for full 4.4.4 GPE image, this will fully restore your Moto G.
Let's start
- Make sure you have fastboot drivers installed (if you managed to soft-brick it you probably have them already installed, otherwise you can get them here)
- Download and extract this
- Reboot your phone in fastboot mode (keep Volume Down and Power buttons pressed for about 5 seconds then release the power button) and plug it to the PC
- Open the extracted folder and run "GPE_XT1032_KOT49H.M004_CFC.bat". Wait for it to finish (ignore errors, they're normal), then reboot to bootloader again (choose Normal powerup and keep pressed Volume Down until it boots to bootloader again)
- Download and extract this (mirror)
- Open the extracted folder and run THE FILE "fastboot flash recovery recovery.img.bat" (poorly chosen filenames, I know)
- Wait for it to finish, then choose "Recovery" item in bootloader and let it reboot to recovery.
- Go to "mounts and storage" and select "format cache", confirm, then select "format /data and /data/media", confirm.
- Go back to main menu and select "wipe data/factory", confirm.
- Return to the folder and run the file "adb push a.zip sdcard a.zip.bat", let it finish (it will take a couple of minutes, the window will close itself when done).
- From recovery select "install zip", then "choose zip from sd card" and select "a.zip". Let it finish, then go back to main menu and choose "power options", then "reboot to bootloader"
- Download and extract this (mirror)
- Open the extracted folder and run "flashall.bat". You should see no error (I got an error while it was flashing recovery but this is not important, what you should notice is that all the errors you got before are gone). Let it finish, then give it some time to boot.
Enjoy
You're done. Now you should have a stock 4.4.2 retail EU moto g. At this point you can flash the rom you want (for example, I flashed the original retail de, since my phone is german) without getting errors
---------------------------------------------------------------------------------------------------------
More or less I followed this, but I wrote the exact steps I made, I fixed wrong commands and uploaded a more complete version for last file
i have the same problem... i am waiting for thoe missing files... and i will try to go back to stock
EDIT i can't download the filles from mega
and the first download is broken
bannab said:
i have the same problem... i am waiting for thoe missing files... and i will try to go back to stock
EDIT i can't download the filles from mega
and the first download is broken
Click to expand...
Click to collapse
I fixed first link, I'm going to check the one from mega... If you find some other problems please let me know so I'll update
Edit: mega link is working. I suppose you're from Italy (me too), it's a DNS problem (mega has been blocked by AGCOM). you can follow this guide to change dns to google ones (8.8.8.8 and 8.8.4.4). When you downloaded the file you can set them back to auto. If someone can suggest an alternative good host (and possibly a way to directly upload from mega (I have a veeeeery slow upload bandwidth) I'll appreciate
i have already tried that method but no luck..
bannab said:
i have already tried that method but no luck..
Click to expand...
Click to collapse
Try with tor bundle.. It's a version of firefox modified for privacy and security purposes, you should be able to download from mega with it
Or this
nope
again lo luck for me.. flash of stock gives me always the same errors.. i think i will keep gpe with root... and wait for a camera with slow-mo..
bannab said:
again lo luck for me.. flash of stock gives me always the same errors.. i think i will keep gpe with root... and wait for a camera with slow-mo..
Click to expand...
Click to collapse
Did you follow exactly the guide? Did you get errors while wiping or flashing a.zip from recovery?
flashing stock
maybe beacuse i have booted after flashing gpe... i needed to boot it beacuse adb gives me error (device not found)
so i will keep gpe
bannab said:
flashing stock
maybe beacuse i have booted after flashing gpe... i needed to boot it beacuse adb gives me error (device not found)
so i will keep gpe
Click to expand...
Click to collapse
That is due to drivers.. OK, in case you do it again, check recovery messages to be sure it's doing its things
You saved my phone, thank you ! :victory:
JcruzV said:
You saved my phone, thank you ! :victory:
Click to expand...
Click to collapse
You're welcome.. That little heart attack when you see it's not booting and it doesn't flash anything [emoji1]
It worked! Thank you.
doodoo28s said:
It worked! Thank you.
Click to expand...
Click to collapse
Glad I helped
Thank's my Friend ! You have save my phone ! Thank youuuuuuu !!!!!!! <3
Hello.I tried to root my device with superboot and now my phone is not booting up,i tried to reboot but still the same,my screen stays black.Can this fix my phone? thnks
Nicolae-Daniel said:
Hello.I tried to root my device with superboot and now my phone is not booting up,i tried to reboot but still the same,my screen stays black.Can this fix my phone? thnks
Click to expand...
Click to collapse
This is useful if you can't flash anything. If you can, you can just flash stock or custom ROM
i suceed come back to 4.4.2 stock!!! thank you!!!!
finally a fix
thanks for posting this fix and all the others involved. i'm on EU so now i have to get back to my regular 4.4.4 Google Play Edition. this is good till i can get that back. been trying for 2 weeks to unbrick this thing and now i have it. thanks again and to the member JcruzV who linked this post. and not to forget PhilZ. :good:
bootsie35 said:
thanks for posting this fix and all the others involved. i'm on EU so now i have to get back to my regular 4.4.4 Google Play Edition. this is good till i can get that back. been trying for 2 weeks to unbrick this thing and now i have it. thanks again and to the member JcruzV who linked this post. and not to forget PhilZ. :good:
Click to expand...
Click to collapse
Didn't know this was linked in other threads
I hope this will be sticked or something, to avoid being forgotten in a couple of months. When I was searching how to unbrick I read of people who gave up and bought a replacement, wasting money when fortunately there is a solution
It did work!
I used Linux, so had to change a few things in the command files.
There are also two things:
1.
adb push a.zip /sdcard/a.zip - no apsce before the 2nd a.zip
2.
after the 3rd step recovery complains about "new ROM will overwrite recovery" - I have answered Yes.
I have got also another problem. Meanwhile I tried to recover my phone after the downgrade from 4.4.4 GPE to 4.4.2 Motorola ROM (before this thread), I have lost the IMEI... Currently it's still 0.
Anyone have an idea to recover this?
Hello everyone, I have a Moto G (2013) aka first generation Moto G & I live in India. I had unlocked my bootloader. I even flashed cwm touch via fastboot but it doesn't go to recovery mode at all. I get a black screen. I tried flashing the official TWRP 2.8.4.0 today, but I get a message that reads, "Partition size mismatch" & I'm stuck. The phone is usable & it boots up normally & I use it daily. But it is the recovery that is messed up. I tried updating to lollipop by ota but the device got stuck on a black screen once the ota was downloaded. I tried downloading the KitKat factory image, but the link is dead. Please, somebody help!! Thanks in advance!
Sent from my XT1033 using xda premium
The partition size mismatch error can be ignored, You get that error because the TWRP 2.8.4.0 is for the XT1032 and not the XT1033. To flash the OTA, you have to use the stock recovery only. Your system should not be modified (eg. It shouldn't be rooted, and if it had been rooted previously, you will have to unroot it.) To flash the stock recovery again, download the Asian XT1033 4.4.4 firmware and just flash the "recovery.img" from it. The flash the OTA. The numerous guides regarding this in the general section should help you.
I have a similar question.
I have unlocked bootloader & rooted moto g.
I received official OTA update today but its not installing. Do I need to lock bootloader or do something else to install the official OTA update?
Facing a similar issue. Updated the moto g and was successful. It was used for a couple of days before the error cropped up.
Now, it boots up but goes to a black screen after the boot animation. However, it still connects to the computer and I'm able to see the phone and its files in explorer. Beyond that, I can't interact with the phone because the screen is totally black.
Additionally, I can access the bootloader, but selecting 'factory' or 'recovery' isn't doing anything - just black screens everywhere.
The phone was perfectly fine for a few days after the update. (The phone is unrooted and unmodded and was running stock at lolipop update.)
Another thread suggests that I should
Code:
fastboot erase cache
fastboot erase userdata
Is that a viable course of action? Has anybody been able to recover from this issue?
pr.itdude said:
I have a similar question.
I have unlocked bootloader & rooted moto g.
I received official OTA update today but its not installing. Do I need to lock bootloader or do something else to install the official OTA update?
Click to expand...
Click to collapse
No need to lock. Unroot, reflash stock signed recovery and you should be good to go. Also undo any modifications you made to the filesystem and wiping /cache should help prevent errors.
---------- Post added at 02:42 AM ---------- Previous post was at 02:40 AM ----------
SoberDogs said:
Facing a similar issue. Updated the moto g and was successful. It was used for a couple of days before the error cropped up.
Now, it boots up but goes to a black screen after the boot animation. However, it still connects to the computer and I'm able to see the phone and its files in explorer. Beyond that, I can't interact with the phone because the screen is totally black.
Additionally, I can access the bootloader, but selecting 'factory' or 'recovery' isn't doing anything - just black screens everywhere.
The phone was perfectly fine for a few days after the update. (The phone is unrooted and unmodded and was running stock at lolipop update.)
Another thread suggests that I should
Code:
fastboot erase cache
fastboot erase userdata
Is that a viable course of action? Has anybody been able to recover from this issue?
Click to expand...
Click to collapse
Try fastboot erase cache, it shouldn't delete any of your data and it might be enough to get the device working again. You might want to wipe the dalvik-cache as well. If all else fails, since you can access you filesystem, backup all important files and do a factory reset.
skyguy126 said:
No need to lock. Unroot, reflash stock signed recovery and you should be good to go. Also undo any modifications you made to the filesystem and wiping /cache should help prevent errors.
Click to expand...
Click to collapse
Ok. Few more Q pls:
1. Reflashing stock recovery wipes system data & apps? After this my phone will be rooted or not? Any links where i can read more about it?
2. I have stock ROM but yes I installed xposed framework & few modules. Is it a filesystem modification?
3. Any other alternative to this?
pr.itdude said:
Ok. Few more Q pls:
1. Reflashing stock recovery wipes system data & apps? After this my phone will be rooted or not? Any links where i can read more about it?
2. I have stock ROM but yes I installed xposed framework & few modules. Is it a filesystem modification?
3. Any other alternative to this?
Click to expand...
Click to collapse
1. No it should not. If you had root before you will still have it. Search in the forum for more info.
2. Yes but you can easily uninstall xposed with the click of a button.
3. This is by far the easiest and safest method. I know of one alternative is to flash the ota update zip through custom recovery but you are on your own there.
skyguy126 said:
1. No it should not. If you had root before you will still have it. Search in the forum for more info.
2. Yes but you can easily uninstall xposed with the click of a button.
3. This is by far the easiest and safest method. I know of one alternative is to flash the ota update zip through custom recovery but you are on your own there.
Click to expand...
Click to collapse
ok so Here what i am planning:
1. Uninstall all modules & xposed framework
2. Unroot using supersu
3. Restore/reflash stock recovery (just recovery not whole firmware as I already have stock rom)
4. Install the update either manually via recovery or using auto install.
Am i on right path? Pls help me on step 3, any link or step-t-step guide? I couldn't find one, every post is abt restoring whole firmware.
TIA. Cheers !!
pr.itdude said:
ok so Here what i am planning:
1. Uninstall all modules & xposed framework
2. Unroot using supersu
3. Restore/reflash stock recovery (just recovery not whole firmware as I already have stock rom)
4. Install the update either manually via recovery or using auto install.
Am i on right path? Pls help me on step 3, any link or step-t-step guide? I couldn't find one, every post is abt restoring whole firmware.
TIA. Cheers !!
Click to expand...
Click to collapse
Yep you should be good good luck!!!
Apologies if this has been asked before but I can't seem to find the answer. I've read this post but it seems more complicated than it needs to be...
I've got an unlocked, rooted xt925.
I'm on CM11 JBBL nightlies (with CWM Recovery) and I want to move to CM12, which I believe means I need to revert from JBBL to KKBL first.
Is that correct?
If so, can I just download the KKBL firmware and flash it? Or do I have to use some other process? I'm on a Mac so I can't use PC-based tools (although I can use adb etc).
And where can I download KBBL from?? And will I lose root?
Thanks...
SamuriHL is the man. He has an updated HoM 4.1 that makes it somewhat easier, but it still involves flashing the FXZ, setting up custom recovery, re-rooting, etc... He has MAC "notes" in the thread, Im not sure if I can link the other forum its on, but f you google house of mot 4.1, it is (or was in my case) the first result
I was on the JBBL and 5.0.2 Validus ROM, but upgraded my BL to KK yesterday and Im running CM 12. So far I am loving it.
updated bootloader
jlang11 said:
SamuriHL is the man. He has an updated HoM 4.1 that makes it somewhat easier, but it still involves flashing the FXZ, setting up custom recovery, re-rooting, etc... He has MAC "notes" in the thread, Im not sure if I can link the other forum its on, but f you google house of mot 4.1, it is (or was in my case) the first result
I was on the JBBL and 5.0.2 Validus ROM, but upgraded my BL to KK yesterday and Im running CM 12. So far I am loving it.
Click to expand...
Click to collapse
Could you please tell me, what KK bootloader you are using now? I'm still not able to get CM 12. "...needs bootloader 4.4..."
xMandy said:
Could you please tell me, what KK bootloader you are using now? I'm still not able to get CM 12. "...needs bootloader 4.4..."
Click to expand...
Click to collapse
What I suggest as it worked for me, find SamuriHL's House of Moto 4.1, follow the directions to a T, as he says read, read, and read again, and use the firmware (FXZ) XT926_4.4.2-KDA20.62-10.1_CFC_1FF.xml. The bootloader kernel is 3.4 that was upgraded on our phones with that version of the firmware. Do a google search for House of Moto 4.1 and it should be easy to find.
XT925 or XT926
jlang11 said:
What I suggest as it worked for me, find SamuriHL's House of Moto 4.1, follow the directions to a T, as he says read, read, and read again, and use the firmware (FXZ) XT926_4.4.2-KDA20.62-10.1_CFC_1FF.xml. The bootloader kernel is 3.4 that was upgraded on our phones with that version of the firmware. Do a google search for House of Moto 4.1 and it should be easy to find.
Click to expand...
Click to collapse
thanks so far!
But why are you using a XT926-FXZ and not some for the XT925?
Any hint how to find out which one is the one I should use? ADB says "vanquish_u"... :silly:
...still trying...
xMandy said:
thanks so far!
But why are you using a XT926-FXZ and not some for the XT925?
Any hint how to find out which one is the one I should use? ADB says "vanquish_u"... :silly:
...still trying...
Click to expand...
Click to collapse
Because I have the xt926
If you have xt925, then make sure you use the correct firmware for your phone...
Hey guys, i'm trying the same, and i don't get it working.
Phone is an unlocked xt925.
Could upgradeto KKBL but now nothing works to get cm12 working, always get bootloops...
virgin xt925
jlang11 said:
Because I have the xt926
If you have xt925, then make sure you use the correct firmware for your phone...
Click to expand...
Click to collapse
as far as I see, the House of Moto does the same as RSD lite - it brings the RAZR back to "a minty factory fresh state" - means 4.1.2. with JBBL.
After that you did the OTA update to 4.4.2.? Is this the trick to get KKBL? Trying to use twrp didn't work for me (still on 4.1.2), the screen was frozen, no touch, no reaction. . .
Didn't get to 4.4.2 so far or was not able to flash a recovery that supports CM 12. :crying:
It would be great if you will share your secret :fingers-crossed:
thx
xMandy said:
as far as I see, the House of Moto does the same as RSD lite - it brings the RAZR back to "a minty factory fresh state" - means 4.1.2. with JBBL.
After that you did the OTA update to 4.4.2.? Is this the trick to get KKBL? Trying to use twrp didn't work for me (still on 4.1.2), the screen was frozen, no touch, no reaction. . .
Didn't get to 4.4.2 so far or was not able to flash a recovery that supports CM 12. :crying:
It would be great if you will share your secret :fingers-crossed:
thx
Click to expand...
Click to collapse
As far as HoM being the same as RSD lite, it mat very well be similar. If you are familiar with RSD by all means use that utility. SamuriHL wrote the scripts for flashing FXZ's and worked hard at making it easy for "n00bs" like myself to upgrade their phones.
As far as flashing back to "minty factory fresh" state, if you are flashing the correct FXZ, you are not flashing 4.1.2, you would be flashing 4.4.2 (see previous post mentioning XT926_4.4.2-KDA20.62-10.1_CFC_1FF.xml) so no you are not OTA to 4.4.2. The 4.4.2 FXZ HAS the KKBL.
All this is assuming you are already UNLOCKED.
I am in NO WAY an expert, and actually I am a n00b myself. Just trying to point you in the right direction. Go back and read the post, then read it again (as SamuriHL states in his post).
xMandy said:
as far as I see, the House of Moto does the same as RSD lite - it brings the RAZR back to "a minty factory fresh state" - means 4.1.2. with JBBL.
After that you did the OTA update to 4.4.2.? Is this the trick to get KKBL? Trying to use twrp didn't work for me (still on 4.1.2), the screen was frozen, no touch, no reaction. . .
Didn't get to 4.4.2 so far or was not able to flash a recovery that supports CM 12. :crying:
It would be great if you will share your secret :fingers-crossed:
thx
Click to expand...
Click to collapse
xMandy said:
thanks so far!
But why are you using a XT926-FXZ and not some for the XT925?
Any hint how to find out which one is the one I should use? ADB says "vanquish_u"... :silly:
...still trying...
Click to expand...
Click to collapse
OK, so here is a little explanation, followed by a link on how to upgrade xt925 or 926 to 4.4.2
So HoM and RSD-Flasher are almost the same as RSD-Lite, they have a little more functions and so on. Everything you might wanna do with RSD-Lite u can do with these two tools.
XMandy: You can find out your version this way: settings -> about phone -> system version. At least on my phone it states xt925
Here is how i upgraded my xt925 to stock 4.4.2 i would recommend to be BL unlocked, but it seems like there are ways to unlock and root 4.4, so that is not that important.
Guide
With everything else from that point on i also got my problems, thats why i'm here in the first place but probably after upgrading you guys can help me too
so far - so bad
esok44 said:
OK, so here is a little explanation, followed by a link on how to upgrade xt925 or 926 to 4.4.2
So HoM and RSD-Flasher are almost the same as RSD-Lite, they have a little more functions and so on. Everything you might wanna do with RSD-Lite u can do with these two tools.
XMandy: You can find out your version this way: settings -> about phone -> system version. At least on my phone it states xt925
Here is how i upgraded my xt925 to stock 4.4.2 i would recommend to be BL unlocked, but it seems like there are ways to unlock and root 4.4, so that is not that important.
Guide
With everything else from that point on i also got my problems, thats why i'm here in the first place but probably after upgrading you guys can help me too
Click to expand...
Click to collapse
I did this several times now. . .
XT 925, VANQUISH_U, unlocked BL:
# Clean install of 4.1.2. with RSD lite and zip-file 9.8.2Q-8-XT925_VQU-22_USERSIGNED_S7_UCAVANQU02NA02F.0R_LSAVNQJBRTFR_P007_A004_CFC.xml
=> works, with result JB 4.1.2
# OTA update
=> restart folowed by bootloader with message:
Device is LOCKED, Status Code: 0
downgraded security version
update gpt_main version vailed
Failed to hab check for gpt_backup: 0x35
failed to load GPT
CID Read Failure
Invalid CID status 0x69
No SP partition found
Fastboot Reason: Invalid GPT
# fastboot flash partition gpt.bin
# fastboot flash tz tz.mbn
# fastboot reboot-bootloader
=> works, with result Device is UNLOCKED, Status Code: 3
# fastboot reboot
=> works, with result KK 4.4.2, version 180.46.117.XT925.CEE-Retail.en.EU
# second OTA update
=> works, with result KK 4.4.2, version 180.46.127.XT925.CEE-Retail.en.EU, build number KDA20.127
==> so far everything is fine
# flashing recovery TWRP-2.8.4.1-xt925.img
=> works, with result recovery boot TWRP is posible and "install from zip" too
# wipe to factory reset
# wipe cache / repair cache
# install zip cm-12-20150217-NIGHTLY-xt925.zip
# install zip gapps-lp-20141220-signed.zip
# reboot to system
==> rebooting and bl warning
==> starting the ignition and looooooop
==> shows the CM 12 logo, is "active" and does this for hours if I won't stop it
So, where's my fault?
Heyho,
The mistake is not on your side. Its what i have stated before:
To not get the bootloop after installing cm12 u must Flash it over cm11. Currently i was not able to find a cm11 Version for kkbl which i could install on the xt925. I Asked i several Threads, regarding this topic and Noone helped/could help me so far
Sorry i thought your mistake was some where else
Sent from my RAZR HD using XDA Free mobile app
getting closer
esok44 said:
Heyho,
The mistake is not on your side. Its what i have stated before:
To not get the bootloop after installing cm12 u must Flash it over cm11. Currently i was not able to find a cm11 Version for kkbl which i could install on the xt925. I Asked i several Threads, regarding this topic and Noone helped/could help me so far
Sorry i thought your mistake was some where else
Sent from my RAZR HD using XDA Free mobile app
Click to expand...
Click to collapse
Sorry to ask again...
Where's the step i have to insert the flash of CM 11?
As far as i know with twrp.2.8.2.1 (KKBL) it's not posible to flash CM 11?
So. . . will this way do it?
# 4.4.2 stock
# flash recovery for jbbl (for example CW6.0.4.4)
# flash CM 11
# flash recovery for kkbl (twrp.2.8.2.1)
# flash CM 12
With some jbbl and CM 11 on the phone i was not able to use the CM 12 update - neither OTA nor recovery flash.
and again a big :good::good::good:
esok44 said:
Heyho,
The mistake is not on your side. Its what i have stated before:
To not get the bootloop after installing cm12 u must Flash it over cm11. Currently i was not able to find a cm11 Version for kkbl which i could install on the xt925. I Asked i several Threads, regarding this topic and Noone helped/could help me so far
Sorry i thought your mistake was some where else
Sent from my RAZR HD using XDA Free mobile app
Click to expand...
Click to collapse
No one posted a logcat of the boot failure yet, afaik.
I can clean flash a cm12 xt925 build just fine.
Unless the logs are provided, it won't get fixed (as long as it's not reproducible by the devs).
kabaldan said:
No one posted a logcat of the boot failure yet, afaik.
I can clean flash a cm12 xt925 build just fine.
Unless the logs are provided, it won't get fixed (as long as it's not reproducible by the devs).
Click to expand...
Click to collapse
I'm having the exact same problem, except on my XT926M.
I was on an unlocked XT926M running 4.1.2 stock Verizon. Yesterday I installed the FXZ 4.4.2 ROM with RSD Lite to upgrade the bootloader to KKBL. It works fine on 4.4.2 (183.46.15.XT926.Verizon.en.us)
Today I tried installing TWRP 2.8.4.2 and installing the latest CM12 nightly (Feb 17). I created a backup with TWRP, factory wiped , and flashed the CM12 image through TWRP. It succeeded flashing, but got stuck on the boot screen. After 20 minutes, I powered it off, tried turning it on again...stuck for another 10. Tried mounting the system partition in TWRP, doing an advanced wipe of system, data (NOT internal storage), and cache, but even that didn't work. Eventually after two hours of reflashing and draining my battery to 75% I decided to restore my TWRP 4.4.2 stock backup so I would have a phone to use again.
I can't post in the actual dev thread where people were talking about this. I would love to help troubleshoot this issue if they would direct me.
kabaldan said:
No one posted a logcat of the boot failure yet, afaik.
I can clean flash a cm12 xt925 build just fine.
Unless the logs are provided, it won't get fixed (as long as it's not reproducible by the devs).
Click to expand...
Click to collapse
Hey Kabaldan,
i wiill provide a logcat later today.
Will just give the most recent cm12 Version a shot.
A logcat will be posted
Thanks for your interest in helping us
I actually found a user on the droidrzr forums who has the same issue in a thread for the Dirty Unicorns Lollipop ROM.
You can see the logs he posted of the window here:
droidrzr.com/topic/56216-romofficialdirty-unicornsv91502moto-msm8960kk-bl21015/page-21#entry491765
This is only a few days old. There's a few others in the thread who were chiming in with the same problem. So far not much progress.
another try
kabaldan said:
No one posted a logcat of the boot failure yet, afaik.
I can clean flash a cm12 xt925 build just fine.
Unless the logs are provided, it won't get fixed (as long as it's not reproducible by the devs).
Click to expand...
Click to collapse
again on-the-fly
XT925, KK 4.4.2 stock, clean, BL unlocked, SuperSu installed, twrp v2.8.4.2 running
# install
# external_sd/#source/+rom und root/cm-12-20150217-NIGHTLY-xt925.zip
# swipe to confirm flash
=> result on screen:
Installing '/external_sd/#source/+rom und root/cm-12-20150217-NIGHTLY-xt925.zip'
Checking for MD5 file. . .
Skipping MD5 check: no MD5 file found
detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system
detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system
script succeeded: result was [0.200000]
Updating partition details. . .
. . .done
# Wipe cache/dalvik
# swipe to wipe
=> result on screen:
Wiping Dalvik Cache Directories. . .
Cleaned: /data/dalvik-cache. . .
- - Dalvik Cache Directories Wipe Complete!
Updating partition details. . .
. . .done
# back
# return
# external_sd/#source/+rom und root/gapps-lp-20141220-signed.zip
# swipe to confirm flash
=> result on screen:
Installing 'external_sd/#source/+rom und root/gapps-lp-20141220-signed.zip'. . .
Checking for MD5 file . . .
Skipping MD5 check: no MD5 file found
*****************************************
Google Apps for Android 4.4.2
*****************************************
Installing files . . .
Cleaning up and setting metadata . . .
Installation complete!
Upddating partition details . . .
. . .done
# Wipe cache/dalvik
# swipe to wpe
=> result on screen:
Cleaned: /data/dalvik-cache. . .
- - Dalvik Cache Directories Wipe Complete!
Updating partition details. . .
. . .done
# Back
# Reboot System
==> result:
BOOTING !
=> first time the phone is booting and installing the apps
=> results on screen:
process " . . . several during the boot . . ." was aborted
System UIDs Inconsistent
UIDs on the system are inconsistent, you need to wipe your data partition or your device will be unstable
=> result after booting:
some com.google.processes were aborted, for example "com.google.phone"
# reboot in recovery twrp 2.8.4.2
# wipe
# data
# swipe to confirm
# reboot to system
==> result: BOOTLOOOOOOP
Can anyone tell me what's goin' on?
xMandy said:
again on-the-fly
XT925, KK 4.4.2 stock, clean, BL unlocked, SuperSu installed, twrp v2.8.4.2 running
# install
# external_sd/#source/+rom und root/cm-12-20150217-NIGHTLY-xt925.zip
# swipe to confirm flash
=> result on screen:
Installing '/external_sd/#source/+rom und root/cm-12-20150217-NIGHTLY-xt925.zip'
Checking for MD5 file. . .
Skipping MD5 check: no MD5 file found
detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system
detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system
script succeeded: result was [0.200000]
Updating partition details. . .
. . .done
# Wipe cache/dalvik
# swipe to wipe
=> result on screen:
Wiping Dalvik Cache Directories. . .
Cleaned: /data/dalvik-cache. . .
- - Dalvik Cache Directories Wipe Complete!
Updating partition details. . .
. . .done
# back
# return
# external_sd/#source/+rom und root/gapps-lp-20141220-signed.zip
# swipe to confirm flash
=> result on screen:
Installing 'external_sd/#source/+rom und root/gapps-lp-20141220-signed.zip'. . .
Checking for MD5 file . . .
Skipping MD5 check: no MD5 file found
*****************************************
Google Apps for Android 4.4.2
*****************************************
Installing files . . .
Cleaning up and setting metadata . . .
Installation complete!
Upddating partition details . . .
. . .done
# Wipe cache/dalvik
# swipe to wpe
=> result on screen:
Cleaned: /data/dalvik-cache. . .
- - Dalvik Cache Directories Wipe Complete!
Updating partition details. . .
. . .done
# Back
# Reboot System
==> result:
BOOTING !
=> first time the phone is booting and installing the apps
=> results on screen:
process " . . . several during the boot . . ." was aborted
System UIDs Inconsistent
UIDs on the system are inconsistent, you need to wipe your data partition or your device will be unstable
=> result after booting:
some com.google.processes were aborted, for example "com.google.phone"
# reboot in recovery twrp 2.8.4.2
# wipe
# data
# swipe to confirm
# reboot to system
==> result: BOOTLOOOOOOP
Can anyone tell me what's goin' on?
Click to expand...
Click to collapse
The Problem with the google apps is that u usd the ones for androdi 4.4.2, i guess u need the ones for android 5...
Sorry Mandy, i was wrong, it was not a faulty gapps Version. I dont know The nistake, but i will try to pull a logcat later when i got a little more battery
Sent from my RAZR HD using XDA Free mobile app
The phone is a normal first gen moto g 8gb which i tried to turn into a gpe phone to get lollipop but failed....
This is the boot loop: http://i.imgur.com/LXHY7D3.jpg
Lucky i can still get into fastboot: http://i.imgur.com/869jRVD.jpg
And recovery is: http://i.imgur.com/CV0QuOw.jpg
i have the right software and firmware i need to flash i just can't get into adb mode something is wrong with recovery.. i guess..
To fix the issue, I recommend using fastboot commands to flash a stock 4.4.4 ROM and then check for 5.02 OTA updates for the stock ROM.
Awesome idea any decent guides on here for this? My searches fail
Flashing stock: http://forum.xda-developers.com/showthread.php?t=2542219
Possible source for ROM: http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=filename&order=ASC&show=100&page=1
audit13 said:
Flashing stock: http://forum.xda-developers.com/showthread.php?t=2542219
Possible source for ROM: http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=filename&order=ASC&show=100&page=1
Click to expand...
Click to collapse
should i use:
XT1032_RETAIL-EU_4.4.4_KXB21.14-L1.40_36_cid7_CFC_1FF.xml
or
XT1032_RETAIL-GB_4.4.4_KXB21.14-L1.40_36_cid7_CFC_1FF.xml
i'm in England (so both eu and gb apply) so really not sure which.... i guess i'll try gb first
You could try either one if they are made for the xt1032 you have.
audit13 said:
You could try either one if they are made for the xt1032 you have.
Click to expand...
Click to collapse
I chose 'gb' and excellent i'm now on a working firmware for the first time in a month+ so i thank you for that i really do
next problem is it's 4.4.4 and not lollipop and says it's 'up to date' when i check for an update boo.. how do i get lollipop?
Did you log into the Play store and update all Motorola apps, particulary Motorola Update services? You must be unrooted and running stock recovery in order for the update to install.
audit13 said:
Did you log into the Play store and update all Motorola apps, particulary Motorola Update services? You must be unrooted and running stock recovery in order for the update to install.
Click to expand...
Click to collapse
no i did not... doing that now :fingers-crossed::good:
audit13 said:
Did you log into the Play store and update all Motorola apps, particulary Motorola Update services? You must be unrooted and running stock recovery in order for the update to install.
Click to expand...
Click to collapse
i sure did i had stock recovery and logged into my Google account and updated ALL apps in the play store and rebooted a couple time but still no update when i checked
i then manually searched for 'Motorola Update services' and it guess what? it needs an update yet it's not in the 'my apps' list in the play store? odd.. but anyway i updated it... then tried a manual update and boom 5.02
let see if it all installs ok.. is there any xposed for lollipop/art yet? even alpha/beta/etc?
Everything worked perfectly thank you
http://i.imgur.com/qGnVRmj.jpg
one last problem it seems no mater what recovery i install it just causes 'wavy lines on the screen' :/
my phone: http://i.imgur.com/fHs9rrD.jpg
The lines are due to the custom recovery not fully supporting the lollipop bootloader. Keep checking the recovery thread for updates.
The lines should not appear with stock recovery.
Sorry to be a pain but do you have links to both? I'm on mobile atm
Sorry, I don't have a link for the stock recovery.
Here's a link for TWRP: http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621
Link for Philz Touch Recovery: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/falcon/
I got it working then i broke it again
I got everything setup and played with lollipop extensively and really liked it although 'over the hood' very little has changed (mostly the notification panel)
I then decided I'd try to install the xposed alpha and boom dead phone :/
No big deal i thought I'll just do the same 4.4.4 install i originally did via fastboot but now I'm stuck at a boot loop
I think the flash memory is corrupted
Fastboot and custom recovery if course still work but when i try to do simple things like clear cache/dalvik i get file system errors like crazy: http://imgur.com/a/wc75k
Any ideas what i can do next?
Edit: added pics
Sorry. Maybe it's brick.
Fastboot commands don't work to re-install stock 4.4.4?
Maybe u fixed it already but here is a guide to repair ur phone. http://forum.xda-developers.com/showthread.php?t=2542219 worked for me too.