**Bear with me as this is my first unlocking/rooting endeavor!**
I bought a brand new Moto G (XT1031) for Boost Mobile. It came with KitKat 4.4.4 pre-installed. I researched/followed guides and was able to unlocked it.
More research was done. I flashed the recovery software TWRP v2.8.6 via ADB fastboot. I then flashed SuperSU v2.46 via TWRP(zip file). Back up was created with TWRP. Attempted to install CyanogenMod 12.1, however, my bootloader version is "4113" so it said it was not supported. It seemed like changing the bootloader was a bad idea, so I did not pursue that idea. I tried to install CM 12, it was successful. I proceeded to install the gapps version for CM12. I rebooted the system.
It stayed on the boot screen(blue robot head) for a hour. I shut off and restarted the phone, it sat on the boot screen for about 30 minutes. It would not load. At this point I messed something up and had to clear everything and install a clean KK 4.4.4 image. I then tried CM12 all over again, but I was still stuck on the loading screen..
So my question is what can I do? Should I try CM11?(I could not find a DL link anywhere!!)
ANY help is appreciated, I have been at it all day..
MeLoDyz said:
**Bear with me as this is my first unlocking/rooting endeavor!**
I bought a brand new Moto G (XT1031) for Boost Mobile. It came with KitKat 4.4.4 pre-installed. I researched/followed guides and was able to unlocked it.
More research was done. I flashed the recovery software TWRP v2.8.6 via ADB fastboot. I then flashed SuperSU v2.46 via TWRP(zip file). Back up was created with TWRP. Attempted to install CyanogenMod 12.1, however, my bootloader version is "4113" so it said it was not supported. It seemed like changing the bootloader was a bad idea, so I did not pursue that idea. I tried to install CM 12, it was successful. I proceeded to install the gapps version for CM12. I rebooted the system.
It stayed on the boot screen(blue robot head) for a hour. I shut off and restarted the phone, it sat on the boot screen for about 30 minutes. It would not load. At this point I messed something up and had to clear everything and install a clean KK 4.4.4 image. I then tried CM12 all over again, but I was still stuck on the loading screen..
So my question is what can I do? Should I try CM11?(I could not find a DL link anywhere!!)
ANY help is appreciated, I have been at it all day..
Click to expand...
Click to collapse
First of all format data, system, cache, delvic cache and install the zip
pradeeppk said:
First of all format data, system, cache, delvic cache and install the zip
Click to expand...
Click to collapse
I have always went into advance wipe on TWRP and wiped the dalvik cache, data, cache, & system before each install of CM. I even wipe the cache in-between the install of CM and gapps.
I have never formatted before.
So I tried it and it deleted my zip files and my back up..
Now I have no OS so I cannot put new zip files of CM/gapps on the phone. I cannot back up because that was deleted -.-
EDIT: was able to flash a stock 4.4.4 OS back and get it to boot.. no idea what to do now ..can someone link me to CM11?
**UPDATE**
Tried lots of things..ended up updating the bootloader to 4119..which enabled me to finally install CM 12.1. BUT..CM would not boot again! Tried putting the stock rom back on, but failed, would not boot..
Now I cannot load any OS, I get stuck on the "warning your device is unlocked" screen. I can still get to the boot loader and recovery though..
I tried to flash back to stock with multiple guides I found via google, but none worked...
calling anyone to extend some help, or is my phone dead?
That's why flashing a "soak test" - scratch that - "test drive" bootloader is a bad idea.
You'll need to flash the KitKat firmware with mfastboot and skip gpt, motoboot, and logo img/bin's.
Sent from my XT1031™
ATTACK said:
That's why flashing a "soak test" - scratch that - "test drive" bootloader is a bad idea.
You'll need to flash the KitKat firmware with mfastboot and skip gpt, motoboot, and logo img/bin's.
Sent from my XT1031™
Click to expand...
Click to collapse
are you referring to steps like this:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk1
mfastboot flash system system.img_sparsechunk2
mfastboot flash system system.img_sparsechunk3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
if so I have tried that and it fails
Yes, flash everything but "gpt", " motoboot" and "logo".
Sent from my XT1031™
ATTACK said:
Yes, flash everything but "gpt", " motoboot" and "logo".
Sent from my XT1031™
Click to expand...
Click to collapse
ah I see, thanks!
I was able to boot stock 4.4.4, however, the screen is a bit glitchy with a line constantly coming down. From what I have read it seems that is caused by the bootloader version 41.19 (that I upgraded to). Is there anyway to get 41.13 back?
..and I guess putting CM on this phone is a no go for whatever reason?
MeLoDyz said:
ah I see, thanks!
I was able to boot stock 4.4.4, however, the screen is a bit glitchy with a line constantly coming down. From what I have read it seems that is caused by the bootloader version 41.19 (that I upgraded to). Is there anyway to get 41.13 back?
..and I guess putting CM on this phone is a no go for whatever reason?
Click to expand...
Click to collapse
Nope - cant downgrade bootloaders.
As far as CM goes, I really wouldn't know, I don't use it. I prefer stock AOSP or Paranoid Android. There's a really nice build of Paranoid Android at Android Forums by Seraph08
http://androidforums.com/index.php?threads/851868/
Sent from my XT1031™
I have the same device as you, and I decided to upgrade my bootloader, and I was able to successfully get CM 12.1 latest nightly installed and working. Here's what I did:
First I started with full stock 4.4.4, flashed TWRP and upgraded my bootloader.
Then afterwards I installed one of the CM11 snapshots and then from there I flashed the latest CM12.1 nightly and everything seems to be working except data breaks sometimes, it usually fixes itself with a reboot.
Ninja3047 said:
I have the same device as you, and I decided to upgrade my bootloader, and I was able to successfully get CM 12.1 latest nightly installed and working. Here's what I did:
First I started with full stock 4.4.4, flashed TWRP and upgraded my bootloader.
Then afterwards I installed one of the CM11 snapshots and then from there I flashed the latest CM12.1 nightly and everything seems to be working except data breaks sometimes, it usually fixes itself with a reboot.
Click to expand...
Click to collapse
That worked for me I am on CM12.1 now!, thanks
Any idea if it is possible to get CM12.1 on a boost XT1031 with 41.13 bootloader, WITHOUT upgrading the bootloader?
Related
Hello,
TL;DR: My question: where can I find a stock 4.4 GPe firmware compatible with XT1032 devices? (cid: 0x00DE
I had a rooted Moto G GPe 4.4, which prompted me yesterday about updating to Lollipop (OTA update, is that right?). Of course, it didn't work. Seriously, for newbies like me reading this, don't accept this, wait for something stable to be available.
So, yesterday, it downloaded everything and started updating. It hanged right in the middle with an error screen. I tried a reboot, same thing (in french it was written "Aucune commande". I guess the proper translation would be no command available or something). I tried a recovery, I had the little android logo lying on the ground with a scary warning on his belly. I tried a factory reset, same thing.
So, I went on this forum, started following this guide, however I was on Linux so I didn't use his .bat script, instead I manually used fastboot and mfastboot.
I downloaded the image named XT1032_RETAIL-EU_4.4.4_KXB21.14-L1.40_36_cid7_CFC_1FF.xml.zip (the CID don't match but it worked) available at this address. For information, the link http://sbf.droid-developers.org/phone.php?device=14 is dead since yesterday at least, which is annoying given the bandwidth of filefactory.
Using mfastboot, I launched these commands:
Code:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot reboot
Everything was fine. My phone booted, prompted me to install the device and download my apps. Aside from the fugly Motorola boot animation and stock apps, great. However, I couldn't get the Lollipop update, since apparently it is only available to 4.4 GPe edition. I thus got even dumber than normally and started to follow this guide. Beware, the sound is very loud on this video, and doing a video for this kind of info is pretty dumb anyway. The process is written down in the description.
I downloaded the 4.4 GPe firmware linked and started to flash it using mfastboot, same process as above. However, upon rebooting I had only a prompt to decrypt my data. WTF? I used my Google Account password to no avail. Rebooted in fastboot mode, tried recovery and factory reset. Nope. So, I flashed again the XT1032_RETAIL-EU_4.4.4_KXB21.14-L1.40_36_cid7_CFC_1FF firmware. I booted fine, and it is currently restoring my system.
Anyone could explain exactly why it did it? Do I have to worry about anything (I don't care about my data, everything is backed up securely. But I critically need my phone and can't afford to brick it).
I am unable to find a stock 4.4 GPe firmware. Anyone got a link? If possible from a reputable source? I'd like to stay on a GPe phone, I hate bloated and ugly designs. And I'd like to update to Lollipop.
Edit: Okay, the flashing did work, however the CID mismatch is more of a problem than I thought. My CID as printed by fastboot is 0x00DE (and NOT 0x000DE as sometimes indicated in some guides). My image CID is 0x0007. I can't speak on the microphone and I don't have any tone when I call. It is a problem. FFS, is there any ROM I can flash working with this CID?
lknr said:
Hello,
TL;DR: My question: where can I find a stock 4.4 GPe firmware compatible with XT1032 devices? (cid: 0x00DE
Anyone could explain exactly why it did it? Do I have to worry about anything (I don't care about my data, everything is backed up securely. But I critically need my phone and can't afford to brick it).
I am unable to find a stock 4.4 GPe firmware. Anyone got a link? If possible from a reputable source? I'd like to stay on a GPe phone, I hate bloated and ugly designs. And I'd like to update to Lollipop.
Click to expand...
Click to collapse
GPE 4.4.x uses ext4 /data partion whereas Retail-XX versions use f2fs. Hence when we restore the /data partition from a different filesystem type it gives that 'enter encryption password' screen. So probably you had restored your /data partition on GPE device from your non-GPE /data backup. Wihout that it should work fine.
nbansal said:
GPE 4.4.x uses ext4 /data partion whereas Retail-XX versions use f2fs. Hence when we restore the /data partition from a different filesystem type it gives that 'enter encryption password' screen. So probably you had restored your /data partition on GPE device from your non-GPE /data backup. Wihout that it should work fine.
Click to expand...
Click to collapse
Okay, that mush be linked indeed. However I didn't restore my backup (I didn't have much files, and by backup I mean my documents were uploaded on the cloud so I don't care about anything on the device. If I launch fastboot erase userdata before flashing the GPE firmware I downloaded, will it still do the enter encryption password screen ? Is there a guide to flash a GPE firmware somewhere?
lknr said:
Okay, that mush be linked indeed. However I didn't restore my backup (I didn't have much files, and by backup I mean my documents were uploaded on the cloud so I don't care about anything on the device. If I launch fastboot erase userdata before flashing the GPE firmware I downloaded, will it still do the enter encryption password screen ? Is there a guide to flash a GPE firmware somewhere?
Click to expand...
Click to collapse
Okay, it seems you didnt wipe data partition when you flashed GPE over Retail version. So when it booted into GPE, GPE cannot interpret f2fs /data partition and thinks its encrypted and prompts for the password. If needs a blank/wiped /data at first boot. In general its a good idea to 'erase userdata' (if via fastboot) or wipe data partition (if using recovery) when flashing any ROM.
nbansal said:
Okay, it seems you didnt wipe data partition when you flashed GPE over Retail version. So when it booted into GPE, GPE cannot interpret f2fs /data partition and thinks its encrypted and prompts for the password. If needs a blank/wiped /data at first boot. In general its a good idea to 'erase userdata' (if via fastboot) or wipe data partition (if using recovery) when flashing any ROM.
Click to expand...
Click to collapse
That was it, simply. Thanks. I followed this guide (incidentally using the very same files I downloaded in my OP), stopped right before the OTA sideload step. It is no downloading the system update on its own, everything seems to be working.
Hello guys, I need urgent help
I've upgraded my moto G 2013 to Lollipop retail UE a couple of days ago, everything was working perfect, I have it only rooted and few apps installed, nothing weird (no xposed). I wanted to install a new bootlogo but just in case I did a backup with the TWRP recovery.
I got a bootloop after flashing that, and when I wanted to restore my backup, it was not there! The ''restore'' tab in TWRP is empty, but I see the backup in my sdcard with the file manager of TWRP, it was done just 2 min before but it's just like if the recovery doesn't see it.
What can I do? I've tried with a factory reset but still in bootloop. Can I flash a Kitkat stock rom via fastboot? Because I've seen in some places that it can brick my phone... I was thinking, maybe I can flash the logo of the Lollipop UE rom?
Thanks in advance, I need your help
matapr0 said:
Hello guys, I need urgent help
I've upgraded my moto G 2013 to Lollipop retail UE a couple of days ago, everything was working perfect, I have it only rooted and few apps installed, nothing weird (no xposed). I wanted to install a new bootlogo but just in case I did a backup with the TWRP recovery.
I got a bootloop after flashing that, and when I wanted to restore my backup, it was not there! The ''restore'' tab in TWRP is empty, but I see the backup in my sdcard with the file manager of TWRP, it was done just 2 min before but it's just like if the recovery doesn't see it.
What can I do? I've tried with a factory reset but still in bootloop. Can I flash a Kitkat stock rom via fastboot? Because I've seen in some places that it can brick my phone... I was thinking, maybe I can flash the logo of the Lollipop UE rom?
Thanks in advance, I need your help
Click to expand...
Click to collapse
yes u can flash the kitkat stock rom but follow these steps carefully......
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
mfastboot reboot
note:
u will receive some errors but no problem continue
after flashing kitkat will see flashing line on ur device every time u reboot ur device
just on and off ur screen and that would do it(fix the problem).
upgrade to lollipop to get rid of that flashing lines problem.
Thank you very much! any help to try to install the backup I have but isn't detected by TWRP recovery? Because I wouldn't like to lose all my data
Did you store it to an external SD card using a OTG device? Did you try changing the location for the restore file in TWRP?
Hi,
after an apparently failed attempt to install the 5.0 OTA update my XT1032 now will boot to a droid lying on its back.
I went to the recovery from there (by pressing VolUp+Power) and did the "factory reset/wipe data" and rebooted.
Same result.
I did "wipe chache". Same result: Droid lying on its back, saying "Kein Befehl" (I guess that means "no command")
I can get into recovery mode (CWM was installed before all this*) so I could try to flash stuff from outside.
But what should I try to flash? I tried flashing a (supposedly) stock system but as soon as I start with "fastboot flash boot boot.img" the phone starts booting again. So I am not really sure what to do now.
Something is seriously wrong with this phone and I would like to restore it to stock settings. I bought it on amazon.DE - so if any one of you guys knows where I could find a truly original stock image for this phone and what to do with it, please let me know.
PS: Right now I can't even get into recovery anymore. The thing just keeps booting and booting. Can't even turn it off.
* meaning: before I flashed the supposed stock recovery that apparently, in combination with the OTA update, got me into this mess
I now followed this guide:
http://forum.xda-developers.com/showthread.php?p=47820707#post47820707
I used option 3b with a 4.4.4 rom ( RETAIL-DE_4.4.4_KXB21.14-L1.40_36_cid7_CFC_1FF )
I excuted all these commands. However, upon flashing the boot.img the phone immediately boots (and gets stuck).
So I re-entered fastboot again to finish the job. Everything else went fine.
But the problem persists: When booting, the phone now displays the "Warning: Bootloader unlocked" message for a long time, with a kind of water ripple effect from bottom to top, repeating.
When I switch it off, it switches back on automatically, trying to boot and getting stuck at this screen. Sometimes I get to the droid lying on its back with a red !-Triangle on top. Poor little bugger. Soft bricked.
What can I do to fix this?
I can still enter fastboot.
I assume that yet again I grabbed the wrong ROM.
Is this supposed to be dead? http://sbf.droid-developers.org/phone.php?device=14
I think you might be on lollipop bootloader as you are having a screen flickering issue & downgrading the boatloader might be dangerous.
I'm don't know whether it will solve your problem but try flashing a lollipop firmware.
I'm not allowed to post links. Google for XT 1032 lollipop firmware. I saw one in groupandroid website.
Download the firmware from the site & execute the given commands.
legolas06 said:
I think you might be on lollipop bootloader as you are having a screen flickering issue & downgrading the boatloader might be dangerous.
I'm don't know whether it will solve your problem but try flashing a lollipop firmware.
I'm not allowed to post links. Google for XT 1032 lollipop firmware. I saw one in groupandroid website.
Download the firmware from the site & execute the given commands.
Click to expand...
Click to collapse
Thank you. I got that file.
"adb devices" won't find my phone, though.
"Fastboot devices" does. So I can't use "adb push ..." to move the ROM to the phone.
Also, whatever option I chose from the Fastboot Flash Mode, the phone starts to boot. So I can not "enter" Recovery.
Should I just use "fastboot update rom.zip"? I don't wan't to miss my last chance to revive this phone.
ADB commands will not work in with the phone fastboot mode.
Since fastboot commands do work, you can manually flash each partition from the stock ROM. Entering recovery isn't required to do this.
fertchen said:
Thank you. I got that file.
"adb devices" won't find my phone, though.
"Fastboot devices" does. So I can't use "adb push ..." to move the ROM to the phone.
Also, whatever option I chose from the Fastboot Flash Mode, the phone starts to boot. So I can not "enter" Recovery.
Should I just use "fastboot update rom.zip"? I don't wan't to miss my last chance to revive this phone.
Click to expand...
Click to collapse
I had similar problems & this method worked for me everytime. Sorry I'm a new user & I cannot post the links.
You can search the forum & find the links.
I found a thread in "xda -> moto g general->[FIRMWARE][XT1032-XT1033] Firmware Lollipop Retail Brasil & Asia 5.0.2" by cristiand391. Download the firmware for your device. It will be in BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml.zip. Extract the contents to the fastboot.exe folder where you use regularly. Run the commands in fastbootmode. Please be careful with the commands.
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
Reboot.
audit13 said:
ADB commands will not work in with the phone fastboot mode.
Since fastboot commands do work, you can manually flash each partition from the stock ROM. Entering recovery isn't required to do this.
Click to expand...
Click to collapse
The problem here is that the phone will boot as soon as I flash the boot.img and the whole thing fails.
Do you see a way out of this situation?
Any way to do this with a .zip ROM?
Have you tried flashing different firmware such as the GPE for your phone?
Does boot.img flash properly? If it does, you could try installing TWRP, boot into TWRP, mount the data partition, and use your computer to copy a custom ROM to the phone fpr flashing.
@Fretchen
That might be because you are on lollipop bootloader & you are trying to flash kitkat bootloader?But I may be wrong. Previously you told that you tried restoring to kitkat & that boot.img is kitkat bootloader. Try with this lollipop firmware.
audit13 said:
Have you tried flashing different firmware such as the GPE for your phone?
Does boot.img flash properly? If it does, you could try installing TWRP, boot into TWRP, mount the data partition, and use your computer to copy a custom ROM to the phone fpr flashing.
Click to expand...
Click to collapse
I now did exactly what legolas06 wrote, using "MoeMoe_BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml"
There were "hab check fails" for recovery and boot but at least the device did not reboot upon flashing the boot.img.
I rebooted it and it is going further than ever before, all the Motorola animations were played but in the end the phone got stuck at the circular blue pool (water) with the bit Motorola 'M' plus the concentric water ripple effect.
I switched it off and on again and then it played through the animations, then updated the apps (total number: 9) and then started the system. Apparently it is working.
Thank you very much, I really appreciate your support.
Allow me thse final questions:
Can I from now on just apply OTA updates?
If not, what can I change to make this possible?
Is it advisable to install a EU Rom soon for whatever reason?
fertchen said:
I now did exactly what legolas06 wrote, using "MoeMoe_BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml"
There were "hab check fails" for recovery and boot but at least the device did not reboot upon flashing the boot.img.
I rebooted it and it is going further than ever before, all the Motorola animations were played but in the end the phone got stuck at the circular blue pool (water) with the bit Motorola 'M' plus the concentric water ripple effect.
I switched it off and on again and then it played through the animations, then updated the apps (total number: 9) and then started the system. Apparently it is working.
Thank you very much, I really appreciate your support.
Allow me thse final questions:
Can I from now on just apply OTA updates?
If not, what can I change to make this possible?
Is it advisable to install a EU Rom soon for whatever reason?
Click to expand...
Click to collapse
Happy that I could help.
You flashed the stock firmware so everything should work again. OTA updates if available would work.
fertchen said:
Allow me thse final questions:
Can I from now on just apply OTA updates?
If not, what can I change to make this possible?
Is it advisable to install a EU Rom soon for whatever reason?
Click to expand...
Click to collapse
I don't know if you can apply OTA updates. Before the OTA update will work, you may need to update all Motorol apps via Play store.
You could wait until a fulkl stock lollipop pop is released for your phone and flash it using fastboot.
You can try different ROMs but stick to the ROMs made for your model. I have an xt1032 and I have installed US Retail, stock Telus, and GPE.
worked for me too, thank you soo much. give this solution a try
legolas06 said:
I had similar problems & this method worked for me everytime. Sorry I'm a new user & I cannot post the links.
You can search the forum & find the links.
I found a thread in "xda -> moto g general->[FIRMWARE][XT1032-XT1033] Firmware Lollipop Retail Brasil & Asia 5.0.2" by cristiand391. Download the firmware for your device. It will be in BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml.zip. Extract the contents to the fastboot.exe folder where you use regularly. Run the commands in fastbootmode. Please be careful with the commands.
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
Reboot.
Click to expand...
Click to collapse
these steps look soo similar that the ones you can find in other blogs/discussions, but for me, in my case the main difference was the firmware, I tried with a loot of them, but the one that is mentioned in this post, installed smoothly, and with no issues, thank you so much, to post your experience and this solution.
My Best Regards,
Esteban
Hey guys
First of all: I think, I ****ed up.
So I was on a custom 5.0.2 Rom and it was really buggy (forceclose, lowmemory, etc.) and so I decided,
that it would be a good idea to go back to stock and flash Slimrom. As far, as I remember, I did the following:
1. Go into my custom recovery and delete everything (I know, I'm an idiot :crying: )
2. Go into fastboot and flash 4.4.4 via a script on my PC
3. Get problems, which I somehow resolve (pls don't ask me, how. I was pretty drunk last night.)
4. 4.4.4 is up and running. I download the stock 5.0.2 OTA files form XDA and try to flash them with TWM.
5. Everything is super buggy under 5.0.2, so I decide to flash back 4.4.4 and use the stock recovery.
6. 5.0.2 runs just fine and I begin to prepare for the custom Slimrom.
7. Install custom recovery, download Slimrom and GApps.
8. Flash Slimrom and get some weird error, that /system and /date can't be mounted. Everything ****ed up from there on...
9. Try to flash the stock 4.4.4 from before (using the script). Doesn't work, gets stuck on bootloader unlocked messege.
10. Try random **** (literally everything, I can find on the web.)
11. Write this post.
Some information, you could need:
XT1032
Fastboot version: 41.18
Unlocked (Status Code: 3)
Boots into recovery
Recovery is TWM 2.8.6.0
Things, I've tried: Flash the stock 4.4.4 system and then flash a custom rom, using TWM Didn't work
Reflash the stock "Kernel Module", found under /showthread.php?t=2649763 Didn't work
Flash an alternate "bootloader unlocked" Screen Didn't work
Please help me, guys :fingers-crossed:
Did you try manually flashing each partition for the 4.4.4 stock ROM? Since you are on a 41.18 bootloader, you should be able to flash every file except motoboot.
audit13 said:
Did you try manually flashing each partition for the 4.4.4 stock ROM? Since you are on a 41.18 bootloader, you should be able to flash every file except motoboot.
Click to expand...
Click to collapse
First of all, thank you for your quick response!
I was able to flash everything without any errors, but unfortunately, it is still stuck on the Warning screen.
Did you erase cache and userdata in fastboot?
audit13 said:
Did you erase cache and userdata in fastboot?
Click to expand...
Click to collapse
Yes, but it did not help
Edit: it gives me an error, when flashing gpt.bin.
it says:
(bootloader) Preflash validation failed
FAILED (remote failure)
So all files flahed except motoboot and gpt? The motoboot file from the stock 4.4.4 flash won't install becuase the 4.4.4 bootloader is older than the bootloader currently installed on your phone.
Even if the gpt.bin file doesn't flash, it doesn't always prevent the phone from booting a stock ROM.
Was the 5.02 ROM the GPE?
audit13 said:
So all files flahed except motoboot and gpt? The motoboot file from the stock 4.4.4 flash won't install becuase the 4.4.4 bootloader is older than the bootloader currently installed on your phone.
Even if the gpt.bin file doesn't flash, it doesn't always prevent the phone from booting a stock ROM.
Was the 5.02 ROM the GPE?
Click to expand...
Click to collapse
When trying to flash the motoboot.img, it says "permission denied" and when trying to flash the gpt.bin, it says "(bootloader) Preflash validation failed FAILED (remote failure)".
The 5.0.2 ROM was the OTA update, which in my case, is the normal motorola one. I did convert my device to a GPE, when Lollipop for the moto G GPE became availible (arround december),
but went back to the normal ROM to get the 5.0.2 OTA.
Thank you for your help :laugh:
Ok, I have used this: http://forum.xda-developers.com/moto-g/development/rom-4-4-4-stock-eu-1-click-easy-flash-t2879757 and i'm back in Stock 4.4.4. I have got no idea, how that worked but it's done
That's great that it worked.
If you want to get 5.02 OTA update, be sure to update Motorola Update Services app in the Play store before checking for updates.
If anyone can advise me on the solution to get upgrade to latest Android System version would be grateful.
Currently I am on India Stock 6.0.1 rooted and TWRP installed (System Version : 24.66.2.quark_reteu.reteuall.en.EU retin). I am getting system update notification to 24.201.2 version. However after download install/update, its failing. It gets restart to TWRP and had manually reboot back to System. And then system detect already downloaded update and starts auto restart. Is there solution to fix this issue....
Thanks
mohangj said:
Currently I am on India Stock 6.0.1 rooted and TWRP installed (System Version : 24.66.2.quark_reteu.reteuall.en.EU retin). I am getting system update notification to 24.201.2 version. However after download install/update, its failing. It gets restart to TWRP and had manually reboot back to System. And then system detect already downloaded update and starts auto restart. Is there solution to fix this issue....
Thanks
Click to expand...
Click to collapse
Your TWRP reference is the clue.
You need to be on pure stock to get any OTA updates. Your TWRP recovery is blocking that, since you don't have stock recovery. It will continue to fail.
You can either flash back to 100% pure stock (including recovery), take the OTA, then re-flash TWRP.
Or you can wait until the full firmware of that update is posted -- not just the OTA, which is not the full version -- and flash that full firmware version manually with ADB or RSD.
If you choose the latter method, until that full firmware is posted you can disable the OTA notification if it bothers you.
(Be aware that some minor OTA updates never have the full firmware version posted.)
ChazzMatt said:
Your TWRP reference is the clue.
You need to be on pure stock to get any OTA updates. Your TWRP recovery is blocking that, since you don't have stock recovery. It will continue to fail.
You can either flash back to 100% pure stock (including recovery), take the OTA, then re-flash TWRP.
Or you can wait until the full firmware of that update is posted -- not just the OTA, which is not the full version -- and flash that full firmware version manually with ADB or RSD.
If you choose the latter method, until that full firmware is posted you can disable the OTA notification if it bothers you.
(Be aware that some minor OTA updates never have the full firmware version posted.)
Click to expand...
Click to collapse
Thanks !!
First method is only the right approach as of now if decide to go for update. Second method won't be possible in near future as Moto Maxx won't be getting Nougat :crying:
Hi ChazzMatt,
I decided to upgrade to 24.201.2 version, had successfully installed stock rom and got OTA update to 24.201.2. Installed TWRP and SuperSu.
Everything is working fine except, it directly booting to TWRP, what could be the issue....any fix.
mohangj said:
Everything is working fine except, it directly booting to TWRP, what could be the issue....any fix.
Click to expand...
Click to collapse
There were other reports about people booting directly to TWRP recovery a few weeks ago, instead of to their system. Sorry, I can't remember the reason or the fix... But there were at least two other people who had that issue. I'll try to research and see if I can find it.
What version of TWRP are you using? Do you have the most recent?
bhb27 said:
TWRP update
twrp-3.0.3-0_MOD_3-quark.img
Download
===================
Feb-17-2016
===================
* All the previously TWRP Mod + the below
* Included the latest TWRP updates to this date
* Kernel Improves
* Latest updates and bugs Fix to the date of TWRP
* Most notable is the fix for Nougat Setting configurations be lost after the wipe of cache or a restore of the ROM Data, only new backups made on the latest MOD TWRP will have this featuring.
Click to expand...
Click to collapse
also, what version of SuperSu are you using? Once rooted with the older version, you can update to newest.
SuperSU v2.79 SR3
https://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip
After flashing the newest TWRP and SuperSu, clear all caches in recovery and reboot. See if that fixes the issue?
OK, I found one of the incidents and I gave him the same advice, but never heard back about results.
However the issue was his phone was booting to the bootloader, not to his TWRP recovery. Is yours actually booting to the TWRP screen or to your bootloader?
Here's his incident, and there was also another I can't find right now. One was going to recovery, but this guy below was going to bootloader.
___
zeeshan.siddique4779 said:
I have isntall this rom every thing is fine , but when ever i restat my phone it goes straight in to bootloader , then i have to press enter to go to the system andriod ? Why it is so ?
Click to expand...
Click to collapse
ChazzMatt said:
Is it going to your TWRP recovery or actually your bootloader screen? Someone else reported this on another ROM and they were mistaken -- it was going to recovery, not the bootloader. I don't remember why. I'll look around and see if I can find the comment.
But try reflashing the latest version of TWRP for Quark by our Quark TWRP maintainer, found here:
twrp-3.0.2-0-Mod_04-quark.img (updated September 2016)
https://www.androidfilehost.com/?fid=529141701856462150
Can't hurt and may help.
You may not have the latest version of TWRP for our Quark, which was released in September 2016. Our Quark maintainer (who has official status) has newer modded versions on Android Host Files the official TWRP website has not yet integrated. It's their fault, not his. So, he provides the newest stuff to us in spite of their neglect.
Once you re-flash that TWRP, then reflash latest SuperSu and clear caches (it's an option you will see after your install something).
Reinstalling SuperSu can't hurt and also may help. Then, let it reboot.
[2017.01.03] SuperSU v2.79 SR2
https://download.chainfire.eu/1019/SuperSU/SR2-SuperSU-v2.79-SR2-20170103215521.zip
When you initially rooted this ROM you had to use beta 2.62 SuperSu, but now you can update to newest if you haven't already.
Click to expand...
Click to collapse
zeeshan.siddique4779 said:
Yes it goes in bootloader screen not in recovery . Then i have to press power button to start phone .
What do you recomenr ? Any solution ?
Click to expand...
Click to collapse
ChazzMatt said:
Have you tried the the three things I suggested?
Install latest TWRP
Install latest SuperSu
Clear all caches in TWRP
In the meanwhile, I'll keep researching -- but any of those may somehow fix your issue.
Click to expand...
Click to collapse
zeeshan.siddique4779 said:
ok i will try and report you back . Thanks for help brother
Click to expand...
Click to collapse
ChazzMatt said:
Also try dirty flashing the ROM again. Boot into TWRP, flash the ROM, clear caches, reboot.
Click to expand...
Click to collapse
My issue is also exactly same what zeeshan.siddique4779 explained. Let me correct what I mentioned TWRP, its bootloader. When I boot/reboot it directly goes to Bootloader (-->START) there I have to press power button to boot system Android. I installed twrp-3.0.3-0_MOD_3-quark.img and cleared all cache, still issue persists.
I tried to go back to stock bootloader and install stock 6.0.1, but install is failing 3/22 error gbt.bin. I searched fix to this...didn't get. Currently I am running LOS 14.1 (root inbuilt in Developer option) with rebooting to bootloader issue
mohangj said:
My issue is also exactly same what zeeshan.siddique4779 explained. Let me correct what I mentioned TWRP, its bootloader. When I boot/reboot it directly goes to Bootloader (-->START) there I have to press power button to boot system Android. I installed twrp-3.0.3-0_MOD_3-quark.img and cleared all cache, still issue persists.
I tried to go back to stock bootloader and install stock 6.0.1, but install is failing 3/22 error gbt.bin. I searched fix to this...didn't get. Currently I am running LOS 14.1 (root inbuilt in Developer option) with rebooting to bootloader issue
Click to expand...
Click to collapse
He was on modified stock ROM for the Droid Turbo XT1254 -- a tweaked, debloated ROM by Computerfreek274 over in the other Quark forum. But same issue...
mohangj said:
I tried to go back to stock bootloader and install stock 6.0.1, but install is failing 3/22 error gbt.bin. I searched fix to this...didn't get. Currently I am running LOS 14.1 (root inbuilt in Developer option) with rebooting to bootloader issue
Click to expand...
Click to collapse
I think this is because with the OTA you took you installed a new bootloader. You can only downgrade to earlier firmware, even with an unlocked bootloader, if you omit gpt.bin from flashing. If you omit gpt.bin from the flash commands you can even downgrade back to Lollipop or Kitkat.
Thanks and I think you are correct. I tried to take stock update and bootloader broke.
How do I omit gbt.bin while flashing. So far I only flashed to stock with RSD. Please refer links, I will give a try.
It worked Thanks brother !!!!
Here what I executed on bootloader
mfastboot oem fb_mode_set
mfastboot flash partition gpt.bin (didn't execute this command)
mfastboot flash motoboot bootloader.img
mfastboot flash radio radio.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash system system.img_sparsechunk.8
mfastboot flash system system.img_sparsechunk.9
mfastboot erase cache
mfastboot erase userdata
mfastboot erase clogo
mfastboot oem fb_mode_clear
mfastboot reboot
mohangj said:
It worked Thanks brother !!!!
Here what I executed on bootloader
mfastboot oem fb_mode_set
mfastboot flash partition gpt.bin (didn't execute this command)
mfastboot flash motoboot bootloader.img
mfastboot flash radio radio.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash system system.img_sparsechunk.8
mfastboot flash system system.img_sparsechunk.9
mfastboot erase cache
mfastboot erase userdata
mfastboot erase clogo
mfastboot oem fb_mode_clear
mfastboot reboot
Click to expand...
Click to collapse
can u give me the link tostock rom? unable to find one i bricked my xt1225
jigar003 said:
can u give me the link to stock rom? unable to find one i bricked my xt1225
Click to expand...
Click to collapse
EVERY QUARK FIRMWARE EVER RELEASED
http://www.filefactory.com/folder/f9d1880e6c5b4800/?sort=created&order=DESC&show=50
Well, almost the every Quark firmware. See, Motorola has released a few OTAs with security fixes and has not posted the full firmware yet. What @mohangj was able to do was DOWNGRADE to the last full firmware posted. And he was able to do that by having an UNLOCKED bootloader.
If your bootloader is still locked, you will only be able to flash the firmware you are bricked on (or higher), you will not be able to downgrade. And if Motorola has not yet publicly released the full firmware version, you have to send it to a repair center or something. Or wait until they release the full firmware publicly.
This is why having an UNLOCKED bootloader is so helpful sometimes!
If your bootloader is unlocked you can flash any XT1225 firmware listed at that link, just omit the GPT.bin file when flashing.
thanks my bootloader is unlocked
jigar003 said:
thanks my bootloader is unlocked
Click to expand...
Click to collapse
Then you're very smart!
jigar003 said:
can u give me the link tostock rom? unable to find one i bricked my xt1225
Click to expand...
Click to collapse
I am using https://forum.xda-developers.com/moto-maxx/general/moto-turbo-indian-variant-marshmallow-t3422783
mohangj said:
It worked Thanks brother !!!!
Here what I executed on bootloader
mfastboot oem fb_mode_set
mfastboot flash partition gpt.bin (didn't execute this command)
mfastboot flash motoboot bootloader.img
mfastboot flash radio radio.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash system system.img_sparsechunk.8
mfastboot flash system system.img_sparsechunk.9
mfastboot erase cache
mfastboot erase userdata
mfastboot erase clogo
mfastboot oem fb_mode_clear
mfastboot reboot
Click to expand...
Click to collapse
**********************************
ChazzMatt,
I am facing another kind of problem again, I had flashed custom Kernel BHB27 (https://forum.xda-developers.com/moto-maxx/development/kernel-bhb27-kernel-t3207526) on stock 6.0.1, It was successfully installed and but I lost Devinebeats Viper4Android effect. I tried to reinstall driver/relash zip file. It didn't work. So I wanted to reflash to Stock. This time I followed same steps as above. But not able to successfully flash, after executing all commands, device reboots to Motorola Android boot screen and then goes off, its getting switched off in some 15-20 secs. Not able to boot completely back to stock. what am I upto now
mohangj said:
**********************************
ChazzMatt,
I am facing another kind of problem again, I had flashed custom Kernel BHB27 (https://forum.xda-developers.com/moto-maxx/development/kernel-bhb27-kernel-t3207526) on stock 6.0.1, It was successfully installed and but I lost Devinebeats Viper4Android effect. I tried to reinstall driver/relash zip file. It didn't work. So I wanted to reflash to Stock. This time I followed same steps as above. But not able to successfully flash, after executing all commands, device reboots to Motorola Android boot screen and then goes off, its getting switched off in some 15-20 secs. Not able to boot completely back to stock. what am I upto now
Click to expand...
Click to collapse
Since all you replaced with @bhb27's kernel was the the kernel, you wouldn't have to re-flash the entire stock image. All you needed to re-flash -- I think -- would be the boot.img. That would have overwritten the custom kernel...
But at this point, since you have re-flashed the entire image andnow the phone won't boot, I'm not sure what is wrong.
You can always try to flash a custom ROM? I know people use Viper on custom ROMs and I believe even with @bhb27 kernel. So, not sure why your Viper didn't work any more. But you need to get your phone up and working again.
Try this Marshmallow ROM for starters:
[ROM][All Quark][6.x.x]Resurrection Remix
https://forum.xda-developers.com/moto-maxx/development/rom-resurrection-remix-t3316232
mohangj said:
**********************************
ChazzMatt,
I am facing another kind of problem again, I had flashed custom Kernel BHB27 (https://forum.xda-developers.com/moto-maxx/development/kernel-bhb27-kernel-t3207526) on stock 6.0.1, It was successfully installed and but I lost Devinebeats Viper4Android effect. I tried to reinstall driver/relash zip file. It didn't work. So I wanted to reflash to Stock. This time I followed same steps as above. But not able to successfully flash, after executing all commands, device reboots to Motorola Android boot screen and then goes off, its getting switched off in some 15-20 secs. Not able to boot completely back to stock. what am I upto now
Click to expand...
Click to collapse
Here's a "custom" ROM based on XT1225 stock Marshmallow. It's just stock Brazilian Quark Marshmallow but modified to run on ALL Quarks (including Droid Turbo XT1254) by @iiWoodstocK. Try flashing that?
[ROM][6.0.1][Stock][Odexed]MPG24.107-70.2 Brazilian 6.0.1 for XT1254[TWRP Flashable]
https://forum.xda-developers.com/droid-turbo/development/rom-mpg24-107-70-2-brazilian-6-0-1-t3426234
ChazzMatt said:
Here's a "custom" ROM based on XT1225 stock Marshmallow. It's just stock Brazilian Quark Marshmallow but modified to run on ALL Quarks (including Droid Turbo XT1254) by @iiWoodstocK. Try flashing that?
[ROM][6.0.1][Stock][Odexed]MPG24.107-70.2 Brazilian 6.0.1 for XT1254[TWRP Flashable]
https://forum.xda-developers.com/droid-turbo/development/rom-mpg24-107-70-2-brazilian-6-0-1-t3426234
Click to expand...
Click to collapse
Thanks for the update. It worked by removing gbt.bin entry line from flash file and flashed it by RSD. No issues now
Need help I'm getting this annoying notification to update to 24.201.2 every now and then hence I final tried to install it failed.
Please check the screens for more.
And recovery also does not open says "no command " error I'm not sure whether I had installed or not. How to fix this? And remove that annoying updated notifications without root.