Hello Guys,
after a week using Paranoid Android my moto g xt1032 acted weird, so I reinstalled stock using fastboot.
I am pretty familiar with the use of fastboot and flashing and so on (Guess I've flashed, and fixed over 20 different phones)
But now I've come to the point I can't even fix my own phone.
What does it do?
Well, when I start my phone, it will only show the "warning bootloader unlocked" message, and just restarts and does the same.
Sometimes it even gives a blue screen > restarts.
I can boot into fastboot mode, I tried to flash a RETAIL UK 4.4.2 And RETAIL UK 4.3 stock firmware, even though I am from The Netherlands,
but UK or German roms are the closed to mine, and as far as my knowledge goes, EU firmware are usually the same.
I managed to go into stock recovery, but when I flash philz or twrp, it just stays at the "warning bootloader unlocked" screen.
Going to try XT1032_RETAIL-EU_4.4.4_KXB21.14-L1.40_36_cid7_CFC_1FF.xml.zip right now.
same result.
bump
bump
Try this - http://forum.xda-developers.com/moto-g/help/guide-recover-xt1032-gpe-4-4-4-t2824377
While my situation below may not be yours, at least this may get you back to a stable and functional device. I hope it helps. And as you are aware this will COMPLETELY wipe your phone. If you can, backup any pictures or files you want to keep before doing this.
My situation was like many others that had flashed a 4.4.4 GPE or custom ROM and ended up with a mini wifi tablet as the radio was off (as stated by dialing 8#8#4626#*#*). I have gone two days with no cell signal due to this. Trying to flash a stock image (http://sbf.droid-developers.org/phone.php?device=14) resulted in boot loops. I believe that is what everyone else is calling it. I never saw the loop as it stayed on the initial logo screen before the animation begins. Maybe it is looping fast and just showing the same screen again instead of it simply not changing. Oh well. I'm fixed now but on EU ROM. Now I'm attempting to install Blur_Version.174.44.1.falcon_umts.Retail.en.US. The EU ROM currently installed is 176.44.1, and while it works I simply want to be stock US version for now. I mention this because there is also a 174.44.4 US ROM on SBF-DROID-DEV. I tried that one (among many others) when trying to revive my phone. None of the stock images worked and I'm currently not happy with any of the custom ROMs. Stock or rooted stock will be good for me. On a tangent but I have a XT1032 purchased from AIO Wireless (now Criket but still part of ATT). Well AIO tweaked Motorola's ROM to disable tethering. I actually use Red Pocket for service (another ATT MVNO) and only bought from AIO becausse they had a sweet deal. Wasn't so sweet after I found I could not tether and after 6 months found a way to unlock bootloader, which cost another $25. In short it spent just as much money and had much frustration that could have been avoided if I had purchased directly from Motorola and got a FULLY stock and unlockable device.
---------- Post added at 11:51 PM ---------- Previous post was at 11:42 PM ----------
Pass this along also to anyone looking: theroot.ninja worked for me to unlock the bootloader (I've not posted enough to XDA so posting true URL is disabled. Google "sunshine bootloader unlock"). I found a vague reference on XDA somewhere but don't recall thread. Basically, certain carriers (like ATT and its MVNOs) have agreement with Motorola to restrict bootloader unlocking on devices they resell. Like I said, cost me $25, but it worked and I've wasted more $$ on less.
My bootloader is unlocked, I can't get into recovery, only fastboot.
and it stays at the "warning bootloader unlocked screen" aka logo screen, and it restarts so now and then.
When I start it up for the first time, the screen turns blue right away, and restarts, after a couple of restarts, it stays stuck on the logo screen :S
I tried lots of stock firmware, but none of them worked, I wonder if it's a hardware fault, but I reassembled everything, without success.
http://sbf.droid-developers.org no longer has the latest firmware images. You need to read through this thread instead:
http://forum.xda-developers.com/showthread.php?t=2546251
4.4.4 Recovery flashable Stock Motorola zips available here:
http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-rom-collection-t2854688
Regarding fastboot and the 4.4.4 firmware image - you are obviously not doing all the necessary commands. Please state the commands you have used. Since you have updated your bootloader, ensure you are actually attempting to flash a 4.4.4 image, as a 4.4.2 image will result in an error.
lost101 said:
http://sbf.droid-developers.org no longer has the latest firmware images. You need to read through this thread instead:
http://forum.xda-developers.com/showthread.php?t=2546251
4.4.4 Recovery flashable Stock Motorola zips available here:
http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-rom-collection-t2854688
Regarding fastboot and the 4.4.4 firmware image - you are obviously not doing all the necessary commands. Please state the commands you have used. Since you have updated your bootloader, ensure you are actually attempting to flash a 4.4.4 image, as a 4.4.2 image will result in an error.
Click to expand...
Click to collapse
I am pretty sure I am using 4.4.4
I used 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_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
I suggest you add the follow command which will entirely wipe any remaining files your phone.
mfastboot erase userdata
lost101 said:
I suggest you add the follow command which will entirely wipe any remaining files your phone.
mfastboot erase userdata
Click to expand...
Click to collapse
Tried it, no change.
Jur13n said:
Tried it, no change.
Click to expand...
Click to collapse
The system flashing commands are wrong. They should be:
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
See if that fixes it for you.
meekrawb said:
The system flashing commands are wrong. They should be:
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
See if that fixes it for you.
Click to expand...
Click to collapse
system.img_sparsechunk.0
system.img_sparsechunk.1
system.img_sparsechunk.2
To be exactly, I know what I am doing
Jur13n said:
system.img_sparsechunk.0
system.img_sparsechunk.1
system.img_sparsechunk.2
To be exactly, I know what I am doing
Click to expand...
Click to collapse
Okay. Good luck!
Jur13n - did you try http://forum.xda-developers.com/mot...-gpe-4-4-4-t2824377/post55768571#post55768571. Once back to 'base' you can update to 4.4.4 OTA or flash another ROM. And if you get stuck again, re-run this process. Three downloads, a few scripts to run; double-click easy.
Good luck.
e.martin.howell said:
Jur13n - did you try http://forum.xda-developers.com/mot...-gpe-4-4-4-t2824377/post55768571#post55768571. Once back to 'base' you can update to 4.4.4 OTA or flash another ROM. And if you get stuck again, re-run this process. Three downloads, a few scripts to run; double-click easy.
Good luck.
Click to expand...
Click to collapse
http://sbf.droid-developers.org/phone.php?device=14 is offline atm, I'll try it.
What do you mean with three downloads o.o?
I only see him saying Blur_Version.174.44.1.falcon_umts.Retail.en.US
Your issue could be due to older images. Here is the EU Retail 4.4.4 image. It doesn't matter where you are in the world, it will work fine.
http://forum.xda-developers.com/showpost.php?p=54757500&postcount=348
lost101 said:
Your issue could be due to older images. Here is the EU Retail 4.4.4 image. It doesn't matter where you are in the world, it will work fine.
http://forum.xda-developers.com/showpost.php?p=54757500&postcount=348
Click to expand...
Click to collapse
Tried it, didn't work.
Going to try the Blur_Version.174.44.1.falcon_umts.Retail.en.US one right now.
-- edit --
no result, also tried to convert it to gpe, no result either.
I guess it's a hardware problem somehow (maybe reading the harddisk fails?)
If you still have the box that the phone came in look at it and it will tell you which Moto G you have.
Related
Huy guys, very strange issue on my XT1080M.
I stopped using this phone a couple of months ago when I got my Moto X and then work provided me with a different device. The phone went dead at some point, and now, even after plugging it in and letting it charge, it will NOT boot up. It will not progress past the Motorola screen. The screen comes on, it vibrates, and then it gets stuck. The Moto logo is the same color every single time (purple) instead of changing.. thought that was interesting.
The phone had a pending software update that I never took, and I wonder if something prompted it to actually start the update instead. Either way, I downloaded the 4.4.4 fxz files and flashed it in RSDLite. The flashing went through successfully, but it still will not boot. Fastboot is accessible, but if you pick "Recovery", it shows the Moto logo, then comes back to the Fastboot screen and says "Boot up failed".
I re-downloaded and reflashed the files thinking maybe something is corrupt, but it still won't boot.
I really hate to lose this phone as it'd be really great to have as a backup, but I'm really out of any ideas. Bootloader is locked. Device was originally rooted and "security unlocked" with rockmymoto and whatever the security off program was (it's been a while..)
Any ideas at all?
digitaloutsider said:
Huy guys, very strange issue on my XT1080M.
I stopped using this phone a couple of months ago when I got my Moto X and then work provided me with a different device. The phone went dead at some point, and now, even after plugging it in and letting it charge, it will NOT boot up. It will not progress past the Motorola screen. The screen comes on, it vibrates, and then it gets stuck. The Moto logo is the same color every single time (purple) instead of changing.. thought that was interesting.
The phone had a pending software update that I never took, and I wonder if something prompted it to actually start the update instead. Either way, I downloaded the 4.4.4 fxz files and flashed it in RSDLite. The flashing went through successfully, but it still will not boot. Fastboot is accessible, but if you pick "Recovery", it shows the Moto logo, then comes back to the Fastboot screen and says "Boot up failed".
I re-downloaded and reflashed the files thinking maybe something is corrupt, but it still won't boot.
I really hate to lose this phone as it'd be really great to have as a backup, but I'm really out of any ideas. Bootloader is locked. Device was originally rooted and "security unlocked" with rockmymoto and whatever the security off program was (it's been a while..)
Any ideas at all?
Click to expand...
Click to collapse
Which FXZ did you actually flash? Go through and manually flash the FXZ and see what happens. Also run an md5 check on the FXZ
Okay, manually flashed it using mfastboot. No difference. Still stuck on the purple Moto logo.
FXZ file used was 1FF-obake-maxx_verizon-user-4.4.4-SU4.21-release-keys.xml.zip from sbf.droid-developers.org.
These are the steps that I used:
mfastboot getvar max-download-size
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
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
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
MD5 matched. Argh.
digitaloutsider said:
Okay, manually flashed it using mfastboot. No difference. Still stuck on the purple Moto logo.
FXZ file used was 1FF-obake-maxx_verizon-user-4.4.4-SU4.21-release-keys.xml.zip from sbf.droid-developers.org.
These are the steps that I used:
mfastboot getvar max-download-size
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
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
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
MD5 matched. Argh.
Click to expand...
Click to collapse
Well im out of suggestions. May be bricked
digitaloutsider said:
Huy guys, very strange issue on my XT1080M.
I stopped using this phone a couple of months ago when I got my Moto X and then work provided me with a different device. The phone went dead at some point, and now, even after plugging it in and letting it charge, it will NOT boot up. It will not progress past the Motorola screen. The screen comes on, it vibrates, and then it gets stuck. The Moto logo is the same color every single time (purple) instead of changing.. thought that was interesting.
The phone had a pending software update that I never took, and I wonder if something prompted it to actually start the update instead. Either way, I downloaded the 4.4.4 fxz files and flashed it in RSDLite. The flashing went through successfully, but it still will not boot. Fastboot is accessible, but if you pick "Recovery", it shows the Moto logo, then comes back to the Fastboot screen and says "Boot up failed".
I re-downloaded and reflashed the files thinking maybe something is corrupt, but it still won't boot.
I really hate to lose this phone as it'd be really great to have as a backup, but I'm really out of any ideas. Bootloader is locked. Device was originally rooted and "security unlocked" with rockmymoto and whatever the security off program was (it's been a while..)
Any ideas at all?
Click to expand...
Click to collapse
Why don't you flash the XML with RSD lite, the 444 has no getvar or erase userdata lines in it.
aviwdoowks said:
Why don't you flash the XML with RSD lite, the 444 has no getvar or erase userdata lines in it.
Click to expand...
Click to collapse
He did. Look at the post you just quoted.
Same problem here. Rebooted one day, never booted back up. Can't get the phone to charge enough to even complete most flashing commands.
Well, I was able to get my hands on another DROID MAXX. Unfortunately, this one already has 4.4.4 so I'm screwed for being able to use Sunshine until some sort of 4.4.4 root comes out. Plus, the device is a 2013 model, so I can't get a BL code from that Chinese guy.
Sigh. Such is life!
digitaloutsider said:
Well, I was able to get my hands on another DROID MAXX. Unfortunately, this one already has 4.4.4 so I'm screwed for being able to use Sunshine until some sort of 4.4.4 root comes out. Plus, the device is a 2013 model, so I can't get a BL code from that Chinese guy.
Sigh. Such is life!
Click to expand...
Click to collapse
Can you flash a custom recovery and get it to boot to that using the broken device?
The old one had a locked bootloader.
Have you tried house of moto to flash yet?
what system version were you on prior to having problems?
I ran into this same issue and never recovered from it. I had an unlocked bootloader prior to attempting to recover. Now it fails to boot and shows the boot loader is now locked.
my moto x fails to boot up and shows no command when I boot up the phone. Fastboot shows boot up failed
I have one that's having a similar issue. Shows the Motorola logo then nothing. Stock ROM and nothing modified.
Edit: It's a Verizon model (If that has any bearing)
So is there no fix to this issue? I tried to flash a custom recovery using fastboot and got stuck in fastboot mode because the image was too large, and failure to flash.
Also now adb can't find the device
motorola droid max stuck black screen at BLBROKE. help me
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
I know the title is a bit confusing, but I will try to explain the context of my situation so you can understand it better.
I have a x1032 since the end of 2013. When the first image of the Google Play Edition went "public", I converted my device to it, and it stayed that way, doing all the OTA updates, until the 5.1 GPE appear.
When I did the update to this version (5.1 GPE), my compass didn't work with some apps (for example, GPS tools and c:geo), and as it is a sensor that I use most of the time, I decided do revert my device from fastboot to the 4.4 “stock Motorola” (don’t remembre if it was 4.4.2 or 4.4.4) and then update it to the 5.0.2.
In the process, I think that I had a soft brick: when I turned on the device, he stayed in the “unlocked bootloader” image, and he didn’t move forward. But, after trying, I saw that I had access to the bootloader menu and to the recovery, without any problem. I tryed to install the images via fastboot, even the new 5.1 GPE and 5.02 Motorola ones, but none of them works.
I searched, and searched, and finally understand that in this cases, the problema is the /system, /data and /cache partitions that need to be formated, and then I can flash any zip rom via recovery.
And now, this is where I stay: Via fastboot I installed the 5.1 GPE rom. Then I installed philz touch recovery, formated all partitions in ext4, wipe them all (just to be sure ), and did an adb push to have the GPE 5.1 zip ROM from @lost101 in my sdcard, and installed it. AND IT WORKS!
Now, the actual problem: I’m having form time to time some random reboots. They always appear after I try to turn the screen on, and after 3 or 4 seconds, the phone reboot.
Can this be related to the softbrick? I tought it could be a rom problem, but no one else have the same complains and @lost101 says that maybe this is from my phone.
Thanks in advance, and sorry for the long text and my bad english.
I suggest you try flashing the GPE 5.1 Firmware Image available here: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Make sure you use only the following commands and use mfastboot available here: https://www.androidfilehost.com/?fid=23578570567719065
mfastboot flash partition gpt.bin
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
mfastboot reboot
You should not need to manually format partitions. The above commands will do everything for you. The reason for your sensor issues are that the fastboot flashing previous was not successful.
Please do the fastboot commands manually, one at a time, and log everything and post it here.
lost101 said:
I suggest you try flashing the GPE 5.1 Firmware Image available here: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Make sure you use only the following commands and use mfastboot available here: https://www.androidfilehost.com/?fid=23578570567719065
mfastboot flash partition gpt.bin
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
mfastboot reboot
You should not need to manually format partitions. The above commands will do everything for you. The reason for your sensor issues are that the fastboot flashing previous was not successful.
Please do the fastboot commands manually, one at a time, and log everything and post it here.
Click to expand...
Click to collapse
You are absolutely right: there were no errors (except the "normal" validation erros because it's a GPE image), and in the end, I didn't need to format the partitions manualy.
I think the problem was the fastboot (I was using the one from the sdk... my bad!).
Now I know that any problems don't come from the software side, because in that part, everthing is ok.
I will just ask you two more things:
- What custom recovery do you recomend?
- Your Low Memory Killer Tweak works without any problem in the 5.1 GPE installed via fastboot?
Thank you very much for your help. You really made my day.
RBras said:
I will just ask you two more things:
- What custom recovery do you recomend?
- Your Low Memory Killer Tweak works without any problem in the 5.1 GPE installed via fastboot?
Click to expand...
Click to collapse
Latest TWRP. Yes, the LMK Tweak will work in that case.
lost101 said:
I suggest you try flashing the GPE 5.1 Firmware Image available here: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Make sure you use only the following commands and use mfastboot available here: https://www.androidfilehost.com/?fid=23578570567719065
mfastboot flash partition gpt.bin
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
mfastboot reboot
You should not need to manually format partitions. The above commands will do everything for you. The reason for your sensor issues are that the fastboot flashing previous was not successful.
Please do the fastboot commands manually, one at a time, and log everything and post it here.
Click to expand...
Click to collapse
Unfortunately, random reboots are still present
I have installed 5.1 Google Play edition factory image, with the mfastboot you told me, but it still reboots randomly. Did the same with the 5.02 EU from Motorola, and it behaves the same way.
The random reboots happen more or less, one time a day, and it's when I try to turn the screen on, it doesen't respond, and after 3 or 4 seconds, the system reboots.
Any clue of what can be? Is there a way to grab some logs to try to understand what's happening, or it is too difficult and it's better I don't have too many hopes?
It would appear some sort of corruption has occured. I can't say anything with certainty - but I do believe Bootloader corruption could cause what you are experiencing.
It's possible you could fix this by reflashing the Lollipop Bootloader. I did not include the fastboot command to do this above.
Here it is: mfastboot flash motoboot motoboot.img
Try that and report back.
lost101 said:
It would appear some sort of corruption has occured. I can't say anything with certainty - but I do believe Bootloader corruption could cause what you are experiencing.
It's possible you could fix this by reflashing the Lollipop Bootloader. I did not include the fastboot command to do this above.
Here it is: mfastboot flash motoboot motoboot.img
Try that and report back.
Click to expand...
Click to collapse
During my time with Moto G, I flashed it using fastboot, dozens of times, but I was so desperate in the other day that I didn't even notice that your list with commands didn't have the bootloader one.
Now I undestand why the bootloader I have is the one from 5.1 GPE.
I'm gonna try it. In the last 2 days I didn't have any random reboot, but I will take my risk and flash the bootloader from the 5.0.2 EU, and I will report back in the next days.
I'm buying you a beer today, for being so helpful and nice. Thank you very much.
I'm reopening this thread to try to see what's happening with my phone.
So, after flashing the bootloader of the 5.1 GPE, the phone was really better than it was in the OP.
My Moto G didn't reboot anymore when I tryed to turn the screen on, but instead, it started to reboot randomly every 2 or 3 weeks, without needing to touch the phone (the phone was rebooting by itself).
In the last month or so, I'm using the XT1032 Retail EU 5.1 (Optimized) v1.0 from @lost101, and now the behavior is, once again, the described in the OP: I try to turn the screen on, the phone doesen't respond, and after 3 or 4 seconds, it reboots by itself.
And this is happening once every 1 or 2 weeks.
So, can anyone give me some help to try to understand what's happening? @lost101 @luca020400 @LuK1337 @matmutant
Usually, I have the original firmwares from Motorola or GPE, or I can have the optimized versions from @lost101 with TWRP.
Thanks for your help, guys!
Just for the record, I get occasional sudden / unexpected power off. It's rare, but stuff can happen when you are dealing with a complex device such as a smart phone. This is especially so, if you are rooting / modifying the operating system.
The problem could be related to something you are installing. Also, I recommend a clean install once every few months.
I was having some connectivity loss earlier, so I powered off, turned back on and on turning back on, I now get the initial splash screen and nothing further. Can boot into the boot menu and recovery. Tried wiping cache first, then factory reset. Neither option changed anything. Any suggestions?
Were you using stock ROM?
Provide more information as to which ROM you were using.
akiratoriyama said:
Were you using stock ROM?
Provide more information as to which ROM you were using.
Click to expand...
Click to collapse
I apologize, this is completely stock. I left it on overnight (plugged in) and apparently the battery wouldn't charge in this state as it was dead this morning. Plugged it in and charged for a bit and then tried turning it on and it is doing the same thing as before - hanging up at the initial splash screen.
I am helping hipsterdoofus with his phone. I work in the same office.
The only thing I can do is get it into fastboot mode. I was able to get the drivers working in my PC.
When I run fastboot devices, it's showing the moto g.
The bootloader isn't unlocked. I tried to do a "fastboot boot recovery.img" to get it to temp boot into twrp, but it fails since the bootloader is locked.
Is it possible to unlock the bootloader from this state from the fastboot menu?
I assume we can't flash twrp from fastboot without the bootloader being unlocked.
I come from using a Nexus 5, so this device is quite a bit different than what I'm used to. Sorry if I'm asking stupid questions.
Just wanted to do an update.
I was able to unlock the bootloader, then I downloaded the GPE_5.1_XT1032_LMY47M.M001_CFC.xml.zip file from a link I found on the forum.
I followed the steps for restoring stock firmware in this thread.
I did the section for flashing from the xml.zip file:
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_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 you get "(bootloader) Preflash validation failed" errors on the first two entries, you should be okay to ignore (something I read on another thread here).
After that, the phone rebooted. We weren't sure if it was ever going to finish booting up. It had the boot animation screen for quite some time before it finally loaded the OS.
So the good news is, the phone is booting up, and it's the GPE edition.
Bad news is, it's not detecting the SIM card.
If anyone has any ideas, I would love to hear them.
SoonerDude said:
So the good news is, the phone is booting up, and it's the GPE edition.
Bad news is, it's not detecting the SIM card.
If anyone has any ideas, I would love to hear them.
Click to expand...
Click to collapse
Maybe trying to reflash corresponding radio firmware ?
http://forum.xda-developers.com/showthread.php?t=2649763
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.