Related
Hi,
I just got my Moto X Dev Edition GSM TMO last week, but I got it very unstable, while I had try to wipe cache and factory reset few times.
Some problem that I have
Numeric Keypad is not shown while using google keyboard. The problem that my email is using 2FA from google to entry my 6-digit PIN
Chrome freeze while open quite complex pages
Gmail freezing while open communication more than 3 email on the messaging mode
Path also unstable while need to scroll down and request to reload more data.
Whatsapp stuck when there's few message has beeen received
Thinking to downgrade the os to 4.4, but when I read in some thread inform better not to downgrade that might cause device brick.
Is there any other solution so I can use my Moto X for daily, while waiting for T-Mobile latest 4.4.2 rom.
Please share
Thank you
If you have to downgrade to 4.4, but you're waiting for T-Mobile 4.4.2, what ROM are you running?
MotoX Developer Edition went from German 4.4.2 to Great Britain 4.4.2 to T-Mobile 4.4.2 no problem. Fastboot FTW!
SymbioticGenius said:
If you have to downgrade to 4.4, but you're waiting for T-Mobile 4.4.2, what ROM are you running?
MotoX Developer Edition went from German 4.4.2 to Great Britain 4.4.2 to T-Mobile 4.4.2 no problem. Fastboot FTW!
Click to expand...
Click to collapse
Currently I'm using T-Mobile 4.4.2 OTA
Is it possible to restore to factory image with T-Mobile 4. 4?
tyapeter said:
Currently I'm using T-Mobile 4.4.2 OTA
Is it possible to restore to factory image with T-Mobile 4. 4?
Click to expand...
Click to collapse
Yes. But don't flash motoboot.img or gpt.img, it won't let you downgrade those. This doesn't means that you won't brick with other version.
eksasol said:
Yes. But don't flash motoboot.img or gpt.img, it won't let you downgrade those. This doesn't means that you won't brick with other version.
Click to expand...
Click to collapse
Eksasol,
What did you mean with don't flash with those files? Is that means unzip the image files and take out those files and zip again?
Which images is the best one for downgrade, from the sbf Blur_Version.161.44.25.ghost_row.Retail.en.US.zip or TMO_RETAIL_XT1053_4.4-13.11.1Q2.X-69-3_MR2_1FF.xml.zip
And also what you mean with "This doesn't means that you won't brick with other version"? Is that mean that not guarantee that downgrade won't have brick on the devices?
Please advice thanks
Let me make it easier. Just flash the system and kernel files leave everything else alone. However the ability to go back depends on how you got to 4.4.2 to begin with, OP said he took the OTA, not sure about you.
My advice assuming you're stock is to call Motorola, tell them you took the ota and these are the issues you're having. Get them to send you a new phone. I'd rather see you do that than brick your phone trying to do it yourself.
MotoX Developer Edition went from German 4.4.2 to Great Britain 4.4.2 to T-Mobile 4.4.2 no problem. Fastboot FTW!
eksasol said:
Yes. But don't flash motoboot.img or gpt.img, it won't let you downgrade those. This doesn't means that you won't brick with other version.
Click to expand...
Click to collapse
Are you sure this is correct? I was told in this thread: http://forum.xda-developers.com/showthread.php?p=50330230#post50330230 (see post #12):
let me make this blunt before you even get your phone
your phone is a DE so you can root any version
is you come with 4.2.2 camera update or 4.4 you can upgrade and downgrade between thouse two versions only
if your phone comes with 4.4.2 you can not downgrade at all so just root it and enjoy because most people are trying to get there and bricking there phones half the time.
Click to expand...
Click to collapse
So the way I understand it one cannot downgrade from 4.4.2 to any other version because bootloader in 4.4.2 was changed and is not compatible with any previous release.
tyapeter said:
Eksasol,
What did you mean with don't flash with those files? Is that means unzip the image files and take out those files and zip again?
Which images is the best one for downgrade, from the sbf Blur_Version.161.44.25.ghost_row.Retail.en.US.zip or TMO_RETAIL_XT1053_4.4-13.11.1Q2.X-69-3_MR2_1FF.xml.zip
And also what you mean with "This doesn't means that you won't brick with other version"? Is that mean that not guarantee that downgrade won't have brick on the devices?
Please advice thanks
Click to expand...
Click to collapse
If you haven't already unlock the bootloader, then you should just send the phone back. Once you unlock the bootloader the warranty is voided and you'll be stuck with that phone. If you still intend on flashing:
You flash them using mfastboot while in flash mode, do not flash motoboot or gpt, also don't run "fastboot getvar". Manually perform these commands:
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 customize
mfastboot erase clogo
After flashing T-Mo 4.4, you can receive OTA update to get back to 4.4.2.
As for downgrading to other versions, read this sticky before flashing anything: http://forum.xda-developers.com/showthread.php?t=2635366
eksasol said:
If you haven't already unlock the bootloader, then you should just send the phone back. Once you unlock the bootloader the warranty is voided and you'll be stuck with that phone. If you still intend on flashing:
You flash them using mfastboot while in flash mode, do not flash motoboot or gpt, also don't run "fastboot getvar". Manually perform these commands:
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 customize
mfastboot erase clogo
After flashing T-Mo 4.4, you can receive OTA update to get back to 4.4.2.
As for downgrading to other versions, read this sticky before flashing anything: http://forum.xda-developers.com/showthread.php?t=2635366
Click to expand...
Click to collapse
Thanks a lot, it works
I just unrooted my moto g xt1068 and flashed stock rom. But for some reasons i am unable to relock the bootloader. Just want to know that will I be able to receive OTA updates even when the bootloader is unlocked or should i have to relock the bootloader?
why nobody answered my questions yet? Plz reply soon
sandy1636 said:
I just unrooted my moto g xt1068 and flashed stock rom. But for some reasons i am unable to relock the bootloader. Just want to know that will I be able to receive OTA updates even when the bootloader is unlocked or should i have to relock the bootloader?
Click to expand...
Click to collapse
Unlocked bootloader, doesn't matter with updates, or system flash..only when one needs Root, then the bootloader needs unlocked, unless a Root exploit is used..
sent by my
5.0_22.11.6 Lollipop (Rooted)
TWRP v2.8.0.1-titan
UPDATE-SuperSU-v2.16
XT1064 Moto G (2nd Gen.)
http://waynekent.com/page6.html
"Praise Jah" YOU people.!
Try this:
Flash Stock firmware using these commands in this order:
Code:
[B]mfastboot.exe oem lock begin[/B]
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
[B]mfastboot.exe oem lock[/B]
mfastboot.exe reboot
Hope this helps
KrishnaSagar said:
Flash Stock firmware using these commands in this order:
Code:
[B]mfastboot.exe oem lock begin[/B]
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
[B]mfastboot.exe oem lock[/B]
mfastboot.exe reboot
Hope this helps
Click to expand...
Click to collapse
i have already entered all these commands and successfully flashed stock rom. But when i enter mfastboot.exe oem lock, its shows as (bootloader) sst lock failure.
That is the standard procedure, but if you are getting errors then please refer to this thread:
http://forum.xda-developers.com/moto-g-2014/general/guide-explaining-boot-loader-locking-t2933827
KrishnaSagar said:
That is the standard procedure, but if you are getting errors then please refer to this thread:
http://forum.xda-developers.com/moto-g-2014/general/guide-explaining-boot-loader-locking-t2933827
Click to expand...
Click to collapse
I have followed the exact steps as mentioned in this thread. But still unable to relock the bootloader.
But I read somewhere that i can still get OTA updates even if bootloader is unlocked as long as i am in stock firmware and recovery. Is that true?
sandy1636 said:
I have followed the exact steps as mentioned in this thread. But still unable to relock the bootloader.
But I read somewhere that i can still get OTA updates even if bootloader is unlocked as long as i am in stock firmware and recovery. Is that true?
Click to expand...
Click to collapse
Yes. OTA updates are available on Unlocked Bootloader as long as you dont Root or change the recovery.
Thread hijack: If you have an unlocked bootloader and rooted xt1068 (and using Philz kernel) on the stock ROM, can you expect to get the OTA update?
I'm finding conflicting responses to this on searching and if I need to go back to stock recovery would happily do that, but I don't want to wipe my device.
grayme said:
Thread hijack: If you have an unlocked bootloader and rooted xt1068 (and using Philz kernel) on the stock ROM, can you expect to get the OTA update?
I'm finding conflicting responses to this on searching and if I need to go back to stock recovery would happily do that, but I don't want to wipe my device.
Click to expand...
Click to collapse
We shall see when the OTA is pushed to blighty. My advice would be to backup the boot, recovery and system partitions in their factory state before tinkering. I just rooted the stock ROM by booting from a TWRP image via fastboot, installed SuperSU and then used dd to image /boot, /recovery and /system to an external SD. If the OTA fails due to me having installed Xposed and removed system apps, I'll just restore the /system image and remove SuperSU... A wipe of the /data partition shouldn't be required.
If the OTA fails for you, I'd suggest flashing back the stock boot, recovery, and system images from the stock retgb firmware zip using fastboot and then trying the OTA upgrade process again.
rufflove said:
We shall see when the OTA is pushed to blighty. My advice would be to backup the boot, recovery and system partitions in their factory state before tinkering. I just rooted the stock ROM by booting from a TWRP image via fastboot, installed SuperSU and then used dd to image /boot, /recovery and /system to an external SD. If the OTA fails due to me having installed Xposed and removed system apps, I'll just restore the /system image and remove SuperSU... A wipe of the /data partition shouldn't be required.
If the OTA fails for you, I'd suggest flashing back the stock boot, recovery, and system images from the stock retgb firmware zip using fastboot and then trying the OTA upgrade process again.
Click to expand...
Click to collapse
It's probably a bit late for me to use dd before I installed Xposed. Thankfully I did back up using CWM before I wiped in installing Lollipop from a thread on here. I think I'll just wait till Motorola decides to push OTA over here.
grayme said:
It's probably a bit late for me to use dd before I installed Xposed. Thankfully I did back up using CWM before I wiped in installing Lollipop from a thread on here. I think I'll just wait till Motorola decides to push OTA over here.
Click to expand...
Click to collapse
Aye, but you should be able to flash back the stock system image from the 4.4.4 release using Motorola's fastboot. I dunno if the standard fastboot or any of custom recovery distros support sparse images. There must also be some way of converting the partial, sparse files into a normal image, too... I guess the questions is whether it's more of faff to start from a formatted data partition, or not.
rufflove said:
Aye, but you should be able to flash back the stock system image from the 4.4.4 release using Motorola's fastboot. I dunno if the standard fastboot or any of custom recovery distros support sparse images. There must also be some way of converting the partial, sparse files into a normal image, too... I guess the questions is whether it's more of faff to start from a formatted data partition, or not.
Click to expand...
Click to collapse
I used to understand these phones, but everything just seems so much more complicated these days!
I'm getting old.
Hi,
I have a Brazilan version XT1097, bootloader unlocked but no root yet.
I cannot install anything from play store because I get an error that does not say much.
All I did was trying to root using a guide I found that tells you to use CF-Autoroot, but it just did not work.
Then I installed TWRP to see if there was any ROMs available since I came from the Nexus 5 and was used to see tons of ROMs on xda to grab and flash.
To my surprise, none is available so far.
Now I am trying to find the original 1097 images to flash on my device and go back to stock.
Might even give up on root, if necessary, but I need the phone back
Any ideas on how to proceed?
A different problem now
The user seco2004 (http://forum.xda-developers.com/member.php?u=4946010) has provided me with his backup image.
I followed the steps on the motorola website to flash all the files but my phone is stuck at the bootloader warning message, that one that says that the bootloader is unlocked.
When I entered TWRP to wipe all over again, it says there is no system installed...
Any pointers are most welcome!
leandroqm said:
The user seco2004 (http://forum.xda-developers.com/member.php?u=4946010) has provided me with his backup image.
I followed the steps on the motorola website to flash all the files but my phone is stuck at the bootloader warning message, that one that says that the bootloader is unlocked.
When I entered TWRP to wipe all over again, it says there is no system installed...
Any pointers are most welcome!
Click to expand...
Click to collapse
I'm not sure if this is what you tried before, but there's pretty much no chance of anything going wrong if you follow the commands:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img (maybe you missed this part? instead of the "system.img", you need to flash the system files one at a time, something like: mfastboot flash system systemfile_1.img, the mfastboot flash system systemfile_2.img, and then proceed with the commands below)
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem config carrier vzw
fastboot oem fb_mode_clear
After all this the phone should boot normally into stock 4.4.4. Sorry for the delay, Tapatalk didn't notify me , hope you got it fixed already.
seco2004 said:
I'm not sure if this is what you tried before, but there's pretty much no chance of anything going wrong if you follow the commands:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img (maybe you missed this part? instead of the "system.img", you need to flash the system files one at a time, something like: mfastboot flash system systemfile_1.img, the mfastboot flash system systemfile_2.img, and then proceed with the commands below)
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem config carrier vzw
fastboot oem fb_mode_clear
After all this the phone should boot normally into stock 4.4.4. Sorry for the delay, Tapatalk didn't notify me , hope you got it fixed already.
Click to expand...
Click to collapse
Yes, I dit it that same night (morning, I should say) by the very same process you described.
Thank you a lot for the images and responses!
leandroqm said:
Yes, I dit it that same night (morning, I should say) by the very same process you described.
Thank you a lot for the images and responses!
Click to expand...
Click to collapse
Did you get it working?
Sent from my XT1097 using Tapatalk
seco2004 said:
Did you get it working?
Sent from my XT1097 using Tapatalk
Click to expand...
Click to collapse
Yes, absolutely!
I upgraded it to lollipop and rooted right afterwards
How did you get a 1097 stock Lollipop image?
TheAquanox said:
How did you get a 1097 stock Lollipop image?
Click to expand...
Click to collapse
secco2004 shared me his backups
But is it 1097 lollipop or 1095 with the módem from 1097? Can you share dais backup? I'm Being unable to tether and would like to find out if it is the rom or the phone.
Greetings !
It was actually the KK 4.4.4 original images.
I had to update to lollipop right after via OTA.
IDK if secco2004 allows me to share it. Could you PM him, please?
He posted recently on the topic.
Yeah, it was actually the 4.4.4 Brazilian firmware, feel free to share it. For lollipop I have just the flasheable zip.
Sent from my XT1097 using Tapatalk
Since secco2004 said it is ok to share, tell me if you want me to sent it somewhere...
It is the XT1097 4.4.4 brazilian original images.
hey, can I have XT1097 stock images please?
I also need it
I flashed NX CM12.1 v3.0 rom and lost gps.
Someone in the thread said that i have to go back to stock, verify gps is working properly... blah, blah, blah.....
So the thing is that i don´t know what stock image to use on my phone and where to get it.
It is a XT1097.
Can any of you guys help me?
Need help please
I've flashed ATT_XT1097_5.0.2_system_ ext4_ root.zip using Mofo.exe and followed directions to the T but soon as its done flashing I reboot back into fastboot mode to wipe the cache but gives me error hab check failed for recovery failed to validate recovery image boot up failed. Please any help would be a life savor i'm lost. Anyone know where to find recovery.img file for Moto X XT1097 stock image file maybe I can flash in fastboot mode? I just hope I Dont have a bricked device. I am stuck in bootloop mode and can't wipe cache.
Thanks!
I really thank you, it worked for me! :good:
Hi guys,
So I have an XT1092. It all started out innocently enough, when I flashed the 5.1 full firmware from the fourth post in this thread. It didn't want to work and got stuck in a... let's just call it a bootloop..., no matter what I did. So I re-flashed the 5.0 firmware that had worked previously. Same thing.
So then I figured that since it's not working, I may as well try converting it to a XT1095 as per this thread. Which worked! I was running 4.4.4 last night and all was good.
Then, it took an OTA in the early hours of this morning, which has since resulted in me losing all ability to use the phone at all.
When I hold the power button, a green light briefly flashes, which typically means that's the battery is dead (it was on charge all night, and still connected at this time). But when I hook it up to my PC, it shows up as a "QHUSB_BULK" - whatever that is.
...what can I do, guys?
Sorry, but there is nothing you can do if it says that. You will have to send it in for repair.
Sent from my XT1095
OP said:
So I have an XT1092. It all started out innocently enough, when I flashed the 5.1 full firmware from the fourth post in this thread. It didn't want to work and got stuck in a... let's just call it a bootloop..., no matter what I did.
Click to expand...
Click to collapse
When you did that, you upgraded the bootloader and partition table to 5.1.
OP said:
So I re-flashed the 5.0 firmware that had worked previously. Same thing.
Click to expand...
Click to collapse
When you did that, it did not downgrade the bootloader and partition table - they stayed on 5.1.
OP said:
So then I figured that since it's not working, I may as well try converting it to a XT1095 as per this thread. Which worked! I was running 4.4.4 last night and all was good.
Click to expand...
Click to collapse
When you did that, it did not downgrade the BL and PT - they stayed on 5.1.
OP said:
Then, it took an OTA in the early hours of this morning, which has since resulted in me losing all ability to use the phone at all.
Click to expand...
Click to collapse
When you did that, the OTA tried to patch the 5.1 BL and PT as if they were the 4.4.4 BL and PT. But you were running the 5.1 BL and PT. That caused a brick.
OP said:
When I hold the power button, a green light briefly flashes, which typically means that's the battery is dead (it was on charge all night, and still connected at this time). But when I hook it up to my PC, it shows up as a "QHUSB_BULK" - whatever that is.
...what can I do, guys?
Click to expand...
Click to collapse
Wait for someone to release the blankflash files for 5.1 (which were never leaked for 4.4.4 or 5.0 so they may never be leaked) or send it in for warranty replacement.
unfnknblvbl said:
Hi guys,
So I have an XT1092. It all started out innocently enough, when I flashed the 5.1 full firmware from the fourth post in this thread. It didn't want to work and got stuck in a... let's just call it a bootloop..., no matter what I did. So I re-flashed the 5.0 firmware that had worked previously. Same thing.
So then I figured that since it's not working, I may as well try converting it to a XT1095 as per this thread. Which worked! I was running 4.4.4 last night and all was good.
Then, it took an OTA in the early hours of this morning, which has since resulted in me losing all ability to use the phone at all.
When I hold the power button, a green light briefly flashes, which typically means that's the battery is dead (it was on charge all night, and still connected at this time). But when I hook it up to my PC, it shows up as a "QHUSB_BULK" - whatever that is.
...what can I do, guys?
Click to expand...
Click to collapse
Well, I see you used my post to downgrade to 4.4.4 and worked for you. And that's odd, because you flashed the "official" firmware of your model previously and got a bootloop. And some people are saying that downgrading your firmware from 5.1 to 4.4.4 will brick and that's not your case.... You bricked after taking the OTA and that's weird because after flashing the 5.1 of your model you upgraded your partition and your boot loader. What I am guessing here is that maybe the partitions and the boot loader of a different version like yours are incompatible with the pure edition. Maybe you can share with us what did you do after the first bootloop to downgrade to the 4.4.4, like what files did your use and what fastboot commands did you use too.
Sorry for your phone, but in several post people are warning that after downgrading from a 5.1 soak you don't have to take OTA.
juliospinoza said:
Sorry for your phone, but in several post people are warning that after downgrading from a 5.1 soak you don't have to take OTA.
Click to expand...
Click to collapse
These aren't Nexus devices. People can't flash whatever they want, downgrade and then take OTAs and never have to worry about bricking.
Rule of thumb - when in doubt don't flash the bootloader or partition table and never take an OTA after downgrading the bootloader.
JulesJam said:
These aren't Nexus devices. People can't flash whatever they want, downgrade and then take OTAs and never have to worry about bricking.
Rule of thumb - when in doubt don't flash the bootloader or partition table and never take an OTA after downgrading the bootloader.
Click to expand...
Click to collapse
That's exactly what I said, but you made it more "sophisticated" taking Nexus devices as an example. Don't see the point to repost.
juliospinoza said:
Don't see the point to repost.
Click to expand...
Click to collapse
My response was succinct, used a memorable distinction as well as a catchy rule of thumb and had adequate paragraph breaks. IOW easier to understand with a nice rhythm to it.
Try to sent to warranty centre , but in my case Motorola didn't cover me this issue.
juliospinoza said:
Maybe you can share with us what did you do after the first bootloop to downgrade to the 4.4.4, like what files did your use and what fastboot commands did you use too.
Click to expand...
Click to collapse
Right, so here's what I did.
1) the 5.1 OTA never worked for me - would always fail during flashing for some reason. So when I found the above post, I flashed the "VICTARA_RETEU_XT1092__5.1_LPE23.32-25.1_cid7_CFC.xml" package with the following commands:
Code:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
mfastboot flash boot boot.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 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 modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot reboot
Then seeing as it didn't want to work, and from prior experience with TWRP being annoying, I then flashed the recovery with "mfastboot flash recovery recovery.img"
Then came the bootloops. Now, I say "bootloops" but it was more complicated than that. What would happen is the boot animation would load up, then once the screen "dimmed" it would turn off. As I didn't clear userdata the first time, it would do the whole "android is upgrading x/65749823562743 apps" message... then reboot after the last one, and start again from the start. I cleared cache and userdata and then something else happened; after the screen dimming, it would turn 'off' but apparently still load. Every now & then, the screen would flash on for just an instant. Long enough for me to see some kind of error, but not long enough to find out what.
2) Giving up on this, I re-flashed the 5.0 "RETEUALL_XT1092_5.0_LXE22.46-19_cid7_CFC.xml" package with the following script:
Code:
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
mfastboot flash boot boot.img
mfastboot flash recovery twrp-2.8.6.0-victara.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 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 modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot reboot
Nothing remarkable there, although I notice that I didn't flash gpt.bin. Can't think why I didn't do that right now, tbh
Anyway, exactly the same issue occurred!
3) not having the patience to deal with that **** as it was nearing 3am, I flashed 4.4.4 "TMO_21.21.42.victara_tmo.tmo.en.US" with the following script:
Code:
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 flash fsg fsg.mbn
mfastboot erase userdata
mfastboot erase cache
mfastboot reboot
...which worked! The phone started normally and all seemed good. I was pretty chuffed.
Then, without thinking I accepted the 5.0 OTA when I awoke all bleary-eyed this morning, and she died. And here we are.
Motorola support seems to think I should return it to them, so they're coming to pick it up on Friday morning. heh.
unfnknblvbl said:
Motorola support seems to think I should return it to them, so they're coming to pick it up on Friday morning. heh.
Click to expand...
Click to collapse
They should give you a warranty replacement - their OTAs should have checks in them to fail to update rather than brick a device when you are running a newer BL than the one the OTA was written to update. This is their fault. Poor coding on the part of the software devs who wrote the OTAs.
The OTAs should check the bootloader version. If it is not the version the OTA was meant to update, the OTA should simply fail to update. End of problem. One simple IF-THEN statement would prevent this.
you'd think so....
unfnknblvbl said:
Right, so here's what I did.
1) the 5.1 OTA never worked for me - would always fail during flashing for some reason. So when I found the above post, I flashed the "VICTARA_RETEU_XT1092__5.1_LPE23.32-25.1_cid7_CFC.xml" package with the following commands:
Code:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
mfastboot flash boot boot.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 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 modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot reboot
Then seeing as it didn't want to work, and from prior experience with TWRP being annoying, I then flashed the recovery with "mfastboot flash recovery recovery.img"
Then came the bootloops. Now, I say "bootloops" but it was more complicated than that. What would happen is the boot animation would load up, then once the screen "dimmed" it would turn off. As I didn't clear userdata the first time, it would do the whole "android is upgrading x/65749823562743 apps" message... then reboot after the last one, and start again from the start. I cleared cache and userdata and then something else happened; after the screen dimming, it would turn 'off' but apparently still load. Every now & then, the screen would flash on for just an instant. Long enough for me to see some kind of error, but not long enough to find out what.
Click to expand...
Click to collapse
I think I know what generated the bootloop, happened to me two days ago. When you upgraded your system and data partition and didn't erased your data, the old data tried to "fit" the new partition, that's why the system the first time was trying to update your apps, but after failing entered again on bootloop. Don't know why this happens, from 4.4.4 to 5.0 you could upgrade without erasing data and nothing happened.
unfnknblvbl said:
2) Giving up on this, I re-flashed the 5.0 "RETEUALL_XT1092_5.0_LXE22.46-19_cid7_CFC.xml" package with the following script:
Code:
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
mfastboot flash boot boot.img
mfastboot flash recovery twrp-2.8.6.0-victara.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 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 modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot reboot
Nothing remarkable there, although I notice that I didn't flash gpt.bin. Can't think why I didn't do that right now, tbh
Anyway, exactly the same issue occurred!
Click to expand...
Click to collapse
Although you didn't flashed the gpt nothing would happened, just an error on fastboot, because you can't downgrade bootloader, the first time you flashed the new version 60.16 and the version on 5.0 is the 60.11.
The bootloop happened because the same reason, your data was there and the system wasn't able to make it "fit" to the new partition, the one you flashed with the 5.1.[/QUOTE]
unfnknblvbl said:
3) not having the patience to deal with that **** as it was nearing 3am, I flashed 4.4.4 "TMO_21.21.42.victara_tmo.tmo.en.US" with the following script:
Code:
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 flash fsg fsg.mbn
mfastboot erase userdata
mfastboot erase cache
mfastboot reboot
...which worked! The phone started normally and all seemed good. I was pretty chuffed.
Then, without thinking I accepted the 5.0 OTA when I awoke all bleary-eyed this morning, and she died. And here we are.
Motorola support seems to think I should return it to them, so they're coming to pick it up on Friday morning. heh.
Click to expand...
Click to collapse
OK. After your final flash you flashed the system and erased data and cache, and the partitions were "clear" from all apps and other stuff, so the system was able to "fit" your data to the partitions properly, that's why your phone booted as brand new, am I right??? Seems that the partitions are compatible from 4.4.4 to 5.1 only if you erase data.
The problem is the next. The first flash set the new bootloader 60.16 and the new partitions, but when you didn't erase your data and cache the phone created a conflict with the old data and new partitions (that's the reason of the bootloop) but, when you flashed the 4.4.4 and erased your data the phone was able to boot with the new partitions. The brick was caused because of the OTA of 5.0 and that's because 5.0 uses bootloader version 60.11 and you were already on 60.16 and, the big problem with motorola OTA's is that they didn't check the mismatch between bootloaders like fastboot does, so the OTA forced the downgrade "thinking" it was an upgrade and bricked your phone. Fastboot didn't allow you to downgrade bootloader, but clearly OTA does and that's the reason of bricked devices.
Your phone should be on warranty because it wasn't your fault (not entirely) because of faulty OTA's.
Resuming. After you are on bootloader version 60.14 or 60.16 you can't take any 5.0 OTA because the mismatch between old and nw bootloaders.
Glad to see that motorola are taking to warranty. And thanks for your well explained situation so everybody could take it as reference!
juliospinoza said:
I think I know what generated the bootloop, happened to me two days ago. When you upgraded your system and data partition and didn't erased your data, the old data tried to "fit" the new partition, that's why the system the first time was trying to update your apps, but after failing entered again on bootloop. Don't know why this happens, from 4.4.4 to 5.0 you could upgrade without erasing data and nothing happened.
Click to expand...
Click to collapse
I forgot to mention; before attempting the downgrade to 5.0, I was able to enter recovery and do a factory reset - I wiped userdata and even the sdcard, and that's where it started just 'looping' with the odd screen flicker.
The fact that it still shows up as something in Windows Device Manager gives me hope. If it were completely out of warranty, I'd try to hack the Qualcomm rescue tools for other phones that report that same QHSUSB_BULK device into doing something with this.
unfnknblvbl said:
I forgot to mention; before attempting the downgrade to 5.0, I was able to enter recovery and do a factory reset - I wiped userdata and even the sdcard, and that's where it started just 'looping' with the odd screen flicker.
The fact that it still shows up as something in Windows Device Manager gives me hope. If it were completely out of warranty, I'd try to hack the Qualcomm rescue tools for other phones that report that same QHSUSB_BULK device into doing something with this.
Click to expand...
Click to collapse
The issue isn't the tools. The tool for reflashing is there. But you need a bin and hex file specific to your device/bootloader that only Moto has right now. Unless it is released/leaked, SOL right now unfortunately.
Sent from my Moto X 2014 Pure Edition using Tapatalk
So, the phone has been sent back to me on the same day they received it. No call, no email. nothing. Weird. I hope they fixed it - I assume they did, otherwise they would have contacted me for payment info.
I'll report back!
Success!
Replaced main PCB, rear inlay - software upgraded to current version 5.1.1 - checked current drain - QC/CIT passed to manufacturer's specifications. New IMEI.
Click to expand...
Click to collapse
...this is probably because I'm in Australia though, and the warranty-voiding disclaimer about unlocking your bootloader isn't legal here. I think. I am not a lawyer.
New bootloader: 60.16
Bam.
Same Model .. Hard Bricked xt1092
i bought it a month ago from flipkart.
when i was doing the OTA update from 4.4.4 to 5.0.2 the installation finished from the recovery and never booted.
when i try to plug in to PC its shows QHUSB_BULK
i tried blankflash but it says FAILED
all the drivers are installed something that ends with Qualcomm.. 9008
is there any way that i cn unbrick it myself?
warmachine68 said:
i bought it a month ago from flipkart.
when i was doing the OTA update from 4.4.4 to 5.0.2 the installation finished from the recovery and never booted.
when i try to plug in to PC its shows QHUSB_BULK
i tried blankflash but it says FAILED
all the drivers are installed something that ends with Qualcomm.. 9008
is there any way that i cn unbrick it myself?
Click to expand...
Click to collapse
Sorry it is impossible to fix yourself. You will have to send it in for repair.
Sent from my XT1095 using Tapatalk
hello all right with you, I hope so, I am Brazilian, and I would take a doubt on the bike variant g2 xt1078 of my region (Brazil).
Accidentally I Flashed the ROM xt1068 on my mobile xt1078, and now the first command "mfastboot.exe flash partition gpt.bin" shows the error "GPT Version Downgrade". And then camndo "mfastboot.exe flash system system.img_sparsechunk.0" It also shows the error "Image is too large" with this system partition has been reduced or changed, I wonder if this has repair, and that any suggestion and welcome.
@lost101
@Kamin4ri
@VitaTaf
@parrotgeek1
l.rochas
Is your Bootloader unlocked?
lost101 said:
Is your Bootloader unlocked?
Click to expand...
Click to collapse
yes unlocked.
What is the exact name of the XT1078 firmware image your are currently trying to flash?
lost101 said:
What is the exact name of the XT1078 firmware image your are currently trying to flash?
Click to expand...
Click to collapse
this and the image of factory with august patch
XT1078_THEA_RETBR_DS_6.0_MPBS24.65-34-5_cid12_subsidy-DEFAULT_CFC.xml
mfastboot flash partition gpt.bin
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 system system.img_sparsechunk.4
And the rest of the commands operates normally
@l.rochas - Do commands in this order:
mfastboot flash motoboot motoboot.img
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 system system.img_sparsechunk.4
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
Use this version of mFastboot: https://www.androidfilehost.com/?fid=24052804347778493
lost101 said:
@l.rochas - Do commands in this order:
mfastboot flash motoboot motoboot.img
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 system system.img_sparsechunk.4
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
Use this version of mFastboot: https://www.androidfilehost.com/?fid=24052804347778493
Click to expand...
Click to collapse
@lost101
does not work, same mistakes previously said
lost101 said:
@l.rochas - Do commands in this order:
mfastboot flash motoboot motoboot.img
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 system system.img_sparsechunk.4
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
Use this version of mFastboot: https://www.androidfilehost.com/?fid=24052804347778493
Click to expand...
Click to collapse
@lost101
does not work, same mistakes previously said
l.rochas said:
@lost101
does not work, same mistakes previously said
Click to expand...
Click to collapse
The issue appears to be that you have flashed the XT1068 Bootloader and this cannot be simply undone by flashing the motoboot.img via mfastboot.
This thread describes the process for unbricking an XT1068, but may also be applicable for your handset. You will need another user with an XT1078 to provide you with the partition backups:
http://forum.xda-developers.com/moto-g-lte/help/moto-g-xt1068-aka-moto-g-2nd-generation-t3435052
There is a risk that this won't work and your phone will never turn on again.
If you prefer, you could just flash a custom Stock MM ROM (if available) or CM/AOSP ROM via TWRP.
lost101 said:
The issue appears to be that you have flashed the XT1068 Bootloader and this cannot be simply undone by flashing the motoboot.img via mfastboot.
This thread describes the process for unbricking an XT1068, but may also be applicable for your handset. You will need another user with an XT1078 to provide you with the partition backups:
http://forum.xda-developers.com/moto-g-lte/help/moto-g-xt1068-aka-moto-g-2nd-generation-t3435052
There is a risk that this won't work and your phone will never turn on again.
If you prefer, you could just flash a custom Stock MM ROM (if available) or CM/AOSP ROM via TWRP.
Click to expand...
Click to collapse
It seems to be a very risky method, but not hurt to try.
l.rochas said:
It seems to be a very risky method, but not hurt to try.
Click to expand...
Click to collapse
You already almost completely destroyed your handset by flashing the wrong bootloader. You don't exactly have many options here.
lost101 said:
The issue appears to be that you have flashed the XT1068 Bootloader and this cannot be simply undone by flashing the motoboot.img via mfastboot.
This thread describes the process for unbricking an XT1068, but may also be applicable for your handset. You will need another user with an XT1078 to provide you with the partition backups:
http://forum.xda-developers.com/moto-g-lte/help/moto-g-xt1068-aka-moto-g-2nd-generation-t3435052
There is a risk that this won't work and your phone will never turn on again.
If you prefer, you could just flash a custom Stock MM ROM (if available) or CM/AOSP ROM via TWRP.
Click to expand...
Click to collapse
I've tried this method.
After a backup of all partitions on another default XT1078, the restore process on my phone finished with error only on /system or /data (I don't remember well).
Then I've tried to boot, but it had boot loop, just blinking very fast the Warning screen of unlocked bootloader.
It didn't work. :/
The only working method was merging XT1068 and XT1078 ROMs. Now Wifi and Mobile Data are working.
Now I can't change this ROM. Lineage or the whole XT1078 stock can't be installed.
The problem was that I didn't realize I was applying a XT1068 ROM on a XT1078 phone.
As all partitions were changed by flashing gpt.bin, the correct gpt.bin of XT1078 can't be applied.
Any solution????
I am afraid that there is no solution right now. You already permanently ****ed up your machine by flashing a wrong motoboot.img and GPT, that is, by not using a correct ROM file. You were careless, because mfastboot is a DANGEROUS tool that requires CARE and a wrong use of this tool can turn your Moto device into a fancy black paperweight. It has no security measures that prevent you from flashing a stock ROM for a wrong device, which is what you did by not making sure that you were using a correct (or at least compatible) firmware.
I am afraid that your device is now crippled for life unless you somehow can force the correct motoboot and GPT in your phone (impossible AFAIK) or you get a new Thea motherboard and replace the current one. You are very lucky that you can still boot it, because most people in your situation are left with a permanent hard brick. Can you get into fastboot and is your bad bootloader unlocked? If so, you can try installing TWRP and LineageOS for Titan (then the worst you risk is a soft brick) or leave the "stock" franken-ROM that "works".
IMO you should get a spare XT1078 motherboard, unlock it's bootloader (AND NEVER TOUCH IT AGAIN UNLESS OTHERWISE SPECIFIED), flash TWRP and IMMEDIATELY flash LineageOS+GApps so you never have to deal with stock ROMs and the dangers they carry when handled carelessly. With custom AOSP based ROMs and recoveries the worst thing you risk is a soft brick, which you can fix by reflashing a proper custom ROM in TWRP and/or wiping partitions. No recovery? You still have a working fastboot to flash another TWRP. Messing with /system is MUCH SAFER than messing with your bootloader.
I hope you have learned a lesson about the real risk of flashing smartphone firmwares without doing enough research first. It's no game, a wrong step and no more phone for you.
benjausen said:
I am afraid that there is no solution right now. You already permanently ****ed up your machine by flashing a wrong motoboot.img and GPT, that is, by not using a correct ROM file. You were careless, because mfastboot is a DANGEROUS tool that requires CARE and a wrong use of this tool can turn your Moto device into a fancy black paperweight. It has no security measures that prevent you from flashing a stock ROM for a wrong device, which is what you did by not making sure that you were using a correct (or at least compatible) firmware.
I am afraid that your device is now crippled for life unless you somehow can force the correct motoboot and GPT in your phone (impossible AFAIK) or you get a new Thea motherboard and replace the current one. You are very lucky that you can still boot it, because most people in your situation are left with a permanent hard brick. Can you get into fastboot and is your bad bootloader unlocked? If so, you can try installing TWRP and LineageOS for Titan (then the worst you risk is a soft brick) or leave the "stock" franken-ROM that "works".
IMO you should get a spare XT1078 motherboard, unlock it's bootloader (AND NEVER TOUCH IT AGAIN UNLESS OTHERWISE SPECIFIED), flash TWRP and IMMEDIATELY flash LineageOS+GApps so you never have to deal with stock ROMs and the dangers they carry when handled carelessly. With custom AOSP based ROMs and recoveries the worst thing you risk is a soft brick, which you can fix by reflashing a proper custom ROM in TWRP and/or wiping partitions. No recovery? You still have a working fastboot to flash another TWRP. Messing with /system is MUCH SAFER than messing with your bootloader.
I hope you have learned a lesson about the real risk of flashing smartphone firmwares without doing enough research first. It's no game, a wrong step and no more phone for you.
Click to expand...
Click to collapse
Nice answer, benjausen.
I've done a lot of things on more than 10 different mobile phone models, but for the first time I think there is no complete solution.
My only solution was using a mix of XT1068 and XT1078 Stock ROMs, flashing one component per time. The only bug is on screen rotation that is rotating to the wrong side. The rest is fine.
I'd like to install LineageOS, but flashing isn't being possible. It is giving error.
Only the way I mentioned was successful. Is there any manual way to flash components separated instead of using a .zip file?
peacehope said:
Nice answer, benjausen.
I've done a lot of things on more than 10 different mobile phone models, but for the first time I think there is no complete solution.
My only solution was using a mix of XT1068 and XT1078 Stock ROMs, flashing one component per time. The only bug is on screen rotation that is rotating to the wrong side. The rest is fine.
I'd like to install LineageOS, but flashing isn't being possible. It is giving error.
Only the way I mentioned was successful. Is there any manual way to flash components separated instead of using a .zip file?
Click to expand...
Click to collapse
I don't have a lot of advice for you, as a previous post states your options are pretty much limited. Try flashing individual .img files from a LineageOS ROM. Try downloading one for Titan and patching the images inside it.
benjausen said:
I don't have a lot of advice for you, as a previous post states your options are pretty much limited. Try flashing individual .img files from a LineageOS ROM. Try downloading one for Titan and patching the images inside it.
Click to expand...
Click to collapse
I don't have now a LineageOS ROM to check, but if I'm not wrong, it doesn't have each separated file as Stock ROM. Am I wrong?
I've flashed many Stock ROMs manually file by file, but never with custom ROMs.
Can you please provide any link teaching this with custom ROMs? I really want to try this.
Maybe this can be a solution, and if it works we will help many people here.